DANA SUMO TM4 - 4.6 Software Installation; CAN Protocol and TM4 ODIN; Selecting Communication Protocol Type; Table 13 TM4 ODIN CAN Default Configuration Values

Installation Guide
CONFIDENTIAL
TG-0259_9 TM4 CO200-A3 Installation Guide
© Dana TM4 inc., 2020-2022
Page 37 of 42
4.6 Software installation
All software-related installation and diagnostics are performed using TM4 ODIN, an MS Windows™
application developed by Dana TM4, and a computer equipped to connect to the TM4 MCU CAN port. For
more information on how to install TM4 ODIN and set up the CAN connection, see the TM4 ODIN Technical
Guide [3].
Note: Dana TM4 is not responsible for any damage to the system caused by misuse or modification of the
application code.
This section gives more information on how to connect to TM4 ODIN, and how to modify CAN speed and
base addresses, if required.
4.6.1 Selecting communication protocol type
The integrator can select either standard or J1939 CAN protocol type after installing the software on the
product.
Note: Standard CAN is the default communication protocol type used.
See the system Operations and Maintenance Guide [5] for more information.
4.6.2 CAN protocol and TM4 ODIN
The TM4 CO200 MCU uses the CAN protocol to send and receive messages/data. Although certain
aspects of the protocol have default settings at the time of delivery (see Table 13), these can be
reconfigured using TM4 ODIN to accommodate the specifics of your integration.
Table 13 TM4 ODIN CAN default configuration values
Specifications
Units
Values
Default baud rate
kb/s
500
Default base address CAN1
--
0x660 (1632)
Default base address CAN2
--
0x680 (1664)
Default base range
--
See Table 14 (CAN1) & Table 15 (CAN2)
For more information on reconfiguring the CAN speed and addresses, see the following sections:
• Reconfiguring CAN bus base addresses, Section 4.6.2.1.
• Reconfiguring the CAN bus baud rate, Section 4.6.2.3.
4.6.2.1 Reconfiguring CAN bus base addresses
Although it is recommended to use the default CAN base addresses whenever possible, there are certain
cases in which the CAN IDs might be in conflict with other CAN modules during vehicle integration. In these
cases, it is possible to configure the base addresses for high and low priority messages and TM4 ODIN
messages.
Note: When multiple MCUs are connected to the same CAN bus, the message base addresses must have
a unique configuration for each MCU connected on the CAN bus.