Deviation for Devo F4?

Well, here is an update. I haven't started looking at the video problem, so there really shouldn't be any difference compared to the previous build as far as how it works, But there have been several filesystem changes. Note that this version is NOT compatible with old filesystems. Once you upload the new dfu you will need to replace the filesystem as well.

Here is the dfu (for both F4 and F7):
www.deviationtx.com/downloads-new/catego...edblue-f4-f7-fakefat

You can install it using Walkera's Devention tool, or the DeviationUploader (here is an updated link which ismuch faster than previous version (but can't upload the filesystem):
dl.dropboxusercontent.com/u/52854517/Dev...nUpload-0.8-F4F7.jar

Once installed, reboot transmitter (hold the ENT button if needed to enter USB mode). Then copy the included 'devo.fs' to the transmitter (you should see the file there already, just overwrite it with the included one.

You can also find buildfs.exe here:
dl.dropboxusercontent.com/u/52854517/buildfs.exe

You can use this to see the contents of the devo.fs file and to create a new one if changes are needed:
To extract:
buildfs.exe --fs <path to devo.fs> --dir <directory to write to> -x

To create a new devo.fs:
buildfs.exe --fs <path to new devo.fs> --dir <directory where devo.fs was previously extracted> -c

I was able to build a FUSE filesystem to access the devo.fs file, which works well on Linux. I ported it to Windows as well, but it isn't qorking properly yet, so I have more debugging to do there.

the 'ne' is likely left over from the previous screen redraw. I'll take a look as I saw the same thing (mine was 'Ok' though).

I didn't keep all the protocols. Only devo and dsm2 are there. But I included the others in case you want a different set of them. The hardware mods are the same as any other Devo Tx, but as I said previously, you can only have 2 or 3 protocols on the tx at one time.

I tried to explain in my previous post, but to modify the INI files (or change the protocols) you :
1) use 'buildfs -x' to exract the filesystem from the transmitter to some directory.
2) add/remove protocols or change the ini files, or add models or whatever in the directory just created
3) use 'buildfs -c' to create a new devo.fs file
4) copy the new devo.fs file to your Tx

the dsm2 and dsmx are treated as different protocols, so yes, I only supplied dsm2 and devo and NOT dsmx. you can change out the protocols using the instructions I provided though.

you can fit a 3rd protocol if you don't want any more than 10 models (you could probably even fit a 4th depending on how complex the models are)

I just wrote the buildfs.exe script, so no there is no thread. what is the command you are running in theCMD prompt, and what is the error you are getting?

To be honest, I didn't test the code much on windows. I wrote and debugged it on linux, and compiled it into exe through Wine. So I need to look at it to see why it isn't working. I don't see anything wrong with what you've done, so it is probably a Windowsism that is breaking it

I take that back. make sure you use '--dir' instead of '-dir' (two hyphens on 'dir' and 'fs', one hyphen on 'c' or 'x').
And make sure the directory you specify for --dir already exists

I also edited the typo in the instructions that caused you to do this. Sorry