Fleet Management

FMI Protocol Support

FMI HOS Protocol Support

FMI CAM Protocol Support

Features Supported by Each Protocol

A603 — Mainly Stops Management

• Stop (destination) protocols — Informs the client of a new destination.
• Stop protocol — Sends stops, or destinations, from the server to the client.
• Stop status protocols — Used by the server to request, or change, the status of a stop on the client. The protocol also is used by the client to send the status of a stop to the server whenever the status of a stop changes on the client.
• Estimated Time of Arrival (ETA) protocol — Used by the server to request ETA and destination information from the client.
• Auto-arrival at stop protocol — Used by the server to change the auto-arrival criteria on the client. The auto-arrival feature is used on the client to automatically detect the user has arrived at a stop, and then to prompt the user if they would like to mark the stop as done and start navigating to the next stop in the list.
• Data deletion protocol — Used by the server to delete data on the client.

A604 — Text Message, Canned Message & Response, GPI File Transfer and Sort Stoplist

• Unicode support.
• Server to client open text message — Sends a simple text message from the server to the client.
• Server to client canned response text message — Sends a text message from the server to the client which requires a response to be selected from a list.
• Message status protocol — Notifies the server of the status of a text message previously sent from the server to the client.
• Canned response list protocols — Maintains the list of canned responses used in the server to client canned response text message protocol.
• Set canned response protocol — Sets (adds or updates) a response in the canned response list.
• Delete canned response protocol — Deletes a canned message from the client.
• Refresh canned response text protocol — Initiated by the client to request updated response text for a particular message or for all messages.
• Set canned message protocol — Adds or updates the text of a canned message on the client.
• Delete canned message protocol — Deletes a canned message from the client.
• Refresh canned message list protocol — Initiated by the client when it requires an updated list of canned messages.
• Sort stop list protocol — Sorts all stops in the list so they can be visited in order in the shortest total distance possible, starting from the driver’s current location.
• File transfer protocols — Transfers files from the server to the client and allow the server to obtain information about the files on the client device.
• GPI file transfer protocol — Sends a GPI file from the server to the client.
• GPI file information protocol — Allows the server to determine the size and version of the current Fleet Management GPI file on the device.
• User interface text protocol — Customizes the text of certain Fleet Management user interface elements. Currently, only the “dispatch” text on the device main menu can be changed.

A604 — Deprecated

• Driver status list protocols — Allows the server to maintain (add, update or delete) the list of driver statuses the user may select.
• Client to server driver status update protocol — Notifies the server when the driver changes the driver status via the user interface on the client.
• Set driver status list item protocol — Allows the server to set (add or update) the textual description corresponding to a particular driver status.
• Delete driver status list item protocol — Allows the server to delete (remove) a textual description corresponding to a particular driver status.
• Refresh driver status list protocol — Allows the client to request the complete list of driver statuses from the server.

A605 — Ping and Messaging Query

• Ping (communication link status) protocol — Sends a “ping” to determine whether the communication link is still active.
• Message throttling protocols — Allows the server to enable or disable certain Fleet Management protocols that are normally initiated by the client and determine which protocols are enabled and disabled.
• Message throttling query protocol — Obtains the throttling state of all protocols that may be throttled.

A606 — Mainly FMI Safe Mode

• FMI safe mode protocol — Enables FMI safe mode (henceforth FMISM) and to set the threshold speed at which it will be enforced.

A607 — Waypoint Management and Driver Status

• Message delete protocol — Allows the server to delete text messages stored on the client.
• Client to server open text message protocol — Sends a simple text message from the client to the server.
• Canned message (Quick Message) list protocols — Maintains the list of canned (predefined) text messages that a client device may send to the server using the Quick Message feature.
• Waypoint protocols — Available to create, modify and delete waypoints that appear under Favorites on the client.
• Driver status monitoring protocols — Communicates the driver status. This status can be set by the server and sent to the device, or changed by the user on the driver information page of the client device.
• Server to client driver status update protocol — Changes the status of the current driver on the client device.
• Client to server driver status update protocol — Notifies the server when the driver changes the driver status via the user interface on the client.
• Server to client driver status request protocol — Used by the server to obtain the driver status currently stored in the device.
• Create waypoint protocol — Allows the server to create or modify a waypoint on the client.
• Waypoint deleted protocol — The client sends this packet when a Fleet Management waypoint is deleted, whether the delete was initiated from the client side or the server side.
• Delete waypoint protocol — Allows the server to delete a waypoint on the client.
• Delete waypoint by category protocol — Allows the server to delete all waypoints on the client that belong to a particular category.
• Create waypoint category protocol — Allows the server to create or modify a waypoint category on the client.
• Driver ID and status protocols — Identifies the current driver and status.
• Driver ID monitoring protocols — Communicates the driver ID.
• Server to client driver ID update protocol — Changes the driver ID of the current driver on the client device.
• Client to server driver ID update protocol — Notifies the server when the driver changes the driver ID via the user interface on the client.
• Server to client driver ID request protocol — Used by the server to obtain the driver ID currently stored in the device.

A608 — Mainly Speed Limit Alerts

• Speed limit alert (SLA) protocols — Alerts the server of speed limit violations.
• Speed limit alert setup protocol — A speeding event starts when the speed threshold is exceeded for time_over seconds and ends when speed drops below threshold for time_under seconds.

A609 — Remote Reboot

• Remote reboot protocol — Remotely reboots the PND.

A610 — HOS 1.0 - AOBRD

• Supports FMI_HOS 1.0.
• AOBRD login protocol — Allows a driver to login to the AOBRD system.
• Driver profile request protocol — Requests the driver profile of a driver who has logged into the AOBRD system.
• Driver profile update protocol — Updates the driver profile of a driver who has logged into the AOBRD system.
• Event log file request protocol — Allows the client to request a driver’s event logs from the server.
• Event log file update protocol — Sends a new event log record to the server.
• AOBRD set odometer request protocol — Allows the server to set the odometer value used by the client.
• AOBRD shipment protocol — Allows the server to provide the client with a set of shipments that are assigned to the specified driver.
• AOBRD annotation protocol — Allows the client to request the driver’s event log annotation from the server.

A611 — Server to Client Long Text Message Protocol

• Server to client long text message protocol — Sends a multi-packet text message from the server to the client. The size of the text message can be up to 2,000 bytes in length.
• Server to client canned response long text message protocol — Sends a long text message from the server to the client which requires a response to be selected from a list.

A612 — Custom Forms Protocol

• Custom Form Template File Transfer (A612) — Uses the File Transfer Protocol originally defined in A604 to send a form template from the server to the client.
• Custom Form Submission (A612) — Uses the File Transfer Protocol to send a completed form to the server.
• Delete Custom Form Template Protocol (A612) — Allows the server to delete a custom form template previously sent to the client.
• Move Custom Form Template Protocol (A612) — Moves the selected custom form template to a different position in the list of form templates.
• Custom Form Template Position Request (A612) — Returns the specified custom form template’s position in the list of form templates.
• Delete All Custom Forms Protocol — Extends the Data Deletion Protocol to delete all custom form templates and submitted custom forms kept on the device.

A613 — Custom Avoidance Protocol

• Custom Avoidance Feature Enable (A613) — Enables FMI to take control of the device’s custom area avoidance feature.
• Custom Avoidance Add/Update Protocol (A613) — Used to send a custom avoidance to the device.
• Custom Avoidance Delete Protocol (A613) — Used to delete a custom avoidance previously send to the device.
• Enable/Disable Custom Avoidance Protocol (A613) — Used to enable or disable a specific custom avoidance. Disabled custom avoidances are still on the device but do not affect navigation.
• Delete All Custom Avoidances Protocol (A613) — Extends the Data Deletion Protocol to delete all custom avoidances kept on the device.

A614 — Path Specific Stops

• Path Specific Stop Protocol (A614) — Builds upon the File Transfer Protocol originally defined in A604 to send a path specific stop to the device.

A615 — HOS 2.0

