nanocom faults
So my newly acquired D2 was sold to me with the 3 amigos.
My Nanocom arrived from Cyprus and I'm trying to decipher the faults.
I'm getting three errors:
1. Shuttle valve electrical switch fault.
2. Signal invalid fault is currently present fault determined as persistent fault does not cause the mil lamp activation
3. P1000=vehicle speed signal error drive cycle B occurred 1 times. Signal fault invalid. Fault currently present
I tried to clear faults with the nanocom but the 3 amigos still remain. Can anyone tell me what these faults mean? Am I to assume that the lights remain on as it is a persistent fault not intermittent and I will need to do a electrical shuttle valve repair? I'm not sure what the other two faults mean and if soldering the shuttle valve circuit board terminals with fix all the problems. I am not a mechanic but pretty good at DIY taking things part and reassembling things.
Great little machine the nanocom by the way.
nanocom faults
Hey buddy. Haven't used the.nanocom myself. But I have got a absamigo. Which only does the slabs ecu. I had the same fault. I got shuttle valve electric fail. It's an easy fix. There is a link with very detailed instructions. There is two or three options to fix it. From memory, the shuttle valve sensor switch is the issue, not the valve itself. So, you bypass it entirely. It still allows the valve to operate normally. But disables it from sending faults to the ecu. I did it to mine and haven't had the same fault since. Now its just yet another low output fault. lol
I'll try find the kink, but if you just google it, it was pretty east to find. I think I googled the error code and fix. 114 : shuttle valve electric fail
Sent from my HTC One XL using Tapatalk 2
Edit, just did a search. If you google "abs mod" its the first link. That's what I used to fix mine.
http://www.landroverclubvi.com/abs-mod.html
Credit to land rover club virgin islands.
Sent from my HTC One XL using Tapatalk 2
thanks. anyone know what the other two faults mean? They sound more sinister.
Instead of running off overseas,,
why not have a look in our very own GOOD OIL forum?
You may find the solution to all your problems,,
if not its still a good read,,
(and its as easy as clicking the blue line in my sig)
"How long since you've visited The Good Oil?"
'93 V8 Rossi
'97 to '07. sold.![]()
'01 V8 D2
'06 to 10. written off.
'03 4.6 V8 HSE D2a with Tornado ECM
'10 to '21
'16.5 RRS SDV8
'21 to Infinity and Beyond!
1988 Isuzu Bus. V10 15L NA Diesel
Home is where you park it..
[IMG][/IMG]
I've moved the thread to Electronic Diagnosis as you'll get more answers in this forum.
Best way to report faults is to save the faults to SDCard. The saved file is a plain text file that includes all the details. You can do this by touching the disk icon at the bottom of the faults screen before you clear the codes.
Based on what you have posted:
1) 11-5 can be a number of things. It is possible the cracked solder joint described in the VI Land Rover Club link above, but can also be caused by leaking modulator valve seals which cause brake fluid contamination of the Shuttle Valve Switch.
2) You haven't included the code or description of what system is effected. If you can post those we might be able to shed some light.
3) The P1000 fault seems to be a variant of P501. It's possible that fixing the SVS fault will solve this issue but when I've seen this type of fault before it is always related to wheel sensor faults.
(PDF attached)P0501: Vehicle speed sensor signal error Drive cycle B:Signal implausible.
I'd suggest you find a copy of the RAVE CD, as the Electrical Library pdf makes life about 100 times easier when identifying connectors referenced in the Diagnostic flow:
You can check the abs sensor speed signals using the ABS inputs function of the Nanocom. Be aware that the SLABS ecu will stop communicating with the EVO at some point above 7kph, so you'll need to keep the speed low. Again recording inputs to SDCard is the best way to collect the information. Once you have connected to the ECU in the ABS Inputs section touch the disk icon and enter a file name. You'll need to touch the disk again before you loose communication with the ECU to end the recording and save the data to file. The data is saved as a semicolon delimited CSV file. You can open this in Excel by using the import function and selecting CSV, you also need to select semicolon as a delimiter as this is disabled by default.
cheers
Paul
Hi Paul,
Excellent post! I agree that using the nanocom's recording function to the SD card is the way to go. Plotting the data up in excel or the free viewer application to visualize is particularly useful and helped me with my recent Faulty MAF diagnosis.
Cheers
Steve
I agree re the GraphicViewerCSV. It's a great choice for viewing Td5 engine data, but unfortunately seems to be limited to that application, as was the Nanocom original.
It definitely would be useful to have another simple way of visualising the Data from other ECU's.
cheers
Paul
| Search AULRO.com ONLY! |
Search All the Web! |
|---|
|
|
|
Bookmarks