Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
cms:units:sensors:props [04/07/2018 13:03]
tagr zark
cms:units:sensors:props [24/09/2018 12:08] (current)
tagr
Line 12: Line 12:
 **Measurement system**\\ In the dropdown list, choose a [[:​cms/​convers/​convers|measurement system]] in which the sensor values will be received. This property and the corresponding dropdown list are only displayed for those sensors whose units of measurement differ depending on the selected system of measures. **Measurement system**\\ In the dropdown list, choose a [[:​cms/​convers/​convers|measurement system]] in which the sensor values will be received. This property and the corresponding dropdown list are only displayed for those sensors whose units of measurement differ depending on the selected system of measures.
  
-**Metrics**\\ Metrics is presented in reports (also in chart legends), tasks, tooltips etc. As a rule, every kind of sensors has its own default metrics (units of measurement). For some sensor types, units of measurement cannot be changed, for others you can do it manually. This is particularly applicable for digital sensors such as engine operation sensor or custom digital sensors. Instead of default On/Off values you can set //​Activated/​Deactivated//,​ //​Laden/​Unladen//,​ //​Open/​Closed//,​ etc.+**Metrics**\\ Metrics is presented in reports (also in chart legends), tasks, tooltips etc. As a rule, every kind of sensors has its own default metrics (units of measurement). For some sensor types, units of measurement cannot be changed, for othersyou can do it manually. This is particularly applicable for digital sensors such as engine operation sensor or custom digital sensors. Instead of default On/Off values you can set //​Activated/​Deactivated//,​ //​Laden/​Unladen//,​ //​Open/​Closed//,​ etc.
  
 **Parameter**\\ Select or enter the [[param|parameter(s)]] whose data the sensor will interpret. **Parameter**\\ Select or enter the [[param|parameter(s)]] whose data the sensor will interpret.
  
 **Last message only**\\ **Last message only**\\
-This checkbox affects sensor value in the unit tooltip and similar places. If enabled, the value of the sensor is calculated only from the most recent message, and in case when no required parameters are present in the last message, there are marked as //​Unknown//​. If disabled, the //last known// values are displayed even if they appear invalid (no matter how up-to-date they are).  ​+This checkbox affects sensor value in the unit tooltip and similar places. If enabled, the value of the sensor is calculated only from the most recent message, and in the case when no required parameters are present in the last message, there are marked as //​Unknown//​. If disabled, the //last known// values are displayed even if they appear invalid (no matter how up-to-date they are).  ​
  
 **Description**\\ This field is optional. It is displayed only in the list of sensors in the unit properties dialog. **Description**\\ This field is optional. It is displayed only in the list of sensors in the unit properties dialog.
Line 24: Line 24:
 [[validation|Validation]] is optional. It determines the interdependence of sensors from each other. ​ [[validation|Validation]] is optional. It determines the interdependence of sensors from each other. ​
  