• New Driver Profile Response (A615) — Allows the device to handle a new response to the Driver Profile Request (A610) that contains the driver’s load type (Passenger Carrying/Property Carrying) and the last time that the driver reported adverse weather. This new data will be used by the Hours-of-Service rules engine to more effectively check for violations.
• New Driver Profile Update (A615) — Allows driver profile update to include the driver’s load type (Passenger Carrying/Property Carrying) and the last time that the driver reported adverse weather.
• Server Initiated Logout (A615) — Forces the logout of an HOS driver.
• Enable/Disable Automatic Driver Status Protocol (A615) — Enables or disables the ability to automatically change an HOS driver’s status between driving and on-duty.
• Enable/Disable 8-Hour Rule Protocol (A615) — Enables or disables the requirement of a 30-minute rest after 8 hours of driving a property carrying vehicle.
• IFTA File Transfer Protocol (A615) — Uses the File Transfer Protocol send IFTA files within a specified date range to the server.
• IFTA File Delete Protocol (A615) — Allows the server to delete IFTA files within a specified date range.
• New Driver Annotations (A615) — The device will send new system generated annotations for adverse weather conditions and all driver logoffs (driver initiated, system initiated, or remote logoff).

A616 — ETA Improvements and Baud Rate Change

• Estimated Time of Arrival Improvements (A616) — Modifies the ETA behavior from A603 to send a message whenever the ETA has changed by more than 15% of the remaining driving time. A 5-minute minimum and 20-minute maximum is applied to the variance, so a change of less than 5 minutes will not send an ETA message even if that is 15% of the remaining time.
• Baud Rate Change Protocol (A616) — Allows the server to negotiate a change in the serial communication speed between 9600 baud and 56K baud.

A617 — Alert Popup and Sensor Display Protocol

• Alert Popup Protocol (A617) — Shows a banner at the bottom of the screen containing a message and icon specified by the server.
• Configure Sensor Display Protocol (A617) — Adds or updates a sensor in the sensor display list.
• Update Sensor Display Status Protocol (A617) — Updates the status of the specified sensor.
• Delete Sensor Display Protocol (A617) — Removes an existing sensor and all status records from the sensor display list.
• Sensor Display List Position Protocol (A617) — Returns the position within the sensor display list of the specified sensor.

A618 — Additional Stops Protocol

• Stop Protocol (A618) — Supports stops with text of up to 2000 bytes by utilizing the generic file transfer protocol.

A619 — HOS Settings Protocol and Improved Violation Checking

• HOS Settings Protocol (A619) — This protocol allows the server to set global HOS settings: Periodic status updates and enable/disable of the FMCSA 8-Hour Rule.
• Violation Checking Improvements (A619) — Modifies the violation checker to consider more variations on the split berth rest provisions.

A620 — Start of Day Setting Using HOS Settings Protocol

• Start of Day Setting (A620) — Controls the time of day used for weekly on-duty calculations and is changed using the HOS settings protocol.

A621 — Custom Forms Protocol

• Custom Form Template Show Request on Client (A621) — This protocol allows the Server to display a Custom Form Template immediately if it is already on the device.
• Custom Form Containing a Picture (A621) — This protocol allows the driver to include a picture in a Custom Form destined to the Server.

A622 — CAM 1.0 (Dash Camera Protocol)

• Lock Dash Camera Configuration (A622) — This protocol allows the server to lock the dash camera configuration settings, which prevents drivers from altering the server defined settings.
• Set Dash Camera Configuration (A622) — The server has the ability to configure the dash camera settings.
• Get Dash Camera Configuration (A622) — This protocol allows the server to query the device for the current dash camera configuration settings.
• Set Dash Camera Notification Configuration (A622) — This protocol allows the server to enable/disable notifications of driver forward collision warnings, lane departure warnings, and/or incident detections.
• Get Dash Camera Notification Configuration (A622) — This protocol allows the server to query the device for the current dash camera notification settings.
• Dash Camera Warning Notification to Server (A622) — This protocol supports notification of forward collision warnings, lane departure warnings, or incidents as they are detected by the device and when configured by the server.
• Dash Camera Incident File Notification for Server (A622) — The server will be notified when an incident event file is saved by the device using this protocol.

A623 — ETA Mode Setting

• Allows the server to configure a client’s mode for reporting ETAs.
• Available configuration settings are “none,” “Server dispatch destinations” (FMI Stops), “driver created destinations,” or “all destination types.”
• This mode setting is saved in FMI Non-Volatile memory.

Other Features

• Enable FMI.
• Product ID and Support — Returns Garmin product ID, software version, and supported protocols and data types.
• Unit ID/ESN Protocol — Extracts the client’s unit ID (or electronic serial number).
• Date and Time Protocol — Transfers the current date and time on the client to the server.
• Position, Velocity, and Time (PVT) Protocol — Provides the server with real-time position, velocity, and time (PVT), which is transmitted by the client approximately once per second.