- Joined
- Nov 19, 2021
- Messages
- 9,502
- Reaction score
- 10,895
- Location
- Cupertino, CA
- Cars
- Air DE-P, ZR, 21"
- DE Number
- 241
- Referral Code
- Q1BTN5Y3
It wasn’t a thing originally. It is a work in progress that has grown and developed over time. Keep in mind there are over 70 ECUs in the car, and not every single one is updateable OTA and not all of them talk to each other. It isn’t *quite* as simple as “send everything to a syslog daemon.”Update on Remote Diagnostics.
With a previous issue (the OP), my reliable service manager at Torrance was able to log in to the car and tell me what the problem was - my battery. So remote diagnostics exist, right?
I have a new issue (turtle mode), and he says he can't tell what the issue is without plugging in to the car. So I am about to get a loaner (waited five days for that, but worth it to drive a rental fossil fuel car) and he will take my car to diagnose the problem. Good service (all in all), but still it seems that Remote Diagnostics is not really fully thought out or fully implemented on my 2022 AGT.
Again, as a software guy who engineered big computer clusters where every CPU and small processor reported it's errors to a central server, it seems that any error that results in a message to the user should log the reason for that message to Lucid's central system, and that should be available for the service team. It is incomprehensible to me that a system might say "Hey, there's something wrong but I don't know what." It is much more likely that there is a very specific sensor reading that has triggered the Turtle Mode alert, and that very specific reading should be reported to Lucid service so they can start the repair process.
I know that others on this forum report that "remote diagnostics is a thing", and I agree it sometimes is. But it does not seem to be adequate.
It’s a bit more complex than your classic “error reporting” scenario.
But you’re right that the onboard and remote diagnostics is by no means “complete” yet; it is a work in progress.