AXIOMATIC AX141120 User manual

USER MANUAL UMAX141120
Version 1B
1 Universal Input, Dual CAN
RTC Controller with SAE J1939
USER MANUAL
P/N: AX141120

UM AX141120 Version 1B2-53
ACRONYMS
ACK Positive Acknowledgement
CSR CAN Status Report
DM Diagnostic Message (from SAE J1939 standard)
DTC Diagnostic Trouble Code
FMI Failure Mode Identifier
OC Occurrence Count
EA The Axiomatic Electronic Assistant (A Service Tool for Axiomatic ECUs)
ECU Electronic Control Unit (from SAE J1939 standard)
MAP Memory Access Protocol
NAK Negative Acknowledgement
PDU1 A format for messages that are to be sent to a destination address,
either specific or global
PDU2 A format used to send information that has been labeled using the Group Extension
technique and does not contain a destination address.
PGN Parameter Group Number (from SAE J1939 standard)
PropB Message that uses a Proprietary B PGN
SPN Suspect Parameter Number (from SAE J1939 standard)

UM AX141120 Version 1B3-53
TABLE OF CONTENTS
1. GENERAL INFORMATION ...................................................................................................................................... 5
1.1. INTRODUCTION TO AX141120 FEATURES.................................................................................................................. 5
1.2. J1939 NETWORK –DIAGNOSTIC BROADCAST ........................................................................................................... 5
1.3. CONTROL SOURCES ................................................................................................................................................. 6
1.4. REAL TIME CLOCK FUNCTION BLOCK........................................................................................................................ 6
1.4.1. RTC Enable Time and Date Transmission and Reception ............................................................................................. 6
1.4.2. RTC Enable Source and Number for Date and Time Setting ........................................................................................ 7
1.4.3. RTC Enable Response for Date and Time Setting ......................................................................................................... 7
1.4.4. Actual Time and Date ................................................................................................................................................... 7
1.5. UNIVERSAL INPUT FUNCTION BLOCKS ....................................................................................................................... 8
1.5.1. Universal Input Type .................................................................................................................................................... 9
1.5.2. Universal Input Range .................................................................................................................................................. 9
1.5.3. Universal Input Analog Filter........................................................................................................................................ 9
1.5.4. Universal Input Error and Range .................................................................................................................................. 9
1.5.5. Universal Input Digital Input Parameters................................................................................................................... 10
1.5.6. Universal Input Frequency/PWM Parameters ........................................................................................................... 11
1.5.7. Universal Input Data Filter ......................................................................................................................................... 11
1.5.8. Universal Input Diagnostic Parameters...................................................................................................................... 12
1.6. MISCELLANEOUS .................................................................................................................................................... 12
1.7. DIAGNOSTICS ......................................................................................................................................................... 12
1.8. CONSTANT DATA.................................................................................................................................................... 14
1.9. MATH FUNCTION BLOCK......................................................................................................................................... 14
1.10. PROGRAMMABLE LOGIC FUNCTION BLOCK ........................................................................................................... 15
1.11. LOOKUP TABLE FUNCTION BLOCK ........................................................................................................................ 16
1.12. CONDITIONAL BLOCK ........................................................................................................................................... 17
1.13. SET /RESET LATCH FUNCTION BLOCK.................................................................................................................. 19
1.14. CAN TRANSMIT FUNCTION BLOCK........................................................................................................................ 19
1.15. CAN RECEIVE FUNCTION BLOCK .......................................................................................................................... 20
1.16. VEHICLE IDENTIFICATION NUMBER (VIN) FUNCTION BLOCK ................................................................................... 21
1.17. LED FUNCTION BLOCK......................................................................................................................................... 21
2. OVERVIEW OF J1939 FEATURES ....................................................................................................................... 23
2.1. INTRODUCTION TO SUPPORTED MESSAGES............................................................................................................. 23
2.2. J1939 NAME,ADDRESS AND SOFTWARE ID............................................................................................................ 24
2.2.1. J1939 Name................................................................................................................................................................ 24
2.2.2. ECU Address ............................................................................................................................................................... 24
2.2.3. Software Identifier ..................................................................................................................................................... 25
3. ECU SETPOINTS ACCESSED WITH THE AXIOMATIC ELECTRONIC ASSISTANT ........................................ 26
3.1. J1939 NETWORK SETPOINTS.................................................................................................................................. 26
3.2. REAL TIME CLOCK SETPOINTS................................................................................................................................ 26
3.3. UNIVERSAL INPUT SETPOINTS ................................................................................................................................. 27
3.4. MISCELLANEOUS SETPOINTS .................................................................................................................................. 28
3.5. DIAGNOSTIC SETPOINTS ......................................................................................................................................... 30
3.6. CONSTANT DATA LIST SETPOINTS .......................................................................................................................... 30
3.7. MATH FUNCTIONAL BLOCK SETPOINTS ................................................................................................................... 32
3.8. PROGRAMMABLE LOGIC BLOCK SETPOINTS ............................................................................................................ 34
3.9. LOOKUP TABLE SETPOINTS .................................................................................................................................... 36
3.10. CONDITIONAL BLOCK SETPOINTS.......................................................................................................................... 38
3.11. SET-RESET LATCH BLOCK ................................................................................................................................... 39
3.12. CAN TRANSMIT SETPOINTS .................................................................................................................................. 39
3.13. CAN RECEIVE SETPOINTS .................................................................................................................................... 41
3.14. VEHICLE IDENTIFICATION SETPOINTS..................................................................................................................... 42
3.15. LED SETPOINTS................................................................................................................................................... 43
4. REFLASHING OVER CAN WITH THE AXIOMATIC ELECTRONIC ASSISTANT BOOTLOADER.................... 45
4.1. PREREQUISITES...................................................................................................................................................... 45

