Click on our menu buttons immediately below to find MegaSquirt® information quickly:

MegaShift™ V2 Settings

This page is obsolete. The help file for the latest full release code is here: V41tune.html - Aug. 15, 2014

V2 MegaShift™ code is the latest release code for controlling automatic transmissions using the GPIO board form Bowling and Grippo. This code has:

Jump to the: Set-Up and Tuning Parameters.

The Windows 9x/ME/XP/Vista software applications you use to tune and configure your MegaShift™ hardware are called TunerStudio by Phil Tobin. You also need a laptop or notebook computer and a conventional serial port (or USB-serial adapter) to communicate with MegaShift™.

CAN Pass-Through

To set up TunerStudio to use MShift™ with CAN from MS-II™:

  1. First set the MS-II™ up normally under Project Properties (if you haven't already set up a controller for your engine controller):

    1. Give your project a name and description,
    2. Select the INI to match the firmware on your primary controller (MS-II™, MicroSquirt®, Sequencer™, etc.). You can either:
      • use a 'pre-defined' firmware from the drop-down list, or
      • click 'Other' and browse to a specific INI file.
    3. Click "OK".

  2. Then set up the MShift™ GPIO controller under 'CAN devices' of the engine controller project:

    For example, if you have a Project that has an MS-II™ as the main controller you will connect the laptop to, and a GPIO board with MShift™ as a CAN device with the CAN ID set to 1 (the default), only GPIO board goes in CAN Devices list and the CAN ID should be set to 1.

    1. Device Identifier (short): Give your CAN controller a short name. This will preface the menu entries as they drop down in TunerStudio so you always know which controller you are working with when you change parameters in the menus.

    2. Device description: This is a longer description to remind you of the configuration you are setting.

    3. Device CAN ID: The CAN ID for the MShift™ code has a default value of 1. You can change the CAN ID in the menus to a value up to 13 to avoid conflicts with other CAN devices - if you do change the MShift™ CAN ID you must also change it to the same new value under 'File/Project Properties/CAN Devices'.

    4. Device Configuration File: You will have to set the 'Device Configuration File' to point the GPIO.ini file for MShift™ (you can download the file from the link for V2.000 code). Note that you can select another file at any time to update the INI (re-start TunerStudioMS to see the new INI), you don't have to remove the CAN Device and then re-create it. If You are updating both the code and the INI, then you also have to reload the code on the MShift™ GPIO board using its serial connection, of course.

    5. Configuration Settings: Be sure to 'Activate' CAN_COMMANDS in the 'Configuration Setting' section of the CAN Devices dialog. This activates the use of CAN pass-through mode for TunerStudio.

Here is a video on setting up CAN in TunerStudioMS: CAN set-up video (22 MBytes)

There is more on the CAN pass-through here:, including assembly and wiring instructions, etc.

Set-Up and Tuning Parameters

The following is a list of of all the tuning parameters in the MShift™ software, and each has a description of how that parameter is used. Pressing F1 at any menu in the tuning software while connected to the internet will take you directly to the corresponding spot in this file.

Note: DO NOT power off the MShift™/GPIO board while the 'Flash Burn' indicator is active. Doing so *will* corrupt your settings. Wait a second or two for the burn to complete before powering down the board.

1 'Bit banging' means the port is turned off and on by specific instructions in the code that occur within normal program flow. In MShift™ the chance to turn these outputs off and on occurs every 1/8th of a millisecond. The alternative is to use timer channels. These are built in processor hardware devices that allows the user to set the PWM frequency and duty cycle, and the hardware handles the PWM switching independently of the program code. This not only reduces computational overhead, but can be switched an much higher (or lower speeds) and is also is much more accurate.

MegaSquirt® and MicroSquirt® controllers are experimental devices intended for educational purposes.
MegaSquirt® and MicroSquirt® controllers are not for sale or use on pollution controlled vehicles. Check the laws that apply in your locality to determine if using a MegaSquirt® or MicroSquirt® controller is legal for your application.
© 2010, 2012 Bruce Bowling and Al Grippo. All rights reserved.