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:adv [07/06/2018 08:40]
irra [Speeding]
cms:units:adv [24/09/2018 12:50] (current)
tagr
Line 11: Line 11:
  
 **Consumption by rates, l/100 km**\\ **Consumption by rates, l/100 km**\\
-In this field the fuel consumption per 100 km is indicated. To modify it, you need the //Edit trip detector and fuel consumption//​ access right towards the unit. Positive digital values can be introduced here. The default value is 0. +In this fieldthe fuel consumption per 100 km is indicated. To modify it, you need the //Edit trip detector and fuel consumption//​ access right towards the unit. Positive digital values can be introduced here. The default value is 0. 
  
-**Urban speed limit**\\+**Seasonal consumption**\\ 
 +Activate this option to set the seasonal calculation of the fuel consumption rate. Specify the fuel consumption per 100 kilometers (default value is 0) and the period (from — to) when this value should be taken into account. To modify this field, the user needs the //Edit trip detector and fuel consumption//​ access right towards the unit.  
 + 
 +If the //Seasonal consumption//​ option is activated, then when a new [[cms/​units/​sensors/​sensors|sensor]] is created with the help of the [[cms/​units/​sensors/​master|math consumption wizard]], the //Seasonal multiplier//​ option is activated there by default, and the value of the coefficient is counted in accordance with the values specified on the //​Advanced//​ tab. 
 + 
 +**Urban speed limit, km/h**\\
 This setting is used in the report on trips. If the unit goes with the speed under indicated here, it is considered as urban mileage. If the speed is higher, this mileage is regarded as suburban. This property can be used in the [[user/​reports/​tables/​trips|trips reports]], [[user/​reports/​templ/​contents/​statistics/​statistics|statistics]],​ and in the advanced [[user/​reports/​adv/​driver|drivers reports]].  ​ This setting is used in the report on trips. If the unit goes with the speed under indicated here, it is considered as urban mileage. If the speed is higher, this mileage is regarded as suburban. This property can be used in the [[user/​reports/​tables/​trips|trips reports]], [[user/​reports/​templ/​contents/​statistics/​statistics|statistics]],​ and in the advanced [[user/​reports/​adv/​driver|drivers reports]].  ​
  
Line 33: Line 38:
  
 **Use fixed limit**\\ **Use fixed limit**\\
-For the //Use fixed limit// method the maximum speed limit is specified individually for each unit in the field //Fixed speed limit//. Upon receiving messages with the speed higher than the indicated one, the speeding is registered by the system. For this method you can also enter the minimum speeding duration in seconds (1 second by default). The speeding the duration of which is less than the indicated one is not registered by the system as a speeding.+For the //Use fixed limit// method the maximum speed limit is specified individually for each unit in the field //Fixed speed limit//. Upon receiving messages with the speed higher than the indicated one, the speeding is registered by the system. For this methodyou can also enter the minimum speeding duration in seconds (1 second by default). The speeding the duration of which is less than the indicated one is not registered by the system as a speeding.
  
 **Use limits from roads**\\ **Use limits from roads**\\
