Runboard.com
You're welcome.
Australian X-Trail Website Members Rides

Site Search

Facebook Aussie Forum Website Twitter Aussie Forum Website YouTube Aussie Forum Website Flickr PhotoBucket MSN Messenger Skype RSS Feed Events Calendar Admin Mailbox Nissan Australia myNissan Capped Service Fuel Consumption Monitor Tyre Size Calculator Australian X-TRAIL Forum Live Chat

Forum Rules   
   Register for a free global account (learn about it) | LOG IN: globally (click here) (Lost Password?)


 
togadog Profile
Live feed
Blog
Friends
Miscellaneous info

X-TRAIL NEWBIE
 

Back To Top

Date Registered: 08-2017
TOTAL POSTS: 2
Reply | QUOTE
once again, Cam and Crank sensor issue, need help before my daughter gets killed in this car


hi fellow members,

I have the 2003 T30 x-trail TI. I have just had the engine redone, new head gasket,full head reco, all timing chains etc etc, and double and triple checked chain position etc. Replaced both cam and crank sensors as was getting the error codes, and then cleared the codes.

The car now drives a few days, smooth as silk, completely 100% like when it was [sign in to see URL] every few days, driving along, it just cuts out and again throws the cam and crank sensor error [sign in to see URL] starts up again straight away and drives on as if nothing happenned, but now has the code each [sign in to see URL] clear them, and get another week or so driving before it happens again.

I have brand new nissan OEM genuine sensors in the [sign in to see URL] somebody found an issue with the new sensors being sold in places like ebay ?

I have a feeling the car is throwing the code at a particular rev range, so will be driving it myself for a while to try and replicate it again, but since this is such a generic issue world wide, can somebody please advise what else could be doing this? could it be bad connectors in the harness? a hairline break or dry joint somewhere between the sensors and ECU ???? it is just downright dangerous for my 17 year old daughter to keep driving [sign in to see URL] someone at nissan has recognised this as a generic fault by now?? must be a paper on it somewhere ???? HELP PLEASE TEAM !!!!
28/Dec/2017, 8:59 pm Link to this post Send Email PM   Send Private Message Blog
 
glugglug Profile
Live feed
Blog
Friends
Miscellaneous info

X-TRAIL NEWBIE
 

Back To Top

Date Registered: 04-2011
Location: Brisbane
TOTAL POSTS: 9
Reply | QUOTE
Re: once again, Cam and Crank sensor issue, need help before my daughter gets killed in this car


Let me add my story to the list and see if we can highlight any similarities.

Mine intermittently goes into limp mode too. It can be up to 6months between bouts and then it will wig out sometimes only once, sometimes 2-3 times a day for a week then be good again for months.
It doesn't log codes for the sensors anymore either, just throws the check engine light goes to limp mode. I cant pinpoint the exact conditions that make it happen and i'm not able to force it to happen either.
Three situations have lined up with the fault more often though.

-It goes into limp when getting back on the throttle after downshifting and using the engine to slow me through a corner
-Cruising down the highway holding constant light throttle for longer than 20mins
-There was also a period of about 3 weeks last year when every time I set speed with the Cruise Control it would instantly throw the engine light and go limp. No new codes or codes at all then either.

I can generally clutch in, turn off the key and then turn it back on and let it clutch it's self back to life and keep on going with little worry but very occasionally it goes into limp mode at the lights and you have to restart it or crawl round the corner at walking pace and then do the manual hard reset of the computer with the key and pumping the pedal.

Because it won't hold codes or even keep the engine light on most places think i'm making it up.

