LOSS OF SYSTEM REDUNDANCY DETECTED - Potential major system failure

[JeffDaniel]

Quick background, I picked up my Cyberbeast in St Louis last week (VIN: 20,3XX), so it's not an extremely early build. Up until today, EVERYTHING was perfect. No gaps worth addressing, no performance issues, it's been the absolute best vehicle I've ever driven.

So today. . .

I was at the Supercharger in Little Rock, AR. Charged to about 50% (from 8%). Unplugged, got in the truck, foot on break, and then THE ERROR! (I'll type it all out so you don't have to try to read it off the picture.

--------------------
LOSS OF SYSTEM REDUNDANCY DETECTED
Unable to shift out of Park (P) because the vehicle has detected a loss of redundancy. Out of Park (P), the vehicle may suddenly lose electrical power, steering, and propulsion, and may be unable to apply the parking brake.

It may be possible to recover the system by performing a vehicle power cycle: Exit the vehicle, close all doors, reenter the vehicle, and attempt to drive.

An override is available for low-speed maneuvering to position the vehicle for roadside support. Be ready to apply the brake pedal.

--------------------

So after having a heart attack, I got out of the vehicle and allowed it to shutdown. I will note, the CT had a loud sound coming from it, similar to a large fan (louder than the standard charging noise). After the truck shut down, the noise went away. I got back in the truck and the error had cleared (thank God).

So my question is, has anyone else had this issue? If so, have you had any reoccurrence? Anyone have this issue where the restart didn't help? Just need to figure out if I need to take it in to a service center for inspection.

Any thoughts or opinions are appreciated.

Sponsored

 

[mongo]

Quick background, I picked up my Cyberbeast in St Louis last week (VIN: 20,3XX), so it's not an extremely early build. Up until today, EVERYTHING was perfect. No gaps worth addressing, no performance issues, it's been the absolute best vehicle I've ever driven.

So today. . .

I was at the Supercharger in Little Rock, AR. Charged to about 50% (from 8%). Unplugged, got in the truck, foot on break, and then THE ERROR! (I'll type it all out so you don't have to try to read it off the picture.

--------------------
LOSS OF SYSTEM REDUNDANCY DETECTED
Unable to shift out of Park (P) because the vehicle has detected a loss of redundancy. Out of Park (P), the vehicle may suddenly lose electrical power, steering, and propulsion, and may be unable to apply the parking brake.

It may be possible to recover the system by performing a vehicle power cycle: Exit the vehicle, close all doors, reenter the vehicle, and attempt to drive.

An override is available for low-speed maneuvering to position the vehicle for roadside support. Be ready to apply the brake pedal.

--------------------

So after having a heart attack, I got out of the vehicle and allowed it to shutdown. I will note, the CT had a loud sound coming from it, similar to a large fan (louder than the standard charging noise). After the truck shut down, the noise went away. I got back in the truck and the error had cleared (thank God).

So my question is, has anyone else had this issue? If so, have you had any reoccurrence? Anyone have this issue where the restart didn't help? Just need to figure out if I need to take it in to a service center for inspection.

Any thoughts or opinions are appreciated.

May have just been a fluke. You could enter the service menu to check what errors it logged. Tesla can also do that remotely.

 

[chaosmarine92]

I would say contact service and see if they can take a look at the logs to figure out if it needs to come in. They should be able to do that remotely.

 

[JeffDaniel]

May have just been a fluke. You could enter the service menu to check what errors it logged. Tesla can also do that remotely.

Great idea. Thank you!

 

[JeffDaniel]

I would say contact service and see if they can take a look at the logs to figure out if it needs to come in. They should be able to do that remotely.

I appreciate the idea. I will be doing that.

 

[Friday]

It almost sounds like there may be spurious comms bus anomalies getting latched in and flagged as errors by the diag monitoring subsystem. I see this occasionally on the stuff I work on. A hard reset usually clears. Could be real, intermittent failures getting logged or a firmware/fpga diag escape that will be fixed in higher revs of SW release. Either way, uploading to Tesla is the best option.

 

[Crissa]

The fans would spin up in an unstable computer state; better to have them running full than have a chip overheat.

This error would pop up for a low voltage system failure - like the DC/DC board or wiring harness. But it could have just been a sensor malfunction or software failure. Hopefully the latter.

If it cleared on reboot, still get a service appointment in case it returns.

-Crissa

 

[JeffDaniel]

UPDATE: I spoke with Tesla Service. After remoting in they saw a massive list of failures. All the errors cleared on the restart, but we still scheduled a service appointment to inspect. The system says that there is no reason to not drive at this time. They asked that I call them back if it happens again before service appointment. If it does, they will send a tow.

The interesting thing is, the girl I spoke with, while very helpful, had never seen this issue before. She almost seemed amazed by how many errors were showing. I'll update after service inspection (in a couple weeks).

 

[mongo]

UPDATE: I spoke with Tesla Service. After remoting in they saw a massive list of failures. All the errors cleared on the restart, but we still scheduled a service appointment to inspect. The system says that there is no reason to not drive at this time. They asked that I call them back if it happens again before service appointment. If it does, they will send a tow.

The interesting thing is, the girl I spoke with, while very helpful, had never seen this issue before. She almost seemed amazed by how many errors were showing. I'll update after service inspection (in a couple weeks).

A communication failure can create a lot of errors very quickly. If 5 modules on one side are trying to talk to 5 modules on the other side, that can generate 25 errors. And there a lot more than 10 modules...

 

[JeffDaniel]

UPDATE #2: ERROR UPON ERRORS

Opened up the service screen. The amount of alerts is almost comical.

 

[SCTesla]

Looks like a coolant issue, tbh. Have them do an hvac purge and see if there are air pockets, then fill it back up.

Not an uncommon problem if it is.

 

[JeffDaniel]

Looks like a coolant issue, tbh. Have them do an hvac purge and see if there are air pockets, then fill it back up.

Not an uncommon problem if it is.

Thanks for the advice.

 

[Horizonvangogh]

I’m @ 8k miles. Had this happen @ around 6k miles. While I was showing off exterior features of the truck for about 20 minutes. I got back in afterwards and had this error. Stepped away from vehicle, locked it and returned. Error was gone and roadside/overide notification disappeared. Been fine since.

 

[JeffDaniel]

I’m @ 8k miles. Had this happen @ around 6k miles. While I was showing off exterior features of the truck for about 20 minutes. I got back in afterwards and had this error. Stepped away from vehicle, locked it and returned. Error was gone and roadside/overide notification disappeared. Been fine since.

That's a HUGE relief. Thank you for sharing that. I just picked mine up last week and have 1300+ miles. I think we all realize that "Foundation Series" is a code for "Willing Beta Tester". So I'm not surprised with an issue coming up, nor does it even upset me. But this one just seemed massive.

 

[SCTesla]

That's a HUGE relief. Thank you for sharing that. I just picked mine up last week and have 1300+ miles. I think we all realize that "Foundation Series" is a code for "Willing Beta Tester". So I'm not surprised with an issue coming up, nor does it even upset me. But this one just seemed massive.

If it is coolant, a small bubble will be fine and you may not have another issue, but a large one will get worse and you may eventually need a tow.

I had that issue at 200 miles....and it was fine for a week, but then got bad.

Sponsored