Connect the logger to the PC via USB.
The Status Bar will display the logger status and time information.
Click ‘Run Configuration’, save the project, and provide a name for the project. The logger will create files with the name of the project.

The configuration will be loaded in the data logger, and logging will start immediately.

Logging Using Filters

Create a new project.

Drag and drop the CAN Filter tool into the bus from which the user wants to log data.

*The User can add the CAN Error tool to the bus for logging CAN errors. See Appendix 1 for various error codes.

Click on the CAN bus icon and set the CAN Bus properties.

*Users can use the ‘Use Bit Timing’ option for advanced configurations.

Click on the filter tool icon to configure the filter settings.

The user can add CAN ID for filtering from DBC files by clicking the browse icon.

Click on the Storage icon and configure the Log file settings.

Connect the logger to the PC via USB.
The status bar will display the logger status and time information.
Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Logging Using J1939 Filters

Create a new project.

Drag and drop the J1939 filter tool into the bus from which the user will log data.

*User can add the CAN Error tool to the bus for logging CAN errors. See Appendix 1 for various error codes.

Click on the J1939 filter tool icon to configure the filter settings.

Enter the filter values.

Users can use a combination of SA, DA & PGN, or they can be used individually.

Click the browse icon to import the PGN values using a J1939 DBC.

Once you have added the value, click ‘Add’.

Users can Add, Edit or Remove filters added to the configurations.

*User can add the CAN Error tool to the bus for logging CAN errors.

Click on the Storage icon and configure the Log file settings.

Connect the logger to the PC via USB.
Status Bar will display the logger status and time information.
Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Logging Analog Channels

Create a new project.

Drag and drop the Analog tool to the Channels area of the configuration window.

Select Analog channel from the Analog channel drop box.
- Enter the sampling rate required for logging in to the sampling rate column.
- Define the ‘Formula’ for scaling the sensor output to engineering units.
  - A- is the slope or the scale factor
  - X- is the input (volts)
  - B- is the offset, and the output will be engineering units.

Click ‘Add’ to add the selected channel.

Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

The configuration will be loaded in the data logger, and logging will start immediately.

How to configure analogue and digital channels using ReXdesk

Logging Digital Channels

Create a new project.

Drag and drop the Digital tool to the Channels area of the configuration window.

Select the Digital channel from Digital channel Dropbox. Enter the sampling rate required for logging in to the sampling rate column.

Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Logging Accelerometer data

Create a new project.

Drag and drop the Accelerometer tool to the channels in the configuration window.

Select the range and enter the sampling rate for logging.

Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Logging Gyroscope data

Create a new project.

Drag and drop the Gyro tool beside IMU in the configuration window.

Select the range and enter the sampling rate for logging.

Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Logging GNSS data

For the information about GNSS orientation of the device refer to Appendix 3 – GNSS Orientation Guide

Create a new project.

Drag and drop the GNSS tool beside GNSS in the configuration window.

Enter the sampling rate for GNSS parameters.

Notes:

The fastest sampling rate is 30Hz.

Click “Run Configuration”, save the project and provide a name for the project. The logger will create files with the name of the project.

Advanced Configuration

Setup Cloud Settings

Upload Configuration to the logger via FTP

Upload Configuration to the logger via AWS

Trigger-Based Logging

Periodic CAN/CAN FD Transmission

HW Info Tool

Snapshot Tool

Setup Cloud Settings

Mobile Settings

FTP Settings

AWS Settings

Mobile Settings

Steps to add new Mobile setting using ReXdesk

Click on the Tool tab in the Navigation bar and select Cloud Settings.

In the Cloud Settings window, select the Mobile option and then select the ‘New Mobile’ option.

In the Mobile Settings window, specify the names of the mobile settings.

Specify the label and user name and set the Password.

Enter the delay interval for communication time out in minutes in the ‘No Communication Timeout (min)’ section.
To use an APN, check the ‘Use APN’ checkbox and specify the APN.

