P1 82B status 53 DTC code

A forum for the Nissan Armada, Infiniti QX56, and beginning in 2014, the Infiniti QX80
ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

This one bothers me, as it's transmission code.
It won't clear, I tried several times. Says Lock position sensor.
I can not find ANY info on that code anywhere.
Sensor location?
Truck drives fine, no CEL, no warnings, 4WD seems to be doing well, just when I engaged 4WD, IBA off appeared in the dash. No idea, if it's supposed to or not.
Thank you


User avatar
VStar650CL
Technical Expert
Posts: 11931
Joined: Thu Nov 12, 2020 1:25 pm
Car: 2013 Nissan Altima 2.5 SL
2004 Nissan Altima 2.5 S

Post

It's not a transmission code, it's from the transfer case. The code is for the Transfer Lock Position sensor, the 4WD sees a conflict between the position indicated and where the lock mechanism actually is. The sensor is a PITA, it's up on the back of the xfer case and requires dropping both driveshafts and lowering the case and transmission. Along with a wiring issue, the error can also be from a worn out switch actuator inside the case (bad news, of course). There's a "learn" algorithm needed for the sensor if you replace it.

QX80 Transfer Lock Sensor.jpg

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

Great. Drivability wise, what does it mean? 4WD - not to jinx - seems to engage. Winter is coming, we might have some snow and ice, don't want to end with stranded vehicle.
Also, do you happen to have part number?
Thank you.
I have shop owner who I know since his age 14, he does such jobs for me very reasonably. Just need to know, if it's safe to drive.
Oh, not to forget. When I rescanned it yesterday, that code changed its status to 10 I believe. Instead of 53. I'll have it rescanned today with a more advanced scanner, mine is $200 Foxtel with Nissan s/w on it, and report back. But, if the "status" changed, what exactly does that mean?

User avatar
VStar650CL
Technical Expert
Posts: 11931
Joined: Thu Nov 12, 2020 1:25 pm
Car: 2013 Nissan Altima 2.5 SL
2004 Nissan Altima 2.5 S

Post

It pretty much means nothing if you're in 2WD, but depending what state the sensor is stuck in, the 4WD modes may not engage properly or at all. I don't know what your "status number" means, Nissan codes have states of "current", "past", and "first trip". There are also "permanent" DTC's, but that shouldn't apply to a driveline code.

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

My scanner under status may show Past (history) or Current or nothing.
20231213_195102.jpg

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

VStar650CL wrote:
Sat Dec 16, 2023 8:12 am
It pretty much means nothing if you're in 2WD, but depending what state the sensor is stuck in, the 4WD modes may not engage properly or at all. I don't know what your "status number" means, Nissan codes have states of "current", "past", and "first trip". There are also "permanent" DTC's, but that shouldn't apply to a driveline code.
Got it. So if 4WD will not engage, I should have 4WD error message in the dash, right? So far, there was none, when I pressed 4WD button.

User avatar
VStar650CL
Technical Expert
Posts: 11931
Joined: Thu Nov 12, 2020 1:25 pm
Car: 2013 Nissan Altima 2.5 SL
2004 Nissan Altima 2.5 S

Post

That's correct. The 4WD may work, but may not lock or work in 4L.

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

Ok, update.
4wd works fine. I live on acreage, lots of muddy grass, got it it out, drives fine no skids. No lights.
And, that code is gone.
The worst so far is that CAN COMM U1000 code. It hangs on several modules.

User avatar
VStar650CL
Technical Expert
Posts: 11931
Joined: Thu Nov 12, 2020 1:25 pm
Car: 2013 Nissan Altima 2.5 SL
2004 Nissan Altima 2.5 S

Post

U1000's are generic, they mean the module throwing the code hasn't heard from another module it should be hearing from for 2 seconds or more. Unless your scanner can talk to every module in the car (which most can't), the only way to track them down is to use the transmit/receive signal chart in the LAN section of the FSM. For each unit throwing the U1000, wherever it has an R, flag the unit which has the T. Then eliminate all the messages which aren't shared between the units throwing the U1000's. The result will be the unit that's MIA.

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

VStar650CL wrote:
Sun Dec 17, 2023 8:10 am
U1000's are generic, they mean the module throwing the code hasn't heard from another module it should be hearing from for 2 seconds or more. Unless your scanner can talk to every module in the car (which most can't), the only way to track them down is to use the transmit/receive signal chart in the LAN section of the FSM. For each unit throwing the U1000, wherever it has an R, flag the unit which has the T. Then eliminate all the messages which aren't shared between the units throwing the U1000's. The result will be the unit that's MIA.
That's above my paygrade. I'll take it to a Nissan shop in about 10 days, let them diagnose it. Actually, am tempted to simply disconnect the battery and see, if it clears something.

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

OK< disconnected battery, jumped battery cables to remove any residual power, all those U codes are gone so far. Including that lock switch code.
Toes crossed.

ukrkoz
Posts: 107
Joined: Mon Jan 14, 2013 3:55 pm

Post

Still clear.


Return to “Armada Forum / QX56 Forum / QX80 Forum”