reverendalc
Member
- Posts
- 36
- Location
- Seattle, WA, USA
I just bought this NAS 2006 RRS HSE 4.4 petrol. The truck goes in and out of emergency or “crash” mode without any pattern, and is sitting suuuuper low with an amber suspension light on the IC and compressor kicking off.
I’m not sure the history of this truck, but I can tell that a bit of troubleshooting had been done in the form of insulation pierces on lots of wires near the compressor and valve assembly.
What I’ve done:
Replace brake switch
Replace brake lamp bulbs
Replace battery
Replace air compressor (hitachi version replaced with hitachi)
Remove/inspect/resolder IC plug
Some more specifics:
When I say emergency, I mean the radio says “system fault vehicle shutting down” as all electronics except IC (with lots of warning messages and lights) go dark and the hazards begin to flash. The truck will continue to run and drive like this, but if I switch it off then I cannot restart until it decides to come to its senses.
When the truck isn’t doing that, it runs and drives perfectly. I drove it home about 10 miles. I have seen numerous faults from the air computer, but the only consistent one that often comes all by itself is “reservoir valve.” I have disassembled and inspected the reservoir valve, bench testing the solenoid and testing the valve action with my lungs. It’s possible but seems highly unlikely to me that the pressure switch is bad.
When I start the truck, the air compressor run for maybe 1 second before cutting off. This triggers the chime, amber warning light, and special modes disabled. If I repeatedly clear the code, the compressor will keep cutting on briefly until it codes, and occasionally run for up to 10 seconds. Monitoring gallery pressure, I have seen a rise from 120 to 600 kpa over the last 50 odd attempts. I cannot lift the truck with the air, and the wheel height sensors accurately report the positions on the 4x4 display. When jacking up either side of the truck, they also accurately reflect the movement.
I have a nanocom EVO, and I have pulled as many as 41 codes from 15 modules after one clear. This is usually after an emergency mode session, most of which are accompanied by EPB warnings, HDC warnings, sometimes ABS too. Clears and restarts repeatedly will usually only result in the one reservoir valve code, after it tries to pump air.
I will update with a list of the codes, but the VAST majority of them involve ECUs losing communication with other ECUs, predominantly the IP and the “Front Lighting” ECU. The second most frequent codes are medium speed can bus errors, and there are also some “module software incompatibility” codes. Then there are codes regarding implausible data, and a bunch of other noise. Again though, when the truck is staying out of emergency mode, I’m only getting the reservoir valve code with the suspension failure.
My nanocom routinely cannot clear codes from Front Lighting ECU, and sometimes ABS or another. My nanocom crashes when I attempt to calibrate the valves via the suspension service. It repeatedly cycles two messages like “failed to query valves” and “comm error.” When I set it to view input, it shows me wheel height sensors but all air related values are zero. When I use my Foxwell NT510 to tell the truck to raise up, it immediately ends the process and says complete.
I have compared the genesis CCF for my asbuilt to the existing, they are dissimilar in some ways. When searching genesis for software, I noticed that a lot of my ECU software and assembly codes and hardware codes didn’t match up completely and I could only match maybe 1 or 2 but rarely all 3 numbers. Choosing the most appropriate looking softwares, I have reflashed any unit I could download for. No difference. I did notice however that there doesn’t seem to be a download for Front Lighting ECU, despite the fact that the nanocom will query it for you. Also, when I request ECU info, I get four errors in a row before it gives the info, and the errors are just short blurbs of hex string with no verbiage.
My next thought is to hunt down the computers and check/clean their connectors. I would love to know where to find each of the computers on the medium speed CAN bus. Maybe the hispeed and fiber buses too. I’m curious if the medium speed runs in the door sill looms, and if there’s any susceptible splices or connectors in those areas? The front windows didn’t work, and the fix for them involved digging into the right hand door sill where water ingress had compromised a splicing of wires. I checked the left hand door sill also, and saw evidence of much water. It looked old though, and I’ve parked the truck outside in some torrential downpours and not seen a drip in the partially disassembled interior. I’ve fussed with much of the wiring and connectors in/near the sill, and haven’t been able to throw a code or invoke emergency mode by doing so.
Sorry for the long winded post and the threat of more posting tomorrow, but I really look forward to your thoughts and suggestions.
Cheers
I’m not sure the history of this truck, but I can tell that a bit of troubleshooting had been done in the form of insulation pierces on lots of wires near the compressor and valve assembly.
What I’ve done:
Replace brake switch
Replace brake lamp bulbs
Replace battery
Replace air compressor (hitachi version replaced with hitachi)
Remove/inspect/resolder IC plug
Some more specifics:
When I say emergency, I mean the radio says “system fault vehicle shutting down” as all electronics except IC (with lots of warning messages and lights) go dark and the hazards begin to flash. The truck will continue to run and drive like this, but if I switch it off then I cannot restart until it decides to come to its senses.
When the truck isn’t doing that, it runs and drives perfectly. I drove it home about 10 miles. I have seen numerous faults from the air computer, but the only consistent one that often comes all by itself is “reservoir valve.” I have disassembled and inspected the reservoir valve, bench testing the solenoid and testing the valve action with my lungs. It’s possible but seems highly unlikely to me that the pressure switch is bad.
When I start the truck, the air compressor run for maybe 1 second before cutting off. This triggers the chime, amber warning light, and special modes disabled. If I repeatedly clear the code, the compressor will keep cutting on briefly until it codes, and occasionally run for up to 10 seconds. Monitoring gallery pressure, I have seen a rise from 120 to 600 kpa over the last 50 odd attempts. I cannot lift the truck with the air, and the wheel height sensors accurately report the positions on the 4x4 display. When jacking up either side of the truck, they also accurately reflect the movement.
I have a nanocom EVO, and I have pulled as many as 41 codes from 15 modules after one clear. This is usually after an emergency mode session, most of which are accompanied by EPB warnings, HDC warnings, sometimes ABS too. Clears and restarts repeatedly will usually only result in the one reservoir valve code, after it tries to pump air.
I will update with a list of the codes, but the VAST majority of them involve ECUs losing communication with other ECUs, predominantly the IP and the “Front Lighting” ECU. The second most frequent codes are medium speed can bus errors, and there are also some “module software incompatibility” codes. Then there are codes regarding implausible data, and a bunch of other noise. Again though, when the truck is staying out of emergency mode, I’m only getting the reservoir valve code with the suspension failure.
My nanocom routinely cannot clear codes from Front Lighting ECU, and sometimes ABS or another. My nanocom crashes when I attempt to calibrate the valves via the suspension service. It repeatedly cycles two messages like “failed to query valves” and “comm error.” When I set it to view input, it shows me wheel height sensors but all air related values are zero. When I use my Foxwell NT510 to tell the truck to raise up, it immediately ends the process and says complete.
I have compared the genesis CCF for my asbuilt to the existing, they are dissimilar in some ways. When searching genesis for software, I noticed that a lot of my ECU software and assembly codes and hardware codes didn’t match up completely and I could only match maybe 1 or 2 but rarely all 3 numbers. Choosing the most appropriate looking softwares, I have reflashed any unit I could download for. No difference. I did notice however that there doesn’t seem to be a download for Front Lighting ECU, despite the fact that the nanocom will query it for you. Also, when I request ECU info, I get four errors in a row before it gives the info, and the errors are just short blurbs of hex string with no verbiage.
My next thought is to hunt down the computers and check/clean their connectors. I would love to know where to find each of the computers on the medium speed CAN bus. Maybe the hispeed and fiber buses too. I’m curious if the medium speed runs in the door sill looms, and if there’s any susceptible splices or connectors in those areas? The front windows didn’t work, and the fix for them involved digging into the right hand door sill where water ingress had compromised a splicing of wires. I checked the left hand door sill also, and saw evidence of much water. It looked old though, and I’ve parked the truck outside in some torrential downpours and not seen a drip in the partially disassembled interior. I’ve fussed with much of the wiring and connectors in/near the sill, and haven’t been able to throw a code or invoke emergency mode by doing so.
Sorry for the long winded post and the threat of more posting tomorrow, but I really look forward to your thoughts and suggestions.
Cheers
, ATC is all terrain control, BCM is body control module, HVAC is also obvious, PA is parking assist, and AFC is audio front control.
