"Charging Unavailable: Contact customer service"

[Sapper]

I posted something similar (before I tried DC fast charging) back in Feb and got no responses, so I assume this is rare. I got the Gravity 31 Dec and only have 600 miles on it. I live in Albuquerque.
Whenever I get in the car I get the warning above. It has affected nothing to this point. The car charges at home flawlessly (Autel 50 amp hardwired).
When I called CS they referred me to SC in Scottsdale. I would always get someone first try, and despite being nice they would just not call back with answers.
My simple questions were how many Gravities have experienced this at your SC and what was the fix? The people that answer phone are not techs and getting them to actually ask a tech if they have seen this before is near impossible.
The release notes from 3.4.1 said it was to get rid of this exact erroneous message so why was I getting it?
I am 90% certain that I never got the error message before 3.4.1 so I suspected software, but ... How could it leave factory without being charged on a DC fast charger?? So, if it charged there ...?
There is no mobile tech for my area. A risk I took when I bought the car so far from the mothership (actually they had one and he left).
Anyway, someone finally called me back and said try a DC fast charger.
Today I tried Telsa, Rivian, and EA chargers at a local shopping center. All of them failed and implied I have a charging problem. Sigh.
So, they are scheduling transport to take it to SC in AZ at huge expense to Lucid.
And the manual does not mention this error message, it says "DC Charging unavailable" but nowhere does the manual list the exact warning I am getting - how is that even possible in software?
And finally for a car that communicates with the mothership Lucid can see nothing remotely of value even if the car is creating warning messages.
So ... I am frustrated. My gut says it is something simple and Lucid is wasting a lot of money, but we will see ...
If anyone has experienced this exact problem, I would appreciate you contacting me.

 

[socktucker]

It is confusing. They have shipped my car thousands of miles and are about to ship it another 1000 miles (round trip) to a different SC to fix what the other SC did. I have no idea why they keep dumping money into this car instead of accepting my buyback request

But yes that is how they do it.

 

[Adnillien]

I posted something similar (before I tried DC fast charging) back in Feb and got no responses, so I assume this is rare. I got the Gravity 31 Dec and only have 600 miles on it. I live in Albuquerque.
Whenever I get in the car I get the warning above. It has affected nothing to this point. The car charges at home flawlessly (Autel 50 amp hardwired).
When I called CS they referred me to SC in Scottsdale. I would always get someone first try, and despite being nice they would just not call back with answers.
My simple questions were how many Gravities have experienced this at your SC and what was the fix? The people that answer phone are not techs and getting them to actually ask a tech if they have seen this before is near impossible.
The release notes from 3.4.1 said it was to get rid of this exact erroneous message so why was I getting it?
I am 90% certain that I never got the error message before 3.4.1 so I suspected software, but ... How could it leave factory without being charged on a DC fast charger?? So, if it charged there ...?
There is no mobile tech for my area. A risk I took when I bought the car so far from the mothership (actually they had one and he left).
Anyway, someone finally called me back and said try a DC fast charger.
Today I tried Telsa, Rivian, and EA chargers at a local shopping center. All of them failed and implied I have a charging problem. Sigh.
So, they are scheduling transport to take it to SC in AZ at huge expense to Lucid.
And the manual does not mention this error message, it says "DC Charging unavailable" but nowhere does the manual list the exact warning I am getting - how is that even possible in software?
And finally for a car that communicates with the mothership Lucid can see nothing remotely of value even if the car is creating warning messages.
So ... I am frustrated. My gut says it is something simple and Lucid is wasting a lot of money, but we will see ...
If anyone has experienced this exact problem, I would appreciate you contacting me.

I have not seen your particular issue reported before. I suspect that the problem is in the rear drive unit (RDU) since it will not charge at either 1000V (EA, Rivian) or 500V (Tesla) chargers. There are contactors in the RDU inverter that route DC directly to the battery or through the DC to DC boost circuit for Tesla chargers. Something in this path has failed. I do think transport to the Scottsdale service center is the right move. Since I use the Scottsdale SC, I will say that they are one of the best service centers in the country.

 

[hwy17er]

I have not seen your particular issue reported before. I suspect that the problem is in the rear drive unit (RDU) since it will not charge at either 1000V (EA, Rivian) or 500V (Tesla) chargers. There are contactors in the RDU inverter that route DC directly to the battery or through the DC to DC boost circuit for Tesla chargers. Something in this path has failed. I do think transport to the Scottsdale service center is the right move. Since I use the Scottsdale SC, I will say that they are one of the best service centers in the country.

Ya, know...reassuring ppl that are experiencing frustrating things is a class act.
Thank you for being like that and sharing your knowledge as any of us could be having this happen to them next