FMU126 RS-232: Difference between revisions
→RS-232 Interface
| Line 1: | Line 1: | ||
==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. | 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 [[ | 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: | ||
In this mode user is able to communicate with the server through terminal. A link between | In this mode user is able to communicate with the server through terminal. A link between FMB 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: | ||
The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 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. | The selected mode has to correspond to the RFID reader's mode. | ||
[[Image:RS-232 MODES.gif]] | |||
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. | ||
<br /> | <br /> | ||
| Line 24: | Line 25: | ||
*RS-232 Garmin mode: | *RS-232 Garmin mode: | ||
Garmin provides a Fleet Management Interface Tool Kit, once | 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: | [[Image:Fmb125_garmin_block.png|800px|none]] | ||
*RS-232 TCP Binary/TCP ASCII mode: | *RS-232 TCP Binary/TCP ASCII mode: | ||
| Line 37: | Line 38: | ||
Message timestamp: | Message timestamp: | ||
Message Timestamp parameter is used to determine if it is necessary to include timestamp in RS232 TCP packet when sending to server. If parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used. | Message Timestamp parameter is used to determine if it is necessary to include timestamp in RS232 TCP packet when sending to server. If parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used. | ||
<br /> | |||
====RS-232 TCP Binary settings==== | ====RS-232 TCP Binary settings==== | ||
[[Image: | [[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 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. | ||
To configure this setting a value from 0 to 255 in decimal has to be entered. Device will convert this value to HEX and compare the 1st, 2nd or 3rd byte from incoming data. If the values do not match, device will not accept incoming data. | To configure this setting a value from 0 to 255 in decimal has to be entered. Device will convert this value to HEX and compare the 1st, 2nd or 3rd byte from incoming data. If the values do not match, device will not accept incoming data. | ||
| Line 47: | Line 51: | ||
<ul> | <ul> | ||
<li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. | <li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. | ||
<ul><li> | <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> | <li>If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX.<br> | ||
<ul><li> | <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> | <li>If Prefix 3 is set to 101 in decimal, it is equal to <font color="blue">65</font> in HEX.<br> | ||
<ul><li> | <ul><li>FMB device will then check the 3rd byte of incoming data and compare to the set Prefix 3.</li></ul></li> | ||
</ul> | </ul> | ||
When values match, data will be accepted and saved to Buffer (using TCP Binary Buffered mode) or sent to server (using TCP Binary mode).<br> | When values match, data will be accepted and saved to Buffer (using TCP Binary Buffered mode) or sent to server (using TCP Binary mode).<br> | ||
| Line 58: | Line 62: | ||
<ul> | <ul> | ||
<li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. | <li>If Prefix 1 is set to 80 in decimal, it is equal to <font color="red">50</font> in HEX. | ||
<ul><li> | <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> | <li>If Prefix 2 is set to 114 in decimal, it is equal to <font color="green">72</font> in HEX.<br> | ||
<ul><li> | <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> | </ul> | ||
Since Prefix 2 does not match incoming 2nd byte, data will not be accepted. | Since Prefix 2 does not match incoming 2nd byte, data will not be accepted. | ||