Enable Realtime Source' to get real-time from the server (select ‘Mobile’ from the drop-down options).

Notes:

'Realtime Source' must be enabled when using AWS upload.

Or

Click OK.

The new mobile setting details have been defined using ReXdesk.

FTP Settings

(a) Steps to add new FTP settings using ReXdesk

(b) Steps to enable FTP configuration in the ReXgen logger.

How to in ReXdesk.

Steps to add new FTP settings using ReXdesk

Click on the Tool tab in the Navigation bar and select Cloud Settings.

Select the ‘FTP ‘option in the Cloud Settings window and then the ‘New FTP’ option.

To use the server, enable ‘Use Server Name’ and specify the Server name and port number.

Or

To use the IP address, enable ‘Use IP Address’ and specify the Server IP and port number.

Specify a label/name for the current FTP settings

Specify Server Name/Server IP and Port.

Select the desired protocol from the ‘Protocol’ drop-down menu (select FTP for ReXgen devices).

Select the desired mode from the ‘Mode’ drop-down menu (select Passive for ReXgen devices).

Specify the User name and Password.

Click ‘OK’.

The new mobile setting details have been defined using ReXdesk.

Click on ’x’ to exit the window.

Steps to enable FTP configuration in the ReXgen logger.

Prepare the base configuration for the logger.

In the Device Configuration window, Click on the ‘Upload’ tab.

Enable the ‘checkbox’ for ‘Store data to FTP using mobile internet’.
- For a single setting, details are auto-filled in the subsequent sections.
- Users can select the desired setting from the corresponding drop-down menu for multiple settings.
Click on the ‘Run’ tab in the Navigation bar.

Save the project:

a) Save project: allows you to save the project with the user-defined name.

b) Continue as “New Project”: saves the configuration labelled ‘New Project.’

Click okay once the configuration is uploaded successfully.

AWS Settings

How to in ReXdesk

Steps to add new AWS settings using ReXdesk

Click on the Tool tab in the Navigation bar and select Cloud Settings

In the Cloud Settings window, select the ‘S3 ‘option and then select the ‘New S3’ option.

In the S3 Settings window, specify the Region from the drop-down menu.

Specify the type of storage services - AWS or Compatible (alternate S3 API-supported storage services).

Specify the S3 Connection type from the drop-down menu. Select Plain for HTTP connection and SSL for HTTPS (Certificate must be added to the XML file).

Specify ‘Port’ details: 80 if the connection type is Plain, 443 if the connection type is SSL.

Specify the bucket name for objects stored in Amazon S3.

Specify the ‘Access Key’ and ‘Secret Key’ for the AWS account.

Click ‘OK’.

The new AWS S3 setting details have been defined using ReXdesk.

Click on ’x’ to exit the window.

Steps to enable AWS configuration in the ReXgen logger

Prepare the base configuration for the logger.

In the Device Configuration window, Click on the ‘Upload’ tab.

Enable the ‘checkbox’ for ‘Enable Aws’.
- For a single setting, details are auto-filled in the subsequent sections.
- Users can select the desired setting from the corresponding drop-down menus for multiple settings.

Click on the ‘Run’ tab in the Navigation bar.

Save the project:

a) Save project: allows you to save the project with the user-defined name.

b) Continue as “New Project”: saves the configuration labelled ‘New Project.’

Click 'OK' once the configuration is uploaded successfully.

Upload configuration to the logger via FTP

This step-by-step guide explains uploading a new configuration to the FTP Server by placing the .rxc file in the logger root folder.

Step 1

Note:

Before you begin the steps, ensure your logger is connected to the server with an existing configuration.

Make the new configuration.
Enable FTP from the Device Configuration menu.

Note:

Set your configuration check time in the given section while enabling FTP.

Step 2

Save the Project with the name you require for the configuration.
Under the ‘Config’ tab, select Export from the drop-down menu.
Select ‘Export ReXgen Configuration (rxc)’ from the listed options.

Step 3

