2,414
edits
Changes
mLine 1:
Line 1: − + Line 10:
Line 10: − br+ − + − br+ Line 22:
Line 22: − + − <br>+ − Line 52:
Line 51: − + − FMM125 RS-232 connection diagram is shown on the figure above.+ − + Line 66:
Line 65: − + − + Line 76:
Line 75: − + − + Line 93:
Line 92: − + Line 120:
Line 119: − + Line 188:
Line 187: − +
Reverted edits by Kriauciunas.to (talk) to last revision by Gabrielius.jankauskas
==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 />FMM125 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 transmit (GNSS NMEA) mode:
*RS-485 transmit (GNSS NMEA) mode:
[[Image:RS485 MODES.gif]]
[[File:RS485 MODES.gif|thumb|RS-485 Modes]]
RS-485 prints GNSS NMEA log and does not respond to commands.<br />
RS-485 prints GNSS NMEA log and does not respond to commands.<br />
*RS-485 receive (LLS) mode:
*RS-485 receive (LLS) mode:
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.
[[Image:FMB125_rs485_block.png|500px|none]]<br />
[[Image:Fmb125_rs485_block.png|500px|none]]<br />
====RS-485 TCP Binary settings====
====RS-485 TCP Binary settings====
[[File:RS-485 TCP BINARY.gif|250x250px]]
[[File:RS-485 TCP BINARY.gif]]
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2 or Prefix 3. These prefixes can be used seperately or in unison.
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2 or Prefix 3. These prefixes can be used seperately or in unison.
==RS-232 Interface==
==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 [[FMM125_RS-232_and_RS-485#RS-485_modes|RS-485]].
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 [[FMB125_RS-232_and_RS-485#RS-485_modes|RS-485]].
FMB125 RS-232 connection diagram is shown on the figure above.
===RS-232 modes===
===RS-232 modes===
Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of [[FMM125_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 [[FMB125_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:
*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 MF7 Mode FMM125 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 FMM125 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 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.
The selected mode has to correspond to the RFID reader's mode.
[[Image:RS-232 MODES.gif]]
[[File:RS-232 MODES.gif|thumb|RS-232 Modes]]
Please contact your local sales representative for more information about RFID IDs and devices.
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 FMM125 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 />FMM125 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|none]]
[[Image:Fmb125_garmin_block.png|800px|none]]
*RS-232 TCP Binary/TCP ASCII mode:
*RS-232 TCP Binary/TCP ASCII mode:
====RS-232 TCP Binary settings====
====RS-232 TCP Binary settings====
[[Image:RS-232 TCP BINARY SETTINGS.gif]]
[[File:RS-232 TCP BINARY SETTINGS.gif]]
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2 or Prefix 3. These prefixes can be used seperately or in unison.
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2 or Prefix 3. These prefixes can be used seperately or in unison.
==Garmin protocols==
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. FMM125 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 FMM125 and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. 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 https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.
===Standard protocols===
===Standard protocols===
''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.
[[Category:FMM125 Manual]]
[[Category:FMB125 Manual]]
