Voronbrg
Well-Known Member
Mine is still at the sc for same issue. Only problem is they can't recreate the issue because they don't have any 11kw capable chargers at the sc. Only 8kw are installed there, well it charges fine at 8kw.
Sponsored
Notes will say something like, "fixed rare problem with L2 charging over 32A."We'll have to say exactly what they say when the next patch notes come out.
This is happening for me as well, my new charger shows up today. If it is a software issue that is alot of expense for what may or may not be a charger problem.WOW! Exactly my thoughts too- but Rivian is shipping me a new charger and having one of their electricians come to install it.
when your vehicle failed to charge, did the charger turn red and require you to reset your breaker?
Same temporary solution here, reducing to 32 amps (~9kw) fixed the charging error for now too.
Same, my replacement charger just showed up a few hours ago.This is happening for me as well, my new charger shows up today. If it is a software issue that is alot of expense for what may or may not be a charger problem.
I'm still able to charge with AC, just needed to lower the current with the Rivian charger. May mean that the AC converter is frying out, maybe? but my guess is not related and just a software bug related to the latest software update.Maybe some of these issues are related to this:
https://www.rivianforums.com/forum/threads/onboard-charger-ac-charging-disabled-customer-satisfaction-campaign-advisory-for-2022-2023-rivian-r1t-r1s-?-rca-34-23-002-1.16922/
Did your charger also turn red when the issue happened? or just the truck ring light where you plug in? report back (please) if reducing to 32amps also fixes it for you.I have this same problem right now as we speak. Going to turn down to 32A
Same here.Mine the charger never turned red, just the ring around the charging port on the car.
Mine is strange because the charging resumed itself when I went down there to check on it. The charger was not red and the truck indicated it was charging and was a percentage point higher than it was indicated when the app told me there was an error.