I am running an FrSky RX via Fbus to my Spirit 2 running 3.7.0 and I take telemetry from my Hobbywing Platinum V5 and send it back to my TX running Ethos 1.5.18.
I just upgraded the Spirit 2 to 3.7.1 and no telemetry is sent. If I clear and rescan the telemetry on the TX, nothing (except for standard RX sensors) appear.
Upon downgrading back to 3.7.0 the Hobbywing ESC telemetry sensors are found
Any ideas on this issue?
Cheers
Mark
Upgrade to 3.7.1 telemetry lost
Hello,
I am running also 1.5.18 ETHOS and the firmware of Spirit is 3.7.1 but Spirit GT -
I have an YGE ESC and there is telemetry also working as before update...
Is your FrSky Integration cable ok? Have you another to change ?
Is your Telem UNI cable ok ? Try another to test it -
Can you try to change temporarily to FPort if that will work ?
Can you change to an other spirit unit if it will work there ?
If it didn't work there is maybe a bug in firmware ...
https://manual.spirit-system.com/index. ... _Telemetry
https://manual.spirit-system.com/index. ... FrSky_FBUS
https://manual.spirit-system.com/index. ... rSky_FPort
Regards
I am running also 1.5.18 ETHOS and the firmware of Spirit is 3.7.1 but Spirit GT -
I have an YGE ESC and there is telemetry also working as before update...
Is your FrSky Integration cable ok? Have you another to change ?
Is your Telem UNI cable ok ? Try another to test it -
Can you try to change temporarily to FPort if that will work ?
Can you change to an other spirit unit if it will work there ?
If it didn't work there is maybe a bug in firmware ...
https://manual.spirit-system.com/index. ... _Telemetry
https://manual.spirit-system.com/index. ... FrSky_FBUS
https://manual.spirit-system.com/index. ... rSky_FPort
Regards
-
mainstreet
- Posts: 11
- Joined: Mon 10. Jul 2023 16:40:41
I also run the Spirit GT on 3.7.1 with no problem, just seems to be the Spirit 2, hence downgrading back to 3.7.0 on Spirit 2 only
My advice:
Before I would downgrade to 3.7.0 I would test if FPort is working or not -
You can save your bank on disk that you have an fall back szenario after changeing the receivertype -
You can really fast test this with the other adjustment in Spirit Software, take there Fport there and test if this will work-
change your receiver to FPort protocoll - then start new with initialisising the FBL and look if there will be an similar behavior like FBus or not.
If this will also not work it seems to be an bug in the new firmware in my opinion-
Before I would downgrade to 3.7.0 I would test if FPort is working or not -
You can save your bank on disk that you have an fall back szenario after changeing the receivertype -
You can really fast test this with the other adjustment in Spirit Software, take there Fport there and test if this will work-
change your receiver to FPort protocoll - then start new with initialisising the FBL and look if there will be an similar behavior like FBus or not.
If this will also not work it seems to be an bug in the new firmware in my opinion-
-
mainstreet
- Posts: 11
- Joined: Mon 10. Jul 2023 16:40:41
I have tried with F.Port as well on 3.7.1 and the same issue occurs
Hello,
we are investigating the issue now. I will reply later today.
we are investigating the issue now. I will reply later today.
Spirit System developer
I have just setup a Spirit Pro (Firmware 3.7.1) via FBUS and the modified integration cable and 3 external FBUS sensors (FrSky FVLS ADV, FrSky FAS100 ADV, FrSky Vari ADV) and a FrSky TW mini receiver. All channels via Spirit Pro are working flawlessly and the telemetry data of the 3 externals sensors are dedected from the radio FrSky TANDEM X20 Pro AW BUT there are no telemetry data from the GeoLink 1 and the ESC Hobbywing Platinum V4 (is connected via Unicable). Additionally the LUA script on the radio also don't get any data from the Spirit Pro. Best regards, Erwin
Next attempt: Spirit Pro downgraded to version 3.6.2, otherwise left everything as described above. Result: everything works as it should, but I have a running message “sensor conflict” on the FrSky X20 Pro. This means that one of the sensors on the Spirit Pro (GeoLink 1 or Hobbywing Platinum V4) must be causing an ID conflict with the external sensors.
Kind regards, Erwin
Kind regards, Erwin