Parameters¶

Each device type in the Enture Platform supports a specific set of parameters. Parameters define how the device communicates, what data is exchanged, and how it is identified and managed within the platform. Each type of parameter will have its own type of data structure which will be in accordance to the protocol used.

Overview¶

Parameters are configuration properties that control device connectivity, data mapping, polling behavior, and protocol-specific settings required for reliable communication and monitoring. Each type of param is based on its corresponding protocol. e.g: S7 params are the parameters which are fetched via Seimens S7Comm protocol.

Modbus Device Parameters¶

Configuration settings required to read a register on a Modbus-enabled device. Connection details (IP/serial port, Slave ID) live on the device; each parameter defines register-level addressing and data access.

Common parameters include: - Register address and function code (Command) - Register size and byte format (word order) - Value / data type - Data processing (Average / Difference) - Correction factor and addition constant

See Modbus Parameters for the full field reference.

S7 Device Parameters¶

Parameters used to read a memory location on a Siemens S7 PLC. PLC connection details (IP, rack, slot) live on the device; each parameter defines the memory address to read.

Common parameters include: - Data block (DB) number - Byte offset and bit offset (for Bool values) - Value type and data length - Data processing (Average / Difference / Negative Difference) - Correction factor

See S7 Parameters for the full field reference.

MQTT Device Parameters¶

Settings that control MQTT-based communication using a publish–subscribe model. Broker connectivity and topic subscription are defined at the device level; each parameter identifies one field within the incoming payload.

Common parameters include: - Identifier (the field name/path within the payload) - Data type - Unit - Data processing (Average / Difference) - Correction factor and addition constant

See MQTT Parameters for the full field reference.

EtherNet/IP Device Parameters¶

Configuration properties for devices communicating over the EtherNet/IP protocol. These parameters define tag access using CIP.

Common parameters include: - Tag path - Value type - Read/write access mode - Polling interval - Timeout

See EtherNet/IP Parameters for the full field reference.

BACnet Device Parameters¶

Configuration properties for points of BACnet/IP controllers. These parameters identify a point by its object type and number.

Common parameters include: - Object type and object instance - Access (read only, write only, read and write) - Write priority - Read interval

See BACnet Parameters for the full field reference.

Virtual / OPC UA Device Parameters¶

Parameters for OPC UA server connections (Virtual Devices). Server connectivity, security, and authentication are configured on the device; each parameter identifies one node to read.

Common parameters include: - Node ID - Data type - Data processing (Average / Difference) - Correction factor and addition constant

See OPC UA Parameters for the full field reference.

Parameters reported to an integration¶

A parameter that is mapped to a field of an integration plant, for example the GOBARdhan Portal, shows a Reported to … badge on the parameter screens. Hover over the badge to see which plant and field use it, and click it to open that plant's field mapping.

Such a parameter can't be deleted: its delete action is disabled, and Enture explains why. Deleting it would stop the plant's reports. To delete it:

1. Open the plant (click the badge), go to Field mapping, and map that field to another parameter, or
2. remove the plant (Settings → Remove plant), which releases all its parameters.

Monitoring a parameter's health¶

Any parameter can be watched against the range — or the set of values — it is supposed to be in, with a permanent record of every deviation and who explained it. This works for parameters that report text or status codes as well as numeric ones.

See Parameter Health.