Fuel pump gone crazy after updating INI file

[grover]

Hi guys,

I just put in a newer version of the firmware (the first time I've done this since the system was first installed 2 1/2 years ago.) I put on version 2.891. The install went okay after one error message the first time (said "Could not read record 59 block during verification. Exception caught: 4") After this I tried again and the verification wento to 100% no problem.

However, when I turned the key for the first time the fuel pump ran for it's normal second or so, shut of, and then came on again. It continues to cycle like this.

Any idea what the heck is going on?

[Bernard Fife]

grover,

You might want to read the red text in the blue box on this page: http://www.megamanual.com/ms2/code.htm

Lance.

[grover]

Thanks Lance. My brain hurts!!! I'm going to see if I can go back and just load an older version as I really don't want to have to create a new MSQ from scratch. I can see an S19 file that is v2.88, but the closest matching INI file is v2.8. Will these work together okay? All I was trying to do was get some version codes to match up so that I could try using TunerStudio (all I've ever used is MegaTune) and now this has turned into a bit of a nightmare...

[grover]

Ok. Now I'm really getting frustrated. I tried to re-load the 2.88 S19 file and I keep getting part way through the verification and then it tells me it has some sort of block. Each time it happens at a different place, sometimes at 4% verification, others at 30-something %. What the heck is going on?

[grover]

Good morning guys. It's a new day and I'm trying to come at this with a clear head. The software side of MS has always been my weak point, so please bear with me.
1. For whatever reason, I can no longer get any code version to fully load into the ECU, it always gets partially there (completes the "writing" phase, but then stops at varying %'s during the verification phase) and then quits. Any idea what would be causing this?
2. Assuming I can get number one resolved, how do I change the MS ECU setting without downloading an MSQ? I've never used TunerStudio before so don't feel familiar with it. My ASSUMPTION is that I'd need to open a new project in TunerStudio (while drawing 12V power from the car battery) and set the MS type first thing and then burn this to the ECU. Is this correct? Again, assuming so, is it possible to then open one of my old MegaTune MSQ's with Tuner Studio to gather all of the settings? In TunerStudio it strongly suggested against creating a new file totally from scratch so I'm a little perplexed as to how else to get my base settings back.

Thanks for you patience.

[grover]

I'm pulling my hair out trying to update new code onto my MSII board. I've previously had an older version of the code (2.6 something I believe) and have been trying to update to 2.891. Each time it will get all of the way through the "writing" phase of the install, and then stall at somepoint during the "verification" phase. I've tried brand new batteries, checked all my connections, etc... and nothing seems to work. Sometimes it will get as little as 4% through the verification, other times as far as 70-something percent. The error code is always something along the lines of "Could not read record XXX block 1 during verification. Exception caught: 4".

I'm using the same laptop I've always used as well as the same DB9 cable. Would really appreciate help on this as I'm getting super frustrated.

[grover]

After many many tries I finally got the code to load. Don't know if this was to pure luck or to do with various connections I wiggled, etc.. Regardless, I'm MOSTLY happy. Only weird thing is that now the AFR reads a constant 12.1. Will recalibrate the LC1 tomorrow morning when everything is cold again, but any chance this is related to the new firmware? thanks for your patience guys.

[kjones6039]

Did you recalibrate you afr table after installing new firmware? It must be done every time you update. (been there, done that)

Ken

[grover]

AHA!!! Thanks Ken, I'll give that a spin first thing tomorrow. Looks like it was set to Narrowband so that could well be the issue. Thanks so much.