Line 1: |
Line 1: |
| ==RS-485 Interface== | | ==RS-485 Interface== |
| | | |
− | RS485 supports only Half Duplex communication. It means that at one time data is only sent/received.<br/>When activated RS-485 driver chip draws constant 30mA current.<br/>When Entering Sleep or Deep sleep, Chip will be powered off too.<br/>FMB125 RS-485 Pins connection diagram are shown on the Figure 66:
| + | RS-485 supports only Half Duplex communication. It means that at one time data is only sent/received.<br/>When activated RS-485 driver chip draws constant 30mA current.<br/>When Entering Sleep or Deep sleep, Chip will be powered off too.<br/>FMB125 RS-485 Pins connection diagram are shown on the Figure 66: |
| | | |
| ===RS-485 modes=== | | ===RS-485 modes=== |
− | * RS485 transmit (FMB log) mode: | + | * RS-485 transmit (FMB log) mode: |
| RS-485 works in transmit mode, it prints FM log. It won’t respond to commands. | | RS-485 works in transmit mode, it prints FM log. It won’t respond to commands. |
| | | |
− | * RS485 transmit (GNSS NMEA) mode: | + | * RS-485 transmit (GNSS NMEA) mode: |
| RS-485 works in transmit mode, it prints GNSS NMEA log. It won’t respond to commands. | | RS-485 works in transmit mode, it prints GNSS NMEA log. It won’t respond to commands. |
| | | |
− | * RS485 receive (LLS) mode: | + | * RS-485 receive (LLS) mode: |
| The mode supports up to five LLS fuel level sensors. Baud rate must be 19200. LLS have receiver id. LLS mode configuration shown in Figure 69. | | The mode supports up to five LLS fuel level sensors. Baud rate must be 19200. LLS have receiver id. LLS mode configuration shown in Figure 69. |
| | | |
− | * RS485 TCP (ASCII, Binary) mode: | + | * RS-485 TCP (ASCII/Binary) modes: |
| In TCP ASCII mode link with external device using text messages can be established. | | In TCP ASCII mode link with external device using text messages can be established. |
| TCP Binary mode is the same as above but binary messages will be accepted. | | TCP Binary mode is the same as above but binary messages will be accepted. |
| | | |
− | ==RS232 Interface== | + | ==RS-232 Interface== |
| RS-232 supports Full Duplex communication. It means that at the same time you can send/receive Data, because it uses separate lines for transmitting and receiving data. | | RS-232 supports Full Duplex communication. It means that at the same time you can send/receive Data, because it uses separate lines for transmitting and receiving data. |
| Most of the modes are the same as RS-485. | | Most of the modes are the same as RS-485. |
− | FMB125 RS232 pins connection diagram are shown on the Figure 66. | + | FMB125 RS2-32 pins connection diagram are shown on the Figure 66. |
| | | |
| ===RS-232 modes=== | | ===RS-232 modes=== |
− | In Configurator windows select RS232/RS485 window where is RS232 Settings (more information about available RS232/RS485 parameters configuration in 5.19.10 FMB125 RS232\RS485 parameters configuration chapter).
| |
− | Most of the modes are the same as RS-485. Same modes are: log mode, NMEA, LLS, TCP Ascii and TCP Binary.
| |
− | In RS232 LLS mode only one LLS fuel level sensor can be connected.
| |
| | | |
− | * RS232 LCD mode:
| + | Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes are identical to those of RS-485. In RS-232 LLS mode only one LLS fuel level sensor can be connected. |
− | In this mode you can communicate with server through terminal. Link between FM and server has to be established for this functionality to work. | |
| | | |
− | * RS232 RFID HID/RFID MF7 mode: | + | * RS-232 LCD mode: |
− | The difference between RFID Mode and RFID MF7 Mode is that in RFID Mode FMB125 understands RFID messages that are in hexadecimal format and RFID MF7 Mode understands messages that are in decimal format. For example:
| + | In this mode user is able to communicate with server through terminal. A link between FMB device and the server has to be established for this mode to function properly. |
− | RFID Mode message – “$aa$02$03$04$17$89$00$01”
| |
− | RFID MF7 Mode message – “1213141519”
| |
− | The chosen mode has to correspond to the RFID reader’s mode. What type of RFID is sent to FMB125 depends on the reader.
| |
− | For more information about RFID ID’s and devices, please contact to your local sales representative.
| |
| | | |
− | * RS232 GARMIN mode: | + | * RS-232 RFID HID/RFID MF7 mode: |
− | Garmin provides a Fleet Management Interface Tool Kit which connected to FMB125 enables the driver to have a "screen" in their vehicle for real-time navigation, messaging, and job dispatch capabilities to help them be more efficient. | + | 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. What type of RFID is sent to FMB125 depends on the 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. |
− | FMB125 and Garmin operational scheme is shown in Figure 77 below: | + | |
| + | * 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, messaging and offers job dispatch capabilities to help them be more efficient.<br/> |
| + | FMB125 and Garmin operational scheme is shown on the figure below. |
| + | [[Image:Fmb125_garmin_block.png|800px|center]] |
| | | |
| ==Garmin protocols== | | ==Garmin protocols== |