Page 1 of 1

Posted: Tue Feb 20, 2007 9:55 am
by grippo
I went through the calculations using your eq = code eq and got the following for a BATFAC = 12 (1.2 ms) and InjOpen = 10 (1.0 ms):

---------BATT ---------PW open
-------72(7.2V)-------22(2.2 ms)
------100(10V)-------17(1.7 ms)
------120(12V)-------13(1.3 ms)
------130(13V)-------11(1.1 ms)
------132(13.2V)-----10(1.0 ms)

These look reasonable to me. What are you getting for these in MT ? If the MT values are different, I will check tonight.

Posted: Wed Feb 21, 2007 10:00 am
by grippo
MT gets its pulsewidth direct from MS II and shouldn't be changing this, other than to correct for msx10 integer to ms decimal units. And PWopen is added directly to the PW, so if you run at say 10V without correction, vs running with correction, the PW should change by .7 ms. I will check this tonight.

Posted: Wed Feb 21, 2007 9:25 pm
by grippo
I tried a run with default batfac(.2ms/V) and a battery voltage of 10 V. I got a PW of 14.5 in MT. I changed battfac to 0 and got a PW of 13.8, a drop of .7 ms, which is exactly what it should be.

In looking at your numbers, I think I see what the problem may be. The batfac in MT when using the default data is .2 ms/V, because that is more meaningful physically, but the default batfac in the code that produces that is 12 msx10 or 1.2 ms. If you factor BatFac and re-write the eq. as follows, you will see what is going on:

PWopen = InjOpen + BatFac *(132 - BAT) / 60

So, what is shown in MT is really BatFac/60 = 12/60 = .2 ms/V.