Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cms:units:sensors:props [04/07/2018 13:03]
tagr zark
cms:units:sensors:props [04/10/2018 05:31] (current)
tagr WH-415
Line 2: Line 2:
 ====== Sensor Properties ====== ====== Sensor Properties ======
  
-When creating, editing or copying a sensor, an additional dialog with sensor ​properties is displayed. It consists of several tabs. In the first one, the basic properties are adjusted: ​+When creating, editing or copying a sensor, an additional dialog with its properties is displayed. It consists of several tabs. In the first one, the basic properties are adjusted: ​
  
 {{ :​units:​sensor.png?​nolink }} {{ :​units:​sensor.png?​nolink }}
Line 10: Line 10:
 **Sensor type**\\ Choose the [[types|sensor type]] to form the dropdown list of available types. **Sensor type**\\ Choose the [[types|sensor type]] to form the dropdown list of available types.
  
-**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 ​should ​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, each kind of sensor ​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 ​should ​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, //​Unknown// ​is displayed. If disabled, the //last known// values are displayed even if they appear invalid (regardless of their relevance).  ​ 
 + 
 +**Do not show unit location**\\ 
 +This option is relevant for the [[cms/​units/​sensors/​types#​digital|digital sensor]] of the //Private mode// type. Its activation allows to hide the information about unit’s location in the monitoring panel, on the map, in reports, tracks, etc. in case a private mode trip is detected. Next to the caption of such a unit, on the [[user/​monitor/​display|map]] and in the monitoring panel, the icon {{:​icons:​private_mode.png?​nolink}} is displayed and the last known location is shown instead of the current one.\\ :!: When using this option, it is recommended to enable the display of the [[user/​monitor/​display#​other_markings|unit’s caption]] on the map.
  
 **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 27:
 [[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 the 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 +∞;
-  * If you add an interval that intersects with an existing one and goes beyond its boundaries, the added interval ​will overwrite ​the existing interval; +  * If you add an interval that intersects with an existing one and goes beyond its boundaries, the added interval ​overwrites ​the existing interval; 
-  * If you add an interval that intersects with an existing one and does not exceed its boundaries, the added interval ​will be inserted inside the existing one. In addition, both the intervals to which the existing one was divided ​will receive ​its text and color;+  * If you add an interval that intersects with an existing one and does not exceed its boundaries, the added interval ​is inserted inside the existing one. In addition, both the intervals to which the existing one was divided ​receives ​its text and color;
   * You can select a color from a color picker or indicate its text value (in HEX) in the corresponding field.   * You can select a color from a color picker or indicate its text value (in HEX) in the corresponding field.
  
-Upon completion, all the set intervals of a chosen ​color along with their text info are shown on the scale. Each interval of the scale, its color, and text can be edited. To do so, click the corresponding interval on the scale and set the necessary parameters. To delete all the set intervals from the scale, click the //Delete// button to the right of it.+Upon completion, all the set intervals of a selected ​color along with their text info are shown on the scale. Each interval of the scale, its color, and text can be edited. To do so, click the corresponding interval on the scale and set the necessary parameters. To delete all the set intervals from the scale, click the //Delete// button to the right of it.
  
 {{ :​units:​intervals_scale.png?​nolink }} {{ :​units:​intervals_scale.png?​nolink }}
  
-To enter intervals, select colors and specify text values, an alternative interface is also provided ​in the form of a table. To switch to the table view, click the corresponding icon to the right of the scale. Click the same button to switch back to the scale. Note that the scale is automatically switched to the table view if more than 10 intervals were created.+To enter intervals, select colors and specify text values, an alternative interface is also provided in the form of a table. To switch to the table view, click the corresponding icon to the right of the scale. Click the same button to switch back to the scale. Note that it is automatically switched to the table view if more than 10 intervals were created.
  
 {{ :​units:​intervals_table.png?​nolink }} {{ :​units:​intervals_table.png?​nolink }}
  
-:!: If a sensor sends values smaller than ones indicated in the first interval, such values are considered ​to be a part of the first interval.+:!: If a sensor sends values smaller than the ones indicated in the first interval, such values are considered ​as a part of the first interval.
  
 Created intervals can be used in several cases: Created intervals can be used in several cases:
Line 63: Line 66:
  
 **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 specified ​for the fuel level sensors. ​The degree ​of the filtration ​is usually adjusted ​in the [[cms/​units/​fuel|]] tab. However, in some cases each sensor needs to be set up individually ​and 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 specified ​for sensors of driver/​trailer binding. If the option is activated, the driver bound to the unit can be unbound from it automatically ​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 ​results ​in the removal of all drivers assigned to this unit. The same is for the trailers.
  
 **Unbinding code**\\ **Unbinding code**\\
-This property is also applicable to the drivers/​trailers binding sensors. Any code can be entered in the Unbinding code field. If the code is specified, the driver/​trailer unbinding is carried out both when the empty value is received, and when the code is received.+This property is also applicable to the drivers/​trailers binding sensors. Any code can be entered in the //Unbinding code// field. If the code is specified, the driver/​trailer unbinding is carried out both when the empty value is received, and when the code is received.
  
 **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 the 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 the calculation tableas it is 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 the engine ignition sensor and the custom digital sensor. Indicate ​the 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 time indicated by you, then the time interval at which the timeout has been exceeded ​is considered invalid, and the remaining time is 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 ​are 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 had 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 86: Line 89:
  
 **With overflow**\\ **With overflow**\\
-This option is available for the sensorsthat can be influenced by occasional resets (mileage sensor, absolute engine hours, absolute fuel consumption sensor). When this option is enabled, the system uses the following algorithm. The value from the latest message is compared to the previous one. If the value is greater than the previous one, their difference is added to the previous value. If it is less, the value from the latest message is added. ​Therefore, ​this function guarantees receiving ​correct mileage data.+This option is available for the sensors that can be influenced by occasional resets (mileage sensor, absolute engine hours, absolute fuel consumption sensor). When this option is enabled, the system uses the following algorithm. The value from the latest message is compared to the previous one. If the value is greater than the previous one, their difference is added to the previous value. If it is less, the value from the latest message is added. ​In this way, it is possible to ensure that correct mileage data is obtained.
  
 **Text parameters**\\ **Text parameters**\\
-This option is available only for the custom sensors. It should be activated if 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 the 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