Deviation 2.1.ea9ee2c4a03d (Devo7e Support)

UPDATE 2013-01-18: The current builds contain fixes for all issues up to post #5155

This build is very experimental for all platforms.
This is the 1st experimental release which adds devo7e support. More on that below. In order to support the 7e, the GUI code was significantly reworked (impacting all platforms) and the Devo10 scrolling-system was redesigned (impacting the Devo10 additionally). This release likely has many regressions in the GUI functionality (though hopefully it is still pretty stable) especially on the Devo10. Theoretically it should not behave significantly differently though, so I'm interested in any issues that are found.

The big new thing is the inclusion of Devo7e support.
With the exception of language support and reduced # of switches/buttons, the Devo7e build should behave identically to the Devo10. The following protocols have been tested to work: Devo, DSM2, DSMX, J6Pro, WK2601, WK2801

The Devo7e code has a big caveat: There is currently no way to go back to Walkera's firmware once you install Deviation. This is likely to remain true until Walkera releases a firmware upgrade for the 7e.

Additionally, installation of the Devo7e is slightly different than for the other Tx. The devo7e zip file contains both the dfu and a bunch of files in the 'protocol' directory. After installing the dfu, it is required to enter the filesystem and copy the 'protocol' dir (and its contents) to the root drive on the 7e. You must also install the devo10 filesystem, but everytime you upgrade the dfu, you must also replace the files in the 'protocol' directory.

Both of those work fine for me in emu_devo8. What is your build platform?

Edit: okay, I see it on windows. fixing.

In emu_devo8:

1. Main page config - I don't see main page layout (empty). If I scroll page, it appears on a moment and disappear. If I make change at layout, it it appears on a moment and disappear.

2. If I changing from complex mix back to DR/Expo, emulator silently closes.

3. Complex mix initially has 1 page only, and have not 'Mixes' and 'Page' controls. If I select any editable curve, edit and return, I will see 'Mixes' and 'Page' controls. After that I can change from complex mix back to DR/Expo.

the 3 problems reported by vlad (which includes the 2 reported by Hexperience) should now be fixed in the trunk. I'll build new binaries for devo8 after I get a bit more feedback on the emulator. The bugs mentioned so far should not affect devo7e or devo10

FYI, I plan to spend the next day or so just fixing regressions. I'll then start looking at the backlog of issues reported. Getting the Devo7e code working has taken a pretty solid 3 weeks and a lot of that was really tedious programming, so I am going to back off for a little bit.

yes though half of that was easy (compile options on other tweaks). The other half was the result of 3 weeks hard work.

both #201 and #202 are fixed. Thanks everyone for playing with this. What I would really like is if someone put together a set of steps to go through to look for regressions. We could build an article and add steps to it over time. That should help catch bugs earlier.
It may even be possible to write an autoIt script that could actually run those steps automatically.

by the way, in debugging the devo7e, I learned how to capture stack traces when the Tx reboots (well, for most types of reboots at least). I plan to add the ability to write that to a file on the Tx before rebooting so that it is possible to glean some information on hard-to-reproduce bugs.

Devo 8

Both GUI (Standard and Advanced)
1) Timer page - funny things with controls, e.g. if I change timer type (lower) it change start control for upper timer, not for lower timer.

Standard GUI
1) Gyro sense page - 'Value 2' control moved left and overlap string 'Value 2'
2) Though it's not related to release, but why channel 6 has name 'PIT' for Airplanes? Will be better AUX1.

PhracturedBlue wrote: by the way, in debugging the devo7e, I learned how to capture stack traces when the Tx reboots (well, for most types of reboots at least). I plan to add the ability to write that to a file on the Tx before rebooting so that it is possible to glean some information on hard-to-reproduce bugs.

Do you mean the cases, when the watchdog restarts it?

What other reboot types are there?
- power loss/glitch;
- ???

The watchdog can reset for several reasons. One is if the code causes a fault (bead memor contents, bad jump address, etc). These I can catch now. Another case is hat the code is in an endless loop and not resetting the watchdog. In that case, the code I have doesn't work.
I may try switching to the windowed watchdog which has the ability to generate an interrupt before rebooting, but i'll start with what I have.

fixed the gyro page and the timer page. The 'Standard' gui really hasn't been setup for planes yet, I'm sure there is a bunch of work to do to make that work properly.

I have updated the 1st post with new builds which fix all the issues reported so far.
I also added the above mentioned stacktrace capture code. there is a new file on the root filesystem called 'errors.txt'
This file should contain stack trace information whenever the transmitter crashes. Note that for me to make use of it, I need the .map and .list file that are generated as part of the build. I have these for builds I generate, but if you are running your own build, make sure to save these 2 files so I can use them for debug.

I recommend you use the version that is at the top of the devo7e thread, or build from source. Many of the issues you listed have already been resolved. Discussion of devo7e status is better left there. This thread was more targeted at addressing regressions to the Deo10/8.

This is normal for most battery types, but it should level out after dropping .1V or .2V (assuming your battery is charged). I'll reverify current usage with the latest builds, but typical consumption is < 150mA I believe which will last more than 10 hours on a 2000mAH battery pack.