Thread

1. jey · 1791167555 · focus · HN ↗

   Seems wild that they can code and deploy an update of a critical-seeming component in the field like that. I thought such a firmware update would need extensive QA in the lab, along with root causing why this bug slipped through their processes anyway.

   But maybe that's the difference between shipping a controller for F1 versus shipping one for an industrial or consumer product? shrug.

   1. Jean-Papoulos · 1791180727 · focus · HN ↗

      They didn't, it just needed a restart. From the first reports the first car's software genuinely glitched out because of the new track/rain/etc and had to be restarted, the other cars got anti-traction control triggered because going this slow for this long unspools the turbo, which got so bad the detection software made a false positive.

      1. gambiting · 1791181388 · focus · HN ↗

         I mean, the article literally says a firmware update was deployed mid race to remove power limits, is the article wrong?

         1. mjpa86 · 1791192446 · focus · HN ↗

            Teams confirmed it was a firmware update on the broadcast. Article is correct.

Unofficial Hacker News client; not affiliated with Y Combinator.