Bavarian Demon Cortex PRO is here!!
#680
Join Date: Dec 2013
Location: Gilching
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Ok, so here is what the unit should do / usually behaves like:
A new system, powered for the first time, never taught anything, will blink double red. This means " I am dumb, please tell me what to do".
If you now plug the jumper into the prog port, it will start the blue blink sequence. No matter if there is anything connected (servos, receiver, etc.), or if it's a blank unit simply powered via USB cable e.g. from a computer, or powered by a battery/BEC.
It will of course not finish this sequence in a correct way when not hooked up perfectly, but it will blink blue.
If the system is not new, but already used and taught a previous setup, and the receiver now used is of a different type/brand, then it will also blink red at start-up, but only a one blink sequence.
Still, if you plug the jumper, the above needs to happen.
Possible reasons for not doing so:
- Jumper is defect, no connection between the pins. Note that it's the outer pins that need to bridge the port (signal to ground). I have seen people modify the jumper to a different state, for what reason ever, which will not work.
- Prog port pins ok, especially the outer ones?
- Unit has a technical defect. Unlikely, but never impossible.
TEST: connect only the unit, nothing else connected, to the computer using the USB cable. When powered, plug the jumper. LED needs to start blinking blue. If it does not, one of the above applies for sure.
This is all I can tell from here. Hope it helps.
A new system, powered for the first time, never taught anything, will blink double red. This means " I am dumb, please tell me what to do".
If you now plug the jumper into the prog port, it will start the blue blink sequence. No matter if there is anything connected (servos, receiver, etc.), or if it's a blank unit simply powered via USB cable e.g. from a computer, or powered by a battery/BEC.
It will of course not finish this sequence in a correct way when not hooked up perfectly, but it will blink blue.
If the system is not new, but already used and taught a previous setup, and the receiver now used is of a different type/brand, then it will also blink red at start-up, but only a one blink sequence.
Still, if you plug the jumper, the above needs to happen.
Possible reasons for not doing so:
- Jumper is defect, no connection between the pins. Note that it's the outer pins that need to bridge the port (signal to ground). I have seen people modify the jumper to a different state, for what reason ever, which will not work.
- Prog port pins ok, especially the outer ones?
- Unit has a technical defect. Unlikely, but never impossible.
TEST: connect only the unit, nothing else connected, to the computer using the USB cable. When powered, plug the jumper. LED needs to start blinking blue. If it does not, one of the above applies for sure.
This is all I can tell from here. Hope it helps.
Last edited by DEMONjoe; 01-29-2019 at 03:17 AM.
#683
My Feedback: (58)
Possible reasons for not doing so:
- Jumper is defect, no connection between the pins. Note that it's the outer pins that need to bridge the port (signal to ground). I have seen people modify the jumper to a different state, for what reason ever, which will not work.
- Prog port pins ok, especially the outer ones?
- Unit has a technical defect. Unlikely, but never impossible.
TEST: connect only the unit, nothing else connected, to the computer using the USB cable. When powered, plug the jumper. LED needs to start blinking blue. If it does not, one of the above applies for sure.
This is all I can tell from here. Hope it helps.[/QUOTE]
DEMONJoe thanks for the help,
1. The jumper functions as it should I even used it to bind a receiver. Also tried another jumper with same result.
2. Both outer prog port pins are in great shape.
3. 'TEST' resulted in same outcome: continuously flashing red light when powered by laptop & with jumper installed.
- Jumper is defect, no connection between the pins. Note that it's the outer pins that need to bridge the port (signal to ground). I have seen people modify the jumper to a different state, for what reason ever, which will not work.
- Prog port pins ok, especially the outer ones?
- Unit has a technical defect. Unlikely, but never impossible.
TEST: connect only the unit, nothing else connected, to the computer using the USB cable. When powered, plug the jumper. LED needs to start blinking blue. If it does not, one of the above applies for sure.
This is all I can tell from here. Hope it helps.[/QUOTE]
DEMONJoe thanks for the help,
1. The jumper functions as it should I even used it to bind a receiver. Also tried another jumper with same result.
2. Both outer prog port pins are in great shape.
3. 'TEST' resulted in same outcome: continuously flashing red light when powered by laptop & with jumper installed.
#684
Join Date: Dec 2013
Location: Gilching
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Ok, so next detail needed: what exactly does the red blink sequence do, I mean what's the sequence like: one blink, 2, 3, 4, 5, 6, 7, 8?
For example a 7 times blink sequence means that it lost it's alignment data, which can happen in rare cases.
For example a 7 times blink sequence means that it lost it's alignment data, which can happen in rare cases.
#686
My Feedback: (58)
DEMONJoe,
When I got home this evening, I decided to hook up the Cortex Pro 1 more time to my laptop.
Once connected there was a solid green light followed by the quickly flashing red light for a few seconds.
Then the LED began a red blinking sequence of 3 blinks (it continued this sequence without the jumper plugged in as well as with it plugged in).
LED never started to blink blue at any time.
Greg
When I got home this evening, I decided to hook up the Cortex Pro 1 more time to my laptop.
Once connected there was a solid green light followed by the quickly flashing red light for a few seconds.
Then the LED began a red blinking sequence of 3 blinks (it continued this sequence without the jumper plugged in as well as with it plugged in).
LED never started to blink blue at any time.
Greg
#688
My Feedback: (58)
F1 Rocket...I'm pretty sure the issue isn't a connection problem per DEMONJoe, but here is my setup for you.
The loom is correctly plugged into ports A-D on the Cortex Pro
Cable 1 (3-wire) is plugged into Aileron channel on receiver.
Cable 2 (3-wire) is plugged into Elevator channel on receiver.
Cable 3 (single orange wire) is plugged into Rudder channel on receiver.
AUX Cable (single grey wire) is plugged into Aux 2 channel on receiver for signal.
Aileron servo is plugged into #1 port on Cortex Pro.
Elevator servo is plugged into #2 port on Cortex Pro.
Rudder servo is plugged into #3 port on Cortex Pro.
The loom is correctly plugged into ports A-D on the Cortex Pro
Cable 1 (3-wire) is plugged into Aileron channel on receiver.
Cable 2 (3-wire) is plugged into Elevator channel on receiver.
Cable 3 (single orange wire) is plugged into Rudder channel on receiver.
AUX Cable (single grey wire) is plugged into Aux 2 channel on receiver for signal.
Aileron servo is plugged into #1 port on Cortex Pro.
Elevator servo is plugged into #2 port on Cortex Pro.
Rudder servo is plugged into #3 port on Cortex Pro.
#689
Join Date: Dec 2013
Location: Gilching
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
This gives us 2 infos at a time:
1) The unit is already programmed and not brand new. Otherwise it would always give you a 2 time blink first, even if moved. Try to use the computer, hook it up and reset it to factory state in the software.
2) When moved during initialization, you cannot set the unit to programming mode. So, alternative to factory default, try to keep it very still to make it not blink 3 times after initializing. If not possible, do factory reset.
#696
My Feedback: (4)
Cortex and Jeti
Have a question for the cortex pro experts. I know when using the cortex pro with a Central Box 200 and dual Jeti Rx's in serial in and serial out that you have to connect a third lead to the cortex from the CB for additional power. I am using a cortex pro with 2 Jeti RX's and a powerbox cockpit srs, do I need to supply the additional power to the cortex pro.
Patrick
Patrick
#697
Have a question for the cortex pro experts. I know when using the cortex pro with a Central Box 200 and dual Jeti Rx's in serial in and serial out that you have to connect a third lead to the cortex from the CB for additional power. I am using a cortex pro with 2 Jeti RX's and a powerbox cockpit srs, do I need to supply the additional power to the cortex pro.
Patrick
Patrick
Danny
#698
Join Date: Dec 2013
Location: Gilching
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Still, we always answer this question with a clear "NO", as no issues are known since ever at all. Same applies for all other brands.
Jeti is the only ones we know about this limited power on the RX ports. No problem thought, using the additional cable here.
Last edited by DEMONjoe; 01-31-2019 at 02:12 AM.
#699
My Feedback: (58)
Demon Joe our success was short lived.
Last night I hooked everything up, powered on the transmitter then powered up the aircraft and got the quickly flashing red light which continued to flash without ever changing.
I plugged in the jumper and the light continued to flash red but again flashed just a little brighter with the jumper installed.
I then unhooked everything and powered up the cortex with my laptop and got a sequence of 2 flashing red lights instead of three like last time.
Any thoughts...?
Last night I hooked everything up, powered on the transmitter then powered up the aircraft and got the quickly flashing red light which continued to flash without ever changing.
I plugged in the jumper and the light continued to flash red but again flashed just a little brighter with the jumper installed.
I then unhooked everything and powered up the cortex with my laptop and got a sequence of 2 flashing red lights instead of three like last time.
Any thoughts...?
#700
Join Date: Dec 2013
Location: Gilching
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
This is weird.
Well, 2 blinks are not too bad, as this states that the unit basically is fine, but back in factory state. For what reason ever?! Hard to tell from here.
A 3 times blink would simply tell about the unit moving during initialization. Not too dramatic either.
Did you try to re-program it now?
Well, 2 blinks are not too bad, as this states that the unit basically is fine, but back in factory state. For what reason ever?! Hard to tell from here.
A 3 times blink would simply tell about the unit moving during initialization. Not too dramatic either.
Did you try to re-program it now?