REXGEN 1REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProDeveloper

REXGEN XML reference: device settings (CONFIG)

Updated

Set the name, timestamp format, sleep behaviour, encryption and wake-up sources that apply to the whole logger.

What CONFIG holds

CONFIG is a required child of REXGENCONFIG. Its settings apply to the whole logger rather than to one port. Its children can appear in any order. Each entry in the settings lists gives the meaning, then whether the schema requires the element, its type and its default where one exists.

The CAN interfaces have their own sleep and wake options. See REXGEN XML reference: CAN interfaces and bit timing. If you are new to the format, start with REXGEN XML configuration: how it fits together.

CONFIG

CONFIG takes a UID attribute (required, unsigned short and unique in the file) and the optional Version, X and Y.

<CONFIG UID="1">
  <GUID>da661b4c-b641-485b-91a7-111cff5d82f8</GUID>
  <InterfaceCount>14</InterfaceCount>
  <Name>RTC2CAN</Name>
  <TimeStampSize>4</TimeStampSize>
  <TimeStampPrecision>10</TimeStampPrecision>
  <SleepMode>NO_SLEEP</SleepMode>
  <ConfigurationVersion>2</ConfigurationVersion>
  <CANPositiveTimeout>0</CANPositiveTimeout>
  <CANSilentDelay>0</CANSilentDelay>
  <CANReceiveTimeout>120</CANReceiveTimeout>
  <EncryptType>No_Encryption</EncryptType>
  <EncryptKey/>
  <LockDevice>false</LockDevice>
  <EncryptDataLog>false</EncryptDataLog>
  <WAKEUP_SOURCE_LIST/>
</CONFIG>
GUID
Identifies this configuration. Generate a new one for every new file. Required. GUID string (8-4-4-4-12 hexadecimal digits).
InterfaceCount
Deprecated. It once counted the interfaces in the file. The schema still requires it, and every example file sets 14. Required. Unsigned short.
Name
Name of the configuration. The logger puts it at the start of every log file name, on internal storage and in cloud storage. Required. String.
TimeStampSize
Size in bytes of the timestamp stored with each record. Use 4. Required. Unsigned short.
TimeStampPrecision
Resolution of the internal timestamp in microseconds. With 10, two records can be no closer than 10 µs apart. Use 10. Required. Unsigned int.
SleepMode
Whether and how the logger sleeps: NO_SLEEP, NORMAL_SLEEP or DEEP_SLEEP. Each model's product page lists its sleep currents. Required. Default NO_SLEEP.
ConfigurationVersion
Version of the configuration. Use 2, the value in every example file. Required. Unsigned short.
CANPositiveTimeout
Time in seconds after which the logger stops sending on CAN when it receives no positive response. The examples set 0. Optional. Unsigned short.
CANSilentDelay
Time in seconds during which the logger sends nothing on CAN. The examples set 0. Optional. Unsigned short.
CANReceiveTimeout
Time in seconds without a received message after which the logger goes to sleep. The examples set 120. Optional. Unsigned short.
EncryptType
Encryption and USB locking scheme: No_Encryption or RSA. Optional. Default No_Encryption.
EncryptKey
Key used with EncryptType. Leave it empty when encryption is disabled. Optional. String.
LockDevice
Locks the logger's USB communication when true. Optional. Boolean. Default false.
EncryptDataLog
Encrypts every log when true. The files are then RXE instead of RXD. Optional. Boolean. Default false.
NTPServer
Network time server used to set the clock on models that connect to a network. The examples leave it empty. Optional. String.
WAKEUP_SOURCE_LIST
The events that wake the logger from sleep, described in the next section. An empty list means no wake-up sources. Optional.

Wake-up sources (WAKEUP_SOURCE_LIST)

Each WAKEUP_SOURCE in the list names one event that wakes the logger. Add one entry for each source. This example wakes a two-channel logger on traffic on either CAN bus.

