FMU126 RS-232 - Revision history

Arnas.Zeb: Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

2023-12-28T13:18:31Z

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

← Older revision		Revision as of 16:18, 28 December 2023
Line 122:		Line 122:
	\|-		\|-
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" \|16		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" \|16
	\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" \|Forward packet to paired ~~Bluetooth~~ device		\| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" \|Forward packet to paired Bluetooth® device
	\|-		\|-
	\|}		\|}

Mantas.Kraujelis at 07:07, 6 December 2021

2021-12-06T07:07:16Z

← Older revision		Revision as of 10:07, 6 December 2021
Line 100:		Line 100:

	===== RS-232 / RS-485 CMD ID=====		===== RS-232 / RS-485 CMD ID=====
	This parameter is used when FMU126 is sending RS232 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). FMU126~~\|}}}~~ behavior when it receives different CMD ID (Type) values in GPRS packet from server.		This parameter is used when FMU126 is sending RS232 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). FMU126 behavior when it receives different CMD ID (Type) values in GPRS packet from server.
	[[File:CMD.gif\|right]]		[[File:CMD.gif\|right]]

Line 139:		Line 139:

	====RS-232 Garmin mode====		====RS-232 Garmin mode====
	Garmin provides a Fleet Management Interface Tool Kit, once FMU126~~\|}}}~~ 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 />FMU126\|}}} and Garmin operational diagram is shown on the figure below.		Garmin provides a Fleet Management Interface Tool Kit, once FMU126 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 />FMU126\|}}} and Garmin operational diagram is shown on the figure below.
	[[Image:FMX125_GARMIN_BLOCK.png\|900px\|none]]		[[Image:FMX125_GARMIN_BLOCK.png\|900px\|none]]

Mantas.Kraujelis at 07:04, 6 December 2021

2021-12-06T07:04:36Z

← Older revision		Revision as of 10:04, 6 December 2021
Line 1:		Line 1:
	~~\|model=FMU125~~
	==RS-232 modes==		==RS-232 modes==
	Available modes for RS-232 interface:		Available modes for RS-232 interface:
Line 39:		Line 38:

	====Log mode====		====Log mode====
	In this mode via RS-232 interface prints the ~~{{{model\|FMX125}}}~~ device log and does not respond to commands.<br />		In this mode via RS-232 interface prints the FMU126 device log and does not respond to commands.<br />

	====GNSS NMEA mode====		====GNSS NMEA mode====
	In NMEA mode via RS-232 interface ~~{{{model\|FMX125}}}~~ prints GNSS NMEA log and does not respond to commands.<br />		In NMEA mode via RS-232 interface FMU126 prints GNSS NMEA log and does not respond to commands.<br />

	====LLS mode====		====LLS mode====
	In LLS mode RS-232 supports one ~~and RS-485 supports up to five - each of which has a receiver ID~~.~~<br/>~~		In LLS mode RS-232 supports one LLS sensor.

	====TCP (ASCII/Binary) modes====		====TCP (ASCII/Binary) modes====
Line 101:		Line 100:

	===== RS-232 / RS-485 CMD ID=====		===== RS-232 / RS-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 FMU126 is sending RS232 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). FMU126\|}}} behavior when it receives different CMD ID (Type) values in GPRS packet from server.
	[[File:CMD.gif\|right]]		[[File:CMD.gif\|right]]

	When ~~{{{model\|}}}~~ receives these CMD ID values in the GPRS packet it behaves accordingly:		When FMU126 receives these CMD ID values in the GPRS packet it behaves accordingly:

	{\| class="wikitable" style="width:70%;"		{\| class="wikitable" style="width:70%;"
Line 134:		Line 133:

	====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 <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code>		The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode FMU126 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 FMU126\|}}} depends on the RFID reader. For example, the RFID MF7 mode message looks like <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code>

	The selected mode has to correspond to the RFID reader's mode.		The selected mode has to correspond to the RFID reader's mode.