I had a wild idea last year when the cruise was playing games that it may have been related to the drive by wire, not the cam sensors.
Either dirty potentiometer in the pedal or a bad solder joint in the aftermarket cruise wiring that was shoved up under the dash like an electronic rats nest. (Nissan tells me all T30's had cruise fitted here at the port even if optioned)
So I pulled it all down and re-soldered every connection into the factory loom. I also found details online of how to disassemble, clean and re-initiate the throttle pedal but thought I'd do one job at a time so I could pin point the fault if it was Cruise or Pedal.
Well re-soldering got me from August 2017 until January 2018 without issue and I dared to hope it was fixed.
Then it died last night, which is why i'm back here reading through all the posts again before I attempt to clean the Throttle Pedal switches this weekend. I'll keep you posted.

Heres a link to the Throttle Position Sensor Cleaning guide for those interested. I only have printouts of the relearn procedure though sorry.
[url][sign in to see URL]


---
2003 ST, manual
12/Jan/2018, 10:52 am Link to this post Send Email PM   Send Private Message Blog
 
PGW Profile
Live feed
Blog
Friends
Miscellaneous info

X-TRAIL NEWBIE
 

Back To Top

Date Registered: 06-2018
TOTAL POSTS: 2
Reply | QUOTE
Re: once again, Cam and Crank sensor issue, need help before my daughter gets killed in this car


Hi
I seem to have a similar problem, but I don't get any fault lights!?
My 2005 X-Trail Ti, manual, Petrol (150,000 km) loses all ignition on all cylinders for 0.5 to 5 seconds before kicking back in again with full power.
It does this after about 30 minutes of highway driving. It only does it one in about every 4-8 trips on the highway.
Once it starts, it continues to stutter for the rest of the trip even if I stop briefly. The stuttering continues no matter whether I change down gear or slow to 60 kphr.
It occurs whether I am in cruise control or not. Fault lights do not come up. It does not go into Limp Mode at anytime. (i.e. no faults / codes so never need to reset)
The problem never causes the car to slow to less than ~ 70 kph but the cut-out and kick-in of power is very unpleasant to drive.
Once the stuttering starts, It continues to stutter until I stop and let the engine cool down. There are no engine fault lights at any time.
It feels like complete loss of ignition on all cylinders for a second or 2. There are no other signs of electrical faults. The lights and instruments do not dim or flicker when this occurs.
The problem can occur during any weather conditions i.e. hot, cold, wet or dry condition, day or night. Apart from this it runs very smoothly, idles well, never stalls, starts easily 1st time every time ... even immediately after I stop and restart on the side of the highway during a stuttering event.
It always runs well when I leave it at the Nissan service centre and they have not experienced the fault and cannot find any problems.
The injectors have been cleaned, compression is excellent, fuel lines checked, computer re-booted. The catalytic converter was changed recently after the Check engine code light came up. It was not stuttering when the Cat Converter fault came up.
The stuttering is still occurring after the Cat converter was changed.
Is it possible to have cam or crank sensor problem or oxygen sensor causing this behaviour but without the fault light coming up ?
This has been occurring for 18 months now with no change in frequency or severity! Can anyone please help?
Regards, Paul

24/Jun/2018, 10:05 pm Link to this post Send Email PM   Send Private Message Blog
 
Revhead Kev Profile
Live feed
Blog
Friends
Miscellaneous info

X-TRAIL HOLIC
 

Back To Top
Premium


Date Registered: 10-2006
Location: Mona Vale, Sydney, AUSTRALIA
TOTAL POSTS: 5285
Reply | QUOTE
Re: once again, Cam and Crank sensor issue, need help before my daughter gets killed in this car


Hi Paul,

The way the Nissan ECU logs fault codes seems to allow intermittent faults to occur without throwing an engine code and illuminating the light. This seems to happen with the cam and crank sensors due to the tolerance between the sensors and the teeth they sense, sometimes causing the fault and then allowing it to operate normally.

The sensors are relatively cheap and easy to swap yourself with basic socket and screwdriver tools and will be an easy way to rule them out as a cause of your problems.

---
Kev X450(c) T30 Guru
03 Titanium Ti T30 Series 1 **MODIFIED**
My Blog
My CarPC Worklog
25/Jun/2018, 5:47 pm Link to this post Send Email PM   Send Private Message Blog
 
ahto42 Profile
Live feed
Blog
Friends
Miscellaneous info



Back To Top

Date Registered: 06-2012
Location: Estonia
TOTAL POSTS: 42
Reply | QUOTE
Re:


My guess is streched chain, because there is no code for it.
 The cam and crank signals are too far away from each other. Can be tested with a 2 channel scope(Pico). I know that 2ms makes a difference. At my brothers shop was a diesel x-trail with cam/crank fault. From my working engine we took the first measurment and after that we compared the results. I know that my chain had over 200k kilometers in it, but the no runner was 2ms behind from mine. Worth checking first.


---
Member id X-2451
Name: Ahto
Location: Estona, Tartu

Model: T31 II 2012 Diesel Auto, LE
23/Jul/2018, 6:53 pm Link to this post Send Email PM   Send Private Message Blog
 
Revhead Kev Profile
Live feed
Blog
Friends
Miscellaneous info

X-TRAIL HOLIC
 

Back To Top
Premium


Date Registered: 10-2006
Location: Mona Vale, Sydney, AUSTRALIA
TOTAL POSTS: 5285
Reply | QUOTE
Re: once again, Cam and Crank sensor issue, need help before my daughter gets killed in this car


A stretched timing chain is usually also indicated by general all-over power loss and increase in fuel consumption as the "stretch" in the chain caused by worn links causes the phasing between inlet cams, exhaust cams and piston position to be slightly out. The engine runs but not to its optimum.

---
Kev X450(c) T30 Guru
03 Titanium Ti T30 Series 1 **MODIFIED**
My Blog
My CarPC Worklog
27/Jul/2018, 12:00 pm Link to this post Send Email PM   Send Private Message Blog
 


Reply





You are not logged in (login)

forum sticker
Back to top Back to top

Back to top

<-- end container -->