Hi there,

Being a new owner of a Spirit pro, I ran into a strange behaviour which I was able to fix but which still makes me curious:

- Jeti Tx DC-16 with REX10 on Rx side.
- Spirit pro attached via EX-Bus using Spirit Jeti integration cable.
- Kontronik Jive Pro 120 HV attached via:

— Kontronik Master -> AUX 1 @ Spirit
— Kontronik Slave -> AUX 2 @ Spirit
— Kontronik Telemetry -> Primary DSM2/X satellite port @ Spirit

Wiring for 140° CCPM uses CH1 to CH4, throttle has been mapped to CH1.

Tx finds REX10 in device config which finds Spirit. Spirit config is accessible (using spirit.bin).

Tx has several flight phases, each with constant percentage (0, 60, 80, AuRo).

Now the strange behaviour: when I configure REX10 to use data windows of „auto“ size and fire up the motor, I can see in Tx device config that Spirit gets dropped (tick mark turns into „x“) after 15 seconds. When I want to turn the motor off again, the model does not react.

When I configure REX10 to use data windows of 10 ms size, the connection is stable and sustains any duration. Firing motor up and down works as expected.

I am using the latest firmware on all my hardware.

Having investigated the issue on the internet, I saw a similar issues a while ago (2015) which seems to have been caused by Jeti using variable data window sizes.

Is this issue known or, even better: is there an explanation for it which helps to avoid the it?

Thanks greatly!
Christian

Hello,

likely this is because Kontronik is sending improper data to the unit through Telemetry.
I always recommend to disconnect everything that is not necessary if there is some issue. Then you can find easier what is causing the trouble.

Normally Auto should work without any problem.

So please try to disconnect the Telemetry cable first and try it again with Auto settings.

_________________
Spirit System developer