Jeti DS-24
#1901

My Feedback: (1)
"you connected a extra lead between channel 4 from the cortex to a free port on the cb? , since you cant use anything else then a receiver on a CB rx port"
Nope. The CortexPro had the two receivers in ports A&B and ports 5&6 went to the CB200. This is the standard setup as instructed by BD.
"What software version was your Cortex Pro at and were both RX's connected to the CB200 via the Cortex?"
I updated all devices to the latest firmware as of January 2021.
Thanks for your thoughts.
Nope. The CortexPro had the two receivers in ports A&B and ports 5&6 went to the CB200. This is the standard setup as instructed by BD.
"What software version was your Cortex Pro at and were both RX's connected to the CB200 via the Cortex?"
I updated all devices to the latest firmware as of January 2021.
Thanks for your thoughts.
#1904
i did the same a few years back , and on take of it went into failsafe , and i could just stop it by grabbing the tail....
since then the lead is allways there!.
you can NOT connect anything else then a RX onto a RX bus on the CB anything more can and will collapse the powersupply , this is what happened.
in the manual it states clearly to connect a powerlead between 4 (cortex) and the CB on any free or y-lead on a existing port.
what happened is that your rx port disabled them selfes.. and cb went into failsafe.
next time make sure you connect a jumper lead...
#1905
"you connected a extra lead between channel 4 from the cortex to a free port on the cb? , since you cant use anything else then a receiver on a CB rx port"
Nope. The CortexPro had the two receivers in ports A&B and ports 5&6 went to the CB200. This is the standard setup as instructed by BD.
"What software version was your Cortex Pro at and were both RX's connected to the CB200 via the Cortex?"
I updated all devices to the latest firmware as of January 2021.
Thanks for your thoughts.
Nope. The CortexPro had the two receivers in ports A&B and ports 5&6 went to the CB200. This is the standard setup as instructed by BD.
"What software version was your Cortex Pro at and were both RX's connected to the CB200 via the Cortex?"
I updated all devices to the latest firmware as of January 2021.
Thanks for your thoughts.
Note for Jeti connection: For Jeti integration and telemetry feedback from a suitable distribution box through the CORTEXpro (e.g. Jeti CentralBox, Emcotec DUPLEX-Edition, etc.), the EX-bus protocol must be used! The primary receiver must be connected to port B on the CORTEXpro, the secondary receiver to port A. Then connect output 6 to CB‘s Rx1 port, output 5 to Rx2. In addition, route a standard patch cable (signal line can stay) from any CB servo output port to port 4 on the CORTEXpro.
#1907
Senior Member
Like Sandor says. You have a LOT of equipment connecting on the Cortex/REX7. Without the power lead you will blow up the RX1 and RX2 of the CB. Why didn’t you use the E ports of the CB to connect all your equipment? (CRU, GPS, expander, Fadec)
Even with the Cortex only it is mandatory to connect the power lead.
#1908

