4,768
edits
Changes
mLine 37:
Line 37: − Line 67:
Line 66: + + − *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. Line 182:
Line 152: − +
Text replacement - "Bluetooth(?!®)" to "Bluetooth®"
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 />
<br />
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.
====RS232 POS printer====
[[Image:RS-232 POS Printer.gif]]
The '''5803 Bluetooth® printer''' tested & confirmed working on command set.
Before every print, a status command byte request is sent. If the device returns the byte within a specific time frame, it means that the device is present. If cleanup task is not running “Get real-time status” command is sent every second to check if printer was connected to MSP500 device. Upon successful detection of a connected printer MSP500 starts printing all the records generated within the last hour.
Commands are sent in this format:
1 byte - Beginning of the command (ESC, GS or similar type byte from ASCII table)
1-2 byte(-s) - (optional) Command identifier
(x) bytes - (optional) Command arguments
Text printing is accomplished by just sending plain ASCII without any commands. If the buffer for the whole print line fills up (>32 chars), it prints the text automatically and feeds one line. If there’s less text, than it only prints and feeds line when linefeed (carriage is not needed) char is sent. Very few commands give back an answer (only status commands from all the tested ones).
Please contact your '''sales representative''' if there is need for the full commands list provided.
==Garmin protocols==
==Garmin protocols==
''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination.
''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination.
[[Category:MSP500 Manual]]
[[Category:MSP500 Manual| 4]]
