3,261
edits
Changes
no edit summary
Making positive changes to driving behavior is an important step in cutting the automotive accidents and wasted fuel during trip. FMB Blue-tooth application will help to monitor driver behavior and receive notifications about possible violations in real time!
Making positive changes to driving behavior is an important step in cutting automotive accidents and wasted fuel during the trip. FMB Blue-tooth application will help to monitor driver behavior and receive notifications about possible violations in real-time!
[[Image:Google-play.png|150px|link=https://play.google.com/store/apps/details?id=com.teltonika.btapp&hl=en]]
[[Image:Google-play.png|150px|link=https://play.google.com/store/apps/details?id=com.teltonika.btapp&hl=en]]
===FMB device nastviti settings===
===FMB device nastviti settings===
----
----
For application to work and detect settings correctly – FMB must be configured correctly. Driver is notified about the event as soon as it is being detected in the device. So the driver may adjust his driving behavior accordingly. Application has not only the visual display of event, but also sound notification, so the phone screen may be even off. Events are generated according FMB device configuration, so make sure ECO Driving, Idling detection, Overspeeding and High RPM features and events are enabled. ''NOTE: High RPM event is available from FMB001/FM3001, FMB1 series devices with connected LV-CAN200, ALL-CAN300 adapter or FMB1/FMB9/FMB2/FMT100 series devices with connected OBDII Dongle''.
For application to work and detect settings correctly – FMB must be configured correctly. The driver is notified about the event as soon as it is being detected in the device. So the driver may adjust his driving behavior accordingly. The application has not only the visual display of the event but also a sound notification, so the phone screen may be even off. Events are generated according to FMB device configuration, so make sure ECO Driving, Idling detection, Overspeeding, and High RPM features and events are enabled. ''NOTE: High RPM event is available from FMB001/FM3001, FMB1 series devices with connected LV-CAN200, ALL-CAN300 adapter, or FMB1/FMB9/FMB2/FMT100 series devices with connected OBDII Dongle''.
<br /><br />
<br /><br />
#::Mode must be configured as Continuous.
#::Mode must be configured as Continuous.
#::Depending on your requirements you can adjust trip start speed and Ignition OFF Timeout.
#::Depending on your requirements you can adjust trip start speed and Ignition OFF Timeout.
#::Eco score Allowed Events describe how many events are tolerated during trip of 100 kilometers
#::Eco score Allowed Events to describe how many events are tolerated during a trip of 100 kilometers
#[[FMB120 Bluetooth settings|'''Blue-tooth''']] – <span style="color:red">Mandatory</span>. Blue-tooth must be enabled.
#[[FMB120 Bluetooth settings|'''Blue-tooth''']] – <span style="color:red">Mandatory</span>. Blue-tooth must be enabled.
[[Image:BTAPP_home.png|right|200px]]
[[Image:BTAPP_home.png|right|200px]]
*You must connect to FMB device by clicking Blue-tooth icon, and selecting your FMB device.
*You must connect to the FMB device by clicking Blue-tooth icon, and selecting your FMB device.
*Each event which was detected by FMB device will be displayed in the application as well. User can be notified visually, event icon will turn yellow and event count will be increased accordingly, and by sound alert as well (can be optionally enabled in application settings).
*Each event that was detected by the FMB device will be displayed in the application as well. Users can be notified visually, event icon will turn yellow and event count will be increased accordingly, and by sound alert as well (can be optionally enabled in application settings).
*Eco score is calculated by FMB device depending on total event amount and trip distance.
*Eco score is calculated by FMB device depending on total event amount and trip distance.
*Eco score, distance and duration is being updated periodically automatically.
*Eco score, distance, and duration is being updated periodically automatically.
*Trip status can be Ongoing and Finished. Trip finish is decided by FMB configuration.If application will be connected to FMB device during ongoing trip – application will update event count, score, distance and trip duration for ongoing trip.
*Trip status can be Ongoing and Finished. The trip finish is decided by FMB configuration. If the application will be connected to FMB device during ongoing trip – the application will update event count, score, distance, and trip duration for ongoing trip.
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
====Trip Type====
====Trip Type====
[[Image:Btapp-triptype-1.gif|right|200px]]
[[Image:Btapp-triptype-1.gif|right|200px]]
In trip type menu you can make:
In the trip type menu you can make:
*You can select trip type for each of your ongoing trips.
*You can select trip type for each of your ongoing trips.
*You can change trip type as many times during trip as you will need. Only last trip type before trip is finished will be recorded and sent to the server.
*You can change the trip type as many times during the trip as you will need. Only the last trip type before the trip is finished will be recorded and sent to the server.
*You can select default trip type for your trips by performing long press on the icon and confirming the change.
*You can select default trip type for your trips by performing a long press on the icon and confirming the change.
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
====History====
====History====
[[Image:BTAPP_history.png|right|200px]]
[[Image:BTAPP_history.png|right|200px]]
In history view you can view all recorded trips. If trip has was completed with application still communicating with FMB device – in history it will be marked by blue line. If device disconnected during trip from the FMB for long period of time– line will be yellow. Usual cases for trip disconnection could be leaving vehicle before trip was completed by FMB configuration. It can be adjusted by Trip parameter Ignition OFF timeout in FMB configuration.
In the history view, you can view all recorded trips. If the trip has was completed with the application still communicating with FMB device – in history it will be marked by the blue line. If the device disconnected during a trip from the FMB for a long period of the timeline will be yellow. Usual cases for trip disconnection could be leaving the vehicle before the trip was completed by FMB configuration. It can be adjusted by Trip parameter Ignition OFF timeout in FMB configuration.
[[Category:Fleet management]]
