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

I have a new release that was made to head off a potential
microsquirt problem due to the coils being turned on with the default
configuration. This code will be flashed in all new microsquirts, but of course is downloadable from here in any microsquirts already sold. The following changes were made relative to 2.873:

1 A new input: ECUType was added (255 = unknown, 1= MS II, 2 =
microsquirt). If ECUtype is outside the valid ECU range, the code
will put the ignition outputs in a safe state and wait in a loop until a known ECU type is put in by the user. This will be signaled in MT by the rpm guage toggling between 0 and 8000 rpm while a red box on the bottom tells you to select ECU Type. You select this from the General menu, which is the only one not greyed out. At this time you should also enter the proper ignition output polarities to avoid coil driver or coil damage, and then burn flash and reboot. While you are at it, you should also set your no. cylinders, wheel config and other values that you know ahead of time and won't change. This is for new people. For those who have an msq, I believe you can load that, then change the ECU Type, then save a new msq with the right ECU Type and reboot. After that you don't need to worry about this process any more. When you upload your msq after a new code change, the ECU Type will automatically be burned and clear the loop.

2. Added baro correction and also air density correction to the cranking
pulsewidth.

3. Put in an alpha N x baro correction that makes alphaN act more like MAP. This was tested by someone who drove a bike up a quite high mountain and said it helped his tune maintain a good idle at botht the top and bottom of the mountain.

4. The dwell timeout was reduced from 1 sec to 0.3 sec, again to protect coils/ drivers from getting damaged.

5. The prime pulse was found to have a bug in it such that I suspect some peole never got a prime pulse. I fixed this and extended it to allow it to be as long as a second if someone wants (I wouldn't).

6. Put in the fix for dual spark ignition output that I developed in v2.862t1 forMenno on the MS II forum/ Ignition Tuning.

7. Made a correction to the N2O algorithm question that
recently came up on the forum. The N2O enrichment input is now a % which multiplies the delta_t between tach pulses. This provides a fixed flowrate for the N2O rather tha a fixed PW. Since the same variable is also used for the x-tau test impulse, which is in ms, a change inthe setting.ini file is required if you want to use N2O enrichment. Lance can explain further, but you just set the N2O variable in the new setting.ini file that he will provide. Make sure you test this by seeing what it does to the PW before you use this with nitrous lese a blown engine will surely result - no one has tested this on a real engine so don't disregard this warning.

8. Default warmup x-tau % values were reduced to avoid low rpm oscillation.

9. A problem was found where if, at startup, you got engine synch at a high rpm > crank_rpm, then ASE was not provided. This was fixed.

There is a new megasquirt-II.ini.2.8 for the latest code, as well as a new settings.ini (that includes the MAPbaro and ECUType settings). They are attached.

Both of these can also be found at: http://www.megamanual.com/ms2/code.htm The source code and S19 files are also there, of course.

Lance.

Hi there,

I've been trying to get v2.88 to run in my MSII and something just doesn't seem right. I upgraded from the latest beta code (v2.871 I think) and stepped through the MSQ and am pretty sure nothing is missing. I also used the latest settings.ini file. When I start up MT, the TPS stays at 32% and the tack bounces between 0 and 8000. The MSQ seems to load ok, and I'm communicating, but most of the options are greyed out in the drop down boxes. I'm stumped. I went back to the v2.871 code and all is good. Do I need to do something different since this code also works for Microsquirt?

I've attached the MSQ in case that helps.

Thanks,
Patrick

FiatFreak,

You need to set the ECU type. Until you do this, the menus are grayed out, and the tach bounces between 0 and 8000 rpm.

The reason this needs to be set is that the MS-II and MicroSquirt have settings for which the defual can be damaging to the hardware on one or the other.

This is mentioned on the code page (as well as in Al's post above).

Lance.

FiatFreak wrote: I've been trying to get v2.88 to run in my MSII and something just doesn't seem right. I upgraded from the latest beta code (v2.871 I think) and stepped through the MSQ and am pretty sure nothing is missing. I also used the latest settings.ini file. When I start up MT, the TPS stays at 32% and the tack bounces between 0 and 8000.

You have just discovered the new "code selection" option, this is exactly what happens if the ECU "type" variable is not set.

In MegaTune, you will notice that all menus are grayed out, except for one, which allows you to set the ECU type (1 for MSII, 2 for MicroSquirt, I think, its listed on the menu). You put in the number that matches the hardware, perform the burn, and the code will spring to life. When you load in the code, this value defaults to 255, which is not a valid ECU, hence the tach bouncing up and down.

You only need to do this one time, it will then be in subsequent .msq files such that when you upgrade code when you reload the msq it will reset the value.

We had to make this selector in the code because there are two signal lines that are different b/w MS-II and uS, for MS-II these are the PWM current limit signals, for uS they are the second VR input channel and second ignition coil driver.

- Bruce

Doh! Don't know how I missed that one guys. I guess I assumed that the code differences were just for uS. Thanks for the quick response!

-Patrick-