1,583
edits
Changes
Template:FMB630 RS-232 and RS-485 (view source)
Revision as of 14:32, 15 July 2019
, 14:32, 15 July 2019Created page with "==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 const..."
==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.
===RS-485 modes===
* RS-485 receive (FMB silent) mode:
RS485 Works in receive mode. Support debug and testing commands. When command is received answer is sent after that it back up to Receive mode.<br/>
* RS-485 transmit (FMB log) mode:
RS-485 prints FMB device log and does not respond to commands.<br/>
* RS-485 transmit (NMEA) mode:
RS-485 prints GNSS NMEA log and does not respond to commands.<br/>
* RS-485 receive (LLS) mode:
This mode supports up to five LLS fuel level sensors each of which has a receiver ID.<br/>
* RS-485 TCP receive (ASCII/Binary) modes:
In TCP ASCII/Binary mode a link with an external device using text messages can be established. Buffered modes save information until link with server is established and records are sent.
==RS-232 Interface==
RS-232 supports full-duplex communication which means the data can be both sent and received at the same time as they use separate transmission lines. Most of the modes are the same as for {{{model|FMB640}}}.
{{{model|FMB640}}} RS-232 connection diagram is shown on the figure above.
===RS-232 modes===
Silent, Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of FMBXXX RS-232 and RS-485 modes. In RS-232 LLS mode only one LLS fuel level sensor can be connected.
* RS-232 LCD mode:
In this mode user is able to communicate with the server through terminal. A link between FMB device and the server has to be established for this mode to function properly.
* RS-232 RFID HID/RFID MF7 mode:
The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' {{{model|FMB640}}} 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 {{{model|FMB640}}} 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.
* ATOL Tachograph mode: This mode is used to connect ATOL tachograph
* UL202-2 Fuel Sensor: Select this mode to make Ultrasonic Fuel Sensors to work on COM port.
* RS-232 Garmin mode:
Garmin provides a Fleet Management Interface Tool Kit, once {{{model|FMB640}}} 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/>{{{model|FMB640}}} and Garmin operational diagram is shown on the figure below.
{{{image|[[Image:FMB630_garmin_block.png|800px|center]]}}}
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB640}}} 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 {{{model|FMB640}}} 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===
Text Message Protocol:
* Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
* 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 quicker response;
* Messages can be up to 199 characters long;
* 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;
* Garmin provides a "virtual keyboard" for text communication.
Stop (Destination) Protocol:
* 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 the list;
* Garmin can provide status of a current Stop in progress;
* 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 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.
Estimated Time of Arrival Protocol:
* 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.
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 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.
Data Deletion Protocol:
* Dispatcher/office has the ability to wipe clean the data on Garmin PND;
* It allows to clean messages in inbox and remove stops.
===Enhanced protocols===
Canned Responses/Messages:
* Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
* Up to 50 of these canned responses can be utilized for any given scenarios;
* Drivers can store up to 120 canned messages, eliminating the need to type while driving.
Status Protocol:
* Up-to-the-minute communications that allow drivers to automatically send status updates;
* Driver's units can store up to 16 status indicators such as start/stop shift, on/off break etc.
===Supported features on TAVL client application===
TAVL client application lets user use the following features of Garmin FMI:
* Text messaging;
* Destination message;
* ETA request.
===Text messaging===
Text messaging feature lets user communicate with the driver (user that operates Garmin device) by sending text messages via GPRS.
===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.
===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.
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.
===RS-485 modes===
* RS-485 receive (FMB silent) mode:
RS485 Works in receive mode. Support debug and testing commands. When command is received answer is sent after that it back up to Receive mode.<br/>
* RS-485 transmit (FMB log) mode:
RS-485 prints FMB device log and does not respond to commands.<br/>
* RS-485 transmit (NMEA) mode:
RS-485 prints GNSS NMEA log and does not respond to commands.<br/>
* RS-485 receive (LLS) mode:
This mode supports up to five LLS fuel level sensors each of which has a receiver ID.<br/>
* RS-485 TCP receive (ASCII/Binary) modes:
In TCP ASCII/Binary mode a link with an external device using text messages can be established. Buffered modes save information until link with server is established and records are sent.
==RS-232 Interface==
RS-232 supports full-duplex communication which means the data can be both sent and received at the same time as they use separate transmission lines. Most of the modes are the same as for {{{model|FMB640}}}.
{{{model|FMB640}}} RS-232 connection diagram is shown on the figure above.
===RS-232 modes===
Silent, Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of FMBXXX RS-232 and RS-485 modes. In RS-232 LLS mode only one LLS fuel level sensor can be connected.
* RS-232 LCD mode:
In this mode user is able to communicate with the server through terminal. A link between FMB device and the server has to be established for this mode to function properly.
* RS-232 RFID HID/RFID MF7 mode:
The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' {{{model|FMB640}}} 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 {{{model|FMB640}}} 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.
* ATOL Tachograph mode: This mode is used to connect ATOL tachograph
* UL202-2 Fuel Sensor: Select this mode to make Ultrasonic Fuel Sensors to work on COM port.
* RS-232 Garmin mode:
Garmin provides a Fleet Management Interface Tool Kit, once {{{model|FMB640}}} 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/>{{{model|FMB640}}} and Garmin operational diagram is shown on the figure below.
{{{image|[[Image:FMB630_garmin_block.png|800px|center]]}}}
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB640}}} 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 {{{model|FMB640}}} 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===
Text Message Protocol:
* Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
* 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 quicker response;
* Messages can be up to 199 characters long;
* 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;
* Garmin provides a "virtual keyboard" for text communication.
Stop (Destination) Protocol:
* 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 the list;
* Garmin can provide status of a current Stop in progress;
* 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 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.
Estimated Time of Arrival Protocol:
* 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.
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 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.
Data Deletion Protocol:
* Dispatcher/office has the ability to wipe clean the data on Garmin PND;
* It allows to clean messages in inbox and remove stops.
===Enhanced protocols===
Canned Responses/Messages:
* Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
* Up to 50 of these canned responses can be utilized for any given scenarios;
* Drivers can store up to 120 canned messages, eliminating the need to type while driving.
Status Protocol:
* Up-to-the-minute communications that allow drivers to automatically send status updates;
* Driver's units can store up to 16 status indicators such as start/stop shift, on/off break etc.
===Supported features on TAVL client application===
TAVL client application lets user use the following features of Garmin FMI:
* Text messaging;
* Destination message;
* ETA request.
===Text messaging===
Text messaging feature lets user communicate with the driver (user that operates Garmin device) by sending text messages via GPRS.
===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.
===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.
