REXGEN 1REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProDeveloper
REXGEN XML reference: device settings (CONFIG)
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. Use10. Required. Unsigned int. SleepMode- Whether and how the logger sleeps:
NO_SLEEP,NORMAL_SLEEPorDEEP_SLEEP. Each model's product page lists its sleep currents. Required. DefaultNO_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_EncryptionorRSA. Optional. DefaultNo_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. Defaultfalse. EncryptDataLog- Encrypts every log when
true. The files are then RXE instead of RXD. Optional. Boolean. Defaultfalse. 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_ONCEorALARM_SCHEDULE. Required in eachWAKEUP_SOURCE. No default. WakeupParameter- The value for an alarm wake-up, in seconds.
0for the other sources. Required in eachWAKEUP_SOURCE. Unsigned int.
| 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 |
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
GUIDfrom another file. Generate a new one each time. - Setting
WakeupSourceTypetofalse. It is not an allowed value. Name a source. - Adding
CAN1orMOVEMENTon 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
Still stuck?
Our engineers answer support questions on every Influx Technology product.