AXIOMATIC UMAX030440 User manual

USER MANUAL UMAX030440
Version 2B
4 Universal Signal Inputs, 5V/8V Voltage Reference,
CAN Controller with SAE J1939
USER MANUAL
P/N: AX030440

UMAX030440 Version 2B 2-51
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 Axiomatic Electronic Assistant (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)

UMAX030440 Version 2B 3-51
TABLE OF CONTENTS
1.1. INTRODUCTION TO AX030440 FEATURES.................................................................................................................. 4
1.2. J1939 NETWORK –DIAGNOSTIC BROADCAST ........................................................................................................... 4
1.3. UNIVERSAL INPUT..................................................................................................................................................... 5
1.3.1. Control Sources............................................................................................................................................................5
1.3.2. Universal Input Type ....................................................................................................................................................5
1.3.3. Universal Input Range.................................................................................................................................................. 5
1.3.4. Universal Input Analog Filter........................................................................................................................................6
1.3.5. Universal Input Error and Range..................................................................................................................................6
1.3.6. Universal Input Digital Input Parameters.....................................................................................................................6
1.3.7. Universal Input Frequency/PWM Parameters .............................................................................................................7
1.3.8. Universal Input Data Filter ...........................................................................................................................................8
1.3.9. Universal Input Diagnostic Parameters........................................................................................................................8
1.4. MISCELLANEOUS...................................................................................................................................................... 8
1.5. DIAGNOSTICS........................................................................................................................................................... 9
1.6. CONSTANT DATA.................................................................................................................................................... 11
1.7. MATH FUNCTION BLOCK......................................................................................................................................... 11
1.8. PROGRAMMABLE LOGIC FUNCTION BLOCK ............................................................................................................. 12
1.9. LOOKUP TABLE FUNCTION BLOCK.......................................................................................................................... 13
1.10. CONDITIONAL BLOCK ........................................................................................................................................... 14
1.11. SET /RESET LATCH FUNCTION BLOCK.................................................................................................................. 15
1.12. CAN TRANSMIT FUNCTION BLOCK........................................................................................................................ 15
1.13. CAN RECEIVE FUNCTION BLOCK.......................................................................................................................... 16
2. OVERVIEW OF J1939 FEATURES....................................................................................................................... 18
2.1. INTRODUCTION TO SUPPORTED MESSAGES............................................................................................................. 18
2.2. J1939 NAME,ADDRESS AND SOFTWARE ID............................................................................................................ 19
2.2.1. J1939 Name................................................................................................................................................................19
2.2.2. ECU Address ...............................................................................................................................................................19
2.2.3. Software Identifier .....................................................................................................................................................20
3. ECU SETPOINTS ACCESSED WITH ELECTRONIC ASSISTANT...................................................................... 21
3.1. J1939 NETWORK SETPOINTS.................................................................................................................................. 21
3.2. UNIVERSAL INPUT SETPOINTS................................................................................................................................. 21
3.3. MISCELLANEOUS SETPOINTS .................................................................................................................................. 22
3.4. DIAGNOSTIC SETPOINTS ......................................................................................................................................... 23
3.5. CONSTANT DATA LIST SETPOINTS .......................................................................................................................... 24
3.6. MATH FUNCTIONAL BLOCK SETPOINTS ................................................................................................................... 24
3.7. PROGRAMMABLE LOGIC BLOCK SETPOINTS............................................................................................................ 26
3.8. LOOKUP TABLE SETPOINTS .................................................................................................................................... 28
3.9. CONDITIONAL BLOCK SETPOINTS............................................................................................................................ 29
3.10. SET-RESET LATCH BLOCK ................................................................................................................................... 30
3.11. CAN TRANSMIT SETPOINTS.................................................................................................................................. 31
3.12. CAN RECEIVE SETPOINTS.................................................................................................................................... 33
3.13. 5V TO 8V REFERENCE SWITCH ............................................................................................................................. 34
4. REFLASHING OVER CAN WITH ELECTRONIC ASSISTANT BOOTLOADER ................................................. 35
4.1. PREREQUISITES...................................................................................................................................................... 35
4.2. RE-FLASHING PROCEDURE ..................................................................................................................................... 35
5. INSTALLATION INSTRUCTIONS ......................................................................................................................... 40
6. TECHNICAL SPECIFICATIONS............................................................................................................................ 41
Reverse polarity protection up to -100V..................................................................................................................................41
User selectable .........................................................................................................................................................................41
+5V/+8V, 100 mA, 2% reference voltage output......................................................................................................................41
7. VERSION HISTORY............................................................................................................................................... 43

