FMI Protocol Support Matrix

Protocol ver. 1 ver. 2 ver. 2.10 ver. 2.5 ver. 2.6 ver. 2.7 ver. 2.8 ver. 2.9 ver. 2.95 ver. 3.0 ver. 3.05
A602
D602
A603
D603
A604
D604
A605 ✔*
D605 ✔*
A606
D606
A607
D607
A608
D608
A609
D609
A611
D611
A612
D612
A613
D613
A614
D614
A616
D616

* Not implemented on the nüvi 7×0 series.

FMI HOS Protocol Support Matrix

Protocol ver. 1.0 ver. 2.0
A610
D610
A615
D615

Note: FMI HOS protocol is supported on the d?zl series.

Features Supported by Each “A” Protocol

A603
  • Stop (destination) protocols – Used to inform the client of a new destination.
  • Stop protocol – Used to send 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
  • Unicode support
  • Server to client open text message – Used to send a simple text message from the server to the client.
  • Server to client canned response text message – Used to send a text message from the server to the client which requires a response to be selected from a list.
  • Message status protocol – Used to notify the server of the status of a text message previously sent from the server to the client.
  • Canned response list protocols – Used to maintain the list of canned responses used in the server to client canned response text message protocol.
  • Set canned response protocol – Used to set (add or update) a response in the canned response list.
  • Delete canned response protocol – Used to delete 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 – Used to add or update the text of a canned message on the client.
  • Delete canned message protocol – Used to delete 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 – Used to sort 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 – Used to transfer 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 – Used to send 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 – Used to customize the text of certain Fleet Management user interface elements. Currently, only the “dispatch” text on the device main menu can be changed.
A604
  • Driver status list protocols – Allow the server to maintain (add, update or delete) the list of driver statuses the user may select.
  • Client to server driver status update protocol – Used to notify 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 (communication link status) protocol – Used to send a “ping” to determine whether the communication link is still active.
  • Message throttling protocols – Allow 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 – Used to obtain the throttling state of all protocols that may be throttled.
A606
  • FMI safe mode protocol – Used to enable FMI safe mode (henceforth FMISM)and to set the threshold speed at which it will be enforced.
A607
  • Message delete protocol – Allows the server to delete text messages stored on the client.
  • Client to server open text message protocol – Used to send a simple text message from the client to the server.
  • Canned message (Quick Message) list protocols – Used to maintain 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 – Used to communicate 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 – Used to change the status of the current driver on the client device.
  • Client to server driver status update protocol – Used to notify 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 – Used to identify the current driver and status.
  • Driver ID monitoring protocols – Used to communicate the driver ID.
  • Server to client driver ID update protocol – Used to change the driver ID of the current driver on the client device.
  • Client to server driver ID update protocol – Used to notify 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
  • Speed limit alert (SLA) protocols – Used to alert 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 protocol – Used to remotely reboot the PND.
A610
  • Supports FMI_HOS 1.0
  • AOBRD login protocol – Allows a driver to login to the AOBRD system.
  • Driver profile request protocol – Used to request the driver profile of a driver who has logged into the AOBRD system.
  • Driver profile update protocol – Used to update 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 – Used to send 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 – Used to send a multi-packet text message from the server to the client. The size of the text message can be up to 2000 bytes in length.
  • Server to client canned response long text message protocol – Used to send a long text message from the server to the client which requires a response to be selected from a list.
A615 - HOS 2.0
  • New Driver Profile Response (A615) - This protocol 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) - This protocol 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) - This message will force the logout of an HOS driver.
  • Enable/Disable Automatic Driver Status Protocol (A615) - This protocol is used to enable or disable the ability to automatically change an HOS driver's status between driving and on-duty.
  • Enable/Disable 8-Hour Rule Protocol (A615) - This protocol is used to enable or disable the requirement of a 30 minute rest after eight hours of driving a property carrying vehicle.
  • IFTA File Transfer Protocol (A615) - This protocol uses the File Transfer Protocol send IFTA files within a specified date range to the server.
  • IFTA File Delete Protocol (A615) - This protocol 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) - This 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 five minute minimum and twenty minute maximum is applied to the variance, so a change of less than five minutes will not send an ETA message even if that is 15% of the remaining time.
  • Baud Rate Change Protocol (A616) - This protocol allows the server to negotiate a change in the serial communication speed between 9600 baud and 56K baud.