MicroSquirt.com read only forum (Jan.15,2018)

I noticed the following advice over on MSefi, dragged a copy over here where I have posting password:

Re: injector test mode stuck
by grippo on Tue Mar 16, 2010 3:06 pm

I fixed injector test mode in code 3.4x for the sequencer, and there is a change that is not in 2.89 code that could possibly cause a problem, but it would be freakish if it happened. What can easily happen is a burn doesn't go through putting the processor in a bad state, or the required sequence to get out of Test Mode is not followed.

Anyway, attached is a new code version (2.90) and corresponding ini file. The only changes from 2.891 were the Inj Test Mode fix and 2 that affect only MAF configurations.The ini file requires the use of TS - it will not work with MT. The only reason is a table generator program was added to allow loading new maf tables and MT won't recognize this program.

Lastly, I attached an instruction file for using Injector Test Mode.

I'm wondering if this might apply to a couple of instances where my bike has been stuck in "Injector Test Mode" on restart, after having saved a template and powered down tuning lap top and bike just prior?
I'm running 2.89, works as desired and I can probably avoid issues on the road simply by not tuning when on the road. Reloading of firmware brings the bike back out of the infected status.
Should I be using 2.9 I wonder? Are there any potential changes with that which might lead me toward further tuning requirements? (as I'm wanting to be done that for a couple of months now and ride, rallies, and such)
Feedback appreciated,
Lorne

If you were driving your car , tuned it, and then restarted it, and found the code corrupted, the Injector Test Mode problem is not a factor. This only occurs when you are in Injector Test mode and can't get out of it. But if you do a burn, what happens is that the whole section of 100s of flash memory variables is erased and has to be re-loaded with the values from ram memory. If this part fails to complete, then when you restart the flash, which was wiped out, is copied to ram, and there is garbage in both memories. The only way to get back is to reload your msq.

If you are using the auto mixture control, which can re-burn flash every few minutes, and the engine is cut while it is in the middle of this, you can get into this state. It would be unlikely, but it could show up every great once in a while.

I don't really think you are in Inj Test mode when you can't restart, unless you were in it before you restarted. But in either case, did you reload just the msq or code + msq ? You should be able to just reload the msq. If the code is getting clobbered, that I don't understand.

As you mention, I had been operating in "Auto Mixture Control" and saved the tune, turned off the lap top & bike just prior to fueling up (don't like to "come to" with myself & bike on fire).
When I turned the key back on, I knew what was going on right away, funny thing is that I did attempt to reboot the lap top, as well reload just the MSQ I had saved one step back of the one last saved (thinking it may have corrupted also). When that didn't work I knew I was going to have to reload firmware as that was how I corrected the same situation the preceeding time.
If that is confusing, then the other part I don't understand is that this all appeared after I had attempted to use "Injector Test Mode" some while back, and had troubles going back into normal mode. That episode seemed to fry one injection fet (which I have not corrected yet on that ecu). Perhaps there is something more the matter with that ECU?
Should I be concerned about upgrading to 2.90 version then do you think?
Thanks for the expertise.
Lorne.

So, just to be clear on how the "Automatic Mixture Control" works for everyone else, if it has been left turned on have people found that they have had a problem(s) at some time when restarting?
I gather this isn't a problem others have had?

Let me clarify - there are 2 modes of operating AMC: (1) let it periodically update RAM, which means if you do not do a save of the ve table any updates will be lost when you turn off the key; (2) let it periodically burn Flash, so you don't have to remember. There should be no risk whatsoever in letting it update ram, the ECU is always updating something or other in ram.

The way I would operate is to let it update ram and then before turning off save the ve table. After doing this for a few times, the tune should be good enough that AMC is just making tiny changes and there is no need to save these, they will quickly come back as soon as you restart the engine. You can use the burn Flash option for the first few weeks of tuning then leave it off and turn it back on for one or 2 times every few months, but I would not leave it on day after day, year after year.

R100RT wrote: If that is confusing, then the other part I don't understand is that this all appeared after I had attempted to use "Injector Test Mode" some while back, and had troubles going back into normal mode. That episode seemed to fry one injection fet (which I have not corrected yet on that ecu). Perhaps there is something more the matter with that ECU?
Should I be concerned about upgrading to 2.90 version then do you think?
Thanks for the expertise.
Lorne.

If using the Injection Test Mode caused code corruption, then reloading the code should get rid of any problem - I burn new code every other day, and sometimes 20 or 30 times a day and I have never had any code corruption. You should not be jinxed just because this problem happened. I have not heard of this causing problems with the hw, but ign would be the most likely. And if there is a hw problem, the newly loaded software should operate fine, just may not be any spark because the fet is shot.

The main reason to update to 2.90 would be if you plan to use Inj Test Mode again.

Very good then, that clarifies all the questions.
Having been going at it manually to date, I haven't enjoyed the benifits of AMC really - hence this learning curve when VE tables near to completion.
Thanks for your help, excellent product!