First I must apologize to Graham, it was indeed his fine work I was referring to.
Dallara, Funny story about the BSA Goldstar and it brings back memories. One of my riding buddies back in the day had a 441 Victor. He loved it and could ride the heck out of it but was I too chicken to start it. ??? LOL
Yes I am 100% sure I did the same process as always. BUT I do not wait for the little dashboard display to stop. You may be on to something there. More on that below.
Yes AC is probably the most knowledgeable person around on the S10 maps. But I have the same Fast Tune tool and access to the same maps. One of my minor disappointments with it was that we do not have access to ALL the maps. All the main ones for sure but not the cranking pulse map or warm up enrichment for instance. On my DIY system cranking pulse is a separate map addressed by coolant temperature. It is very rich and if I remember right, ranges from around .7 to 3 times the "Required Fuel" value depending on how cold it is. "Required Fuel" is essentially the injector open time required for WFO. All the other values in the in the normal fuel tables are refereed to as volumetric efficiency and are a percent of RF. So VE * RF and several other minor tweak factors yield injector open time. (simplified) Anyway I digress, and it was pointed out that I can't explain fuel injection logic. . . :
Jaeger, you like to mention how similar so many EFI systems are, and I agree with you. But then you change tacks and say the Super Tenere must be fundamentally different to have this "hard start" issue.
No never said that, it is very similar to the others. But I believe there is minor a bug somewhere. We often say in my world, a debugged piece or software is one who's explode inputs have not been tried yet.
Now to the important part.
First I did RTFM ;D and I do not fine anywhere any direction to wait for the display to finish before starting. I would think if that were important, Yamaha would have given us a clue. Aso if they thought it was a risk, they could just block it from starting until it was finished in the ECU. Trivial software.
Second, I did actually experimenter with deliberately hitting the start button at various points during the display initialization cycle and could never detect any difference. And I did not expect to. See next.
Third, do not confuse what you see on the display with the initialization of the EFI! The EFI loop runs somewhere in the 500 to 1000 times a second range. So it does all it's needed initialization in a millisecond or so. Then it is ready to go. The little display dance we see is very very slow so that we poor very slow humans can see it. Also because it is driving analog needles and they can only go so fast.
So starting before the display finishes is not IMHO operator error.
That all being said, here is where I think you may be on to something! What if there is a bug in the way the ECU handles the interrupt subroutines for the display dance such that if you hit the starter at EXACTLY the right time it gets lost? This kind of issue is not at all unknown in my EE world. That would pretty much explain everything we are seeing. It is of course just a wild theory and I don't know how we would ever prove it but it sure make a good argument for following your recommendation to wait for the display to finish before starting. ::008::
I still say that would be a fault and not an operator error but there may be an operator workaround. Can't hurt.