Line 140:		Line 139:

	====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 FMU126\|}}} 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 />FMU126\|}}} and Garmin operational diagram is shown on the figure below.
	[[Image:FMX125_GARMIN_BLOCK.png\|900px\|none]]		[[Image:FMX125_GARMIN_BLOCK.png\|900px\|none]]

	==Garmin protocols==		==Garmin protocols==
	The following is a list of protocols supported and the corresponding list of features/benefits. ~~{{{model~~\|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of ~~{{{model~~\|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.		The following is a list of protocols supported and the corresponding list of features/benefits. FMU126\|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of FMU126\|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.

	'''Standard protocols'''		'''Standard protocols'''

Mantas.Kraujelis at 06:58, 6 December 2021

2021-12-06T06:58:35Z

← Older revision		Revision as of 09:58, 6 December 2021
Line 1:		Line 1:
			\|model=FMU125
	==RS-232 modes==		==RS-232 modes==
	Available modes for RS-232 interface:		Available modes for RS-232 interface:

Mantas.Kraujelis: /* RS-232 / RS-485 modes */

2021-12-06T06:57:42Z

RS-232 / RS-485 modes

← Older revision		Revision as of 09:57, 6 December 2021
Line 1:		Line 1:
	==RS-232 ~~/ RS-485~~ modes==		==RS-232 modes==
	Available modes for RS-232 ~~and RS-485 interfaces~~:		Available modes for RS-232 interface:

	{\| class="wikitable" style="text-align:center; background-color:#ffffff;"		{\| class="wikitable" style="text-align:center; background-color:#ffffff;"
Line 35:		Line 35:
	\| ✔		\| ✔
	\| ✔		\| ✔
	\|-
	~~\| style="vertical-align:middle;" \| RS-485~~
	~~\| ✔~~
	~~\| ✔~~
	~~\| ✔~~
	\|
	\|
	\|
	\|
	~~\| ✔~~
	~~\| ✔~~
	\|
	\|
	\|
	\|
	\|}		\|}

	====Log mode====		====Log mode====
	In this mode via RS-232 ~~or RS-485~~ interface prints the {{{model\|FMX125}}} device log and does not respond to commands.<br />		In this mode via RS-232 interface prints the {{{model\|FMX125}}} device log and does not respond to commands.<br />

	====GNSS NMEA mode====		====GNSS NMEA mode====
	In NMEA mode via RS-232 ~~or RS-485~~ interface {{{model\|FMX125}}} prints GNSS NMEA log and does not respond to commands.<br />		In NMEA mode via RS-232 interface {{{model\|FMX125}}} prints GNSS NMEA log and does not respond to commands.<br />

	====LLS mode====		====LLS mode====
Line 140:		Line 125:
	\|-		\|-
	\|}		\|}
	~~<br></br>~~

	~~==RS-232 Modes==~~

	====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.

Mantas.Kraujelis at 06:56, 6 December 2021

2021-12-06T06:56:27Z

Show changes

Tomas.kriauciunas: Protected "FMU126 RS-232" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2021-04-12T07:48:36Z

Protected "FMU126 RS-232" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 10:48, 12 April 2021
(No difference)

Tomas.kriauciunas at 07:48, 12 April 2021

2021-04-12T07:48:31Z

@@ Line 37: / Line 37: @@
 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 />

Tomas.kriauciunas at 12:55, 19 March 2021

2021-03-19T12:55:00Z

@@ Line 1: / Line 1: @@
 ==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]].
-FMB125 RS-232 connection diagram is shown on the figure above.
+FMU126 RS-232 connection diagram is shown on the figure above.
 ===RS-232 modes===
@@ Line 22: / Line 21: @@
 <br />
 *RS-232 Garmin mode:

Tomas.kriauciunas: /* RS-232 Interface */

2021-03-19T12:54:03Z

RS-232 Interface

← Older revision		Revision as of 15:54, 19 March 2021
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. ~~FMU126~~ RS-232 connection diagram is shown on the figure above.		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 [[~~FMU126_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.		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 ~~FMU~~ device and the server has to be established for this mode to function properly.		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 ~~FMB126~~ 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 ~~FMB126~~ 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 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 ~~FMU126~~ 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 />~~FMU126~~ and Garmin operational diagram is shown on the figure below.		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:~~Fm garmin block~~.png\|800px\|none]]		[[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:~~TCP_Binary_2~~.~~png\|250px\|none~~]]		[[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>~~FMU~~ device will then check the 1st byte of incoming data and compare to the set Prefix 1.</li></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>~~FMU~~ device will then check the 2nd byte of incoming data and compare to the set Prefix 2.</li></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>~~FMU~~ device will then check the 3rd byte of incoming data and compare to the set Prefix 3.</li></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>~~FMU~~ device will then check the 1st byte of incoming data and compare to the set Prefix 1.</li></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>~~FMU~~ 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><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.