Baffling problem....My C5 can't be fixed?!?
Or is it more of a time thing....and changes. Sometimes at 175..sometimes at 190 etc? Things happen at certain temps. If you can correlate this code to a specific temp it may help you. Certain function or monitorings are activated at certain intervals...sometimes its temperature the computer looks for before it brings other sensors online.
Does the car exibit any secondary symptoms beside the code? Backfiring? Shuts down?Why cant you drive it? If its just getting a code? So it must be having secondary symptoms?
Why did you check the cam position signal if the code is for crank position signal?
Did you check and clean all grounds? Many times when a symptom or failure is associated with a specific temp...but not correlated to a computers function of that temp...it can be ground related. Increased temps will increase resisitance across a ground. Especially on grounds that are on the block or cylinder heads. As the engine warms...the grounds "move" and increase resistance.
I would take EVERY ground off that car...take them apart, clean the contacts and the mount surface and reattach.
I was going to say check the crank thrust bearing but you already did. I chased that one around for a month on one of my cars.
Some of these questions may seem out in left field...but its hard for you to include ALL the info thats pertinant. So if you can answer these questions...maybe others can help more.
Good luck!
Here's hoping you figure it out.
1) check to see what else happens at 185deg that can mess up a sensor. Does a cooling fan come on? Does a relay set??? If so, then....
2) look into the engine harness. There may likely be some damage to it that is messing with sensor outputs when other components become active.
Another thing. Was anything done to the car just before this problem started?
I'm confused as to why you are getting a crank sensor code for the cam sensor going nuts, unless the PCM is comparing the two and the bad cam sensor is what is setting the code.
Have you checked cam end play? I have seen this on GM diesels(not that they are the same, just as an example)
Trending Topics
The Best V8 Stories One Small Block at Time
) or a schematic for one, but if it operates anything like I'm familiar with it should go something like this:
In operation, the supply voltage powers the detector and supplies bias and a current source to the emitter of the transistor. The detector senses the position of the camshaft, and at the appropriate interval supplies a trigger pulse to the base of the transistor. When this happens it biases the transistor so that it opens (a transistor is basically just a small electronic switch), supplying the output signal. When the trigger pulse is absent, the transistor is closed and no current flows.
If the sensor itself has been replaced as you said, you can rule that out. This leaves us with the possibility of a problem with the supply voltage, the supply voltage line, the output signal line, or the PCM itself.
As was stated previously, the first thing to do is to check and clean all your grounds. Bad grounds can cause all kinds of crazy **** you wouldn't expect. If that doesn't help, beg/borrow/steal a PCM to swap with yours and see if that has any effect at all. Do these two steps first, as they are the easiest and quickest to accomplish. No sense in digging around in the wiring if you don't have to. If none of these resolve the issue, it's time to start proubleshooting the electronics.
First, put that O-scope on the supply voltage line to the CPS to see what happens to the supply voltage when the output signal takes a ****. Now, electronics is a two way street, so if you see the supply voltage do crazy stuff that doesn't necessarily mean there's a problem with it, as a problem on the output line can most certainly feed back through and effect the supply voltage. I don't know what kind of O-scope W2W is using, but if they have a decent 2-channel digital one that can do logs, you can hook one lead to the supply line and one to the output line. That way if there is some funkyness on the supply line when the output goes nuts, you can go back to the log, crank the Time/DIV on the scope way down, and possibly see which signal freaks out first.
You're also going to want to make some resistance checks with a multimeter, both cold and at temp where the problem is occuring, and compare the readings (so write them down). You'll want to measure from each individual line (supply and output) to ground, to any adjacent lines in the wiring loom, and to any adjacent pins on the connector to the PCM (you'll need a pin-out for this). All these measurements should be open, or a very high resistance value. A short or a low resistance value would indicate a problem, i.e. a short from line to ground or from line to another line in the loom. These values should not change from cold to hot.
Between all these steps, that should cover about 95% of the possible problems, if not more. Check the grounds and try a different PCM. Check the supply voltage. Take those resistance readings. Let me know the results, and I can guide you further.
If all else fails, I'd say just replace the wiring harness period. Any problems there should be identified using the outlined procedures, but better safe than sorry.
When you hooked the BS3 up, did it completely eliminate the the PCM and all associated wiring? Never had the opportunity to play with one, so you'll have to clue me in on that one.
A bad ground can cause a seemingly unrelated circuit to backfeed another. Like when my stoplights illuminated my dashboard when I stepped on the brake in my C5.
A bad ground in the rear of the car caused the stoplights to ground through the dashlights.Check all grounding points, ground wires and GROUNDING STRAPS! A ground strap could also be missing! And in a C5 where so much is non-conductive that could lead to a floating ground.
One further tip is to realize that a circuit under no current load may show JUST FINE with a DVM resistence check. But could certainly still fault under a current load. GOOD LUCK!
Last edited by cantdrv65; Jun 14, 2007 at 07:47 PM.
Mike






