Deviation v5.0.0 build with latest protocols

Thanks for your hard work vlad...
hope to see this in the nightlies soon. i need it in combination with frskyx

Also wanna thank you for your hard work on developing Deviation further.
CU joerg

A parody of the US elections:
vlad_vy - "Making Deviation Great Again"

Thanks Vlad, I love the old interface.

Just a FYI since you are under the hood - comments bug unfixed in all releases

I thought you were supposed to be able to keep comments in the model.ini files now, but all releases, yours and others, seem to delete them again when you make any change to the model in the transmitter.

This post said that it was fixed: www.deviationtx.com/forum/6-general-disc...odel-ini-files#42012

I tested this on D10 and 8S with V5.0.0, nightlies and your builds. All are deleting comments in the model.ini files.

If you ever get bored and want something to do...... hopefully the fix is out there and just didn't get merged into the current code.

I use comments in model.ini files to document channel layout and switch functions for models I release to other people. What would be really great is if the comments could be displayed on the transmitter screen especially now that quads have so many functions.

Is this build available as a github branch somewhere - preferably in the main repo? I'd love to see another automated build based on this. A lot of people run the nightly builds just to get new protocols. This was fine last year when the release was years old and the nightly was fairly stable, but that's no longer the case.

This is why one of the changes I wanted when I proposed forking deviation was to add an intermediate build between release and nightly: basically release + new protocols that were documented + bug fixes (loosely defined as not requiring a documentation change).

Thomas.Heiss wrote:

Thomas.Heiss wrote: First firmware test today with zip/dfu version dated 09/28/2016. So one day / one version behind last final 09/29/2016 version
- Devo10
- AR6210
- TM1000

Telemetry monitor (and main telemetry voltage field) was frozen at 12.1V.
All telemetry monitor fields constantly black/inverted (including main screen voltage).
When I landed and had the transmitter in near of the TM1000 the telemetry did not come back anymore as release 5.0.0 + fcd0669 did before.
....
TX transmit signal was OK (no deadlock) - controlling the EPO glider was no problem over the whole flight.
....

I)
Another ground test in near distance with build version 09/28/2016 AR6210+TM1000 in same room immediately got me a frozen telemetry screen.
....Other tests at 100uw showed, like Vlad describes, that telemetry returned once back in distance.
2nd test flight showed again the same behavior (loss of telemetry in-flight).

II) New test with Devo10 build version 02 Oct 2016 08:55:
Same behavior as build 09/28/2016.

Re-producable / repeated telemetry losses in-flight (freeze). Transmit works fine (no deadlock).
It's always just a quick telemetry connection.

So somehow in my test setup telemetry RX code creates a hangup in sporadic situations, and is always re-producable in -flight.
First 100uw ground tests were in parallel successful however, see below.

I also encountered a COMPLETE RX/telemetry freeze, just like I did once with 200QX on an older Indigo DSM test build.
Plugging in a new flight pack did not reset telemetry monitor.
I had to either turn OFF the transmitter OR switch to another model memory slot.

III) New in-flight firmware test - 4 lipos (about 15-40 minutes per flight) - with Vlad's test build zip/dfu version dated 10/07/2016 with
- telemetry frozen fix "CYRF_06_RX_CFG, 0x48": www.deviationtx.com/forum/protocol-devel...rrors?start=20#54584
- new mentioned 7CH re-write DSMx protocol code
- including FlightLog filtering code from #54690 www.deviationtx.com/forum/builds/6407-de.../54562?quote=1#54690

with
- Devo10
- Spektrum AR6210 (6CH setting)
- Spektrum TM1000 (works fine - not corrupt)
- 100mw output power
- EPO glider (explicitly tried to fly higher + more far away - as far as I could see the 2,2m wing glider)

with
- 0 Holds
- <10 FrameLosses: checked 4 times (4 lipos) and it showed ~8F max., so far below 20F, quite good!


Telemetry monitor in this build is again rocking stable so far for me - just like release V5.0.0 + V4.01-nightly-build-fcd0669.
Checked the monitor multiple times "live" during flight, checked monitor FlightLog values after landing on each flight of the four.
Not freezed / fields black/inverted any time!!

