Deviation 2.1.bffc70489f1f (Devo12 support)

Here is the 1st experimental build with Devo12 support
As noted in the Devo12 thread:
This uses the Devo8 interface at 320x240. We'll eventually build a proper interface, but it is not a priority
The installation procedure for the Devo12 is different:
1) install the firmware dfu via the 'Firmware' tab
2) unzip the filesystem
3) install the devo12-lib.dfu as a library (via the 'Library' tab)
4) power on and see the USB indicator.
5) format the drive
6) upload the contents of the 'filesystem' dir to the tx (what is inside the 'filesystem' dir, not the dir itself. you should have tx.ini and errors.txt in the root of the Devo12 filesystem)
7) power off and enjoy

I have verified that you can go back to stock by flashing the original firmware and library dfu. you will lose all model data as well as all settings though.

For everyone else:
The switch names ave all changed.
AIL DR is now 'AIL DR0' and 'AIL DR1'. This applies to all toggle switches. They should transparently map from your old models, but once you load this firmware, your models are no longer compatible with any previous dfu! Make sure to backup your models dir 1st!

Other changes since the last expermental build:
* the devo10 default model icons have changed to public-domain variants
* The file-format for bmp files on the devo10 has changed a little. Old icons may not be compatible
* several bug fixes in page navigation/display
* there is a 'debug' zip file included in the build. Do not put this on your tx, but hold onto it in case you have issues. It can beused to debug crashes
* improved 'standard' icons from FDR

Note that this release has only been lightly tested on each platform. I am quite sure that the switch-name changes will wreak havoc all over the place (especially in the standard mixer)

Deviation, unlike Walera's firmware, does not try to detect whether the telemetry module is installed. If you don't have it than I believe there is no LNA attached to the CYRF chip. This is the opposite of what the Devo7e has.
It means that receiving telemetry is probably completely unrealistic at any meaningful range.

So Deviation may show you have 'Telemetry' and it may work on the bench, butI'd be really surprised if it worked in the field.

Tom_ate wrote: >>* The file-format for bmp files on the devo10 has changed a little. Old icons may not be compatible

Could you please add a small hint into the "modelico"-directory about the exact changes, and how to build icons for Devo10 with this new build (which may become to new standard format also for future releases, I am sure...)
Thanks!

This is likely not a permanent state. But I was unable to actually create bmp files that worked with the old code (I know the syntax, but not how to actually push the buttons in Gimp to achieve it). If someone has instructions on how to do so, I could probably tweak it to work with both syntaxes.

rbe2012 wrote: Shouldn't we try to examine if a telemetry capable module is installed and switch off the corresponding functions if not?

Why bother? Of all the things I could spend my time on, I see very little ROI on developing that code. You should know enough about your radio to know whether telemetry is going to work or not, and if you get it wrong, no harm is done.

Naviso wrote: Can you please tell me how i can check, if the connection between LNA and CYRF is there? the data i receive while flying indoor with the Mini CP are correct (Temperature raising, voltage dropping)
Thank you in advance

If it works then it works. If it doesn't work, you'll see the telemetry data turn red (devo8) or inversed(devo10) I think. I am not sure how to detect which module is in your TX. There probably is some way, but I don't know it.

thloh85 wrote: In the input monitor, my Devo12 sees the all channel jumping up and down like mad.
The sticks's input monitor keeps skipping around 1-2 up and down. For example, on throttle stick at mid, the value is not a solid 0, rather it runs between -1 to 1. I'm not seeing this behavior on my Devo10 on Deviation 2.1 (not running this experimental build). Is this normal?
Thanks for the reply in adv

Sorry, I should have mentioned this. I see the same thing on my devo12 and not the devo 8/10/7e. I haven't yet debugged it. It is 'normal' for this build, but absolutely needs to be fixed.

I had that issue too and had to read the manual
Hold the trainer switch while powering on instead