MergenHub Envest
Home/Docs/User Manual (in-app, complete)

Connectivity

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.

ChannelModbus_1 (driver+network) DevicePLC / RTU (IP, unit) DevicePLC / RTU Tag 1 (address+type)Tag 2 (address+type)Tag 3 (address+type)
Figure 2 — Channel → Device → Tag hierarchy.
DriverThe channel's protocol (selected once).
Write optimizationMethod + duty cycle (at most N writes per cycle).
Socket sharingFor single-socket devices, one connection per channel (One-Socket-per-Channel).
Warning If both MergenHub and another server connect to the same site at the same time (e.g. a single-socket cellular gateway), one of them may be rejected (ECONNREFUSED). Use a single client for single-socket devices.
Limit The number of channels that can be opened with each driver is limited (e.g. Modbus TCP 1024, MQTT 60). Details: Channel and Device Limits.

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 CollectionTurn device scanning on/off (servermain.DEVICE_DATA_COLLECTION).
SimulatedSynthetic data without hardware (testing).
Tag GenerationAutomatic tag generation if the driver supports it (with address validation).
CopyDuplicate the device with all its tags/groups.
LimitThe 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.

DriverMax. channels · max. devices per channel
Modbus TCP/IP Ethernet1024 channels · 8192 devices
Modbus RTU Serial1024 channels · 255 devices
Modbus ASCII Serial100 channels · 247 devices
DNP Client Ethernet1024 channels · 1024 devices
IEC 60870-5-104 Client1024 channels · 1024 devices (stations)
IEC 61850 MMS Client256 channels · 256 devices
MQTT Client60 channels (broker connection) · 1024 devices
OMRON FINS Ethernet512 channels · 32 devices
OMRON NJ Ethernet256 channels · 1024 devices
Siemens S7 TCP/IP1024 channels · 1024 devices
OPC UA Client256 channels (session) · 256 devices
Simulator1024 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.

Scan time A channel scans its devices sequentially. On a crowded channel near the limit the scan cycle gets longer: in testing, 8192 Modbus TCP devices on a single channel were refreshed about every 40 s (even with a tag scan rate of 1 s). Split devices that need fast updates across multiple channels — channels run independently and in parallel (in the 1024-channel tests every value was refreshed within ≤1 s).
Tip Some drivers merge connections going to the same endpoint: in IEC 104, stations on the same IP:port share a single socket (the common address must differ for each station); in MQTT, channels going to the same broker use a single connection.

Tags

A tag is a variable bound to a single address on the device. The address format is driver-specific (see Protocols).

Data typeBoolean, Word, Short, DWord, Long, Float, Double, String…
AccessRead Only / Read-Write (industry standard: 0=RO, 1=RW).
Scan ratePer tag/group; can also be client-driven.
ScalingRaw 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.

PurposeSplits large devices into logical subsets (e.g. "Motors", "Temperatures") — makes it easier to navigate thousands of tags.
Parent GroupThe target group under which tags generated by automatic tag generation are placed.
Copy / moveA group can be duplicated together with all the tags in it.
Tip Since group names are also part of the OPC path, decide on group names early for address stability on the client side — renaming later breaks client paths (use Aliases for that).

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.

TypeNone (raw), Linear, Square Root (flow/pressure sensors).
Raw Lo/HiThe raw range coming from the device (e.g. 0–65535 or the raw equivalent of 4–20 mA).
Scaled Lo/HiThe engineering range (e.g. 0–100 m³/h).
Scaled Data Type / Clamp / NegateScaled 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).

Tip For raw 0–65535 on a 4–20 mA loop: Raw Lo/Hi = the sensor's raw values at 4 mA / 20 mA, Scaled Lo/Hi = engineering min/max. Clamp trims out-of-range noise.

Timing

Device timing matches the reference server one to one:

Request TimeoutWait time for a single request (ms). Retries if exceeded.
Attempts Before TimeoutApplies to connection and request attempts.
Inter-Request DelayBreathing room between requests; for slow devices.
Auto-Demotion / Failure BackoffBack-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-drivenA 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.