|
VK, we are recommending that Secondary receiver be plugged directly into CB200 RX2. SO the CP will only have a wire in port b(in) and 6 (out). and a jumper wire for power.
for data, In my case, I have a Rex 7 as a backup rx, so I have an expander plugged in it, with the CB200 ext plugged into the expander along with a MUI30. all this runs through he secondary receiver whilst the airplane is running on the primary R3 through the CP serially.. Its working perfectly. we will look at Pauls data file and see what we can discover.. There is also ZERO issues with the umbilical setup. |
Danny,
You have mail! Many thanks for the follow-up. Paul |
Originally Posted by JSF-TC
(Post 12359275)
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 Similar experiences. Have you got E-mail adress? Mine is [email protected] |
Are we sure that in the case Secondary receiver would have been directly plugged in CB200 Rx2 port, bypassing the CortexPro, it would have avoid lockout, since Rx's signals were indication good 9/9/100% ?
|
Originally Posted by Looping31
(Post 12359319)
Are we sure that in the case Secondary receiver would have been directly plugged in CB200 Rx2 port, bypassing the CortexPro, it would have avoid lockout, since Rx's signals were indication good 9/9/100% ?
|
Originally Posted by ERRC
(Post 12359316)
|
Originally Posted by gooseF22
(Post 12359286)
VK, we are recommending that Secondary receiver be plugged directly into CB200 RX2. SO the CP will only have a wire in port b(in) and 6 (out). and a jumper wire for power.
for data, In my case, I have a Rex 7 as a backup rx, so I have an expander plugged in it, with the CB200 ext plugged into the expander along with a MUI30. all this runs through he secondary receiver whilst the airplane is running on the primary R3 through the CP serially.. Its working perfectly. we will look at Pauls data file and see what we can discover.. There is also ZERO issues with the umbilical setup. |
Originally Posted by F1 Rocket
(Post 12359332)
Yes, if the CB does not see data on RX1 it will switch to RX2.
So.. If you are going to go that route for now, the only thing extra to do, is to turn off the cortex pro sometime, and trim the model quickly.. this way the feel really won't change a lot for a few seconds it is on RX2. If you are pulling on the sticks when it happens, the CP isn't really doing a lot anyway, but the CP can hide a model being little out of trim.. What you might feel is the sensitivity increase. But if you originally put some expo in, that should be ok. I use a switch to disable any gyro.. 3 ways in the Jeti. One is to use the trim function on the gain.. the other is to free mix gain to gain at -100%, and the final is simply to put the gain channel on a knob or switch. I use the trim function, or the mix(when i have an Mspeed reducing gain at high speed). The standard setup with the umbilical like the original still works superbly.. the only thing you theoretically give up is the poly fuses. which take a direct short to trigger. something that I have never had happen, and only seen once.. A lot of people are looking at this issue.. stay tuned. update to TX4.23 and CP1.4 when you can |
Damn! Just fried my CB200. Misspinned when doing the Cortex Pro software update and Rx2 to CB. Does Esprit fix them. I suspect it is a blown fuse.
|
Originally Posted by tp777fo
(Post 12359616)
Damn! Just fried my CB200. Misspinned when doing the Cortex Pro software update and Rx2 to CB. Does Esprit fix them. I suspect it is a blown fuse.
|
Im really pissed. The Cortex Pro has been nothing but trouble. I couldnt get it to work in my JR stuff, and now the Jeti troubles. I finally got the 1.4 update done and when I put it back in the jet I couldnt get it to work. Not worth risking my airplane so I I just took the thing out and will fly just like I have for years....gyro less.
|
Hi Tom,
Sorry to hear of your troubles. Contact Esprit and they will replace the CB at the 50% crash discount. FYI to everyone, Be very careful connecting the leads to ports 4/5/and 6 of the Cortex Pro. It is easy to get the connector one or two pins off and create a short that can damage the Central Box. Also, never connect anything when the system is powered. |
This damage has been done multiple times, and will continue to be done, until Bavarian change the case design to prevent it, on the Pro and the heli equivalent unit.
It is that cutout in the case for the 3-pin connector that causes the issue. Until Bavarian change the case design, install a dummy connector across the pins of the unused port above the ones that go to the CB. Paul |
Originally Posted by gooseF22
(Post 12359286)
VK, we are recommending that Secondary receiver be plugged directly into CB200 RX2. SO the CP will only have a wire in port b(in) and 6 (out). and a jumper wire for power.
|
As for frying electronic parts: look 2 times plug it once..
i did the recomended setup. and all works fine as before, feels safer to be honnest. knowing that there is a failsafe now without third party electronics can or would block signals. |
I have done this as well with mine, but I'm hoping for Deamon will be able to fix this issue, I got these because it was a clean install (4 wires.....now 5) with Jeti for me it's no longer the case, this is a work around for a very serious issue.
|
The factory has released FW 1.4/1400 to correct the reported issues. As with many things in the Jeti system there are many ways to connect the Cortex Pro. The option to connect RX2 directly to the CB is just that, an option. It is not a "work around".
|
I am going to keep using mine as I have been, I haven't had any issues. Both Rx's into the Cortex Pro.
|
Originally Posted by AEROSHELDON
(Post 12360623)
I am going to keep using mine as I have been, I haven't had any issues. Both Rx's into the Cortex Pro.
we did not apply throttle yet , so yes feel free to disregard any word comming from demon and their distributors. your a dealer maybe you should inform about the firmware upgrade and recomand the bypass until all is solved?. i did the last recomendation. better safe then sorry.. |
Originally Posted by digitech
(Post 12360636)
i had 8 hours flight time then full lockout at start lucky enough
we did not apply throttle yet , so yes feel free to disregard any word comming from demon and their distributors. your a dealer maybe you should inform about the firmware upgrade and recomand the bypass until all is solved?. i did the last recomendation. better safe then sorry.. See POST 292.... ?? |
Originally Posted by AEROSHELDON
(Post 12360637)
Um, Demon says the update (that I installed) will fix it. So are you saying I should not trust Demon that it is actually fixed?
See POST 292.... ?? |
I'll stick with Danny on this one, but point taken. They seem to be split amongst themselves. Please allow me to enjoy my hobby as I see fit without bashing me though, and I will do the same for you.
Have a good one! |
2 Attachment(s)
Originally Posted by JSF-TC
(Post 12359715)
This damage has been done multiple times, and will continue to be done, until Bavarian change the case design to prevent it, on the Pro and the heli equivalent unit.
It is that cutout in the case for the 3-pin connector that causes the issue. Until Bavarian change the case design, install a dummy connector across the pins of the unused port above the ones that go to the CB. Paul Edited to add: The loop in the photo is NOT a wire. It is non-conductive plastic. |
Originally Posted by digitech
(Post 12360636)
i had 8 hours flight time then full lockout at start lucky enough
we did not apply throttle yet , so yes feel free to disregard any word comming from demon and their distributors. your a dealer maybe you should inform about the firmware upgrade and recomand the bypass until all is solved?. i did the last recomendation. better safe then sorry.. Ditto - I had at least 10hrs on mine, and decided to take the risk (albeit with the earlier v1.3 s/w) and I got bit - luckily whilst still on the ground (post #273). I have since updated the s/w to v1.4/1400 AND removed RX2 from the gyro, going direct to the CB. When Bavarian first released v1.4 they made a big deal about how the issue was only linked to a rare, low signal strength/ quality Rx switching problem (post #271). Now, my lockout was with both RX at 9/9/100%, so I can deduce one of 2 things; 1) Bavarian found a code issue and can absolutely link that issue to a LOW signal quality/ strength condition, which to me then implies that they have NOT fixed the underlying high signal strength/ quality lockout issue that I (at least) had, or; 2) The issue that Bavarian found and then fixed with the code is not related to signal strength/ quality, and the fix is good for all scenarios. Personally, until Bavarian come out and update us on what they have found, I will continue to bypass the gyro with Rx2, as I would lean more towards option 1) above being the case, and that another fix is needed. Paul |
I fixed mine...took it out. I didnt trust that the problem with passing the RX data to the CB wouldnt lock the entire system up even with RX2 directly connected to the CB. I found I like the way the jet flies better without than with. Wont use a Cortex Pro again until the problem is found and fixed.
|
| All times are GMT -8. The time now is 09:00 AM. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.