Modbus TCP/IP to NVGate - Revision history

Lmagimel at 08:56, 26 November 2024

2024-11-26T08:56:27Z

← Older revision		Revision as of 10:56, 26 November 2024
Line 1:		Line 1:
			[[category:WikiOros]]
	This add-on allows NVGate to read inputs with Modbus TCP/IP protocol. It converts bus values to Simulated DC input and can be used as physical inputs in NVGate, which are synchronized with dynamic / parametric / Ext. sync. channels acquired from OR3X or O4 analyzer. It supports all the Modbus register types. This add-on can also update or create properties that are metadata stored in the NVGate measurements. The metadata can be computed from one bus value (min, max, average, first, last) or can be read from a file. <br>		This add-on allows NVGate to read inputs with Modbus TCP/IP protocol. It converts bus values to Simulated DC input and can be used as physical inputs in NVGate, which are synchronized with dynamic / parametric / Ext. sync. channels acquired from OR3X or O4 analyzer. It supports all the Modbus register types. This add-on can also update or create properties that are metadata stored in the NVGate measurements. The metadata can be computed from one bus value (min, max, average, first, last) or can be read from a file. <br>
	[[File:modbus-drawing.png\|800px]]		[[File:modbus-drawing.png\|800px]]

ChaoranDu: /* Download */

2024-06-06T07:09:30Z

Download