My Feedback: (1)
Why did I even use a CB200, I could have just used a REX12?
It was sitting in the drawer, unused, I thought ***, why not??? Now I know to never use a CB200 again. Which I don't have to worry about because it was smashed to pieces.
Its off topic, but I have had nothing but bad luck the past 6-months. My 2nd flight with my Rebel Hot had a flame out, resulting in $800 worth of damage (I fixed it, but its has scars). I still don't know why the X45 quit. It has been tested and worked until I smashed it in to the ground yesterday. Now it don't go, maybe Keith can fix it.
I bounced a foam Avanti on landing and the wind flipped it on its back and broke it. Just unbelievable.
I test flew my new Joker and had a bad landing and broke the landing gear and cracked the fuselage. It is waiting on parts and I have no idea what to do with the cracks in the fiberglass.
I had another Sebart Avanit (EDF), which I absolutely loved and it unexpectedly dove in to the ground last summer resulting in complete destruction.
It seems each time I go to the field I loose money and spend months fixing airplanes. I'm thinking my models should be static display only!
At least the vendors are benefiting from my bad luck, I foolishly keep buying more stuff.
It was sitting in the drawer, unused, I thought ***, why not??? Now I know to never use a CB200 again. Which I don't have to worry about because it was smashed to pieces.
Its off topic, but I have had nothing but bad luck the past 6-months. My 2nd flight with my Rebel Hot had a flame out, resulting in $800 worth of damage (I fixed it, but its has scars). I still don't know why the X45 quit. It has been tested and worked until I smashed it in to the ground yesterday. Now it don't go, maybe Keith can fix it.
I bounced a foam Avanti on landing and the wind flipped it on its back and broke it. Just unbelievable.
I test flew my new Joker and had a bad landing and broke the landing gear and cracked the fuselage. It is waiting on parts and I have no idea what to do with the cracks in the fiberglass.
I had another Sebart Avanit (EDF), which I absolutely loved and it unexpectedly dove in to the ground last summer resulting in complete destruction.
It seems each time I go to the field I loose money and spend months fixing airplanes. I'm thinking my models should be static display only!
At least the vendors are benefiting from my bad luck, I foolishly keep buying more stuff.
Last edited by jvaliensi; 02-16-2021 at 07:46 AM.
#1910
Its off topic, but I have had nothing but bad luck the past 6-months. My 2nd flight with my Rebel Hot had a flame out, resulting in $800 worth of damage (I fixed it, but its has scars). I still don't know why the X45 quit. It has been tested and worked until I smashed it in to the ground yesterday. Now it don't go, maybe Keith can fix it.
I bounced a foam Avanti on landing and the wind flipped it on its back and broke it. Just unbelievable.
I test flew my new Joker and had a bad landing and broke the landing gear and cracked the fuselage. It is waiting on parts and I have no idea what to do with the cracks in the fiberglass.
I had another Sebart Avanit (EDF), which I absolutely loved and it unexpectedly dove in to the ground last summer resulting in complete destruction.
It seems each time I go to the field I loose money and spend months fixing airplanes. I'm thinking my models should be static display only!
At least the vendors are benefiting from my bad luck, I foolishly keep buying more stuff.
I bounced a foam Avanti on landing and the wind flipped it on its back and broke it. Just unbelievable.
I test flew my new Joker and had a bad landing and broke the landing gear and cracked the fuselage. It is waiting on parts and I have no idea what to do with the cracks in the fiberglass.
I had another Sebart Avanit (EDF), which I absolutely loved and it unexpectedly dove in to the ground last summer resulting in complete destruction.
It seems each time I go to the field I loose money and spend months fixing airplanes. I'm thinking my models should be static display only!
At least the vendors are benefiting from my bad luck, I foolishly keep buying more stuff.
jvaliensi, I don't think that your countless issues are related to your luck !
No offense intended ... you have to find some knowledgeable friends with whom you can share and enjoy the technical part of the hobby.
We all overlook issues when we are convinced we did them right ... but it is amazing how a friend can instantly pick up a reversed gyro or control surface . In fact, I would say everybody with Jeti knowledge would have advised you about the mistake you made with the connection.
Now on the humor side: I think you are an extremely lucky guy .... you still have all your body parts together after all the things you described
.Jack
#1911

My Feedback: (1)
I am very fortunate to have LA Jet Guy (David) at the field where we fly. I'm sure he has forgotten more about Jeti that I know. It is amazing to me how David will take time to help Jeti users.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
#1912

