REXGEN 1REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProDeveloper

REXGEN XML reference: digital outputs, LEDs and sensor set-up

Updated

Drive the logger's digital outputs, choose what its LEDs show and set how the IMU is mounted. This guide covers the output and sensor setup blocks of the XML configuration.

About this guide

The schema, ReXConfig.xsd revision 1.1, defines the output and sensor setup blocks in this guide.

Each block takes a UID attribute (required and unique in the file) and the optional Version, X and Y. It sits inside BLOCKS in a list named after it, for example LED_LIST. Each entry gives the meaning, then whether the schema requires the element and its type.

Digital outputs (DIGITAL_OUTPUT_LIST)

The product pages list two digital inputs or outputs and a relay driver on REXGEN Air. They list two digital channels on REXGEN Pro, one of them PWM-capable.

DIGITAL_OUTPUT

This output switches on while the value from block 40, for example a trigger, is active.

<DIGITAL_OUTPUT UID="50">
  <PhysicalNumber>0</PhysicalNumber>
  <InputUID>40</InputUID>
  <DigitalType>DIGITAL</DigitalType>
  <ActiveState>HI</ActiveState>
  <PWMFrequency>0</PWMFrequency>
</DIGITAL_OUTPUT>
PhysicalNumber
The output channel, counted from 0. Required. Unsigned byte.
InputUID
UID of the block whose value drives the output. Required. Unsigned short.
DigitalType
DIGITAL for on and off, PWM for a pulse-width output. The type also allows FREQUENCY and IMPULSE. Required.
ActiveState
The output level when active: HI or LOW. Required.
PWMFrequency
PWM frequency in Hz. 0 when not used. Required. Unsigned int.

For the electrical limits and wiring of each output, see each model's pinouts guide, such as REXGEN Air: pinouts, harnesses, LEDs and installation.

Status LEDs (LED_LIST)

LED

An LED block takes over one of the logger's LEDs and sets its pattern from two inputs. This one blinks fast while trigger 40 is active and returns to slow blinking when block 41 deactivates it.

<LED UID="51">
  <PhysicalNumber>0</PhysicalNumber>
  <AssignOption>MODEL</AssignOption>
  <InputUIDActive>40</InputUIDActive>
  <InputUIDDeactive>41</InputUIDDeactive>
  <WhenActive>FAST</WhenActive>
  <WhenDeactive>SLOW</WhenDeactive>
  <WhenNotActive>NORMAL</WhenNotActive>
  <ActiveTimeout>0</ActiveTimeout>
  <DeactiveTimeout>0</DeactiveTimeout>
</LED>
PhysicalNumber
Which LED. Required. Unsigned byte.
AssignOption
DEFAULT keeps the LED's standard meaning. MODEL uses the meaning set in this block. Required.
InputUIDActive, InputUIDDeactive
UIDs of the blocks that switch the LED to its active and deactivated states. Required. Unsigned short.
WhenActive, WhenDeactive, WhenNotActive
The pattern in each state: OFF, ON, NORMAL, FAST or SLOW. Required.
ActiveTimeout, DeactiveTimeout
How long each state lasts, in milliseconds. Required. Unsigned int.
How the status LEDs behave REXGEN · LED STATES How the status LEDs behave State Light over time What you see Off Dark Solid On without a break Slow blink On and off at a slow, steady rate Fast blink On and off rapidly Alternating A B Two LEDs light in turn LED on LED off Timing is not to scale. The LED table in each product guide says what each state means on that logger.

Each model's pinouts guide lists what its LEDs mean by default.

IMU mounting (IMU_CONFIGURATION_LIST)

IMU_CONFIGURATION

This block tells the logger how its IMU is oriented in the vehicle. Motion and dead reckoning values then come out in the vehicle's axes.

<IMU_CONFIGURATION UID="52">
  <PhysicalNumber>0</PhysicalNumber>
  <CoordinationFrame>FLU</CoordinationFrame>
  <IMUXPlusFace>FRONT</IMUXPlusFace>
  <IMUZPlusFace>TOP</IMUZPlusFace>
  <UseManualOffset>false</UseManualOffset>
  <PitchManualOffset>0</PitchManualOffset>
  <RollManualOffset>0</RollManualOffset>
  <YawManualOffset>0</YawManualOffset>
  <UseManualGyroBiasCompensation>false</UseManualGyroBiasCompensation>
</IMU_CONFIGURATION>
PhysicalNumber
The IMU. Use 0 for the internal one. Required. Unsigned byte.
CoordinationFrame
Axis convention: FLU (forward, left, up) or FRD (forward, right, down). Optional.
IMUXPlusFace, IMUZPlusFace
Which face of the enclosure the IMU's +X and +Z axes point through: DEFAULT, FRONT, BACK, TOP, BOTTOM, LEFT or RIGHT. Optional. Default DEFAULT.
UseManualOffset, PitchManualOffset, RollManualOffset, YawManualOffset
Fixed angle corrections in degrees, applied when UseManualOffset is true. Optional. Default false and 0.
UseManualGyroBiasCompensation, GyroXBias, GyroYBias, GyroZBias
Fixed gyroscope bias corrections, applied when compensation is enabled. Optional. Default false and 0.

The mounting angles for dead reckoning sit in the GNSSINTERFACE. These guides cover them:

Orientation angles (ORIENTATION_LIST)

ORIENTATION

This block makes one orientation angle, computed from the IMU, available to other blocks to record or send.

<ORIENTATION UID="53">
  <PhysicalNumber>0</PhysicalNumber>
  <Angle>PITCH</Angle>
  <CalculationMethod>DEFAULT</CalculationMethod>
  <SamplingRate>100</SamplingRate>
</ORIENTATION>
Angle
PITCH, ROLL or YAW. Required.
CalculationMethod
DEFAULT is the only value. Required.
PhysicalNumber
The IMU. Use 0 for the internal one. Required. Unsigned byte. Default 0.
SamplingRate
Sampling period in milliseconds. Required. Unsigned short.

Thermocouple channels (TC_LIST)

TC

This block describes one thermocouple channel. No REXGEN product page lists thermocouple inputs. Thermocouples normally connect through a K-TC module on CAN.

<TC UID="54">
  <PhysicalNumber>0</PhysicalNumber>
  <Type>K</Type>
  <Mode>Normal</Mode>
  <Rate>1000</Rate>
  <ParA>1</ParA>
  <ParB>0</ParB>
</TC>
PhysicalNumber
The channel, counted from 0. Required. Unsigned byte.
Type
Thermocouple type: B, E, J, K, N, R, S or T. Optional. Default K.
Mode
Normal, NoCJC (no cold-junction compensation), OnlyCJC, NoCalibration or RAW. Optional. Default Normal.
Rate
Sampling period in milliseconds. Optional. Unsigned short. Default 1000.
ParA, ParB
Factor and offset applied to the value. Optional. Float. Default 1 and 0.

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.