Devo8 current build testing

PB, there is any sense to test and comment current builds? I've installed the build environment and now I can test Devo8 builds. I see many issues with russian translating. Maybe there is problem with russian language file (or it's size)? Other languages working fine. Build 7ed47c841e06.

My latest russian language file (synchronized with lang.hu)

Yes, there is now an issue with the russian language file size. I will look into it.

Something is wrong with DSM2 protocol. If I change scale over 100% nothing to change with servo throw, servo doesn't move any farther. With DEVO protocol servo can move up to 150% throw. Seems that DSM2 protocol already has maximum 150% throw. With firmware 1.1.2 all are the same.

The channel data (10 bit) 0xaa..0x200..0x356 for 100% transmitter-travel
The channel data (11 bit) 0x154..0x400..0x6AC for 100% transmitter-travel

PhracturedBlue wrote: Yes, there is now an issue with the russian language file size. I will look into it.

Fixed

Something is wrong with DSM2 protocol. If I change scale over 100% nothing to change with servo throw, servo doesn't move any farther. With DEVO protocol servo can move up to 150% throw. Seems that DSM2 protocol already has maximum 150% throw. With firmware 1.1.2 all are the same.

fixed. This means users with DSM2 will need to recalibrate their models when they take this latest code though

Buld 4ab4a1258770

1. Now Russian interface looking fine. With except:
1) Tx 'Telemetry' page, russian Volt1,2,3 don't fit and go on boxes,
2) At 'Model' page 'Model Name:' and 'Icon' buttons cut off text with 2 trailing points - "Ladybird.." (Ladybird DSM2) and "Znac.." (Znachok). With firmware 1.1.2 text can take place up to edges of buttons.

2. Servo travel for DSM2 protocol now work properly, up to scale 150%.

3. DSM2 protocol, 8 and 9 channel mode (JR RD921)
1) 8 channel mode: 1 channel - work normally, 2 channel - work normally, 3 channel - work with delays (interrupted), 4 channel - work with delays (interrupted), 5 channel - don't working, 6 channel - work with very long delays, 7 channel - work with delays (interrupted), 8 channel - don't working.
1) 9 channel mode: 1 channel - work normally, 2 channel - work normally, 3 channel - work normally, 4 channel - work normally, 5 channel - vibrate, 6 channel - work normally, 7 channel - work normally, 8 channel - don't working, 9 channel - work normally.

It's much better than earlier, but 8 and 9 channel mode don't work properly.

With NiMh battery, 'Battery Alarm' = 4.20V, after battery alarm I get critical warning (3.80V) "Critical battery level detected. Settings have been saved. Any future configuration settings will NOT be saved. Change batteries now!" in 7 min and full shootdown of Tx in 13 min.

Generally if there is a build I want tested, it is posted in the announcement section as an 'Experimental build'
At the moment, I do not have any features that I need further feedback on, so the last experimental build is out of date.
If you really want to follow the bleeding edge, you must compile the build yourself following the README on bitbucket (listed above)

You need install the build environment and download latest source code.

bitbucket.org/PhracturedBlue/deviation

vlad, 4.2V is very low for NIMH batteries. You are very near the dropoff point at 4.2V, so I am not surprised that your batteries fail quickly from 4.2V to shutdown.

If you think your battery voltage really isn't 4.2V (measure with voltmeter) or if I am misunderstanding the issue, please provide more detail.

It's not a problem at all, but only demonstration how quickly battery fail after 'Battery Alarm' = 4.20V. Real battery voltage about 0.1V higher than value at screen.

You can get a feel for battery dropoff here:
shdesigns.org/batts/battcyc.html
for a 4-battery NIMH pack, by the time you hit 4.3V you probably want to shut it down. I'm glad it works as intended though.