Spirit System

Hey there, I am actually experiencing the very same thing, however I am running the latest (3.7.1) firmware. I am sure I am doing something wrong setup-wise but am out of things to try.

I can confirm that I see valid data for RPM and battery voltage from the ESC when using the desktop app connected via USB, but am not seeing RPM when scanning for telemetry. I do see battery voltage and current however.

My setup:
Frsky x20s - Ethos 1.5.19
BetaFPV SuperG Nano Elrs transmitter (flashed with 3.5.3) firmware
Spirit Ethos integration script 3.7.1
HobbyWing Platinum v5
SpritGT flashed with 3.7.1
Radiomaster RP3-H

Thanks!

Hey Spirit-Friends,

I'm also experiencing the same issues with the RP3-H on Radiomaster TX-16s. Telemetry only works at relatively slow 100 Hz Packet Rate and Telem. Ratio 1:2. With all other Packet rates, most of the Sensors (e.g. GPS, Baro, Hdg, BattVol.) are lost.

The GT is running Firmware 3.7.2 in combination with Hobbywing Platinum 120A V4 and latest ELRS firmware.

I really hope ELRS/ CRSF-Support will be further enhanced with following updates. I really enjoy the GT on my Raw 580.

I tried the recommended 100hz. Got some data on the sensors, but not consistently. But got sensor lost warnings all the time. External telemetry drops without recovering. Link telemetry from the rp3h remains. Even RxBt from external cable to lipo drops. Now back to f500. No telemetry from the Spirit unit, but do get RxBt from external cable from rp3h to lipo. Sensor keeps dropping occasionally though. Could baud rate have anything to do with this problem?

frisos@gmx.co.uk wrote:I tried the recommended 100hz. Got some data on the sensors, but not consistently. But got sensor lost warnings all the time. External telemetry drops without recovering. Link telemetry from the rp3h remains. Even RxBt from external cable to lipo drops. Now back to f500. No telemetry from the Spirit unit, but do get RxBt from external cable from rp3h to lipo. Sensor keeps dropping occasionally though. Could baud rate have anything to do with this problem?

Spirit must have been aware of this problem for quite some time. Even with 3.7.2, there has been no improvement at all.

There was an improvement at 100Hz/Full, but there is little benefit to using ELRS/CRSF at this resolution.
If you look at it cynically, it may be that they are differentiating it from Spirit wave. Wave achieves the same low latency as ELRS.
I gave up.

(Addition)
This is purely a personal opinion. As a commercial company, vendor lock-in strategies are a necessary evil to some degree to sustain product development.
Spirit is definitely worth the money.

On the latest Spirit version with RP3-H it still doesn't initialize correctly half of the time. The receiver will connect and provide its own telemetry but Spirit shows no response. The manual has the odd recommendation to run 100hz packet rate but set the receiver Init Rate to F1000 (note init rate isn't a setting in the latest ELRS version, but you can manually force it to initialize at a certain rate by changing it while it's connected). Doing this makes it far more likely for it to initialize correctly, but it also takes forever because the receiver will have to search for the correct packet rate. It makes no sense to intentionally set them to be mismatched, something must be wrong with Spirit implementation that makes it fail unless there's a long delay. Also Spirit telemetry is extremely unreliable. It works correctly with all packet rates and telem ratios on OMP OFS3, Rotorflight, Ikon etc. Please look into this again. Considering just switching over everything to RF at this point.

Hello,

we have RP3-H with TX16S running EdgeTX working properly with all packet rates. We will test with more recent RX version to see how it will perform.
Even more interesting it works well with all original CRSF receivers. Sadly for us, ELRS is in development everyday which mean any new update could make it potentionally incompatible.
Even more sad is that there is no official documentation, only hints that we have to reverse engineer and/or read from other projects which is time consuming and for this reason not too interesting nor recommended in helicopter world where safety is must have. However it seems ELRS is well marketed these days so we will take more time at this.
It has nothing to do with our marketing.

ZeXx86 wrote:Hello,

we have RP3-H with TX16S running EdgeTX working properly with all packet rates. We will test with more recent RX version to see how it will perform.
Even more interesting it works well with all original CRSF receivers. Sadly for us, ELRS is in development everyday which mean any new update could make it potentionally incompatible.
Even more sad is that there is no official documentation, only hints that we have to reverse engineer and/or read from other projects which is time consuming and for this reason not too interesting nor recommended in helicopter world where safety is must have. However it seems ELRS is well marketed these days so we will take more time at this.
It has nothing to do with our marketing.

Checked today, RPM still missing in telemetry values in TX16s but in Spirit Settings RPM is present, also governor is working.

Anyone have telemetry working yet with the RP3-H rx and RMTX16S tx? Everything I have tried has not worked. I did have it intermittently or randomly working with a Spirit II and that has been it. Sad that MSH can get it working but Spirit is a no go. I`m trying to decide what to do with five helis right now that have Spirit II or GT on them.

Right now we are spending time to make it work with the latest ELRS firmwares again. We can replicate the issue with RP3-H. With original CrossFire it works well.

Problem was resolved. Also there will be full CRSF/ELRS integration coming in the 3.7.4 update available possibly in the following week,