MotoService: Difference between revisions

From NewEagleWiki
Jump to navigation Jump to search
 
(112 intermediate revisions by 8 users not shown)
Line 1: Line 1:
==Introduction==
{{Navigation}} [[MotoHawk-Platform | MotoHawk Platform]] > '''MotoService'''
MotoService is used to distribute the following apps to vendors in one installation file:


*MotoUpdate
=Introduction=
*MotoViewer
*MotoServer Runtime
*KVASER driver installation


The install may be customized by placing an ECUFiles folder in the same directory as the Setup.exe. The ECUFiles folder will copy the contents of the folders (displays (.dis), TDBDLL (.dll), and Updates(.mfu)) into the target installations disks' ECUFiles folder. It should be noted that it will copy to the local disk only when distributed via a removable drive or zip archive.  
MotoService consists of two powerful applications in one package. MotoService combines MotoViewer which is an economical display and diagnostic tool and MotoUpdate for field flashing of electronic control units. MotoService is used to distribute the following two apps to vendors in one installation file.


The PortInfo.cfg file can be customized to add specific ports to the installation. The PortInfo.cfg file should be placed in the ECUFiles folder in the installation directory. This enables the distributors of MotoService to package their own CD or zip archive for distribution to vendors.  
=MotoViewer=
[[File:MotoViewer0.jpg|right|300px|thumb|MotoViewer]]
'''[[MotoViewer]]''' provides an economical solution for basic ECM data and diagnostic needs.


[[MotoUpdateAuthor]] is used to generate and maintain MotoUpdate (.mfu) files.
'''Key Features''':
* Graphical data logging
* Detailed fault diagnostic list
* View ECM fault history
* Clear active and historic faults
* View engine runtime hours
* View engine sensor data
* Chart option to graph data
* Extensive use of Microsoft GUI standards to promote user familiarity
* Comprehensive online help system


==MotoUpdate==
=MotoUpdate=
MotoUpdate™ is MotoTron's PC-based, end-of-line module upgrade tool. It provides end-users the ability to upgrade a module while out in the field. MotoUpdate™ is capable of upgrading any module within MotoTron's product range that has production software pre-installed. Upgrading a module in the field is a more convenient and quicker way than returning the module to have it reprogrammed.
[[File:MU_welcome.JPG|right|300px|thumb|MotoUpdate]]
The '''[[MotoUpdate]]''' tool provides an easy solution for reprogramming ECMs in the field or service shop.  


[[Image:MU_welcome.JPG]]
'''Key Features:'''


'''Note:''' MotoUpdate™ can only be used with the correct license on a supplied dongle. If a licensed dongle is found, the licensee name will be displayed on the bottom left-hand corner of the application.
* User friendly application — limited PC experience required to operate
* Allow field/service personnel to update an ECM when new calibrations are required
* Simple one-step process
* Save time and money by updating the ECM on site.
* Easy-to-use application
* Operator friendly: requires basic computer skills to initiate the programming download to ECM
* Programming file can be configured to only allow reprogramming based on previous software ID eligibility
* Includes a detailed user-information update readme file authored by authorized engineering staff


===About MotoUpdate™ ===
=MotoUpdateAuthor=
Left click the MotoUpdate™ icon on the top left-hand corner of the window and select About MotoUpdate™ to view application and driver version.MotoUpdate is an easy to use application to ensure simple and straightforward upgrading of modules in the field.
[[File:MUA_screenshot.png|right|300px|thumb|MotoUpdateAuthor]]
'''[[MotoUpdateAuthor]]''' is used to generate and maintain MotoUpdate (.mfu) files.


'''Location'''
=Downloads=


Click on the drop down menu to select the specific module you wish to upgrade. Should the specific module not appear on the menu list, the specific module needed has to be configured through MotoServer™. See Port Configuration for details.
'''MotoService'''


'''Exit'''
{| class="wikitable" style="text-align: center;" cellpadding = "5"


Click Cancel to close the MotoUpdate™ application.  Note: MotoServer™ has to be manually closed after MotoUpdate has been closed. See MotoServer™ for details.
!scope="col" style = "width:200px;"|Product     
!scope="col" style = "width:200px;"|Downloads
!scope="col" style = "width:200px;"|Notes


'''Next'''
|-
|MotoService 10.0.0.265
|rowspan="12"|
'''[[MotoService_Downloads|Download]]'''
|For new silver dongles only
|-
|MotoService 10.0.0.253
|For new silver dongles only
|-
|MotoService 10.0.0.244
|For new silver dongles only
|-
|MotoService 10.0.0.240
|For new silver dongles only
|-
|MotoService 8.13.8.207
|'''-'''
|-
|MotoService 8.13.7.192
|'''-'''
|-
|MotoService 8.13.7.140
|'''-'''
|-
|MotoService 8.13.7.120
|'''-'''
|}


