REXDESKREXGEN 1REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProManual

REXDESK: transmit periodic CAN messages and HW info

Updated

Use a REXGEN as a CAN transmitter. Send messages on a fixed period and stamp them with the time. Another tool on the bus can also ask the logger for its firmware, configuration, serial number and clock.

What the logger can send

The Transmitting group of the Tools panel holds three tools. You drop all three on the Output area of the configuration:

Periodic transmission

  1. Create a project. Select New Project on the toolbar.
  2. Drop Periodic on Output. Drag Periodic from the Transmitting group onto the Output area. The Periodic messages window opens.
  3. Set the bus. If the bus is not set up for logging already, select its Bus icon and set the type and bit rate. Bit Timing is there for advanced configurations.
  4. Add the messages. Select Add for each message and fill in its row. The columns are described below.
  5. Run the configuration. Select Run, then save and name the project. The configuration loads and the logger starts at once.
The Periodic messages window with four rows: a CAN Standard and a CAN Extended message on a 100 period, and two linked CAN FD messages with 64 data bytes, the DLC list open from 0 to 64
Each row is one message. A linked row follows the message above it.

The toolbar of the window:

Add, Remove
Adds a message, or deletes the selected one.
Link Message Up, Unlink
Links one or more messages to the message above, or breaks the link.
Move Up, Move Down
Moves an unlinked message up or down the list.
Load
Load CSV reads the messages from a CSV file. Load From Cloud reads them from the cloud.
Save CSV
Saves the messages as a CSV file.

The columns of each message are below. Some builds label Ident as Tx Ident.

Ident
The message identifier.
Linked
Shows whether the message is linked to the one above.
Period
How often the message is sent.
Delay
The delay before the message is sent.
CAN 0 to CAN 3
The bus or buses the message goes out on.
Type
CAN Standard, CAN Extended, CAN FD Standard or CAN FD Extended.
BRS
Bit rate switch, for CAN FD messages.
Log Tx
Also records the sent messages in the log on the logger.
DLC
The number of data bytes, from 0 to 8. CAN FD also allows 12, 16, 20, 24, 32, 48 or 64.
Data
The data bytes.

Add a timestamp or the clock to a message

The button at the end of a row opens Link signals to the selected message. Select +, then select TimeStamp or RTC under Signal. Set its Start Bit and Bit Count in the message, then select OK.

The Link signals to the selected message window with a Signal list offering TimeStamp and RTC, Start Bit and Bit Count columns and plus and minus buttons
Link the logger's timestamp or clock into a message.

Periodic transmission is also how a REXGEN requests OBD-II data. See REXGEN: log OBD2 Mode 1 PIDs.

Watch: Set up periodic message transmission in REXGEN (1:03)

HW info

With HW Info in the configuration, another tool on the bus can send the logger a CAN request and get back:

  • The firmware version
  • The configuration version, which confirms the logger is configured and the configuration is active
  • The manufacturing information, including the serial number
  • The date and time of the logger's clock

Drag HW Info onto the Output area and set it up:

The HW Info settings with Output CAN set to CAN 0, Rx Ident 0x7E0 and Tx Ident 0x7E8
Rx Ident and Tx Ident set the first of four request and four response identifiers.
Output CAN
CAN 0 or CAN 1.
Rx Ident
The first identifier the logger listens on for requests from the external tool.
Tx Ident
The first identifier the logger answers on.

Each kind of information has its own pair of identifiers, counting up from those two. With Rx Ident 7E0 and Tx Ident 7E8:

HW info request and response identifiers, with Rx Ident 7E0 and Tx Ident 7E8
Information Request Response Example request Example response
Firmware Rx Ident Tx Ident 7E0 7E8
Configuration ID Rx Ident + 1 Tx Ident + 1 7E1 7E9
Manufacturing info Rx Ident + 2 Tx Ident + 2 7E2 7EA
RTC time Rx Ident + 3 Tx Ident + 3 7E3 7EB
HW Info request and response identifiers REXDESK · HW INFO HW Info request and response identifiers Request from the tool Logger Response Information and data bytes REXGEN logger HW Info Rx Ident 7E0 Tx Ident 7E8 Firmware 0 1 2 3 4 version and type bytes Rx Ident + 1 7E1 Tx Ident + 1 7E9 Configuration ID 0 1 2 3 4 version number in bytes 0 to 3 Rx Ident + 2 7E2 Tx Ident + 2 7EA Manufacturing info 0 1 2 3 4 product, assembly, batch, serial Rx Ident + 3 7E3 Tx Ident + 3 7EB RTC time 0 1 2 3 4 UNIX date and time in bytes 0 to 3 Rx Ident and Tx Ident are the first identifiers, set in the HW Info block on CAN 0 or CAN 1; each kind of information uses the next one up. The byte table in the guide gives each layout.
HW info response data, bytes 0 to 4
Response Bytes 0 to 4
Firmware FW_MAJOR_VERSION, FW_MAJOR_VERSION, FW_MINOR_VERSION, FW_BRANCH, FW_TYPE
Configuration ID Configuration version number in bytes 0 to 3
Manufacturing info Product, assembly, batch, batch, SERIAL_NUMBER
RTC time UNIX date and time in bytes 0 to 3
FW_TYPE
0 release, 1 alpha, 2 beta, 3 pre-release.
FW_BRANCH
0 main branch.

Next: REXDESK: sleep and wake settings.

Products in this guide

REXDESK

Logger setup & data export

View REXDESK Ask an engineer

REXGEN 1

Vehicle black box

View REXGEN 1 Ask an engineer

REXGEN 2

Evidence data logger

View REXGEN 2 Ask an engineer

REXGEN 2 IMU GNSS

Motion & location data logging

View REXGEN 2 IMU GNSS Ask an engineer

REXGEN Air

CAN to cloud

View REXGEN Air Ask an engineer

REXGEN Pro

Edge data platform

View REXGEN Pro Ask an engineer

Still stuck?

Our engineers answer support questions on every Influx Technology product.