AXIOMATIC UMAX141100 User manual
USER MANUAL UMAX141100
CAN to Bluetooth
BRIDGE AND DATALOGGER
WITH CAN
USER MANUAL
P/N: AX141100
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change ii
VERSION HISTORY
V
ersion Date
A
uthor Modification
1.0.0. Nov 18, 2016
A
ntti Keränen Initial Version
-- Nov. 18, 2016
A
manda Wilkins Marketin
g
Review
1.0.1. Mar. 5, 2017 Antti Keränen CAN Rx filtering description updated,
CAN Scope function and BT MAP Tool
description added.
1.0.2. Mar. 20, 2017 Antti Keränen New functionality added (firmware
v1.01). SPP command reference
updated.
-- March 20, 2017 Amanda Wilkins Updated connection and operating
ran
g
e in Technical Spec.
1.0.3. June 12, 2017 Antti Keränen Bluetooth node ID configuration added.
BT module communication failure
detection added
(
in section 1
)
.
1.0.4. June 15, 2017 Antti Keränen CAN RX Filtering description
enhanced.
1.0.5. Februar
y
16, 2018
A
ntti Keränen
A
ndroid apps’ links updated.
1.0.6. Februar
y
26, 2018
A
ntti Keränen Default PIN codes note added.
DEFAULT PIN CODES
Pairing: 000000
Configuration mode: 000000
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change iii
ACRONYMS
ACK Positive Acknowledgement (from SAE J1939 standard)
BATT +/- Battery positive (a.k.a. Vps) or Battery Negative (a.k.a. GND)
BD ADDR Bluetooth Device Address
BLE Bluetooth Low Energy
BT Bluetooth
EA Electronic Assistant®, p/n AX070502 (A Service Tool for Axiomatic ECUs)
ECU Electronic Control Unit (from SAE J1939 standard)
GND Ground reference (a.k.a. BATT-)
MAP Memory Access Protocol
PGN Parameter Group Number (from SAE J1939 standard)
SPN Suspect Parameter Number (from SAE J1939 standard)
TP Transport Protocol
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change iv
LISTOFCONTENTS
1.
OVERVIEW OF THE CONTROLLER....................................................................................................................... 8
2.
CAN TO BLUETOOTH FUNCTION BLOCKS ....................................................................................................... 10
2.1.
PIN codes........................................................................................................................................................ 10
2.2.
CAN Bus Configuration.................................................................................................................................... 11
2.3.
Connection Options......................................................................................................................................... 12
2.4.
CAN Receive Filtering ..................................................................................................................................... 13
2.5.
CAN Data Logging........................................................................................................................................... 14
2.6.
Flash Memory Operations ............................................................................................................................... 15
2.7.
Real Time Clock Settings ................................................................................................................................ 16
2.8.
Miscellaneous Settings.................................................................................................................................... 17
2.9.
CAN Scope...................................................................................................................................................... 18
2.10.
LED Configuration ....................................................................................................................................... 19
3.
INSTALLATION INSTRUCTIONS.......................................................................................................................... 20
3.1.
Dimensions and Pinout.................................................................................................................................... 20
4.
OVERVIEW OF J1939 FEATURES........................................................................................................................ 21
4.1.
Introduction to Supported Messages............................................................................................................... 21
4.2.
NAME, Address and Software ID.................................................................................................................... 21
5.
SPP COMMUNICATIONS....................................................................................................................................... 23
5.1.
Overall message format................................................................................................................................... 23
5.2.
Message types................................................................................................................................................. 23
5.2.1.
CAN messages............................................................................................................................................ 24
5.2.2.
MAP access................................................................................................................................................. 24
5.2.3.
Configuration messages.............................................................................................................................. 24
5.2.4.
Download flash contents ............................................................................................................................. 26
5.2.5.
LED commands........................................................................................................................................... 26
6.
ECU SETPOINTS ACCESSED WITH ELECTRONIC ASSISTANT ...................................................................... 27
7.
ACCESSING REMOTE AXIOMATIC ECUS WITH BT MAP TOOL ...................................................................... 28
8.
REFLASHING OVER CAN WITH EA BOOTLOADER.......................................................................................... 29
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change v
LISTOFTABLES
Table 1 – CAN Rx filter definition .................................................................................................................................... 13
Table 2 – Flash chip details............................................................................................................................................. 15
Table 3 – AX141100 Connector Pinout........................................................................................................................... 20
Table 4 – Overall message format .................................................................................................................................. 23
Table 5 – Proprietary SPP message types ..................................................................................................................... 23
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change vi
LISTOFFIGURES
Figure 1 – AX141100 Block Diagram................................................................................................................................ 8
Figure 2 – PIN Code settings .......................................................................................................................................... 10
Figure 3 – CAN bus configuration ................................................................................................................................... 11
Figure 4 – Connection options......................................................................................................................................... 12
Figure 5 – CAN Receive Filtering.................................................................................................................................... 13
Figure 6 – CAN Logging Configuration ........................................................................................................................... 14
Figure 7 – Flash memory operations............................................................................................................................... 15
Figure 8 – Real Time Clock............................................................................................................................................. 16
Figure 9 – Miscellaneous settings................................................................................................................................... 17
Figure 10 – CAN Scope................................................................................................................................................... 18
Figure 11 – LED Configuration........................................................................................................................................ 19
Figure 12 – AX141100 Dimensional Drawing ................................................................................................................. 20
Figure 13 – BT MAP Tool................................................................................................................................................ 28
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change vii
REFERENCES
J1939 Recommended Practice for a Serial Control and Communications Vehicle
Network, SAE, April 2011
J1939/21 Data Link Layer, SAE, December 2010
J1939/71 Vehicle Application Layer, SAE, March 2011
J1939/73 Application Layer-Diagnostics, SAE, February 2010
J1939/81 Network Management, SAE, May 2003
TDAX141100 Technical Datasheet, CAN to Bluetooth bridge and datalogger with CAN,
Axiomatic Technologies 2016
UMAX07050x User Manual V5.13.84, Electronic Assistant and USB-CAN, Axiomatic
Technologies, October 2016
This document assumes the reader is familiar with the SAE J1939 standard. Terminology
from the standard is used, but not described in this document.
NOTE: This product is supported by Electronic Assistant
®
V5.13.84.0 and higher.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 8 - 36
1.
OverviewofTheController
Figure 1 – AX141100 Block Diagram
The CAN to Bluetooth device (later CAN2BT) can be used for accessing the CAN bus and the other
CAN nodes connected to it using Bluetooth communications and a smart device, such as a phone
or a tablet.
The CAN2BT device provides also data logging capabilities. It has 4GBits of internal Flash storage
for storing the selected CAN messages with time stamp information.
The CAN2BT device can be configured using an Android application called CAN2BT Configuration.
With this tool, all the functionality of the CAN2BT device can be configured, such as setting PIN
codes, connection options, CAN receive filtering and CAN data logging rules. Also RTC time setting
and different Flash memory operations such as download data and data erase are supported.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 9 - 36
The CAN2BT device can be operated in two main operation modes, namely the Interface Mode and
the Bridge Mode. The Interface Mode is targeted for data logging operation and in this mode the
CAN2BT device can be accessed using Electronic Assistant.
When in Bridge Mode, the CAN receive filtering is disabled and the device accepts all incoming CAN
frames. The main purpose of the Bridge Mode is to use two CAN2BT devices as a wireless CAN
data bridge between two different CAN networks. When in Bridge Mode, the CAN2BT device is
transparent to the CAN bus and cannot be seen in Electronic Assistant’s list of J1939 nodes. The
device can be still accessed using the CAN2BT Configuration tool.
In case the module startup fails (a communication error between the CPU and the Bluetooth module
is detected), the CAN2BT device will indicate the failure by sending the following DM1 (PGN 0xFECA
/ 65226) to CAN bus on 1s intervals. In addition to the DM1, the two built-in LEDs are blinking and
not responding to user configuration nor control messages. In failure mode, the unit will be accessible
only via the CAN bus.
ConditionLampSPNFMIOCSrc.Address
BTmodulefailureMALFUNCTION3368(WCM1)3110xFB(251)
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 10 - 36
2.
CANtoBluetoothFunctionBlocks
This section explains the different functions and configuration available on the CAN2BT. The
CAN2BT Configuration Android application is used as a reference. The application is available from
Google Play.
2.1.
PINcodes
Figure 2 – PIN Code settings
The PIN Code settings allow the user to define PIN codes that are used when accessing the device.
Pairing PIN is the PIN code that will be used when pairing the CAN2BT device with a new smart
device. Configuration PIN code is required when configuration is accessed (most configuration
options require that the CAN2BT device is put to configuration mode. Entering the configuration
mode requires the user to enter the configuration PIN). Remote Connection PIN is the code that is
used when the CAN2BT makes a connection with another CAN2BT device (when forming a data
brigde for wireless CAN communications).
DEFAULT PIN CODES
Pairing: 000000
Configuration mode: 000000
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 11 - 36
2.2.
CANBusConfiguration
Figure 3 – CAN bus configuration
CAN bus configuration allows changing the CAN interface baudrate. The list of available baudrate
options include 50k, 100k, 125k, 250k (default), 500k and 1M. When changing the baudrate, the
CAN2BT device needs to be restarted (power cycled) to apply the new baudrate to the CAN
interface.
The Echo TX CAN Frames makes the CAN2BT device to send back all CAN messages that are
sent to its Bluetooth interface using commands 0x12 and 0x13. Please see section 5.2 for more info
about CAN message sending.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 12 - 36
2.3.
ConnectionOptions
Figure 4 – Connection options
Connection options menu list the functions available for connecting the CAN2BT device to other
CAN2BT node. Scan starts a scan for other Bluetooth nodes (CAN2BT works as a master). Connect
to node makes a connection to one of the nodes returned in the Scan results. Disconnect from
node disconnects the currently active connection. Set autoconnect can be used for setting a BD
ADDRESS of a remote node with which the CAN2BT device will attempt to connect automatically at
power on (targeted for data bridge operations). Disable autoconnect will reset the BD ADDRESS
set using command Set autoconnect.
Define accepted BD ADDR lets the user to configure a Bluetooth address that will be the only
address from which connections are allowed. All other nodes trying to connect to the CAN2BT device
will be ignored.
All functions that are used for defining BD ADDRESSes expect to receive an index number that
matches to the BD ADDR list returned upon successful device scan (using the Scan command). The
list of valid numbers is from 1 to number of Bluetooth nodes found. Index 0 is also accepted, it is
interpreted as the BD ADDR of the device that is currenty used for configuring the device. This is
useful in cases where the accepted BD ADDR needs to be set.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 13 - 36
2.4.
CANReceiveFiltering
Figure 5 – CAN Receive Filtering
By default the device won’t read in all received CAN messages. With the CAN receive filtering
functions, the user can change this behaviour. Disable CAN fitering removes all CAN receive
filtering and makes the CAN2BT device capable of receiving all CAN frames on the bus. With CAN
filtering disabled, the CAN2BT device is invisible to the CAN bus. This is the mode that is preferred
for using the device as a bridge between two CAN buses.
Enable CAN filtering restores the default CAN receive filtering and makes the CAN2BT device
visible to the CAN bus (it will respond to Address Claim messages).
Add CAN RX filter lets the user to define a single CAN filter and optional mask that are added to
the low level (HW) CAN receive filter registers. Please note, that if the mask is not specified, the
firmware uses a default mask of 29 (or 11) bits wide that will compare all bits in the received CAN
frame against the specified filter.
Up to 28 filter definitions will be accepted. The Remove CAN RX filter will remove the specified filter
(the removal is done by comparing the IDs of the configured filters and the ID specified to be
removed).
The CAN filter definition for adding and removing filters is as follows:
bit 31 bit 30 bits 29-0
Use ExtID Use RTR Filter ID
Table 1 – CAN Rx filter definition
Example29bitIDfilter&maskforreceivingall(J1939)frameswithSourceAddress0xF9
Filter: 800000F9, Mask: FF
Example11bitIDfilter&maskforreceivingID0x701(CANopenmasterHB)
Filter: 701, Mask: 7FF
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 14 - 36
2.5.
CANDataLogging
Figure 6 – CAN Logging Configuration
The Datalogging configuration includes defining different PGNs or Source Addresses to log. These
two functions assume PGNs and Source Addresses as defined in the J1939 specification. The
Define ID to log allows the user to freely define a CAN frame ID that will be logged.
Please note, that the CAN Logging configuration does not change the CAN receive filtering. In most
cases (unless the device has CAN receive filtering disabled), the user has to define proper CAN
receive filters in order the CAN2BT to be able to receive all CAN frames that need to be logged.
The current data logging rules can be read using the List all logging rules function. The Erase all
logging rules will erase all rules.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 15 - 36
2.6.
FlashMemoryOperations
Figure 7 – Flash memory operations
Contents of the Flash memory can be downloaded to an Android smart device using the Download
flash contents. This function will transfer 96 bytes of the Flash contents at a time, please refer to
section 5 for details.
The Flash can be erased few blocks at a time or then a full erase can be done using Erase all flash
blocks. The Flash erase functions will require that the device is in configuration mode, so the Flash
contents are protected with the Configuration PIN.
The current flash address (block and page) can be set using the Flash address function. All the
following Flash writes will use this setting.
Erasing a single block can be done by setting the erase start block and end block to a same value
(please note that the flash erase is flash block specific). To download a single flash page, the start
address (block & page) and end address (block & page) need to be set to a same value.
Flash t
y
pe Micron MT29F4G08ABAD
A
(
4GBits
)
B
y
tes per pa
g
e 2112
Pa
g
es per block 64
Blocks in total 4096
Table 2 – Flash chip details
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 16 - 36
2.7.
RealTimeClockSettings
Figure 8 – Real Time Clock
There is an RTC on the CAN2BT device. The RTC is powered from a supercap, capable of keeping
the time and data information for 96 hours of stand-by if fully charged before the stand-by period.
The fully charging means that the CAN2BT device is being powered at least 8 hours continously.
The time can be set using the Set time and read using the Get time function. Setting the time
requires that the CAN2BT device is in configuration mode.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 17 - 36
2.8.
MiscellaneousSettings
Figure 9 – Miscellaneous settings
The miscellaneous settings consist of setting the CAN2BT device to the configuration mode, and
exiting the configuration mode. The CAN2BT device can be also SW reset and the CAN bootloader
can be started for firmware updates (please also see section 8).
The Enter Configuration mode requires the user to enter the current Configuration PIN number. In
case the smart device is disconnected from the CAN2BT device during configuration, the CAN2BT
device automatically exits the confitguration mode.
SW Reset will reset the CPU of the CAN2BT device. Start bootloader will set the start bootloader
flag and then reset the CPU. This makes the CAN2BT device enter the firmware reflash mode, and
it will be visible on the CAN bus and accessible from EA as Bootloader #1 (please see section 8 for
more detailed description of firmware reflashing). Default settings will restore factory default
settings and then reset the CPU.
Bluetooth ID allows the user to configure the name that device will advertise. The default is
“CAN2BT”. In case there are multiple CAN2BT devices in range, it might be advantageous to
configure unique names to different controllers. The Bluetooth ID accepts charaters in range 0x20
(‘space’) to 0x7E (‘~’) and can hold up to 248 characters.
The configured Bluetooth ID is also available in the J1939 Software ID (SPN 234).
In case the CAN2BT device is not in configuration mode and the user tries to configure it, the
configuration commands return non-zero values.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 18 - 36
2.9.
CANScope
Figure 10 – CAN Scope
The CAN Scope function shows the frames on the CAN bus. Only the frames that pass the receive
filters (please see section 2.4) are shown. The CAN Scope function can be also used for manually
sending CAN frames to tbe bus.
The data for the frame to be sent is given in hexadecimal format. The data bytes for the CAN frame
need to be given in sequence of bytes. The separator between the bytes can be one of the following
characters:
: ; - , .
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 19 - 36
2.10.
LEDConfiguration
Figure 11 – LED Configuration
The build in LEDs of the CAN2BT device can be also manually controlled. The LED Mode function
allows the user to set the LED function, default – LED activity based on BT RX and TX and manual
– LED states as commanded using the LED commands. Please see section 5.2 for more detailed
info about the available LED commands.
UMAX141100 Version 1.0.6. Preliminary Documentation – May be subject to change 20 - 36
3.
InstallationInstructions
3.1.
DimensionsandPinout
Figure 12 – AX141100 Dimensional Drawing
PIN # FUNCTION
1 CAN_L
2 CAN_H
3 CAN _SHIELD
4 NOT USED
5 NOT USED
6 NOT USED
7 BATT +
8 BATT -
Table 3 – AX141100 Connector Pinout
This manual suits for next models
1
Table of contents
