VSS killed itself?

[1BadAction]

Your first post said emulator, sometimes things go bad there, just takes a restart, upload verify and emulate to make it right.

I've never had an ECM/PCM go bad and never got a bad one from JY, so I can't comment on new ones. VSS would be a more likely suspect.

Yes, it was during emulation... When I parked it, it was running like crap, throwing codes, not responding to anything. So last night I checked fuses, then uninstalled everything and put the computer back to stock. It wouldn't even start and run in limp home. Codes wouldn't clear, no response at all.

if you look in my previous posts, I had the same thing happen to me a few weeks ago. 7060/80E 454. speedo still worked, trans didn't shift.
http://www.gearhead-efi.com/Fuel-Inj...ll=1#post20340

Durning my tuning and programming with my burn 2, I ended up somehow loosing VSS. I also had a code 51 which EagleMark had showed me (it had been there awhile). And I still have this weird datastream glitch.

During this extremely frustrating day of tuning, I could not get the VSS signal back by programming. I thought it was just a flash error because how could it just all of a sudden loose the VSS?

Local autozone had the computer for $99 instock. Snagged it, installed my G3 and flashed a new chip. Bingo, Everything works again.

For some reason I still have my doubts that it was the computer for sure.....but the reman computer did fix my issue so IDK WTF.

This is really really odd that you have the same issue as I just had with the same setup....although you're emulating.

Very strange we've had the same problem, indeed. I wonder if it's just the old electronics? I'll see what I can find locally. I did pull the pcm so I'd have a core.

Hopefully it's not the EEPROM

[EagleMark]

It can't be the EEPROM during emulation and everything you said above is a sure sign something happened to emulator. SOmetimes it just happens, you need to learn the signs like above. Reload the bin to TunerPRo, Upload to emulator, Verify, Emulate, turn key on and should come on, blink and stay on till started.

Did you set Mask ID to AA to disable checksum?

[1BadAction]

It can't be the EEPROM during emulation and everything you said above is a sure sign something happened to emulator. SOmetimes it just happens, you need to learn the signs like above. Reload the bin to TunerPRo, Upload to emulator, Verify, Emulate, turn key on and should come on, blink and stay on till started.

Did you set Mask ID to AA to disable checksum?

Yes, I agree, but to diagnose it, I took out the G1, installed the stock prom, and tried it that way. Wouldn't even start. I set the PCM into limp home a couple times when emulating. I just shut everything down, waited 30 seconds, then started it back up seemed fine until right before I stopped messing with it last saturday.

That explains why it would still run (albeit setting tons of codes) while emulating, but wouldn't run at all when I put the PCM back to stock. Sounds like it's the eeprom itself and not actually the PCM that is the problem.

How do I set the mask ID? That should fix the issue with emulating. I think the killed PCM was my own ham-fisted fault...

[EagleMark]

Open Mask ID and change from 85 to AA.

You probably have a error 51 Prom Failed set in PCM, clear codes and try again. If 51 is set it won't run right even if you fixed the issue until codes are cleared. Emulating without AA sets error 51.

Whenever I hook up to data first thing I check is Error codes.

[1BadAction]

The computer holds that code even though it's physically unplugged?

[EagleMark]

It will clear if unplugged/power removed. But if you emulate without AA it could set real fast again. Testing is cheap compared to a new PCM...

Open your bin, save your bin as TP will calculate checksum, then change mask ID to AA, save bin, then do the upload, verify etc...

[1BadAction]

It will clear if unplugged/power removed. But if you emulate without AA it could set real fast again. Testing is cheap compared to a new PCM...

Open your bin, save your bin as TP will calculate checksum, then change mask ID to AA, save bin, then do the upload, verify etc...

I had the PCM unplugged when I swapped to the stock EEPROM. Still a bunch of error codes.

I can't find where to change mask ID. It's not in scalars, is that where I should be looking?