Boxersix
06-10-2010, 12:53 AM
Eg still swapped in the WRX and running great. I've had Vss2 input disconnected while trying to diag cluster issues way back and never got around to hooking it up. Code #33 is constantly active as a result.
I thought this caused the ECU to pull some timing from the range, and a member on another forum brought it to light yet again tonight while talking about the motor and electricals.. True???, and to what extent of timing draw are we talking? I noticed I can run 87 without ping now, lolz
Now going back to hook it up, Connector B60, pin #11. Voltage chart say it's either has zero OR 5 volts when either key on, engine off or running .
Is this truly looking for an all or nothing voltage signal, or should that on the FSM chart the typical sensor range of 0 to 5 volts?
So basically, should I tap this into the WRX VSS output wire, or just leave it axed as it is now.
also........My JECS PCM is only throwing that one code #33, even though I have no EGR, no EGR temp, no purge solenoid, ETc, etc. No codes for any of those stored in memory...just curious if that's normal....doesn't seem like it is...
I thought this caused the ECU to pull some timing from the range, and a member on another forum brought it to light yet again tonight while talking about the motor and electricals.. True???, and to what extent of timing draw are we talking? I noticed I can run 87 without ping now, lolz
Now going back to hook it up, Connector B60, pin #11. Voltage chart say it's either has zero OR 5 volts when either key on, engine off or running .
Is this truly looking for an all or nothing voltage signal, or should that on the FSM chart the typical sensor range of 0 to 5 volts?
So basically, should I tap this into the WRX VSS output wire, or just leave it axed as it is now.
also........My JECS PCM is only throwing that one code #33, even though I have no EGR, no EGR temp, no purge solenoid, ETc, etc. No codes for any of those stored in memory...just curious if that's normal....doesn't seem like it is...