Modelfilename appending with EEprom Typ

[Helle]

Hy,

I thing the EEpromfilename shold be appended with the EEprom Typ Versions
EEprom 212 213 214 and so on

Same as companion append the Software Realse Nr. of open9x

got allways the wrong file!

Helle

[jhsa]

Yes, And the downloaded fw should also have the revision number and eeprom number..
Would it make life easier?

[kaos]

I am doing that manually now. would be nice if it is automatic. this applies for all 9x variant.
when back up an eeprom from tx, the FW, revision can be added to file name automatically. ie: open9X-NOHT-r2054.bin, er9x-m128-r121.bin, er9x-m64-FHT-r781.bin............

[jhsa]

And the number of the eeprom too:

er9x-m128-r121-e212.bin

This also when you download a new version of the fw. the revision and eeprom version that works with it.

[ReSt]

And don't forget the Eeprom variant

My private solution for my locally compiled versions of open9x:
I force the eeprom variant to 3 (FrSky + GVars) and set the preferences to FrSky + GVars, independent of what I compile.
This seems to work. Since then I never had a problem with an invalid EEPROM message of the radio.
May be it takes a little bit more EEprom space, but it works without trouble (as far as I can say up to now).

Reinhard

[MikeB]

This is why I try to keep the er9x EEPROM from changing. I'm just adding flight phases to the M128 version. This has added extra EEPROM items at the end, but this is a safe change. Er9x will either ignore the extra items, or will add zeroes at the end for them automatically.
With the compression used, multiple zeroes get compressed into a single byte.
So for compatibility, I've added the same storage to the M64 er9x. Models might get 1 byte longer, but the EEPROM files remain compatible.

Mike.