What causes a bad connection?
My CPU keeps saying "connections to sensor 2 are poor or bad"
I checked all the connections and they are fine. I dont know what wrong with it.
What causes a bad connection?
My CPU keeps saying "connections to sensor 2 are poor or bad"
I checked all the connections and they are fine. I dont know what wrong with it.
Is this a new install?
Disconnect the sensors from the CPU and check the RJ11 heads - I noticed that one of mine were fused together which caused one of the copper wires inside to not gain contact. Simply separating it with my fingernail fixed it. This was only on my initial install, though.
Can you take any HD pictures of the CPU ports (without anything plugged into them), and the RJ11 connectors for those two diodes?
my CPU makes me install the heads into ports 2 and 3 for the front Dual, and 1 and 4 for the rear. Are you putting them into the correct ports?
I really have no idea if they are plugged in correctly. They are all on front.
And for some reason, it stopped sending an error message so i dont know why it did that.
But I bought the unit used from a member of this site, so im sure it wasnt abused.
Who did the install?!?
As aa203 said, check the heads are plugged in the right ports. Was it working before?
The cpu is probably programmed for a different port
I did the install and yeah they all have been working.
I turned the car on again and no alert, so I guess it fixed itself.
Keep an eyeball on it. If it comes up again, contact Cliff. You might need a replacement head sensor
He already saw this thread and emailed me.
As always, on top of the game lol
I believe the LI is sensitive to voltage drops during the car's startup. When you are cranking there is a ton of load on the battery, so it's not uncommon for voltage to drop down below 12V for a bit. Presumably, the startup sequence on the LI uses a bit more power than just normal "idle."
I've noticed times where it will tell me a sensor connection is bad when I start the car. If I power it off then back on once the car is running (and not cranking), I get no more indications of problems.
If they could somehow program in a brief delay (maybe 1-2 seconds) in the startup to allow for voltage drop during cranking, I'm guessing we'd hear less "sensors are bad" errors around here... my hunch is that nothing at all is wrong, it's just the CPU being paranoid because it didn't get the expected response from the sensor instantly. If it doesn't have enough voltage on the wire, it's understandable that it would have problems seeing the sensor(s).
Bookmarks