AXIOMATIC UMAX142100A Protocol Converter
Product Specifications
- Model: UMAX142100A
- Version: 2.0.3
- Features: RS232-RS232-RS422 Router with Ethernet and CAN
- Default Password: AX142100A
Overview of Controller
The RS232-RS232-RS422 Router with Ethernet and CAN (3RS-ENET-CAN) forwards serial port messages between the three serial ports, CAN, and Ethernet based on a custom routing configuration. Configuration is done using a web browser and the built-in web server on the device.
| Pin # | Function |
|---|---|
| 1 | RS-422 RX+ |
Ethernet Connector / RS422
| Pin # | Function |
|---|---|
| 1 | Power + |
Frequently Asked Questions
Q: How do I reset the device to factory settings?
A: To reset the device to factory settings, press and hold the reset button for 10 seconds.
Q: Can I update the firmware of the device?
A: Yes, you can update the firmware using the Axiomatic Electronic Assistant software. Please refer to the user manual for detailed instructions on firmware updates.
Modification Initial Draft Descriptions added for Receive Message Configuration and Transmit Message Configuration. Configuration web pages’ screenshots updated. Marketing review Updated power protections and quiescent current as per validation results Updated dimensional drawing & storage temperature Added a note about RS Port #3 Added vibration and shock testing
Positive Acknowledgement (from SAE J1939 standard) Battery positive (a.k.a. Vps) or Battery Negative (a.k.a. GND) Diagnostic Message (from SAE J1939 standard) Diagnostic Trouble Code (from SAE J1939 standard) Axiomatic Electronic Assistant (A Service Tool for Axiomatic ECUs) Electronic Control Unit (from SAE J1939 standard) Ground reference (a.k.a. BATT-)
Inputs and Outputs Internet Protocol Media Access Control Memory Access Protocol Negative Acknowledgement (from SAE J1939 standard) A format for messages that are to be sent to a destination address, either specific or global (from SAE J1939 standard) A format used to send information that has been labeled using the Group Extension technique and does not contain a destination address. Parameter Group Number (from SAE J1939 standard) Message that uses the Proprietary A PGN for peer-to-peer communication Message that uses a Proprietary B PGN for broadcast communication Suspect Parameter Number (from SAE J1939 standard) Transmission Control Protocol / Internet Protocol Transport Protocol Voltage Power Supply (a.k.a. BATT+)
J1939/81
Network Management, SAE, May 2003
TDAX142100A
Technical Datasheet, RS232-RS232-RS422-ENET-CAN Converter, Axiomatic Technologies
UMAX07050x
User Manual, Axiomatic Electronic Assistant and USB-CAN, Axiomatic Technologies
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 Axiomatic Electronic Assistant V5.15.129.0 and higher
UMAX142100A
vii
1. OVERVIEW OF CONTROLLER
Figure 1 Block diagram of the RS232-RS232-RS422 Router with Ethernet and CAN
The RS232-RS232-RS422 Router with Ethernet and CAN (later 3RS-ENET-CAN) is a device that forwards serial port messages between the three serial ports, CAN and Ethernet based on a custom routing configuration. The configuration can be done using a web browser and the built-in web server running on the 3RS-ENET-CAN device.
The Axiomatic Electronic Assistant can be used to configure the network parameters of the 3RSENET-CAN converter. The configuration of all parameters can be done via the web browser interface (port 80).
UMAX142100A
8 – 42
2. INSTALLATION INSTRUCTIONS 2.1. Dimensions and Pinout
Figure 2 Controller Dimensions and Label
CAN Connector / 2x RS232
Pin # Function
1
RS-422 RX+
2
RS-422 TX+
3
RS-422 RX-
4
RS-232 TX 2
5
RS-232 RX 2
6
CAN_L
7
CAN_H
8
RS-232 TX 1
9
RS-232 RX 1
10 RS-422 TX-
11 Ground
12 Ground
Ethernet Connector / RS422
Pin # Function
1
Power +
2
Power –
3
Power –
4
Ethernet TX –
5
Ethernet RX +
6
Ethernet TX +
7
Power +
8
Ethernet RX –
Table 1 AX142100A Connector Pinout
UMAX142100A
9 – 42
3. OVERVIEW OF J1939 FEATURES
The software was designed to provide flexibility to the user with respect to messages sent from the ECU by providing:
· Configurable ECU Instance in the NAME (to allow multiple ECUs on the same network) · Configurable PGN and Data Parameters · Configurable Diagnostic Messaging Parameters, as required
3.1. Introduction to Supported Messages
The ECU is compliant with the standard SAE J1939 and supports following PGNs from the standard.
From J1939-21 Data Link Layer · Request
· Acknowledgement
· Transport Protocol Connection Management · Transport Protocol Data Transfer Message · Proprietary B
from to
59904 59392 60416 60160 65280 65535
0x00EA00 0x00E800 0x00EC00 0x00EB00 0x00FF00 0x00FFFF
From J1939-73 Diagnostics · DM1 Active Diagnostic Trouble Codes
· DM2 Previously Active Diagnostic Trouble Codes
· DM3 Diagnostic Data Clear/Reset for Previously Active DTCs
· DM11 Diagnostic Data Clear/Reset for Active DTCs
65226 65227 65228 65235
0x00FECA 0x00FECB 0x00FECC 0x00FED3
From J1939-81 Network Management · Address Claimed/Cannot Claim
· Commanded Address
60928 0x00EE00 65240 0x00FED8
From J1939-71 Vehicle Application Layer · ECU Identification Information
· Software Identification
· Component Identification
64965 0x00FDC5 65242 0x00FEDA 65259 0x00FEEB
None of the application layer PGNs are supported as part of the default configurations, but they can be selected as desired for transmit function blocks.
Setpoints are accessed using standard Memory Access Protocol (MAP) with proprietary addresses. The Axiomatic Electronic Assistant (EA) allows for quick and easy configuration of the unit over CAN network.
UMAX142100A
10 – 42
3.2. NAME, Address and Identification Information
The 3RS-ENET-CAN ECU has the following default 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 Industry Group Vehicle System Instance Vehicle System Function Function Instance ECU Instance Manufacture Code Identity Number
Yes
0, Global 0
0, Non-specific system 25, Axiomatic Protocol Converter 21, Axiomatic AX142100A 0, First Instance 162, Axiomatic Technologies 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 from one another when they are connected on the same network.
The default value of the “ECU Address” setpoint is 128 (0x80), which is the preferred starting address for self-configurable ECUs as set by the SAE in J1939 tables B3 and B7. The EA will allow the selection of any address between 0 and 253. 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 10 Analog input will continue select the next highest address until it finds one that it can claim. See J1939/81 for more details about address claiming.
UMAX142100A
11 – 42
ECU Identification Information
PGN 64965
ECU Identification Information
Transmission Repetition Rate:
On request
Data Length: Extended Data Page: Data Page: PDU Format: PDU Specific: Default Priority: Parameter Group Number:
Variable 0 0 253 197 PGN Supporting Information: 6 64965 (0x00FDC5)
Start Position a b c d e
(a)*(b)*(c)*(d)*(e)*
Length Variable Variable Variable Variable Variable
Parameter Name
ECU Part Number, Delimiter (ASCII “*”) ECU Serial Number, Delimiter (ASCII “*”) ECU Location, Delimiter (ASCII “*”) ECU Type, Delimiter (ASCII “*”) ECU Manufacturer Name, Delimiter (ASCII “*”)
-ECUID
SPN 2901 2902 2903 2904 4304
Software Identifier
PGN 65242
Software Identification
Transmission Repetition Rate:
On request
Data Length: Extended Data Page: Data Page: PDU Format: PDU Specific: Default Priority: Parameter Group Number:
Variable 0 0 254 218 PGN Supporting Information: 6 65242 (0x00FEDA)
Start Position
Length
Parameter Name
1
1 Byte
Number of software identification fields
2-n
Variable
Software identification(s), Delimiter (ASCII “*”)
Byte 1 is set to 5, and the identification fields are as follows.
(Part Number)*(Version)*(Date)*(Owner)*(Description)
-SOFT
SPN 965 234
The EA shows all this information in its “General ECU Information” page.
Note: The information provided in the Software ID is available for any J1939 service tool which supports the PGN -SOFT
UMAX142100A
12 – 42
Component Identification
PGN 65259
Transmission Repetition Rate:
Data Length: Extended Data Page: Data Page: PDU Format: PDU Specific: Default Priority: Parameter Group Number:
Start Position a b c d
(a)*(b)*(c)*(d)*(e)*
Length 1-5 Byte Variable Variable Variable
Component Identification
On request
Variable 0 0 254 235 PGN Supporting Information: 6 65259 (0x00FEEB)
Parameter Name Make, Delimiter (ASCII “*”) Model, Delimiter (ASCII “*”) Serial Number, Delimiter (ASCII “*”) Unit Number (Power Unit), Delimiter (ASCII “*”)
-CI
SPN 586 587 588 233
UMAX142100A
13 – 42
4. WEB BROWSER BASED CONTROLLER CONFIGURATION
The 3RS-ENET-CAN controller supports configuration of the data routing parameters from Ethernet port using a standard web browser.
The default password: `AX142100A’
4.1. Parameter Editing The 3RS-ENET-CAN has a web server running on TCP port 80. The web server asks for a password before the configuration pages can be accessed. The default password is `AX142100A’ (this is case sensitive).
When the correct password is entered, the configuration page is opened. The settings can be applied by clicking the button at the top of the page. In case the user doesn’t want to change settings, the connection can be closed.
UMAX142100A
14 – 42
<configured ip> <configured ip>/index.shtml
The Home page gives an overview of the main settings and device status information. This page contains no editable settings.
UMAX142100A
15 – 42
<configured ip>/main_settings.shtml
The Main Settings page allows the user to modify the device’s IP address, netmask and the main configuration parameters for the communication interfaces. The CAN configuration parameters include the default baud rate to use and the auto-baud rate capability.
The serial port configuration contains, baud rate (freely settable, allowed range: 1200bps … 256kbps), number of data, start and stop bits and parity.
UMAX142100A
16 – 42
The serial port configuration also supports custom message delimiter character. By default, only the detected idle condition on the serial interface is considered as a message delimiter. By configuring a customer message delimiter character, messages can be picked up from a continuous serial data stream. In the settings (see also Table 1 AX142100A Connector Pinout) RS Port 1 == RS232, pins 8 & 9 of the CAN / RS232 / RS422 Connector RS Port 2 == RS232, pins 4 & 5 of the CAN / RS232 / RS422 Connector RS Port 3 == RS422, pins 1, 2, 3 & 10 of the CAN / RS232 / RS422 Connector
To achieve reliable data routing performance when RS Port 3 (RS422 / Pins 1, 2, 3 and 10) is not being used, it should be left out from all Data Routing Settings, or the pins should be properly terminated.
UMAX142100A
17 – 42
<configured ip>/serial_data_routing.shtml
The data routing configuration is done for each interface separately. The routing is done for all frames received from the three serial ports. Each serial interface supports 3 routing rules.
Each of the rules have a list of output interfaces, match bytes and mask bytes (software filter), add start and end bytes and CAN options, such as add a custom CAN frame ID, use Ext/Std ID and whether to use TP or not. For data forwarded to CAN interface, it is also possible to use CAN message byte 0 as an index.
The Output interfaces should be entered as comma separated list with no spaces. Match and Mask Bytes define a software filter for selecting the frames that will be routed to the configured output interfaces.
Start bytes (hex) and Number of start bytes to add define the bytes that should be added to the beginning of the forwarded frame.
End bytes (hex) and Number of end bytes to add define the bytes that should be added to the end of the forwarded frame.
In case the CAN Interface (interface #4) is among the Output interfaces, the forwarded frames that end up to CAN bus can be configured to have a specific CAN frame ID. In case a CAN frame ID is not defined, the first 29/11 bits (depending on the CAN ID type) will be used as the CAN frame ID.
UMAX142100A
18 – 42
In case Use TP is selected, the forwarded frame will be wrapped to TP frames in case the length exceeds 8 bytes. In case TP is not used, the frame will be sent as multiple single CAN frames. The option to add frame index to byte 0 has an effect only if TP is not used.
The Match and Mask Bytes are applied like this on the received serial port data. In case comparison is true, the data is forwarded:
“RX data & mask” == match
The Match bytes (hex), Mask bytes (hex), Number of start bytes to add, Start bytes (hex), Number of end bytes to add and End bytes (hex) are applied to the received serial data.
Add a custom CAN Frame ID, Use this Frame ID (hex), CAN Frame ID length, Use TP and Add frame index to byte 0 are applied to data that is forwarded to the CAN interface (#4).
Forward all data bytes / Number of bytes to forward are applied to all forwarded data.
Please note, that the TP messaging is used only when 29bit CAN frame ID is specified. In case TP is in use, the PGN wrapped inside the TP frame is specified using the Use this Frame ID (hex) option.
The Add frame index to byte 0 option can be used with 11bit frame IDs. This implements “TP like” CAN output.
UMAX142100A
19 – 42
<configured ip>/can_data_routing.shtml
CAN interface supports 16 data routing rules. Each one of the rules has a list of Output interfaces, Filter ID (hex) and Filter Mask (hex) (software filter) and Data replacing options. The data replacing is supported for the CAN Frame ID bits. Also, the number of data bytes to forward can be specified.
The output interfaces should be entered as comma separated list with no spaces. Filter ID and Mask are identical to the hardware filter configuration, these two settings are used in a software filter for selecting the frames that will be routed to the configured output interfaces.
The Replace Filter ID (hex) and Replace Filter Mask (hex) can be used for example to modify the Source Address, PGN and/or Priority bits of the J1939 frame. The data replacing function is applied for all frames that pass the software filter and will be done before routing the frame to the configured output interfaces.
To forward all data from frames with a PGN 0xFF01 to interfaces 2 & 3 and modify the forwarded PGN to 0xFF82, the following setup would need to be used:
Output Interfaces: 2,3 Filter ID (hex): 0xFF0100 Filter Mask (hex): 0xFFFF00 Rule State: `Enabled, use filter&mask’ selected Frame ID Type: `Extended (29bit)’ selected RTR: `don’t care’ selected Replace Filter ID (hex): 0xFF8200 Replace Filter Mask (hex): 0xFFFF00 `Data replacing’: `Use replace filter&mask’ selected `Data forwarding’: `Forward full message’ selected
UMAX142100A
20 – 42
<configured ip>/can_rx_filtering.shtml
The receive filter is used for selecting which CAN frames will be received. All received CAN frames that pass the reception filter will be forwarded to the data routing module. The configured CAN ID filter will be assigned to the CAN interface’s acceptance filter registers. No additional software filtering will be done in the message reception. However, the data routing module supports software filtering for selecting the frames that will be routed. In case all CAN receive filters are disabled, only selected J1939 CAN frames will be accepted. The accepted messages are the ones sent to Global Address (0xFF) and messages sent to 3RS-ENETCAN’s address, (default 0x80). Successful reception of all other CAN frames requires a custom CAN receive filter to be defined. The Filter ID (hex) defines the 29-bit extended or 11-bit standard frame ID. The Filter Mask bit `1′ forces the compare, `0′ marks the bit as `don’t care’. To configure a filter for receiving all possible frames, the ID and Mask should be set to `0′ and Filter State should be set to Enabled for both ID types.
UMAX142100A
21 – 42
<configured ip>/eth_data_routing.shtml
The routing rules are applied to all Ethernet frames that are sent to the configured (local) TCP/UDP port. Ethernet interface supports 3 routing rules.
Each of the rules have a list of output interfaces, match bytes and mask bytes (software filter), add start and end bytes and CAN options, such as add a custom CAN frame ID, use Ext/Std ID and whether to use TP or not. For data forwarded to CAN interface, it is also possible to use CAN message byte 0 as an index.
The Output interfaces should be entered as comma separated list with no spaces. Match and Mask Bytes define a software filter for selecting the frames that will be routed to the configured output interfaces.
Start bytes (hex) and Number of start bytes to add define the bytes that should be added to the beginning of the forwarded frame.
End bytes (hex) and Number of end bytes to add define the bytes that should be added to the end of the forwarded frame.
In case the CAN Interface (interface #4) is among the Output interfaces, the forwarded frames that end up to CAN bus can be configured to have a specific CAN frame ID. In case a CAN frame ID is not defined, the first 29/11 bits (depending on the CAN ID type) will be used as the CAN frame ID.
In case Use TP is selected, the forwarded frame will be wrapped to TP frames in case the length exceeds 8 bytes. In case TP is not used, the frame will be sent as multiple single CAN frames. The option to add frame index to byte 0 has an effect only if TP is not used.
UMAX142100A
22 – 42
The Match and Mask Bytes are applied like this on the received Ethernet frame data. In case comparison is true, the data is forwarded:
“RX data & mask” == match
The Match bytes (hex), Mask bytes (hex), Number of start bytes to add, Start bytes (hex), Number of end bytes to add and End bytes (hex) are applied to the received serial data.
Add a custom CAN Frame ID, Use this Frame ID (hex), CAN Frame ID length, Use TP and Add frame index to byte 0 are applied to data that is forwarded to the CAN interface (#4).
Forward all data bytes / Number of bytes to forward are applied to all forwarded data.
Please note, that the TP messaging is used only when 29bit CAN frame ID is specified. In case TP is in use, the PGN wrapped inside the TP frame is specified using the Use this Frame ID (hex) option.
The Add frame index to byte 0 option can be used with 11bit frame IDs. This implements “TP like” CAN output.
UMAX142100A
23 – 42
<configured ip>/rx_message_config.shtml
A value from a received frame, such as GPS data, can be parsed using the configuration options available in the Receive Message Configuration page. 3RS-ENET-CAN converter supports 4 serial message configurations.
Match bytes (hex, Serial&Ethernet) define the start of the serial message that should be parsed from the serial data stream. Mask bytes (hex, Serial&Ethernet) set the mask that will be used in the Match bytes detection.
When reading CAN data, the Identifier (hex, CAN) and Identifier Mask (hex, CAN) define the rules for checking the received CAN frames.
The data type to be parsed is selected from the Data Type drop down menu.
Configuration and data range for the data to be parsed is defined in the Data Width (CAN), Data Byte Position, Data Bit Position, Data Maximum, Data Minimum, Data Resolution and Data Offset.
If the received data needs to expire after a certain time, this can be defined using the AutoReset Time.
UMAX142100A
24 – 42
Receive message configuration examples
The above configuration (on the left) reads in a CAN frame with J1939 PGN 0xFF80. The CAN frame is defined using the full ID and a mask that requires that all bits in the CAN frame need to match the configured ID.
The CAN data is 16 bits wide, and parsing starts from CAN payload byte 0, bit 0. The maximum value for the data is 1000.00 (parsed value) and the resolution to use when parsing CAN data is 0.25 units per bit. Data Type CAN continuous defines that the maximum, minimum, offset and resolution settings are applied. With CAN discrete data, the offset and resolution are not applied, and the maximum value is set by the Data Width (CAN).
Since the AutoReset Time is 0, the received data will be valid until the next CAN frame is received or the 3RS-ENET-CAN converter’s power is cycled.
On the right side, an example Receive Message Configuration for serial data parsing is shown. This configuration defines that a serial message with the first four bytes 0x24, 0x47, 0x53, 0x2C ($GS, xrn in ascii) shall be read in (in which x is the value to parse). The Mask bytes define that all four bytes need to match fully.
The data type is Integer, and the maximum value is 5000. Data Resolution is set to 1, so the parsed value is converted to Integer type with no additional scaling.
The data is parsed starting from the first byte following the configured Match bytes (hex, Serial&Ethernet).
UMAX142100A
25 – 42
<configured ip>/tx_message_config.shtml
A periodically transmitted data message can be configured using the configuration options on the Transmit Message Configuration page. The message can be sent to all communication interfaces on the 3RS-ENET-CAN converter. 3RS-ENET-CAN converter supports 4 transmit messages.
Output Interface lists all supported interfaces for sending the message. Data Source selects the source for the data to be included into the transmit message. Transmit Interval defines the periodic transmission interval in milliseconds.
Identifier (hex, CAN) is the CAN frame ID to use. This will be applied only to messages that are transmitted to CAN.
Static transmit data, start defines the static bytes to add to a serial/ethernet message. These bytes are added before the variable data field. Static transmit data, end defines the bytes to add after the variable data field.
Data Type, Data Width (CAN), Data Byte Position, Data Bit Position, Data Maximum, Data Minimum, Data Resolution and Data Offset configure the variable data, inserted between the static start and end bytes or to a CAN frame.
UMAX142100A
26 – 42
Transmit message configuration examples
The above configuration (on the left) transmits a message $DS,0,0,0,x,0n (in which x is the variable data field) into the serial port #1.
The Data Source for the variable data field is CAN Receive Message #1 and the message is transmitted every 5000ms.
The complete list of Static bytes, start is 0x24,0x44,0x53,0x2c,0x30,0x2c,0x30,0x2c,0x30,0x2c, which is $DS,0,0,0, in ascii. The Static bytes, end is 0x2c,0x30,0x0d. This is 0n in ascii.
The Data Type to insert is Floating point and the data should be inserted starting from byte 10 in the transmit message. Please note that the Static bytes, start need to contain enough bytes to be added to the message before the variable data field, otherwise the transmit message gets inadvertently truncated by null data. Maximum value for the data field is 1000.00 and the data from Receive Message #1 is not scaled (Data Resolution is 1.00).
On the right side, a CAN transmit message is configured. This message uses data from Receive Message #2 and is sent at 1000ms intervals.
Identifier (hex, CAN) defines the CAN ID to use. Static transmit data, start and Static transmit data, end are not configured since those settings are not used in CAN transmit messages.
The Data Type CAN continuous defines that the data in CAN payload bytes should be scaled using Data Maximum, Data Minimum, Data Resolution and Data Offset settings. Data Byte Position and Data Bit Position settings define the data location in the CAN payload data bytes.
UMAX142100A
27 – 42
<configured ip>/settings_transfer.shtml
The AX142100A supports settings upload and download using the legacy text and binary format. The settings can be downloaded from the AX142100A by using the corresponding link on the Settings Upload/Download page. The settings upload function opens a dialog for selecting a previously saved settings file. Both types of settings, text and binary can be selected.
UMAX142100A
28 – 42
<configured ip>/fullconfig The 3RS-ENET-CAN supports the use of cURL (or equivalent) for full settings file download and upload in the legacy text format. This is an alternative method for the method found on the `Settings Upload/Download’ page. Please note that to access the configuration, the correct password needs to be entered first. The current configuration can be downloaded to PC using command: curl -o “./config.file” “http://192.168.1.20/fullconfig”
The saved configuration can be uploaded to the 3RS-ENET-CAN device: curl –upload-file “./config.file” “http://192.168.1.20/fullconfig”
Note, that cURL configuration upload and download are supported for backwards compatibility purposes only. cURL won’t return meaningful status after successful data transfer, in most cases only the status and message curl: (52) Empty reply from server or similar is shown.
UMAX142100A
29 – 42
4.2. TCP/UDP Connections
The forwarded frames can be sent as proprietary TCP or UDP frames. A client can listen to these frames by initiating a TCP (or UDP) connection to port 4000 (or to custom port, configured using EA or a web browser) on the 3RS-ENET-CAN. These forwarded data messages are sent when the data become available from serial ports or from CAN interface The TCP/UDP port can be written to, the received frames will be forwarded to output interfaces specified on the routing configuration page #5. The Message Header contains: 4-byte Axiomatic Tag, AXIO in capital letters 2-byte Protocol ID, 20008 = 0x4E28 2-byte Message ID 1-byte Message Version, 0 (for future use) 2-byte Message Data Length
The proprietary messaging protocol Message Header format is presented below.
Octet
0
1
2
3
Offset Octet 0
4
8
A
X
0x41
0x58
0x28
0x4E
Protocol ID (20008)
I
O
0x49
0x4F
Axiomatic Tag
Message ID
0x00 Message Version=0
Message Data Length
Message Data
Table 2 TCP message header format
The Axiomatic Tag is used for message header identification.
The Protocol ID defines a proprietary protocol carried by this message. This field allows different protocols to use the same protocol independent message structure. The AX142100A uses Protocol ID = 0x4E28
The Message ID defines the type of the Message Data:
Message ID 0 1
Message name Undefined message Forwarded data
UMAX142100A
30 – 42
The first byte of the payload data in the Ethernet frame contains status bits that control how the AX142100A handles the received Ethernet data. In case the Raw data flag is set, all following bytes are considered as data with no special formatting. <first byte> & 0x40 == Raw data In case the Raw data flag is not set, the data bytes are considered as CAN data <first byte> & 0x10 == 0x10 -> 29bit CAN frame ID <first byte> & 0x10 == 0x00 -> 11bit CAN frame ID <first byte> & 0x0F == CAN data length
An example printout of the TCP client (see also Table 3 Example TCP client implementation) reveals the TCP frame contents when a CAN frame is forwarded to Ethernet.
Figure 3 TCP/IP frame contents vs. CAN data The frame starts with the header bytes described in Table 2. After the header, the first byte of the payload data is marked green. It contains a flag that the CAN frame has 29bit ID and 8 data bytes. The CAN frame ID is marked orange and CAN data bytes with yellow. Please note that the AX142100A considers the Ethernet frames like the one above as CAN data (no Raw data flag set). When this data is forwarded to the CAN interface, the frame ID type (29bit/11bit) and the ID bytes are automatically picked up from the Ethernet frame. On the other hand, when the Ethernet frame contains Raw data, the data is forwarded `as is’ and no special processing is applied (other than the routing rules defined for Ethernet data).
UMAX142100A
31 – 42
#include <winsock2.h> #include <Ws2tcpip.h> #include <stdio.h>
#define DEFAULT_BUFLEN
256
#define IP_ADDRESS
“192.168.1.20”
#define FWD_DATA_PORT 4000
#define dRAW_DATA_FLAG 0x40
int main(void) {
int iResult, index; WSADATA wsaData;
SOCKET ConnectSocket = INVALID_SOCKET; struct sockaddr_in clientService;
int recvbuflen = DEFAULT_BUFLEN; char recvbuf[DEFAULT_BUFLEN];
// Initialize Winsock iResult = WSAStartup(MAKEWORD(2,2), &wsaData); if (iResult != NO_ERROR) {
printf(“WSAStartup failed with error: %dn”, iResult); return 1; }
// Create a socket for connecting to the AX142100 ConnectSocket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); if (ConnectSocket == INVALID_SOCKET) {
printf(“socket failed with error: %dn”, WSAGetLastError()); WSACleanup(); return 1; }
clientService.sin_family = AF_INET; clientService.sin_addr.s_addr = inet_addr( IP_ADDRESS ); clientService.sin_port = htons( FWD_DATA_PORT );
// Connect to the AX142100 iResult = connect( ConnectSocket, (SOCKADDR*) &clientService, sizeof(clientService) ); if (iResult == SOCKET_ERROR) {
printf(“connect failed with error: %dn”, WSAGetLastError() ); closesocket(ConnectSocket); WSACleanup(); return 1; }
// Receive data until the AX142100 closes the connection do {
memset((void *)recvbuf, 0x00, sizeof(recvbuf)); iResult = recv(ConnectSocket, recvbuf, recvbuflen, 0); if ( iResult > 0 ) {
printf(“Bytes received: %d (msg data in hex below)n”, iResult); for ( index = 1; index < iResult+1; index++ ) {
printf(“%02X “, (unsigned char)recvbuf[index-1]); if ( (index % 8) == 0 ) printf(“n”); } printf(“n”);
// Send back with ID + 1 (Frame ID is in indexes 12 … 15) if( recvbuf[12] < 255 ) recvbuf[12]++;
#if 0 // Send back as raw data instead of CAN data recvbuf[11] |= dRAW_DATA_FLAG; printf(“message flagged as raw data.n”); #endif
iResult = send( ConnectSocket, recvbuf, iResult, 0 ); if (iResult == SOCKET_ERROR) {
printf(“send failed with error: %dn”, WSAGetLastError());
UMAX142100A
32 – 42
closesocket(ConnectSocket); WSACleanup();
return 1; }
printf(“%d bytes sent backn”, iResult); } else if ( iResult == 0 )
printf(“Connection closedn”); else
printf(“recv failed with error: %dn”, WSAGetLastError());
} while( iResult > 0 );
return 0; }
Table 3 Example TCP client implementation
The example can be compiled using MinGW: <MinGW location>bingcc.exe -Wall -o data_client data_client.c -lws2_32
UMAX142100A
33 – 42
5. ECU SETPOINTS ACCESSED WITH AXIOMATIC ELECTRONIC ASSISTANT
This section describes in detail each setpoint, and their default and ranges. The setpoints are divided into setpoint groups as they are shown in EA. For more information on how each setpoint is used by 3RS-ENET-CAN, refer to the relevant section in this user manual.
5.1. J1939 Setpoints
“ECU Instance Number” and “ECU Address” setpoints and their effect are defined in section 3.2.
Name ECU Instance Number ECU Address
Range 0-7 0-253
Default 0x00 0x80
Table 4 J1939 Setpoints
Notes Per J1939-81 Preferred address for a selfconfigurable ECU
If non-default values for the “ECU Instance Number” or “ECU Address” are used, they will be mirrored during a setpoint file flashing and will only take effect once the entire file has been downloaded to the unit. After the setpoint flashing is complete, the unit will claim the new address and/or re-claim the address with the new NAME. If these setpoints are changing, it is recommended to close and re-open the CAN connection on EA after the file is loaded so that only the new NAME and address are showing in the J1939 CAN Network ECU list.
Figure 4 Screen Capture of J1939 Network Setpoints
UMAX142100A
34 – 42
5.2. Ethernet Parameter Setpoints
The Ethernet parameters can be configured using EA. A power cycle is needed for taking the new network settings into use.
Figure 5 Screen Capture of Ethernet Parameter Setpoints
Name IP Address, B0 IP Address, B1 IP Address, B2 IP Address, B3 Port
Remote IP Address, B0 Remote IP Address, B1 Remote IP Address, B2 Remote IP Address, B3 Remote Port
Autoconnect to Remote
Netmask, B0 Netmask, B1 Netmask, B2 Netmask, B3
Range 0…255 0…255 0…255 0…255 0…65535
0…255 0…255 0…255 0…255 0…65535
0, 1
Default 192 168 1 20 4000
192 168 1 120 4001
0 False
0…255
255
0…255
255
0…255
255
0…255
0
Table 5 Ethernet Parameter Setpoints
Notes These settings define an IP address: 192.168.1.20
Default port for incoming TCP connections These settings define an IP address for remote connection: 192.168.1.120
Default port for remote TCP connection Whether to automatically initiate remote TCP/UDP connection These settings define a netmask 255.255.255.0
UMAX142100A
35 – 42
5.3. Overall Configuration Options
Figure 6 Screen Capture of Overall Configuration Options Setpoints
Name
Range
Enable configuration web server 0, 1
Set defaults now
0, 1
Default 1 True
0 False
Notes Configuration web server running on port 80 (TCP) This setpoint is password protected. The password is `SetDefaults’.
Table 6 Overall Configuration Options Setpoints
UMAX142100A
36 – 42
6. REFLASHING OVER ETHERNET USING A WEB BROWSER The AX142100A can be upgraded with new application firmware using a web browser. Once the correct configuration password is entered, the firmware reflash can be done using the `Firmware’ page. <configured ip>/firmware.shtml
On the `Firmware’ page, a file selection dialog can be opened by pressing the `Browse…’ button.
Navigate to where you had saved the AF-23012-x.xx.af file sent from Axiomatic. (Note: only binary (.af) files can be flashed using the web browser firmware update interface.)
UMAX142100A
37 – 42
Once the file is selected, the actual upload/upgrade process is started by pressing the `Upload’ button.
The firmware upload process is shown below the `Upload’ button.
Once the upload is finished and the file checked and stored to a temporary location on the AX142100A, the user is prompted to either to `Apply New Firmware’ or cancel the operation.
UMAX142100A
38 – 42
The firmware reflash procedure takes 30 seconds to finish. After this the AX142100A reboots automatically to the new firmware and returns to the password dialog.
UMAX142100A
39 – 42
APPENDIX A – TECHNICAL SPECIFICATION
Specifications are indicative and subject to change. Actual performance will vary depending on the application and operating conditions. Users should satisfy themselves that the product is suitable for use in the intended application.
All our products carry a limited warranty against defects in material and workmanship. Please refer to our Warranty, Application Limitations & Return Materials Process as described on https://www.axiomatic.com/service/.
All specifications are typical at nominal input voltage and 25°C unless otherwise specified.
Power
Power Supply Input Quiescent Current Surge Protection Under-Voltage Protection Over-Voltage Protection Reverse Polarity Protection
12 or 24 VDC nominal (9 to 36 VDC) 150 mA @ 12 V; 90 mA @ 24 V typical 95 VDC Hardware shutdown at 6 VDC Hardware shutdown at 45 VDC Provided up to -36 VDC
Functionality
Conversion Platform
Ethernet RS-422 RS-232 ASCII Features
CAN
The Protocol Converter comes pre-programmed with standard protocol conversion logic for bidirectional data exchange between an Ethernet (proprietary TCP communications), an RS-422 bus, two RS-232 buses and a CAN network (SAE J1939).
Data is forwarded “as-is” between the different serial ports. Also, CAN/Ethernet data is forwarded directly to serial interfaces with the configuration allowing the user to specify the CAN message ID (or TCP port) to listen
for data to be forwarded.
1 10/100 Mbit Ethernet compliant port 10BASE-T, 100BASE-Tx (auto-negotiation and full-duplex supported) Auto-MDIX
1 RS-422 port Baud rate: up to 10.5 Mbit/s Note: RS-422 connections can be used as RS-485. See pinout.
2 RS-232 ports for serial communications Three-wire Baud rate: up to 400 kbit/s
Maximum Number of ASCII devices Serial Communications Port 0 Serial Communications Port 1 Message Queue Size
2 RS422 RS232 Configurable
1 SAE J1939 port Isolated Baud rate: 250 kbit/s (default)
General Specifications
Microcontroller Isolation Web Interface
User Interface
STM32H723VGT 32-bit, 1 MB flash memory
CAN isolation: 330 Vrms
Refer to the User Manual. The functionality of the web interface includes but is not limited to the following. Specify CAN message filters and CAN message IDs to be received Link RS-232 or RS-422 to CAN bus and Ethernet Define CAN node ID and baud rate Define Ethernet parameters (IP address, netmask) Configure message queues
Axiomatic Electronic Assistant (P/N: AX070502 or AX070506K) for Windows operating systems comes with a royalty-free license for use on multiple computers. It requires an Axiomatic USB-CAN converter to link the device’s CAN port to a Windows-based PC.
The functionality of the Axiomatic Electronic Assistant includes IP address configuration and firmware reflashing.
UMAX142100A
40 – 42
LED Indicators
Enclosure and Dimensions Weight Operating Temperature Storage Temperature Compliance Protection Vibration Shock Electrical Connections
Mating Connectors Mating Cables Mounting
Power LED GREEN = Power ON RED = Fault condition GREEN/RED = Power OFF
2 GREEN LEDs for Ethernet LINK/ACT: ON means connection (LINK)
Flashing means activity (ACT) OFF means Ethernet connection is down 10/100: Transmission Speed 100 Mbit/s = ON Transmission Speed 10 Mbit/s = OFF
Nylon 6/6, 30% glass fill Ultrasonically welded 4.19 in x 1.81 in x 1.31 in (106 mm x 46mm x 33 mm) L X W X H includes integral connectors Flammability rating: UL 94V-0 Refer to dimensional drawing.
0.172 lb. (0.078 kg)
-40C to 70C (-40F to 158F)
-40C to 85°C (-40F to 185°F)
RoHS
IP67
MIL-STD-202H, method 204, test condition C 10 g peak (Sine) MIL-STD-202H, method 214A, test condition I/B 7.56 Grms (Random)
MIL-STD-202H, method 213B, test condition A 50 g peak
CAN / RS-232 / RS-422 Connector 1 Phoenix Contact M12 12-pin connector (A-coded), Female P/N: 1441833
Note: To use RS-422 as RS-485, connect the Tx+ and Rx+ pin to D+ on the RS-485 connector. Also connect the
Tx- and Rx- to pin D-.
PIN #
Description
1
RS-422 RX+
2
RS-422 TX+
3
RS-422 RX-
4
RS-232 TX 2
5
RS-232 RX 2
6
CAN_L
7
CAN_H
8
RS-232 TX 1
9
RS-232 RX 1
10
RS-422 TX-
11
GND
12
GND
Ethernet / Power Connector
1 Phoenix Contact M12 8-pin connector (A-coded), Female P/N: 1441817
PIN #
Description
1
Power +
2
Power –
3
Power –
4
Ethernet TX-
5
Ethernet RX+
6
Ethernet TX+
7
Power +
8
Ethernet RX-
Not supplied Mating connectors should meet the following standard for M12 connectors, IEC 61076-2-101:2012. They should be A-coded.
AX070531 (1.7 m (5.5 ft.), 8-pin M12 A-coded, Unterminated Leads, Ethernet Jack, Ethernet and Power Cable) mates with the Ethernet / Power Connector
AX070533 (RS-232, RS-232 (RS-485), RS-422 Cable 1.5 m (5 ft.), 12-pin M12, Unterminated Leads, CAN Cable) mates with the CAN / RS-232 / RS-422 / RS-485 Connector
Mounting holes sized for #10 or M5 bolts
UMAX142100A
41 – 42
Dimensional Drawings AX070533 Mating Cable
AX070531 Mating Cable UMAX142100A
42 – 42
OUR PRODUCTS
AC/DC Power Supplies Actuator Controls/Interfaces Automotive Ethernet Interfaces Battery Chargers CAN Controls, Routers, Repeaters CAN/WiFi, CAN/Bluetooth, Routers Current/Voltage/PWM Converters DC/DC Power Converters Engine Temperature Scanners Ethernet/CAN Converters, Gateways, Switches Fan Drive Controllers Gateways, CAN/Modbus, RS-232 Gyroscopes, Inclinometers Hydraulic Valve Controllers Inclinometers, Triaxial I/O Controls LVDT Signal Converters Machine Controls Modbus, RS-422, RS-485 Controls Motor Controls, Inverters Power Supplies, DC/DC, AC/DC PWM Signal Converters/Isolators Resolver Signal Conditioners Service Tools Signal Conditioners, Converters Strain Gauge CAN Controls Surge Suppressors
OUR COMPANY
Axiomatic provides electronic machine control components to the off-highway, commercial vehicle, electric vehicle, power generator set, material handling, renewable energy and industrial OEM markets. We innovate with engineered and off-the-shelf machine controls that add value for our customers.
QUALITY DESIGN AND MANUFACTURING
We have an ISO9001:2015 registered design/manufacturing facility in Canada.
WARRANTY, APPLICATION APPROVALS/LIMITATIONS
Axiomatic Technologies Corporation reserves the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. Users should satisfy themselves that the product is suitable for use in the intended application. All our products carry a limited warranty against defects in material and workmanship. Please refer to our Warranty, Application Approvals/Limitations and Return Materials Process at https://www.axiomatic.com/service/.
COMPLIANCE
Product compliance details can be found in the product literature and/or on axiomatic.com. Any inquiries should be sent to sales@axiomatic.com.
SAFE USE
All products should be serviced by Axiomatic. Do not open the product and perform the service yourself.
This product can expose you to chemicals which are known in the State of California, USA to cause cancer and reproductive harm. For more information go to www.P65Warnings.ca.gov.
SERVICE
All products to be returned to Axiomatic require a Return Materials Authorization Number (RMA#) from rma@axiomatic.com. Please provide the following information when requesting an RMA number:
· Serial number, part number · Runtime hours, description of problem · Wiring set up diagram, application and other comments as needed
DISPOSAL
Axiomatic products are electronic waste. Please follow your local environmental waste and recycling laws, regulations and policies for safe disposal or recycling of electronic waste.
CONTACTS
Axiomatic Technologies Corporation 1445 Courtneypark Drive E. Mississauga, ON CANADA L5T 2E3 TEL: +1 905 602 9270 FAX: +1 905 602 9279 www.axiomatic.com sales@axiomatic.com
Axiomatic Technologies Oy Höytämöntie 6 33880 Lempäälä FINLAND TEL: +358 103 375 750
www.axiomatic.com
salesfinland@axiomatic.com
Copyright 2024
Documents / Resources
 |
AXIOMATIC UMAX142100A Protocol Converter [pdf] User Manual UMAX142100A Protocol Converter, UMAX142100A, Protocol Converter, Converter |