0
edits
Changes
mLine 37:
Line 37: − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − +
→Garmin protocols
==Garmin protocols==
==Garmin protocols==
The following is a list of protocols supported and the corresponding feature/benefit. FMB125 can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the work of FMB125 and Garmin products. For more information about Garmin products and FMI versions, please go to http://www8.garmin.com/solutions/pnd/supportedproducts.jsp. Notice that some Garmin products use different connection cables than others.
The following is a list of protocols supported and the corresponding feature/benefit. FMB125 can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of FMB125 and Garmin products. For more information about Garmin products and FMI versions, please go to http://www8.garmin.com/solutions/pnd/supportedproducts.jsp. Notice that some Garmin products use different connection cables than others.
===Standard protocols===
===Standard protocols===
Text Message Protocol:
Text Message Protocol:
* Allows text messages sent to device to be displayed in "inbox" on unit;
* Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
* Garmin can provide confirmation that message was read;
* Garmin can provide a confirmation that message was read;
* Garmin can also provide a yes/no box below the text of the message to enable a simple quick response;
* Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
* Messages can be up to 199 characters in length;
* Messages can be up to 199 characters long;
* Messages can also be generated from device and sent to dispatch/office;
* Messages can also be generated from device and sent to dispatcher/office;
* Messages received will be notified to driver through a pop-up alert on Garmin screen;
* Messages received will be notified about to driver through a pop-up alert on Garmin screen;
* Garmin provides a "virtual keyboard" on device through a touch-screen format for all text communication.
* Garmin provides a "virtual keyboard" for text communication.
Stop (Destination) Protocol:
Stop (Destination) Protocol:
* Garmin can display a list of Stops/Jobs reported to the device in a separate icon called "My Stops".
* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";
* Driver has ability to navigate directly to Stop from list.
* Driver has ability to navigate directly to Stop from the list;
* Garmin can provide status on current Stop in progress.
* Garmin can provide status of a current Stop in progress;
* Is driver stopped at location?
* Garmin can indicate whether the driver has stopped at the location;
* How far has Driver progressed through the list of Stops?
* Garmin can inform how far the driver has progressed through the list of Stops;
* Garmin can also provide confirmation that driver has received a particular Stop, read the details, or deleted it from list.
* Garmin can provide confirmation that the driver has received a particular Stop, familiarized oneself with the details or removed it from the list;
* Can provide confirmation that a Stop has been completed.
* Can provide confirmation that a Stop has been reached.
Estimated Time of Arrival Protocol:
Estimated Time of Arrival Protocol:
* Dispatcher/office can request the ETA of the current stop/job in progress.
* Dispatcher/office can request the ETA of the current stop/job in progress.
* Garmin will notify the actual time of arrival as well as distance remaining to stop.
* Garmin can notify about the actual time of arrival as well as the distance remaining to a stop.
Auto-Arrival at Stop Protocol:
Auto-Arrival at Stop Protocol:
* This feature is used to tell the Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if they would like to mark the Stop as done and begin navigating to next Stop on the list.
* This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if one would like to mark the Stop as done and begin navigating to a next Stop on the list.
* Auto-arrival can be determined by how long the unit is stopped close to the destination (in the event driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated.
* Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated.
Data Deletion Protocol:
Data Deletion Protocol:
* Dispatch/office has the ability to wipe clean the data on the Garmin PND.
* Dispatcher/office has the ability to wipe clean the data on Garmin PND.
* Clean up messages in inbox/remove stops.
* It allows to clean messages in inbox and remove stops.
===Enchanced protocols===
===Enhanced protocols===
Canned Responses/Messages:
Canned Responses/Messages:
