MotoTune Conflict: Difference between revisions
Jump to navigation
Jump to search
| (14 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
You may run into issues with [[MotoTune | You may run into issues with [[MotoTune|'''MotoTune''']]'s CAN messaging conflicting with other CAN communications in your system. It is possible to change the CAN IDs on which MotoTune communicates to avoid this. This <noinclude>article</noinclude><includeonly>section</includeonly> will describe how to do so. | ||
You will need to make changes both | You will need to make changes to both your model and your MotoTune configuration to support the new MotoTune communication CAN IDs. | ||
====Model Configuration==== | ====Model Configuration==== | ||
#Disable the MotoTune Protocol in the CAN Definition block | #Disable the MotoTune Protocol in the CAN Definition block | ||
#Add '''MotoTune Custom CAN Protocol Handler''' block (Idle Triggered) | #Add the '''MotoTune Custom CAN Protocol Handler''' block (Idle Triggered) | ||
#:RX ID = hex2dec('1A000B02') | #:RX ID = hex2dec('1A000B02') | ||
#:RX ID mask = hex2dec('1F00FFFF') | #:RX ID mask = hex2dec('1F00FFFF') | ||
#:TX ID = hex2dec('1A00020B') | #:TX ID = hex2dec('1A00020B') | ||
<!-- | |||
<gallery> | [[file:MTConflict ProtocolDisabled.png|500px|left|thumb|MotoTune Protocol Disabled]] | ||
file:MTConflict ProtocolDisabled.png|MotoTune Protocol Disabled | [[file:MTConflict NewIDs.png|350px|left|thumb|New CAN IDs for the MotoTune Custom CAN Protocol block]] | ||
file:MTConflict NewIDs.png|New CAN IDs for the MotoTune Custom CAN Protocol block | --> | ||
<gallery widths=500px heights=500px> | |||
file:MTConflict ProtocolDisabled.png|500px|MotoTune Protocol Disabled | |||
file:MTConflict NewIDs.png|500px|New CAN IDs for the MotoTune Custom CAN Protocol block | |||
</gallery> | </gallery> | ||
====MotoTune/MotoServer Configuration==== | ====MotoTune/MotoServer Configuration==== | ||
#Open MotoTune | #Open MotoTune and configure the MotoServer Ports | ||
#Edit Port Names and | #Edit Port Names and create a Custom CAN Mapping | ||
#:TX ID: 436210434 (this is 0x1A000B02, but use decimal here) | #:TX ID: 436210434 (this is 0x1A000B02, but use decimal here) | ||
#:RX ID: 436208139 (this is 0x1A00020B, but use decimal here) | #:RX ID: 436208139 (this is 0x1A00020B, but use decimal here) | ||
#Create a new Port configuration | #Create a new Port configuration | ||
#After flashing the module, the MotoTune protocol will no longer be available on PCM-1 | #After flashing the module, the MotoTune protocol will no longer be available on PCM-1 and will only be available on the new custom mapping. | ||
<gallery perrow= | <gallery widths=350px heights=350px perrow=4> | ||
file:MTConflict MTMenu.png|MotoTune context menu | file:MTConflict MTMenu.png|MotoTune context menu | ||
file:MTConflict PortConfig EditNames.png|Edit Names | file:MTConflict PortConfig EditNames.png|Edit Names | ||
| Line 37: | Line 39: | ||
</gallery> | </gallery> | ||
====MotoTune dongle is plugged in but MotoViewer | ====MotoTune dongle is plugged in, but MotoViewer won't open.==== | ||
In order to open up Motoviewer a separate MotoService dongle is required. | In order to open up Motoviewer, a separate MotoService dongle is required. | ||
==== | ====MotoTune has stopped working after a Re-install/Update.==== | ||
If | *If you are upgrading from 8.13 to 10.0, please uninstall 8.13 first then install 10.0 if you have encountered issues. | ||
*When downgrading from 10.0 to 8.13, please uninstall 10.0 '''and''' the MotoLicense Handler '''before''' installing the 8.13 version of MotoTune | |||
Latest revision as of 16:13, 1 March 2023
You may run into issues with MotoTune's CAN messaging conflicting with other CAN communications in your system. It is possible to change the CAN IDs on which MotoTune communicates to avoid this. This article will describe how to do so.
You will need to make changes to both your model and your MotoTune configuration to support the new MotoTune communication CAN IDs.
Model Configuration
- Disable the MotoTune Protocol in the CAN Definition block
- Add the MotoTune Custom CAN Protocol Handler block (Idle Triggered)
- RX ID = hex2dec('1A000B02')
- RX ID mask = hex2dec('1F00FFFF')
- TX ID = hex2dec('1A00020B')
-
MotoTune Protocol Disabled
-
New CAN IDs for the MotoTune Custom CAN Protocol block
MotoTune/MotoServer Configuration
- Open MotoTune and configure the MotoServer Ports
- Edit Port Names and create a Custom CAN Mapping
- TX ID: 436210434 (this is 0x1A000B02, but use decimal here)
- RX ID: 436208139 (this is 0x1A00020B, but use decimal here)
- Create a new Port configuration
- After flashing the module, the MotoTune protocol will no longer be available on PCM-1 and will only be available on the new custom mapping.
-
MotoTune context menu
-
Edit Names
-
Add a port name
-
Select 'CAN Custom'
-
Enter your name and the appropriate CAN IDs
-
Add a port configuration
-
-
Now your custom port is in the ports list!
-
Don't forget to select it in the Program dialog box
MotoTune dongle is plugged in, but MotoViewer won't open.
In order to open up Motoviewer, a separate MotoService dongle is required.
MotoTune has stopped working after a Re-install/Update.
- If you are upgrading from 8.13 to 10.0, please uninstall 8.13 first then install 10.0 if you have encountered issues.
- When downgrading from 10.0 to 8.13, please uninstall 10.0 and the MotoLicense Handler before installing the 8.13 version of MotoTune