If he does, they will have to take penalty for new MGU-H (the last one failed in AUS)
They are still deciding whether or not to use an old MGU-H and Turbo with the rest of the Spec 3 upgrade.
I don't understand this at all. Why don't they just switch engines at a frequency that completely matches what they can produce? They aren't in the game anyway so might as well consider every grand prix a test run of sorts instead. So get spec #3 with a brand new Turbo/MGU-h package so that they cover as much ground as possible, test wise, to be closer to on-track by the end of 2017.SameSame wrote: ↑11 Jul 2017, 16:42They are still deciding whether or not to use an old MGU-H and Turbo with the rest of the Spec 3 upgrade.
https://www.motorsport.com/f1/news/hond ... nda+engine
That would be the most logical option, especially considering Hungary coming up. It makes one wonder if in fact they have anything new to test. This Spec 3 is the update that has been planned since pre-season testing; if that’s all they could produce in 5 months then there’s not much hope for an upgrade per GP.hurril wrote: ↑11 Jul 2017, 17:11I don't understand this at all. Why don't they just switch engines at a frequency that completely matches what they can produce? They aren't in the game anyway so might as well consider every grand prix a test run of sorts instead. So get spec #3 with a brand new Turbo/MGU-h package so that they cover as much ground as possible, test wise, to be closer to on-track by the end of 2017.
The current engine seems to be able to get there.
FYI : repeating a bunch of stuff said previously in this thread, but briefly ... there was Spec 2, there have been a whole bunch of tweaks to the MGU-H and that looks like it's still ongoing, and this Spec 3 is supposedly only part of a much bigger change which is being worked on (search out Wazari's last couple of posts), there has been one (or two ?) fuel changes, and a bunch of mapping refinements. Up to you whether you consider it 'fast enough' or not, but it isn't just Spec 3.if that’s all they could produce in 5 months then there’s not much hope for an upgrade per GP
If you bothered to read my post in context; I was specifically referring to hardware upgrades, that fall under the controlled components list, per GP.bigblue wrote: ↑11 Jul 2017, 18:15FYI : repeating a bunch of stuff said previously in this thread, but briefly ... there was Spec 2, there have been a whole bunch of tweaks to the MGU-H and that looks like it's still ongoing, and this Spec 3 is supposedly only part of a much bigger change which is being worked on (search out Wazari's last couple of posts), there has been one (or two ?) fuel changes, and a bunch of mapping refinements. Up to you whether you consider it 'fast enough' or not, but it isn't just Spec 3.if that’s all they could produce in 5 months then there’s not much hope for an upgrade per GP
Well I (still!) hold Honda very high and have nothing but awe for what they are able to put out. But perhaps you are right in that, perhaps they are not able to produce items that are both "spec #3" and "reliable" at the same time.SameSame wrote: ↑11 Jul 2017, 17:39That would be the most logical option, especially considering Hungary coming up. It makes one wonder if in fact they have anything new to test. This Spec 3 is the update that has been planned since pre-season testing; if that’s all they could produce in 5 months then there’s not much hope for an upgrade per GP.hurril wrote: ↑11 Jul 2017, 17:11I don't understand this at all. Why don't they just switch engines at a frequency that completely matches what they can produce? They aren't in the game anyway so might as well consider every grand prix a test run of sorts instead. So get spec #3 with a brand new Turbo/MGU-h package so that they cover as much ground as possible, test wise, to be closer to on-track by the end of 2017.SameSame wrote: ↑11 Jul 2017, 16:42
They are still deciding whether or not to use an old MGU-H and Turbo with the rest of the Spec 3 upgrade.
https://www.motorsport.com/f1/news/hond ... nda+engine
The current engine seems to be able to get there.
Sorry, wasn't obvious to me, thought you meant not much has happened in general - was just commenting that quite a lot has been going on, though admittedly without a really big performance change yet.
No worries.
The current ECU is a TAG-320 (standard across the field). The tool to code it is simulink, which is used with matlab. Simulink produces the C that's then compiled and run on the TAG-320.
Wow, that is extremely surprising to find out that they use Simulink. I have used Simulink with hardware in the loop before; and in my experience it is only useful for prototyping. It is not very efficient at generating C, even though it is built on it and has an option to generate raw C without uploading the code to the hardware, as it's focus is to be used as a high level programming language.Craigy wrote: ↑11 Jul 2017, 20:48The current ECU is a TAG-320 (standard across the field). The tool to code it is simulink, which is used with matlab. Simulink produces the C that's then compiled and run on the TAG-320.
There's a lot more to the code systems than just "here's the tool **write stuff**...here's the code" as the whole thing is built to run simulations while the cars are on track and during development cycles.
Hardware in the loop simulation doesn't use bespoke test code, it uses the same stuff the cars are always running so it has to be written generically enough to do everything.
That's pretty subjective.