Teltonika FMB630, Руководство пользователя

Страница: 90 / 173

90

Deceleration (braking) exceeds defined value

Cornering force exceeds defined value
Program continously monitors and process data from accelerometer than decides
whether harsh event is detected or not. If any of three cases are satisfied event is
generated. Record is saved and sent to server (FMB630 must be configured properly).
Event value is multiplied by 10 before sending/saving record to get more precision
when displaying
data *.
Digital output No.1 is activated for a period of time to warn driver. Output on-time
should/can be configured separately for each case.
*Example. If acceleration harsh event of 3.55 m/s2 detected. Record with value 3.55*10 = 35.5
≈ 36 will be saved ant sent to server.
13.2 Overspeeding Scenario
Overspeeding scenario helps to prevent from exceeding fixed speed and inspects driver if
needed. Any DOUT (which is configured) is controlled by scenario for user needs, to manage
buzzer, LED etc. Then DOUT control is enebled and Overspeeding is detected, DOUT becomes
active for 0,3 second every 1 second.
13.2.1 Mounting Requirements and Working Conditions
1. All scenarios on corresponding Digital Output can be enabled at once.
2. Ignition must be on.
3. Device module mounting position doesn’t have any influence for correct scenario
operation.
13.2.2 Configuration
Figure 70 Overspeeding configuration parameters
Overspeeding. Selects which DOUT will control Overspeeding scenario.
Max Allowed Speed. Set speed limit to reach without triggering Overspeeding event.
13.3 Immobilizer/ Authorized Driving Scenario
Immobilizer (iButton list checking disabled) Vehicle can be used only if iButton is
connected. In this scenario iButton list is not used; connect any iButton to pass Immobilizer
security. Selected DOUT is controlled by scenario for user needs.