DR/Expo data fails to convert/translate r1197

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Write ER9X EEPROM data to g9x stock board transmitter

Transmitter detects ER9X data and proceeds to translate. Once completed, the 
DR/EXPO data is missing from all models. (companion9x does not have this 
problem, by the way. It translates correctly.)

Original issue reported on code.google.com by gru...@gmail.com on 8 Nov 2011 at 10:55

[GoogleCodeExporter]

We had this bug before and it was corrected. I tested it was working myself. 
But my testing was on the V4 board. So perhaps the translation bug still exists 
only for the stock board???

Original comment by gru...@gmail.com on 8 Nov 2011 at 10:57

[GoogleCodeExporter]

Hmmm. I remember me solving this issue in companion9x. I will check tomorrow. 
This issue will wait for the night. Not more ;) Could you attach the EEPROM 
please?

Original comment by bson...@gmail.com on 8 Nov 2011 at 11:00

[GoogleCodeExporter]

I attached the data files in the c'9X issues site.

Original comment by gru...@gmail.com on 9 Nov 2011 at 10:54

[GoogleCodeExporter]

Ah ok, thanks!

Original comment by bson...@gmail.com on 9 Nov 2011 at 10:57

[GoogleCodeExporter]

I need to know which is the target you chose on companion9x. If you choosed 
er9x, then I understand why it doesn't work: companion9x is not able today to 
write the expos/drs in er9x format (it's not so simple, and truly some cases 
will be impossible, g9x is more powerful with it's unlimited switches!).

Then if I am right, it's not a bug for g9x, but c9x! In any case it's in my 
plate :)

Original comment by bson...@gmail.com on 9 Nov 2011 at 8:47

[GoogleCodeExporter]

Target was as stated(??) gruvin9x - stock. Definitely.

Original comment by gru...@gmail.com on 10 Nov 2011 at 4:52

[GoogleCodeExporter]

But the data files you provided in the c9x issue are .eepe files. Then you had 
to use companion9x to transfer them and you choosed one of the 2 formats (in 
the parameters dialog box):
- gruvin9x format <= impossible, you wouldn't have conversions on the Tx!
- er9x format <= but in this case when c9x generated the tmp hex to be 
transferred by avrdude, the expos were already missing!

Original comment by bson...@gmail.com on 10 Nov 2011 at 8:43

[GoogleCodeExporter]

I don't understand what you're saying. Why does any of this matter? The file 
that was written to the transmitter WAS ER9X format. For all I know, it was 
written using eePe, not c'9x. Does it make any difference? If it's ER9X data, 
then it's ER9X data, right?

Original comment by gru...@gmail.com on 11 Nov 2011 at 4:33

[GoogleCodeExporter]

I am saying that a .eepe file, when it's transferred from c9x is converted to 
an internal memory model which is not the eeprom model, and then it's converted 
again to the chosen format (gruvin9x-stock, gruvin9x-v4, er9x), depending of 
c9x configuration. If you have chosen er9x, the DR/EXPOS are lost, due to 
actual c9x limitation.

Original comment by bson...@gmail.com on 11 Nov 2011 at 9:01

[GoogleCodeExporter]

Yes, understood but .. .oh ... I see. Hmmm. Well, I guess we'll have to test it 
again from the start to be sure what is or is not happening. I'm pretty sure 
this was c9x loading an eepe file that was saved from eepe. But I just can't 
recall now. Sorry.

Original comment by gru...@gmail.com on 13 Nov 2011 at 12:17

[GoogleCodeExporter]

This seems to be working OK. We installed g9x r1220 on a stock radio today and 
watched it convert er9x data. DR/EXPO all came across correctly.

Original comment by gru...@gmail.com on 18 Nov 2011 at 5:27

[GoogleCodeExporter]

Perfect, I change its state to verified then!

Original comment by bson...@gmail.com on 18 Nov 2011 at 8:39

• Changed state: Verified