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

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 11-71
FMI=4, Voltage Below Normal, Or
Shorted To Low Source
FMI=3, Voltage Above Normal, Or Shorted To
High Source
FMI=5, Current Below Normal Or Open
Circuit
FMI=6, Current Above Normal Or Grounded
Circuit
FMI=17, Data Valid But Below Normal
Operating Range –Least Severe Level
FMI=15, Data Valid But Above Normal
Operating Range –Least Severe Level
FMI=18, Data Valid But Below Normal
Operating Range –Moderately Severe
Level
FMI=16, Data Valid But Above Normal
Operating Range –Moderately Severe Level
FMI=21, Data Drifted Low
FMI=20, Data Drifted High
If the FMI used is anything other than one of those in Table 30, then both the low
and the high faults will be assigned the same FMI. This condition should be
avoided, as the log will still use different OC for the two types of faults, even though
they will be reported the same in the DTC.
When the fault is linked to a DTC, a non-volatile log of the occurrence count (OC) is kept. As
soon as the controller detects a new (previously inactive) fault, it will start decrementing the
Delay Before Sending DM1 timer for the Diagnostic function block. If the fault has remained
present during the delay time, then the controller will set the DTC to active, and it will
increment the OC in the log. A DM1 will immediately be generated that includes the new DTC.
The timer is provided so that intermittent faults do not overwhelm the network as the fault
comes and goes, since a DM1 message would be sent every time the fault shows up or goes
away.
J1939 Network function block for further details.
2.5.1 Network Bus Terminating Resistors
The controller does not have an embedded 120 Ohm CAN bus terminating resistor.
Terminating resistors should be installed externally on both ends of the CAN twisted pair cable
according to the J1939/11(15) standards to avoid communication errors.
Even if the length of the CAN network is short and the signal reflection from both ends of the
cable can be ignored, at least one 120 Ohm resistor is required for the majority of CAN
transceivers to operate properly.
2.6 Modbus TCP Interface
The Modbus TCP/IP interface1runs over a standard 10/100 Mbit/s Ethernet link. The controller
is presented as a slave device (a server) on the Modbus network. It supports with up to 8
simultaneous client connections from master devices.
1The interface is compliant with:

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 12-71
•MODBUS Messaging on TCP/IP Implementation Guide V1.0b. Modbus Organization. October 24,
2006, 46p.
•MODBUS Application Protocol Specification V1.1b3. Modbus Organization. April 26, 2012, 50p.
The following Modbus functions are supported by the controller.
Table 3. Modbus Functions Supported by the Controller
Name
Function
Code/Subcode
Description
Read Discrete Inputs
2
Reads values of the universal inputs when they are
in the discrete voltage level mode
Read Input Registers
4
Reads values of the universal inputs
Read Holding Registers
3
Reads one or several configuration parameters
Write Single Register
6
Writes a configuration parameter
Write Multiple Registers
16
Writes one or several configuration parameters
Read/Write Multiple
Registers
23
Writes and then reads configuration parameters
Encapsulated Interface
Transport
43/14
Reads Device Identification
The Modbus addresses are presented in the Error! Reference source not found. section.
The Unit Identifier in the Modbus TCP header is ignored.
Floating-point variables are presented in a standard IEEE 754 single-precision 32-bit format,
most significant word first. Double-word 32-bit integers are also presented with the most
significant word first.
Reading and writing operations on variables occupying more than one word (a 16-bit Modbus
register) are buffered. The buffering is made transparent to the user. However, it should be
taken into consideration that writing to a non-volatile memory is not performed until all registers
assigned to the variable are written. The writing operation should be performed without
overlapping (writing to the same register twice) and without breaking the writing operation
sequence with a reading operation or a writing operation to a different variable.
The Modbus functions “Write Multiple Registers” and “Read/Write Multiple Registers”, when
they include all registers assigned to a variable in one function call, meet the abovementioned
writing requirements.
The Modbus writing operations are subject to a validity check. If a configuration parameter
value is not in a valid range, the Modbus operation will succeed, but the configuration
parameter will not be written.
The following device identification information can be read using the Encapsulated Interface
Transport 43/14 function.
Table 4. Modbus Device Identification
Object ID
Object Name
Description
0x00
VendorName
“Axiomatic”

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 13-71
Object ID
Object Name
Description
0x01
ProductCode
Controller P/N. “AX180800”
0x02
MajorMinorRevision
Current firmware version. For example, “V1.00”
0x03
VendorUrl
“www.axiomatic.com”
0x04
ProductName
“IO Controller”
0x05
ModelName
Same as ProductCode. Controller P/N. “AX180800”
0x06
UserApplicationName
Firmware description. Depends on the firmware version. For
V1.xx: “20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN
Controller”
0x80
SerialNumber
Private Object. Controller S/N. For example, “0012020016”
All device identification objects are presented in ASCII strings.
2.7 Discovery Protocol
The controller supports an Axiomatic proprietary protocol that allows the discovery of
Axiomatic controllers on a LAN by sending a global UDP request on port 351001.
1 O. Bogush, "Ethernet to CAN Converter Discovery Protocol. CAN-ENET, AX140900, Project 15129.
Document version: 1," Axiomatic Technologies Corporation, October 26, 2016.
Axiomatic provides a Windows console application AxioDisc.exe that can be used to
discover the controller. The application shows the controller MAC address, IP address, web
server port (not used), device port (Modbus port), device port type (TCP), the controller part
number and serial number, see Figure 2.
The AxioDisc.exe. application is available upon request.
Figure 2. Discovery of the Controller on LAN Using AxioDisc.exe Application
2.8 Default Settings
The controller Universal Inputs are configured to input voltages in the 0…5V voltage range by
default. These voltages can be read through Modbus interface.
The CAN output messages are not set up by default. They can be configured to accommodate
user-specific application requirements, see Error! Reference source not found. in
REF _Ref43292189 \h CONTROLLER CONFIGURATION section.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 14-71
3 CONTROLLER LOGICAL STRUCTURE
The controller is internally organized as a set of function blocks, which can be individually
configured and arbitrarily connected together to achieve the required system functionality, see
Figure 3.
Figure 3. The Controller Logical Block Diagram
Each function block is absolutely independent and has its own set of configuration parameters,
aka setpoints. The configuration parameters can be viewed and changed through CAN bus
using Axiomatic Electronic Assistant®(EA) software or over Modbus interface.
The Universal Input function block presents the controller physical input channels. This
function block can measure multiple physical parameters.
The J1939 CAN interface is presented by the CAN Input Signal, CAN Output Message and
J1939 Network function blocks. The CAN Input Signal functional blocks are used to receive
CAN signals transmitted on the CAN bus. They have one signal output, which is updated once
the signal is received. The CAN Output Message function blocks are used to transmit CAN
signals on the CAN bus. Each CAN message can hold up to ten individual CAN output signals,
receiving data from their own signal inputs.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 15-71
The Modbus interface is presented by the Ethernet function block that contains Modbus
TCP/IP network settings.
For data processing, when required, there are Math, Set-Reset Latch, Lookup Table
Conditional Logic, and Programmable Logic function blocks. They perform a unique set of
functions that is explained in respective part of the Section 3.
The converter also has a Global Parameters function block containing four constant output
signals and other auxiliary outputs.
3.1 Function Block Signals
The controller function blocks can communicate with each other through internal signal inputs
and outputs. Each signal input of one function block can be connected to any signal output of
another function block using an appropriate configuration parameter. There is no limitation on
the number of signal inputs connected to one signal output.
When a signal input is connected to a signal output, data from the signal output of one function
block is available on the signal input of another function block.
Function block signals can be “Undefined”, “Discrete”or “Continuous”. The “Undefined”signal
type is reserved for a disconnected signal source or a no-signal transient condition. The
“Discrete” and “Continuous” signal types are used to communicate discrete and continuous
signals, respectively.
Discrete signals present data with a finite number of states. They are stored in four-byte
unsigned integer variables that can present any state in the 0…0xFFFFFFFF range.
Continuous signals present continuous data, usually physical parameters. They are stored in
single-precision floating-point variables. The continuous signals are not normalized and usually
present data in physical units.
When a discrete signal output is connected to a continuous signal input, the discrete signal is
converted into a positive continuous signal of the same value.
When a continuous signal output is connected to a discrete signal input, the following rules
apply. A positive continuous signal is converted into the same value discrete signal. A
fractional part of the continuous signal is truncated. If the continuous signal is above the
maximum discrete signal value, it is saturated to the maximum discrete signal value:
0xFFFFFFFF. All negative continuous signals are converted into zeros.
The undefined signals are converted into zeros unless the function block can process the
undefined signal state, for example: CAN Output Message function block will output all ones
for undefined signals.
3.2 Output Signal Sources
The controller output signal sources of all function blocks and source numbers are presented
in the table below.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 16-71
Table 5. Controller Signal Sources
Signal
Source
Number
Signal Name
Signal Type
Source Number
0
Not Connected
Undefined
0
1
Universal Input
Discrete or Continuous1
[1…4]
2
Thermocouple Temperature Input
Any2
[1…20]
3
Thermocouple Voltage Input
Any2
[1…20]
4
Thermocouple Input Raw Data
Any2
[1…20]
5
RTD Temperature Input
Any2
[1…2]
6
RTD Resistance Input
Any2
[1…2]
7
RTD Input Raw Data
Any2
[1…2]
8
CAN Input Signal
Any2
[1…3]
9
Math Function
Any2
[1…5]
10
Conditional Logic
Any2
[1…10]
11
Set-Reset Latch
Any2
[1…5]
12
Lookup Table
Any2
[1…10]
13
Programmable Logic
Any2
[1…3]
14
Global Continuous Constant Signal
Continuous
1
15
Global Discrete Constant Signal
Discrete
1
16
Supply Voltage
Continuous
1
17
Microcontroller Temperature
Continuous
1
1Depends on the Input Parameter.
2Depends on the Signal Type configuration parameter.
3.3 Universal Inputs
The Universal Input function block translates physical input signals into the internal function
block output signal that can be used by other function blocks of the controller.
There are 4 independent Universal Input function blocks presenting their own universal
physical inputs.
Figure 4. Universal Input Function Block
The internal function block output signal type and units of measurement are presented below.
Table 6. Universal Input Function Block Output Signal
Input Parameter
Type
Units
Voltage
Continuous
V
Current
Continuous
mA
Discrete Voltage Level
Discrete
{0,1}
Frequency
Continuous
Hz
PWM Duty Cycle
Continuous
%

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 17-71
Each Universal Input function block has the following configuration parameters.
Table 7. Universal Input Function Block Configuration Parameters
Parameter
Default Value
Range
Units
Description
Input Parameter
1 - Voltage
0 - Input Disabled,
1 - Voltage,
2 - Current,
3 - Discrete Voltage
Level,
4 - Frequency,
5 - PWM Duty Cycle
–
Defines the input physical
parameter that will be
measured by the function
block.
Voltage Range
0 - 0…5V
0 - 0…5 V,
1 - 0…10 V
V
Used in the "Voltage"
mode
Current Range1
0 - 0…20 mA
0 - 0…20mA,
1 - 4…20 mA
mA
Used in the "Current"
mode
Input Range Min
0
0…100
-
Depends on the Input
Parameter. Used for
diagnostic purposes
Input Range Max
5
0…100
-
Depends on the Input
Parameter. Used for
diagnostic purposes
Voltage LoZ Input
0 - No
0 - No,
1 - Yes
–
Activates a 10kOhm pull-
down resistor to avoid
ghost voltages in the
"Voltage" mode. Warning:
Measurement accuracy
will be decreased!
Analog Input Filter
0 - Disabled
0 - Disabled,
1 - 50Hz Noise
Rejection,
2 - 60Hz Noise
Rejection,
3 - Both: 60Hz and 50Hz
Noise Rejection
–
Noise Rejection in
"Voltage", "Current" and
“Resistance” modes
Pull-Up/Pull-Down
Resistor
0 - Disabled
0 - Disabled,
1 - 10kOhm Pull-Up,
2 - 10kOhm Pull-Down
–
Used in "Discrete Voltage
Level", "Frequency", and
"PWM Duty Cycle"
modes.
Input Polarity
0 - Active High
0 - Active High,
1 - Active Low
–
Used in "Discrete Voltage
Level", "Frequency", and
"PWM Duty Cycle"
modes.
Discrete Input
Debounce Time
50ms
0…1000
ms
Used in "Discrete Voltage
Level" mode. If 0 - no
debouncing.
Frequency Range
0 -
1Hz…10kHz
0 - 1Hz…10kHz,
Hz
A 16-bit counter is used.
Used in "Frequency", and
"PWM Duty Cycle"
modes.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 18-71
Parameter
Default Value
Range
Units
Description
Frequency/PWM
Debounce Filter3
0 - Disabled
0 - Disabled,
1 - 142ns,
2 - 1.14us,
3 - 6.10us
–
Used in "Frequency", and
"PWM Duty Cycle"
modes.
Frequency/PWM
Averaging
0 - No
Averaging
0 - No Averaging,
1 - 3 Readings,
2 - 5 Readings,
3 - 10 Readings
–
Defines a moving
average filer used in
"Frequency", and "PWM
Duty Cycle" modes.
1 Input currents below 3mA are output as 0mA when 4…20 mA current range is set.
3.3.1 Voltage Measurements
The Universal Inputs can measure voltages in voltage ranges set by the Voltage Range
configuration parameter.
To avoid an influence of ghost voltages, the Voltage LoZ Input configuration parameter can be
activated. This will reduce the accuracy of voltage measurements due to the influence of the
10kOhm pull-down shunt resistor and should be used only after careful consideration of the
shunt resistor influence on the measured circuit.
The user can set the Analog Input Filter configuration parameter to reduce noise in voltage and
other analog signal measurements. The filter is designed to suppress noise from industrial
offline voltages. Even when the analog input filter is disabled, the minimum signal filtering is
performed by the function block. The parameters of the analog input filter are presented below.
Table 8. Universal Input Analog Input Filter Parameters
Analog Input Filter
Cut-off Frequency
(at -3dB)
Settling Time
(to 100% of Final Value)
Output Signal Update Rate
Disabled1
70Hz
10ms
1.67ms
50Hz Noise Rejection
12Hz
76.7ms
3.33ms
60Hz Noise Rejection
14Hz
63.3ms
3.33ms
Both: 60Hz and 50Hz
Noise Rejection
2.3Hz
396.7ms
16.67ms
1Minimum filtering is still performed.
3.3.2 Current Measurements
There are two standard current ranges available for current measurements. When the current
is below 3mA in the “4…20mA” current range, the output will be forced to zero to facilitate
detection of an open circuit condition on the Universal Input.
The Analog Input Filter can be set to reduce the input noise.
3.3.3 Discrete Voltage Level
The Universal Inputs can accept discrete voltage levels. The user should specify the input
polarity and define whether the pull-up/pull-down resistor is necessary on the input.
When the “10kOhm Pull-Up” is selected, the pull-up resistor is connected to the internal +14V
power supply.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 19-71
The input states are sampled every 1ms. If debouncing is required, it is set by the Discrete
Input Debounce Time configuration parameter. If the Discrete Input Debounce Time is zero,
the discrete voltage level input is not debounced.
3.3.4 Frequency and PWM
The frequency and PWM duty cycle measurements are performed by counting high-frequency
internal clock pulses on every period of the input signal. The universal input channels have
different internal organization due to limited hardware resources.
All universal inputs use 16-bit counters with the constant frequency range of 1...10kHz
Table 9. Universal Input Function Block Counters
Function
Block
Counter
Frequency
Range
Counter
Base
Shared Input
Frequency Range
and Debounce Filter
Setting
Universal
Input #1
16-bit
1Hz…10kHz,
Dedicated
N/A
Same input
Universal
Input #2
Dedicated
N/A
Same input
Universal
Input #3
Dedicated
N/A
Same input
Universal
Input #4
Dedicated
N/A
Same input
To measure frequency or PWM duty cycle, the user should first select the Frequency Range
parameter and then define how the Pull-Up/Pull-Down Resistor, Frequency/PWM Debounce
Filter, and the Frequency/PWM Averaging parameters should be set.
The Input Polarity defines the active edge of the input signal. The Pull-Up/Pull-Down Resistor
can be used to pull the input to a no-signal state to avoid an undefined input condition when
the signal source is disconnected. The Input Polarity and Pull-Up/Pull-Down Resistor are
normally set the following way.
Table 10. Setting Pull-Up/Pull-Down Resistor for Selected Input Polarity. Universal Inputs
Input Polarity
Pull-Up/Pull-Down Resistor
Active High
“Disabled” or “10kOhm Pull-Down”
Active Low
“Disabled” or “10kOhm Pull-Up”
The frequency/PWM debounce filter is used to filter out parasitic spikes that can be present in
a noisy input signal. It can be helpful to prevent the input from going into the Recovery state
(see 3.3.4.1 Special Conditions) when, for example, mechanical switches are used to
commutate the input signal.
The debounce filter should be used with caution since it can reduce the accuracy and
resolution of frequency and PWM measurements if the debouncing time is not significantly less
than the period of the input signal.
When a frequency or PWM signal presents a slowly changing parameter, setting an additional
moving average filter using the Frequency/PWM Averaging configuration parameter can be
helpful in smoothing the results of the input measurements.

