FMU126 RS-232: Difference between revisions
no edit summary
No edit summary |
|||
| 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. Most of the modes are the same as for [[FMB125_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]]. | ||
FMU126 RS-232 connection diagram is shown on the figure above. | |||
===RS-232 modes=== | ===RS-232 modes=== | ||
| Line 22: | Line 21: | ||
<br /> | <br /> | ||
*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 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]] | |||
*RS-232 TCP Binary/TCP ASCII mode: | |||
In TCP ASCII/Binary mode all data received from external device is sent directly to 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 buffer if there is no link with server and data cannot be sent immediately. When link is established and there is data to transmit, then RS232 data from 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 external device only to main server. In Buffered modes – to both main and backup/duplicate servers. | |||
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. | |||
<br /> | |||
====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 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. | |||
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 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 incoming 2nd byte, data will not be accepted. | |||
*RS-232 Garmin mode: | *RS-232 Garmin mode: | ||