← Older revision		Revision as of 09:09, 6 June 2024
Line 4:		Line 4:

	==Download==		==Download==
	[https://~~orossas~~.~~sharepoint~~.com/~~:u:~~/g/~~support/EfXYG0x~~-~~txpKnOlRb5KxPtYB~~-~~gS_OBmEv570lsjsVGRLZA?e=wAMMkP~~ Download here]<br>		[https://my.oros.com/categories/software/modbus-tcp-ip/ Download here]<br>

	==Requirements==		==Requirements==

ChaoranDu at 11:39, 4 June 2024

2024-06-04T11:39:57Z

← Older revision		Revision as of 13:39, 4 June 2024
Line 10:		Line 10:
	* Modbus to NVGate add-on.		* Modbus to NVGate add-on.
	* Your own TCP/IP Modbus server or the demo server provided with Modbus to NVGate.		* Your own TCP/IP Modbus server or the demo server provided with Modbus to NVGate.
	* The PC running the Modbus TCP/IP client add-on should host at least 2 Ethernet connectors. One is dedicated for OR3X analyzer, and the other is for establishing connection to the Modbus server. The Modbus server is identified with an IP address and a port number.

	==Procedure==		==Procedure==

ChaoranDu at 11:37, 4 June 2024

2024-06-04T11:37:42Z

← Older revision		Revision as of 13:37, 4 June 2024
Line 5:		Line 5:
	==Download==		==Download==
	[https://orossas.sharepoint.com/:u:/g/support/EfXYG0x-txpKnOlRb5KxPtYB-gS_OBmEv570lsjsVGRLZA?e=wAMMkP Download here]<br>		[https://orossas.sharepoint.com/:u:/g/support/EfXYG0x-txpKnOlRb5KxPtYB-gS_OBmEv570lsjsVGRLZA?e=wAMMkP Download here]<br>


	==Requirements==		==Requirements==
Line 14:		Line 13:

	==Procedure==		==Procedure==

	Please follow the following steps:		Please follow the following steps:

ChaoranDu at 11:34, 4 June 2024

2024-06-04T11:34:07Z

← Older revision		Revision as of 13:34, 4 June 2024
Line 64:		Line 64:

	[[File:modbus_3.png]]		[[File:modbus_3.png]]

			===Properties file===
			A JSON file giving the value of some properties. The method of the property must be ‘file’.

			===Unit file===
			The conversion coefficient between the units from MODBUS and the NVGate default unit (in International System of Units, SI).

			===ModbusToNVGate.ini===
			The ModbusToNVGate.ini file contains:
			* Server IP and port.
			* NVGate server IP and port (when NVGate is executed on a different PC from the Modbus to NVGate add-on)
			* Modbus RTU mode (advanced usage): enable RTU mode with 1.

ChaoranDu at 11:32, 4 June 2024

2024-06-04T11:32:18Z

← Older revision		Revision as of 13:32, 4 June 2024
Line 62:		Line 62:
	** Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file.		** Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file.
	** # digits after dot: value rounding.		** # digits after dot: value rounding.

			[[File:modbus_3.png]]

ChaoranDu at 11:31, 4 June 2024

2024-06-04T11:31:09Z

← Older revision		Revision as of 13:31, 4 June 2024
Line 47:		Line 47:
	===Input file===		===Input file===
	This file contains the list of data to be read from the server:		This file contains the list of data to be read from the server:
	• General		* General
	o Label: Name of the input displayed in NVGate.		** Label: Name of the input displayed in NVGate.
	o User unit: the unit as described in the Units.xlsx		** User unit: the unit as described in the Units.xlsx
	o Min value and Max value: The minimum and maximum value (expressed in user unit). The min value must correspond to Bus data min, and the max value must correspond to Bus data max, i.e., if a temperature in [-20, 100] can be encoded on the bus with values in [-200, 1000]. So, range min = -20 and max = 100.		** Min value and Max value: The minimum and maximum value (expressed in user unit). The min value must correspond to Bus data min, and the max value must correspond to Bus data max, i.e., if a temperature in [-20, 100] can be encoded on the bus with values in [-200, 1000]. So, range min = -20 and max = 100.
	• Modbus input
	o Address: the register address.		* Modbus input
	o Type: type of MODBUS request (among Discrete Input, Internal Bits, Holding Register, Input Register).		** Address: the register address.
	o Bit: for Discrete Input or Internal Bits, the position of the bit in the register		** Type: type of MODBUS request (among Discrete Input, Internal Bits, Holding Register, Input Register).
	o Bus min, Bus max: Bus data: see range (in this example, the values must be min = -200 and max = 1000).		** Bit: for Discrete Input or Internal Bits, the position of the bit in the register
	• NVGate Simulated DC number: Must be in [1, 32].		** Bus min, Bus max: Bus data: see range (in this example, the values must be min = -200 and max = 1000).
	• Measurement properties (the parameters are metadata written in the measurement when the recording stops. They are accessible from Measurement Properties in NVGate.)		* NVGate Simulated DC number: Must be in [1, 32].
	o Name: the name displayed in NVGate.		* Measurement properties (the parameters are metadata written in the measurement when the recording stops. They are accessible from Measurement Properties in NVGate.)
	o Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file.		** Name: the name displayed in NVGate.
	o # digits after dot: value rounding.		** Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file.
			** # digits after dot: value rounding.

ChaoranDu at 11:29, 4 June 2024

2024-06-04T11:29:49Z

← Older revision		Revision as of 13:29, 4 June 2024
Line 40:		Line 40:

	[[File:modbus_2.png]]		[[File:modbus_2.png]]


			===Recording===
			The add-on detects Recording starts and stops in NVGate. When properties are defined in the Input file, they are updated when the recording stops.

			===Input file===
			This file contains the list of data to be read from the server:
			• General
			o Label: Name of the input displayed in NVGate.
			o User unit: the unit as described in the Units.xlsx
			o Min value and Max value: The minimum and maximum value (expressed in user unit). The min value must correspond to Bus data min, and the max value must correspond to Bus data max, i.e., if a temperature in [-20, 100] can be encoded on the bus with values in [-200, 1000]. So, range min = -20 and max = 100.
			• Modbus input
			o Address: the register address.
			o Type: type of MODBUS request (among Discrete Input, Internal Bits, Holding Register, Input Register).
			o Bit: for Discrete Input or Internal Bits, the position of the bit in the register
			o Bus min, Bus max: Bus data: see range (in this example, the values must be min = -200 and max = 1000).
			• NVGate Simulated DC number: Must be in [1, 32].
			• Measurement properties (the parameters are metadata written in the measurement when the recording stops. They are accessible from Measurement Properties in NVGate.)
			o Name: the name displayed in NVGate.
			o Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file.
			o # digits after dot: value rounding.

ChaoranDu at 11:28, 4 June 2024

2024-06-04T11:28:08Z

← Older revision		Revision as of 13:28, 4 June 2024
Line 32:		Line 32:

	[[File:modbus.png]]		[[File:modbus.png]]

			8. In NVGate, in the analyzer Setting Browser / Front end / Simulated DC Inputs, you’ll see that Simulated DC Values are collected.

			[[File:modbus_1.png]]

			From Acquisition / Connect Inputs, you can drag and drop the DC simulated channels (in the DC inputs tab) in a module (Recorder for example):

			[[File:modbus_2.png]]

ChaoranDu at 11:22, 4 June 2024

2024-06-04T11:22:38Z

← Older revision		Revision as of 13:22, 4 June 2024
Line 31:		Line 31:
	7. Click on start.		7. Click on start.

	[[File:~~modbus_1~~.png]]		[[File:modbus.png]]