AXIOMATIC AX090690 User manual

USER MANUAL UMAX090690
Version V1.3
Dual 12V Li-ion BATTERY CHARGER
With SAEJ1939
USER MANUAL
P/N: AX090690

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 2-37
ACCRONYMS
ACK Positive Acknowledgement (from SAE J1939 standard)
CAN Controller Area Network
DM Diagnostic Message (from SAE J1939 standard)
DTC Diagnostic Trouble Code
EA Electronic Assistant, p/n AX070502 (A Service Tool for Axiomatic ECUs)
ECU Electronic Control Unit (from SAE J1939 standard)
FMI Failure Mode Identifier
NAK Negative Acknowledgement (from SAE J1939 standard)
PDU1 A format for messages that are to be sent to a destination address, either specific
or global (from SAE J1939 standard)
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)
PropA Message that uses the Proprietary A PGN for peer-to-peer communication
PropB Message that uses a Proprietary B PGN for broadcast communication
PWM Pulse Width Modulation
OC Occurrence Count
SPN Suspect Parameter Number (from SAE J1939 standard)
VPS Voltage Power Supply

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 3-37
TABLE OF CONTENTS
1. INTRODUCTION.......................................................................................................................6
2. BATTERY CHARGER THEORY OF OPERATION...................................................................7
2.1. BATTERY CHARGER MODES ............................................................................................................................... 7
Charger Temperature...................................................................................................................................................8
2.2. BATTERY CHARGER STATE DIAGRAM ................................................................................................................. 9
2.3. BATTERY PROTECTION....................................................................................................................................... 9
3. OVERVIEW OF J1939 FEATURES........................................................................................11
3.1. INTRODUCTION TO SUPPORTED MESSAGES....................................................................................................... 11
3.2. NAME,ADDRESS AND SOFTWARE ID................................................................................................................. 12
J1939 Name................................................................................................................................................................ 12
ECU Address ............................................................................................................................................................... 12
Software Identifier .....................................................................................................................................................13
4. BATTERY CHARGER FUNCTION BLOCKS.........................................................................15
4.1. CHARGING PROFILE FUNCTION BLOCKS............................................................................................................ 15
4.2. MISCELLANEOUS INPUT FUNCTION BLOCK ........................................................................................................ 15
4.3. J1939 NETWORK FUNCTION BLOCK ................................................................................................................. 15
4.4. DIAGNOSTIC INPUT FUNCTION BLOCKS ............................................................................................................. 15
4.5. CAN TRANSMIT FUNCTION BLOCK.................................................................................................................... 18
4.6. CAN RECEIVE FUNCTION BLOCK...................................................................................................................... 19
5. ECU SETPOINTS ACCESSED WITH ELECTRONIC ASSISTANT .......................................21
5.1. NETWORK SETPOINTS ...................................................................................................................................... 21
5.2. COMMON CAN SETPOINTS............................................................................................................................... 21
5.3. CHARGING PROFILE SETPOINTS........................................................................................................................ 22
5.4. MISCELLANEOUS INPUT SETPOINTS .................................................................................................................. 24
5.5. DIAGNOSTIC INPUT SETPOINTS ......................................................................................................................... 24
5.6. CAN RECEIVE SETPOINTS................................................................................................................................ 25
5.7. CAN TRANSMIT SETPOINTS.............................................................................................................................. 26
6. BATTERY CHARGER ERROR CODES.................................................................................28
6.1. BATTERY ERROR CODES.................................................................................................................................. 28
7. REFLASHING OVER CAN WITH EA BOOTLOADER.......................................................29
8. INSTALLATION INSTRUCTIONS...........................................................................................34
9. TECHNICAL SPECIFICATIONS.............................................................................................35
9.1. INPUT SPECIFICATIONS..................................................................................................................................... 35
9.2. OUTPUT SPECIFICATIONS ................................................................................................................................. 35
9.3. GENERAL SPECIFICATIONS ............................................................................................................................... 35
10. VERSION HISTORY................................................................................................................37

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 4-37
Table 1 - Charger LED State Values............................................................................................6
Table 2 –Charger Mode Values .................................................................................................8
Table 3 –CAN Transmit Data Sources ......................................................................................18
Table 4 –Default CAN Transmit Messages................................................................................19
Table 5 –Default Network Setpoints ........................................................................................21
Table 6 –Default Common Control Setpoints............................................................................22
Table 7 –Default Charging Profile Setpoints .............................................................................23
Table 8 –Default Display Board Setpoints ................................................................................24
Table 9 –Default CAN Receive Setpoints..................................................................................25
Table 10 –Default CAN Transmit Setpoints ..............................................................................27
Table 11 –Error Codes............................................................................................................28

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 5-37
Figure 1. Battery Charger Algorithm Profile.................................................................................7
Figure 2 . Voltage-Current Charging Profile ..................................................................................7
Figure 3 . Battery Charger State Diagram ....................................................................................9

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 6-37
1. INTRODUCTION
The battery charger is designed to autonomously charge dual sided batteries. The AX090690
model can charge dual 12V batteries with a maximum charging current of 1.25A
Once programmed, the charger does not require any operator’s involvement in the charging
process; the charger automatically recognizes the presence of the battery, charges the battery to
the maximum capacity, and automatically maintains the battery charge if the charger is connected
to the power line. The charger will continue to charge the battery even if disconnected from the
J1939 CAN network.
When the charger is disconnected from the power line it automatically switches off, protecting the
batteries from discharge.
There are three main charge modes –Precharge Mode, Bulk Charge Mode, and Constant Voltage
Charge Mode –along with Float Mode for maintaining charge. Temperature sensing using an
auxiliary temperature sensor or through the J1939 network protects batteries from overheating,
shutting down the charging process if the battery temperature exceeds a certain level.
An internal red-green LED indicator on the front panel of the charger is used to monitor the internal
state of the charger. The charger states and corresponding LED indications are described in Table
1.
LED State
Description
Red/Green (Flashing)
Idle.
Green (Flashing)
At least one charger is in the precharge, bulk
charge, or constant voltage stage.
Green (Solid)
Both Chargers have completed charging and
are in the Charge Termination (Float) stage.
Red (Solid)
At least one charger has experienced a fault.
Table 1 - Charger LED State Values
Note that the LED indication prioritizes Fault state above all else, followed by active charging. This
means that for example, if Charger 1 is finished charging, but Charger 2 is still charging its battery,
the LED will stay blinking green until both are finished.
If connected to the J1939 CAN network, the charger continuously transmits its internal state,
charging current and the battery voltage. It can also use the J1939 network to acquire the battery
temperature and to perform any user specific functions on demand. The battery charger also
supports J1939 regular node functions, including address claiming, PGN responses, etc.
The RS232 interface of the charger allows the user to change the battery type, program battery
charger setpoints, flash the new software, and watch an internal state of the charger using one of
the standard terminal emulation software (Tera Term, Hyperterminal, etc.).

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 7-37
2. BATTERY CHARGER THEORY OF OPERATION
The battery charger implements a three-stage charging algorithm with an additional charge stage
for maintenance.
Constant
voltage
Voltage
Time
Precharge
Stage
Bulk Charge Stage
Absorption
Stage
Float Stage
Current
Constant
current
Constant
current
Constant
voltage
Voltage, Current
Charging
Maintaining
Charge
Figure 1. Battery Charger Algorithm Profile
The charging process starts from the Precharge Stage, then, when the battery voltage reaches a
certain point, the charger switches to the Bulk Charge Stage, and the charging process is finalized
in the Absorption (Constant Voltage Charge) Stage.
After the battery is fully charged, the charger maintains the battery charge in Float Mode.
2.1. Battery Charger Modes
Each stage of the charging process corresponds to one or two battery charger modes. There are
also modes reflecting an idle or an error condition of the charger and a special power supply mode
used for testing.
The charger starts functioning from Idle Mode. It stays in Idle Mode until the Charger is enabled,
and a battery is connected to the charger.
Ich
Ibc
Vbc_start
Vbat
Vpc_start
Vbc_rst
Vfl_start
Vfl
Vcv_start
Vcv
Veq_stop
Ipc
Ieq
Icv_stop
Ifl_stop
Figure 2. Voltage-Current Charging Profile

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 8-37
When the charger recognizes the battery, it starts analyzing the battery state. If the battery is
deeply discharged and its voltage is between Vpc_start and Vbc_start (See section 2.2), the
charger will start the precharging process, charging the battery with a relatively small constant
current Ipc. The small current prevents a deeply discharged battery from damage, which otherwise
could occur due to gas emission from the battery electrolyte at high current. The charger will stay
in the Precharge Mode until the battery voltage reaches the Vbc_start voltage.
When the battery reaches Vbc_start voltage, the charger will enter the Bulk Charge Mode
increasing the charging current to Ibc. It will charge the battery with the Ibc current until the battery
voltage reaches Vcv_start. At this point the battery is around 75% charged and the charger can go
to the Constant Voltage Charge Mode limiting the charging voltage to Vcv. This will cause a
gradual drop of the charging current. When the charging current drops to Icv_stop, the battery is
considered fully charged, and the charger will stop the charging process and go to Standby Mode.
In Standby Mode the charger only monitors the battery voltage. It will maintain the battery charge
either by periodically recharging the battery when the battery voltage drops below Vbc_restart, or
by maintaining the charge in Float Mode, if the voltage drops below Vfl_start voltage.
In Float Mode the charger limits the charging voltage to Vfl and the charging current Ibc. When the
charging current drops below Ifl_stop, the charger returns to Standby Mode, keeping the battery
voltage at a predefined level.
The charger stages can be used as signal sources for transmitting over CAN. The corresponding
values to the stages are given in Table 2.
Value
Charger Mode
0
Idle Mode
1
Charge Termination (Float) Mode
2
Precharge Mode
3
Constant Current Mode
4
Constant Voltage Mode
5
Recharge Mode
Table 2 –Charger Mode Values
Charger Temperature
In addition to the charging profile parameters, each charger has a temperature sensor. The
charger will turn off its output and go to Idle state if the temperature threshold is exceeded. The
charger will remain in Idle state until the Temperature Hysteresis value is cleared.
In case of electronics failure, the charger will be locked in Module Error Mode until either the
battery or the power is disconnected, and the charger goes to the initial Idle Mode.
Battery Temperature
Battery temperature can be measured using the RTD inputs. By default, the firmware is configured
to use a PT1000 temperature sensor. The maximum battery temperature is configured through the

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 9-37
Miscellaneous Input setpoint “Shutdown Temperature”. If no RTD is connected, ensure the RTD
Enable setpoint is set to ‘Disabled’.
2.2. Battery Charger State Diagram
A complete set of the charger modes and their relations to each other are shown on the Battery
Charger State Diagram (Figure 3).
Figure 3. Battery Charger State Diagram
In order to avoid accidental switching of the charger from one mode to another due to noise,
transients, etc., the condition causing the transition must stay on for at least 3 seconds.
2.3. Battery Protection
To prevent a battery from damage, the battery charger has a time-out condition of 48 hours. The
charger will return to Idle state if the charge time exceeds this value.
By default, the battery charger will not start charging a battery with a voltage less than the
Precharge Mode Start Voltage. However, some batteries may contain a safety feature which
disconnects the output when not charging. In this case, the battery may hold a charge, but the
battery charger will read no voltage from the battery terminals. For this reason, the battery charger

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 10-37
contains an additional function, Precharge Mode Force Enable. When enabled, the charger will
bypass the battery voltage check, and attempt to charge the battery in Precharge mode.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 11-37
3. OVERVIEW OF J1939 FEATURES
The software was designed to provide flexibility to the user with respect to messages sent to and
from the ECU by providing:
•Configurable ECU Instance in the NAME (to allow multiple ECUs on the same network)
•Configurable Transmit PGN and SPN Parameters
3.1. Introduction to Supported Messages
The ECU is compliant with the standard SAE J1939, and supports the following PGNs
From J1939-21 - Data Link Layer
•Request 59904 ($00EA00)
•Acknowledgment 59392 ($00E800)
•Transport Protocol –Connection Management 60416 ($00EC00)
•Transport Protocol –Data Transfer Message 60160 ($00EB00)
Note: Any Proprietary B PGN in the range 65280 to 65535 ($00FF00 to $00FFFF) can be selected
From J1939-73 –Diagnostics
•DM1 –Active Diagnostic Trouble Codes 65226 ($00FECA)
•DM2 –Previously Active Diagnostic Trouble Codes 65227 ($00FECB)
•DM3 –Diagnostic Data Clear/Reset for Previously Active DTCs 65228 ($00FECC)
•DM11 –Diagnostic Data Clear/Reset for Active DTCs 65235 ($00FED3)
From J1939-81 - Network Management
•Address Claimed/Cannot Claim 60928 ($00EE00)
•Commanded Address 65240 ($00FED8)
6BFrom J1939-71 –Vehicle Application Layer
•Software Identification 65242 ($00FEDA)
None of the application layer PGNs are supported as part of the default configurations, but they
can be selected as desired for either transmit or received function blocks.
Setpoints are accessed using standard Memory Access Protocol (MAP) with proprietary
addresses. The Electronic Assistant (EA) allows for quick and easy configuration of the unit over
the CAN network.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 12-37
3.2. Name, Address and Software ID
J1939 Name
The battery charger ECU has the following defaults for the J1939 NAME. The user should refer to
the SAE J1939/81 standard for more information on these parameters and their ranges.
Arbitrary Address Capable
Yes
Industry Group
0, Global
Vehicle System Instance
0
Vehicle System
0, Non-specific system
Function
141, Axiomatic Battery Charger
Function Instance
8, Axiomatic AX090690, Battery
Charger
ECU Instance
0, First Instance
Manufacture Code
162, Axiomatic Technologies
Corporation
Identity Number
Variable, uniquely assigned during
factory programming for each ECU
The ECU Instance is a configurable setpoint associated with the NAME. Changing this value will
allow multiple ECUs of this type to be distinguishable by other ECUs (including the Electronic
Assistant) when they are all connected on the same network.
ECU Address
The default value of this setpoint is 128 (0x80), which is the preferred starting address for self-
configurable ECUs as set by the SAE in J1939 tables B3 to B7. The EA will allow the selection of
any address between 0 to 253, and it is the user's responsibility to select an address that
complies with the standard. The user must also be aware that since the unit is arbitrary address
capable, if another ECU with a higher priority NAME contends for the selected address, the battery
charger will continue select the next highest address until it finds one that it can claim. See
J1939/81 for more details about address claiming.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 13-37
Software Identifier
For the battery charger ECU, Byte 1 is set to 5, and the identification fields are as follows
(Part Number)*(Version)*(Date)*(Owner)*(Description)
PGN 65242 Software Identification - SOFT
Transmission Repetition Rate: On request
Data Length: Variable
Extended Data Page: 0
Data Page: 0
PDU Format: 254
PDU Specific: 218 PGN Supporting Information:
Default Priority: 6
Parameter Group Number: 65242 (0xFEDA)
Start Position Length Parameter Name SPN
1 1 Byte Number of software identification fields 965
2-n Variable Software identification(s), Delimiter (ASCII “*”) 234

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 14-37
EA shows all this information in “General ECU Information”, as shown below
Note: The information provided in the Software ID is available for any J1939 service tool which
supports the PGN -SOFT.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 15-37
4. BATTERY CHARGER FUNCTION BLOCKS
4.1. Charging Profile Function Blocks
The Charging Profile function blocks are used to set all parameters needed in the battery charging
algorithm. These parameters characterize the conditions which the charging algorithm will use to
switch between charging modes. The Chargers can be disabled, enabled, or set to be controlled
by CAN Rx messages.
Please refer to Section 2, where these parameters are described in detail.
4.2. Miscellaneous Input Function Block
The Miscellaneous Input function block is used to define parameters used in controlling the ECU.
The Undervoltage Threshold, Overvoltage Threshold and Shutdown Temperature, setpoints
are used to determine the values at which the ECU generates the corresponding fault.
The CAN1 Diagnostic Setting determines the behaviour over CAN1. Diagnostic messages can
be turned ON/OFF, as well as set to block empty diagnostic messages.
4.3. J1939 Network Function Block
The Network function block controls the way the battery charger communicates on the J1939
network. Further details on the J1939 network features are available in Section 5.
The Module Address (ECU Address in EA), setpoint specifies the dynamic network address of the
battery charger, which is claimed when the charger is connected to the network. This setpoint can
be changed automatically in case the address is already taken by a higher priority in the ECU.
The ECU Instance (ECU Instance Number in the EA), setpoint should be set by the user if two or
more battery chargers are present on the network.
4.4. Diagnostic Input Function Blocks
The Diagnostic Input function blocks are used to setup the diagnostic messages for the controller.
The 5 types of diagnostics supported by the battery charger are shown in Table 8.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 16-37
Function Block
Minimum Threshold
Maximum Threshold
Feedback Overcurrent
Fault
N/A
Charge Profile Regulation
Current Setting
VPS Undervoltage Fault
VPS Undervoltage
N/A
VPS Overvoltage Fault
N/A
VPS Overvoltage
Over Temperature Fault
N/A
Temperature Shutdown
Lost Communication
Fault
N/A
Received Message
Timeout (any)
Table 8 –Fault Detection Thresholds
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’s 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 battery charger 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 battery charger 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 battery charger 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

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 17-37
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 4. 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 9 –Low Fault FMI versus High Fault FMI
If the FMI used is anything other than one of those in Table 4, 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.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 18-37
4.5. CAN Transmit Function Block
The CAN Transmit function block is used to send datafrom the battery charger to the J1939 network.
Normally, to disable a transmit message, the Transmit Repetition Rate is set to zero. However,
should the message share its Parameter Group Number (PGN) with another message, this is not
necessarily true. In the case where multiple messages share the same Transmit PGN, the repetition
rate selected in the message with the LOWEST number will be used for ALL the messages that use
that PGN.
By default, all messages are sent on Proprietary B PGNs as broadcast messages. If all the data is
not necessary, disable the entire message by setting the lowest channel using that PGN to zero. If
some of the data is not necessary, simply change the PGN of the superfluous channel(s) to an
unused value in the Proprietary B range.
Since the defaults are PropB messages, the Transmit Message Priority is always initialized to 6
(low priority) and the Destination Address (for PDU1) setpoint is not used. This setpoint is only
valid when a PDU1 PGN has been select, and it can be set either to the Global Address (0xFF) for
broadcasts or sent to a specific address as setup by the user.
Enabling the Override Source Address, allows the Source Address of the J1939 Identifier to be
changed to any value between 0…255.
The Transmit Data Size,Transmit Data Index in Array (LSB),Transmit Bit Index in Byte
(LSB),Transmit Resolution and Transmit Offset can all be used to map the data to any SPN
supported message by the J1939 standard from any Data Source of the Transmit function block.
Table 5 exhibits the possible Data Sources for use in CAN Transmits.
Value
Control Source
0
No Control Source
1
CAN Receive
2
Constant Discrete Signal
3
Constant Continuous Signal
4
Power Supply Voltage
5
Charger Feedback Voltage
6
Charger Feedback Current
7
Charger Configuration
8
Charger Mode (See Table 2)
9
Charger Temperature
10
Charger Error Signal
Table 3 –CAN Transmit Data Sources
The battery charger supports up to 5 unique CAN Transmit Messages, all of which can be
programmed to send any available data to the CAN network. Each CAN Transmit Message is setup
to send data from 4 configurable sources, and if each of the 4 sources is used, each source can
have a size as large as 2-Bytes. Only the first 2 CAN Transmit Messages are configured by default,
with the remaining 3 set to unused; the default list is shown in Table 4 below.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 19-37
CAN Transmit 1
Default Transmit Data
Byte
Position
Bit
Position
PGN
1
Charger 1 Mode
1st
1st
0xFF00
2
Charger 1 Voltage
2nd
3rd
0xFF00
3
Charger 1 Current
3rd
5th
0xFF00
4
Charger 1 Temperature
4th
7th
0xFF00
CAN Transmit 2
Default Transmit Data
Byte
Position
Bit
Position
PGN
1
Charger 2 Mode
1st
1st
0xFF01
2
Charger 2 Voltage
2nd
3rd
0xFF01
3
Charger 2 Current
3rd
5th
0xFF01
4
Charger 2 Temperature
4th
7th
0xFF01
Table 4 –Default CAN Transmit Messages
4.6. CAN Receive Function Block
The CAN Receive function block is designed to take any SPN from the J1939 network and use it
as a control/enable/override source for any relay outputs or CAN Transmits.
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 enabled.
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. This will trigger a Lost Communication
event if the cell input associated with the CAN Receive message is set to User Controlled under Rx
Timeout Setting. In order to avoid timeouts 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 fault.
By default, all control messages are expected to be sent to the battery charger on Proprietary B
PGNs. However, should a PDU1 message be selected, the battery charger can be setup to receive
it from any ECY 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 Receive Data Size, Receive Data Index in Array (LSB), Receive Bit Index in Byte (LSB),
Receive Resolution and Receive Offset can all be used to map any SPN supported by the J1939
standard to the output data of the Received function block.
As mentioned earlier, a CAN receive function block can be selected as the source of the control
input for the charger function blocks. When this is the case the Receive Data Minimum (Off
Threshold) and Receive Data Maximum (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 output types. These values are in whatever units the data is AFTER the
resolution and offset is applied to the CAN Receive signal.

UMAX090690. Version: 1.2 Preliminary Documentation –May Be Subject To Change 20-37