Strange eepe/Companion9x issue?

[ShowMaster]

It may be firmware r677 but..
latest eepe will download mixes from 2 SP equipped 9x's but the latest Companion9X give me an error. Both programs download the TX's firmware. I've reinstalled the latest.34 companion with no help. After upgrading the TX FW to r677 from r666 I was able to download the mixes from both transmitters with C9X one time?
What the heck is going on? It happens on 2 different computers running xp and different usb cables?
Error message is invalid eeprom file and something about temp.hex
SM

[pmackenzie]

The latest version of ER9X has some changes to the general settings in the EEPROM from version 9 to version 10.
This was done to add the switch alarm settings and stick motion backlight features.

Companion9X probably just has not caught up yet so it sees the new data and thinks the eeprom is corrupted.

Pat MacKenzie

[ShowMaster]

Whew, I think that's it! I did roll back the firmware to r666 and was able to down load the mixes but when I tell companion to save the mix it saves as a ,xml file with 0 size? when i open it in companion there's nothing there. eepe works OK and saves the mix as a .eepe file that will open in eepe.
This all worked before I updated to r677 and I guess going back to r666 does not fix it 100%. More going on than I understand so I'm going to use eepe and get my tx's all up to date and working with r677 again with my saved eepe mixes.
Would going to r677 from r666 change the eeprom so that it stays a version 10 even when flashed back?
Just curious what the eeprom versions actually do.
I'm just trying to put my mind at ease that I didn't mess up at this end and also understand more of what you have to do to make it all work.
Thanks for your help. Going to sleep on it and start fress in the morning.
SM

[jhsa]

Also I couldn't load eepe models (.eppm) into companion?? Or maybe it's just me doing something wrong?
João

[Romolo]

Ok current windows release (0.34) cannot read version10 eepe files....
but we have already done necessary mods... 0.35 will be published asap...
Romolo

EDIT: version 0.35 released

[Romolo]

Also I couldn't load eepe models (.eppm) into companion?? Or maybe it's just me doing something wrong?
João

eepm files are dumps of the single model structure.
We are looking for a smart way to do not break compatibility with eepe but to be, at the same time, able to understand if it's a model from er9x, open9x, gruvin, th9x and so on.
Meanwhile the workaround is to read them in eepe, save a whole eeprom with just one model and open the file in companion.

[erazz]

Yeah, that's part of the reason I moved to different file extensions.

Adding the headers simply makes it easier to make sure you're downloading the correct file. If you think there's something I could do to help in compatibility let me know.

I admit that I haven't looked at companion yet. Do you have separate dialogs to edit different eeproms? I simply didn't want to deal with the complexity of changing all the details from all the separate eeproms. I also wanted to use standardized controls in order to make editing easier.

[Romolo]

Erazz,
No we have a unique interface.... only not needed field are hidden/disabled.
Main changes from eepe are: preferences (as you have to choose the firmware you are dealing with, EXPO/DR editor, simulator, fw burning dialogs, printouts

We are thinking about a way to deal .eepm files in an unique way amongst all firmwares, maybe adding something to the header that helps eepe to understand it's not a model coming from a er9x firmware. We want keep compatibility with eepe, we do not want to break it.

Keep up your good work,
Romolo

[bertrand35]

Hi,

Right, we plan to support eepm files as well. When exporting eepm for er9x we would like to have exactly the same header and same format than the eePe ones for compatibility reasons. And when exporting to other firmwares, we will still use the eeprom format / compression, but with a different header, including the fw name and version. So that companion9x will be able to read all model files.

The problem we face here with the eepm files is that we don't know the sticks mode (since they are not stored into the file). Perhaps Erazz, would you agree about accepting files with a slightly different header (including the sticks mode)?

Also we plan to work on another file format, xml based, and firmware independant, but that is another story. We will show the xsd on this forum as a request for comments ... More on that soon.

Bertrand.

[erazz]

Oh yeah. Absolutely!

I think an XML would be a very good format for this though making the reader would not be fun. As it is we just read the data straight into the buffer. Would you store the actual data in the XML or would you decimate it?

(now you have me interested )

[erazz]

I've just uploaded to the eePe trunk some of my work towards XML.
It's a lot of work but it looks to be shaping up wonderfully.

I think this will make it very easy to read from various eeproms.

Check it out.

[cre8tiveleo]

AAAAAAAAAAAAAHHHHHHHHH

Heeheee..

Okay, so I wanted to change my fuses BACK to let the firmware upgrade erase my eprom data... (to see if it clears up some issues with a test er9x from Rob and Bertrand)



Where.. in the latest version of eepe can you do that...

[erazz]

Why would you want to erase your eeprom?
The easiest way that I can think of is just to create a new memory in eepe and upload it to your transmitter. That will erase and format your eeprom.

[capitaineflam25]

Hi,

i'm not sure it is the appropriate thread but when i restore an eeprom i lose some of the previously set parameters: Int. Frsky Alarm ON, Alert [Yel], Alert [Ora], Alert [Red], and also RSSI alarms parameter.

I'm using Companion9X 0.42 with Er9x-Frsky 736

Regards

[MikeB]

Does this happen with eepe as well?
Currently, the RSSI alarms are not stored by er9x, they are read from the Tx module where they are stored. If they are changing then this is some other problem!
I think the other items should be stored OK.

Mike.

[capitaineflam25]

You're right the bug didn't reproduce in eepe.

Regards

[Romolo]

It was fixed in companion some time ago, may you check again ?

[capitaineflam25]

It's ok now, i can't reproduce the bug in latest Companion9X.

Regards

[spagoziak]

I was wondering.... what are these options for? How do they work? I haven't found any documentation on them yet. (I have the dht diy mod installed and working)

[Kilrah]

What options?