This shows you the differences between two versions of the page.
Both sides previous revision Previous revision  
user:reports:dat:dat [07/06/2018 11:19] irra [Speed] WH3, WH4, WH5 
user:reports:dat:dat [01/10/2018 13:50] (current) tagr 


Line 6:  Line 6:  
The time of completion/start/end of any state is displayed in the reports in the format specified in the [[user/reports/templ/settings/generalSettings > General]] section of a report template.  The time of completion/start/end of any state is displayed in the reports in the format specified in the [[user/reports/templ/settings/generalSettings > General]] section of a report template.  
  In the tables that include the duration of a state, the hours may not be combined into days (if the interval is longer than 24 hours). It means that instead of //5 days 12:34:56// it is displayed as //132:34:56//. To disable days and leave only hours, select the //hours:minutes:seconds// duration format in the table properties of the report template. This option does not only affect the formatting in the cells, but also the row //Total//. Moreover, the duration may be shown in the format of //hours// (with two decimal places). For instance, //3.45// instead of //3:27//. This is done by means of activating the //hours (with two decimal places)// option.  +  In the tables that include the duration of a state, the hours may not be combined into days (if the interval is longer than 24 hours). It means that instead of //5 days 12:34:56// it is displayed as //132:34:56//. To disable days and leave only hours, select the //hours:minutes:seconds// duration format in the table properties of the report template. This option does not only affect the formatting in the cells, but also the row //Total//. Moreover, the duration may be shown in the format of //hours// (with two decimal places). For instance, //3.45// instead of //3:27//. This is done by means of activating the //hours (with two decimal places)// option. 
