Bavarian Demon Cortex PRO is here!!
06-07-2017, 01:31 PM
#251
Gain/mode setting is the same as with the original Cortex. Using the Gyro function in a Jeti system -30% = approx 30% gain in Bank 1. 30% = approx 30% in Bank 2. While the scaling/ratio of the individual tuning parameters is different in the Pro, the effect is very close to the original.
06-07-2017, 01:37 PM
#252
OK guys, thanks to your help and this forum I was able to update the software of the Cortex Pro and also to wire it correctly. I got this figured out now, but already have the next question. I find it very positive to be able to adjust the gains and most other functions right through the radio, but why is the gain adjustable between "3" and "20"? This makes the comparison the old percentages of the old Cortex pretty difficult. Also, how do I adjust the flight mode switch not to interfere with the gain set in the radio? The old Cortex understood "-30%" travel as 30% normal/dampening gain, but how will that work with the Pro???
Sorry for my stupid questions, but the manual s*cks big time and the transition from the old to the new Cortex is harder than I thought.
Thomas
Sorry for my stupid questions, but the manual s*cks big time and the transition from the old to the new Cortex is harder than I thought.
Thomas
06-07-2017, 03:56 PM
#255
ok 
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
06-12-2017, 08:56 AM
#256
ok
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
06-12-2017, 09:10 AM
#258
ok
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
FYI
The menu available in the radio duplicates the functionality of the Cortex Pro setup software. Normally there is no need to make changes to the Ail, Elev, Rud settings here prior to flying. Use the default values. Then tune as needed/desired based on flight performance. An overall gain setting (as driven by the aux channel) of 25-30% is very safe to start with.
Thomas
06-12-2017, 11:34 AM
#259
A screen capture of your gyro setup would simplify things. Just go to system menu, scroll to screen capture, assign a switch and then go to your gyro menu and flip the switch and it will write a bitmap of the screen to your SD card which you can post here. That said did you assign a tuning control and if so did you select it as 0 to 100% or -100% to +100% ? Also Tuning will not allow you to change the polarity of the value. For exampe a gyro setting of -10% with Tuning set to P7 (-100/+100) and the gyro sense field set to 30% will NOT provide a range of -40% to +20%, it will only allow adjustment from -40% to 0%. Without knowing how it's configured it's hard to know exactly what's going on.
06-21-2017, 06:21 AM
#263
I don't know the numbers but, if desperate, you can go into the software and reset back to factory defaults. Just remember to reset the orientation and re-teach afterwards.
08-09-2017, 10:00 PM
#270
Your sticks are not in neutral and your gyro has not locked yet. If you have trimmed the model or are using flight modes, this happens
You may have to tech in your gyro once more with new zero values to get rid of this because the sticks have to be in zero and calm before the PRO locks.
I have asked them to give us a GOOD-TO-GO flag when the gyro is locked. Then we can make a telemetry warning if we try to fly with unlocked gyro.
It is easy to overlook that rudder movements are missing when you are powering up the model.
When I am turning on my model, my DC 24 is saying " RECEIVER BOUND - WAIT FOR GYRO" , but I would also like to make an alarm saying " GYRO NOT READY" if I move the throttle-cut switch before the gyro has locked.
You may have to tech in your gyro once more with new zero values to get rid of this because the sticks have to be in zero and calm before the PRO locks.
I have asked them to give us a GOOD-TO-GO flag when the gyro is locked. Then we can make a telemetry warning if we try to fly with unlocked gyro.
It is easy to overlook that rudder movements are missing when you are powering up the model.
When I am turning on my model, my DC 24 is saying " RECEIVER BOUND - WAIT FOR GYRO" , but I would also like to make an alarm saying " GYRO NOT READY" if I move the throttle-cut switch before the gyro has locked.
08-09-2017, 10:14 PM
#271
Actually ver 1.4/1400.
- Mandatory update – respective the use of 2 serial receivers.
A rare potential problem in data processing, resulting from a very bad receiver signal strength combined with a multiple switching between the receivers, was corrected.
Software and firmware for stabilization systems by Bavarian Demon
- Mandatory update – respective the use of 2 serial receivers.
A rare potential problem in data processing, resulting from a very bad receiver signal strength combined with a multiple switching between the receivers, was corrected.
Software and firmware for stabilization systems by Bavarian Demon
08-10-2017, 12:26 AM
#272
Actually ver 1.4/1400.
- Mandatory update – respective the use of 2 serial receivers.
A rare potential problem in data processing, resulting from a very bad receiver signal strength combined with a multiple switching between the receivers, was corrected.
Software and firmware for stabilization systems by Bavarian Demon
- Mandatory update – respective the use of 2 serial receivers.
A rare potential problem in data processing, resulting from a very bad receiver signal strength combined with a multiple switching between the receivers, was corrected.
Software and firmware for stabilization systems by Bavarian Demon
Ok. I will run another upgrade :-)
08-10-2017, 06:26 PM
#273
Well, I got bit by the Cortex Pro dual serial data stream lockout issue today. I have had 40+ successful flights on my Ultra Flash with Jeti CB200 and dual R3/RSW receivers running through the Pro with no issues, until the second flight today.
I will admit that I haven't updated yet to the v1.4/1400 s/w as I only saw that notice today, and as I have never had problems and fly with repeatably good signal strength, I thought the risk was worth taking today, and planned to update tomorrow.
Luckily, the model went into failsafe and the motor shut down as I was pulling off my taxi-tank just prior to entering the runway. One minute later and it could have all ended in tears. 2-way comms between the Tx and the model was lost as the ECU telemetry data was flashing on the Tx, indicating that it was not being updated. Both receivers were reporting a 9/9/100% strength and quality - that link directly between the receivers and the Tx was still live.
Whilst the model was still powered and in full failsafe, I disconnected RX1 from the Cortex - no change - still in failsafe. I then connected RX1 directly to the CB200 and I immediately regained control of the model as it came out of failsafe.
To me, this proves that the Cortex Pro had locked out and stopped 2-way communication between both receivers and the Central Box.
As the v1.4/1400 s/w update has been stated to fix a rare LOW signal strength/ quality issue, I would contend that whilst Bavarian may have found an issue that was fixed, that the true root-cause of a HIGH signal strength/ quality shutdown has still not been found or fixed. I must have at least 10hrs of powered time on my Ultra Flash with the Cortex Pro (based upon engine hours) and have never seen this or any other issue before, so some complex set of conditions must have aligned today to cause the issue.
Along with updating the Cortex Pro to v1.4/1400, I will bypass the gyro on my back-up Rx2, and connect it directly to the Central Box, providing an independent link to the model. The CB will only switch to the backup Rx2 if the signal drops from Rx1, so loss of the gyro inputs to me is acceptable in this multiple failure case.
Looking forward to seeing the root-cause analysis and fix for this one.
Paul
I will admit that I haven't updated yet to the v1.4/1400 s/w as I only saw that notice today, and as I have never had problems and fly with repeatably good signal strength, I thought the risk was worth taking today, and planned to update tomorrow.
Luckily, the model went into failsafe and the motor shut down as I was pulling off my taxi-tank just prior to entering the runway. One minute later and it could have all ended in tears. 2-way comms between the Tx and the model was lost as the ECU telemetry data was flashing on the Tx, indicating that it was not being updated. Both receivers were reporting a 9/9/100% strength and quality - that link directly between the receivers and the Tx was still live.
Whilst the model was still powered and in full failsafe, I disconnected RX1 from the Cortex - no change - still in failsafe. I then connected RX1 directly to the CB200 and I immediately regained control of the model as it came out of failsafe.
To me, this proves that the Cortex Pro had locked out and stopped 2-way communication between both receivers and the Central Box.
As the v1.4/1400 s/w update has been stated to fix a rare LOW signal strength/ quality issue, I would contend that whilst Bavarian may have found an issue that was fixed, that the true root-cause of a HIGH signal strength/ quality shutdown has still not been found or fixed. I must have at least 10hrs of powered time on my Ultra Flash with the Cortex Pro (based upon engine hours) and have never seen this or any other issue before, so some complex set of conditions must have aligned today to cause the issue.
Along with updating the Cortex Pro to v1.4/1400, I will bypass the gyro on my back-up Rx2, and connect it directly to the Central Box, providing an independent link to the model. The CB will only switch to the backup Rx2 if the signal drops from Rx1, so loss of the gyro inputs to me is acceptable in this multiple failure case.
Looking forward to seeing the root-cause analysis and fix for this one.
Paul
Last edited by JSF-TC; 08-10-2017 at 06:29 PM.
08-10-2017, 06:37 PM
#274
08-10-2017, 06:42 PM
#275
Hey Paul,
Glad to hear it happened on the ground! I'm also a bit skeptical of the fix as I've had 2 events. The first was on the bench with the TX within a few feet of the plane, and second was post flight a few feet in front of me just as I set the brake to shut down. For now I'm holding off using the CP.
Glad to hear it happened on the ground! I'm also a bit skeptical of the fix as I've had 2 events. The first was on the bench with the TX within a few feet of the plane, and second was post flight a few feet in front of me just as I set the brake to shut down. For now I'm holding off using the CP.