<CONFIG UID="1">
  <GUID>2f7b1c3e-8a4d-4c6b-9e21-5d0a7f3b6c14</GUID>
  <InterfaceCount>14</InterfaceCount>
  <Name>WakeOnCAN</Name>
  <TimeStampSize>4</TimeStampSize>
  <TimeStampPrecision>10</TimeStampPrecision>
  <SleepMode>NORMAL_SLEEP</SleepMode>
  <ConfigurationVersion>2</ConfigurationVersion>
  <CANReceiveTimeout>120</CANReceiveTimeout>
  <WAKEUP_SOURCE_LIST>
    <WAKEUP_SOURCE>
      <WakeupSourceType>CAN0</WakeupSourceType>
      <WakeupParameter>0</WakeupParameter>
    </WAKEUP_SOURCE>
    <WAKEUP_SOURCE>
      <WakeupSourceType>CAN1</WakeupSourceType>
      <WakeupParameter>0</WakeupParameter>
    </WAKEUP_SOURCE>
  </WAKEUP_SOURCE_LIST>
</CONFIG>
WakeupSourceType
The event: CAN0, CAN1, MOVEMENT, ALARM_AFTER_SLEEP, ALARM_ONCE or ALARM_SCHEDULE. Required in each WAKEUP_SOURCE. No default.
WakeupParameter
The value for an alarm wake-up, in seconds. 0 for the other sources. Required in each WAKEUP_SOURCE. Unsigned int.
Wake-up sources by model
Source Models
CAN0 All REXGEN models
CAN1 Models with a second CAN channel: REXGEN 2, REXGEN 2 IMU GNSS, REXGEN Air, REXGEN Pro
MOVEMENT REXGEN 2 IMU GNSS, REXGEN Air, REXGEN Pro
ALARM_AFTER_SLEEP, ALARM_ONCE, ALARM_SCHEDULE Not confirmed for any model
Sleep settings and wake-up sources REXGEN XML · SLEEP AND WAKE Sleep settings and wake-up sources Logging resting state SleepMode NO_SLEEP: stays in Logging No message for CANReceiveTimeout seconds (CONFIG), or no bus activity for SleepNoActivityTime seconds on a CANINTERFACE: it sleeps in the mode SleepMode and SleepOption set Normal sleep NORMAL_SLEEP Deep sleep DEEP_SLEEP wake wake Wakes on each WAKEUP_SOURCE in WAKEUP_SOURCE_LIST CAN0 traffic on CAN 0: every REXGEN model CAN1 traffic on CAN 1: REXGEN 2, REXGEN 2 IMU GNSS, REXGEN Air, REXGEN Pro MOVEMENT REXGEN 2 IMU GNSS, REXGEN Air, REXGEN Pro ALARM_AFTER_SLEEP, ALARM_ONCE, ALARM_SCHEDULE alarm wake-ups, WakeupParameter in seconds: not confirmed for any model WakeUpOption WAKE_UP on a CANINTERFACE also lets traffic on that port wake the logger. confirmed on the models named not confirmed An empty WAKEUP_SOURCE_LIST means no wake-up sources. Which sources wake each sleep mode, and the sleep currents, are in the REXDESK sleep and wake settings guide.

For the same settings in REXDESK, with the sleep current figures, see REXDESK: sleep and wake settings.

Encryption and device locking

Three elements work together. EncryptDataLog enables log encryption, which changes the file type from RXD to RXE. LockDevice blocks USB access to the logger. EncryptType and EncryptKey carry the scheme and its key.

What each model offers differs. REXGEN 1 and REXGEN 2 list AES log encryption with RSA device locking. REXGEN Air lists SHA with device locking. Log encryption is a licensed feature, available on request. Set it up in REXDESK rather than writing the key by hand. See REXDESK: activate a licence and encrypt logs.

Common mistakes

  • Reusing a GUID from another file. Generate a new one each time.
  • Setting WakeupSourceType to false. It is not an allowed value. Name a source.
  • Adding CAN1 or MOVEMENT on a model that lacks the second channel or the IMU. The file still validates, but the source never fires.

Next: REXGEN XML reference: cloud upload and mobile settings.

Products in this guide

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.