1,663
edits
Changes
FMU125 RS-232 and RS-485 (view source)
Revision as of 10:07, 6 November 2019
, 10:07, 6 November 2019→RS-232 modes
==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/>FMU125 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 />FMU125 RS-485 connection diagram is shown below.
===RS-485 modes===
===RS-485 modes===
* RS-485 transmit (GNSS NMEA) mode:
*RS-485 transmit (FMU log) mode:
* RS-485 receive (LLS) mode:
RS-485 prints FMU device log and does not respond to commands.<br />
This mode supports up to five LLS fuel level sensors each of which has a receiver ID.<br/>
*RS-485 transmit (GNSS 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 (ASCII/Binary) modes:
In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format.
In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format.
Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of [[FMU125_RS-232_and_RS-485#RS-485_modes|RS-485]]. In RS-232 LLS mode only one LLS fuel level sensor can be connected. Additionally TCP ASCII Buffered and TCP Binary Buffered modes are available.
Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of [[FMU125_RS-232_and_RS-485#RS-485_modes|RS-485]]. In RS-232 LLS mode only one LLS fuel level sensor can be connected. Additionally TCP ASCII Buffered and TCP Binary Buffered modes are available.
* RS-232 LCD mode:
*RS-232 LCD mode:
In this mode user is able to communicate with the server through terminal. A link between FMU device and the server has to be established for this mode to function properly.
In this mode user is able to communicate with the server through terminal. A link between FMU device and the server has to be established for this mode to function properly.
* RS-232 RFID HID/RFID MF7 mode:
*RS-232 RFID HID/RFID MF7 mode:
* RS-232 Garmin mode:
The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode FMB125 understands RFID messages that are in hexadecimal text format and RFID HID Mode interpretes messages that are in binary format. The type of RFID message sent to FMB125 depends on the RFID reader. For example, RFID MF7 mode message looks like "$aa$02$03$04$17$89$00$01" while HID mode message is of following format: "1213141519". The selected mode has to correspond to the RFID reader's mode. Please contact your local sales representative for more information about RFID IDs and devices.
Garmin provides a Fleet Management Interface Tool Kit, once FMU125 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/>FMU125 and Garmin operational diagram is shown on the figure below.
<br />
*RS-232 Garmin mode:
Garmin provides a Fleet Management Interface Tool Kit, once FMU125 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 />FMU125 and Garmin operational diagram is shown on the figure below.
[[Image:800px-Fmx125 garmin block.png|800px|none]]
[[Image:800px-Fmx125 garmin block.png|800px|none]]
* RS-232 TCP Binary/TCP ASCII mode:
*RS-232 TCP Binary/TCP ASCII mode:
In TCP ASCII/Binary mode all data received from external device is sent directly to server. Data is encapsulated in codec 12 format. TCP Binary Mode has a delay of 30 ms, if no data is received for 30 ms, data is sent to the server. TCP ASCII mode waits for the End of Line (EOL) character (0x0D0A, \r\n) to pack data and send it to the server
In TCP ASCII/Binary mode all data received from external device is sent directly to server. Data is encapsulated in codec 12 format. TCP Binary Mode has a delay of 30 ms, if no data is received for 30 ms, data is sent to the server. TCP ASCII mode waits for the End of Line (EOL) character (0x0D0A, \r\n) to pack data and send it to the server
* RS-232 TCP Binary Buffered/TCP ASCII Buffered mode:
*RS-232 TCP Binary Buffered/TCP ASCII Buffered mode:
TCP ASCII Buffered and TCP Binary Buffered modes are used to collect data from RS232 and save it in buffer if there is no link with server and data cannot be sent immediately. When link is established and there is data to transmit, then RS232 data from buffer is transmitted after all records are sent. Data is sent in codec 13 protocol.
TCP ASCII Buffered and TCP Binary Buffered modes are used to collect data from RS232 and save it in buffer if there is no link with server and data cannot be sent immediately. When link is established and there is data to transmit, then RS232 data from buffer is transmitted after all records are sent. Data is sent in codec 13 protocol.
Note. That in TCP ASCII and TCP Binary modes device sends data from external device only to main server. In Buffered modes – to both main and backup/duplicate servers.
Note. That in TCP ASCII and TCP Binary modes device sends data from external device only to main server. In Buffered modes – to both main and backup/duplicate servers.
Text Message Protocol:
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;
*Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
* Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
*Garmin can provide a confirmation that message was read;
* Messages can be up to 199 characters long;
*Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
* Messages can also be generated from device and sent to dispatcher/office;
*Messages can be up to 199 characters long;
* Messages received will be notified to driver through a pop-up alert on Garmin screen;
*Messages can also be generated from device and sent to dispatcher/office;
* Garmin provides a "virtual keyboard" for text communication.
*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:
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 display a list of Stops/Jobs reported to the device in a separate category called "My Stops";
* Garmin can provide status of a current Stop in progress;
*Driver has ability to navigate directly to Stop from the list;
* Garmin can indicate whether the driver has stopped at the location;
*Garmin can provide status of a current Stop in progress;
* Garmin can inform how far the driver has progressed through the list of Stops;
*Garmin can indicate whether the driver has stopped at the location;
* Garmin can provide confirmation that the driver has received a particular Stop, familiarized himself/herself with its details or removed it from the list;
*Garmin can inform how far the driver has progressed through the list of Stops;
* Can provide confirmation that a Stop has been reached.
*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:
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.
*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:
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.
*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:
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.
*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===
===Enhanced protocols===
Canned Responses/Messages:
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;
*Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
* Drivers can store up to 120 canned messages, eliminating the need to type while driving.
*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:
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.
*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===
===Supported features on TAVL client application===
TAVL client application lets user use the following features of Garmin FMI:
TAVL client application lets user use the following features of Garmin FMI:
* Text messaging;
* Destination message;
*Text messaging;
* ETA request.
*Destination message;
*ETA request.
===Text messaging===
===Text messaging===
