MotoTune Conflict

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 both to your model and to MotoTune configuration to support the new MotoTune communication CAN IDs.

Model Configuration

1. Disable the MotoTune Protocol in the CAN Definition block
2. Add MotoTune Custom CAN Protocol Handler block (Idle Triggered)

   RX ID = hex2dec('1A000B02')

   RX ID mask = hex2dec('1F00FFFF')

   TX ID = hex2dec('1A00020B')

FIXME: Add gallery of screenshots here

MotoTune/MotoServer Configuration

1. Open MotoTune, and configure MotoServer Ports
2. 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)

3. Create a new Port configuration
4. 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.

FIXME: Add gallery of screenshots here