You have to give him his due. He hazes the rear, recognizes that he has a hot sticky rear, blows by clusters in the first half lap while the rear is hot but starting to cool down right? I just watched the race from his fork cam. Awesome.
Too bad the entire weekend wasn't wet. Wasn't this Pecco's first rain win?
…as the fuel load comes down at about half distance Marquez is coming by. Then he crashes...
There's still 62 points left. Go back and watch the race from Pecco's fork cam. In that corner the pavement has been patched. It appears his line was just slightly wide and he catches the edge of that patch at full lean. And clearly the Pramac launch software/set-up is better than the factory's. Jorge has launched better in the entire second half of the season. Pecco was faster, it would have been different if he had led from the start.The DNFs doomed Pecco.
Doesn't matter, the points have been lost. Pecco was/is faster as evidenced by the Q2 session.
Unless Jorge make an epic mistake during Sunday's GP, it's likely a done deal. I mean, never say never, as one can't predict what the final race will be since there's so many variables, but I wouldn't be putting money on Pecco to retain the title right now, even as much as I want the factory team to retain the title.
I don't know if your software/setup argument holds-up though. They have access to each other's data, as do all of the GP24 teams (I don't know if the GP23 teams are excluded from that sharing). If there was a setup advantage, surely the factory Ducati team would know about it and use it as well.
I think MM has it next year though. On a year old bike he manages to finish 2nd in today's sprint. He's clearly not afraid of crashing and has a lot of race experience to draw on.
If Pecco had finished 6th in the 8 DNFs he's had (assuming an even split, 4/4, between GP and Sprint races) he'd be 29 points ahead as of right now.
What fork camera? No one has a camera on their forks.Go back and watch the race from Pecco's fork cam.
Yes you don't select the particular camera. But I note the front camera is typically on when the riders close and chasing. Did you actually watch from Pecco's feed? Probably not. Anything for an insult right? As far as the ETV stuff I've been steadily attempting to get you all to understand that everything you feel from a "tuned bike" is really the changes to the ETV maps. The one thing that's clear to me is that you are so slow you couldn't detect the actual handling issue on your SF. Stone hands. So, I've learned all the mapping (and change it as suits me). Sorted a chassis that truly screams at you that it's wrong. And now I'm blueprinting an 1103 from which I will get more power, greater reliability and more rapid acceleration (more than one way to get a motor to spin up faster other than power). And you've learned or accomplished what?Jesus. This is like when you were writing about your bike having "AI" or any post that mentions "ETV." No ...., search "etv map." It's hilarious.
When you select the on-board camera when viewing from a browser window, you merely select "OB1" or "OB2" etc., with the numeral being each respective rider. You don't get to pick which on-board camera. Typically its the tail camera, unless they're using one of that rider's three cameras for the commentary feed.
To be blunt: What is called the "ETV Restriction” in the WRT software has no direct connection to the ETV control. I do not mean to offend you in any way but your understanding of the system and tables is at a similar level as Woolich support seems to have. Yes, you see an effect by changing parameters in this table for sure but there is no need to even touch the rev limiter because of these changes and there is no direct link to cylinder pressure. The only real impact to cylinder pressure comes from spark advance changes and this table has no impact on Spark advance at all. And touching the Spark advance maps at full load is really not needed as the Spark mapping is pretty much spot on from the factory. I think it’s for sure fun to tinker with a system like this and make some adjustments based on your personal preferences. As long as you don’t make any drastic changes you are likely to be fine and not trigger any torque monitoring.
BTW, there is no speed limiting. Some USA models have a power limit in the OEM map but Woolich is not displaying this table in the software so you cannot disable it.
I sure can comment. My main comment is that Woolich is lacking a great amount of general understanding of these ECUs. Clearly Woolich must have missed that the Pani V4 MY22 and up now has 4 engine power modes versus 3 for the older models. To me it looks like all they do with a new software version is copy table definitions from older versions over without any validation work on a bike.
I have no personal interest in making their software any better. I invested a lot of time in expanding my understanding of this ECU Software and I share it only with with very few people in the tuning industry that I collaborate with and that I can trust.