Hi,
currently iNav ESC telemetry/output only supports AM32/BL32 ESC telemetry as source for battery voltage, current draw, ESC temperature and a few more.
I am using YGE escs and like to get telemetry data into iNav, none of the protocols selectable in YGE software is compatible with iNav (OpenYGE, YGE, Mikado, HoTTv4, JetiExBus, MSBv2, JR PROPO, Spektrum X-Bus, FrSky S.Port, Futaba, PowerBoxSystems). I would recommend HoTTv4, since this is already wide spread, but there is no personal preference as long as it can transport all data available. I see 2 options to activate this, either it can be detected silently in an automatic way or user has to define it like telemetry_protocol = auto, bl32, hott.
I already took a look into esc_telemetry source code, the biggest change will be adding polling the data and of cause the parsing. Maybe worth to take a look into the code from ExpressLRS. In 4.0.1 you can choose HoTTv4 as serial input, what I've successfully tested with AM32 ESC.
https://github.com/ExpressLRS/ExpressLRS/blob/master/src/src/rx-serial/SerialHoTT_TLM.cpp
Honestly, not a lot of iNav pilots using YGE escs, they are more used in LoS flying and 3D helicopters, but since Rotorflight is getting more and more into those scenes, iNav compatible flight controller will do it as well. These ESCs are quiet expensive, but have high quality data and it would be shame to not be able to process them in iNav. AM32 supports this as telemetry output and ELRS can handle it too.
YGE manufacturer:
https://www.yge.de/
I am open for testing and reviewing code, but don't see myself solving this by my own.
Thanks, Ingo
Hi,
currently iNav ESC telemetry/output only supports AM32/BL32 ESC telemetry as source for battery voltage, current draw, ESC temperature and a few more.
I am using YGE escs and like to get telemetry data into iNav, none of the protocols selectable in YGE software is compatible with iNav (OpenYGE, YGE, Mikado, HoTTv4, JetiExBus, MSBv2, JR PROPO, Spektrum X-Bus, FrSky S.Port, Futaba, PowerBoxSystems). I would recommend HoTTv4, since this is already wide spread, but there is no personal preference as long as it can transport all data available. I see 2 options to activate this, either it can be detected silently in an automatic way or user has to define it like telemetry_protocol = auto, bl32, hott.
I already took a look into esc_telemetry source code, the biggest change will be adding polling the data and of cause the parsing. Maybe worth to take a look into the code from ExpressLRS. In 4.0.1 you can choose HoTTv4 as serial input, what I've successfully tested with AM32 ESC.
https://github.com/ExpressLRS/ExpressLRS/blob/master/src/src/rx-serial/SerialHoTT_TLM.cpp
Honestly, not a lot of iNav pilots using YGE escs, they are more used in LoS flying and 3D helicopters, but since Rotorflight is getting more and more into those scenes, iNav compatible flight controller will do it as well. These ESCs are quiet expensive, but have high quality data and it would be shame to not be able to process them in iNav. AM32 supports this as telemetry output and ELRS can handle it too.
YGE manufacturer:
https://www.yge.de/
I am open for testing and reviewing code, but don't see myself solving this by my own.
Thanks, Ingo