216 kw charging achieved at EA station after OTA update

[Canthoney]

If it was an employee on a pre-release build, I can absolutely understand why it would get taken down. Unless it's a public "beta", it's confidential until release.

That makes sense. I’m guessing it’s not public if they removed it though

Sponsored

 

[Scott]

So an employee posted this picture and probably was told to take it down? I thought we were past this when customer started getting their trucks, I don’t quite understand the secrecy

It makes a ton of sense to me. It is great to test in a low stakes / low risk situation. If there are bugs, you don't hurt paying customers. If you have to pull back a feature and not release it due to problems, no one is disappointed.

This is a good way to manage software roll outs, and exactly how I would do it if I ran that team. I expect if this was an employee posting internal testing releases online, then they got a very stern talking to today.

Even if there are no bugs, think of the impact of pushing out release notes / a preview before any real customer can get it: support now has tons of users calling in asking "how do I get the update?", thus wasting CS time and annoying users.

 

[Riviot]

Car wash mode!!! Charge port door opening every time bugged the hell out of me.

 

[805Badger]

Just checked mine. No update available. Not sure if there is a way to force it but I'm really disliking this staggered rollout stuff. Polestar is the same way.

Same here

 

[pc500]

Same here

It's Risk management. If something goes wrong, do you want 20,000 vehicles visiting a service center at once? Slow-roll is the norm, but allowing a user to force a manual update is an acceptable compromise. Now that doesn't yet exist as a feature.

 

[R1Sky Business]

It makes a ton of sense to me. It is great to test in a low stakes / low risk situation. If there are bugs, you don't hurt paying customers. If you have to pull back a feature and not release it due to problems, no one is disappointed.

This is a good way to manage software roll outs, and exactly how I would do it if I ran that team. I expect if this was an employee posting internal testing releases online, then they got a very stern talking to today.

Even if there are no bugs, think of the impact of pushing out release notes / a preview before any real customer can get it: support now has tons of users calling in asking "how do I get the update?", thus wasting CS time and annoying users.

It’s all planned. Just buzz creation….and it’s working

 

[R1Sky Business]

I see your occupation is "Engineer". Not sure what type, but in the IT world, it is always best practice to stagger any sort of large scale release.

What if this update bricks every single car? Easier to remediate if only a small subset of cars got the update. Plus, as the rollouts go, there are logs collected to determine if there are any issues. There's always a feedback loop so issues can be addressed. If no issues, continue deploying. Also less strain on the deployment servers.

So does this finally deliver the 140 miles in 20 minutes that was initially promised???

 

[r1vlife]

Just had a mobile service this morning to get my truck to display the right color and for him to install the missing door handle trim piece. The senior tech working on my vehicle received this update last night and just start testing it. It'll probably be a few weeks for it to hit us. He mentioned that he was able to get 10-80% in 30 min in previous releases and that it is all about finding the right chargers and being at the right temperature.

 

[kylealden]

It’s all planned. Just buzz creation….and it’s working

(this is not a real thing)

 

[mgc0216]

Staggering your rollout is how you ensure you didn't miss a bug that is massively impactful to the entire fleet...

As the Ops voice in the room: It's also how you ensure you don't overwhelm your backend services by having 90% of your fleet trying to update at once (although with autoscaling and CDNs this is less of an issue that it has been in the past, but still best practice is to try and moderate the traffic as best as possible).

ETA: I think I'm going to add this to my list of system design interview questions. Design a system to update the software for a fleet of electric vehicles.

 

[SASSquatch]

Just checked mine. No update available. Not sure if there is a way to force it but I'm really disliking this staggered rollout stuff. Polestar is the same way.

That one update that bricks everyone's R1T but that you were saved from because it was pulled before it got rolled out to you will make you appreciate staggered rollout...

 

[Dark-Fx]

That one update that bricks everyone's R1T but that you were saved from because it was pulled before it got rolled out to you make you appreciate staggered rollout...

No way, it would give me ammo to talk with a lawyer about right-to-repair.

 

[Joel]

Just checked mine. No update available. Not sure if there is a way to force it but I'm really disliking this staggered rollout stuff. Polestar is the same way.

Polestar seems to now do a staggered deployment of service center 2-3 weeks then fleet. This seems to be the case for the last 2 versions.

 

[lostpacket]

edit: made this it's own thread for visibility

 

[SASSquatch]

No way, it would give me ammo to talk with a lawyer about right-to-repair.

I hear you, and that would be a valiant battle to fight (paging Rich Rebuilds) but I think that the way manufacturers are headed, it is going to be an uphill climb.

Sponsored