3.1 Turbo/Tuner pro HELP code59

[ab8127542]

I know this might sound dumb, but I've done this myself...

Are you sure you have the ribbon cable installed correctly in the MEMCAL adapter?

About checksum. TP automatically updates checksum when you save a bin, so if you're burning EEPROMs, disabling Checksum is not needed. If you're uploading whole bins to an emulator, sometimes you can get away without checksum being disabled, however, if you're truly emulating, where only singular changes are being made checksum absolutely has to be disabled. That being said I have had a couple instances where it wasn't disabled, and emulating SEEMED to work, but wasn't really working properly.

Installing an unmodified MEMCAL, does the engine start?

well, no, not exactly. The ICM fires it, when it's time for the .bin to take over, it chokes. This happens with checksum disabled as well. That's being said it has 36lb injectors on it, so the one time it started, it was rough and I'm 99% my limp mode for the 19lb'ers were running it. I didn't let it run long.

I double checked my cable, it seemed fine. I have a question. I've heard (read) about hitting the ecm with a bad checksum could brick it. Now I've tried multiple ecms, but they have all been hit with the same bin at one time or another, during this fiasco.

Is the checksum regenerated/updated when you make changes in emulation, i.e. like changes fueling etc?

[Six_Shooter]

No, bad checksum will not brink an ECM, at least not OBD1 ECMs.

No, checksum is only updated when the bin is saved. This is why checksum needs to be disabled during emulation.

So are you saying that it runs on base timing, but not when timing is being commanded by the ECM?

[ab8127542]

No, bad checksum will not brink an ECM, at least not OBD1 ECMs.

No, checksum is only updated when the bin is saved. This is why checksum needs to be disabled during emulation.

So are you saying that it runs on base timing, but not when timing is being commanded by the ECM?

Correct. that's what I believe is occuring. Where I'm getting confused is this happens regardless of what bin you use. Even a factory unmodified bin that never hits tunerpro, just straight to the prom, gets you a flickering light.

Same with emulation. The one exception; in beginning an emulation session, disabling checksum gets you no CEL, but what I perceive as the base timing only issue. With the flickering light, you don't even get the stumble.

I've got WB02 wired in, otherwise a fairly solid/stock wiring harness throughout the car. I would blame my chip burner, seeing as how you get the issue bypassing TP, but I can't get through with emulation either.

Possible electrical? what would (if anything) invoke this ECM behavior if it electrical and not in the bin/hardware?

[1project2many]

First test, and best. Key off for 30 seconds or more. Then turn key on but do not start car. CEL shoould light for 5-10 seconds, turn off for several seconds, then turn on and stay on. If this does not happen then you shouldn't bother trying to start the engine. This test indicates the PCM is able to execute code, the code is working, and the checksum is not incorrect (or engineering mode is active). If the light behaves as expected you should stop chasing checksum/bin/ecm issues.

for what it's worth, it's a 1989 Corsica hatchback. Five speed swap, LG5 turbo. LS springs, roller rockers and it's got a three-bar map in it. '730.

For my own curiousity, did you modify anything in code for the 3 BAR MAP? Using 3 BAR MAP with an unmodified 2 BAR calibration can produce bad results such is vastly incorrect timing and fuel values for the engine.

[ab8127542]

Apologize for the gap in time, I've been away for the Easter holiday..

I've gotten back at it, got the noid light set out. I get one flash of the noid light whenever you first turn the key on and crank. Injectors then have no pulse. I unplugged the injector harness at the back of the upper intake, and ran the noid light pre-injectors via a little engineering. Same result, one quick flash, nothing else there after. This points to a wiring issue, no?

I'm going to get out there again first thing in the a.m., start checking the harness over, with the multimeter. Its a healthy harness, and I see no breaks or shorts. I guess I'm not convinced it's still not in the .bin I'm running

[ab8127542]

First test, and best. Key off for 30 seconds or more. Then turn key on but do not start car. CEL shoould light for 5-10 seconds, turn off for several seconds, then turn on and stay on. If this does not happen then you shouldn't bother trying to start the engine. This test indicates the PCM is able to execute code, the code is working, and the checksum is not incorrect (or engineering mode is active). If the light behaves as expected you should stop chasing checksum/bin/ecm issues.



For my own curiousity, did you modify anything in code for the 3 BAR MAP? Using 3 BAR MAP with an unmodified 2 BAR calibration can produce bad results such is vastly incorrect timing and fuel values for the engine.

I would put the appropriate map sensor with the appropriate tune. My connector is modified to fit all maps.

[ab8127542]

Update. Strong voltage at the injectors, no short to grounds I can find.

Also, I discovered when you crank it for extended periods of time, every 5 or 6 seconds you'll get one injector pulse, this is straight from the harness, injectors disconnected. When you test it through the injector connectors themselves, same result. They're just not getting decent signal from the ECM.

Before I throw the ICM and CPS under the bus, not only are they both brand new, well fairly new, but I replaced the ICM with a known good one with the same results. And I'm getting RPM readings on the dash and through tunerpro, I'm just not getting injector signal.

On that note:

These past two days I've noticed something new, I simply cannot get my data stream working correctly. It connects and then disconnects endlessly, but when it connects you get a few seconds of data that seems to be correct. I've triple checked my tunerpro settings, my plug, connections in USB locations. It starts with an error 1 on tuner pro and will literally climb into the thousands cycling in and out of data.

Im still entertaining the idea of a bad part or wiring issue, but I am just convinced it's got to be something in the tune I cannot find any other issue, and I'm running out of things to test

[Six_Shooter]

Have you tried disconnecting the TPS on an engine start attempt?