Bavarian Demon Cortex PRO is here!!
#304
My Feedback: (2)
I guess you could run 2 RX into the Cortex, and only have RX1 connected from the gyro to the CB, and then a 3rd RX direct into the CB RX2 port.
That way, you could build time on the Cortex and look for any further signal switching lockout issues, and still have an independent RX direct into the CB to protect against a lockout.
I assume you'd have to run them all in clone mode, but I have never tried it.
Paul
That way, you could build time on the Cortex and look for any further signal switching lockout issues, and still have an independent RX direct into the CB to protect against a lockout.
I assume you'd have to run them all in clone mode, but I have never tried it.
Paul
#305
My Feedback: (53)
I guess you could run 2 RX into the Cortex, and only have RX1 connected from the gyro to the CB, and then a 3rd RX direct into the CB RX2 port.
That way, you could build time on the Cortex and look for any further signal switching lockout issues, and still have an independent RX direct into the CB to protect against a lockout.
I assume you'd have to run them all in clone mode, but I have never tried it.
Paul
That way, you could build time on the Cortex and look for any further signal switching lockout issues, and still have an independent RX direct into the CB to protect against a lockout.
I assume you'd have to run them all in clone mode, but I have never tried it.
Paul
#306
Join Date: Oct 2008
Location: St-Jean sur Richelieu,
QC, CANADA
Posts: 457
Likes: 0
Received 0 Likes
on
0 Posts
Hello All,
Can someone explain clearly the issue or what may happen, I'm not sure I completely understand the (possible) issue. Is it only in Jeti CB setup or also apply to other setup like X24 or powerbox ? I'm planning to buy a Cortex Pro on my very soon project and I would like to know more about this (I will use dual futaba SBus receivers to Cortex Pro and to an expander (probably a PowerBox)).
Thanks
Can someone explain clearly the issue or what may happen, I'm not sure I completely understand the (possible) issue. Is it only in Jeti CB setup or also apply to other setup like X24 or powerbox ? I'm planning to buy a Cortex Pro on my very soon project and I would like to know more about this (I will use dual futaba SBus receivers to Cortex Pro and to an expander (probably a PowerBox)).
Thanks
Last edited by RobinLeblond; 08-17-2017 at 10:53 AM. Reason: Just dicovered that X24 doesn't support anything between it ports and the Rx
#307
My Feedback: (16)
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.
Thanks
Last edited by Reever45; 08-21-2017 at 01:26 PM. Reason: Meant to say REX7
#309
My Feedback: (99)
Maybe I am thinking about it wrong, but: If the CP blocks RX1 and RX2 is active to the CB, wouldn't you get an alarm and be able to land the plane? And if Demon is right and they have fixed it with the update, then RX2 should not ever take over under normal circumstances?
#312
We have no reported lockout issues since v1.4 has been released. If you know of this first hand please post it or have the person who has had a lockout with v1.4 post here or contact us.
#314
My Feedback: (28)
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 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
#315
Thread Starter
I ran my second rx REX 7 directly to the CB200 and bypassed the CP, my question is why you are hooking the telemetry up from CB200 EXT to the expander plugged into REX7? i left my expander plugged into EXT port on CB200 with my telemetry plugged into it and nothing into the rx2 and all telemetry seems fine?
Thanks
Thanks
#316
My Feedback: (10)
Make sure you all upgrade to 3.24 according to Jeti there could be a issue with internal data overload.
losing sync all the double path setups could be affected.
especially if you use lots of sensors and telemtric.
make sure you get the latest Firmware for the cortex AND Jeti..
losing sync all the double path setups could be affected.
especially if you use lots of sensors and telemtric.
make sure you get the latest Firmware for the cortex AND Jeti..
#317
My Feedback: (7)
Tom,
Maybe I am thinking about it wrong, but: If the CP blocks RX1 and RX2 is active to the CB, wouldn't you get an alarm and be able to land the plane? And if Demon is right and they have fixed it with the update, then RX2 should not ever take over under normal circumstances?
Maybe I am thinking about it wrong, but: If the CP blocks RX1 and RX2 is active to the CB, wouldn't you get an alarm and be able to land the plane? And if Demon is right and they have fixed it with the update, then RX2 should not ever take over under normal circumstances?
Connecting Rx2 directly to the Central box will prevent any loss of control but I don't think you would ever know that the problem occurred..I think telemetry and everything else from the central box would simply go through Rx2 and unless you could tell that you no longer had stabilization you would never know it happened...Probably the most likely way you would know something happened is that since most use much less expo when the Cortex is on vs off your airplane would simply seem more sensitive if the problem occurred..
#318
Thread Starter
you can set it to alarm you at the loss of signal 1. but remember the PRO will switch at a low Q. and its normal to use both receivers in a low Q.
I wish Jeti had a way of telling us which receiver port is the driver port at any given point, but it doesn't.
I wish Jeti had a way of telling us which receiver port is the driver port at any given point, but it doesn't.
#320
My Feedback: (99)
Make sure you all upgrade to 3.24 according to Jeti there could be a issue with internal data overload.
losing sync all the double path setups could be affected.
especially if you use lots of sensors and telemtric.
make sure you get the latest Firmware for the cortex AND Jeti..
losing sync all the double path setups could be affected.
especially if you use lots of sensors and telemtric.
make sure you get the latest Firmware for the cortex AND Jeti..
#322
My Feedback: (7)
In general if a receiver is having trouble receiving data for any amount of time it will show up as a low Q value but I'm pretty sure that the CB200 decides whether to use Rx1 or Rx2 on a frame by frame basis so it should be possible for Rx2s data to be used if RX1 simply dropped a couple of frames but still has a Q value of 98%..
#323
My Feedback: (7)
While it's possible to alarm on loss of Rx1 when I had the Cortex Pro lock up before the latest firmware update I never got an alarm because the link between both receivers and the transmitter was perfect, there was simply no data passed between the Cortex Pro and the CB200. I lost telemetry from the CB200 which I didn't have any alarms set for at the time so I had no indication that anything bad had happened until the CB200 went into failsafe. If someone connects Rx2 directly to the CB200 I don't think they will even lose CB200 telemetry so I don't think they would necessarily notice anything was wrong if the Cortex Pro stopped sending EX Bus data from Rx1 to the CB200. That is the only reason I'm not a fan of the Rx2 direct to the CB200 configuration. While it should protect your model, which is a very good thing it seems it also masks this issue to the point where you may never know if a problem still exists..Based on the information available I'm actually pretty confident that the latest firmware will resolve this issue, I still have another issue that I need to get to the bottom off before flying again but I think as soon as I'm sure that's been taken care of I'm going to simply connect both receivers directly to the Cortex Pro.
#324
My Feedback: (2)
Wayne,
Are you suggesting that the CP merges the RX1 & RX2 data and re-broadcasts the 'best' signal along with gyro inputs onto both RX1 & RX2 outputs to the CB. If that were to happen, the CB would never see a single RX drop-out as the CP would 'fill-in' on its output.
I would have expected that the CP would keep the 2 RX streams completely separate and pass them through with added gyro commands, letting the CB determine which RX to use.
On your point about bypassing the CP with RX2, I have flown my Ultra Flash with the gyro inadvertently set to 0% gain (remember the DS-16 s/w error earlier this year). It flew very differently and it was immediately apparent that something had changed. I'm sure for those cases where the CB switched to a non-gyro stabilized RX that I would notice a difference.
Paul
Are you suggesting that the CP merges the RX1 & RX2 data and re-broadcasts the 'best' signal along with gyro inputs onto both RX1 & RX2 outputs to the CB. If that were to happen, the CB would never see a single RX drop-out as the CP would 'fill-in' on its output.
I would have expected that the CP would keep the 2 RX streams completely separate and pass them through with added gyro commands, letting the CB determine which RX to use.
On your point about bypassing the CP with RX2, I have flown my Ultra Flash with the gyro inadvertently set to 0% gain (remember the DS-16 s/w error earlier this year). It flew very differently and it was immediately apparent that something had changed. I'm sure for those cases where the CB switched to a non-gyro stabilized RX that I would notice a difference.
Paul
#325
My Feedback: (7)
Wayne,
Are you suggesting that the CP merges the RX1 & RX2 data and re-broadcasts the 'best' signal along with gyro inputs onto both RX1 & RX2 outputs to the CB. If that were to happen, the CB would never see a single RX drop-out as the CP would 'fill-in' on its output.
I would have expected that the CP would keep the 2 RX streams completely separate and pass them through with added gyro commands, letting the CB determine which RX to use.
On your point about bypassing the CP with RX2, I have flown my Ultra Flash with the gyro inadvertently set to 0% gain (remember the DS-16 s/w error earlier this year). It flew very differently and it was immediately apparent that something had changed. I'm sure for those cases where the CB switched to a non-gyro stabilized RX that I would notice a difference.
Paul
Are you suggesting that the CP merges the RX1 & RX2 data and re-broadcasts the 'best' signal along with gyro inputs onto both RX1 & RX2 outputs to the CB. If that were to happen, the CB would never see a single RX drop-out as the CP would 'fill-in' on its output.
I would have expected that the CP would keep the 2 RX streams completely separate and pass them through with added gyro commands, letting the CB determine which RX to use.
On your point about bypassing the CP with RX2, I have flown my Ultra Flash with the gyro inadvertently set to 0% gain (remember the DS-16 s/w error earlier this year). It flew very differently and it was immediately apparent that something had changed. I'm sure for those cases where the CB switched to a non-gyro stabilized RX that I would notice a difference.
Paul
As for whether the Cortex Pro processes both streams separately I don;t know but if I had to guess I suspect data from both receivers is simply sitting in queues and if Rx1's data is valid it gets stabilized, if not then they try Rx2 but they may well have the processing horsepower to be constantly stabilizing both even though Rx2's data will be discarded if Rx1 is valid.
Last edited by wfield0455; 08-22-2017 at 11:51 AM.