OpenTX - Nightly builds for pre-2.0 testing

[seagovernor]

In companion, A1, A2, A3 and A4 have all same format, but in Taranis radio you will find the format for A4 is strange and also has - sign too.

[janlebelg]

i got a idea good or bad
is it more essay to program special functions separably of switch sounds
and the sound comes link a user preferences when you create a new model already setup
the user almost uses the same button for the same option
these preferences can be used by model setup
there are 28 switch positions
it could clarify the Special functions
i am maybe not the first to say it bud i never read it any were
regards
great job already donne

[seagovernor]

Which are your parameters on A4? If you don't want any alarm on A4, you just have to put 0.00V on all its range/alarm values

Somehow I got correct format (0.00v) for A4 vs -0000.00v previousely. (by refreshing the same firmware 1.99.6)
But it still says A4 critical, with all zero value input, o.oov.
I checked other model equipped with X6R receiver. It work fine, it does not say any warnig.
The model with X8R receiver has telemetries, normal precision variometer connected with sensor hub that has RPM sensor and temperature sensor. I am not sure these sensors cause problems.
Anyway is A4 same as A1 or A2 on D series receivers?

[iloveopenrc]

I just installed 1.99.6 on my X9D.
Now, the telemetry values Cnsp and Powr are not working anymore.
Did something change that i have to reconfigure to make it work again?
(I am using a X8R receiver with a high-precision vario and a FAS100 current sensor connected to the vario)

[bertrand35]

Did you check your settings in the Telemetry screen?

[iloveopenrc]

Ah, sorry!
Found the error.
Voltage and current source were set to A2 and A3 instead of FAS.

By the way... persistence of Cnsp is not working yet??

[bertrand35]

1.99.7 coming ...
Translations updated
Companion is now able to write the firmware in massstorage mode (as Mike explained above). Side note it continues to use the DFU mode as usual when the Taranis is OFF (no massstorage).
Better averaging on RSSI / RxBatt / A1 ... A4

[MikeB]

That should make flashing nice and quick. I've been using that mode for months, it's so easy!

Mike.

[bertrand35]

Ah, sorry!
Found the error.
Voltage and current source were set to A2 and A3 instead of FAS.

By the way... persistence of Cnsp is not working yet??

EEPROM needs to be modified, it will be for next release, please open an issue so that I don't forget it!

[seagovernor]

Did you check your settings in the Telemetry screen?

After updating firmware 1.99.7, the A4 critical warning is somehow solved, but not perfectly.
When pushing down + or - button of taranis radio on Range under A4 channel;
the number is changing back and forth like 0.00v to 0000.00v. Not only this value changes, but others change as follows:
A4 channel -0000.00v
Range 0000.00v
Offset -0000.00v
Low Alarm -51.40v
Critical Alarm -12.85v

Trying to change values Low and Critical Alarm, it changes --- 25.70v, 12.85v, 0.00 v, -12.85v, -25.70v, -38.55v, -51.40v, -64.25v so on, look like 12.85 multiples.

To change values Range value is highlighted on 0000.00v and pushing the + or - button.
All format of the value changed to normal:
A4 channel 0.00v
Range 0.00v
Offset 0.00v
Low Alarm 0.00v
Critical Alarm 0.00v

[janlebelg]

opentx-taranis-haptic-lua-ppmus-sqt5font-faichoice-fr-1.99.7

flashing ok bud dit only show the progression screen of flashing
but not the little screen when done were you have to say ok

dit not find a bug till now

[davx]

Hi,

OpenTX 1.99.7:
In the Input menu, when I set different rates according to flight modes, I can't see the numbers of the corresponding flight modes anymore.

[bertrand35]

Yes, there is not anymore the indication of the flight mode in this screen, too many things to display in little space!

[bertrand35]

Did you check your settings in the Telemetry screen?

After updating firmware 1.99.7, the A4 critical warning is somehow solved, but not perfectly.
When pushing down + or - button of taranis radio on Range under A4 channel;
the number is changing back and forth like 0.00v to 0000.00v. Not only this value changes, but others change as follows:
A4 channel -0000.00v
Range 0000.00v
Offset -0000.00v
Low Alarm -51.40v
Critical Alarm -12.85v

