BTAPP Mobile application

From Wiki Knowledge Base | Teltonika GPS
Main Page > EOL Products > BTAPP Mobile application

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!

Google-play.png

FMB device nativity settings


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.

Recommended FMB parameters

Fmb120 trip settings.png
BTAPP BT.png
  1. Green DrivingOptional. If enabled in Features menu – it will generate harsh acceleration, harsh breaking and harsh cornering events. Depending on required sensitivity – you can adjust acceleration, braking and cornering coefficients (smaller – more sensitive)
  2. Over speedingOptional. If enabled in Features menu – it will generate over speeding events when vehicle speed will exceed configured threshold.
  3. Excessive idlingOptional. If enabled in Accelerometer Features menu – it will generate excessive idling events when vehicle speed will exceed configured threshold.Eventual records must be enabled.
  4. RPMOptional. If enabled in I/O menu it will generate excessive idling events when vehicle speed will exceed configured threshold.
    Notice: RPM can be obtained from OBD or using LVCAN. You should use only one. Otherwise you will get 2 events simultaneously.
  5. TripMandatory. Trip scenario must be enabled.
    Eventual records must be enabled.
    Mode must be configured as Continuous.
    Depending on your requirements you can adjust trip start speed and Ignition OFF Timeout.
    Eco score Allowed Events to describe how many events are tolerated during a trip of 100 kilometers
  6. Blue-toothMandatory. Blue-tooth must be enabled.






BTAPP interface



Eco Driving

BTAPP home.png
  • You must connect to the FMB device by clicking Blue-tooth icon, and selecting your FMB device.
  • 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, distance, and duration is being updated periodically automatically.
  • 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 an ongoing trip – the application will update event count, score, distance, and trip duration for an ongoing trip.














Trip Type

Btapp-triptype-1.gif

In the trip type menu you can make:

  • You can select trip type for each of your ongoing trips.
  • 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 a long press on the icon and confirming the change.


















History

BTAPP history.png

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.