Thread: Nanocom code p1884

If I had that fault the first place I would look is at the back/top LH corner under the console to see if the wires to the XYZ switch were chafed and shorting.
There is a retainer for the wiring loom there which is right next to a protruding bolt and it would be easy for the loom to wear through and short.
You have to remove the console top to get to it easily and that requires drilling out 12 or so rivets.
It's a reasonably common reason for those types of errors , although it doesn't seem to occur all that often.

Regards Philip A

Thanks Phillip A!

I'm a little hesitant to drill out rivets but it doesn't seem like I have many other avenues to explore

Originally Posted by lyhoon94

Thanks Phillip A!

I'm a little hesitant to drill out rivets but it doesn't seem like I have many other avenues to explore

Only pop rivets. Easy peasy.

.... M&S lights flashed and it wouldn't turn over.

Switched on the nanocom and read the gear box faults, resulted in "code p1884 can message md_ind invalid". No other faults.

Took a picture and cleared the fault, still no start, but fault also didn't reappear.

Scan the engine ECU too for codes cos it might be a more relevant there but confirm it doesnt crank or it cranks but doesnt start cos if it doesnt crank check the lucar connector on the starter solenoid to be well connected eventually give it a tug to the starter with a hammer and see then, that fault code would not stop it crank(it's about torque input via CAN) but it can be the result of a no crank issue so if it doesnt crank work on the starting system's path

Originally Posted by PhilipA

If I had that fault the first place I would look is at the back/top LH corner under the console to see if the wires to the XYZ switch were chafed and shorting.
There is a retainer for the wiring loom there which is right next to a protruding bolt and it would be easy for the loom to wear through and short.
You have to remove the console top to get to it easily and that requires drilling out 12 or so rivets.
It's a reasonably common reason for those types of errors , although it doesn't seem to occur all that often.

Regards Philip A

am I close to the right spot?

Originally Posted by sierrafery

Scan the engine ECU too for codes cos it might be a more relevant there but confirm it doesnt crank or it cranks but doesnt start cos if it doesnt crank check the lucar connector on the starter solenoid to be well connected eventually give it a tug to the starter with a hammer and see then, that fault code would not stop it crank(it's about torque input via CAN) but it can be the result of a no crank issue so if it doesnt crank work on the starting system's path

Thanks heaps sierrafery!

I had given a few taps to whatever I could from the top but ive been hesitant to get underneath as it was parked on the grass and the last few days have been wet and inconvenient.

Today I had finished early and given the good weather, I got underneath and had a poke around. Found the starter motor not connected, I made the connection between the loose wire and the starter motor and voila.

Took it for a run around the block and parked it on the drive way. The connector looks wrecked though, so I plan to snip it off and replace it with a new female blade tomorrow.

Pictures to come.