MotoTune-FAQ

Connection Troubleshooting

The following should be checked if you have encountered communication problems with the controller.

1. With key-on, check for power at ECUP (pin F on the J-Box) and BATT, if applicable (pin A on the J-Box).

2. Check continuity between battery ground, the J-box ground and the ECU ground.

3. Check for the correct polarity on CAN wires. Pin J is CAN+ and pin K is CAN-.

4. Check for the appropriate port set-up under the Moto-Server icon.

5. If all of the above are set correctly, reset the Moto-Server by right-clicking on the satellite from the task bar and exiting. Close MotoTune, unplug the Kavaser USB connector from the CAN/USB hub and computer.

6. Restart MotoTune and plug the Kavaser USB back into the computer and the CAN/USB hub.

Adding a Port and setting the CityID

Communication problems can also arise when trying to communicate with two different controllers simultaneously. MotoTune uses an identifier called a CityID to identify the hardware online. In the model, the city ID is set under in the 'CAN ID' block.

MotoHawk CAN Definition Block

Follow these steps to add a new port location with a unique CityID:

1. Right click on the MotoServer Satellite icon on the task bar, right click on Ports.

2. The Ports Configuration will pop up and then click on 'Edit Names'.

3. A new window pops up labeled 'Port Name Mappings'. :4. Click on 'Add' and choose 'CAN Kingdom' and hit Next.

5. Give the new location a name (PCM-2 or PCM-B) and set the CityID. *Note: (Hex A == Dec 10, Hex B == Dec 11, Hex C == Dec 12, Hex D == Dec 13)

Port Configuration Procedure

Flashing Procedures

The ECM-0555-048-0710 (both -F and -C) will be used as an example.

Please note that if the dimensions of an array or map have changed, Transfer-Upgrade will need help in moving the table from one build .CAL file to the next. Transfer-Upgrade moves values from one .CAL file into another, by the VARDEC name only. If the VARDEC's attributes (dimensions, etc.) have changed, or the VARDEC is new or has been deleted, that info is shown as well.

TRANSFER-UPGRADE and SYNCHRONIZE

The normal process for moving from one software build to the next (e.g. from MyApp_002.srz to MyApp_003.srz) is:

1. Download calibration (desired settings) from module running old program, creating: MyApp_002_(description).cal

2. Create a template calibration file, either "from programming file" or by downloading from module running new program: MyApp_003_template.cal

3. Do a Transfer-Upgrade from MyApp_002_(description).cal into MyApp_003_template.cal, which copies, by VARDEC name, settings from the source .CAL into the destination .CAL. You get a chance to save into a new file: MyApp_003_(description).cal. The destination template tells MotoTune what settings exist to be transferred.

4. After programming an ECU module with the new program, open the upgraded calibration file MyApp_003_(description).cal in MotoTune. Go on-line (if opened off-line), right-click the calibration filename, and select "Synchronize" to synch disk (file) contents with ECU contents.

PLEASE NOTE: if there are calibration file settings that are stored in FLASH memory (instead of EEPROM non-volatile memory), those will cause an error message about not being able to change and asking if ECU is a production FLASH module. If you are trying to change settings stored in FLASH (typical calibration setting not set as Volatile or NonVolatile memory storage), then you will need to MERGE the upgraded calibration file back into the new .SRZ program (making the , and re-flash the ECU module with the new, transfer-upgraded calibration

MERGE and Re-flash

1. Take the MyApp_003_(description).cal file and the MyApp_003.srz file. Use File-->Merge, or the Merge button, or (when calibration file is open, off-line) right-click on calibration filename and choose Merge.

2. Merge the calibration file into the .SRZ file. This will make the calibration settings in the .CAL file become the factory default settings in the .SRZ file. Save the resulting file: MyApp_003_(description).srz

3. Program the ECU module with MyApp_003_(description).srz

Installation Procedure

To install MT/MSR 8.13.7.118, the MotoTune developer team recommends:

1. Exit all open MotoTune (and MATLAB / MotoHawk) sessions.

2. Using Windows Task Manager, check for any "mnfeature.exe" processes running; if so, kill with "End Process".

3. Using Windows Add / Remove Programs, uninstall: MotoTune

4. Using Windows Add / Remove Programs, uninstall: MotoServerRuntime

5. Delete folder "C:\Program Files\Common Files\MotoTron\Server\" (this deletes files "mnfeature.exe" and "mnfeatureps.dll")

6. Unzip the contents of the respective new installer zipfiles into a temporary directory. (MotoServerRuntime now has a helper folder "ISSetupPrerequisites" that must be in the same folder as the installer .EXE file when you run it.)

7. Install: MotoServerRuntime (as administrator, on Windows Vista machines)

8. Install: MotoTune (as administrator, on Windows Vista machines)

Licensing

To update your tokens, please send the token serial number and license transaction file for each token to: mcslicense@woodward.com.

To see serial number information (requires MotoServerRuntime 8.13.6.73 or later). 1. Start MotoTune (to start MotoServerRuntime (antenna dish in lower right corner). 2. Right-click antenna dish, choose "About MotoServer" 3. Choose "License Info" 4. Choose "Token Info" (this info may be CTRL-V pasted into an email)

Use LicenseUpdate (Start, All Programs, MotoTools, LicenseUpdate) to create transaction file.