There are two hardware versions of MegaSquirt-II™, and two corresponding code versions. ALL MS-II™ controllers sold since August 2005 are V2 (the vast majority of MS-II™s) have a blue solder mask and use the code and INI from the blue box below, as do all Microsquirt® controllers.

Older MS-II™s with the green solder mask use the code and INI from the green box further down the page.

The most recent 'ready to load' .s19 file and INI file for uploading to MegaSquirt-II™ is here: Monitor_v2.905.abs.s19 (Right click and 'Save As') megasquirt-II_2905.ini (Right click and 'Save As') Click this link for instructions to load this code. . v2.905 code requires TunerStudioMS code (or at least beta code 0.999.8d or higher). MegaTune will not work properly with this code. This is because with 2.905 code the user can now burn MAF tables, configure automatic CAN messages, and recognize 2.9xx as CAN enabled; these functions are not in MegaTune. For use with MShift™ code, v2.905 code requires MShift™ code version 2.100 or higher. Note that for 2.88x or higher code, the first thing you must do is set the ECU Type (under 'Fuel Set-Up/General') to match your hardware (MS-II™ or MicroSquirt™), the tuning software will not let you change anything else until you do this. Do not change settings, expect the stim to work, load an MSQ, etc., until you have set the ECU Type (MS-II™ = 1, MicroSquirt® = 2, the MS-II Sequencer™ will be 3). This setting applies to MS-II™ derivatives with code 2.88 or higher code only. ECU Type setting was inserted to head off the potential MicroSquirt® problems due to the coils being turned on with the old default configuration. As of the 2.88 code, if ECU Type is not set, the code will put the ignition outputs in a safe state (cycling the rpm from 0 to 8000 rpm, and also flashing the fuel pump LED) and wait until a known ECU type is put in by the user. Note that you will need to create a new MSQ by hand rather than rely on the tuning software to correctly interpret an old version (you can export/import the tables to save a lot of effort retyping the MSQ settings). Here is the help file for this code.

To load a 'ready to load' .S19 file to your MegaSquirt-II™ over the serial port, you need to use Eric Fahlgren's MegaSquirt-II downloader program (click the link to download), which works from either a window or from the command line. To use install new code using the downloader.exe: Power down MegaSquirt® EFI Controller, Put the boot jumper on both pins of the header marked B/LD (for "bootloader") on the MegaSquirt-II™ (not the main board), (on MicroSquirt® controllers, ground the bootloader wire) Power up MegaSquirt® (plug in the stim) or MicroSquirt® controller. The LEDs on MegaSquirt® will flash very briefly (if installed), then go out. This is proper response for the LEDs when the MegaSquirt-II goes into bootload mode (i.e. when the bootload jumper is on). Start the downloader program (make sure TunerStudioMS is not running), and select the appropriate COM port. Note that 'File/Update' does not work on the downloader to fetch the latest code and INI anymore. You can get the latest code and matching INI from this link: www.megamanual.com/ms2/code.htm Select the appropriate .S19 file using 'File/Open', and the downloader will read, write and verify the code to the processor in about 10 seconds or so. If you have a problem connecting to the controller, see the tips here: www.megamanual.com/connect.htm The process ends with a message like "Verification succeeded, 999 records total (4 skipped)." Shut down the downloader program. Remove power from MegaSquirt® (disconnect the stim) or MicroSquirt® controller. Remove the boot jumper (or put it on just one pin of the B/LD header for storage), Start the tuning software (TunerStudioMS) and set the COM port and speed if necessary. You will need to download and activate the latest INI file. Under the 'File/Project/Project Properties' of TunerStudio, click on the 'Other' check box. Click the 'Browse' button. Locate the INI file you downloaded for the link above (www.megamanual.com/ms2/code.htm). Click on the appropriate INI file you download from the code page (www.megamanual.com/ms2/code.htm) to activate it. You will find all recent the INI files here: http://www.megamanual.com/files/ini/ and the recent code S19 loadable files here: http://www.megamanual.com/files/code/ See the readme file in the package for more details. To use the v1.31 or v2.X code, see the configuration instructions here: www.megamanual.com/ms2/configure.htm For a full description of how the MS-II Serial Interface works see this link: www.megamanual.com/com/serial.htm Code for Older Green MS-II Daughter Cards The reason for two different codes is simple: to install CAN networking on the new MS-II™ we had to move the fuel and idle pins, since they were using the CAN pins as I/O. This does NOT mean any changes in wiring, because the new fuel and idle go to the same place on the motherboard. We are also using the C64 version of the processor, which has 4K of RAM vs. the 2K on the C32 (the C32 is the one populated on the V1 version of MS-II™). This has been the holdup for MS-II™, we have been waiting all this time for the automotive-temp version of the C64 to arrive, and this is what we have populated on the V2 version of MS-II™. The V2.0 code uses more than the 2K of RAM that the C32 had in order to get all of the CAN variables incorporated in the version 2 embedded code, so the C32 part used on the V1 version cannot handle this (without some condensing of variables, etc). This means you MUST install only v2.x software on the CAN MS2 and only v1.x software on non-CAN MS-II™. The real issue between the first released boards (the first 170 that were shipped in April 2005) and the ones from August 2005 and later is that the old boards did not have the CAN transceiver, the new version (V2) has CAN. But to use CAN, we had to move the signal lines on the processor for the fuel pump and fast idle - these happen to be the ones used for the CAN signals (CANH and CANL). So, to be able to use CAN (on V2 version), we had to move the fuel pump and fast idle to other spare I/O pins. This also affected the bootloader - this code has to make sure the fuel pump, injectors, ignition, etc, are off during a bootloader operation. Since the pins moved, we also had to move these as well in the bootloader. In fact, we are hand-programming each and every MegaSquirt-II® with the bootloader through the BDM, just to verify this operation and processor/board health. Users still need to put in the version 2 embedded code into the MS-II™ once they receive it (we do spot check boards with the full code). The best way to determine the MS-II™ version of any board is that the original boards had green LPI solder mask, where as the new V2 boards are now blue solder mask. So MegaSquirt-II version V1 is green, and the latest V2 (with CAN and the extra memory) is blue. The boards also have the "V2.0" or "V2.1" silkscreened onto the V1 boards and "V3.0" silk screened onto the V2 boards.

The MegaSquirt-II™ current release code for the V1 MS-II (with the green solder mask) is here: main_v1.34.c As well, a 'ready to load' .s19 file for uploading to V1 MegaSquirt-II™ is here: Monitor_v1.34.abs.s19 (Right click and 'Save As') The INI file for 1.34 code is numbered 1.31, and is found here: megasquirt-II.ini.1.31 The complete Codewarrior project file is here: MSII_V1_Proj.zip