My Feedback: (2)
Not trying to be argumentative, and I fully agree that overloading the CB200 RX ports is the most probable cause of the crash based on the system diagram provided, but when the original Cortex Pro secondary power lead requirement from a Jeti CB came up a few years ago, I recall putting an ammeter in the line to see what the current draw really was.
I had a R3/RSW RX connected to the Cortex Pro and then connected to one of the CB200 Rx ports. I don't recall the exact current draw measured, but it was well below the stated limit for the single CB200 RX port (150mA). Going from memory, I would say that less than 80mA would be a reasonable recollection.
I can see that if you then cascade additional devices off the back of the RX via the Cortex Pro, you could easily pull more than 150mA, but just hanging a single Rx should be no issue. In fact I ran my Ultra Flash just like this (1 R3 Rx via the CP + 1 R3 directly) without issue. By running both RX via the CP that would provide 300mA available to the CP + 2x RX which should be more than sufficient.
I get that Bavarian Daemon have to cover all situations and recommending/ mandating in the instructions to add a secondary power supply covers them for situations where additional devices are daisy-chained off the Rx's, but for a simple installation of RX only via the CP then I have not seen any data that underpins that requirement.
Does anyone have any measured data for the current draw of various Rx's and the Cortex Pro when just operating in a serial bus configuration? It should be a constant value as there are no variables such as servo loads to consider.
Paul
I had a R3/RSW RX connected to the Cortex Pro and then connected to one of the CB200 Rx ports. I don't recall the exact current draw measured, but it was well below the stated limit for the single CB200 RX port (150mA). Going from memory, I would say that less than 80mA would be a reasonable recollection.
I can see that if you then cascade additional devices off the back of the RX via the Cortex Pro, you could easily pull more than 150mA, but just hanging a single Rx should be no issue. In fact I ran my Ultra Flash just like this (1 R3 Rx via the CP + 1 R3 directly) without issue. By running both RX via the CP that would provide 300mA available to the CP + 2x RX which should be more than sufficient.
I get that Bavarian Daemon have to cover all situations and recommending/ mandating in the instructions to add a secondary power supply covers them for situations where additional devices are daisy-chained off the Rx's, but for a simple installation of RX only via the CP then I have not seen any data that underpins that requirement.
Does anyone have any measured data for the current draw of various Rx's and the Cortex Pro when just operating in a serial bus configuration? It should be a constant value as there are no variables such as servo loads to consider.
Paul
#1913
I am very fortunate to have LA Jet Guy (David) at the field where we fly. I'm sure he has forgotten more about Jeti that I know. It is amazing to me how David will take time to help Jeti users.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
as long you use the CRU as a retract controller its fine , as soon you hook servo,s to it , it takes that power from the RX lead in your case the low power line.
next time please ask on any jeti groupo , you are a facebook user also , tons of information and friendly guys that can help.
dont be shy to ask anything , there are no stupid questions in this hobby..
i hope you dont give up on this wonderfull hobby..
send your CRU in to me or to our dealer i will get it fixed for you for free if you pay for the shipping..
#1914
I am very fortunate to have LA Jet Guy (David) at the field where we fly. I'm sure he has forgotten more about Jeti that I know. It is amazing to me how David will take time to help Jeti users.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
Not trying to be argumentative, and I fully agree that overloading the CB200 RX ports is the most probable cause of the crash based on the system diagram provided, but when the original Cortex Pro secondary power lead requirement from a Jeti CB came up a few years ago, I recall putting an ammeter in the line to see what the current draw really was.
I had a R3/RSW RX connected to the Cortex Pro and then connected to one of the CB200 Rx ports. I don't recall the exact current draw measured, but it was well below the stated limit for the single CB200 RX port (150mA). Going from memory, I would say that less than 80mA would be a reasonable recollection.
I can see that if you then cascade additional devices off the back of the RX via the Cortex Pro, you could easily pull more than 150mA, but just hanging a single Rx should be no issue. In fact I ran my Ultra Flash just like this (1 R3 Rx via the CP + 1 R3 directly) without issue. By running both RX via the CP that would provide 300mA available to the CP + 2x RX which should be more than sufficient.
I get that Bavarian Daemon have to cover all situations and recommending/ mandating in the instructions to add a secondary power supply covers them for situations where additional devices are daisy-chained off the Rx's, but for a simple installation of RX only via the CP then I have not seen any data that underpins that requirement.
Does anyone have any measured data for the current draw of various Rx's and the Cortex Pro when just operating in a serial bus configuration? It should be a constant value as there are no variables such as servo loads to consider.
Paul
I had a R3/RSW RX connected to the Cortex Pro and then connected to one of the CB200 Rx ports. I don't recall the exact current draw measured, but it was well below the stated limit for the single CB200 RX port (150mA). Going from memory, I would say that less than 80mA would be a reasonable recollection.
I can see that if you then cascade additional devices off the back of the RX via the Cortex Pro, you could easily pull more than 150mA, but just hanging a single Rx should be no issue. In fact I ran my Ultra Flash just like this (1 R3 Rx via the CP + 1 R3 directly) without issue. By running both RX via the CP that would provide 300mA available to the CP + 2x RX which should be more than sufficient.
I get that Bavarian Daemon have to cover all situations and recommending/ mandating in the instructions to add a secondary power supply covers them for situations where additional devices are daisy-chained off the Rx's, but for a simple installation of RX only via the CP then I have not seen any data that underpins that requirement.
Does anyone have any measured data for the current draw of various Rx's and the Cortex Pro when just operating in a serial bus configuration? It should be a constant value as there are no variables such as servo loads to consider.
Paul
but jeti also mentions to put no power users to these channels...
The following users liked this post:
Skunkwrks (02-17-2021)
#1916
all servo,s can be programmed by the CRU to have a max currecnt but all is dependand on the power output.
its in the manual.
#1917