TX transmit code rocking stable as in every Deviation version (no deadlocks, no holds, no >40F) before. Always full steering control at any time.

I currently have no alarm for "telemetry out of range" active during flight (e.g >40F), only H>0 warning.
Probably I would get noticed on (shorter) sporadic "telemetry (range) notifications" H=255?

Thomas.Heiss wrote:

vlad_vy wrote: I havn't problems with telemetry (Devo8+ AR6210 + TM1000), 100uw test, with distance up to many Frame losses and several Holds. V1 =7,33V, V2=6,3V or 11,2V with different batteries, GPS show all info. After telemetry fields become black/inverted, all restored with shorter distance.

P.S. I done several range tests, with many Frame Losses and 8 Holds, about 30 min of uninterrupted testing. Telemetry work fine, I can't get it frozen.

My 100uw first ground test on build 02 Oct 2016 08:55 (only did one) was successful, like Vlad described, too.
Out of range -> telemetry monitor black/inverted fields.
Back in range -> monitor fields back to normal + displaying new FlightLog numbers.
Typical test-case which always worked for 5.0.0 + fcd0669 before.

In-flight I lost again telemetry monitor link to TM1000 and it did not come back anymore when I landed and had the glider next to the transmitter.
Comparing builds 09/28 and 10/02 I would say that telemetry lost (out-of-range) was earlier with 09/28??
10/02 telemetry was fine for a while, I manually checked the screen if the fields were black/inverted that soon.

I will have to go back and re-test with release 5.0.0, which always worked - like V4.0.1-nightly-build fcd0669 (BitBucket) - once I fix this glider fuselage (little bit of trouble with bad sight / cloudy / dark as of today).
....
I will try to re-test without bat field on main screen as well was with 5.0.0.
With build 10/02/2016 my test was with configured Bat telemetry alarm on #4-6 jumping slots, so I should have noticed.
With build 09/28/2016 my test was with configured Bat telemetry alarm on #1-3 non-jumping slots.

Further 100µw/300µw/1mw ground tests on Vlad's test build zip/dfu version dated 10/07/2016 with fixes/protocol enhancements are on my TODO list.

For the above III) in-flight test Bat telemetry alarm on #4-6 jumping slots +RxV (#1-3 non-jumping slots) was activated.
Bat telemetry on main screen (3s) was activated too for in-flight test - works great.
I have NOT noticed swapping of the telemetry fields to black/inverted at any time (when I looked up here and then).
So this works for me on 3s.

---

However I would love to have a previous build zip without latest FlightLog filtering code enhancement - so I can maybe intensively re-test FlightLog telemetry out of range / sporadic number jumping cases and write down all numbers I see on telemetry monitor.

....Like I did my videos before on Indigos test build 36cce5c once in the "DSM telemetry support" thread.

I somehow missed to download the previous build zip without FlightLog filtering before
Update: Thanks Vlad for old build zip upload.

Will try to start with this build 10/07/2016 and it's added (basic) FlightLog filtering code if time allows next 4-6 weeks.
Well, why even bother testing ground range on 100µw-1mw output power when it works just that great in-flight on 100mw


Q: Is it better to activate FlightLog logging and use the CSV transform tool instead of only manually writing down shown FlightLog numbers from telemetry monitor?

Will probably ask some further "understanding code" questions on current Vlad's implementation on our "DSMx/protocol errors" thread after re-checking "DSM telemetry support" thread...there was one comment about it by Vlad in the latter thread some time ago...

Thanks to Vlad for your support!

Thomas

I made a upgrade from 4.01 to this 5.0 build (with DSM protocol fixes). I found a problem in GUI - Devo8S. On main screen in Boxes (like Timer, Throttle) I see a value refresh like flickering. I don't know why probiem is.

Yes, its this problem.

vlad_vy wrote: Moreover, it fit to Devo7e..

Just even checked, it seems to run on my nonstandard ultimate 7e, only some protocol mismatches..muchas gracias.

Is itpossible to get an "ultimate version"?
I.E. language support, added switches, added pots..

Thank you vlady_vy. Now DEVO8S working without box flickering.