UMAX180800, 20 Thermocouple, 2 RTD, 4 Inputs, 6 Relays Dual CAN Controller Version 1 Page: 20-71
3.3.4.1 Special Conditions
Frequencies below the Minimum Frequency value will be measured as zero and frequencies
above the Maximum Frequency value will saturate at the Maximum Frequency value for the
Frequency Range, see Table 11 and Table 12.
Table 11. Maximum, Minimum Frequencies and Maximum Recovery Time for Universal Inputs
Frequency
Range
Counter
Minimum
Frequency
Maximum Frequency
Maximum Recovery
Time
1Hz…10kHz
16-Bit
0.9155Hz
12.5kHz
10.9ms
Frequencies above the Maximum Frequency value will switch the input to the Recovery state.
The input will stay in the Recovery state until the upcoming counter saturation event when the
frequency will be measured again. The input will leave the Recovery state if the measured
frequency value is below the Maximum Frequency.
Table 12. Frequency and PWM Measurements for Universal Inputs. Special Conditions
Input Mode
Signal Frequency ()
 
Zero Frequency
(DC)
   
Below Minimum
Frequency 
   
Working Frequency
 
Above Maximum
Frequency 
Measured
Frequency 
 
 
 
 
Recovery state
Measured PWM
Duty Cycle 
 󰇝󰇞
