Ok - a small update here.

I upgraded to 2.8 firmware a couple of days ago and today was the first proper flight with that. Whilst the integration and Spirit based sensor info is OK, I'm not getting the HobbyWing info through anymore.

I had a crash that promptedd the change to 2.8 (I was waiting for parts) - so I'll check my wiring see if that got damaged

Edit - err quick update on HobbyWing integration - after a long detailed, forensic investigation it appears that the problem was simple - some idiot had plugged the integration cable back into the wrong socket n

Good catch!

I forgot to mention that my Spirit firmware is version 2.8 and all the Hobbywing sensors work.

Sent from my SM-G950F using Tapatalk

Here is what happens during my sensor lost issue.


https://youtu.be/Hvs_m4wkqBc

_________________
Find me on HeliFreak, username Xoexoe

The only obvious difference is that Dennis I are using the "small but perfectly formed" QX7, whereas you and Dan are using the Horus / Horus clone, perhaps it is something to do with the different LUA????

But just to confuse things Adrian seems to be using both Horus and QX7 - do you get the same problem with the QX7 Adrian?

I set up my new Spirit 2 FBL on my Oxy 4 Max. It also has the same issue using my same Horus. But what’s interesting is that after losing telemetry I went into my telemetry menu on OpenTX to see what was going on. Of course my Hobbywing info is not communicating, but I still have data from my FrSky LiPo cell checker! This FrSky sensor goes directly to the S.Port and doesn’t get filtered into the FBL unit like the Hobbywing telemetry does.

(My other heli above, the micro Spirit on Oxy 2, did not have a LiPo cell checker installed.)

Item 7 below is the LiPo sensor. Item 8 is a calculated value based on item 7.




Now I’m tempted to try that Arduino-Hobbywing-S.Port project that some on HeliFreak are using.

_________________
Find me on HeliFreak, username Xoexoe

Hello,

when you enter the Spirit integration menu Telemetry sensors are not updated to make the integration faster. But immediately after closing the menu it should work again.
This is normal and correct behavior.

In case telemetry sensors would update all the time, integration menu speed would be slower.

_________________
Spirit System developer

The telemetry doesn’t work even after closing integration. If it started working again after closing then I don’t think it’d bother me too much.

_________________
Find me on HeliFreak, username Xoexoe

have you tried resetting telemetry to see if it works.

Yes, I reset telemetry using the OpenTX menu, then tried rediscovering sensors. No reconnection.

_________________
Find me on HeliFreak, username Xoexoe

Hello,

it look like OpenTX developers decided to remove EXIT command from Lua support in Horus.
I dont know what was the reason but this is why sensors are not updated anymore even after exiting the scripts.

Very likely Status LED is still blinking after exiting - which should not happen.

Downgrading to older OpenTX should resolve the problem. We have to update Lua scripts in some way to make it work probably.

_________________
Spirit System developer