Flysky AFHDS 2A, protocol as used i10, i6, iT4,

hmm ok so I should be able to get the external volt input pin from X6B or iA6C receiver? Basically giving RSSI, V Rx batt, V Ext batt?

I can't get it to work, only 2 values as shown, no ext bat for me on both rx tested.

goebish wrote: External voltage sensor is still not implemented, it's on my todo list ...

Good to know. I'll keep an eye on this post. Thanks

Using Devo 7e and testing with FS-IA4B in my Glider
Devo7e-v5.0.0-26d39af

Bind and Range - Great
Receiver Voltage and alarms - Great
RSSI shows up but is inverted -60db unable to set rssi alarms is there a workaround for -+ db Values

Thanks for Deviation and Multiple Protocols

Hi Goebish,

I loaded your firmware and have tested with IA6C of Hobbyking, I get the RX voltage, RSSI and LQI (I assume). But no luck yet I do not get the External Voltage Monitoring.
See this movie, they speak also about different firmware.


I also tested with Flysky X6B, I do get same telemetry, rx volt etc, but not yet the external volt monitoring input.

I am wondering is there any scale factor to be typed? With Frsky there is a scale factor in protocol option for external adc to get correct readout? (So maybe value received but stay displayed at 0V?)

I am using u7e - 256.

I checked the telemetry monitor page only.
The external V bat input is just hard wired input to the Rx, it is not something connected to an I-bus input.

It is not available on other receivers than ia6c and x6b.

Great Job Goebish!! This time it works for me!
At least for IA6C and for X6B, receiver we can now monitor the Lipo voltage.

Shown in the Telemetry monitor:
Row 1: 1st Box RSSI - 2nd Box RX Volt - 3rd Box Rx Ext Volt input.

Tried to test with my 7e but couldn't load new firm without protocol mismatch errors
is this right? tried using Deviation upload jar and drag and drop entire Zip contents
but protocol mismatch error on transmitter startup sorry if this is novice error

Thanks

It is for U7E-256, so it is a 7e where the CPU has been replaced.

After flash of the latest nightlies, I also needed to update my devo folder, then putting back my old hardware and tx ini, icons and models folders. (For some reason without doing that, it booted but menus seem corrupted or missing.) Normally only flashing dfu is enough.


@ Goebish while you are on it, is it possible to add a small finetune field, so we can put voltage spot on, something like multiplier 0.01V? So we can calibrate, using multimeter?

Oh btw resolutions seem different?
Box 2: Rx Volt 4.60V resolution 0.01V (The field name is TelemV1)
Box 3: External Vbat Volt, 11.5V resolution is only 0.1V. (The field name is C1)
Edit, Box3, voltage below 10V is also displayed with two digits.

Instead of using Cel Voltage C1: Can we not better use field AllCell or TelemV2 ?

Ok thanks for clarification.

But what about using the "AllCell" field instead, would sound more logic to me than C1, for this ext RX Vbat port..
It was a bit trial and error as in deviation I can't see which "telemetry box" has which "label", so have to select try them all one by one, click to to figure out which field carry what data.
Did not expect it was in C1.

I am going to have a short test flight.
Trying to set battery alert, but C1 really intended for cell voltage, as in alert setup it is restricted to max 5V. So can't use to setup alert for low pack voltage.