My Feedback: (1)
So, when I added the CRU to my REX7 E2, that is what overloaded the RX outputs of the CB200. Makes sense, because all prior flights didn't have the CRU. Funny that I put a 3rd battery in the plane to power the gear and still ended up overloading it.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
#1918
I am very fortunate to have LA Jet Guy (David) at the field where we fly. I'm sure he has forgotten more about Jeti that I know. It is amazing to me how David will take time to help Jeti users.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
I guess I should have ask him to look at the little Avanti, but I had success with it in the past, so I didn't expect any trouble. I think adding the CRU to the airplane was the proverbially straw that broke the camel's back.
Your Rebel should be ready... whenever you are ready let’s get you flying again and have you enjoy the hobby.
contact me next time you want to go out to field and I will be there..
David
#1919
So, when I added the CRU to my REX7 E2, that is what overloaded the RX outputs of the CB200. Makes sense, because all prior flights didn't have the CRU. Funny that I put a 3rd battery in the plane to power the gear and still ended up overloading it.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
this is from the jeti CB200 manual :
Caution: Rx1, Rx2, Ext1, and OUT/IN are not protected against overload.
Maximum output current is 300mA for output.
Overloading causes irreversible damage of the Central Box.
in the quick manual from the bavarian demon i found this :
CONNECTION SERIAL-IN / SERIAL-OUT Connect receiver to port A, or, in case of 2 receivers, to A+B.
Serial output available on ports 5+6 parallel.
Using Jeti, it‘s important to stick to the connection advice in the main manual!
as per your statements :
"just got a response form my Digitech dealer, and they will not help me get it fixed."
i believe i just old you i will fix it for free , as long you pay for the shipping.
so i dont know who you got it from? feel free to contact me on [email protected].
as for the servo outputs as you said your old school and read manuals.
it was clearly written everywhere what goes and what goes not .
simply put , you connected to much stuff on a receiver while you have 3 protected dedicated ports that are for those..
best Regards
Sandor
#1921

