OpenTX 2.1.1 Breaks Telemetry Data

[Hands0n]

I updated my Taranis today to the latest OpenTX 2.1.1 after being stuck in a proverbial time warp with it for over a year.  It felt the right thing to do.  But it did buy me a whole heap of trouble with my Telemetry screen and functions relating to monitoring the LiPo voltages.

Usually I will monitor the overall Cells voltage, that is the total voltage of the LiPo.  But I will also monitor the voltage of the lowest cell, with audio alerts set for 50% and then my low threshold of 3.7V which gives me around one minute to land before getting to 3.6V or below. 

Updating to OpenTX 2.1.1 killed my Logical Switches relating to this function and therefore the Special Functions no longer worked either! 

It took an age of searching around to find out what had been done.  Essentially, Cell no longer exists, you have to create the relevant Sensor yourself on the specific model';s Telemetry page.  I don';t know when this changed, it may have been earlier than 2.1.1.

The solution that I have found is as follows:

Add a new sensor.

To display the lowest cell voltage set it up like this
Type: Calculated
Formula: Cell
Cell Sensor: Cels
Cell Index: Lowest

To display the voltage difference between the highest and lowest cells set it up like this
Type: Calculated
Formula: Cell
Cell Sensor: Cels
Cell Index: Delta

Cell Index is the key here. You can also show individual cell voltages. Simply add a sensor for each cell of your battery, configure as above and select the cell number in the Cell Index.


Source: http://openrcforums.com/forum/viewtopic.php?f=45&t=7266#p99547

Ironically from a poster called "quadfather" - is that you Tim?

This advice really helped me a lot. So I hope its good for you also ...


Edit: There is a whole thread on OpenTX that discusses the new Telemetry paradigm. Very well worth a read and bookmarking for future reference.

See here "OpenTX 2.1 telemetry system preview"--> http://openrcforums.com/forum/viewtopic.php?f=45&t=6887&sid=899de7915b2b12474280edc11175e6c5

[quadfather]

T';was me, I';m afraid.

Autocorrupt provided by Tapatalk

[quadfather]

It was said that v2.1 will break everything telemetry related that you had set up in v2.0.  Although it could have been said a bit louder perhaps.  Lua scripts are also affected.

Although 2.1.1 has sorted the problems with model conversion, it will not migrate telemetry configurations and anything related to that, such as custom functions.

Doesn';t bother me, I only have five models.  But those that have many and/or sophisticated setups may want to reconsider the upgrade.  It';s worth it, IMO, but potentially a lot of work.

Autocorrupt provided by Tapatalk

[Hands0n]

It was said that v2.1 will break everything telemetry related that you had set up in v2.0.  Although it could have been said a bit louder perhaps.

Amen to that 

It had me going for quite a while. I reckon about an hour';s solid searching, YouTube';ing and then stumbled upon your post on the OpenTX forum.   I must say that the OpenTX documentation on 2.1.1 is sadly lacking.  Granted, this is OS and a lot of volunteer work. But stuff like this really has got to make it into the Wiki and Release Notes.  It could ruin the relationship otherwise!

I only have two models that use Telemetry right now. The problem, for me, is that my brain has not yet taken on board the new paradigm of creating your own sensors for "stuff" that you want to see on the Telemetry screen.

[Tim2100]

I had similar problem when 2.1 was released.  I had just got my telemetry sorted then did the upgrade to 2.1 and lost telemetry settings and scripts.  I got scared and restored 2.0.x   I will wait until I have the brain power before attempting the upgrade again unless I can find a tutorial to help me set up the telemetry screens.

[Hands0n]

Setting up the Telemetry screens is exactly as you did before. The trick in 2.1 is that you now have to define your own "Sensors" based on whatever is available to you.

So in my case, the FrSky voltage sensor gave me the aggregate battery voltage. I then created a Sensor to give me the voltage of the lowest cell. Also four more Sensors, one for each cell of the battery I use.

Now I';ve got my head around it I find it a very powerful tool. Completely customisable.

For such a major paradigm change the Developer team missed a big trick in getting this information out.

Sent from my HTC One_M8 using Tapatalk