MotoTune-FAQ: Difference between revisions

From NewEagleWiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:


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.
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 ===
=== 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:
The normal process for moving from one software build to the next (e.g. from MyApp_002.srz to MyApp_003.srz) is:


Line 14: Line 16:


: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
: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 ===
=== 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.
: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
: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
:3.  Program the ECU module with MyApp_003_(description).srz

Revision as of 17:18, 17 January 2010

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