Renault: Hulkenberg problem related to MGU-K change
Nico Hulkenberg’s retirement from the Chinese Grand Prix was caused by an issue related to Renault’s new-spec MGU-K, the team has confirmed.
Nico Hulkenberg, Renault F1 Team R.S. 19, takes his grid position
Steven Tee / Motorsport Images
The team believes that the German's retirement was brought about by a software glitch that can be resolved without any need for modified hardware.
Renault was forced to produce a new spec MGU-K after McLaren’s Carlos Sainz suffered a failure in the Australian GP.
The Spaniard had the new unit for Bahrain, but the works team stuck with the original version, only to suffer a costly double retirement with both Hulkenberg and his teammate Daniel Ricciardo in the closing laps of the race.
Both works drivers and McLaren’s Lando Norris took revised units for China, and Renault believes that the change triggered a software problem that forced Hulkenberg out of the race.
“It’s too early to say exactly what happened,” Renault F1 boss Cyril Abiteboul told Motorsport.com. “But we had the problem in Melbourne, and a very quick reaction in Bahrain for one part only for Carlos.
“We had to push massively on production in order to get more parts, which meant that we had to fast track some of the process and some of the sign-off that we do. And basically something was triggered that we had not had the time to properly sign off. It’s not an excuse, it’s a fact.
“All of the other cars have worked without any problem using the same part. We’ve covered 5000kms on the dyno with that part. It’s just for one particular reason we went into a mode which triggered something in the software.”
Abiteboul believes that there will no need to rush through a third spec of MGU-K hardware before the next race in Baku.
“We don’t think so. We think it’s something that is outside of the part itself, we don’t think that the part that Nico was using was damaged. We think it’s a software issue, we think we need to change something on the software to deal with something that was changed in the hardware.
“That’s why we were hoping to try and fix it in the course of the race. Maybe it was not broadcast, but there were a number of actions that Nico was trying to do. He could not go as far as rebooting the whole car.
“That’s almost what was necessary. If you want to drive the car now, you could, it’s working absolutely fine! It’s a typical software problem – you have a ‘freeze’ you need to reboot. It’s pretty much what we were trying to do on track, but it didn’t work.”
Abiteboul conceded that Renault has to get on top of its ongoing reliability issues: “We need to investigate, and we need to stop putting ourselves in such a complex situation, backs to the wall, having to react in an emergency, because you can’t work in an emergency in F1.
“We are playing catch-up with that, and that has to stop as soon as possible.”
Be part of Motorsport community
Join the conversationShare Or Save This Story
Subscribe and access Motorsport.com with your ad-blocker.
From Formula 1 to MotoGP we report straight from the paddock because we love our sport, just like you. In order to keep delivering our expert journalism, our website uses advertising. Still, we want to give you the opportunity to enjoy an ad-free and tracker-free website and to continue using your adblocker.
Top Comments