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

Hey all - wondering if I should continue chasing this map.

I have a MS1 which fried this past weekend. The car has a big ground-interrupt switch. It was running with a jump-box connected (tiny battery), but the ground-switch was NOT turned on.

The ground cable of the jump box was removed. Car died, and it appears that the MOSFET switch that sends a signal to the injector drivers was the primary failure.

I can't get my laptop to connect to the MS box - at this point, I suspect the serial cable, but won't know til tomorrow. However, if the cable is correct, should I spend lots of time trying to get my data off the broken MS? I want to put that map on a MSII, which I have.

Time is of the essence in this particular case - the car needs to be running by the weekend.

So - the question is simple - do you THINK that Other Stuff got damaged when the ground was removed? The processor appears to be sending the correct signal to the MOSFET.

Would that sort of electrical interruption cause widespread damage/an inability to connect to a laptop?

It would be WAY preferable to get the existing data, put it into the new MSII and be done with it - if I had more time, I'd just download a baseline map & go to the dyno, but if I can avoid it for this weekend, great.

Thoughts?



Iain

Well, the thing is that an MS1 map won't translate directly over to an MS2 and would need some tweaking to work anyway. I would probably just go ahead and hook up the MS2. I can also walk you through testing out what's dead in the MS1 once you have a serial cable.

Matt Cramer wrote:Well, the thing is that an MS1 map won't translate directly over to an MS2 and would need some tweaking to work anyway. I would probably just go ahead and hook up the MS2. I can also walk you through testing out what's dead in the MS1 once you have a serial cable.

Thanks! Would the MS1 _data_ - information, values, etc - be visible & able to be manually input into the new MS2 map?

That's what I'm missing - the actual data. My logic was this:

1. Get data off MS1.
2. Take those values and put them into an MS2 map (understanding that this might not be _super_ simple - close is good enough for this weekend)
3. Install MS2.

In theory, the car should run the same - I hope. I can't even remember the tables - VE and fuel/MAP, what else? I was simply hoping to get those values into the MS2 for the weekend.

I do have a slot reserved on a dyno for Friday morning if I do have to start from scratch, but if I COULD take the values from my old maps/tables, put them into the MS2 map, and have the car run largely the same as it did before the jump box was removed, I'd be happy. I have a competition this weekend in Nebraska - if it were one week farther out, I would just install the MS2 and go to the dyno when comfortable. Super pressed for time.

Is my logic flawed? Will it not be possible to take the values from the MS1 data and plug them into the MS2 files?

Thanks a lot - I've been really happy with MS, continue to do so; can't blame the MS for this one, 100% operator (not me) error.


Iain

Yes, you can copy over many of the basic settings by hand, and the VE and spark maps can be exported in VEX format. The VE table may need some tweaking though.

Matt Cramer wrote:Yes, you can copy over many of the basic settings by hand, and the VE and spark maps can be exported in VEX format. The VE table may need some tweaking though.

Excellent, thanks! I appreciate it.

At this point, I _hope_ the cable I was using last night is a nullmodem cable (was too wiped to check last night), was not getting any response from the ECU. Have another one now, will check it before I plug it in.

I really appreciate the help, Matt!


Iain