MSefi.com read only forum (Jan.15,2018)

Hi everyone,
Hopefully you guys can help because i'm stumpped. I had a MSII unit in my car for the last couple years. I haven't been able to run the car for quite some time, but finally got around to playing with it this week. I went to start it, after it had sat about a year. Prior to putting the car away, the ECU ran just fine. This is a V2.2 board with a V1 MSII unit installed.

At first, the car fired up, but didn't want to idle. In Megatune, the RPM's showed as if it was divided by 100 (ie. 3200 RPM on the tach registered as 32 in Megatune). After some troubleshooting (replaced various EDIS pieces, assuming it was an ign problem) with no luck, I decided to just reload the firmware and start from scratch.

Once I placed the jumper on the board and cycled the ECU on, I could no longer connect. Hyperterm will not return a character. Using the port check app, it doesn't make a connection. Same deal with Megatune now.

When I connected it up to a stim board, I have the following LED's lit (constant, not flashing):
FIDLE (on Stim)
Fuel Pump (on Stim)
All 3 of the MSII LEDs

I've verified that the stim is supplying sufficient power (1 amp/12v ac/dc). I wasn't able to locate a burnt trace or anything obvious on the board to indicate what failed.

Does anyone have some suggestions on where to start? I'm really stuck on where to begin.

Thanks
Drew

What firmware are you using?

Don't laugh, it's really old. I believe it's 1.8 something.

Could you confirm that, or post an MSQ? I'm not sure there was a standard 1.8 firmware.

Aw you're right, looking back through my old files, my MSQ files state:
MSII Rev 1.31

3, 8's, they look the same

Can you try reloading the 1.31 S19 file again?

That's what I wanted to attempt, but I can't seem to communicate anymore with the board. Even in hyperterm, I can't get it to echo out key strokes, which is why I'm not even sure where to begin.

What error message do you get when you attempt to load the code?

At this point, I just get a timeout message when trying to connect using the download app. I've double checked that Comm 1 is setup right and that was the port I was using previously that worked.

Could you post a screen shot of the message?