Modbus slave integration with FMX125/FMX640 - Revision history

Arijus.C at 06:42, 7 January 2026

2026-01-07T06:42:11Z

← Older revision		Revision as of 09:42, 7 January 2026
Line 218:		Line 218:
	For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.		For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.

	''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the ~~Helpdesk~~ or your sales manager.''		''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Partner Portal/HelpDesk or your sales manager.''

	In our case, the sensor baud rate is 9600 and parity is None.		In our case, the sensor baud rate is 9600 and parity is None.

Sakalauskas.paulius: /* FMX6 series device configuration */

2025-01-02T13:56:28Z

FMX6 series device configuration

← Older revision		Revision as of 16:56, 2 January 2025
Line 217:		Line 217:
	<br />		<br />
	For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.		For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.

	~~[[File:FMC650 RS485 configuration.png]]~~

	''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Helpdesk or your sales manager.''		''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Helpdesk or your sales manager.''
Line 225:		Line 223:

	Leave the CMD ID field and start ID, Stop ID settings as it is.		Leave the CMD ID field and start ID, Stop ID settings as it is.

			[[File:FMC650 RS485 configuration.png]]

	===Creating the Modbus command===		===Creating the Modbus command===

Sakalauskas.paulius at 13:55, 2 January 2025

2025-01-02T13:55:39Z

← Older revision		Revision as of 16:55, 2 January 2025
Line 217:		Line 217:
	<br />		<br />
	For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.		For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.

			[[File:FMC650 RS485 configuration.png]]

	''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Helpdesk or your sales manager.''		''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Helpdesk or your sales manager.''

Sakalauskas.paulius at 13:53, 2 January 2025

2025-01-02T13:53:44Z

← Older revision		Revision as of 16:53, 2 January 2025
Line 1:		Line 1:
	we can use the '''FMX125/FMX650''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server side, we can easily integrate all the Modbus-supported equipment like '''Generators''', '''Energy Meters''', '''Fuel level sensors''', and ''' Temperature & Humidity sensors''', etc. without the additional cost of a Modbus controller and Router.		We can use the '''FMX125/FMX650''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server side, we can easily integrate all the Modbus-supported equipment like '''Generators''', '''Energy Meters''', '''Fuel level sensors''', and ''' Temperature & Humidity sensors''', etc. without the additional cost of a Modbus controller and Router.

	===System Architecture===		===System Architecture===

Sakalauskas.paulius at 13:52, 2 January 2025

2025-01-02T13:52:57Z

← Older revision		Revision as of 16:52, 2 January 2025
Line 1:		Line 1:
	we can use the '''FMX125/~~FMX640~~''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server side, we can easily integrate all the Modbus-supported equipment like '''Generators''', '''Energy Meters''', '''Fuel level sensors''', and ''' Temperature & Humidity sensors''', etc. without the additional cost of a Modbus controller and Router.		we can use the '''FMX125/FMX650''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server side, we can easily integrate all the Modbus-supported equipment like '''Generators''', '''Energy Meters''', '''Fuel level sensors''', and ''' Temperature & Humidity sensors''', etc. without the additional cost of a Modbus controller and Router.

	===System Architecture===		===System Architecture===