My Feedback: (2)
jvaliensi,
If you had connected the CRU to a CB200 servo port, not the Rex7, all would have been fine.
You had everything daisy-chained from the Rex 7, and with only 300mA available from the 2 C200 Rx ports, the door servos pushed you over the edge and they both blew, shutting both Rx's down.
I'm assuming that the previous setup with the JP controller, that it was connected directly to a CB servo port, or maybe the JP controller uses direct battery power for the servos.
Paul
If you had connected the CRU to a CB200 servo port, not the Rex7, all would have been fine.
You had everything daisy-chained from the Rex 7, and with only 300mA available from the 2 C200 Rx ports, the door servos pushed you over the edge and they both blew, shutting both Rx's down.
I'm assuming that the previous setup with the JP controller, that it was connected directly to a CB servo port, or maybe the JP controller uses direct battery power for the servos.
Paul
#1923
Senior Member
#1924
So, when I added the CRU to my REX7 E2, that is what overloaded the RX outputs of the CB200. Makes sense, because all prior flights didn't have the CRU. Funny that I put a 3rd battery in the plane to power the gear and still ended up overloading it.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
If Cortex would have included a wiring diagram in their quick start guide... I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings. It is a sign I'm old and being phased out.
I only wanted the CRU to end the pesky buzzing of a gear door servo. The JP controller worked great otherwise, and had another power source.
I just got a response form my Digitech dealer, and they will not help me get it fixed. I tested it yesterday and it works okay, and I wanted a new cover, because in the crash it got scratched and dented.
so it goes.
It makes me a little sad to read what you have written above to be honest!
You say:
Funny that I put a 3rd battery in the plane to power the gear and still ended up overloading it
That's actually not funny in my opinion, but rather sad. This means that YOU did NOT read the manual before connecting the CRU. If you did, you would have seen the following text on page 6 (section 2.1):
2.1 . Battery
Anything works between 6 volts and 14 volts.
NOTE! Ask your manufacturer the voltage for the landing gears.!
The CRU will pass ALL voltage thru to the Landing gear.
EXEPT for the Doors these are driven directly by the Receiver Voltage!
And then you say:
I guess the new generation relies on Youtube for instructions, I'm old school and like to read manuals and drawings
Well, the manual for the CRU is right here to fetch from Digitech's page for the CRU: https://www.digitech-aerosports.nl/p...uplex-2-4-jeti
(here is a direct link to the manual: https://www.digitech-aerosports.nl/_downloads/51332824
So, you clearly do NOT have to rely on "youtube" for instructions, just read the manuals as you are used to?
And lastly:
I just got a response form my Digitech dealer, and they will not help me get it fixed.
That's NOT true. You were offered a fix of the housing and a check of the electronics as long as you paid the shipping yourself. Remember, you had a crash that was YOUR fault, so Digitech is being nice and offering to help you for free, that's not a bad deal, is it ?
And please note, I'm the developer of the hardware and software for the CRU (among other things that Digitech sells, so I know kind of what I'm talking about

The following 2 users liked this post by Carsten Groen:
David J Ruskin (05-02-2021),
Didier (02-17-2021)
#1925

My Feedback: (2)
jvaliensi,
I feel your pain. I'm done with the CB400 also.
My Buccaneer scratch-build first flight loss has pointed a finger towards the CB400 as being partially responsible. Just like the CB200 and CB220, the CB400 has poly-fuses on each servo output and a number of people have contacted me about a history of crashes being attributed to the poly-fuse tripping and shutting down a critical servo. While the CB400 is rated for 30A continuous, each poly-fuse is only rated for 4-5A. The suspicion on the Buccaneer is that the elevator servo current draw caused the poly-fuse to blow.
Just Google 'CB400 poly fuse crash' and see what you find, especially on Flying Giants.
For my next build of the Buccaneer, I plan on using 2 CB210 boxes that don't use the poly-fuses. Distributing the 2 CB210's will also save on wiring.
Paul
I feel your pain. I'm done with the CB400 also.
My Buccaneer scratch-build first flight loss has pointed a finger towards the CB400 as being partially responsible. Just like the CB200 and CB220, the CB400 has poly-fuses on each servo output and a number of people have contacted me about a history of crashes being attributed to the poly-fuse tripping and shutting down a critical servo. While the CB400 is rated for 30A continuous, each poly-fuse is only rated for 4-5A. The suspicion on the Buccaneer is that the elevator servo current draw caused the poly-fuse to blow.
Just Google 'CB400 poly fuse crash' and see what you find, especially on Flying Giants.
For my next build of the Buccaneer, I plan on using 2 CB210 boxes that don't use the poly-fuses. Distributing the 2 CB210's will also save on wiring.
Paul



