Spirit System

The following problem after update.
As you know, on the DS-24 under Device Overview, the menu of the Spirit is located under the receiver, in my case Rex3.
If I select e.g. the point "Stablilisierungsreiter" the menu opens, closes itself however after approx. 3 seconds again and I find myself again in the device overview.
For a short time "Kein Gerät angeschlossen- No Device connected" appears. Then behind Spirit a "X" appears for a moment, then it changes to a "ok".
This happens with most submenus, not with all, e.g. "General".
Latest updates on the radio 5.06, receiver 1.15 and Spirit 3.4.1 including current Spirit.Bin file.
On the PC everything can be set, heli flies well. But the menu on the DS-24 is just not good. I would like to make settings on the field. That's just the point with this FBL. With previous version everything worked.
Is the problem known? Is there a solution? With the request for help.
Thanks
Greetings
Martin

Translated with http://www.DeepL.com/Translator (free version)

Hello,

we are sorry for the troubles. You can try to flash 3.4.0 and verify if problem will persist.
Unfortunately from your message I dont know what exactly was updated and what was previous version.
Since we have national holidays I can help more after 2 days.

Hi ZeXx86,
thank you for your quick answer.
I had 3.4.0 before, unfortunately it was the same result,
the menu vanished after a few seconds.
In fact I am not sure which version worked.
I think 3.2.2.
First I updated the DS24.
Then I started spirit settings on the pc, here it reads it has to be updated.
Please ask, if you have further questionon on this issue.
But first, have happy holidays, maybe you can help me later.
Kind regards,
Martin

Thank you for the details.

You can try resetting JETI telemetry sensors. There was difference in the Spirit sensor list in older version. So more recent versions could fail.
If you are using more EXBUS sensors, could you try to disconnect them temporarily?

More recent Spirit firmwares are using more bandwidth from EXBUS, if some other sensor does not work perfectly it could have data losses.
For example some Kontronik ESC telemetris were causing troubles with their older firmware.

I have a MUI 75 on this heli.
Now I took it off.
Resettet the sensors with "Auto" Button.
Only S Vibes and S RPM remain from the spirit.
No improvement, still the same problem.

General, Diagnosys, Limits and Setup Assitence work,
Servos, Sensors, Stabiliser, Advanced do not work.

When I power on the heli.
The red light of spirit lights up.
When I open the spirit menu on the DC24
the light of the spirit is flashing and
is still flashing when I quit the menu.

After power off and on again,
it lights up again.

Hi Thomas, hi Martin,

i have the same issue with a Spirit GTR!
System:
DS 24 with 5.06
Spirit GTR with 3.41 => sw-version doesn't matter, problem since 3.31
Kolibri 140 HV sw 3.00
Jeti MTAG

I have exactly the same issue as Martin. I tried different sw-versions (3.3.1/ 3.4.0 /3.4.1) the issue remains.
I disconnected all sensors, reset the device to factory settings, .... nothing

BUT: i have testet 2 other Helis with a Spirit RS/ Kolibri or Kosmik and MTAG => this works perfectly! All latest software on the units (3.4.1).
I testet a µSpirit (3.2.2) and a Spirit Pro (3.2.2 and 3.4.1) => fine!

The issue looks like a reset of the device with a following reconnect. Is there a possibility that the device is damaged?

No, nothing is really damaged

It is enough to click at the Close menu in the Integration.

It only mean that the unit is still in the configuration mode, because configuration was not closed.

Anytime you will open software or integration the unit will start to blink with the LED light which is perfectly correct.
But it looks like you are talking about some other problem. Please explain it in a greater detail.

If you are using a telemetry sensor, never plug it at the E2 pin.

Hi,

first E2 is never connected!
The problem is: i can't setup the Spirit with the Transmitter. If i open the configuration menu it will closed after ~2s and a message pops up: "System will be reconnected!".
It is the same like Martins issue.

This behavior stays, if i disconnect all sensors.

The only issue could be some old version of the BIN file.
If BIN file is old it might not work properly.

I am afraid but Martin had probably very different problem.