MSP500 Features settings - Revision history

Arnas.Zeb: Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

2023-12-28T13:29:15Z

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

← Older revision		Revision as of 16:29, 28 December 2023
Line 62:		Line 62:
	Over speeding scenario supports multiple speed sources:		Over speeding scenario supports multiple speed sources:
	* GNSS		* GNSS
	* OBDII (~~Bluetooth~~)		* OBDII (Bluetooth®)
	* Pulse counter input (vehicle speed sensor signal on AIN wire)		* Pulse counter input (vehicle speed sensor signal on AIN wire)

Tomas.kriauciunas: /* Over Speeding */

2021-04-13T09:28:24Z

Over Speeding

← Older revision		Revision as of 12:28, 13 April 2021
Line 67:		Line 67:
	Speed source can be chosen in the configurator Features tab inside Over Speeding box.		Speed source can be chosen in the configurator Features tab inside Over Speeding box.

	Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver. If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).		Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver.<br>
	<br />		If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).
			<br>
	In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).		In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).
	<br /><br />		<br /><br />

Tomas.kriauciunas: /* Over Speeding */

2021-04-13T09:26:12Z

Over Speeding

← Older revision		Revision as of 12:26, 13 April 2021
Line 58:		Line 58:

	==Over Speeding==		==Over Speeding==
	[[Image:~~Over_Speeding~~.gif\|{{{general\|size}}}\|right]]		[[Image:MSP500_Over_Speeding.gif\|{{{general\|size}}}\|right]]
	Over speeding scenario functionality has been modified for the MSP500 hardware.<br />		Over speeding scenario functionality has been modified for the MSP500 hardware.<br />
	Over speeding scenario supports multiple speed sources:		Over speeding scenario supports multiple speed sources:

Tomas.kriauciunas at 10:24, 12 April 2021

2021-04-12T10:24:44Z

← Older revision		Revision as of 13:24, 12 April 2021
Line 29:		Line 29:
	<td style="width: 8%; text-align:left">Source</td>		<td style="width: 8%; text-align:left">Source</td>
	<td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>		<td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
	</tr>~~}}}~~		</tr>
	<tr>		<tr>
	<td style="width: 8%; text-align:left">Eco/Green Driving Duration</td>		<td style="width: 8%; text-align:left">Eco/Green Driving Duration</td>

Tomas.kriauciunas at 10:24, 12 April 2021

2021-04-12T10:24:16Z

← Older revision		Revision as of 13:24, 12 April 2021
Line 29:		Line 29:
	<td style="width: 8%; text-align:left">Source</td>		<td style="width: 8%; text-align:left">Source</td>
	<td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>		<td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
	~~</tr>~~
	~~{{{txt_advanced\|<tr>~~
	~~<td style="width: 8%; text-align:left">[[{{{model\|MSP500}}} Features settings#Advanced Eco Driving\|Advanced Eco Driving]]</td>~~
	<td style="width: 8%; text-align:left">When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below.</td>
	</tr>}}}		</tr>}}}
	<tr>		<tr>

Tomas.kriauciunas at 10:22, 12 April 2021

2021-04-12T10:22:11Z

← Older revision		Revision as of 13:22, 12 April 2021
Line 60:		Line 60:
	</table>		</table>

	~~{{{FMT100_eco\|==Advanced Eco Driving==~~
	From 03.25.14.Rev.03 base firmware version new '''[[MSP500_Parameter_list\|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.

	When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[MSP500_AVL_ID\|254]]'''.
	~~<table class="nd-othertables" style="width: 68%;">~~
	~~<tr>~~
	~~<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>~~
	~~<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>~~
	~~</tr>~~
	~~<tr>~~
	~~<td style="width: 8%; text-align:left;">Eco Driving Average</td>~~
	<td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Average will cause records with Eco Driving event Average value to be saved and send to the server.</td>
	~~</tr>~~
	~~<tr>~~
	~~<td style="width: 8%; text-align:left;">Eco Driving Maximum</td>~~
	<td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>
	~~</tr>~~
	~~</table>~~
	~~}}}~~
	~~<br>~~
	~~===Data output===~~
	~~----~~
	Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server (MSP500 must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout\|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>

	~~===Auto calibration===~~
	~~----~~
	~~The auto-calibration process is following:~~

	~~#The vehicle is stopped.~~
	~~#There is a straight road ahead.~~
	~~#Send SMS ''"auto_calibrate:set"'' to the {{{model_2\|FMB}}} device.~~
	~~#Accelerate to >30 km/h for 5 sec.~~
	~~#{{{model_2\|FMB}}} will send a response when calibration is completed successfully.~~

	~~Calibration is saved to internal flash memory, which means it will stay after a reset.~~
	~~To check auto-calibration status send a following short text message to the {{{model_2\|FMB}}} device: ''"auto_calibrate:get"''.~~

	==Over Speeding==		==Over Speeding==

Tomas.kriauciunas at 09:23, 12 April 2021

2021-04-12T09:23:31Z

← Older revision		Revision as of 12:23, 12 April 2021
Line 153:		Line 153:
	#''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when correction coefficient is 1 and [[{{{model\|MSP500}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.		#''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when correction coefficient is 1 and [[{{{model\|MSP500}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.
	#''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.		#''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.

			[[Category:MSP500 Configuration]]

Tomas.kriauciunas at 09:12, 12 April 2021

2021-04-12T09:12:55Z

@@ Line 144: / Line 144: @@
 * {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years.
 }}}
 ==GNSS Fuel Counter==

Tomas.kriauciunas at 09:10, 12 April 2021

2021-04-12T09:10:47Z

← Older revision		Revision as of 12:10, 12 April 2021
Line 108:		Line 108:

	Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver. If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).		Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver. If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).
			<br />
	~~'''Example'''~~
	In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).		In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).
	<br /><br />		<br /><br />

Tomas.kriauciunas: /* Over Speeding */

2021-04-12T09:10:09Z

Over Speeding

← Older revision		Revision as of 12:10, 12 April 2021
Line 98:		Line 98:

	==Over Speeding==		==Over Speeding==
			[[Image:Over_Speeding.gif\|{{{general\|size}}}\|right]]
	[[Image:Over_Speeding.gif\|{{{general\|size}}}\|right]] ~~<br /><br /><br /><br />~~
	Over speeding scenario functionality has been modified for the MSP500 hardware.<br />		Over speeding scenario functionality has been modified for the MSP500 hardware.<br />
	Over speeding scenario supports multiple speed sources:		Over speeding scenario supports multiple speed sources:
Line 112:		Line 111:
	'''Example'''		'''Example'''
	In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).		In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).

	~~<br /><br />~~
	~~<br /><br />~~
	~~<br /><br />~~
	~~<br /><br />~~
	<br /><br />		<br /><br />