BeingDecoder

01 / GUIDE

Overview

The main purpose of BeingDecoder is to configure a CanBus-controller board parameters such as CanBus parameters or logging trigger.
The same interface is able to manage log downloads and conversion.

02 / GUIDE

CAN-bus parameters

This interface lets you change CAN-bus parameters. The fields are described for CAN-bus line 1, but apply to the second line as well:

1. Enable CAN-bus: when selected, the board can log; otherwise the bus is disabled.
2. CAN-bus speed, from 33,333 to 1,000,000 bit/s.
3. CAN-bus transceiver mode. Nor (normal) sends ACK to other nodes and is recommended; Sil (silent) does not send ACK and should be used only by advanced users.

For advanced parameters (not required), see this document:

4. CAN-bus filter settings pop-up.
5. IDHigh and IDLow for List masking mode.
6. MIDHigh and MIDLow for Mask masking mode.
7. Choose between List and Mask masking modes.
8. Apply changes.

03 / GUIDE

Logging triggers

The log trigger starts logging only when a condition is met, improving efficiency and recording only useful information.
Three modes are available:

1. Always: starts logging when the board powers on.
2. ID: starts logging when the specified ID is found in CAN-bus traffic.
3. Signal: starts logging when a condition is met on a signal. It requires a .json configuration (.json generator from .dbc). Select the file with the Candb button or enter its path. After updating the .json file, choose a signal from the database and set its start condition.

04 / GUIDE

Save configuration

Saving the configuration is straightforward:

1. Specify the output path with the button and choose the folder in the file explorer.
2. The Config Generator button creates the config.bei file containing all CAN-bus configuration and trigger information.

05 / GUIDE

File system

When the CanBus-Controller board is connected over USB (only USB-C–USB-A data cables are compatible) or the microSD is inserted in a PC, you can view its file system:

1. Config folder: contains only config.bei. To change configuration, overwrite this file from BeingDecoder or manually. If it is missing or invalid, the board cannot operate correctly. Only files generated by BeingDecoder are compatible.
2. Error folder: contains log errors.
3. Log folder: contains sequentially numbered log files.
4. Stream folder: streams CAN-bus data held in a particular file.
5. Update folder: place the new firmware here; after reboot, the board automatically starts the update procedure.

06 / GUIDE

Log conversion

Data conversion is straightforward:

1. Select the log data to convert. They are in the Log folder, use the .brc extension, and can be selected by direct path or with the Log button.
2. Select a .json configuration (how to generate .json) by entering its path or using the button.
3. Select the output path by entering it or using the button.
4. Enter the file name; the .csv extension is recommended but not required.
5. Because the log contains the native CAN-bus packet frequency, this parameter resamples to the desired frequency. Do not exceed the channel’s real frequency.
6. The Smart checkbox increases conversion speed by analyzing only an initial portion of data. Disable it to ensure all packets are converted.
7. Start conversion.
8. Check conversion status.

07 / GUIDE

Licence activation

With the purchase of a BeingRobotic device, you are entitled to a BeingDecoder licence. Install BeingLicencer and follow these steps:

1. Open the installed program and press the copy button.
2. After signing in to beingrobotic.com, the licence generator appears at the top of this page. Paste the copied code and press “Request license”.
3. After a few seconds, a new interface appears. Press copy or copy the entire code manually.
4. Paste the code into the lower text box.
5. Press “Set license”.

You can now use the BeingDecoder application.

08 / GUIDE

Problem with installation?

Windows installation

While our applications await digital signing, Windows may show this warning. To install, follow these steps:

1. Click “More info”.
2. The warning concerns the publisher, which is currently unrecognized.
3. Click “Run anyway”.

The application does not request administrator privileges: it only needs to read and write files, without accessing system files.
If you have concerns about the procedure, email us.