-Next, you need to set the calculation table for the sensor. It is especially needed for analogue ​sensors. Not all sensors send ready-made values that can be put into a report and understood by the end user. If the possibility to transform parameters is not provided with a device itself, this transformation is adjusted with the help of the [[calc|]] or the [[:​cms/​units/​sensors/​calc#​calculation_table_wizard|Calculation Table Wizard]]. ​+Next, you need to set the calculation table for the sensor. It is especially needed for analog ​sensors. Not all sensors send ready-made values that can be put into a report and understood by the end user. If the possibility to transform parameters is not provided with a device itself, this transformation is adjusted with the help of the [[calc|]] or the [[:​cms/​units/​sensors/​calc#​calculation_table_wizard|Calculation Table Wizard]]. ​
  
 ===== Intervals and colors ===== ===== Intervals and colors =====
  
-Wialon system provides a possibility to differentiate sensor values by color. For this purpose in sensor properties it is possible to create intervals of values and choose their colors. There is also a possibility to accompany received digital values with text. +Wialon system provides a possibility to differentiate sensor values by color. For this purpose in sensor propertiesit is possible to create intervals of values and choose their colors. There is also a possibility to accompany received digital values with text. 
  
-By default any sensor values (from -∞ to +∞) are displayed in black. Click the {{:​icons:​add.png?​nolink}} button next to the scale to set the interval, select a color for it, and enter text. Note that values are set for each interval individually. Here are some peculiarities of setting intervals and choosing their color that could be useful:+By defaultany sensor values (from -∞ to +∞) are displayed in black. Click the {{:​icons:​add.png?​nolink}} button next to the scale to set the interval, select a color for it, and enter text. Note that values are set for each interval individually. Here are some peculiarities of setting intervals and choosing their color that could be useful:
  
   * No value in the first field corresponds to -∞, in the second — to +∞;   * No value in the first field corresponds to -∞, in the second — to +∞;
Line 63: Line 63:
  
 **Redefine filtration level**\\ **Redefine filtration level**\\
-This property is specific for fuel level sensors. Filtration degree is usually adjusted on the [[cms/​units/​fuel|]] tab. However, in some cases each sensor needs to be set up individually. This provides ​gives such possibility. ​+This property is specific for fuel level sensors. Filtration degree is usually adjusted on the [[cms/​units/​fuel|]] tab. However, in some cases each sensor needs to be set up individually. This option ​provides such possibility. ​
  
 **Filtration level**\\ **Filtration level**\\
-The possibility of indicating filtration level is applicable to the following sensors: temperature sensor, engine revs sensor, voltage sensor, accelerometer,​ custom sensor, weight sensor. This option allows to apply smoothing algorithm to the sensor values. It is necessary to indicate the level of such smoothing (from 0 to 255) in the corresponding field. The filtration level is indicated individually for the sensors of such type. :!: The filtration level is only taken into account in reports (in tables and in charts while drawing smoothed lines).+The possibility of indicating filtration level is applicable to the following sensors: temperature sensor, engine revs sensor, voltage sensor, accelerometer,​ custom sensor, weight sensor. This option allows to apply the smoothing algorithm to the sensor values. It is necessary to indicate the level of such smoothing (from 0 to 255) in the corresponding field. The filtration level is indicated individually for the sensors of such type. :!: The filtration level is only taken into account in reports (in tables and in charts while drawing smoothed lines).
  
 **Validate unbinding**\\ ​ **Validate unbinding**\\ ​
-This property is specific for sensors of driver/​trailer binding. If the option is activated, the driver bound to the unit can be automatically unbound from it only if empty value comes from the same parameter which was used to bind the driver. Otherwise, the removal of the driver based on any parameter will result in the removal of all drivers assigned to this unit. The same works for the trailers as well.+This property is specific for sensors of driver/​trailer binding. If the option is activated, the driver bound to the unit can be automatically unbound from it only if the empty value comes from the same parameter which was used to bind the driver. Otherwise, the removal of the driver based on any parameter will result in the removal of all drivers assigned to this unit. The same works for the trailers as well.
  
 **Unbinding code**\\ **Unbinding code**\\
Line 75: Line 75:
  
 **Overflow by raw data**\\ ​ **Overflow by raw data**\\ ​
-This option appears only for differential counter sensors with overflow. If it is activated, raw data is analyzed first, and then the calculation table is applied. It means that raw data (and not data processed with calculation table as in case when the option is disabled) is taken to estimate overflow.+This option appears only for differential counter sensors with overflow. If it is activated, raw data is analyzed first, and then the calculation table is applied. It means that raw data (and not data processed with calculation table as in the case when the option is disabled) is taken to estimate overflow.
  
 **Timeout**\\ **Timeout**\\
-This property is a specific feature for engine ignition sensor and custom digital sensor. Indicate time value (in seconds). If nothing is indicated in the field or 0 is entered, the option is considered to be disabled. If time between messages exceeds the one indicated by you, then the period of time on which the timeout has been exceeded will be considered invalid, and the remaining time will be divided into intervals (before and after the invalid time period). In other words, the last message before, and the first message after the invalid time period will be considered the end of the first and the beginning of the second interval, correspondingly.+This property is a specific feature for engine ignition sensor and custom digital sensor. Indicate time value (in seconds). If nothing is indicated in the field or 0 is entered, the option is considered to be disabled. If the time between messages exceeds the one indicated by you, then the period of time on which the timeout has been exceeded will be considered invalid, and the remaining time will be divided into intervals (before and after the invalid time period). In other words, the last message before, and the first message after the invalid time period will be considered the end of the first and the beginning of the second interval, correspondingly.
  
-For example, a custom digital sensor is used and 1 hour timeout has been indicated. The following data comes from the digital sensor: 1 (22:00), 1 (22:10), 1 (07:50), and 1 (08:00). If the timeout property had not been indicated, we would have one continuous interval (from 22:00 to 08:00). But using 1 hour timeout we receive the following situation: there is less than 1 hour between the 1st and 2nd message, so we have the first interval (from 22:00 to 22:10); between the 2nd and 3rd messages more than 1 hour passes, so this data is considered to be an invalid time period (from 22:10 to 07:50); and there is less than hour between the 3rd and 4th message, so we receive the second interval (from 07:50 to 08:00).+For example, a custom digital sensor is used and 1-hour timeout has been indicated. The following data comes from the digital sensor: 1 (22:00), 1 (22:10), 1 (07:50), and 1 (08:00). If the timeout property had not been indicated, we would have one continuous interval (from 22:00 to 08:00). But using 1 hour timeout we receive the following situation: there is less than 1 hour between the 1st and 2nd message, so we have the first interval (from 22:00 to 22:10); between the 2nd and 3rd messages more than 1 hour passes, so this data is considered to be an invalid time period (from 22:10 to 07:50); and there is less than an hour between the 3rd and 4th message, so we receive the second interval (from 07:50 to 08:00).
  
 **Consumption,​ l/h**\\ **Consumption,​ l/h**\\
Line 89: Line 89:
  
 **Text parameters**\\ **Text parameters**\\
-This option is available only for the custom sensors. It should be activated if a sensor sends text parameters instead of numeric. In this case, in the table of intervals and colors you can list these parameters and give them broader descriptions. For example, a device sends parameters //error1//, //error2//, //error3//, etc. In accordance with the documentation for the device, you can specify a decryption for each parameter(i.e. //Power supply disconnected//,​ //Invalid data//, etc.). Besides, you can use special characters like * (asterisk). For example, the values can be entered as //error*// and its text would be simply //Error//.+This option is available only for the custom sensors. It should be activated if a sensor sends text parameters instead of numeric. In this case, in the table of intervals and colorsyou can list these parameters and give them broader descriptions. For example, a device sends parameters //error1//, //error2//, //error3//, etc. In accordance with the documentation for the device, you can specify a decryption for each parameter(i.e. //Power supply disconnected//,​ //Invalid data//, etc.). Besides, you can use special characters like * (asterisk). For example, the values can be entered as //error*// and its text would be simply //Error//.
  
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam