• The site migration is complete! Hopefully everything transferred properly from the multiple decades old software we were using before. If you notice any issues please let me know, thanks! Also, I'm still working on things like chatbox, etc so hopefully those will be working in the next week or two.

Northstar TPS sensor part number?

But it doesn't feel like it's spring loaded like a l67 one when I move it, it doesn't retract it's like free floating

Sent from my SM-G920V using Tapatalk
 


cb0badffd2e735b408bde44866254b0d.jpg


The part in the middle that hooks to the shaft on the throttle body is that spring loaded? Cuz mines not wondering if the springs broke or something

Sent from my SM-G920V using Tapatalk
 


Okay is it all sloppy too? When you move it with your finger doesn't it stay where you moved it?

Sent from my SM-G920V using Tapatalk
 




far more often im finding intermittent issues on terminals/conn's

the N*/lsx newer TPS's are internally floating (to self compensate for aaxial centerline alignment issues, it doesn't need a sporing, its the shaft that's sprung.

gm made it more idiot proof than the old style tps's like the L67, which is basically similar to the design for early efi TPS's from back in the 80's

problem is people still installed em wrong, so they dumbed it down a bit and saved $ at the same time.

backprobe the tps and drivbe till it faults and see if the 5v drops out, then backprobe at the PCM and retest, if its wiring the pcm will see it but the tps conn probing wouldn't. if its the sensor, then both would show the same signal glitch
 
Turbocharged400sbc said:
far more often im finding intermittent issues on terminals/conn's

the N*/lsx newer TPS's are internally floating (to self compensate for aaxial centerline alignment issues, it doesn't need a sporing, its the shaft that's sprung.

gm made it more idiot proof than the old style tps's like the L67, which is basically similar to the design for early efi TPS's from back in the 80's

problem is people still installed em wrong, so they dumbed it down a bit and saved $ at the same time.

backprobe the tps and drivbe till it faults and see if the 5v drops out, then backprobe at the PCM and retest, if its wiring the pcm will see it but the tps conn probing wouldn't. if its the sensor, then both would show the same signal glitch
Click to expand...
Thanks for the info my map sensor is reading all messed up so I ordered a new one i read online that the TPS could act up if it's not agreeing with the map sensor so I hope this fixes it. I just put a used 2 bar map on and didn't know if it worked and apparently it doesn't the reason why I put one on is because zzp had me set up on a single bar map when I top swapped. Scotty set me up with a gtp bin and we have been tuning then this started happening. Also I do have a mechanical autometer boost/vacuum gauge plumbed right between the LIM and map sensor that reads correctly.

Sent from my SM-G920V using Tapatalk
 
Last edited:
Be careful how you Plumb your boost gauge I would not recommend off of the map sensor as the additional volume of air that must be moved during manifold air pressure changes is large enough to slow down and f***** up the map Reading speed.
Temporarily remove it n retest
 
It read vacuum fine with the single bar map on my aeroforce just stopped at 0 because it was a single bar.

Sent from my SM-G920V using Tapatalk
 
You must log in or register to reply here.
Back
Top