Brian-MS90D
Well-Known Member
- First Name
- Brian
- Joined
- Mar 19, 2024
- Threads
- 1
- Messages
- 46
- Reaction score
- 60
- Location
- Cincinnati, OH
- Vehicles
- Rivian R1S (Dual Motor, Max pack, LA Silver)
- Thread starter
- #1
Picked up new R1S Dual Motor Max on Sunday. Left Monday for long road trip vacation. Absolutely love the vehicle. However, starting Monday I noticed a troubling issue. Whenever the car goes to sleep, upon re-entering and trying to drive it gives the following errors (in order):
It then will not shift into Drive or Reverse. Binnacle will not say "Ready." Additionally, the HVAC will not turn on (all other functions work such as lights, radio, frunk/truck, etc).
In order to clear it, I have to do two of the three "reboot" methods. The method that works the most reliably is:
Additionally, the car works normally as long as I do not let it sleep. For example, if charging (DC or AC) has not completed then the faults will not come up. I used this to my advantage last night overnight at hotel by lowering the amps and creating a very long charge time so that when I came back to the car in the morning it was still charging. Or, if I leave dog mode on while at a restaurant that will prevent the car from sleeping and avoid the faults.
I have also noticed that I cannot remotely control the climate from the Rivian phone app. Even when the car is functioning normally if it has not gone to sleep yet, it never "connects" to turn on/off or modify the climate settings. That being said, I can monitor the charge status remotely from the app.
If I only try to do a hard reboot (without the sleep reboot), during the reboot the car does not make the clicking noises around the car and behind the dashboard. The faults will remain. I can only clear the faults by doing the combination of the two reboots (and it appears in any order, although I have not fully proved this out yet).
Once operational, everything is normal. I've observed and confirmed that both motors are engaged at low speed. And, that only the front motor is engaged at highway speed. I've driven ~ 600 miles now over 2 days despite these faults that are generated when I allow the car to sleep.
Rivian phone support had no ideas. They scheduled me with a service appointment for Monday when I return home (assuming my reboot scheme works for the rest of the week). I haven't read anything like this in the forum or elsewhere online.
Has anyone seen this or have any ideas?
It then will not shift into Drive or Reverse. Binnacle will not say "Ready." Additionally, the HVAC will not turn on (all other functions work such as lights, radio, frunk/truck, etc).
In order to clear it, I have to do two of the three "reboot" methods. The method that works the most reliably is:
- "Sleep reboot" - Turn off proximity key, bluetooth, and WIFI. Lock the car and ensure nothing on the seats, no USB plugged in, and nothing connected to charge port. Wait ~ 15 minutes for the car to complete a sleep cycle.
- "Hard reboot" - Left steering wheel button + hazard button reboot. During the reboot, many things click around the car and behind the dashboard.
Additionally, the car works normally as long as I do not let it sleep. For example, if charging (DC or AC) has not completed then the faults will not come up. I used this to my advantage last night overnight at hotel by lowering the amps and creating a very long charge time so that when I came back to the car in the morning it was still charging. Or, if I leave dog mode on while at a restaurant that will prevent the car from sleeping and avoid the faults.
I have also noticed that I cannot remotely control the climate from the Rivian phone app. Even when the car is functioning normally if it has not gone to sleep yet, it never "connects" to turn on/off or modify the climate settings. That being said, I can monitor the charge status remotely from the app.
If I only try to do a hard reboot (without the sleep reboot), during the reboot the car does not make the clicking noises around the car and behind the dashboard. The faults will remain. I can only clear the faults by doing the combination of the two reboots (and it appears in any order, although I have not fully proved this out yet).
Once operational, everything is normal. I've observed and confirmed that both motors are engaged at low speed. And, that only the front motor is engaged at highway speed. I've driven ~ 600 miles now over 2 days despite these faults that are generated when I allow the car to sleep.
Rivian phone support had no ideas. They scheduled me with a service appointment for Monday when I return home (assuming my reboot scheme works for the rest of the week). I haven't read anything like this in the forum or elsewhere online.
Has anyone seen this or have any ideas?
Sponsored