Trying to change values Low and Critical Alarm, it changes --- 25.70v, 12.85v, 0.00 v, -12.85v, -25.70v, -38.55v, -51.40v, -64.25v so on, look like 12.85 multiples.

To change values Range value is highlighted on 0000.00v and pushing the + or - button.
All format of the value changed to normal:
A4 channel 0.00v
Range 0.00v
Offset 0.00v
Low Alarm 0.00v
Critical Alarm 0.00v

Someone reproduces a bug on A4? I can't !!! Would you try on a fresh model?

[MicheleVilla]

Taranis
In Special Function [Enter Long press] Menu the option "Clear" and "Delete" have the same effect?
If yes one of the two is redundant

[Kilrah]

Just try it?

Clear only empties the line, delete empties the line and shifts below lines up (empty line is deleted).

[MicheleVilla]

Just try it?

Clear only empties the line, delete empties the line and shifts below lines up (empty line is deleted).

I have try but every times with last line...
Thank you

[bertrand35]

Yes, for the last line it's redundant, open an issue for 2.0x, I can fix it

[Kilrah]

Someone reproduces a bug on A4? I can't !!! Would you try on a fresh model?

No, everything works fine here.
Please give an EXACT step by step procedure to reproduce...

[seagovernor]

I've noticed a strange format of A4 after flashed with ver 1.99.5, I believe. then I heard the beeping sound. I did not realized what is going on.
I talked on this matter in the following thread; 'Taranis beeping constantly when connected to X8R'.
Then I added the missing sound A3 and A4 after updated to ver 1.99.6, when you released the sounds.
Then it says A4 critical warning repeatedly. So I tried to set value all to zero in A4, but I could not because A4 value was -0000.00, and Range, Waring, and Critical value could not be zero. I behaved strangely.
The only suspect cause is, I think, that I over-wrote the new firmware 1.99.6 over the old one 1.99.5 directly on SD card.
After updating to ver 1.99.7, it still had A4 critical warning. Somehow I fixed A4 warning sound, but it is still unstable.
When I have time, I will take movie and I will post or PM to you.
Regards

[seagovernor]

Now I can set all numbers as zero even in strange format.
I can not set Range value with any number except zero because it changes 0.00 to 0000.00 back and forth when pushing + and - button.
I had - values at A4 channel, Range, Low alarm and critical alarm, now I have positive value all the time. It changed somehow, I don't what happened.
I attached a movie and an eepe. This eepe shows number in Range in companion, but it was zero in the taranis radio.

[Kilrah]

I mean can you reproduce the problem starting from a new model.

This is the first thing to check when reporting a problem. There have been evolutions in the way the data is stored, so as mentioned in the first post if you use test versions during the development cycle your models will get corrupted once in a while.
If you can't reproduce it with a new model on the current firmware then there is likely no problem.

Also, please provide the raw .bin EEPROM file, the .eePe is not of much help as it's been altered by companion already.

[seagovernor]

Hi, Kilrah.
I hope the model is corrupted. No other model in the radio have problem.
I attached my eeprom. (Please, remove 'zip' and write 'bin')
Regards

[bertrand35]

Ah yes, I reproduce the problem wih your bin file.

[bertrand35]

I have a workaround: your range is incredibly big. Just edit the ratio and press the - key until it returns to a correct value. Your model got corrupted as Kilrah explained.

[seagovernor]

Yes, I worked on the model in companion. And then write back in the radio. The problem is solved.
As you mentioned, the model file was corrupted, I believe. I am sorry to bother you much.
Thanks a lot.

[Scott Page]

I'm getting questions (why me??) why Github says the release date for 2.0 is Today yet it's not released. Clarification please.

[Kilrah]

There are still some hours left in the day. Can't people just be patient?

[Scott Page]

There are still some hours left in the day. Can't people just be patient?

(not at FrSky Headquarters)
LOL. I really didn't think it would be today, but rather was a goal which may or may not be reached and just needed to be updated. Wow, today, really! dang - now I'm excited.

[Kilrah]

If final tests are OK, yes.

But in general the dates are only there because without them the milestone thing puts releases in the wrong order, nothing more. I.e. don't look at them.