Changes

==RS-485 interface==

==RS-485 interface==

RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br/>When activated RS-485 driver chip draws constant 30mA current, when entering Sleep or Deep sleep, RS-485 will be powered off.<br/>FMB125 RS-485 connection diagram is shown below.

RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br/>When activated RS-485 driver chip draws constant 30mA current, when entering Sleep or Deep sleep RS-485 will be powered off.<br/>FMB125 RS-485 connection diagram is shown below.

===RS-485 modes===

===RS-485 modes===

* RS-485 TCP (ASCII/Binary) modes:

* RS-485 TCP (ASCII/Binary) modes:

In TCP ASCII/Binary mode a link with external an device using text messages can be established.

In TCP ASCII/Binary mode a link with an external device using text messages can be established.

[[Image:Fmb125_rs485_block.png|500px|center]]

[[Image:Fmb125_rs485_block.png|500px|center]]

* RS-232 RFID HID/RFID MF7 mode:

* RS-232 RFID HID/RFID MF7 mode:

The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' FMB125 understands RFID messages that are in hexadecimal format and ''RFID MF7 Mode'' interpretes messages that are in decimal format. The type of RFID message sent to FMB125 depends on the RFID reader. For example, ''RFID HID mode'' message looks like "$aa$02$03$04$17$89$00$01" while ''MF7 mode'' message is of following format: "1213141519".<br/>The selected mode has to correspond to the RFID reader's mode.<br/>For more information about RFID IDs and devices please contact your local sales representative.

The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' FMB125 understands RFID messages that are in hexadecimal format and ''RFID MF7 Mode'' interpretes messages that are in decimal format. The type of RFID message sent to FMB125 depends on the RFID reader. For example, ''RFID HID'' mode message looks like "$aa$02$03$04$17$89$00$01" while ''MF7 mode'' message is of following format: "1213141519".<br/>The selected mode has to correspond to the RFID reader's mode.<br/>Please contact your local sales representative for more information about RFID IDs and devices.

* RS-232 GARMIN mode:

* RS-232 Garmin mode:

Garmin provides a Fleet Management Interface Tool Kit, once FMB125 is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging, and offers job dispatch capabilities to help them be more efficient.<br/>FMB125 and Garmin operational diagram is shown on the figure below.

Garmin provides a Fleet Management Interface Tool Kit, once FMB125 is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging, and offers job dispatch capabilities to help them be more efficient.<br/>FMB125 and Garmin operational diagram is shown on the figure below.

[[Image:Fmb125_garmin_block.png|800px|center]]

[[Image:Fmb125_garmin_block.png|800px|center]]

==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 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.

The following is a list of protocols supported and the corresponding list of features/benefits. 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 refer to http://www8.garmin.com/solutions/pnd/supportedproducts.jsp. Notice that some Garmin products use different connection cables than others.

===Standard protocols===

===Standard protocols===

* Messages can be up to 199 characters long;

* Messages can be up to 199 characters long;

* Messages can also be generated from device and sent to dispatcher/office;

* Messages can also be generated from device and sent to dispatcher/office;

* Messages received will be notified about to driver through a pop-up alert on Garmin screen;

* Messages received will be notified to driver through a pop-up alert on Garmin screen;

* Garmin provides a "virtual keyboard" for text communication.

* Garmin provides a "virtual keyboard" for text communication.

* Garmin can indicate whether the driver has stopped at the location;

* Garmin can indicate whether the driver has stopped at the location;

* Garmin can inform how far the driver has progressed through the list of Stops;

* Garmin can inform how far the driver has progressed through the list of Stops;

* Garmin can provide confirmation that the driver has received a particular Stop, familiarized oneself with the details or removed it from the list;

* Garmin can provide confirmation that the driver has received a particular Stop, familiarized himself/herself with its details or removed it from the list;

* Can provide confirmation that a Stop has been reached.

* 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 can notify about the actual time of arrival as well as the distance remaining to a 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 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;

* 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 he/she 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 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.

* 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.

===Destination message===

===Destination message===

Destination message is used to inform the driver of a new destination. When Garmin device receives a destination message from the server it displays it as a "Stop" to the driver and also gives the driver an ability to start navigating to the "Stop" location. New destination in TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

Destination message is used to inform the driver of a new destination. When Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver an ability to start navigating to the Stop location. New destination in TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

===ETA request message===

===ETA request message===

''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination.

''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination.