MotoService

MotoHawk Control Solutions

Introduction

MotoService is a package of software used to distribute the following apps to vendors in one installation file. The components included in this package are as follows:

• MotoUpdate
• 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.

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.

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

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.

MotoTools Version FAQs

MotoTools does not support multiple versions installed simultaneously. For all MotoTools (MotoUpdate, MotoViewer, MotoTune, and MotoServer Runtime) 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 must be the same.

MotoService and Windows 8 Compatibility

MotoService is not currently compatible with Windows 8. This issue is being worked on, and will be fixed in a future release of MotoService.

MotoService Dongle and USB 3.0 Compatibility

We are working on USB 3.0 issue. 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 64Bit 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 64bit .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

I cannot open MotoService and I am getting a 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.

Another USB 3.0 workaround

Turn off the xHCI mode in your computers BIOS settings. By this, the super-speed of the USB 3.0 interface will throttle down to high-speed (USB 2.0), in our tests it ran perfectly. Most motherboards allow 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.

How do I create an MotoService install package for my Service Technicians

Download MotoService, unzip that file on your engineering machine, inside the zip it looked like:

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 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:

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).

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