Save the file with the desired name.
Click ‘Save’.
Once saved, rename the file as ‘config.rxc.’

Note:

Ensure that you rename the file as 'config.rxc' only.
If the xml is custom-made, ensure to change the guid of the xml file whenever it is sent through the server.

Step 4

Upload the configuration file to your FTP folder by adding it to the root folder of the logger.

Note:

Once the USB is removed, only then the logger will connect to the server and upload files.

Upload configuration to the logger via AWS

This step-by-step guide explains uploading a new configuration to the AWS S3 bucket by placing the .rxc file in the logger root folder..

Step 1

Note:

Before you begin the steps, ensure your logger is connected to the server with an existing configuration.

Make the new configuration.
Enable AWS from the Device Configuration menu.

Note:

Set your configuration check time in the given section while enabling AWS.

Step 2

Save the Project with the name you require for the configuration.
Under the ‘Config’ tab, select Export from the drop-down menu.
Select ‘Export ReXgen Configuration (rxc)’ from the listed options.

Step 3

Save the file with the desired name.
Click ‘Save’.
Once saved, rename the file as ‘config.rxc.’

Note:

Ensure that you rename the file as 'config.rxc' only.
If the xml is custom-made, ensure to change the guid of the xml file whenever it is sent through the server.

Step 4

Add to your config folder in your S3 bucket by adding it to the root folder of the logger.

Note:

Once the USB is removed, only then the logger will connect to the server and upload files.

Trigger-Based Logging

Clicking the trigger icon displays the trigger window.

Click on the 'New trigger' to add a new trigger action.

'Start logging' and 'Stop logging' can be added as trigger actions.

‘Log Time (sec)’ enables the logger to log for the given time after a trigger occurs.

‘Pre–Trigger Time (sec)’ specifies the duration for which pre-trigger data must be saved.

‘Debounce (msec)’ time is when the switch does not register another click, relevant when you use Digital I/P.

Click ‘Next’ to select the trigger type.

Select bus and trigger type and click ‘Next’.

Defining Trigger Conditions

Trigger by CAN identifier (Ident)– This option will enable the user to specify the CAN/CAN FD ID on which the trigger should be active.

ReXdesk allows the user to specify the CAN manually/CAN FD ID or import a DBC file.

Trigger by parameter– This option will enable the user to specify the parameter/signal value on which the trigger should be active.

ReXdesk allows the user to import signals from a DBC file.

Trigger by DM1 J1939 counter– This option will enable the user to set up a trigger based on the increase, decrease or change in the DM1 counter.

ReXdesk allows the user to specify the source address of the DM1 message, which the logger should be monitoring.

Trigger by digital channel– A digital trigger will be enabled only when the digital input is present in the configuration. Refer to Appendix 4 for setting up digital triggers in ReXgen.

Drag and drop the ‘Dig In’ tool to the channels in the configuration window.

Select the digital channel and sampling rate, and then click add.

Now, you can proceed with creating triggers based on the digital input.

This option will enable users to set up triggers based on the rising or falling edge or digital input changes. The default state of the digital bus is high.

When a trigger is present in the configuration, the Storage icon will change to indicate it.

Notes:

The default state of the digital bus is high; if you want to use the active trigger state as high, please GND the Digital PINs initially.

Periodic CAN/CAN FD Transmission

Create a new project.

Drag and drop the ‘Periodic Transmission’ tool to the ‘Output’ area of the configuration window.

If you have not configured the same in the logging area, click the CAN bus icons and set the CAN bus properties.

*Users can use the ‘Bit Timing’ option for advanced configurations.

In the periodic messages window,
- Add: This allows the user to add the messages to be transmitted.
  - Remove: This allows the user to delete unwanted messages.
  - Link Message UP: This allows the user to link one/multiple messages to the previous message.
  - Unlink: This allows the user to unlink one/multiple messages from the previous linked message.
  - Move Up: This allows the user to move a specific, unlinked configuration upward.
  - Move Down: This allows the user to move a specific, unlinked configuration downwards.
  - Load:
