S70 DTC P1671 Driver 4 Line 1

nikolayy · Post by **nikolayy** » 05 Jul 2007, 21:37

My check engine light is on like 3-4 days so i went to car repair shop to check the car (volvo s 70).....the code is P1671
So far this is the info i found:DTC P1671 Driver 4 Line 1
No idea what means
If somebody can help me understand what this mean

Post by **Ozark Lee** » 06 Jul 2007, 05:54

That is an ECU data line error. Does the car run OK?

If so, clear the code and see if it comes back.

If the car doesn't run or shift properly it is either a wire to the ECU or the ECU itself.

...Lee

deaster2 · Post by **deaster2** » 06 Jul 2007, 11:46

nikolayy wrote:My check engine light is on like 3-4 days so i went to car repair shop to check the car (volvo s 70).....the code is P1671
So far this is the info i found:DTC P1671 Driver 4 Line 1
No idea what means
If somebody can help me understand what this mean

Code Make Description
P1671 Volvo CMP Actuator Performance Problem Or Signal Out Of Range
CMP=Camshaft Position
First thing to check would be the camshaft position sensor,
connections and wiring...

nikolayy · Post by **nikolayy** » 06 Jul 2007, 20:50

Thanks guys for the replay.......
The car run fine..the only think is when i am slowing down and then accelerating i feel something like is skipping one gear or something.....
Today i disconnect the battery for half hour the check engine light was off but in 13miles of driving came back on......
this is so far
thanks again

Post by **Ozark Lee** » 06 Jul 2007, 21:33

I will certainly defer to Deaster2. I am out of the city and many of my resources are not available to me. I don't have VADIS at my fingertips hence little information on a S-70.

I looked up the code in the 850 manual and it does not exist. All codes around it pointed to the data error or ECU error. The generic P code lookup pointed to the same.

...Lee

nikolayy · Post by **nikolayy** » 06 Jul 2007, 23:01

By the way the exact info from the repair papers is

ENGINE CODE IS 1671..MANUFACTURE CONTROLLED COMPUTER OUTPUT CIRCUT. RECOMMENDED DEALER

I just found the same number (1671) with P in front of the code

And just 1 more thing, the car idle at 900 r/min....i think it should be 800 r/min ............ it might be part of the problem
Is all that big issue....can i drive the car or i should go to the DEALER

deaster2 · Post by **deaster2** » 09 Jul 2007, 12:08

nikolayy wrote:By the way the exact info from the repair papers is

ENGINE CODE IS 1671..MANUFACTURE CONTROLLED COMPUTER OUTPUT CIRCUT. RECOMMENDED DEALER

I just found the same number (1671) with P in front of the code

On July 2nd, I got a massive update to my Genisys pc-based software as well as new firmware for the OBDII scanner. I rechecked the P1671 code...same results as in my first post.
I called the Genisys help desk and talked to a tech by the name of Brad...who assured me this was the correct info for the Volvo specific DTC P1671. Still not convinced, a friend, that uses the Snap-On OBDII scanner, looked the code up on his scanner. The Snap-On definition is:
P1671 1998 S70 Volvo Manufacturer Control Auxiallary Input/Output(1998 was the earliest S70 Volvo the scanner had),
which matches what nikolayy found. A note - Snap-On says that P1671 is a Generic code, while Genisys says it's a Volvo specific code which may be the difference.
It is very possible that my Genisys system is wrong, even though I've been assured that it isn't. I can say that in the two years I've been using it, it has always lead me to the problem with sensors, actuators and modules.
EDIT:
I just found out there IS a General Motors Generic DTC P1671
which matches the Snap-On scanner and what nikolayy found.
The Volvo specific code P1671 matches what my Genisys software displayed.(CMP Actuator)

Ozark Lee, by all means jump in, two heads are always better than one...I have found that to be true when dealing with car problems.

Post by **Ozark Lee** » 09 Jul 2007, 13:32

OK,

I started poking around in VADIS and I cannot find a listing for that code on other than the 2000 model year. It is a fault in the camshaft reset valve. It is also called the Variable Valve Timing (VVT) valve.

When this condition is encountered the ECU disables the variable valve timing and sets the CEL.

The listed symptoms are an uneven idle and the CEL illuminated.

VADIS lists a part number of 1275578 for the valve and 30731212 for the gasket.

It is a very simple repair. The procedure is to remove the upper timing belt cover. Locate the valve, it is located directly above the exhaust camshaft, behind the exhaust cam sprocket, on the top of the upper camshaft housing. It is held in with 4 bolts and has a single electrical connector.

Remove the 4 bolts, remove the old gasket, clean the mating surface and any residual oil in the channels below the valve.

Replace the gasket, replace the valve and tighten the bolts to 10 N/m.

Attach the electrical connector and replace the upper timing belt cover.

...Lee

deaster2 · Post by **deaster2** » 09 Jul 2007, 15:20

Ozark Lee wrote:OK,

I started poking around in VADIS and I cannot find a listing for that code on other than the 2000 model year. It is a fault in the camshaft reset valve. It is also called the Variable Valve Timing (VVT) valve.

When this condition is encountered the ECU disables the variable valve timing and sets the CEL.

The listed symptoms are an uneven idle and the CEL illuminated.

VADIS lists a part number of 1275578 for the valve and 30731212 for the gasket.

It is a very simple repair. The procedure is to remove the upper timing belt cover. Locate the valve, it is located directly above the exhaust camshaft, behind the exhaust cam sprocket, on the top of the upper camshaft housing. It is held in with 4 bolts and has a single electrical connector.

Remove the 4 bolts, remove the old gasket, clean the mating surface and any residual oil in the channels below the valve.

Replace the gasket, replace the valve and tighten the bolts to 10 N/m.

Attach the electrical connector and replace the upper timing belt cover.

...Lee

Your research makes sense...I have learned something from this experience, and hopefully, nikolayy's problem solved...