-According to the method //Use limits from roads//, the registration of a speeding depends on the current speed limitation road signs used on various road sections. In other words, the system contains the data on speed limits for the particular road section, and if a unit exceeds this speed limit while moving by this section, the speeding is registered. For this method you can indicate the tolerance on speeding value. In this case a speeding ​ is considered to be the movement at a speed that is higher than the sum of the values of speed limit and tolerance on speeding. For example, in some countries exceeding the speed limit by 10 km/h is not a violation, that is why you can indicate 10 km/h tolerance on speeding. Therefore, by a road with the speed limit of 60 km/h, the unit can move with a speed of 70 km/h, and this speed will not be considered a speeding. Moreover, here (the same as for the previous method) the minimum speeding duration can be indicated.+According to the method //Use limits from roads//, the registration of a speeding depends on the current speed limitation road signs used on various road sections ​(provided that the road limit is more than 30 km/h). In other words, the system contains the data on speed limits for the particular road section, and if a unit exceeds this speed limit while moving by this section, the speeding is registered. For this methodyou can indicate the tolerance on speeding value. In this casea speeding is considered to be the movement at a speed that is higher than the sum of the values of speed limit and tolerance on speeding. For example, in some countries exceeding the speed limit by 10 km/h is not a violation, that is why you can indicate 10 km/h tolerance on speeding. Therefore, by a road with the speed limit of 60 km/h, the unit can move with a speed of 70 km/h, and this speed will not be considered a speeding. Moreover, here (the same as for the previous method) the minimum speeding duration can be indicated.
  
 :!: If «0» is indicated in the field //Min. speeding time, seconds//, the speeding is registered even if there is only one message with speeding, The duration of such interval in the reports is //​00:​00//​. ​ :!: If «0» is indicated in the field //Min. speeding time, seconds//, the speeding is registered even if there is only one message with speeding, The duration of such interval in the reports is //​00:​00//​. ​
  
-Speedings are registered in the system, and subsequently you can generate a [[user/​reports/​tables/​speedings|speedings report]]. Moreover, during building a track you can enable speeding markers which highlight the corresponding events on the track.+Speedings are registered in the system, and subsequentlyyou can generate a [[user/​reports/​tables/​speedings|speedings report]]. Moreover, during building a track you can enable speeding markers which highlight the corresponding events on the track.
  
 ===== Driver Activity ===== ===== Driver Activity =====