UMAX030440 Version 2B 4-51
GENERAL INFORMATION
1.1. Introduction to AX030440 Features
The 4UIN-8VREF-2CAN electronic control unit (ECU) is designed to provide a simple interface for
Universal Inputs over a J1939 CAN Network, to be used in a power generator set or industrial
environment. The hardware supports 4 Universal Inputs. The universal inputs accept voltage,
current, resistance, frequency, PWM duty cycle, and discrete voltage levels. A +8V or +5V
reference voltage output can be used to power external sensors/equipment. The voltage reference
level can be configured using EA.
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 EA communicates with the
controller over J1939 CAN bus 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 using 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
Diagnostic messages are triggered by the internal function blocks and then broadcasted on the
CAN bus network. However, in some applications this broadcast may not be required and so the

UMAX030440 Version 2B 5-51
user has the option to disable or enable this feature. Section 1.4 and 3.3 shows the configuration
of this feature by using the Electronic Assistant tool.
1.3. Universal Input
1.3.1. 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…4]
2
CAN Receive
[1…10]
3
Constant Data
[1…15]
4
Math Block
[1…5]
5
Programmable Logic Block
[1…3]
6
Lookup Table
[1…10]
7
Conditional Logic Block
[1…10]
8
Set-Reset Latch
[1…5]
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.
1.3.2. Universal Input Type
The Input Type parameter allows the user to select how the controller responds to the behaviour
of the input. Table 2 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
6
Resistive Input
Table 2: Universal Input Types
1.3.3. 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 3 shows the options available for this parameter when a
Voltage Input is selected, and Table 4 show the options for a Current Input.
Value
Meaning
0
0 - 5V Analog Input

UMAX030440 Version 2B 6-51
1
0 - 10V Analog Input
Table 3: Voltage Input Ranges
Value
Meaning
0
0 - 20mA Analog Input
1
4 - 20mA Analog Input
Table 4: Current Input Ranges
Also, the Pull Up/Down parameter can be set when the Input Type is set to Voltage Input and
Input Range is set to 0-5V Analog Input. It allows the ECU to work in two modes for this input
range: 5V in High Impedance and 5V with 10kOhm Impedance.
Note: It is only possible to set the pull-down resistor either high or low if the Input Type is set to
Input Voltage. If 10kOhm pull-down is disabled, the ECU will run in 5V in High Impedance mode.
Setting the pull-up resistor option is not available for this input type.
1.3.4. 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 5, 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 5: Analog Filter
1.3.5. Universal Input Error and Range
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.3.6. 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 6: 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

UMAX030440 Version 2B 7-51
0
Input Not Implemented
1
Normal Logic
2
Inverse Logic
3
Latched Logic
4
Inverse Latched Logic
Table 7: 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 behaviour 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.
Debounce Time
Input Remains OFF
Input = OFF
Input = ON
Change of state detected,
Debounce time started
Figure 1: Digital Input Debounce Time
1.3.7. 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 8.
Value
Meaning
0
Filter Disabled
1
Filter 111ns

UMAX030440 Version 2B 8-51
2
Filter 1.78 us
3
Filter 14.22 us
Table 8: 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.3.8. 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 9. By default,
additional software filtering is disabled.
Value
Meaning
0
No Filter
1
Moving Average
2
Repeating Average
Table 9: 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.
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.3.9. Universal Input Diagnostic Parameters
The Error Clear Hysteresis is used to set the hysteresis value at which an input error can be
cleared.
1.4. Miscellaneous
The Miscellaneous function block contains various parameters that affect the general diagnostic
performance of the ECU.
(Input –ValueN-1)
FilterConstant

InputN
N

UMAX030440 Version 2B 9-51
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 CAN Interface. This can be used to disable diagnostics entirely, only transmit messages
without a blank SPN, or transmit diagnostic messages normally.
1.5. Diagnostics
The Diagnostic function block includes twelve 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. 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 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.

UMAX030440 Version 2B 10-51
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 10. 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 10: Low Fault FMI versus High Fault FMI
If the FMI used is anything other than one of those in Table 10, then both the low and
the high faults will be assigned the same FMI. This condition should be avoided, as the