Configuration
The Configuration section determines the Data source selection and addressing.
The Configuration section defines where the Tag connects and how it addresses the source for data collection or output. In practice, you bind the Tag to a specific Data Connector and supply the address that identifies the exact datapoint or endpoint. The format and type of the address depends on the Data Connector, and the underlying protocol.

What’s generally configured here
Data Connection: Select the Data Connection instance (created on an Area in a higher location in the Asset Hierarchy) that this Tag will use. The instance carries endpoint details, credentials, and protocol defaults; the Tag provides the precise address within that source.
Addressing: Specify the address (node, register, topic etc., depending on the protocol) that identifies the datapoint. Addressing rules depend on the connector type (see per-connector subsections).
Read vs. Write in Configuration
Read: The Tag subscribes/polls the configured address and ingests the resulting values as measurements.
Write: The Tag publishes/sends values from a specified Tag to the configured address, acting as a command or setpoint.
If the Tag is configured as a Write Tag the Source Tag must always be specified. The Source Tag name selects what to output to the destination address, by sending all measurements produced by the selected Tag to the destination address.

Supported Data Connectors
Choose one of the following connector types; each has its own addressing model and options:
MQTT — Bind to a topic for subscribing (Read) or publishing (Write) JSON formatted data.
OPC UA — Reference items on an OPC-UA server for read / write operations.
Modbus TCP/RTU — Map to addresses on a Modbus slave, supporting both read and writes.
Equation — Virtual Tag (read only) that produces measurements computed from an expression referencing other Tags; useful for derived values without changing field devices.
Emulator — Synthetic read-only data source for testing and demos, generating measurements without requiring external connections.
Each connector has a dedicated subsection explaining its UI, required fields, and exact addressing syntax.
Last updated
Was this helpful?