| Line 97: |
Line 97: |
| | Since Prefix 2 does not match the incoming 2nd byte, data will not be accepted. | | Since Prefix 2 does not match the incoming 2nd byte, data will not be accepted. |
| | | | |
| − | ==RS-232 Interface== | + | ==RS-232 Modes== |
| − | 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|FMB125}}}_RS-232_and_RS-485#RS-485_modes|RS-485]]. When entering Sleep or Deep sleep RS-232 will be powered off.
| |
| − | | |
| − | ===RS-232 modes===
| |
| − | ------------------
| |
| − | Log mode, NMEA, LLS, TCP ASCII, and TCP Binary modes are identical to those of [[{{{model|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==== |
| − | ------------------
| |
| | In this mode, the user is able to communicate with the server through the terminal. A link between the FMB device and the server has to be established for this mode to function properly. | | In this mode, the user is able to communicate with the server through the terminal. A link between the FMB device and the server has to be established for this mode to function properly. |
| | | | |
| Line 113: |
Line 107: |
| | | | |
| | ====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 "$aa$02$03$04$17$89$00$01" while HID mode message is of the following format: "1213141519". | | 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 "$aa$02$03$04$17$89$00$01" while HID mode message is of the following format: "1213141519". |
| | | | |
| Line 121: |
Line 114: |
| | | | |
| | ====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 {{{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. |
| | [[Image:FMX125_GARMIN_BLOCK.png|900px|none]] | | [[Image:FMX125_GARMIN_BLOCK.png|900px|none]] |
| | | | |
| − | ====RS-232 TCP Binary/TCP ASCII mode====
| |
| − | ------------------
| |
| − | In TCP ASCII/Binary mode all data received from the external device is sent directly to the 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====
| |
| − | ------------------
| |
| − | TCP ASCII Buffered and TCP Binary Buffered modes are used to collect data from RS232 and save it in the buffer if there is no link with the server and data cannot be sent immediately. When the link is established and there is data to transmit, then RS232 data from the 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 the external device only to the main server. In Buffered modes – to both main and backup/duplicate servers.
| |
| − | Message timestamp:
| |
| − | The message Timestamp parameter is used to determine if it is necessary to include a timestamp in the RS232 TCP packet when sending to the server. If the parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.
| |
| − |
| |
| − | =====RS-232 TCP Binary settings=====
| |
| − | ------------------
| |
| − | [[Image: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 separately or in unison.
| |
| − | To configure this setting a value from 0 to 255 in decimal has to be entered. The device will convert this value to HEX and compare the 1st, 2nd, or 3rd byte from incoming data. If the values do not match, the device will not accept incoming data.
| |
| − |
| |
| − | Example:<br>
| |
| − | Incoming packet through RS232/RS485 using TCP Binary/TCP Binary Buffered mode - <font color="red">50</font> <font color="green">72</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67
| |
| − | <ul>
| |
| − | <li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX.
| |
| − | <ul><li>FMB device will then check the 1st byte of incoming data and compare to the set Prefix 1.</li></ul></li>
| |
| − | <li>If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX.<br>
| |
| − | <ul><li>FMB device will then check the 2nd byte of incoming data and compare to the set Prefix 2.</li></ul></li>
| |
| − | <li>If Prefix 3 is set to 101 in decimal, it is equal to <font color="blue">65</font> in HEX.<br>
| |
| − | <ul><li>FMB device will then check the 3rd byte of incoming data and compare to the set Prefix 3.</li></ul></li>
| |
| − | </ul>
| |
| − | When values match, data will be accepted and saved to Buffer (using TCP Binary Buffered mode) or sent to the server (using TCP Binary mode).<br>
| |
| − |
| |
| − | Incoming packet through RS232/RS485 using TCP Binary/TCP Binary Buffered mode - <font color="red">50</font> <font color="green">0</font> <font color="blue">65</font> 66 69 78 20 57 6f 72 6b 69 6e 67
| |
| − | <ul>
| |
| − | <li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX.
| |
| − | <ul><li>FMB device will then check the 1st byte of incoming data and compare to the set Prefix 1.</li></ul></li>
| |
| − | <li>If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX.<br>
| |
| − | <ul><li>FMB device will then check the 2nd byte <font color="green">0</font> of incoming data and compare to the set Prefix 2.</li></ul></li>
| |
| − | </ul>
| |
| − | Since Prefix 2 does not match the incoming 2nd byte, data will not be accepted.
| |
| | | | |
| − | =====Codec 12/13 Packet Merge=====
| + | ==Codec 12/13 Packet Merge== |
| | ------------------ | | ------------------ |
| | This additional option configures the device to merge RS-232 records into a single packet instead of sending many separate packets. This functionality only affects TCP Binary Buffered or TCP Ascii Buffered RS232 modes. When enabled, the device will merge saved RS-232 records together into a single data packet until it is able to send it to the server.<br /> | | This additional option configures the device to merge RS-232 records into a single packet instead of sending many separate packets. This functionality only affects TCP Binary Buffered or TCP Ascii Buffered RS232 modes. When enabled, the device will merge saved RS-232 records together into a single data packet until it is able to send it to the server.<br /> |
| Line 171: |
Line 125: |
| | [[Image:packet_merge.png|225px|none]] | | [[Image:packet_merge.png|225px|none]] |
| | | | |
| − | =====RS-232 CMD ID=====
| + | ==RS-232/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 {{{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: |