UM AX141120 Version 1B4-53
4.2. RE-FLASHING PROCEDURE ..................................................................................................................................... 45
5. INSTALLATION INSTRUCTIONS ......................................................................................................................... 50
6. TECHNICAL SPECIFICATIONS............................................................................................................................ 51
7. VERSION HISTORY............................................................................................................................................... 53

UM AX141120 Version 1B5-53
1. GENERAL INFORMATION
1.1. Introduction to AX141120 Features
The 1UIN-2CAN-RTC electronic control unit (ECU) is designed to provide a simple interface for
Real Time Clock and Universal Input over a Dual J1939 CAN Network, to be used in an industrial
environment. The hardware supports 1 Universal Input.
The ECU has been designed to allow the maximum amount of versatility to optimize the
performance of the machine. Numerous configurable variables, called setpoints, have been
provided which are accessible using Axiomatic Technologies’ Electronic Assistant. Information
about the setpoint defaults and ranges is outlined in Section 3. The Axiomatic EA communicates
with the controller over J1939 CAN port#1 and uses Memory Access Protocol (MAP) to read/write
each setpoint. Once the ECU has been setup as desired, the setpoints can be saved to a file, and
flashed into other controllers over CAN port #1 using the EA.
The ECU is an arbitrary address capable ECU, which can perform dynamic address allocation at
the run time. It also provides all necessary network support required by the J1939 standard.
1.2. J1939 Network – Diagnostic Broadcast

UM AX141120 Version 1B6-53
Diagnostic messages are triggered by the internal function blocks and then broadcast on the CAN
bus network. However, in some applications this broadcast may not be required and so the user
has the option to disable or enable this feature. Section 3.1 shows the configuration of this feature
by using the Axiomatic Electronic Assistant tool.
1.3. Control Sources
The different function blocks in the ECU are commanded by a set of Control Sources. This section
lists the different available control sources for these functions and their respective ranges.
Value
Meaning
Source Range
0
Control Not Used
[0]
1
Universal Input
[1]
2
CAN Receive
[1…5]
3
Constant Data
[1…4]
4
Math Block
[1…4]
5
Programmable Logic Block
[1…2]
6
Lookup Table
[1…6]
7
Conditional Logic Block
[1…10]
8
Set-Reset Latch
[1…3]
9
RTC Seconds
[1...60]
10
RTC Minutes
[1...60]
11
RTC Hours
[1...24]
12
RTC Days
[1...32]
13
RTC Years
[1...100]
14
Transmission of PGN 54528
[1…1]
15
Reception of PGN 54528
[1…1]
Table 1: Control Sources
While these sources are available for all functional blocks, it is not recommended to use Constant
Data as a source in the Set-Reset Latch block. Additionally, it is recommended to set the
Response type as “Jump To” for the Lookup Table if it is used as a control source for the Real
Time Clock or LED. When the Lookup table is an output of the Programmable Logic, and the
Programmable Logic controls the RTC or LED, the Response Type should also be set to “Jump
To”.
When the Transmission of PGN 54528 is set as a control source, the state will be active for the
next 100ms after the message has been transmitted. Also, when the Reception of PGN 54528 is
set as a control source, the state will be active for the next 500ms upon receiving the message.
1.4. Real Time Clock Function Block
The Real Time Clock of the controller can be configured via CAN. The RTC can be used as a
control source for all available logic blocks. The subsection below explains the functionality and
available parameters in more detail.
1.4.1. RTC Enable Time and Date Transmission and Reception

