websurfer

I finally got my NX350h windows tinted. I think the tint tech left the doors opened for around 3.5-4 hours. That may have drained the car battery. He said he threw a charger to the vehicle also after he finished. There was a check engine light on the dash and it states to check with dealer now. Before it state check with manual.

When I got home, I checked the 12V voltage and it was at 12.85V. So it appears fully charged. The checked engine light didn't disappear yet.

I also opened and closed the gas cap to sure it clicked.





Anyone have any idea?

websurfer

I found this one but different year and model.
https://www.clublexus.com/forums/nx-...nsimssion.html

midcow3

This is an interesting article that might apply to you check engine light problem.

Lexus: How to Reset Your ECU | Clublexus


YMMV,
MidCow3

oreon333

Your check engine light is there just because as you said the battery might have got discharged, happened to me a few times actually. All you got to do is just connect the OBDII scanner, if you got one, and just erase the code(s). or just ignore the error if you do not have the scanner, or get one

websurfer

Thanks,

The tint tech indicated to drive the vehicle around. I have the Bluedriver OBDII and it's doesn't work for the NX correctly. I'll look for another.

websurfer

I'm not too urgent to clear the alert, I'm trying to see if the alert is really something I need to be worried about.

gcskoor

Unfortunately, the NX does tend to throw a code when the battery is discharged with tjust the car doors open. I guess the systems are partially active and when it dies in some unknown state throws a code.

In caseyou have the same issue, on my code the reset, my first OBDII reader could reset the dash check light, but went I went into to some maintenance screen to look at the car status, it still showed the recorded code issue. I did not want the Lexus dealer to ask or charge for a reset, so found a code reader that could clear the permanent code. This was over a 1 1/2 years, so def just an issue with the discharged battery.

I wonder how many Lexus NXs get towed to the dealer for this type of issue? I bet more than we know.

Freds430

Happened to our NX when we got PPF and windows tinted. Dash showed code. We took it to our Lexus dealer who eliminated the code. They said would have disappeared on their own in a week. When I did mine a year later and a friend did hers they put on a trickle charger.

midcow3

I bet AAA would reset the code for free.

lsft

The code will disappear if nothing is wrong. You could get a OBDII and software to clear the codes or read what the code is and see if it is related.

websurfer

Thanks All.

I'll drive it today and see what happens.

Lexus/Toyota should update the software to throw an error code for 12V battery weak instead of check engine light then push over the air update. Need to hire better engineers.

Droid13

The ODBII system is not what I'd call a particularly intelligent diagnostics system, and its operation is fairly similar across all manufacturers due to its standardization. Its basically 90s tech. That's why we still need to occasionally rely on expensive experienced mechanics with their expensive scan tools performing the actual diagnosis (this is why ODBII has also created the "parts canon" situation where less experienced fixers simply throw parts at a code instead of understanding why the code is there in the first place). The system simply/blindly stores codes when some device monitored by the vehicle report measurements that are outside of set limits without any effort whatsoever to understand why, its duty is simply to report. A low voltage situation can mess up measurements across a lot of monitored devices and cause all sorts of codes to be stored because of this and the cause is really up to a human to decide (whether its a low battery, a broken or scuffed wire, a sensor or electronic module not operating correctly, etc). If the original cause goes away, sometimes the CEL will go off after some time (hours, days perhaps), but the code remains in memory. Most mechanics after reviewing the stored codes, will usually delete all of them and see which come back if any, to see what might really be going on.

I suppose perhaps in the future we might have a fleet AI system monitoring your car instead of dumb ODBII but not simply comparing them to device specs as now, but also intelligently comparing all of them with all the measurements being recorded by the entire fleet of vehicles and matching trillions of these patterns of measurements collectively captured with what repairs or causes were found for specific error situations. On that day, your car will take over driving and immediately proceed to the car repair center where a robot is already waiting outside with the replacement wire for your car because it already knows that you have a wire with a melted insulation jacket that came loose and touched the exhaust manifold. Today, we call that a TSB and it is probably 10000X slower than if an AI could indeed have access to this level of information.

TheCDN

Had same issue after I drained battery installing backseat covers etc for our dog. Had doors open for a while and it killed battery. Lexus jumped started the car under warranty in my driveway, and I had similar warning indication pop up on centre display. Dealer called next day to make sure everything was ok. They said that it would take several drive sessions, ie starting travelling shutting off, repeat, to clear 'code', which it did. Discussion with tech at next dealer visit said that 'codes' are a little out of date with these cars. There's so much data kept for technicians to look at including all your safety monitoring systems. Anyways fault stopped popping up after a few days of driving on it's own.

oreon333

If you only drive Toyota/Lexus, here is a wonderful OBDII scanner you might want to get -> It is bi-directional scanner and it comes with lifetime updates + it does full systems and all services.

websurfer

I drove the vehicle right out of the garage today and the light cleared. I guess it needed time to recharge itself