| Author | Message | ||
     Sincityx1 |
So I've been using the latest (just tried with 1.12.1) Ecmspy and running into an issue burning data back to an eeprom for a US 2001 X1. Here's my test sequence that shows the problem. 1. Load Stock X1 Eeprom. 2. Load Fuel map (in this case i'm trying the Race ECM map that I generated by hand editing the tables and saving the MSQ.) 3. Save Eeprom. 4. Load new Eeprom. http://www.pixelranchstudios.com/images/buellx1/Ee promNotSavingCorrectly.jpg As you can see by this picture it appears the eeprom is not being saved correctly. I tried this with many fuel maps, including road tests from MLV. Any thought Gunter/others? | ||
| Id073897 |
Please update to the most recent version. There had been an issue with the serial communication, which had been fixed. Regards, Gunter | ||
| Sincityx1 |
As stated in the post I'm using 1.12.1 with the MLV v2.941 released today. This happens without even burning to the ECM. Loading eeprom from file (Fetch from stock ECM) and doing steps 2-4. I did get this to work today by not loading the MSQ; instead editing the cells by hand and saving the EEPROM and not the Fuel Map / *.msq. EDIT>> Also I found out if I load two ECMSpy applications, load the MSQ into the first then copy the map cells via Ctrl+C/V into the loaded EEPROM in the second app then save the eeprom it will load/burn correctly. So I can get it to work but not as intended. Hopefully I'm being clear enough. Want to help ECMSpy as much as possible. (Message edited by sincityx1 on May 21, 2008) | ||
| Id073897 |
Please mail your broken eeprom copies to support (at) ecmspy.com Regards, Gunter |