UM AX141120 Version 1B7-53
The Enable Time and Date PGN 54528 transmission and Enable Time and Date PGN 54528
reception parameters allow to set on which CAN interface transmission and reception will happen.
The data transmitted is set according to the SAE J1939-71 standard. The possible options are
listed in the Table 2. By default, both, CAN #1 and CAN #2 are enabled. The unit also supports the
Time/Date PGN (65254) by populating a Time/Date CAN message. Refer to the Section 2 and
PGNs and to J1939-71 Standard for the detailed information.
Value
Meaning
0
Disabled
1
Only to CAN #1
2
Only to CAN #2
3
To Both CAN Interfaces
Table 2: Options for Reception and Transmission
1.4.2. RTC Enable Source and Number for Date and Time Setting
The Real Time Clock can be controlled by all control sources mentioned in Table 1. The device
constantly checks the condition of the control source and reacts according to the value set in
Enable Response for Date and Time Setting setpoint. For example, if Enable Source for Date
and Time Setting is set to RTC Minutes and Enable Number for Date and Time Setting is set to
10, the RTC will respond accordingly on the 10th minute of each hour (ex. 01:10:00, 02:10:00, etc.).
The default option is To Both CAN Interfaces.Control sources allow to configure the unit in an
flexible and application specific way.
1.4.3. RTC Enable Response for Date and Time Setting
The Enable Response for Date and Time Setting has two options listed in Table 3. These
options define the behavior of the unit during the triggering of the control source. First option
enables both CAN Interfaces for transmission when control event happens. Second option works
in an opposite way. By default, the Enable When On is set.
Value
Meaning
0
Enable When On
1
Enable When Off
Table 3: Enable Response Types
1.4.4. Actual Time and Date
Beside transmission and reception of the time and date the AX141120 shows the actual time and
date under Real Time Clock setpoint block. The time is shown in the following format: HH:MM:SS
and the date is shown as YYYY/MM/DD. All these parameters are not configurable and presented
in a read only format. To refresh the time shown, the page in the Axiomatic EA should be refreshed
or values under Enable Time and Date PGN 54528 Transmission or Enable Source for Date
and Time Transmission should be altered.
Additionally, the Time Zone setpoint is configurable. The ECU supports 37 different time zones
starting from UTC-12 to UTC+14. The device updates this value when the time zone changes via
CAN or is changed manually. The change of the Time Zone setpoint will alter the transmitted time
and date respective to the UTC being set. Receiving the CAN Time/Date Adjust message will reset

UM AX141120 Version 1B8-53
the time shown along with a set time zone, so the ECU will consider the received time as already
updated to the given time zone and will not recalculate it. The list of all time zones available is
listed in Table 4below.
Value
Meaning
0
UTC-12
1
UTC-11
2
UTC-10
3
UTC-9:30
4
UTC-9
5
UTC-8
6
UTC-7
7
UTC-6
8
UTC-5
9
UTC-4
10
UTC-3
11
UTC-2:30
12
UTC-2
13
UTC-1
14
UTC+0
15
UTC+1
16
UTC+2
17
UTC+3
18
UTC+4
19
UTC+4:30
20
UTC+5
21
UTC+5:30
22
UTC+5:45
23
UTC+6
24
UTC+6:30
25
UTC+7
26
UTC+8
27
UTC+8:45
28
UTC+9
29
UTC+9:30
30
UTC+10
31
UTC+10:30
32
UTC+11
33
UTC+12
34
UTC+12:45
35
UTC+13
36
UTC+14
Table 4: List of Supported Time Zones
1.5. Universal Input Function Blocks
The universal input of the controller can be configured as a variety of different input types. The
input can be used as control sources for CAN output, as well as other logic blocks. The sub

UM AX141120 Version 1B9-53
sections below explain in more detail the functionality and available setpoints/parameters of the
universal input.
1.5.1. Universal Input Type
The Input Type parameter allows the user to select how the controller responds to the behaviour
of the input. Table 5 shows the different options for each input.
Value
Meaning
0
Input Disabled
1
Voltage Input
2
Current Input
3
Digital Input
4
Frequency Input
5
PWM Input
Table 5: Universal Input Types
1.5.2. Universal Input Range
The Input Range parameter is used to specify the expected range of Voltage or Current inputs. It
is disabled for other input types. Table 6 shows the options available for this parameter when a
Voltage Input is selected, and Table 7 show the options for a Current Input.
Value
Meaning
0
0 - 5V Analog Input
1
0 - 10V Analog Input
Table 6: Voltage Input Ranges
Value
Meaning
0
0 - 20mA Analog Input
1
4 - 20mA Analog Input
Table 7: Current Input Ranges
1.5.3. Universal Input Analog Filter
The Analog Filter parameter is only applicable when a voltage or a current type is being measured.
In these cases, the ADC will automatically filter as per Table 8, and is set for 50Hz noise rejection
by default.
Value
Meaning
0
Input Filter Off
1
Filter 50Hz
2
Filter 60Hz
3
Filter 50Hz and 60Hz
Table 8: Analog Filter
1.5.4. Universal Input Error and Range

UM AX141120 Version 1B10-53
Each Input can have different Input Ranges which can be configured. The Range Min and Range
Max parameters are used to set the range for the input. The Error Min and Error Max parameters
are used to set when the accompanying diagnostic message will be triggered.
1.5.5. Universal Input Digital Input Parameters
If the Input is configured as a Digital Input, the following setpoints become available to help
configure the input.
The Pull Up/Down parameter is used to change the configuration of internal resistors with the
following options.
Value
Meaning
0
No Pull
1
Pull Up Network
2
Pull Down Network
Table 9: Digital Input Pull Up/Down
The Logic Type parameter is used to determine how the input is received when configured as a
Digital Input.
Value
Meaning
0
Input Not Implemented
1
Normal Logic
2
Inverse Logic
3
Latched Logic
4
Inverse Latched Logic
Table 10: Digital Input Logic Type
By default, the Normal Logic type is used for the digital input.
In Normal Logic mode, the input state is 1 in case the input signal is interpreted as an ON-signal.
The input state turns 0 if the input signal is interpreted as an OFF-signal.
For the Inverse Logic type, the opposite behavior applies. If the input signal is ON, the state turns 0
and if the input signal is OFF, the state turns 1.
Setting the Input to Latched Logic, the input state is toggled between 1 and 0 every time the input
signal of the respective digital input changes from OFF to ON.
In Inverse Latched Logic mode, the opposite behavior applies. The input state toggles between 1
and 0 every time the input signal changes from ON to OFF.
The Digital Input Debounce Time parameter is a useful parameter in cases where the digital input
signal coming into the controller is noisy. Figure 1 shows how the Debounce Time helps detect a
correct input signal.

