What's new
By:

Drive System Error / Loss of Propulsion Mid-Drive

S

studdross

New Member

Joined
Jul 18, 2026
Messages
3
Reaction score
7
Cars
Lucid Gravity Touring
My Gravity Touring threw up a “pull over safely” warning while driving 50mph. It happened immediately after changing from standard braking regen to high.

No propulsion, the vehicle would only maintain current speed (but if the speed went down it would only coast at that speed or less, so on and so forth).

Luckily able to pull over into a neighborhood and opened the alert to see Dive System Error and the vehicle would not go back into gear; pressing the brake to shift to D or R would retrigger the error. Tried soft and hard resets. Eventually raking the key fob away for 20 minutes allowed it to reset and able to drive it home, no further issues so far.

We’re at less than 500 miles, excited to see what the service follow-up and process looks like…
 

Attachments

  • IMG_0607.webp
    IMG_0607.webp
    1.4 MB · Views: 79
Sorry to hear or your car's trouble. Please let us know how service deals with this unfortunate situation.
 
I would also send your pics and incident info to the software feedback support email:

marqie

Thread 'What to Include When Submitting SW Feedback'

Thank you to everyone who has taken the time to share software feedback with us at [email protected]. Your insights play an important role in helping us enhance your ownership experience.

When submitting software feedback, please be sure to include the following details to help the team with their review:
  • VIN
  • Software version
  • Timestamp of the concern
  • Any additional context or relevant information
  • Pictures if available (can be super helpful)
We will reach out if additional information is needed. If your vehicle requires service, please contact your...
  • Like
  • Love
 
RajD said:
I would also send your pics and incident info to the software feedback support email:

marqie

Thread 'What to Include When Submitting SW Feedback'

Thank you to everyone who has taken the time to share software feedback with us at [email protected]. Your insights play an important role in helping us enhance your ownership experience.

When submitting software feedback, please be sure to include the following details to help the team with their review:
  • VIN
  • Software version
  • Timestamp of the concern
  • Any additional context or relevant information
  • Pictures if available (can be super helpful)
We will reach out if additional information is needed. If your vehicle requires service, please contact your...
  • Like
  • Love
Click to expand...
Given that the error is red, and not yellow, my suspicion is a hardware problem, not software.

Sorry to hear about your trouble, OP! I hope it gets resolved quickly. <3
 
borski said:
Given that the error is red, and not yellow, my suspicion is a hardware problem, not software.

Sorry to hear about your trouble, OP! I hope it gets resolved quickly. <3
Click to expand...
I’ve found that one of the failure modes that gives that message is a fault in the low voltage system.
Definitely need that functioning for anything else to work.
If,in an ICE car, you lost power to your ecu you’d be just as dead in the road.
 
To follow up and close this out: Lucid service checked the error logs and data from my vehicle, both remotely and later onsite for a mobile service appointment, and could not find anything to flag as the culprit. The issue has not appeared again. The vehicle was under software version 3.6.0 when the error occurred, it's been under that, 3.6.3 and 3.6.4 with no issue. Fingers crossed it stays that way... :)
 
I had the same problem a few months after I got my 23 touring. They replaced the rear drive unit to fix whatever the problem was. No problems since then.
 
studdross said:
To follow up and close this out: Lucid service checked the error logs and data from my vehicle, both remotely and later onsite for a mobile service appointment, and could not find anything to flag as the culprit. The issue has not appeared again. The vehicle was under software version 3.6.0 when the error occurred, it's been under that, 3.6.3 and 3.6.4 with no issue. Fingers crossed it stays that way... :)
Click to expand...
Thank you for sharing, @studdross. I just sent you a DM.
 
You must log in or register to reply here.
Back
Top