MotoUpdate: Difference between revisions

From NewEagleWiki
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
[[File:MU_welcome.JPG|right|300px|thumb|MotoUpdate]]
[[File:MU_welcome.JPG|right|300px|thumb|MotoUpdate]]
=Introduction=
=Introduction=
MotoUpdate is MotoTron's PC-based, end-of-line/field-service module upgrade tool. It is included as part of the '''[[MotoService]]''' package. MotoUpdate 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.
MotoUpdate is MotoTron's PC-based, end-of-line/field-service module upgrade tool. It is included as part of the '''[[MotoService]]''' package. MotoUpdate 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 more convenient and quicker than returning the module to have it reprogrammed.


=Using MotoUpdate=
=Using MotoUpdate=
Line 21: Line 21:
'''Next'''
'''Next'''


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.
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===
===Upgrade Options===
Line 39: Line 39:
'''Back'''
'''Back'''


Click Back to back up to previous window – MotoUpdate main window.
Click Back to back up to the previous window – the MotoUpdate main window.


'''Next'''
'''Next'''
Line 47: Line 47:
'''Warning Window'''
'''Warning Window'''


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.
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 it to your distributor to be reprogrammed.


===Upgrade Details===
===Upgrade Details===
Line 61: Line 61:
'''Software ID '''
'''Software ID '''


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


'''Comments'''
'''Comments'''
Line 69: Line 69:
'''OK'''
'''OK'''


Click OK to back up to previous window – Upgrade Options window.
Click OK to back up to the previous window – the Upgrade Options window.


===Programming the module===
===Programming the Module===
[[Image:MU_prog.JPG]]
[[Image:MU_prog.JPG]]


MotoUpdate™ will now proceed with the upgrading.
MotoUpdate will now proceed with the upgrade. 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 one minute using the CAN bus, slightly longer if using serial bus.
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]]
[[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.
Once the programming is complete, you will be given the option of upgrading another module or quitting the MotoUpdate application. Click Finish to quit the application. Check the Upgrade Again option and click Next to proceed to upgrading another module.


===Troubleshooting===
===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.  
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]]
[[Image:MU_error.JPG]]
Line 90: Line 89:
*Check that the module has been powered up.  
*Check that the module has been powered up.  
*Check that the USB-to-CAN cable has been connected properly.  
*Check that the USB-to-CAN cable has been connected properly.  
*Check the Port Configuration of MotoServer has been configured properly.  
*Check that 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)  
*Check if you have a licensed dongle and it has been plugged properly into the USB port. (Moving the mouse cursor over the MotoServer icon on the icon tray will determine if the dongle is plugged in 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™)
*Close both MotoServer and MotoUpdate, then restart MotoUpdate. (MotoServer will restart automatically once you reopen MotoUpdate.)

Latest revision as of 15:49, 2 March 2023

New Eagle > Products Wiki > MotoHawk Platform > MotoService > MotoUpdate

MotoUpdate

Introduction

MotoUpdate is MotoTron's PC-based, end-of-line/field-service module upgrade tool. It is included as part of the MotoService package. MotoUpdate 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 more convenient and quicker than returning the module to have it reprogrammed.

Using MotoUpdate

Note: MotoUpdate can only be used with the correct license on a supplied dongle. If a licensed dongle is found, the licensee's name will be displayed on the bottom left-hand corner of the application.

Left click the MotoUpdate icon on the top left-hand corner of the window and select About MotoUpdate to view the application and driver version. MotoUpdate is an easy-to-use application to ensure simple and straightforward upgrading of modules in the field.

Location

Click on the dropdown 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.

Exit

Click Cancel to close the MotoUpdate application. Note: MotoServer has to be manually closed after MotoUpdate has been closed.

Next

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

Once MotoUpdate has determined the software ID, the suitable upgrade options will be displayed in a window.

Calibration ID

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.

Details

Click Details to view Upgrade Details of the upgrade calibration patch found.

Back

Click Back to back up to the previous window – the MotoUpdate main window.

Next

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.

Warning Window

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 it to your distributor to be reprogrammed.

Upgrade Details

The upgrade calibration patch contains the unique calibration ID to be matched with the suitable version of software.

Calibration ID

This is the unique calibration ID for the upgrade calibration patch that is available to the module.

Software ID

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.

Comments

This provides a description for this upgrade calibration patch.

OK

Click OK to back up to the previous window – the Upgrade Options window.

Programming the Module

MotoUpdate will now proceed with the upgrade. 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 one minute using the CAN bus, slightly longer if using serial bus.

Once the programming is complete, you will be given the option of upgrading another module or quitting the 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.

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 that 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 cursor over the MotoServer icon on the icon tray will determine if the dongle is plugged in properly and that you have a licensed dongle.)
  • Close both MotoServer and MotoUpdate, then restart MotoUpdate. (MotoServer will restart automatically once you reopen MotoUpdate.)