AXIOMATIC AX180800 User manual

User Manual UMAX180800
Version 1
Firmware 1.xx
EA 5.15.125.0+
USER MANUAL
20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN
Controller
P/N: AX180800
In Europe:
Axiomatic Technologies Oy
Höytämöntie 6
33880 Lempäälä - Finland
Tel. [phone]
Fax. [phone]
www.axiomatic.fi
In North America:
Axiomatic Technologies Corporation
5915 Wallace Street
Mississauga, ON Canada L4Z 1Z8
Tel. [phone]
Fax. [phone]
www.axiomatic.com

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1
ii
ACRONYMS
ARP
Address Resolution Protocol
ASCII
American Standard Code for Information Interchange
AWG
American wire gauge
CAN
Controller Area Network
CE
European Conformity
CMOS
Complementary metal-oxide-semiconductor
DC
Direct Current
DIN
German Institute for Standardization
DM
Diagnostic message. Defined in J1939/73 standard
EA
Electronic Assistant. PC application software from Axiomatic
ECU
Electronic control unit
EEPROM
Electrically Erasable Programmable Read-Only Memory
EMI
Electromagnetic Interference
EN
European Standard
GPL
General Public License
ICMP
Internet Control Message Protocol
ID
Identifier
IEC
International Electrotechnical Commission
IEEE
Institute of Electrical and Electronics Engineers
IP
Internet Protocol or Ingress Protection (for housing)
ISO
International Organization for Standardization
LAN
Local Area Network
LED
Light-emitting diode
LoZ
Low resistance
LSB
Less Significant Byte
MAC
Media Access Control (address)
MDIX
Medium Dependent Interface Crossover (MDI-X)
PC
Personal Computer
PGN
Parameter Group Number. Defined in J1939/73 standard
PHY
Physical Layer Transceiver (Ethernet chip)
P/N
Part Number
PWM
Pulse-width modulation
RoHS
Restriction of Hazardous Substances
RTOS
Real-Time Operating System
SAE J1939
CAN-based higher-level protocol designed and supported by the Society of
automobile Engineers (SAE)
S/N
Serial Number
TBD
To be determined
TCP
Transmission Control Protocol
UDP
User Datagram Protocol
UL
Underwriters Laboratories (safety organization)
USB
Universal Serial Bus
VDC
Volt Direct Current
UTP
Unshielded twisted pair

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1
iii
TABLE OF CONTENTS
1INTRODUCTION.................................................................................................................5
2CONTROLLER DESCRIPTION..........................................................................................6
2.1 Hardware Block Diagram.............................................................................................6
2.2 Software Organization .................................................................................................7
2.3 CAN Interface ..............................................................................................................7
2.3.1 CAN Baud Rate....................................................................................................8
2.3.2 J1939 Name and Address ....................................................................................8
2.3.3 Slew Rate Control.................................................................................................9
2.4 The controller has an ability to adjust the CAN transceiver slew rate for better
performance on the CAN physical network, see Miscellaneous .............................................9
2.5 Diagnostics ..................................................................................................................9
2.5.1 Network Bus Terminating Resistors....................................................................11
2.6 Modbus TCP Interface...............................................................................................11
2.7 Discovery Protocol.....................................................................................................13
2.8 Default Settings..........................................................................................................13
3CONTROLLER LOGICAL STRUCTURE..........................................................................14
3.1 Function Block Signals...............................................................................................15
3.2 Output Signal Sources...............................................................................................15
3.3 Universal Inputs.........................................................................................................16
3.3.1 Voltage Measurements.......................................................................................18
3.3.2 Current Measurements.......................................................................................18
3.3.3 Discrete Voltage Level........................................................................................18
3.3.4 Frequency and PWM..........................................................................................19
3.3.4.1 Special Conditions...........................................................................................20
3.3.5 Diagnostics.........................................................................................................20
3.4 Thermocouple Input Function Block...........................................................................21
3.4.1 Thermocouple Input Cold Junction Compensation .............................................21
3.4.2 Thermocouple Input Diagnostic Parameters.......................................................21
3.4.3 Thermocouple Input Warning and Shutdown......................................................22
3.5 RTD Input Function Block..........................................................................................22
3.5.1 RTD Coefficients.................................................................................................22
3.5.2 Warning and Shutdown Limits............................................................................23
3.6 Relay Output Function Block......................................................................................23
3.6.1 Relay Output Functionality..................................................................................23
3.6.2 Relay Output Control / Enable Sources / Override Source.................................24
3.6.3 Relay Output Enable...........................................................................................24
3.6.4 Relay Output Override........................................................................................25
3.6.5 Unlatch Source...................................................................................................26
3.7 Math Function Block ..................................................................................................26
3.8 Conditional Block.......................................................................................................27
3.9 Set / Reset Latch Function Block...............................................................................28
3.10 Lookup Table Function Block.....................................................................................28
3.11 Programmable Logic Function Block .........................................................................29
3.12 Global Parameters.....................................................................................................30
3.13 Miscellaneous............................................................................................................31
3.14 Diagnostics ................................................................................................................31

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1
iv
3.15 J1939 Network...........................................................................................................33
3.15.1 ECU Network Parameters...................................................................................34
3.15.2 CAN Network Parameters...................................................................................34
3.16 Constant Data............................................................................................................35
3.17 Ethernet .....................................................................................................................35
3.18 CAN Input Signals......................................................................................................36
3.19 CAN Output Messages ..............................................................................................37
4CONTROLLER CONFIGURATION...................................................................................41
4.1 Modbus Configuration................................................................................................41
4.2 CAN Configuration.....................................................................................................41
4.3 Function blocks in EA ................................................................................................42
4.3.1 J1939 Network Setpoints....................................................................................42
4.3.2 RTD Function Block............................................................................................43
4.3.3 Universal Input Setpoints....................................................................................45
4.3.4 Thermocouple Input Setpoints............................................................................46
4.3.5 Relay Output Setpoints.......................................................................................47
4.3.6 Math Function Block Setpoints ...........................................................................48
4.3.7 Conditional Logic Block Setpoints.......................................................................50
4.3.8 Set-Reset Latch Block ........................................................................................51
4.3.9 Lookup Table Setpoints......................................................................................51
4.3.10 Programmable Logic Block Setpoints.................................................................53
4.3.11 Miscellaneous Setpoints.....................................................................................55
4.3.12 Diagnostic Setpoints...........................................................................................56
4.3.13 Constant Data List Setpoints ..............................................................................56
4.3.14 Ethernet Setpoints ..............................................................................................57
4.3.15 CAN Transmit Setpoints .....................................................................................58
4.3.16 CAN Receive Setpoints ......................................................................................60
4.4 Setpoint File...............................................................................................................61
5FLASHING NEW FIRMWARE ..........................................................................................62
6TECHNICAL SPECIFICATIONS.......................................................................................66
6.1 Technical Specifications ............................................................................................66
6.2 Inputs.........................................................................................................................66
6.3 Outputs ......................................................................................................................67
6.4 Communication..........................................................................................................67
6.5 General Specifications...............................................................................................67
6.6 Dimensional Drawing.................................................................................................68
7THIRD-PARTY SOFTWARE LICENSE NOTICES............................................................69
8VERSION HISTORY.........................................................................................................71

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 5-71
1 INTRODUCTION
The following user manual describes architecture, functionality, configuration parameters and
flashing instructions for the 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller
with SAE J1939 CAN and Modbus TCP/IP Ethernet communication links. It also contains
controller technical specifications and installation instructions to help users build a custom
solution on the base of this controller.
The user should check whether the application firmware installed in the controller is covered by
this user manual. It can be done through CAN bus using Axiomatic Electronic Assistant®(EA)
software or using Ethernet Modbus TCP/IP link.
The user manual is valid for application firmware with the same major version number as the
user manual. For example, this user manual is valid for any converter application firmware
V1.xx. Updates specific to the user manual are done by adding letters: A, B, …, Z to the user
manual version number.
It is assumed, that the user is familiar with Modbus and J1939 CAN groups of standards. The
terminology from these standards is widely used in this manual.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 6-71
2 CONTROLLER DESCRIPTION
The controller is designed to convert physical signals from bipolar and universal inputs into
J1939 CAN signals and input register data for the Modbus TCP interface. The universal inputs
accept voltage, current, frequency, PWM duty cycle, and discrete voltage levels.
The J1939 CAN network can operate at standard 250 and 500 kbit/s and non-standard
667kbit/s and 1Mbit/s baud rates. The required baud rate is detected automatically upon
connection to the CAN network.
The Modbus TCP/IP interface runs on a standard 10/100 Mbit/s Ethernet link providing up to 5
simultaneous client connections.
The controller can be configured through a set of configuration parameters over CAN or
Ethernet interface to fit the user-specific application requirements.
2.1 Hardware Block Diagram
The controller contains 20 thermocouple, 2 RTD, and 4 universal inputs, 6 relays, two CAN
interfaces and one Ethernet port, and a protected power supply. An embedded 32-bit
microcontroller provides necessary processing power to the controller.
Figure 1. The Controller Hardware Block Diagram
The controller has a wide range of protection features including a transient and reverse polarity
protection, see TECHNICAL SPECIFICATIONS section.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 7-71
2.2 Software Organization
The controller belongs to a family of Axiomatic smart controllers with configurable internal
architecture. This architecture allows building of a signal converting algorithm based on a set
of predefined internal configurable function blocks without the need of a custom software.
The user can configure the controller internal structure and individual function blocks using PC-
based Axiomatic Electronic Assistant®(EA) software through CAN interface, without
disconnecting the converter from the user system. Alternatively, the user can configure the
controller through the Modbus link.
The controller application firmware can be updated through CAN interface in the field using
EA, see FLASHING NEW FIRMWARE section. Updating firmware over Modbus is currently
not implemented.
2.3 CAN Interface
The CAN interface is compliant with Bosch CAN protocol specification, Rev.2.0, Part B, and
the following SAE J1939 standards:
Table 1. CAN Standard Implementation
ISO/OSI Network Model
Layer
J1939 Standard
Physical
J1939/11 –Physical Layer, 250K bit/s, Twisted Shielded Pair. Rev.
SEP 2006.
J1939/15 - Reduced Physical Layer, 250K bits/sec, Un-Shielded
Twisted Pair (UTP). Rev. AUG 2008.
J1939/14 - Physical Layer, 500 Kbps. Rev. OCT 2011.
J1939/16 –Automatic Baud Rate Detection Process. Rev. NOV 2018.
Data Link
J1939/21 –Data Link Layer. Rev. DEC 2006
The controller supports Transport Protocol for Commanded Address
messages (PGN 65240), ECU identification messages -ECUID (PGN
64965), and software identification messages -SOFT (PGN 65242). It
also supports responses on PGN Requests (PGN 59904).
Please note that the Proprietary A PGN (PGN 61184) is taken by
Axiomatic Simple Proprietary Protocol and is not available for the user.
Network
J1939, Appendix B –Address and Identity Assignments. Rev. FEB
2010.
J1939/81 –Network Management. Rev. MAR2017.
The controller is an Arbitrary Address Capable ECU. It can dynamically
change its network address in real-time to resolve an address conflict
with other ECUs.
The controller supports: Address Claimed Messages (PGN 60928),
Requests for Address Claimed Messages (PGN 59904) and
Commanded Address Messages (PGN 65240).
Transport
N/A in J1939.
Session
N/A in J1939.
Presentation
N/A in J1939.
Application
J1939/71 –Vehicle Application Layer. Rev. APR 2014 with J1939DA –
Digital Annex. Rev. OCT 2014.
The controller can receive and transmit application-specific PGNs. All
application-specific PGNs are user-programmable.
J1939/73 –Application Layer –Diagnostics. Rev. FEB 2010

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 8-71
ISO/OSI Network Model
Layer
J1939 Standard
Memory access protocol (MAP) support. DM14, DM15, DM16 are used
by EA to program configuration parameters.
DM13 support is provided to temporarily suppress transmission of
application-specific PGNs.
2.3.1 CAN Baud Rate
The controller can operate at J1939 standard 250 and 500 kbit/s baud rates. It can also run at
667kbit/s and 1Mbit/s –the maximum baud rate supported by the CAN hardware.
The baud rate selection is performed automatically upon connection to the CAN network using
passive and active automatic baud rate detection process described in J1939/16. Once
detected, the baud rate is stored in non-volatile memory and used on the next controller
power-up.
The baud rate detection can be disabled for permanently installed units to maintain the desired
baud rate on the CAN network.
2.3.2 J1939 Name and Address
Before sending and receiving any application data, the converter claims its network address
with a unique J1939 Name. The Name fields are presented in the table below:
Table 2. J1939 Name Fields
Field Name
Field Length
Field Value
Configurable
Arbitrary Address Capable
1 bit
1 (Capable)
No
Industry Group
3 bit
0 (Global)
No
Vehicle System Instance
4 bit
0 (First Instance)
No
Vehicle System
7 bit
0 (Nonspecific System)
No
Reserved
1 bit
0
No
Function
8 bit
126 (IO Controller, Axiomatic
proprietary)
No
Function Instance
5 bit
20 (AX180800, Axiomatic proprietary)
No
ECU Instance
3 bit
0 (First Instance)
Yes
Manufacturer Code
11 bit
162 (Axiomatic Technologies Corp.)
No
Identity Number
21 bit
Calculated on the base of the
microcontroller unique ID
No
The user can change the controller ECU Instance using EA to accommodate multiple signal
input controllers on the same CAN network.
The controller takes its network ECU Address from a pool of addresses assigned to self-
configurable ECUs. The default address can be changed during an arbitration process or upon
receiving a commanded address message. The new address value will be stored in a non-
volatile memory and used next time for claiming the network address. The ECU Address can
also be changed in EA.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 9-71
2.3.3 Slew Rate Control
2.4 The controller has an ability to adjust the CAN transceiver slew rate for better
performance on the CAN physical network, see Miscellaneous
The Miscellaneous function block contains various parameters that affect the general
diagnostic performance of the ECU.
The Undervoltage Threshold, Overvoltage Threshold, and Shutdown Temperature
setpoints are used to set the limits for when their respective diagnostic messages are
triggered.
Lastly, the CAN Diagnostic Setting1 and CAN Diagnostic Setting2 parameters are used to
control all diagnostics with one general setting for CAN Interface 1 and CAN Interface 2
respectively. This can be used to disable diagnostics entirely, only transmit messages without
a blank SPN, or transmit diagnostic messages normally.
2.5 Diagnostics
The Diagnostic function block includes 120 faults, each representing a diagnostic message
that the ECU is able to produce. Each Universal Input has a Voltage Out of Range Low and
Voltage Out of Range High Faut. Each RTD has Temperature Out of Range Low and
Temperature Out of Range High, High and Low Shutdown Faults. Each Thermocouple Input
has Temperature Out of Range Low and Temperature Out of Range High, High and Low
Shutdown, and Open Circuit Faults. The remaining faults cover VPS Overvoltage and
Undervoltage, Overtemperature, and other faults.
If and only if the Event Generates a DTC in DM1 parameter is set to true will the other
setpoints in the function block be enabled. They are all related to the data that is sent to the
J1939 network as part of the DM1 message, Active Diagnostic Trouble Codes.
A Diagnostic Trouble Code (DTC) is defined by the J1939 standard as a 4-byte value which is a
combination of:
SPN Suspect Parameter Number (first 19 bits of the DTC, LSB first)
FMI Failure Mode Identifier (next 5 bits of the DTC)
CM Conversion Method (1 bit, always set to 0)
OC Occurrence Count (7 bits, number of times the fault has
happened)
In addition to supporting the DM1 message, the Controller also supports
DM2 Previously Active Diagnostic Trouble Codes Sent only on request
DM3 Diagnostic Data Clear/Reset of Previously Active DTCs Done only on request
DM11 Diagnostic Data Clear/Reset for Active DTCs Done only on request
So long as even one Diagnostic function block has Event Generates a DTC in DM1 set to
true, the Controller will send the DM1 message every one second, regardless of whether there
are any active faults, as recommended by the standard. While there are no active DTCs, the
Controller will send the “No Active Faults” message. If a previously active DTC becomes

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 10-71
inactive, a DM1 will be sent immediately to reflect this. As soon as the last active DTC goes
inactive, it will send a DM1 indicating that there are no more active DTCs.
If there is more than on active DTC at any given time, the regular DM1 message will be sent
using a multipacket Broadcast Announce Message (BAM). If the controller receives a request
for a DM1 while this is true, it will send the multipacket message to the Requester Address
using the Transport Protocol (TP).
At power up, the DM1 message willnot be broadcast until after a 5 second delay.
This is done to prevent any power up or initialization conditions from being
flagged as an active error on the network.
The Diagnostic function block has a setpoint Event Cleared Only by DM11. By default, this is
set to false, which means that as soon as the condition that caused an error flag to be set goes
away, the DTC is automatically made Previously Active, and is no longer included in the DM1
message. However, when this setpoint is set to true, even if the flag is cleared, the DTC will
not be made inactive, so it will continue to be sent on the DM1 message. Only when a DM11
has been requested will the DTC go inactive. This feature may be useful in a system where a
critical fault needs to be clearly identified as having happened, even if the conditions that
caused it went away.
In addition to all the active DTCs, another part of the DM1 message is the first byte, which
reflects the Lamp Status. Each Diagnostic function block has the setpoint Lamp Set by Event
in DM1 which determines which lamp will be set in this byte while the DTC is active. The
J1939 standard defines the lamps as ‘Malfunction’, ‘Red Stop’, ‘Amber, Warning’ or ‘Protect’.
By default, the ‘Amber, Warning’ lamp is typically the one set by any active fault.
By default, every Diagnostic function block has associated with it a proprietary SPN. However,
this setpoint SPN for Event used in DTC is fully configurable by the user should they wish it to
reflect a standard SPN define in J1939-71 instead. If the SPN is change, the OC of the
associate error log is automatically reset to zero.
Every Diagnostic function block also has associated with it a default FMI. The only setpoint for
the user to change the FMI is FMI for Event used in DTC, even though some Diagnostic
function blocks can have both high and low errors. In those cases, the FMI in the setpoint
reflects that of the low-end condition, and the FMI used by the high fault will be determined per
Table 30. If the FMI is changed, the OC of the associate error log is automatically reset to
zero.
Table 30. Low Fault FMI versus High Fault FMI
FMI for Event used in DTC –Low Fault
Corresponding FMI used in DTC –High Fault
FMI=1, Data Valid But Below Normal
Operational Range –Most Severe Level
FMI=0, Data Valid But Above Normal
Operational Range –Most Severe Level