a) Load CSV: This allows the user to load the CSV file.
b) Load From Cloud: This allows the user to load the configuration from the cloud.
- Save CSV: This allows the user to save the periodic messages in CSV format.

Users can enter the following information:

Ident: Message Identifier
Linked: Know if the message is linked.
Period: Specify the Period of transmission.
Delay: Specify the delay in transmission.
CAN 0/CAN 1/CAN 2/CAN 3: Option to choose the transmission bus.
Type: Specifies the type of CAN message (CAN/CAN FD) (Standard/Extended).
BRS: Bit Rate Switch.
Log Tx: stores the logged transmission messages into the SD card.
DLC: Data Length Code (0-64).
Data

HW Info Tool

The user application can transmit a CAN Message to ReXgen to trigger the following responses:

1) Current Firmware version of the ReXgen.

2) ReXgen should confirm that it is configured, has a configuration version, and has an active configuration.

3) Send the serial number of the ReXgen.

4) Send the RTC Date & time.

Format of the Transmitted message:

FW_TYPE 0-Release, 1-alpha, 2-beta, 3-pre release

FW_BRANCH 0 -Main branch

Allows to drag and drop the same into the configuration. The tool has the following settings:

Output CAN
- Users can choose CAN 0 or CAN 1
Rx Ident: Start range CAN ID of messages transmitted from an external tool.
Tx Ident: Start range CAN ID of messages transmitted from ReXgen.

Example:

If Rx Ident is 7E0 and TX Ident is 7E8 in the configuration, the Identifiers will be as shown below:

Snapshot Tool

In the context of CAN bus logging, a snapshot file refers to a JSON-formatted file containing a periodic sample or "snapshot" of decoded CAN bus data for select CAN signals of interest.

The steps below help you transmit a periodic sample of decoded CAN bus data for select CAN messages of interest in JSON format.

Notes:

Before you begin these steps, add and enable AWS configuration for the ReXgen logger.

Drag the Snapshot tool in the Transmitting section in the configuration window.

This opens the Snapshot window.

Add Snapshot File: this allows the user to add and name a new snapshot file.
Remove Snapshot File: this allows the user to remove an existing snapshot file.
Add Items: this allows the user to add items to a snapshot file.
Remove Items: this allows users to remove items from a snapshot file.

Click on the ‘Add Snapshot File’ tab –

Enter the desired name, sampling rate (sec) and upload rate, and click OK.

Once the name of the Snapshot file is assigned, click the ‘Add Items’ tab to add the required items to the snapshot file.

Add them from the existing DBC file by clicking on the check box beside them.

Note:

One snapshot file supports only fourteen (14) items.

To add a new dbc file, click on the folder icon, select the desired dbc file containing the parameters, and click ‘Open’.

Select up to fourteen items and click ‘OK’.

Once the items are added to the snapshot file, specify the CAN source for each item separately.

Click “Run” to update the configuration.

The configuration will be loaded into the data logger and immediately start uploading to the S3 bucket.
The snapshot file is stored in the ‘Root’ folder inside your S3 bucket.

Open the root folder to view the snapshot file.

The file is stored in ‘.json’ format.

View the live value updates of the configured snapshot parameters in the snapshot .json file.

Note:

Snapshot is limited to 1 file with 13 items.
Multiplexes signals are not supported.

Retrieving Raw Data Log

Connect the logger to the PC via USB.

The status bar will display the logger status and time information.

Click on the ‘Internal Storage.’

The below window will open.

The log files in the logger’s internal memory will be displayed.
Select the files to be retrieved.
Click Download. If retrieved individually, the files will be downloaded in .mf4/.rxd/.blf/.asc/.trc/.csv/.xml/.mat format.

One-Click Export after Linking DBC to CAN/CAN FD Bus

Click ‘DBC’ in the library window to import the DBC file to be linked.

Once the DBC is imported into the library, a pop-up window will be displayed to link the added DBC to the required bus.

