logoalt Hacker News

enough_ahnaf • today at 8:20 AM • 2 replies • view on HN

Amazing to learn on this thread. Does anyone know what they would use to simulate ECU problems like this? Im a firmware engineer in the industry and kind of seeing a problem like this and this thread really opened up my eye to what it looks like under the layers of Media in F1


Replies

johnwalkr • today at 9:52 AM

I looked it up yesterday and they have the ECU in the loop for the driving simulators (the ones the drivers practice with and that are used for checking mechanical changes). But these use empirical models, they can't simulate everything. You would have to get a lot right in the models and top of that know where to test edge cases and then simulate all inputs correctly for those. You can surely input yesterday's weather conditions but whatever model is there might not predict an output that goes to the next model and so on..

I'm sure there's also all kinds of other HIL testing but it comes down to thinking about all conditions and having models and tests that are realistic enough for those conditions. It's impossible to have perfect coverage.

It's probably kind of lucky that enough cars were impacted so that the issue was revealed instead of having a just a few cars knocked out of the race.

j4k0bfr • today at 9:06 AM

With something safety-critical like an ECU, I'd be surprised if they left formal proof out of their software design and testing. This would make unexpected hardware behaviour much more likely imo. I guess I'd get around it by setting up automated hardware-in-the-loop simulators for testing every possible environment and input. Surely the cost would be worth it for F1 as a whole.

At a startup I worked at, we jerry-rigged Pi 5's with commercial of-the-shelf environmental sim software to achieve this. Very cost effective, lol.