UM AX141120 Version 1B11-53
Debounce Time
Input Remains OFF
Input = OFF
Input = ON
Change of state detected,
Debounce time started
Figure 1: Digital Input Debounce Time
1.5.6. Universal Input Frequency/PWM Parameters
If the Input is configured as either a Frequency Input or a PWM Input, then the following
parameters become available.
The PWM Debounce Filter is applied to the input before the state is read by the processor. The
options for this setpoint are shown in Table 11.
Value
Meaning
0
Filter Disabled
1
Filter 111ns
2
Filter 1.78 us
3
Filter 14.22 us
Table 11: PWM Debounce Filter
The Number of Pulses per Revolution parameter, if greater than 0, will convert a frequency input
into RPM instead of Hertz, based on the value entered.
1.5.7. Universal Input Data Filter
All analog inputs (Voltage or Current) can be further filtered once the raw data has been measured.
The Data Filter Type parameter determines what kind of filter is used per Table 12. By default,
additional software filtering is disabled.
Value
Meaning
0
No Filter
1
Moving Average
2
Repeating Average
Table 12: Data Filter Type
The Data Filter Constant is used with all types of filters as per the formulas below:
Calculation with no filter:
Value = Input
The data is simply a ‘snapshot’ of the latest value measured by the ADC or timer.

UM AX141120 Version 1B12-53
Calculation with the moving average filter:
ValueN= ValueN-1 +
This filter is called every 1ms
Calculation with the repeating average filter:
Value =
At every reading of the input value, it is added to the sum. At every Nth read, the sum is divided by
N, and the result is the new input value. The value and counter will be set to zero for the next read.
This filter is called every 1ms.
1.5.8. Universal Input Diagnostic Parameters
The Error Detection Enabled setpoint allows for diagnostic warnings for the input to be triggered
or be disabled. If enabled, the Error Clear Hysteresis is used to set the hysteresis value at which
an input error can be cleared. Lastly, the Error Delay setpoint is directly linked to the same
parameter for the all diagnostics associated with the particular Universal Input, and can be used to
set all of them to the same value.
1.6. 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 Setting parameter is used to control all diagnostics with one general
setting for each CAN Interface independent of the other. This can be used to disable diagnostics
entirely, only transmit messages without a blank SPN, or transmit diagnostic messages normally.
1.7. Diagnostics
The Diagnostic function block includes six faults, each representing a diagnostic message that the
ECU is able to produce. Each Digital Output has a set of accompanying faults, all six outputs have
an Open Circuit, Short To VCC, and Short To Ground fault. While the two low-sourced outputs
have an additional Overcurrent fault. 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)
(Input – ValueN-1)
FilterConstant
Σ
InputN
N

UM AX141120 Version 1B13-53
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 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 will not 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

UM AX141120 Version 1B14-53
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 13. If the
FMI is changed, the OC of the associate error log is automatically reset to zero.
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
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
Table 13: Low Fault FMI versus High Fault FMI
If the FMI used is anything other than one of those in Table 13, 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. It is the user’s responsibility to make sure this does not
happen.
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.
1.8. Constant Data
The Constant Data Block contains four configurable constant data setpoints which can be used as
a control source for other functions. While they are available as a control source to all functions, it
is recommended not to use constant data as a control source for the Set-Reset Latch Block.
1.9. Math Function Block

UM AX141120 Version 1B15-53
There are four mathematical function blocks that allow the user to define basic algorithms. A math
function block can take up to six input signals. Each input is then scaled according to the
associated limit and scaling setpoints.
Inputs are converted into percentage value based on the “Input X Minimum” and “Input X
Maximum” values selected. For additional control the user can also adjust the “Input X Decimal
Digits” setpoint to increase the resolution of the input data and the min and max values.
A mathematical function block includes three selectable functions, in which each implements
equation A operator B, where A and B are function inputs and operator is function selected with a
setpoint “Math Function X”. Setpoint options are presented in Table 14. The functions are
connected together, so that result of the preceding function goes into Input A of the next function.
Thus Function 1 has both Input A and Input B selectable with setpoints, where Functions 2 to 4
have only Input B selectable. Input is selected by setting “Function X Input Y Source” and
“Function X Input Y Number”. If “Function X Input B Source” is set to 0 ‘Control not used’ signal
goes through function unchanged.
  =󰇡(1 1 1)2 23 3 󰇢4 4