If grouping is used, a table receives additional column (//Grouping//) which displays the time in the following way:  If grouping is used, a table receives additional column (//Grouping//) which displays the time in the following way:  
Line 44:  Line 44:  
===== Speed =====  ===== Speed =====  
  The average and maximum speed values can be included in the same reports as the mileage: trips, geofences, rides, speedings, digital sensors. Note that the **average speed** directly depends on the mileage because it is calculated by dividing mileage by duration (for example, distance traveled with a sensor on divided by the duration of an on state. That is why a situation can happen when the average speed is zero and the maximum speed is a positive number. It can happen (1) if the duration of a state is zero (see explanation above); (2) if the mileage is zero (the unit was parked or the mileage counter is set incorrectly); (3) if the mileage is insignificant, for example, //0,01//, and the result of division is smaller than 1. Note that mileage can be calculated either by all messages or by trips only (the option in the [[user/reports/templ/settings/generalsettings]] of a report), and this obviously affects the resulting values of the average speed.  +  The average and maximum speed values can be included in the same reports as the mileage: trips, geofences, rides, speedings, digital sensors. Note that the **average speed** directly depends on the mileage because it is calculated by dividing mileage by duration (for example, distance traveled with a sensor on divided by the duration of an on the state. That is why a situation can happen when the average speed is zero and the maximum speed is a positive number. It can happen (1) if the duration of a state is zero (see explanation above); (2) if the mileage is zero (the unit was parked or the mileage counter is set incorrectly); (3) if the mileage is insignificant, for example, //0,01//, and the result of division is smaller than 1. Note that mileage can be calculated either by all messages or by trips only (the option in the [[user/reports/templ/settings/generalsettings]] of a report), and this obviously affects the resulting values of the average speed. 
The **Maximum speed** has nothing to do with the mileage and any counters. To calculate the maximum speed within an interval, all messages which get to this interval are analyzed and the largest speed value is selected and displayed in the corresponding cell.  The **Maximum speed** has nothing to do with the mileage and any counters. To calculate the maximum speed within an interval, all messages which get to this interval are analyzed and the largest speed value is selected and displayed in the corresponding cell.  
Line 69:  Line 69:  
The consumption by math does not require fuel sensors. The consumption rates and coefficients indicated in the properties of the ignition and engine efficiency sensors are multiplied by time.  The consumption by math does not require fuel sensors. The consumption rates and coefficients indicated in the properties of the ignition and engine efficiency sensors are multiplied by time.  
  In a report template several methods of calculating fuel can be selected simultaneously. In this case a separate column is generated for each method. Moreover, if there are several sensors of the same type, then a separate column is generated for each of them. If you want a certain sensor to be used for the fuel calculation, enter its name mask in the //Sensor masks// filter of the parameters of the table. If in the report template you select columns that do not correspond to the unit's properties, zeros are displayed in the cells of the resulting report.  +  In a report template, several methods of calculating fuel can be selected simultaneously. In this case, a separate column is generated for each method. Moreover, if there are several sensors of the same type, then a separate column is generated for each of them. If you want a certain sensor to be used for the fuel calculation, enter its name mask in the //Sensor masks// filter of the parameters of the table. If in the report template you select columns that do not correspond to the unit's properties, zeros are displayed in the cells of the resulting report. 
In the statistics, there is no possibility to show the information for each sensor separately. In such rows as //Avg consumption ...//, //Consumed by ...//, //Rates deviation ...//, etc. you can get only one value for each type of a fuel sensor (FLS/ImpFCS/AbsFCS/InsFCS). That is why the consumed fuel (//Consumed by ...//) in the statistics is the sum of the sensors of this type, and the average consumption (//Avg consumption ...//) is the arithmetic average of those sensors. However, the calculation of the deviation from rates (//Rates deviation ...//) depends on the adjustments of the sensors. If a unit has two sensors of the same type, the deviation from rates is calculated for each sensor separately, but for the statistics (as it can be only one row) the sum of those deviations is shown. Thus, the formula is:  In the statistics, there is no possibility to show the information for each sensor separately. In such rows as //Avg consumption ...//, //Consumed by ...//, //Rates deviation ...//, etc. you can get only one value for each type of a fuel sensor (FLS/ImpFCS/AbsFCS/InsFCS). That is why the consumed fuel (//Consumed by ...//) in the statistics is the sum of the sensors of this type, and the average consumption (//Avg consumption ...//) is the arithmetic average of those sensors. However, the calculation of the deviation from rates (//Rates deviation ...//) depends on the adjustments of the sensors. If a unit has two sensors of the same type, the deviation from rates is calculated for each sensor separately, but for the statistics (as it can be only one row) the sum of those deviations is shown. Thus, the formula is:  
Line 85:  Line 85:  
==== Consumption Math ====  ==== Consumption Math ====  
  During the mathematical calculation the fuel consumption is computed separately for each pair of messages.  +  During the mathematical calculation, the fuel consumption is computed separately for each pair of messages. 
The following algorithm is used:  The following algorithm is used:  
Line 92:  Line 92:  
 For the operating sensors the values indicated in the //Consumed, l/h// field of their [[cms/units/sensors/typesproperties]] are summed.   For the operating sensors the values indicated in the //Consumed, l/h// field of their [[cms/units/sensors/typesproperties]] are summed.  
 The values of the engine efficiency sensors are calculated.   The values of the engine efficiency sensors are calculated.  
   The received values are summed according to the formula //k1 + (k2  1) + (k3  1) + … + (kn – 1)//. In that way the coefficient is formed. If the sum of the coefficients is less than 0 or invalid, the total coefficient is 1.  +   The received values are summed according to the formula //k1 + (k2  1) + (k3  1) + … + (kn – 1)//. In that way,the coefficient is formed. If the sum of the coefficients is less than 0 or invalid, the total coefficient is 1. 
 To determine the current fuel consumption of the unit, the value from the point 2 is multiplied by the value of the point 4.   To determine the current fuel consumption of the unit, the value from the point 2 is multiplied by the value of the point 4.  
 The value from the previous message till the current one is multiplied by the value from the point 5.   The value from the previous message till the current one is multiplied by the value from the point 5.  
   The consumption for each message pair for the indicated interval is summed and in that way the fuel consumption is determined by the consumption math.  +   The consumption for each message pair for the indicated interval is summed and in that way, the fuel consumption is determined by the consumption math. 
