FMM125 RS-232 and RS-485: Difference between revisions
no edit summary
(Created page with "==RS-485 interface== RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br/>When activated RS-485 driver chip draws const...") |
No edit summary |
||
Line 16: | Line 16: | ||
In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format. | In TCP ASCII/Binary mode a link with an external device using text messages can be established. In TCP ASCII/Binary mode all data received from external device through RS-485 is sent directly to server (if link is currently active). Data is encapsulated in codec 12 format. | ||
[[Image: | [[Image:Fmx125 rs485 block.png|500px|none]] | ||
====RS-485 TCP Binary settings==== | ====RS-485 TCP Binary settings==== | ||
Line 61: | Line 61: | ||
* RS-232 Garmin mode: | * RS-232 Garmin mode: | ||
Garmin provides a Fleet Management Interface Tool Kit, once FMM125 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/>FMM125 and Garmin operational diagram is shown on the figure below. | Garmin provides a Fleet Management Interface Tool Kit, once FMM125 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/>FMM125 and Garmin operational diagram is shown on the figure below. | ||
[[Image: | [[Image:800px-Fmx125 garmin block.png|800px|none]] | ||
* RS-232 TCP Binary/TCP ASCII mode: | * RS-232 TCP Binary/TCP ASCII mode: |