Skip to content

Acquire device tags and publish them northbound

Configure southbound channels, acquire and process tag samples, publish eligible nodes through OPC UA, and gate writes by identity, license, tag, and runtime state.

  • Channel → Device → Group → Tag
  • Multi-protocol architecture
  • Northbound OPC UA
Gateway
Channel
DeviceDevice
GroupGroupGroup
TagTagTagTag
AcquireProcessOPC UA
Configuration model Channel → Device → Group → Tag Persistent identity and hierarchy
Southbound paths Network · Serial · OPC UA Client Selected and validated per project
Northbound path OPC UA Server Components, certificates, and interoperability must be confirmed
Compatibility rule Device-specific validation Model, firmware, address, data type, and read/write

Implemented core capabilities

Hierarchical device model

Use Channel, Device, Group, and Tag layers to keep configuration and runtime identity explicit.

Multi-protocol southbound connectivity

Select isolated protocol factories per project and validate them against the target hardware.

Acquisition lifecycle

Coordinate start, stop, polling, subscriptions, reconnects, and session retirement.

Processing and deadband

Process samples and apply deadband rules before downstream publication.

Northbound OPC UA publishing

Publish eligible tags while controlling endpoint, node, republish, and write boundaries.

Controlled write pipeline

Validate identity, license, tag identity, data type, access level, and channel state before writing.

Guarded runtime changes

Use pending state, locks, write quiescence, scoped reloads, and convergence checks.

Capacity and diagnostics

Expose point counts, status, and diagnostics that explain blocked or failed behavior.

A clear four-step path

  1. 1

    Configure

    Create Channel, Device, Group, and Tag configuration.

  2. 2

    Acquire

    Start the selected protocol runtime and observe lifecycle status.

  3. 3

    Process

    Apply common sample handling and deadband behavior.

  4. 4

    Publish

    Publish eligible data through OPC UA and admit controlled writes.

Where this product fits

  • Multi-vendor device data aggregation
  • Modbus to OPC UA bridging
  • Edge sample processing and deadband
  • Guarded runtime configuration maintenance

Licensing, requirements, and boundaries

Licensing and editions

By licensed runtime points

Gateway runtime capacity is controlled by the point allowance in the license.

Protocol and hardware validation

The presence of a protocol implementation does not certify hardware compatibility; model, firmware, addresses, data types, and read/write behavior still require verification.

Component and security requirements

OPC UA components, certificates, trust, network segmentation, and service deployment must be confirmed per project.

Technical requirements

  • ASP.NET Core Web Host targeting net10.0.
  • Southbound connections include network, serial, and OPC UA Client paths; target permissions and drivers require validation.
  • Northbound OPC UA Server uses Softing components; licensing, certificates, trust lists, and interoperability require confirmation.
  • OS, hardware, storage, retention, service hosting, backup, and network-security baselines remain deployment-specific.