Line 203:		Line 203:
	If we are using an RS232 Modbus device, we need to connect FM device '''Tx''' to Modbus device '''Rx''' and FM device '''Rx''' to Modbus device '''Tx'''.<br />		If we are using an RS232 Modbus device, we need to connect FM device '''Tx''' to Modbus device '''Rx''' and FM device '''Rx''' to Modbus device '''Tx'''.<br />

	If you are using ~~FMX640~~, you need to use an RJ45 cable for connecting the RS232/RS485 devices.<br />		If you are using FMX650, you need to use an RJ45 cable for connecting the RS232/RS485 devices.<br />

	===FM device configuration===		=== FMX125/225 device configuration ===

	<br />		<br />
	For the Modbus integration, we need to select '''RS485''' as UART mode and '''TCP Binary''' as RS485 mode. Set the baud rate and parity as per the sensor configuration. In our case, the sensor baud rate is 9600 and parity is None. Leave the CMD ID field and Prefix settings as it is. ~~We used FMX125 for testing but in FMX640 also you can use the same settings~~		For the Modbus integration, we need to select '''RS485''' as UART mode and '''TCP Binary''' as RS485 mode. Set the baud rate and parity as per the sensor configuration. In our case, the sensor baud rate is 9600 and parity is None. Leave the CMD ID field and Prefix settings as it is. <br />
	<br />		<br />

			[[File:RS485 Configuration.png]]

			=== FMX6 series device configuration ===

	<br />		<br />
			For the Modbus integration, we need to select '''RS485''' as mode and '''TCP/UDP Binary''' as RS485 mode. Set the baud rate as per the sensor's documentation.

	~~[[File~~:~~RS485 Configuration~~.~~png]]~~		''Note: The parity on FMX650 is always set as "none." If the sensor’s default parity is not "none," it must be set to "none" to connect with the FMX650. If the parity cannot be changed on the sensor side and a specific parity type is required for sensor <-> FMC650 communication, please contact Teltonika support via the Helpdesk or your sales manager.''

			In our case, the sensor baud rate is 9600 and parity is None.

			Leave the CMD ID field and start ID, Stop ID settings as it is.

	===Creating the Modbus command===		===Creating the Modbus command===
Line 332:		Line 341:
	'''Codec ID''' - in Codec12 it is always 0x0C.<br />		'''Codec ID''' - in Codec12 it is always 0x0C.<br />
	'''Command/Response Quantity 1''' - it is ignored when parsing the message.<br />		'''Command/Response Quantity 1''' - it is ignored when parsing the message.<br />
	'''Type''' - 0x0E – If you set the type as 0E the device will route this command to serial ports.<br />		'''Type''' - 0x0E – If you set the type as 0E the device will route this command to serial ports ( Only for FMX125/FMX225)<br />
	'''Command/Response Size''' – command or response length.<br />		'''Command/Response Size''' – command or response length.<br />
	'''Command/Response''' – command or response in HEX.<br />		'''Command/Response''' – command or response in HEX.<br />
Line 338:		Line 347:
	'''CRC-16''' – calculated from Codec ID to the Command Quantity 2. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data.<br />		'''CRC-16''' – calculated from Codec ID to the Command Quantity 2. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data.<br />

	Let‘s create our GPRS command as per the codec 12 protocol.		Let‘s create our GPRS command as per the codec 12 protocol for FMX125/225

	'''</span><span style="background-color:#00ff00;">010300000008440C</span>''' is the Modbus command; we have used this command as the payload of our GPRS command.		'''</span><span style="background-color:#00ff00;">010300000008440C</span>''' is the Modbus command; we have used this command as the payload of our GPRS command.
Line 345:		Line 354:

	'''00000000 00000010 0C 01 0E 00000008 </span><span style="background-color:#00ff00;">010300000008440C</span> 01 00001181'''		'''00000000 00000010 0C 01 0E 00000008 </span><span style="background-color:#00ff00;">010300000008440C</span> 01 00001181'''


			Now, let‘s create our GPRS command as per the codec 12 protocol for FMX6 series devices.

			'''<span style="background-color:#00ff00;">''010300000008440C''</span>''' ''is the Modbus command; we have used this command as the payload of our GPRS command.''

			'''''00000000 00000010 0C 01 05 00000008 <span style="background-color:#00ff00;">010300000008440C</span> 01 0000DA8B'''''

			'''''05''' -> The command ID is dependent on the value we select in the configurator. For command Type, you have to use configured Command ID -1. By default, we are using command ID 6 in the configuration. Therefore, the command from sever has to be with '''05''' and the response from the sensor to the server will have command ID '''06''' in the codec packet.''

	<br />		<br />
