silverghost

iTrader: (15)

I am a long time lurker who has done all of his tuning and ROM file data editing with Ecuflash 1.30. I recently tried to update to Ecuflash 1.41. When I open my ROM files with the 1.41 version, the tables are fowled up usually on the Y-axis. So, if I look at timing or fuel tables the RPM axis may alternate 19240 and 24. The numbers for the left hand column for my JDM MAP sensor tables bear no relation at all to what is supposed to be there. I am currently getting a PO365 code. In spite of correcting all the JDM MAP sensor definition tables as mrfred listed in his JDM MAP thread, I still get the code. When go back to look at the "fixed" MAP sensor tables , they are scrambled again.

Can anyone point me to a thread that addresses this problem? Alternatively, can you tell me why a table edited in 1.42 is scrambled again when you reopen the file after saving it? My laptop is regrettably a Vista unit.

tom04841

Try changing the endian in the xml file to "big" rather than the "little" that is probably there

silverghost

iTrader: (15)

I am using Ecuflash 1.41 and its associated Evo9base and 8590015 files that were loaded with program. By my way of thinking there should be no endian conflicts within the same application. Or are you saying that there can be endian conflicts between the ROM file and the Ecuflash version? That sounds unlikely but I am not a computer wizard.

silverghost

iTrader: (15)

Tom,

Apologies to you. There were both endian and xml syntax errors introduced by me. Thanks for the help