| Line 30: |
Line 30: |
| | <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> |
| − | {{{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> |
| | <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td> | | <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td> |
| Line 60: |
Line 56: |
| | </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== |
| | + | [[Image:MSP500_Over_Speeding.gif|{{{general|size}}}|right]] |
| | + | Over speeding scenario functionality has been modified for the MSP500 hardware.<br /> |
| | + | Over speeding scenario supports multiple speed sources: |
| | + | * GNSS |
| | + | * OBDII (Bluetooth®) |
| | + | * Pulse counter input (vehicle speed sensor signal on AIN wire) |
| | | | |
| | + | Speed source can be chosen in the configurator Features tab inside Over Speeding box. |
| | | | |
| − | When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value.
| + | Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver.<br> |
| − | [[Image:Over_Speeding.gif|{{{general|size}}}|left]] <br /><br /><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 /><br />
| + | <br> |
| − | <br /><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)). |
| − | <br /><br />
| |
| − | <br /><br />
| |
| | <br /><br /> | | <br /><br /> |
| | | | |
| Line 140: |
Line 105: |
| | * {{{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. | | * {{{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. |
| | }}} | | }}} |
| − |
| |
| − | {{{immobilizer_feature|==Immobilizer==
| |
| − |
| |
| − | [[Image:Immobilizer.gif|{{{general|size}}}|right]]
| |
| − |
| |
| − | If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in iButton list.<br/>
| |
| − | <br/><br/>
| |
| − | Ignition off timeout parameter is used to set the duration after which authorization is activated, when the ignition is turned off. For example, if Ignition off timeout is set to 30 seconds, when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.
| |
| − |
| |
| − |
| |
| − | From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model|MSP500}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in MSP500 devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model|MSP500}}}_Beacon_List here]'''.
| |
| − |
| |
| − | By using iBeacon authorization, immobilizer feature can be used with devices which doesn't have 1-wire data connection available.
| |
| − | <br/><br/><youtube>gjuiJjAejWU</youtube>}}}
| |
| − |
| |
| − | {{{ibutton_feature|==iButton Read Notification==
| |
| − |
| |
| − | This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.
| |
| − | [[Image:IButton_Read_Notification.gif|{{{general|size}}}|left]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}
| |
| | | | |
| | ==GNSS Fuel Counter== | | ==GNSS Fuel Counter== |
| Line 169: |
Line 115: |
| | #''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. |
| | | | |
| − | {{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
| + | [[Category:MSP500 Configuration]] |
| − | | |
| − | [[Image:DOUT_Control_Via_Ignition.gif|{{{dout_control_via_ignition|size}}}|right]] | |
| − | | |
| − | This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>
| |
| − | | |
| − | Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V.<br/><br/>
| |
| − | | |
| − | <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;">DOUT Control via Ignition Scenario</td>
| |
| − | <td style="width: 8%; text-align:left">Enable/Disable DOUT Control Via Ignition scenario</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td style="width: 8%; text-align:left">DOUT Control</td>
| |
| − | <td style="width: 8%; text-align:left">Scenario controls configured DOUT if ignition timeout exceeds its limit</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td style="width: 8%; text-align:left">DOUT Deactivation Via DIN</td>
| |
| − | <td style="width: 8%; text-align:left">DOUT is turned off if configured DIN is in on (voltage applied) state</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td style="width: 8%; text-align:left">Ignition Off timeout</td>
| |
| − | <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
| |
| − | </tr>
| |
| − | </table>}}}
| |