Undefined (not
allowed)
 
–signal duty cycle
 
Recovery state
The time between two consequent counter saturation events defines the Maximum Recovery
Time, see Table 11 Error! Reference source not found.. This time is the maximum transient t
ime when the measured frequency will stay equal to the Maximum Frequency value.
When the PWM signal is absent, the duty cycle is measured as 0 or 100% based on the
voltage level on the input and the selected Input Polarity. The voltage level is sampled on the
counter saturation events until the PWM signal is back on the input.
The transient time between the PWM signal duty cycle and the duty cycle of the DC level when
the signal disappears can be up to the Maximum Recovery Time. During the transient time, the
measured value will stay equal to the last measured value of the PWM signal duty cycle.
The PWM input signal with a frequency above zero but below the Minimum Frequency value is
not allowed. The duty cycle will not be measured, instead, it will be jumping between 0% and
100% depending on the voltage level at the input on the counter saturation events.
When the PWM input signal frequency exceeds the Maximum Frequency value, the input goes
into the Recovery state and the PWM duty cycle is measured as 0%. Similar to frequency
measurements, the input will stay in the Recovery state for up to the Maximum Recovery Time
before the duty cycle is measured again.
3.3.5 Diagnostics
The ECU has a diagnostic option for Measuring Out of Limits Faults: for low limit and high limit.
The default values can be found in the Section 4.3.3. Disregarding the parameter set in the