Skip to content

Logging

The Online Mode covers both the transmission close to RealTime and Logging of CAN messages and data, see chapter Online Mode.

The colored dot in the Machines Overview indicates the status:

  • Grey – device is offline.
  • Green – device is online and it is logging data.
  • Blue – device is online and it transmits RealTime data.

The device logs CAN messages, GNSS data, and internal variables.

All the recorded data is saved in an internal, nonvolatile memory and automatically sent to the DataPlatform when a connection is available.

Note

The internal nonvolatile memory also stores recorded data as *.CLF-files. The maximum number of files which can be stored on the internal memory is 4000 files with a file size up to 1 KB. When the total of 4000 files is reached, newly saved files will overwrite the oldest file.

Configuring variables for CAN communication

To enable CAN communication and data logging, you must configure the following variables.

CAN Settings

The variables required concern the CAN connection and belong to the object dictionary group DEVICE VARIABLES.

Object Dictionary Group DEVICE VARIABLES
Figure 1: Object Dictionary Group DEVICE VARIABLES

Variable Value Function
CANOPEN NMT STARTUP 0 Automatically sets the device to CANopen mode "Operational".
CAN1/CAN2/CAN3:DEVICE CANOPEN NODE-ID 1 …​ 127 The CANopen node address (can_be_left_at_the_standard_value).
CAN1/CAN2/CAN3:DEVICE CAN BAUD RATE min. 50 kbit/s; max. 1 Mbit/s (default: 250kBit/s) The baud rate at which the CAN bus operates.

Logging Variables

The variables required concern the logfile and belong to the DEVICE VARIABLES > LOGGING object dictionary group.

LOGGING Object Dictionary Group
Figure 2: LOGGING Object Dictionary Group

Variable Function
LOGGING -- FILE UPLOAD PERIOD Period in which the logfile is completed and sent to the DataPlatform. value = 0 → data is sent when the size of the logfile reaches 1 kB.
LOGGING -- SEND FILE COMMAND Assign any value to the variable during operation in order to immediately close and transfer the existing logfile.

To track which device configuration was used to log the data, use the Device Configuration Version String device variable (part of DEVICE VARIABLES, not the LOGGING object dictionary group). Its value is written to every logfile. For more information, see DOD Versioning.