Channels
A project is a three-level hierarchy. A channel represents a single communication path and driver; its settings carry the network/serial parameters shared by all devices on that channel.
| Driver | The channel's protocol (selected once). |
| Write optimization | Method + duty cycle (at most N writes per cycle). |
| Socket sharing | For single-socket devices, one connection per channel (One-Socket-per-Channel). |
Devices
A device is a physical PLC/RTU/gateway on the channel. The address/identity (IP, unit id, rack/slot…) and timing are set at device level.
| Data Collection | Turn device scanning on/off (servermain.DEVICE_DATA_COLLECTION). |
| Simulated | Synthetic data without hardware (testing). |
| Tag Generation | Automatic tag generation if the driver supports it (with address validation). |
| Copy | Duplicate the device with all its tags/groups. |
| Limit | The number of devices that can be added to a channel depends on the driver (e.g. FINS 32, S7 1024, Modbus TCP 8192) — see Channel and Device Limits. |
Channel and Device Limits
For each driver, the maximum number of channels that can be opened and the maximum number of devices on a channel are limited. The values match the limits in the driver manuals of the industry-standard OPC server; the channel ceiling is additionally capped at 1024. The limit is per driver, not a project total: more channels can be opened in total by using different drivers.
| Driver | Max. channels · max. devices per channel |
| Modbus TCP/IP Ethernet | 1024 channels · 8192 devices |
| Modbus RTU Serial | 1024 channels · 255 devices |
| Modbus ASCII Serial | 100 channels · 247 devices |
| DNP Client Ethernet | 1024 channels · 1024 devices |
| IEC 60870-5-104 Client | 1024 channels · 1024 devices (stations) |
| IEC 61850 MMS Client | 256 channels · 256 devices |
| MQTT Client | 60 channels (broker connection) · 1024 devices |
| OMRON FINS Ethernet | 512 channels · 32 devices |
| OMRON NJ Ethernet | 256 channels · 1024 devices |
| Siemens S7 TCP/IP | 1024 channels · 1024 devices |
| OPC UA Client | 256 channels (session) · 256 devices |
| Simulator | 1024 channels · 999 devices |
When it is checked: only when adding — creating channels/devices (UI, REST API, AI assistant/MCP), copying and importing (Kepware JSON, project package, template). If the limit is reached, the operation is rejected, the reason is shown on screen, and the project is not changed at all. Nothing is rejected or deleted when an existing saved project is loaded; an old project that exceeds the limit keeps running, being edited and being deleted from — only new additions to that driver are blocked.
Verification: each value was tested at the limit itself with protocol simulators against a running MergenHub: all tags became Good, values updated without interruption, one more than the limit was rejected, and all connections were released on deletion. Since the limits are per driver, they were also tested with all drivers at their limits at the same time.
Tags
A tag is a variable bound to a single address on the device. The address format is driver-specific (see Protocols).
| Data type | Boolean, Word, Short, DWord, Long, Float, Double, String… |
| Access | Read Only / Read-Write (industry standard: 0=RO, 1=RW). |
| Scan rate | Per tag/group; can also be client-driven. |
| Scaling | Raw device value → engineering value (see Scaling). |
Bulk add: tags can be POSTed as an array (batch). An invalid tag is skipped and a skip report is kept (lenient import).
Tag Groups
Tags can be divided into groups ("Tag Group") under a device; groups can be nested. Each group appears as a folder in the OPC UA address space: the client accesses it through the path Kanal.Cihaz.Grup.Tag.
| Purpose | Splits large devices into logical subsets (e.g. "Motors", "Temperatures") — makes it easier to navigate thousands of tags. |
| Parent Group | The target group under which tags generated by automatic tag generation are placed. |
| Copy / move | A group can be duplicated together with all the tags in it. |
Scaling
Scaling converts the raw device value to an engineering unit ("Scaling"); it is set for this tag in the Scaling group of the property editor.
| Type | None (raw), Linear, Square Root (flow/pressure sensors). |
| Raw Lo/Hi | The raw range coming from the device (e.g. 0–65535 or the raw equivalent of 4–20 mA). |
| Scaled Lo/Hi | The engineering range (e.g. 0–100 m³/h). |
| Scaled Data Type / Clamp / Negate | Scaled type, lower/upper limiting (clamp), sign inversion. |
Linear: eng = (raw − rawLo)/(rawHi − rawLo) × (engHi − engLo) + engLo. If turned off, the raw value is used. Scaling is applied only to open (subscribed/scanned) tags (slot-based for performance).
Timing
Device timing matches the reference server one to one:
| Request Timeout | Wait time for a single request (ms). Retries if exceeded. |
| Attempts Before Timeout | Applies to connection and request attempts. |
| Inter-Request Delay | Breathing room between requests; for slow devices. |
| Auto-Demotion / Failure Backoff | Back-off that temporarily takes out a device that fails repeatedly. |
Scan Mode: Eager vs Demand-Driven
There are two scan behaviors (Settings → Scan):
| Eager (industry parity) | All enabled channels connect at startup and are scanned continuously — even without a consumer. Channels "always read". |
| Demand-driven | A device is scanned only while it has a consumer (OPC subscriber / UI / Logger); an idle device uses no socket/CPU/RAM. |
With an OPC client subscribed to all tags, both give about the same result in steady state; the difference is at startup and when there are no consumers. _System._DemandPoll and a pending write wake the device in both modes.
MergenHub