Click on the ‘Internal Storage.’

The below window will open.

Select the data logs and click on Download.

Choose the export format and file location.

On clicking ‘Save’, ReXdesk will convert the RAW data to physical values according to the DBC assigned in Step 2.

Exporting Data using CAN/CAN FD DBC File

This method exports only specific messages/signals from the RAW data using a DBC file.

The user will need to assign the DBC to the specific CAN Bus.

Click on the ‘Internal Storage.’

The below window will open.

Select the data logs and click on Download;

Select the ‘Advanced’ option and open the ‘Export data’ window below.

Choose the output format (.mf4/.mat/.csv).

Choose the time format (Only applicable for .csv format).

The user can choose the ‘Merge’ option if multiple data logs are to be exported.

Specify the output location for saving the exported data.

Click on the ‘load DBC file’ icon.

Drag and drop the required DBC messages/signals to the corresponding bus.

Notes:

ReXdesk supports PGN-based export when J1939 DBC is imported.

Click ‘Process’.
ReXdesk will process the RAW data and save the decoded data to the location specified in the first step.

Viewing Live Data

Ensure the Live USB icon is enabled during the configuration preparation to enable live data.

Run the configuration. The logging configuration can be ‘Log All’ or by using ‘Filter’.

Click the ‘Live’ icon in the navigation bar to open the live data window.

Click ‘Online’ to start viewing the live CAN data. To stop live data, click on the offline icon.

Logged data from the live data window can be exported to .asc format.

Log OBD2 Mode 1

The following literature explains how to use Influx ReXgen devices to Log OBD2 Mode 1

OBD2 generally focuses on emission control and supports a broad range of standard parameter IDs (PIDs) that can be logged across most vehicles.

'How to' - with ReXgen?

The OBD data can be easily logged using any ReXgen logger from Influx with the ReXdesk software.

Periodic CAN/CAN FD Transmission

Step 1

Create a new project.

Step 2

Drag and drop the 'Periodic Transmission' tool to the 'Output' area of the configuration window.

Step 3

If you have not configured the same in the logging area, click the CAN bus icons and set the CAN bus properties.

Step 4

To initiate OBDII Mode1 data logging, users must configure periodic transmission with OBD requests to the ECU.

Ident: specifies if the identifier is for "request messages" or "response messages."
- ID 7DF - OBD2 message identifier for a standard 11-bit.
- ID 7E8 - main engine or ECU response identifier.
*Linked: lets you link the message(s).
*Period: Specify the Period of transmission.
*Delay: Specify the delay in transmission.
CAN 0/CAN 1/CAN 2/CAN 3: Option to choose the transmission bus.
Type: CAN message (Standard/Extended).
DLC: Data Length Code (0-64).

(* - define only if/when needed)

Data:
- Request data message –
- Response data message –

Length: Specifies the length of bytes (after it) containing valid data. For example, in the request message

'02' specifies that the Engine or ECU must respond to the mode 01 and PID 0A codes in the next two bytes.

Similarly, for the response message

'04' specifies that the Engine or ECU response lies in the next four bytes, mode '01' request is replaced with '41' for responses and the PID code 0A's data is in the next four bytes '23 E6' (hex values).

Mode: specifies the diagnostic services described in the latest OBD-II standard SAE J1979 (this document is made explicitly for Mode 1).

PID: these are the standard OBD-II PIDs as defined by SAE J1979.

0A - Fuel pressure
05 - Engine coolant temperature
0C - Engine speed
0D - Vehicle speed

Decoding data values for the PIDs:

For example, if the output data looks like this

Then,

Similarly, all the hex data values need to be decoded according to their respective PID formulas

(Click for detailed list)

*For Heavier vehicles that use extended 29-bit CAN identifiers with bit rates 250K or 500K, the OBDII PID identifier is 18DB33F1 instead of 7DF. Also, the response ID is 18DAF1XX, where 'XX' varies according to various OEMs, as it is up to them to determine what CAN ID they assign for ECUs.