Line 518:		Line 536:
	<br />		<br />

	Teltonika FMX125 & ~~FMX640~~ devices are capable to integrate equipment and sensors that use Modbus RTU protocol. We have successfully integrated TZONE TZ-THT02 RS485 Modbus RTU Temperature and Humidity sensor with FMC125.		Teltonika FMX125 & FMX650 devices are capable to integrate equipment and sensors that use Modbus RTU protocol. We have successfully integrated TZONE TZ-THT02 RS485 Modbus RTU Temperature and Humidity sensor with FMC125.

	[[Category: Frequently Asked Questions - FAQ]]		[[Category: Frequently Asked Questions - FAQ]]

Naveen.rapheal at 13:10, 6 June 2023

2023-06-06T13:10:51Z

← Older revision		Revision as of 16:10, 6 June 2023
Line 3:		Line 3:
	===System Architecture===		===System Architecture===

	[[File:MODBUS SLAVE integration topology v1.1.png\|center]]		[[File:MODBUS SLAVE integration topology v1.1.png\|center\|1058x1058px]]

	To implement this feature, we must properly implement the Teltonika '''[[Codec#Codec 12\|codec 12]]''' protocol in the server. In the device, we need to use '''TCP Binary''' mode. We need to primarily convert the Modbus commands to the '''Codec 12 GPRS commands''' and send them to the Teltonika device. The FM device (Teltonika device) will route these commands to the Modbus field device through '''RS232/RS485 serial interface'''. The response for the Modbus command from the field device will collect by the FM device, packed as a '''GPRS response''', and will send to the server by using Codec 12 protocol. In the server, we need to decode this data according to the Modbus protocol.		To implement this feature, we must properly implement the Teltonika '''[[Codec#Codec 12\|codec 12]]''' protocol in the server. In the device, we need to use '''TCP Binary''' mode. We need to primarily convert the Modbus commands to the '''Codec 12 GPRS commands''' and send them to the Teltonika device. The FM device (Teltonika device) will route these commands to the Modbus field device through '''RS232/RS485 serial interface'''. The response for the Modbus command from the field device will collect by the FM device, packed as a '''GPRS response''', and will send to the server by using Codec 12 protocol. In the server, we need to decode this data according to the Modbus protocol.

Naveen.rapheal: /* System Architecture */

2023-06-06T13:09:00Z

System Architecture

← Older revision		Revision as of 16:09, 6 June 2023
Line 3:		Line 3:
	===System Architecture===		===System Architecture===

	[[File:~~New System_Architecture~~.png\|center]]		[[File:MODBUS SLAVE integration topology v1.1.png\|center]]

	To implement this feature, we must properly implement the Teltonika '''[[Codec#Codec 12\|codec 12]]''' protocol in the server. In the device, we need to use '''TCP Binary''' mode. We need to primarily convert the Modbus commands to the '''Codec 12 GPRS commands''' and send them to the Teltonika device. The FM device (Teltonika device) will route these commands to the Modbus field device through '''RS232/RS485 serial interface'''. The response for the Modbus command from the field device will collect by the FM device, packed as a '''GPRS response''', and will send to the server by using Codec 12 protocol. In the server, we need to decode this data according to the Modbus protocol.		To implement this feature, we must properly implement the Teltonika '''[[Codec#Codec 12\|codec 12]]''' protocol in the server. In the device, we need to use '''TCP Binary''' mode. We need to primarily convert the Modbus commands to the '''Codec 12 GPRS commands''' and send them to the Teltonika device. The FM device (Teltonika device) will route these commands to the Modbus field device through '''RS232/RS485 serial interface'''. The response for the Modbus command from the field device will collect by the FM device, packed as a '''GPRS response''', and will send to the server by using Codec 12 protocol. In the server, we need to decode this data according to the Modbus protocol.

Naveen.rapheal: Protected "Modbus slave integration with FMX125/FMX640" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2023-05-26T06:06:50Z

Protected "Modbus slave integration with FMX125/FMX640" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 09:06, 26 May 2023
(No difference)

Naveen.rapheal: Created page with "we can use the '''FMX125/FMX640''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server si..."

2023-05-26T06:04:18Z

Created page with "we can use the '''FMX125/FMX640''' device‘s '''TCP - Binary''' feature to integrate the '''Modbus- RTU''' slave devices. If we can do some minor development on the server si..."

Show changes