0
=, True when InA equals InB
1
!=, True when InA not equal InB
2
>, True when InA greater than InB
3
>=, True when InA greater than or equal InB
4
<, True when InA less than InB
5
<=, True when InA less than or equal InB
6
OR, True when InA or InB is True
7
AND, True when InA and InB are True
8
XOR, True when either InA or InB is True, but not both
9
+, Result = InA plus InB
10
-, Result = InA minus InB
11
x, Result = InA times InB
12
/, Result = InA divided by InB
13
MIN, Result = Smallest of InA and InB
14
MAX, Result = Largest of InA and InB
Table 14: Math function X Operator Options
For logic operations (6, 7, and 8) scaled input greater than or equal to 1 is treated as TRUE. For
logic operations (0 to 8), the result of the function will always be 0 (FALSE) of 1 (TRUE). For the
arithmetic functions (9 to 14), it is recommended to scale the data such that the resulting operation
will not exceed full scale (0 to 100%) and saturate the output result.
When dividing, a zero divider will always result in a 100% output value for the associated function.
Lastly the resulting mathematical calculation, presented as a percentage value, can be scaled into
the appropriate physical units using the “Math Output Minimum Range” and “Math Output
Maximum Range” setpoints. These values are also used as the limits when the Math Function is
selected as the input source for another function block.
1.10. Programmable Logic Function Block
The Programmable Logic Function Block is a powerful tool. Programmable Logic can be linked to
up to three Lookup Tables, any of which would be selected only under given conditions. Thus, the
output of a Programmable Logic at any given time will be the output of the Lookup Table selected

UM AX141120 Version 1B16-53
by the defined logic. Therefore, up to three different responses to the same input, or three different
responses to different inputs, can become the input to another function block.
In order to enable any one of the Programmable Logic blocks, the “Logic Enabled” setpoint must
be set to ‘True’. By default, all Logic blocks are disabled.
The three associated tables are selected by setting “Table Number X” setpoint to desired Lookup
Table number, for example selecting 1would set Lookup Table 1 as TableX.
For each TableX there are three conditions that define the logic to select the associated Lookup
Table as Logic output. Each condition implements function 1  2
where Operator is logical operator defined by setpoint “Table X – Condition Y Operator”. Setpoint
options are listed in Table 15. Condition arguments are selected with “Table X – Condition Y
Argument Z Source” and “Table X – Condition Y Argument Z Number” setpoints. If ‘0 – Control
not Used’ option is selected as “Table x – Condition Y Argument Z Source” the argument is
interpreted as 0.
0
=, Equal
1
!=, Not Equal
2
>, Greater Than
3
>=, Greater Than or Equal
4
<, Less Than
5
<=, Less Than or Equal
Table 15: Table X – Condition Y Operator Options
The three conditions are evaluated and if the result satisfies logical operation defined with “Logical
Operator X” setpoint, given in Table 16, the associated Lookup Table is selected as output of the
Logical block. Option ‘0 – Default Table’ selects associated Lookup Table in all conditions.
0
Default Table (Table1)
1
Cnd1 And Cnd2 And Cnd3
2
Cnd1 Or Cnd2 Or Cnd3
3
(Cnd1 And Cnd2) Or Cnd3
4
(Cnd1 Or Cnd2) And Cnd3
Table 16: Table X – Conditions Logical Operator Options
The three logical operations are evaluated in order and the first to satisfy gets selected, thus if
Table1 logical operation is satisfied, the Lookup Table associated with Table1 gets selected
regardless of two other logical operations. In addition, if none of the logical operations is satisfied
the Lookup Table associated with Table1 gets selected.
1.11. Lookup Table Function Block
Lookup Tables are used to give output response up to 10 slopes per input. If more than 10 slopes
are required, A Programmable Logic Block can be used to combine up to three tables to get 30
slopes as described in Section 1.10.
Lookup tables have two differing modes defined by “X-Axis Type” setpoint, given in Table 17.
Option ‘0 – Data Response’ is the normal mode where block input signal is selected with the “X-
Axis Source” and “X-Axis Number” setpoints and X values present directly input signal values.
With option ‘1 – Time Response’ the input signal is time and X values present time in milliseconds.
And selected input signal is used as digital enable.

