I'm having a strange problem with a new EEPROM that I'm using with a 2timer. I have the 2timer connected to a toggle switch, which is connected to an ECU ground.

If I leave the circuit open, the car will start with no problems. However, when the 2timer is grounded, the shift lock solenoid goes berserk (Yes, I know, it's an auto...). It intermittently receives current, and I hear a rapid "clicking" noise (that's characteristic of a solenoid). Today, I tried starting the car with the 2timer grounded, and it seemed to work fine. The solenoid was still going berserk, but the car started up immediately and idled fine. Therefore, it seems that the chip works, but something is intermittently cutting power to the solenoid. I had this problem before when there was a short in my datalogging cable, but that has been fixed. As of now, the datalogging cable is removed, and the problem remains.

The potential difference between the the ground pin on the chip and the ECU ground I used is negligibly low, so I strongly doubt that it's the issue. Just in case, I grounded the terminal on the switch to the chassis, and it made no difference. I have both the top cover and bottom cover off of the ECU, and it makes no difference. I've also probed all my connections with a multimeter, and I can't find any shorts.

I hooked an oscilloscope to the connector for the shift-lock solenoid. When the 2timer isn't grounded, it sees a constant 12V signal. However, when it is grounded, I see a square wave on the scope with a peak-peak voltage drop of 1V and a period of 40ms. I have no idea of why this is happening.

Has anybody experienced anything like this before? Any suggestions?

My setup is as follows:
- d15b7 block, d16z6 head
- 5th gen DX slushbox...
- p28 ECU with a datalogging header and switches for J1, J12, and the 2timer
- EEPROM has OEM p28 and p06 maps with checksum removed and datalogging added (I can't verify this though)

Thanks,

Dan

 

I'm guessing from the fact that you cannot verify your ROMs. That you are also unable to burn new ROMs to the EEPROM? Sounds kind of like you are having a ROM problem. Is your CEL on?

I had one of my ROMs do something similar to this once. I'm not sure what it was in the end because all I did to make it go away was burn a new ROM to my EEPROM chip. Made sure everything was removed and turned off/on as I wanted it and it worked.

 

Yep. I broke down and bought a chip burner, but I won't get it until the end of the week. Did you have the issue with an auto ECU?

Also, my CEL is off for both cases.