Telemetry/Jeti/Hobbywing Platinum V5

[ODPA]

I am struggling to get my new GTR to see the telemetry from my Hobbywing Platinum V5. I have telemetry enabled and settings adjusted to match current heli in the Spirit software. I also have it connected as indicated in the Spirit instruction to the sat 1 port. I used the included cable from HW and made sure it was only two wires and no internally connect red wire. I have also tried connecting to the E1 port which is what I had to do to get my Kontronik ESC telemetry to show up on another GTR but with this heli nothing. I can see the ESD settings in my Jeti under the Spirit integration but when I scan for telemetry all I see is the Spirit telemetry and nothing shows up for the HW. Any suggestions on what I am missing?

[ZeXx86]

First make sure you can see ESC telemetry in the Spirit Settings. It has to be connected at the SAT1 port. Also you have to select HobbyWing v5 in the Telemetry settings (Spirit unit).
Also make sure ESC is set for correct protocol (default from HobbyWing). Otherwise it will not work if someone selected for example VBAR protocol.

If it will work in the PC software you should see it immediately also at the JETI.

[ODPA]

I will have to look again but I do not think it was showing up in software either. Shows enabled and set to HW plat V5 but nothing. Will have to work on settings I have an ota u it but did not see anything specific to that.

[ODPA]

Ok it looks like the spirit gtr unit getting the telemetry. The voltage and esc temp are showing. Capacity and rpm and others show zero but it is my understanding these won’t show a value until under load. But for some reason they will not populate to the transmitter. I have the telemetry wire connected to sat1. Any other suggestions as to why the values would not be populating to the transmitter?

[Habásek]

https://manual.spirit-system.com/index. ... ntegration

- 9 Telemetry data
In order to display Telemetry data you have to scan for new sensors first. Go to Menu - Timers/Sensors - Sensors/Logging Setup and then press AUTO button. Scanning will take a few seconds untill all Telemetry variables will show up.

[ODPA]

Thank you all for the help. I am not sure what fixed it to be honest but it is working. When I posted this I had scanned for new telemetry sensors in my Jeti several times and all it would return was the 9 spirit sensors. These nine did not seem to be working at first either. When I would spool up the Heli there was no reported rpm just zero. Other than volts everything else was zero. I checked on it later and scanned a couple more times with no change in the results. I also checked the esc firmware which was already up to date and did not appear to be the vbar one but went ahead and flashed it with the same up to date version. Scanned a couple more times for sensors and the same nine showed up. Unplugged everything and restarted my transmitter and spooled up the Heli while looking at each telemetry sensor. Now 7 out of nine are working. A couple things of note from my original post is that this is not my first GTR, I had already scanned for sensors in my Jeti, and my other GTR is hooked to a kontronik. What I found is that with my kontronik the sat1 port did not work at all for telemetry and I had to route the telemetry wire to the E1 port. Once connected this way the Jeti found the 9 Spirit sensors and an additional 9 or 10 kontronik sensors. The Spirit sensors mostly show nothing on that setup except vibes and altitude. I was expecting the same behavior with the HW so was looking for HW sensors to show in the list which never happened. Instead they are working with the 9 Spirit telemetry sensors. So maybe it was working the whole time and I just did not notice because I was expecting it to be like my other setup. This is my first go with HW so that part is new to me. So again thank you all for the help. Maybe this will help someone else down the road.

[ZeXx86]

Please make sure there is nothing connected at the E2 pin. This could cause random problems with telemetry/channel data not working properly. The top pin must be unused.