UM AX141120 Version 1B17-53
0
Data Response
1
Time Response
Table 17: X-Axis Type Options
The slopes are defined with (x, y) points and associated point response. X value presents input
signal value and Y value corresponding Lookup Table output value. “PointN – Response” setpoint
defines type of the slope from preceding point to the point in question. Response options are given
in Table 18. ‘Ramp To’ gives a linearized slope between points, whereas ‘Jump to’ gives a point to
point response, where any input value between XN-1 and XNwill result Lookup Table output being
YN. “Point0 – Response” is always ‘Jump To’ and cannot be edited. Choosing ‘Ignored’ response
causes associated point and all the following points to be ignored.
0
Ignore
1
Ramp To
2
Jump To
Table 18: PointN – Response Options
The X values are limited by minimum and maximum range of the selected input source if the
source is a Math Function Block. For the fore mentioned sources X-Axis data will be redefined
when ranges are changed, therefore inputs should be adjusted before changing X-Axis values. For
other sources Xmin and Xmax are -100000 and 1000000. The X-Axis is constraint to be in rising
order, thus value of the next index is greater than or equal to preceding one. Therefore, when
adjusting the X-Axis data, it is recommended that X10 is changed first, then lower indexes in
descending order.
 <= <= <= <= <= <= <= <= <= <= <=  <= 
The Y-Axis has no constraints on the data it presents, thus inverse, decreasing, increasing or other
response can be easily established. The Smallest of the Y-Axis values is used as Lookup Table
output min and the largest of the Y-Axis values is used as Lookup Table output max (i.e. used as
Xmin and Xmax values in linear calculation). Ignored points are not considered for min and max
values.
1.12. Conditional Block
The Conditional Block compares up to four different input sources with different logical or relational
operators. The result of each block can therefore only be true (1) or false (0). Figure 2
demonstrates the connections between all parameters.

UM AX141120 Version 1B18-53
Figure 2: Conditional Block Diagram
Each Conditional Block offers two conditions. Both compare two inputs, which can hold a logical
value or an integer value. The output of the conditions can only be true or false and will be
compared by Operator 3 with a logical operator. This comparison is the result of the Conditional
Block and can control any output source.
value of each source will then be compared to each other with an operator of Table 19. If no
source is selected, the output value of an Input will be zero.
Value
Meaning
0
==, True when Argument 1 is equal to Argument 2
1
!=, True when Argument 1 is not equal to Argument 2
2
>, True when Argument 1 is greater than Argument 2
3
>=, True when Argument 1 is greater than Argument 2
4
<, True when Argument 1 is less than Argument 2
5
<=, True when Argument 1 is less than or equal Argument 2
6
OR, True when Argument 1 or Argument 2 is True
7
AND, True when Argument 1 and Argument 2 are True
Table 19: Input Operator Options
Operator 1 and Operator 2 are configured to OR by default. The table above cannot be used for
comparing the conditions because they can only be compared with logical operators, which are
listed in Table 20.
Value
Meaning
0
OR, True when Argument 1 or Argument 2 is True
1
AND, True when Argument 1 and Argument 2 are True
2
XOR, True when Argument 1 is not equal to Argument 2
Table 20: Condition Operator Options

