Flysky telemetry - the second temperature and maybe altitude? about deviation HOT 11 CLOSED

I think I can add the second temperature sensor telemetry.
Regarding the altitude sensor I'd need a dump because I've no idea of its ID / range, unit ...

from deviation.

I understand. I'll try to figure it out if I get one. There is also some magic needed to set/reset the 0 altitude offset on the transmitter side, so maybe we can live without it for some time :-)

You may close the issue on this.

from deviation.

Added telemetry for 2nd temperature sensor.

from deviation.

I think I just found what we're looking for in betaglight source code:
https://github.com/betaflight/betaflight/blob/master/src/main/telemetry/ibus_shared.h#L69
Seems altitude sensor ID is 0x83 and the value is signed centimeter ... please get back to me when you've one of those sensors, I'll make a test build.
You can use this topic on the forums, I'll be notified: https://www.deviationtx.com/forum/protocol-development/5251-flysky-afhds-2a-protocol-as-used-i10-i6-it4

from deviation.

Maybe take a look at the https://github.com/benb0jangles/FlySky-i6-Mod-/tree/master/10ch%20Mavlink%20Mod%20i6%20Updater

And thanks for the support. I'm still impressed with the Deviation potential. I'll be happy to help you and the community. I'm using Flysky hardware and recently the T8SG V2 transmitter with deviation software. It is even better then the original Flysky FS-i6X one that I have.

As the betaflight/INAV can put any data on FS telemetry - maybe it is even possible to have GPS or whatever telemetry data on Deviationtx with this software. The Mavlink mod is the example - but Flysky transmitters can't benefit much from that due to the lack of the alarms and no way to store the telemetry data.

from deviation.

Yup, same thing:
https://github.com/qba667/MAVLinkToIbus/blob/master/MAVLinkToIBUS/IBUSTelemetry.h#L71

from deviation.

Yeah, it is a great way to go. I'll be happy to have it on the transmitter with alarms, logging, and all the stuff the Deviationtx offers.

from deviation.

Just be aware that the TGY-CAT01 is a 32-bit sensor data which is not handled by the current code.

from deviation.

Yeah, I won't implement it unless someone can check if it works anyway.

from deviation.

Can you think about GPS and doing it to the INAV/ Betaflight telemetry code on Ibus, just as the Mavlink example mod? We also can have the altitude data from there, not only from the CAT01.

from deviation.

Ok, I won't be able to do that right now but it should be fine in October.
Also, I realize that using a 32 bit ibus sensor (flysky or betaflight) could break the current implementation (only if they're sent before 16 bit sensors, that probably doesn't happen as they've id with higher numbers).
Closing this issue for now but it's on my todo list.

from deviation.