Telemetry question - Taranis & X8R

[RGN01]

Please could someone help me understand the telemetry screen in Companion9X? Or point me to a manual that can help with this query.

I'm using the Taranis and a X8R RX with a 4-cell NiMh battery. As I don't have any modules plugged into the X8R, I'm using A1 to measure the battery voltage. A fully charged pack reads 5.6V with a multimeter but 2.67V on the telemetry but the X8R apparently has a 1:4 voltage divider so that equates to 10.68V!

I'm probably doing someting wrong on the options for A1 - but what?

The Companion9X Telemetry screen for A1 gives the following options (how should I set these for this configuration?):

• Range
• Min Value
• Alarm 1 and Alarm 2 - each can have a < or > and a number

Thanks.

Richard

[MikeB]

Set the range to 13.2V (4 times 3.3).

Mike.

[RGN01]

Thanks for the reply, Mike. I tried that and it then reads 8.8V for a half-charged 4-cell pack.

This page clearly says it is a 1:4 divider http://www.frsky-rc.com/support/Details.php?fqa_id=110 but I've tried three RXs and they are all doing this. I wonder if it is a 4:1 divider?

I'll do more testing.

Oh, what does the Min. Voltage setting do, please?

Richard

[jhsa]

The maximum voltage the receiver A1 pin can read is 3.3V. So a 1:4 divider can read 4 times that value without the voltage at the receiver pin exceeding the 3.3V
That max voltage is what you set in the "Range" field

[RGN01]

Thanks, guys. I think what is confusing me is that the voltage read has quite a high error rate - up to about 0.5V over the range of 4V to 5.6V!

I have set the voltage 13.2V as suggested and am now 'playing' with the offset, trying to find the optimum setting.

Richard

[Kilrah]

Does your receiver have the latest firmware?
There was an issue with the integrated A1 voltage reading of the X8R that was fluctuating, it's been corrected a few weeks ago.

[RGN01]

Thanks, Kilrah. No, they are a few months old and I haven't updated them.

Is there an 'idiot's guide' to updating them you can point me to, please? I've found these two items that I need to order to update them:
http://www.t9hobbysport.com/frsky-smart ... pter-cable
http://www.t9hobbysport.com/fuc3-upgrad ... -receivers

Is there anything else I need?

Thanks again!

Richard

[Kilrah]

Nope, looks good!

[RGN01]

The upgrade worked just fine - now fine tuning the voltages etc.

Thanks.

Richard

[Delucs]

Taranis supports multiple same sensors as long as they do not have the same ID address, but how does the Taranis display it if there are for instance 2 FAS-40, and can it sum them? (maybe in the next firmware?)

Sent from my using Tapatalk

[Kilrah]

Multiple values of the same type are not supported, that would need a complete overhaul of the telemetry interface. I suppose the sensors would need different firmwares too.

[Delucs]

maybe I then misunderstood, because as you can change the ID, the receiver at least has no problems on the bus with it, no?

Sent from my using Tapatalk

[Kilrah]

You're right that it won't cause bus conflicts, but the radio won't know what to do with it (it will currently actually fill the same field alternatively with the data from both sensors).
The whole telemetry interface was written at the time of the hub telemetry, where there was a well-defined array of sensors and there could only be one of each. The new bus system is much more flexible and calls for an entire rewrite of that part to make full use of. Due to lack of time it was just "patched" to allow displaying values from the new system in the old interface.

[Delucs]

too bad that it will not fit into V2.0, this sensor hub is a strength of the system! btw can the new companion 1.99 be used with software 1.52? (I saw that you could set offsets now for the sensors but I do not want to fly with a beta )

Sent from my using Tapatalk

[Kilrah]

Of course not - setting an offset in companion won't do much if the firmware doesn't have code to make use of it!
Writing an eeprom with 1.99 in an r2940 radio will just give you an invalid eeprom message. The companion/firmware pair has to match, which is why we've merged them and will be giving them the same version numbers.

[Delucs]

unfortunately that's what I thought, so I should be patient till release...

Sent from my using Tapatalk