Line 38: |
Line 38: |
| | | |
| ====Log mode==== | | ====Log mode==== |
− | In this mode via RS-232 interface prints the {{{model|FMX125}}} device log and does not respond to commands.<br /> | + | In this mode via RS-232 interface prints the FMU126 device log and does not respond to commands.<br /> |
| | | |
| ====GNSS NMEA mode==== | | ====GNSS NMEA mode==== |
− | In NMEA mode via RS-232 interface {{{model|FMX125}}} prints GNSS NMEA log and does not respond to commands.<br /> | + | In NMEA mode via RS-232 interface FMU126 prints GNSS NMEA log and does not respond to commands.<br /> |
| | | |
| ====LLS mode==== | | ====LLS mode==== |
− | In LLS mode RS-232 supports one and RS-485 supports up to five - each of which has a receiver ID.<br/> | + | In LLS mode RS-232 supports one LLS sensor. |
| | | |
| ====TCP (ASCII/Binary) modes==== | | ====TCP (ASCII/Binary) modes==== |
Line 100: |
Line 100: |
| | | |
| ===== RS-232 / RS-485 CMD ID===== | | ===== RS-232 / RS-485 CMD ID===== |
− | This parameter is used when {{{model|}}} is sending RS232/RS485 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). {{{model|}}} behavior when it receives different CMD ID (Type) values in GPRS packet from server. | + | This parameter is used when FMU126 is sending RS232 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). FMU126 behavior when it receives different CMD ID (Type) values in GPRS packet from server. |
| [[File:CMD.gif|right]] | | [[File:CMD.gif|right]] |
| | | |
− | When {{{model|}}} receives these CMD ID values in the GPRS packet it behaves accordingly: | + | When FMU126 receives these CMD ID values in the GPRS packet it behaves accordingly: |
| | | |
| {| class="wikitable" style="width:70%;" | | {| class="wikitable" style="width:70%;" |
Line 122: |
Line 122: |
| |- | | |- |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |16 | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |16 |
− | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to paired Bluetooth device | + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to paired Bluetooth® device |
| |- | | |- |
| |} | | |} |
Line 133: |
Line 133: |
| | | |
| ====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 {{{model|}}} understands RFID messages that are in hexadecimal text format and RFID HID Mode interprets messages that are in binary format. The type of RFID message sent to {{{model|}}} depends on the RFID reader. For example, the RFID MF7 mode message looks like <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code> | + | The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode FMU126 understands RFID messages that are in hexadecimal text format and RFID HID Mode interprets messages that are in binary format. The type of RFID message sent to FMU126|}}} depends on the RFID reader. For example, the RFID MF7 mode message looks like <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code> |
| | | |
| The selected mode has to correspond to the RFID reader's mode. | | The selected mode has to correspond to the RFID reader's mode. |
Line 139: |
Line 139: |
| | | |
| ====RS-232 Garmin mode==== | | ====RS-232 Garmin mode==== |
− | Garmin provides a Fleet Management Interface Tool Kit, once {{{model|}}} 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|}}} and Garmin operational diagram is shown on the figure below. | + | Garmin provides a Fleet Management Interface Tool Kit, once FMU126 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 />FMU126|}}} and Garmin operational diagram is shown on the figure below. |
| [[Image:FMX125_GARMIN_BLOCK.png|900px|none]] | | [[Image:FMX125_GARMIN_BLOCK.png|900px|none]] |
| | | |
| ==Garmin protocols== | | ==Garmin protocols== |
− | The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|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 {{{model|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. | + | The following is a list of protocols supported and the corresponding list of features/benefits. FMU126|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 FMU126|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''' |