UM AX141120 Version 1B19-53
If only one condition is used, it is to make sure that Operator 3 is set to OR so that the result is based
solely on the condition which has been chosen.
1.13. Set / Reset Latch Function Block
Set-Reset Block consists of only 2 control sources: Reset Source and Set Source. The purpose
of these blocks is to simulate a modified latching function in which the ‘Reset Signal’ has more
precedence. The ‘latching’ function works as per the Table 21 below.
‘Set Signal’
‘Reset Signal’
‘Set-Reset Block Output’
(Initial State: OFF)
OFF
OFF
Latched State
OFF
ON
OFF
ON
OFF
ON
ON
ON
OFF
Table 21 – Set-Reset Function block operation
The Reset and Set sources have associated with them a minimum and maximum threshold values
which determine the ON and OFF state. For the Reset Source are Reset Minimum Threshold
and Reset Maximum Threshold. Similarly, for the Set Source are Set Minimum Threshold and
Set Maximum Threshold. These setpoints also allow to have a dead band in between ON/OFF
states and they are in terms of percentage of input selected.
As seen in Table 21 above, the ‘Reset Signal’ has more precedence over the ‘Set Signal’ - if the
state of ‘Reset Signal’ is ON, the state of ‘Set-Reset Block Output’ will be OFF. To create an ON
state in ‘Set-Reset Block Output’ the state of ‘Reset Signal’ must be OFF while the state of ‘Set
Signal’ is ON. In this case, the state of ‘Set-Reset Block Output’ will remain ON even if ‘Set Signal’
turns OFF as long as ‘Reset Signal’ remains OFF. As soon as the ‘Reset Signal’ turns ON the ‘Set-
Reset Block Output’ will turn OFF regardless of the state of ‘Set Signal’.
1.14. CAN Transmit Function Block
The ECU provides up to 5 fully configurable CAN Transmit messages. Each block can be designated
to a CAN Interface and has its own PGN. Different transmit messages that share a PGN will be
broadcast together as one message. Additionally, the ECU can populate two more messages:
Time/Date Adjust (PGN 54528; generates every 1000 ms), and Time/Date (PGN 65254; ECU
generates as a response from a PGN Request message with the contents of Time/Date as per
J1939-71 65254 PGN).
The CAN transmit message is always enabled and the Repetition Rate defines which time in
milliseconds the CAN transmit message is repeated. The CAN message will not transmit on the
J1939 network in case all CAN transmits have the same PGN and the Repetition Rate of the first
CAN transmit is set to zero. In the case of shared PGNs the rate of the lowest number CAN
Transmit is used, i.e. if CAN Transmit 1 and CAN Transmit 4 share a PGN, the Repetition Rate of
CAN Transmit 1 is used.
The CAN Transmit messages can be sent on any Proprietary A or B PGN as broadcast messages.
By default, the Message Priority is set to 6 (low priority).
The Destination Address of the J1939 Identifier can be changed to any value between 0…255.

UM AX141120 Version 1B20-53
The Data Size,Data Index in Array (LSB), Bit Index in Byte (LSB), Resolution,and Offset can
all be used to map any SPN supported message by the J1939 standard from any Data
Source/Number of the Transmit Function Block.
1.15. CAN Receive Function Block
The ECU supports up to 5 unique fully configurable CAN Receive Messages. The CAN Receive
function block is designed to take any SPN from the J1939 network and use it as a Control
Source for any relay outputs or CAN transmits. The ECU also can receive a Time/Date Adjust
message to adjust current time and date in the RTC as a separate block.
The input must specify which CAN Interface is to be used to receive data.
The Receive Message Enabled is the most important setpoint associated with this function block
and it should be selected first. Changing it will result in other setpoints being enabled/disabled as
appropriate. By default, all receive messages are disabled.
Once a message has been enabled, a Lost Communication fault will be flagged if that message is
not received within the Receive Message Timeout period if this has been set to 10ms or higher.
This will trigger a Lost Communication event and the output data of the CAN Receive message will
be set to 0. To avoid timeouts (if set to 10ms or higher) on a heavily saturated network, it is
recommended to set the period at least three times longer than the expected update rate. To
disable the timeout feature, simply set this value to zero, in which case the received message will
never timeout and will never trigger a Lost Communication event.
By default, all control messages are expected to be sent to the ECU on Proprietary B PGNs.
However, should a PDU1 message be selected, the ECU can be configured to receive it from any
ECU by setting the Specific Address that sends the PGN to the Global Address (0xFF). If a
specific address is selected instead, then any other ECU data on the PGN will be ignored.
The Data Size, Data Index in Array (LSB), Bit Index in Byte (LSB), Resolution and Offset can
all be used to map any SPN supported by the J1939 standard to the output data of the Received
function block.
The Data Min (Off Threshold) and Data Max (On Threshold) setpoints determine the minimum and
maximum values of the control signal. As the names imply, they are also used as the ON/OFF
thresholds for digital level types. These values are in whatever units the incoming data is after the
resolution and offset are applied to the CAN Receive signal.
To have a CAN Receive message trigger, a relay output ON or OFF is to make sure the Data Min
(OFF Threshold) and Data Max (ON Threshold) parameters are adjusted to the user’s
application. When the CAN Receive message (after having the resolution and offset applied to it),
anything at Data Max (ON Threshold) parameter or higher, will trigger an ON command. Similarly,
anything at Data Min (OFF Threshold) parameter or lower will trigger an OFF command. Any data
in between will not change the state, thus providing a hysteresis. Figure 3 illustrates this behaviour.