Components > Driver > Modbus Slave

The Modbus slave driver is an invisible server component. Here it is possible to connect to this slave with other Modbus Gateways. All components that refer to the same interface (the COM port for serial or the combination of IP and port for the IP protocols) belong to the same Modbus network. The components must then all have a different device ID. Thus, several components within a network, as well as several components in different networks are supported.

Data points of the component

Name	Type	Function
Debug [Text]	Output	Caution: Diagnostics or debug outputs are only intended for the event of an error. Please use only after consultation with the support team! These may significantly affect the performance of the service when used.
Dynamic	Folder	The input and output channels are displayed in the folder Dynamic. Depending on the type, different data points are provided. The channels are structured according to register types.
Debug Verbose	Input	Unlocks the extended diagnostics.
Local IP	Bidirectional	The IP address of the driver can be changed here at runtime.
Driver on / off	Bidirectional	Driver on or off.
Driver status	Output	Outputs the connection status. undefined = driver off false = no connection true = connection exists

Properties of the component

Name	Standard	Function
Channels	0	The imported or manually created channels are listed here. These then appear in the data point folder Dynamic. The description of the Modbus channel editor follows below.
Connection	Serial ...	The connection type of the Modbus slave is set here (see below). Possible settings are: Modbus RTU (Serial), ASCII (Serial), TCP and UDP-IP (also Secure).
Device ID	1	Set Modbus Device ID.
Driver on / off		Defines whether the driver is activated automatically when the project is started.

Channel Editor

Name	Register Address [dec]	Datatype	Number of registers	Register-Type	Access Type	Bit Access
Channel001	1234	UInt16 AB	1	Input Register	Read/Write
...

Name:

Name of the channel which is displayed in the folder Dynamic in the communication window.

Register address [decimal]:

Address of the start register, from here the values are set. The address must be specified in decimal.

Data type:

The specific data type for the registers. If the data to be read is displayed in several registers, the data type must be adapted accordingly.

Number of registers:

Number of registers to be used.

Register type:

No function is specified. A function is only defined in the master and determines there, in which way which register blocks should be accessed. Instead, it indicates here which of the 4 register data sets (coils, discrete inputs, input registers or HoldingRegister) a channel belongs to.

Access type:

In addition to the register type, the access type can be used to define how a register can be accessed (read, write, both - inputs can of course only be accessed by reading)

Bit Access:

For UINT16 data types you can set whether these values should be accessed bitwise.

Import / Export:

When exporting, 2 files are created. Once the export file for the slave itself (.xml) as a data backup and then the xml file that can be imported in the Modbus master (_master.xml).