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 [12/09/2019 17:32]
alse
cms:units:sensors:props [28/11/2019 12:06] (current)
alse [Additional Properties]
Line 17: Line 17:
  
 **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 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).  + 
 +If this option is enabled, the sensor value displayed ​in the unit tooltip and other places is calculated only from the most recent message.  In case there are no required parameters in the last message, //Unknown// is shown. If the option is disabled, the last known value which is calculated within a minute is displayed (regardless of whether it is recent).   ​
  
 **Do not show unit location**\\ **Do not show unit location**\\
Line 93: Line 94:
  
 **With overflow**\\ **With overflow**\\
-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.+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. ​This algorithm ensures ​that the resets are taken into account and correct data is obtained.
  
 **Text parameters**\\ **Text parameters**\\
 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 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 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//.
  
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2020 Gurtam