7E installation problem

deviation-devo7e-v4.0.1-6a63c8e.

("new" below means something has changed

1.) Start up: message "Bad/missing protocol modules!"
2.) Opened Model 1, changed Model type to Plane
3.) new: Tx is defaulting to 10 mW (was 150 but 10 is correct -- no power mod)
4.) Protocol selected DSM2
5.) new: Re-Init is the next action (used to be "Bind")
6.) new: # Channels is 12 (I think it used to be 7?)
7.) Mixer GuI left as Advanced
8.) Went to TX menu, Tx config
9.) Stick Mode is Mode 2 (default)
10.) Calibrated sticks.
11.) Went to Channel Monitor
12.) Channel monitor shows left stick vert. assigned to CH3, Right stick vert. assigned to CH1
13.) Switching off Tx, and switching on again message: CH1 is 0% safe value = -100% (repeated twice) then the Bad/Missing modules message.

Notes:
To see if the protocol modules had somehow not transferred properly I opened the Protocol folder on the Tx and counted 16 modules present. This is the same as found in the build.
I then deleted the entire protocol directory on the Tx, and loaded a fresh version from the build. Tx drive was properly unmounted. Was able to reproduce the the above.

I then checked the Mixer
1-THR was mixed to ELE, and 3CH-ELE was mixed to THR

I then changed the Model type to Heli
No change in channel assignments

Here's a "good" model.ini for the plane version of above. Created in the v4.01 official release version of deviation.

with the 7e you always have to replace the protocols folder with the one that came in the build you are installing, hence you receiving the bad/missing protocols message

Harry I replaced everything when I started testing, including the protocols folder. The TX was blank. I moved the entire build in.

I also copied the protocols folder a second time -- and noted that above. No change.

I tested HappyHarry's latest build and the protocols are working fine after copying them from the ZIP to the Protocols folder (I forgot to do it originally, got the same message, copied them, message gone)

Okay wording looks slightly different -- Harry said replace protocols folder robca said copying protocols -- does that mean individual files copy vs folder w/files copy?

I'll try copying the files rather than the folder with files......

Copied individual files. No difference.

Okay, I'm going to wipe the Tx again. Unzip the build again and copy it over again.....

files/folder with files it makes no difference, just be sure to use the protocol modules from the exact build you are installing, not just from another 4.0.1 build but the exact build (6a63c8e in this case)

When you flash a new build of Deviation, usually your filesystem doesn't change. So I usually just copy over the new files. For the protocol directory, since the files are always the same 16 file, I just copy them over the old ones, replacing them

I flashed a lot of time, never had to wipe the Tx (not that it would hurt, mind you , just an extra step I was lucky not to have to do)

robca, I wiped it to eliminate any question in testing.

Just wiped it again. Unzipped the build. Copied the build to the Tx (except .dfu and dev zip). Unmounted the Tx. Turned it on and got the Bad or missing protocol message immediately.

I got the build here:

www.deviationtx.com/forum/builds/2661-7e...timer-weekly-updates

I used the zipped file attached to the first post there.

VTdev,
it is more likely that this message is a result of an active model config which defines a protocol what is not activated in the hardware.ini. Please take a look at the hardware.ini and the modelXX.ini you're trying to load.

If Harry didn't wipe the Tx either, then maybe that is the difference.

Or if you both didn't use the same build file zip that I did, than that might be a difference.

Only two I can think of....

rbe, attaching both here. They were received in the build zip.

it's my build file your using so of course i used it, and yes i wiped the tx as i always do when testing a new build.

i just re wiped the tx and used my build to flash and copied the filesystem accross and it worked fine.

you must be doing something wrong in your process

maybe PB or FDR if you read this could move these install posts to another thread, as there is no need to fill the channel switching testing thread with install issues

I've just wiped the Tx and reinstalled the official released version, and no Bad/missing protocol message. Starts up fine.

So I wiped again and reinstalled the new build, one more time. I used exactly the same method as the above official release (except for the fact that the new build included a hardware.ini -- which was copied across) and on turning the Tx on, had exactly the same Bad/Missing protocol message as before.

i don't know what else to say or suggest, i have re-downloaded the file from the site to make sure there wasn't an issue when uploaded, extracted it, flashed the dfu, erased the usb drive contents and copied the new extracted filesystem across. i have done this in windows and repeated it again in linux, and it works perfectly in both OS's. Also as you have seen other users are having no problems with the file so i'm afraid that using a simple method of elimination that leaves your method/your tx/your computer as the problem.

please tell me you are flashing the new dfu and not just copying across the filesystem?

Wiped, did the official version again. no problems.

Wiped, did the new build again, same old problem.

Deleted the protocol directory.

Copied it to the Tx again.

Same problem.

Any suggestions?

I am copying it across the filesystem. With both the official version and the new build.

Why would they vary?

flash the new dfu with dfuse, it doesn't install the core firmware just by copying it across with the filesystem, please go read the manual on how to install deviation, you need to follow this method every time you want to install a newer version