Click Next to view the module’s Upgrade Options. MotoUpdate™ will now access the module to determine the Software ID for the software programmed onto the module.


===Upgrade Options===
'''MotoUpdateAuthor'''


[[Image:MU_upgrade.JPG]]
{| class="wikitable" style="text-align: center;" cellpadding = "5"


Once MotoUpdate™ has determined the Software ID, the suitable upgrade options will be displayed in a window.
!scope="col" style = "width:200px;"|Product     
!scope="col" style = "width:200px;"|Downloads
!scope="col" style = "width:200px;"|Notes
|-
|MotoUpdateAuthor 10.0.0.253
|rowspan="5"|
'''[[MotoUpdateAuthor Downloads|Download]]'''
|For new silver dongles only
|-
|MotoUpdateAuthor 10.0.0.244
|For new silver dongles only
|-
|MotoUpdateAuthor 10.0.0.240
|For new silver dongles only
|-
|MotoUpdateAuthor 8.13.7.120
|'''-'''
|}


'''Calibration ID'''
=Purchase=


This is the unique calibration ID for the upgrade calibration patch that is available to the module. MotoUpdate™ matches the Software ID with the Calibration ID to determine compatibility. The location where the upgrade calibration patch is found is also displayed.
{| class="wikitable" style="text-align: center;" cellpadding = "5" 
!scope="col" style = "width:250px;"|Product
!scope="col" style = "width:250px;"|Part Number         
!scope="col" style = "width:250px;"|Webstore


'''Details'''  
|-
|MotoService only
|ASM-MSVC-003A
|'''[https://store.neweagle.net/shop/products/software/motohawk/motoservice/motoservice-kit-no-usb-to-can/ Purchase]
|-
|MotoService kit <br/> (includes single-channel USB-to-CAN interface)
|ASM-MSVC-003A-1
|'''[http://store.neweagle.net/shop/products/software/motohawk/motoservice/motoservice-kit-single-channel-usb-can/ Purchase]
|-
|MotoService kit <br/> (includes dual-channel USB-to-CAN interface)
|ASM-MSVC-003A-2
|'''[http://store.neweagle.net/shop/products/software/motohawk/motoservice/motoservice-kit-dual-channel-usb-can/ Purchase]
|-
|MotoService kit <br/> (includes galvanic, dual-channel USB-to-CAN interface)
|ASM-MSVC-003A-2G
|'''[http://store.neweagle.net/shop/products/software/motohawk/motoservice/motoservice-kit-dual-channel-galvanic-usb-can/ Purchase]
|-
|MotoService kit <br/> (includes single-channel USB-to-CAN interface)
|ASM-MSVC-003A-3
|'''[http://store.neweagle.net/shop/products/software/motohawk/motoservice/motoservice-kit-oem-leaf/ Purchase]
|}


Click Details to view Upgrade Details of the upgrade calibration patch found.
= Frequently Asked Questions (FAQ) =


'''Back'''
==Can MotoService be installed on a computer with MotoTune?==
No, MotoTools does not support multiple versions installed simultaneously. For all MotoTools (MotoUpdate, MotoViewer, MotoTune and MotoServerRuntime) the user should have only one version installed. It is recommended to use Windows Add/Remove programs to uninstall the older version before starting a new installation. Also, the versions of MotoTune, MotoService and MotoServerRuntime must all be the same.


Click Back to back up to previous window – MotoUpdate main window.
== Is MotoService compatible with Windows 8?==
No, MotoService is not currently compatible with Windows 8.


'''Next'''
== Is the MotoService Dongle compatible with USB 3.0?==


Click Next to begin upgrading the module. This is a very crucial step in the upgrading process and a pop-up warning window (Fig.3) will appear.
This problem is caused by an error in the Windows 7 driver of the USB 3.0 controller which does not treat some USB commands correctly according to the USB specifications.


'''Warning Window'''
However, independent from updates from Intel, we are currently testing a new driver version for the CRYPTO-BOX with a workaround for this USB 3.0 problem. If you want to test this driver, please download it here: www.marx.com/ftp/temp/USB3/CBU_Test_Drv_21Jan2013.zip


It is very important that there are no interruptions to the upgrading process as it will render the module unusable. A “dead” module can only be resurrected by returning to your distributor to be reprogrammed.  
IMPORTANT: The driver should work fine but is currently not yet digitally signed! To install it under Windows 7 64-bit versions, you have to restart the computer and hit the F8 key multiple times before Windows starts. Then choose "Disable Driver Signature Enforcement". This has to be done each time Windows starts when using this driver. We will offer a WHQL certified version of the driver as soon as we have finished testing and passed certification procedure. Make sure that you have plugged in the CRYPTO-BOX. Unzip the driver package. Open the Device Manager, right-click on the "CBUSB ver 2.0" device and choose "Update Driver Software" -> "Browse my computer for driver software" -> "Let me pick from a list of device drivers on my computer" -> "Have Disk". Now select the corresponding 32- or 64-bit .INF file from the driver package and click "OK". If Windows says that the driver is not signed, choose that you want to install the driver anyway.


===Upgrade Details===
'''Another USB 3.0 Workaround'''


[[Image:MU_upgrade_det.JPG]]
Turn off the xHCI mode in your computer's BIOS settings. This will cause the super-speed of the USB 3.0 interface to throttle down to high-speed (USB 2.0); in our tests it ran perfectly. Most motherboards allow you to disable the xHCI mode in the BIOS selectively to individual USB 3.0 ports, so you can still use the other ports at full speed.


The upgrade calibration patch contains the unique calibration ID to be matched with the suitable version of software.
==Why do I see an "XML load error"?==
[[image: Motoservice_error.JPG]]


'''Calibration ID'''
This error is caused when .net framework 4.0 becomes corrupted or deleted. Re-install .net framework 4.0 to fix the issue. The .net framework is freely available for download on the web.


This is the unique calibration ID for the upgrade calibration patch that is available to the module.
== How do I create a MotoService install package for my service technicians? ==


'''Software ID '''
Download '''[http://www.neweagle.net/support/wiki/docs/RequiredFiles/MotoService_RELEASE_8_13_7_120.zip MotoService]''', and unzip that file on your engineering machine. Inside, the zip will look like this:


This is the ID assigned to a particular version of software. Only compatible calibrations can be used with each version of software. MotoUpdate™ will try and match the Software ID found on the module with the Software ID on the upgrade calibration patch.
[[File:motoservice_unzip1.jpg]]
 
'''Comments'''
 
This provides a description for this upgrade calibration patch.
 
'''OK'''
 
Click OK to back up to previous window – Upgrade Options window.
 
===Programming the module===
[[Image:MU_prog.JPG]]
 
MotoUpdate™ will now proceed with the upgrading.
First it will look for the module on the specified location. Once the module is found, MotoUpdate™ will begin programming the upgrade calibration patch onto the module.The programming process should take less than 1 minute using the CAN bus, slightly longer if using serial bus.
 
[[Image:MU_finish.JPG]]
 
Once programming is complete, you will be given the option of upgrading another module or the quit MotoUpdate™ application. Click Finish to quit the application. Check the Upgrade again option and click Next to proceed to upgrading another module.
 
===Troubleshooting===
Most commonly occurring problems you may come across are caused by synchronization or connection problems between MotoUpdate™ and the module while programming the module.
 
[[Image:MU_error.JPG]]
 
Below are a few things you can check to rectify these problems.
 
*Check that the module has been powered up.
*Check that the USB-to-CAN cable has been connected properly.
*Check the Port Configuration of MotoServer has been configured properly.
*Check if you have a licensed dongle and it has been plugged properly into the USB port. (Moving the mouse pointer over the *MotoServer icon on the icon tray will determine if the dongle is plugged properly and that you have a licensed dongle)
*Close both the MotoServer and MotoUpdate™, then restart MotoUpdate™. (MotoServer will restart automatically once you reopen MotoUpdate™)
 
==MotoViewer™==
MotoViewer™ is MotoTron's PC-based display tool and provides all of the functionality needed for parameters in a MotoTron module. A user friendly, intuitive MS Windows-based display interface provides the user with easy access to all of the display-related RAM and ROM parameters contained in a MotoTron control unit.
 
MotoViewer™ consists of a basic window with a Menu Bar, a Display Area and a Status Bar. Any displays which are opened will be placed in the Display Area. Remember that for MotoViewer™ to work, you must have a licensed dongle plugged into the computer. See Troubleshooting if licensee name does not show up.
 
'''Main Window'''
This is the main window with the Menu Bar, Display Area and Status Bar:
 
[[Image:MV_main_win.JPG]]
 
 
===Using MotoViewer===
 
When you open MotoViewer™ through the display shortcut on the desktop, MotoViewer™ should open with the selected display on the screen. The display will be populated with display parameters for the connected module.
If there is no display shortcut on the desktop, you will need to first open MotoViewer™ independently.
Once MotoViewer™ is opened, click on File on the Menu Bar and select Open from the sub-menu. You can also make use of the default shortcut key by typing Alt+O. Select the required display file to open a display.
Another way to open a display is to click on File from the Menu Bar and move the mouse pointer over Recent Display. A list of recently opened display should now pop out. This is a much faster way of opening displays which you have been viewing recently.
 
'''About MotoViewer™'''
Click the Help on the Menu Bar and select About MotoViewer to view application and driver version.
 
'''Menu Bar'''
 
The Menu Bar consists of the File, View, Tools and Help menus.   
 
'''Display Area'''
 
The Display Area is where all opened displays will be placed. You also have the ability to  customize the background of the Display Area. See Display Options for details.
 
'''Status Bar'''
 
The Status Bar will display the current status of the connected module. Click on View from Menu Bar to click on Status Bar to display or hide the bar.
 
'''Toolbars'''
 
Additional toolbars can be easily added by using the Customize option.
 
'''Display Options'''
 
[[Image:MV_disp_opt.JPG]]
 
Click on View on the Menu Bar. Select Options from the sub-menu to access the Display Options. You can also right-click on the Display Area and select Options from the menu that pops up.
 
'''Preferences'''
 
Click on File from the Menu Bar and select Preferences from its sub-menu. From the Preferences window, you will have access to the Locations and General tabs. From the Locations tabs you can change the locations of both the log files and the folder where all display files are found. From the General tab, you can reset the toolbars and Workspace.
 
===Customizing the Toolbar===
 
[[Image:MV_toolbar.JPG]]
 
'''Toolbars Tab''' allows you to add, rename, delete and reset toolbars. There are not default toolbars so all toolbars will have to be created from scratch.
 
'''The Commands Tab''' allows you to drag and drop the various built-in commands or menus onto any existing toolbars on the main window. The commands are divided into the following 4 different categories:
*File
*View
*Tools
*Help
 
'''The Keyboard Tab''' allows you to Assign, Remove or Reset All shortcut keys to commands.
 
'''The Tools Tab''' gives you the powerful ability to add a quick-launch button to bring up other useful tools from within MotoViewer™.
 
'''The Options tab''' will feature settings and options for you to personalize the various toolbars and menus. These features are divided to 2 sub-sections: Personalized Menus and Toolbars, Other.
 
===Troubleshooting===
Most commonly occurring problems you may come across are caused by synchronization or connection problems between MotoViewer™ and the module while programming the module. Below are a few things you can check to rectify these problems.
*Check that the module has been powered up.
*Check that the USB-to-CAN cable has been connected properly.
*Check the port configuration of MotoServer has been configured properly.
*Check if you have a licensed dongle and it has been plugged properly into the USB port. (Moving the mouse pointer over the MotoServer icon on the icon tray will determine if the dongle is plugged properly and that you have a licensed dongle)
*Close both the MotoServer and MotoViewer™, then restart MotoViewer™. (MotoServer will restart automatically once you reopen MotoViewer™)


==MotoService FAQs ==
=== What are the minimum PC system requirements for [[MotoService]]? ===
The official requirments are stated as:
*Pentium® III 667 MHz PC
*256 MB of RAM
*Windows® XP SP2 and Vista or greater
[[MotoService]] (which is [[MotoViewer]] and [[MotoUpdate]]) has been used successfully on 'Windows 7 x64' as well.
=== How do I create an MotoService install package for my Service Technicians ===
Download [http://www.neweagle.net/support/wiki/docs/RequiredFiles/MotoService_RELEASE_8_13_7_120.zip MotoService], unzip that file on your engineering machine, inside the zip it looked like:
[[File:motoservice_unzip1.jpg]]


Inside 'ecufiles', add 'Programs' and 'TDBDLL', so it looks like:
Inside 'ecufiles', add 'Programs' and 'TDBDLL', so it looks like:
Line 201: Line 166:
[[File:motoservice_unzip2.jpg]]
[[File:motoservice_unzip2.jpg]]


You can add any srz's or [[MotoTune]] dll's that are needed for your customers, you might want to add a 'Displays' folder too, with any [[MotoTune]] displays your service technicians will need.
 
You can add any MFU's or '''[[MotoTune]]''' dll's that are needed for your customers. You might want to add a 'Displays' folder, too, with any MotoTune displays your service technicians will need.


You can edit PortInfo.cfg to add/remove ports (these will be added/removed on the installed machine).
You can edit PortInfo.cfg to add/remove ports (these will be added/removed on the installed machine).
Line 209: Line 175:
The example above will make it so that your customer has just PCM-1 on the machine after running the installer.
The example above will make it so that your customer has just PCM-1 on the machine after running the installer.


After these steps were complete, move the whole folder to a thumb drive (you might burn to a CD) and then install on new machine, running 'MotoService RELEASE 8.13.7.120.exe' from the thumb drive. Do not zip up the files, simply copy the whole directory out to the thumb drive (or burn to CD). See below:
 
After these steps are complete, move the whole folder to a thumb drive (you might burn it to a CD) and then install on a new machine, running 'MotoService RELEASE 8.13.7.120.exe' from the thumb drive. Do not zip up the files, simply copy the whole directory out to the thumb drive (or burn to CD). See below:


[[File:motoservice_thmb.jpg]]
[[File:motoservice_thmb.jpg]]


When installed on a clean machine, you should see that the ECUFiles is replicated in the C:\ECUFiles\ folder required for the tools to connect to the ECU, and only port PCM-1 is available (with the example above).
When installed on a clean machine, you should see that the ECUFiles is replicated in the C:\ECUFiles\ folder required for the tools to connect to the ECU, and only port PCM-1 is available (like the example above).
 
=== What is a recommended hardware set-up for production module programming ===
*Set-up a test bench
*Dedicate a power supply and PC
*Use an anti-static pad
*Maintain some type of data base for version control including software and calibrations
*Create and Label the ECUs
*Pack and ship in an appropriate container

Latest revision as of 19:41, 9 March 2023

New Eagle > Products Wiki > MotoHawk Platform > MotoService

Introduction

MotoService consists of two powerful applications in one package. MotoService combines MotoViewer which is an economical display and diagnostic tool and MotoUpdate for field flashing of electronic control units. MotoService is used to distribute the following two apps to vendors in one installation file.

MotoViewer

MotoViewer

MotoViewer provides an economical solution for basic ECM data and diagnostic needs.

Key Features:

  • Graphical data logging
  • Detailed fault diagnostic list
  • View ECM fault history
  • Clear active and historic faults
  • View engine runtime hours
  • View engine sensor data
  • Chart option to graph data
  • Extensive use of Microsoft GUI standards to promote user familiarity
  • Comprehensive online help system

MotoUpdate

MotoUpdate

The MotoUpdate tool provides an easy solution for reprogramming ECMs in the field or service shop.

Key Features:

  • User friendly application — limited PC experience required to operate
  • Allow field/service personnel to update an ECM when new calibrations are required
  • Simple one-step process
  • Save time and money by updating the ECM on site.
  • Easy-to-use application
  • Operator friendly: requires basic computer skills to initiate the programming download to ECM
  • Programming file can be configured to only allow reprogramming based on previous software ID eligibility
  • Includes a detailed user-information update readme file authored by authorized engineering staff

MotoUpdateAuthor

MotoUpdateAuthor

MotoUpdateAuthor is used to generate and maintain MotoUpdate (.mfu) files.

Downloads

MotoService

Product Downloads Notes
MotoService 10.0.0.265

Download

For new silver dongles only
MotoService 10.0.0.253 For new silver dongles only
MotoService 10.0.0.244 For new silver dongles only
MotoService 10.0.0.240 For new silver dongles only
MotoService 8.13.8.207 -
MotoService 8.13.7.192 -
MotoService 8.13.7.140 -
MotoService 8.13.7.120 -


MotoUpdateAuthor

Product Downloads Notes
MotoUpdateAuthor 10.0.0.253

Download

For new silver dongles only
MotoUpdateAuthor 10.0.0.244 For new silver dongles only
MotoUpdateAuthor 10.0.0.240 For new silver dongles only
MotoUpdateAuthor 8.13.7.120 -

Purchase

Product Part Number Webstore
MotoService only ASM-MSVC-003A Purchase
MotoService kit
(includes single-channel USB-to-CAN interface) 		ASM-MSVC-003A-1 Purchase
MotoService kit
(includes dual-channel USB-to-CAN interface) 		ASM-MSVC-003A-2 Purchase
MotoService kit
(includes galvanic, dual-channel USB-to-CAN interface) 		ASM-MSVC-003A-2G Purchase
MotoService kit
(includes single-channel USB-to-CAN interface) 		ASM-MSVC-003A-3 Purchase

Frequently Asked Questions (FAQ)

Can MotoService be installed on a computer with MotoTune?

No, MotoTools does not support multiple versions installed simultaneously. For all MotoTools (MotoUpdate, MotoViewer, MotoTune and MotoServerRuntime) the user should have only one version installed. It is recommended to use Windows Add/Remove programs to uninstall the older version before starting a new installation. Also, the versions of MotoTune, MotoService and MotoServerRuntime must all be the same.

Is MotoService compatible with Windows 8?

No, MotoService is not currently compatible with Windows 8.

Is the MotoService Dongle compatible with USB 3.0?

This problem is caused by an error in the Windows 7 driver of the USB 3.0 controller which does not treat some USB commands correctly according to the USB specifications.

However, independent from updates from Intel, we are currently testing a new driver version for the CRYPTO-BOX with a workaround for this USB 3.0 problem. If you want to test this driver, please download it here: www.marx.com/ftp/temp/USB3/CBU_Test_Drv_21Jan2013.zip

IMPORTANT: The driver should work fine but is currently not yet digitally signed! To install it under Windows 7 64-bit versions, you have to restart the computer and hit the F8 key multiple times before Windows starts. Then choose "Disable Driver Signature Enforcement". This has to be done each time Windows starts when using this driver. We will offer a WHQL certified version of the driver as soon as we have finished testing and passed certification procedure. Make sure that you have plugged in the CRYPTO-BOX. Unzip the driver package. Open the Device Manager, right-click on the "CBUSB ver 2.0" device and choose "Update Driver Software" -> "Browse my computer for driver software" -> "Let me pick from a list of device drivers on my computer" -> "Have Disk". Now select the corresponding 32- or 64-bit .INF file from the driver package and click "OK". If Windows says that the driver is not signed, choose that you want to install the driver anyway.

Another USB 3.0 Workaround

Turn off the xHCI mode in your computer's BIOS settings. This will cause the super-speed of the USB 3.0 interface to throttle down to high-speed (USB 2.0); in our tests it ran perfectly. Most motherboards allow you to disable the xHCI mode in the BIOS selectively to individual USB 3.0 ports, so you can still use the other ports at full speed.

Why do I see an "XML load error"?

This error is caused when .net framework 4.0 becomes corrupted or deleted. Re-install .net framework 4.0 to fix the issue. The .net framework is freely available for download on the web.

How do I create a MotoService install package for my service technicians?

Download MotoService, and unzip that file on your engineering machine. Inside, the zip will look like this:


Inside 'ecufiles', add 'Programs' and 'TDBDLL', so it looks like:


You can add any MFU's or MotoTune dll's that are needed for your customers. You might want to add a 'Displays' folder, too, with any MotoTune displays your service technicians will need.

You can edit PortInfo.cfg to add/remove ports (these will be added/removed on the installed machine).

The example above will make it so that your customer has just PCM-1 on the machine after running the installer.


After these steps are complete, move the whole folder to a thumb drive (you might burn it to a CD) and then install on a new machine, running 'MotoService RELEASE 8.13.7.120.exe' from the thumb drive. Do not zip up the files, simply copy the whole directory out to the thumb drive (or burn to CD). See below:

When installed on a clean machine, you should see that the ECUFiles is replicated in the C:\ECUFiles\ folder required for the tools to connect to the ECU, and only port PCM-1 is available (like the example above).

Retrieved from "https://wiki.neweagle.net//index.php?title=MotoService&oldid=32909"