Devo 12

Sorry, I didn't mean to make it sound like I didn't know how to do the mapping. I meant I wasn't sure how I would actually handle it in the code from a migration perspective. I think I've got it sorted now though

I've finished the hardware documentation:
www.deviationtx.com/articles/19-devo-12-hardware-connections

I thought you guys might like this.
There are still some display issues (some fonts aren't showing properly), and for some reason the analog update isn't working, so i can't actually read channel values, but I think everything else is functional now.



Just as a reminder, we're going to start with the Devo8 interface, which means 320x240 which is why it is running in a window. eventually we'll do a custom 480x272 interface, but for now this will get the functionality out there much more quickly.

Congrats!

Mine came with a europe->us plug in the case. If you don't have it, you can get one for a couple bucks (you only need the adapter not a power converter)

I don't think you'll have any problem charging with usb. I think the normal connection is limited to 500mA (low power USB). I think. USB has a special high-power mode that needs to be enabled explicitly by the slave, and the Devo12 won't enable it. That said. check your batteries while charging and make sure they don't get very warm.

Well, I fixed the display issue and the channel scanning issue. Both of which took a lot more effort than I expected.
So now, I just need to integrate the code into the trunk and provide a mechanism to build the library dfu, and we'll be ready for the 1st experimental release.

PhracturedBlue wrote: Well, I fixed the display issue and the channel scanning issue. Both of which took a lot more effort than I expected.
So now, I just need to integrate the code into the trunk and provide a mechanism to build the library dfu, and we'll be ready for the 1st experimental release.

Cool!
What's next? F7 or F4?

You'll need to wait another day or so for the experimental builds. I still don't have any way to automate the library dfu creation (the 'media' directory needs to be uploaded via dfu rather than the standard USB filesystem way...all other files use the filesystem). I am having difficulty finding a solution to this that will work in windows and linux.

And while I know FDR said it in jest, I have no plans to support the F7 at this time. I have no idea how to deal with the FPV aspects, and I think adding 2 new Tx to the supported list for the next build is sufficient.

Rather than immediately focusing on a proper 480x272 interface, or enhancements for the 7e (or elsewhere), I expect I will try to work on getting all the bugs that have been introduced in the past month hammered down and get out a new official release, as it has been 2 months since 2.1.0

1st experimental build for the devo12 is available:
www.deviationtx.com/forum/builds/1380-de...89f1f-devo12-support

you can go back to stock by upgrading the firmware and lib.you will lose all model and configuration settings though.

Note that it may be necessary to shutdown and power back into programming mode after upgrading the firmware before upgrading the lib. You'll know this is the case if you get a 'State machine' error. It doesn't mean anything is wrong.