Hi All,

I'm setting up my second Spirit RS on a TDR and ran into a glitch with the Spirit setup wizard on the radio.

Has anyone had a "Disconnected" error while using the Jeti setup wizard for the Spirit RS FBL - with a TelMe Jeti connected on E1?

I'm using the setup wizard on a Jeti DS-12 "Spirit Editon" TX.

This is what happens

The wizard will suddenly crash (app closes) and dumps me back to the Devices screen. While navigating the setup wizard menu. The Wizard app crashes a few seconds into the process.

My hardware

Knotronic Jive Pro 120A HV
Kontronic TelMe Jeti connected at E1 on the RS FBL
Jeti DS-12 "Spirit Editon" TX

When I disconnect the TelMe, the app works perfectly.

I don't recall the firmware versions in play, but all firmware is up to date as of 8-7-2020.

Connecting the FBL to a PC (while TelMe is connected) works fine, no issues.

RX is good

When the wizard app crashes, the RX is still active - no signal loss, no loss of control to the servos.

The TelMe works perfectly

When not in the Setup Wizard App, the TelMe is sending telemetry back to the radio - functioning normally.

No problems setting up the first RS unit

I used the same TX to setup my first RS unit, the TX wizard worked perfectly.

The other heli [with the first RS FBL] has a Kontronic Kolibri 140 HV w/integrated telemetry (NO TelMe).

Thank you!

_________________
------------
Kevin
Helicopters: If you have too many, you're sure to have enough!

Hello,

can you tell me in which step of the setup wizard the problem occur?

Is ESC Telemetry option in the unit set to Disabled?

Anyway the cable is not needed during FBL setup but these two things shouldnt be related at all.

_________________
Spirit System developer

Thank you for your reply.

The app crashes almost immediately, in the first couple of screens - after selecting the FBL orientation for example.

I know for certain I didn't turn on telemetry in the RS FBL. If the default is "off", I believe the telemetry in the RS FBL is OFF - but will verify this evening and post back.

When you say "the cable isn't needed" are you referring to the TelMe cable? If so, agreed, not needed during setup, but interesting that the app crashes when the TelMe is connected.

An observation
Configuring a [different] Spirit RS with the same Jeti "Spirit Edition" radio on a heli with a Kolibri ESC, all worked perfectly - Kolibri telemetry cable [front port] connected to the E1 port on the RS unit.

_________________
------------
Kevin
Helicopters: If you have too many, you're sure to have enough!

Can you try to connect Kolibri ESC to the Spirit RS that has such issue with other Kontronik?

Unfortunately I dont know where can be the problem located at the moment. But with this test it can be more clear.

_________________
Spirit System developer

I'll try - I think I can position the two helis close and connect the Kolibri to the RS unit in question. I'll try this evening and report back.

Thank you.

_________________
------------
Kevin
Helicopters: If you have too many, you're sure to have enough!

That would be great. Make sure to disconnect all cables from other ESC.

_________________
Spirit System developer

Will do.

_________________
------------
Kevin
Helicopters: If you have too many, you're sure to have enough!

I confirmed the ESC Telemetry is disabled in the RS.

Connecting the Kolibri ESC to the suspect RS did not reproduce the Wizard app crash.

Swap Jive Pros
I had another Jive Pro 120 HV so I tried it with the suspect RS unit. No issues! The Wizard app worked from start to finish.

So what was the issue?
I connected the spare Jive Pro to the computer and verified the firmware is 1.14 (the latest). I then connected the original Jive Pro (causing the app to crash) to the computer - the firmware was 1.10! I updated the firmware to 1.14 and now the problem is gone, the Wizard works perfectly.

I thought I had updated the ESC previously, but I had not.

I stepped through the wizard a few times and no issues. I will complete my setup tomorrow using the TX wizard. Should the problem reappear, I'll report back. For now, the issue I posted seems to be solved!

Thank you!

_________________
------------
Kevin
Helicopters: If you have too many, you're sure to have enough!

Very interesting...so something changed in the way telemetry is sent I would guess.
Still would be good to investigate why the “errant” telemetry was not gracefully handled.

It look like ESC was sending invalid telemetry data in some sense. This caused interference on the EX BUS which disturned also Spirit unit.
So that connection was unstable and when connection is unstable it will close opened device in Device Explorer.

_________________
Spirit System developer