This is an old revision of the document!

Table of Contents


On the Sensors tab of Unit Properties dialog, sensors connected to equipment are added and configured as well as edited and removed.

On the list you see each sensor name, its type, parameter, custom description, etc.

To create a new sensor push Add a New Sensor button, fill in the fields and press OK.

To edit an existing sensor or just view its settings, select this sensor and press Modify Sensor.

To quickly create a sensor with similar settings, select this sensor and press Clone Sensor.

To delete a sensor, select this sensor and press Delete Sensor.

If you use similar devices for different units, it is convenient to configure sensors once, and then import them to other units.

There is the Visible checkbox against each sensor. It controls whether sensor is shown or hidden. By default, the checkbox is enabled or disabled depending on sensor type. However, you may want to hide or show some particular sensors. Hiding is reasonable especially if a sensor is used as a validator and does not have its proper meaning.

Sensors' order on the list can be changed manually. To place sensors in a desirable order, just drag them up and down holding on the arrow-shaped icon on the left. Sensors' order and visibility is considered in unit info tip, track player, track hittest, and in the Messages panel. Only visible sensors are shown and they follow in the order as given here, in unit properties dialog.

Sensor Properties

Give a name to the sensor. It must consist of 1 or more symbols. The name will be visible in unit info tip, in reports and messages.

Sensor type
Choose the sensor type form the dropdown list of available types.

Unit of measure
As a rule, possible unit of measure is given. However you can key in your own. This is especially applicable for digital sensors such as engine operation sensor or custom digital sensors. Instead of default On/Off values you can key in Activated/Deactivated, Laden/Unladen, and the like.

Parameters come in messages. If the unit already has messages, parameter name can be picked up from the list of available in the last message.

This field is optional. Add any description and options if needed.

Validator and Validation type
This is optional. Validation defines dependency of sensors from each other.

Then you have to set calculation table for the sensor. It is especially needed for analogue sensors. Not all sensors send ready values that can be put into a report and be intelligible to any user. If the possibility to transform parameters is not provided with device itself, this transformation is adjusted with special calculation table.

Was this helpful?
Thank you!