Line 46: Line 51:
 Information on driver activity helps to track whether the driver follows the AETR standards or not. Such information is displayed in the unit or driver [[:​user/​monitor/​extra#​unit_s_tooltip|tooltips]] as well as in the [[:​user/​monitor/​extra#​extended_unit_information|extended unit information]] if the corresponding checkbox is indicated in the //​[[:​user/​set/​general#​general_settings|User Settings]]//​ dialog. Information on driver activity helps to track whether the driver follows the AETR standards or not. Such information is displayed in the unit or driver [[:​user/​monitor/​extra#​unit_s_tooltip|tooltips]] as well as in the [[:​user/​monitor/​extra#​extended_unit_information|extended unit information]] if the corresponding checkbox is indicated in the //​[[:​user/​set/​general#​general_settings|User Settings]]//​ dialog.
  
-This section allows to choose the source for determining driver activity. The dropdown list contains 3 items: //None//, //​Tachograph//,​ and //​Bindings//​. If the //None// item is chosen, the unit or driver tooltipsor the extended unit information do not show the current data on the driver activity. If the //​Tachograph//​ item is chosen, the information on the activity of a driver bound to this unit is received from the tachograph installed in the vehicle. If the //Binding// item is chosen (for example, if a vehicle is not equipped with a tachograph),​ the activity of a driver bound to this unit is determined in the following way:+This section allows to choose the source for determining driver activity. The dropdown list contains 3 items: //None//, //​Tachograph//,​ and //​Bindings//​. If the //None// item is chosen, the unit or driver tooltips or the extended unit information do not show the current data on the driver activity. If the //​Tachograph//​ item is chosen, the information on the activity of a driver bound to this unit is received from the tachograph installed in the vehicle. If the //Binding// item is chosen (for example, if a vehicle is not equipped with a tachograph),​ the activity of a driver bound to this unit is determined in the following way:
  
   * //Driving// status is registered as the driver activity when either trip or stop have been detected for a unit.   * //Driving// status is registered as the driver activity when either trip or stop have been detected for a unit.
Line 59: Line 64:
 ===== Track Colors ===== ===== Track Colors =====
  
-Different colors can be used to show on the map not only the unit itselfbut also its movements (tracks). ​+Different colors can be used to show on the map not only the unit itself but also its movements (tracks). ​
  
 Tracks can be built in the [[user/​tracks/​tracks|Tracks]] panel, [[user/​msg/​msg|]] panel, [[user/​reports/​reports|Reports]] panel, or in the [[user/​monitor/​monitor|Monitoring]] panel (the //Quick track// option). ​ Tracks can be built in the [[user/​tracks/​tracks|Tracks]] panel, [[user/​msg/​msg|]] panel, [[user/​reports/​reports|Reports]] panel, or in the [[user/​monitor/​monitor|Monitoring]] panel (the //Quick track// option). ​
Line 69: Line 74:
  
 **Single**\\ **Single**\\
-This option is designed to color the track in one color, which is convenient, for instancewhen building tracks for unit groups so that they do not visually merge with each other. The color of the track is selected from the palette. :!: When you sequentially build several tracks for one unit, a different color is used for each of them (taken in order from the palette).+This option is designed to color the track in one color, which is convenient, for instance when building tracks for unit groups so that they do not visually merge with each other. The color of the track is selected from the palette. :!: When you sequentially build several tracks for one unit, a different color is used for each of them (taken in order from the palette).
  
 {{ :​units:​adv0.png?​nolink }} {{ :​units:​adv0.png?​nolink }}
  
 **By Speed**\\ **By Speed**\\
-This option is designed to change the color of the track depending on the speed. To set the values for the speed intervals and indicate their colors, click the add interval button ({{:​icons:​add.png?​nolink}}). The track color is set for each interval individually. In other words, it is necessary to set an interval, select the color, and click //OK//. Afterwards, the same procedure should be done for the rest of intervals. Pay attention to some peculiarities of setting intervals and choosing their color:+This option is designed to change the color of the track depending on the speed. To set the values for the speed intervals and indicate their colors, click the add interval button ({{:​icons:​add.png?​nolink}}). The track color is set for each interval individually. In other words, it is necessary to set an interval, select the color, and click //OK//. Afterwards, the same procedure should be done for the rest of the intervals. Pay attention to some peculiarities of setting intervals and choosing their color:
  
   * 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 107: Line 112:
  
 **Allow positioning by cellular base stations**\\ ​ **Allow positioning by cellular base stations**\\ ​
-Positioning by cellular base stations (//LBS detection//​) is an alternative method of defining unit location. This method involves the use of cellular base stations as reference points for the location detection. Note that the method is not as accurate as the use of GPS, and just allows to receive the approximate location. When  ​enabling ​this checkbox, the //LBS detection// is used only if it is newer than the GPS data.+Positioning by cellular base stations (//LBS detection//​) is an alternative method of defining unit location. This method involves the use of cellular base stations as reference points for the location detection. Note that the method is not as accurate as the use of GPS, and just allows to receive the approximate location. When this checkbox ​is enabled, the //LBS detection// is used only if it is newer than the GPS data.
  
-**Skip invalid messages**\\ Some controllers may send a flag about coordinates validity/​invalidity in messages. A message with invalid coordinates is marked by the flag of invalidity, and when sending such a message to the server, the current time and the last valid coordinates are given. Wialon will consider this message as a message without position data, and it will be not used when constructing movement tracks, detecting location in reports, etc. However, if this message contains other parameters (such as sensors), they will be used. +**Skip invalid messages**\\ Some controllers may send a flag about coordinates validity/​invalidity in messages. A message with invalid coordinates is marked by the flag of invalidity, and when sending such a message to the server, the current time and the last valid coordinates are given. Wialon will consider this message as a message without position data, and it will be not used when constructing movement tracks, detecting ​the location in reports, etc. However, if this message contains other parameters (such as sensors), they will be used. 
  
 **Minimum satellites**\\ If the number of satellites locked is lower, the message is considered to be invalid. Some types of equipment can give out the correct coordinates with only two satellites. The recommended value is at least three. **Minimum satellites**\\ If the number of satellites locked is lower, the message is considered to be invalid. Some types of equipment can give out the correct coordinates with only two satellites. The recommended value is at least three.
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam