Week old Air Touring is showing this after driving through an unavoidable large puddle on the freeway. Have a call into Lucid -- no response yet beyond acknowledgement.
Strange. Let us know what customer care says.I don’t know, really. Deeper than it looked, but other cars were going through. And nothing happened right away … the fault showed up about 10-15 minutes later.
No. Service can, and they connect with a CAT6 cable.Water probably made it into a connector and shorted a sensor. Bet it goes away when everything dries up, assuming there is some type of self check/self clearing of the error.
This happens to my Miata's rear o2 sensor when I drive through deep standing water. It will throw a check engine, I pull the code to confirm it's the rear o2, then clear it. Doesn't come back so long as the sensor/connector is dry.
Makes me wonder how you would pull and clear codes on the Air. Does it even have an obd2 port? Can you pull and clear codes?
Interesting. Wonder what type of network protocol it uses, LIN? Flexray?No. Service can, and they connect with a CAT6 cable.
Just curious if you had the Miata long enough to know if such connector would be susceptible to corrosion from moisture.Water probably made it into a connector and shorted a sensor. Bet it goes away when everything dries up, assuming there is some type of self check/self clearing of the error.
This happens to my Miata's rear o2 sensor when I drive through deep standing water. It will throw a check engine, I pull the code to confirm it's the rear o2, then clear it. Doesn't come back so long as the sensor/connector is dry.
Makes me wonder how you would pull and clear codes on the Air. Does it even have an obd2 port? Can you pull and clear codes?
To be clear this shouldn't be an issue on a new car. In this case, I'd insist they check it and find the issue, or at least have it documented on the service records so if a part needed to be replaced in the future you could point back at this instance. Finding it may be difficult unless it's really obvious a connector isn't snapped together properly.Just curious if you had the Miata long enough to know if such connector would be susceptible to corrosion from moisture.
My landscaper uses waterproof connectors for 12 V lighting so there must be a reason why this is not done for cars.
That'd make sense. Thanks for the info.To be clear this shouldn't be an issue on a new car. In this case, I'd insist they check it and find the issue, or at least have it documented on the service records so if a part needed to be replaced in the future you could point back at this instance. Finding it may be difficult unless it's really obvious a connector isn't snapped together properly.
Most car connectors that are critical will have seals. The O2 being one of them. Each individual wire in the connector will also have a gasket.
Like this, see the gasket around the connector: https://www.bmotorsports.com/shop/product_info.php/products_id/496
And this, the yellow gaskets are for each individual wire:
Home » Shop » Connectors / Harnesses » Delphi / Packard » Connector Kits » GM Delphi / Packard - 2-way Shrouded GT 150 3.5mm centerline sealed female Kit for IAT
Ballenger Motorsports GM Delphi / Packard - 2-way Shrouded GT 150 3.5mm centerline sealed female Kit for IAT (CONN-75643) for only $3.99!www.bmotorsports.com
I don't know much about EV braking systems because I really just play with ICE cars. With ICE cars there isn't much electronics going on around the brakes. Usually just a wheel speed sensor.
Glad it worked out! Yeah they should definitely still inspect as there must be an incompetent seal somewhere that led water to get in…unless this was just a coincidence, which it may or may not be since it didn’t happen until 15 min after the puddle?As it happens, @NoseyReporter was right on the money. The faults went away on their own, and both auto hold and park are now working correctly. Interestingly (although this might be completely unrelated), the turn signal sound got a lot feebler for about ten minutes or so, and then came back to its normal volume.
I will still have Lucid look at it, though, when I take my car in to fix the dead front radar sensor.
It’s been pretty snowy and wet here in Boulder since I got my car. And knock on wood, no issues yet. I do have to wonder if there’s a seal somewhere in your car that is letting water in. Certainly a good hypothesis.Every one (5) of my faults (except for the dead screens = module) happened in the rain. Don't know if this is co-incidence, but I understand you folk out Arizona way have never seen rain...so don't understand the importance of water-proofing electrical systems.
{Peter being English (tease) ... never known an English car that ran in the wet. Lucid is a dry-climate car.}
Now would be a good time to test drive a batch of Lucids in the "atmospheric river". Maybe build a factory in Aberdeen, WA and test drive them in the Olympic Park?
Hello @rao_94583, possible, I'll check with the PPF shop on Monday. If this is similar to the issue you had maybe it solves itself before the towing service arrives tomorrow afternoon.Could it be that they sprayed the car underside prior to the PPF (or even after, I suppose)? If they really do have an iffy seal in there, I can imagine it causing a fault after a little while. And maybe it will just disappear, like mine did. The service center could not see anything in the logs.
I just got those same two faults today after removing the original rear tire, replacing it with a spare, and driving down a steep incline. I then remembered that my spare was only at 20 psi, so I quickly went back home and pumped it up to 42 psi but the warnings persisted. I drove to my destination and back which was about 60km while those two faults kept cycling and beeping in the background.Thanks @Cosmo Cruz. I had to flatbed my Lucid to Costa Mesa last week. Service center representative said it will be there for about 2 weeks or so - not sure if they are overwhelmed with repairs. So far no feedback on diagnosis or possible root cause of the "Brake System Fault". Car has ~500 miles on it. I'm bummed :-(. If anyone else has encountered similar/identical faults and had it repaired, would appreciate your feedback on what the root-cause was and the fix.