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:

• 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

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.

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.

OR

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.