Sensor Integration

Connect everything. Understand everything.

The Twynvex ingest layer connects natively to OPC-UA servers, MQTT brokers, Modbus TCP controllers, and REST APIs. It also includes connectors for OSIsoft PI and InfluxDB historians. No custom middleware, no proprietary data bus — just standard protocols running directly to the twin engine.

Supported Protocols

Six ways to connect to your plant.

OPC-UA

Native OPC-UA client with security policy enforcement, subscription management, and automatic node discovery. Supports Anonymous, Username, and Certificate authentication.

MQTT

MQTT 3.1.1 and 5.0 broker bridge with QoS 0, 1, and 2. Supports TLS, username/password auth, and configurable topic filtering with wildcard subscriptions.

Modbus TCP

Modbus TCP polling with configurable scan rates, coil and register mapping, and multi-unit-id support for legacy PLCs and field instruments.

REST API

HTTP/S REST endpoint for push ingestion from custom data sources, middleware, or existing data pipelines. JSON and CSV payload formats supported.

OSIsoft PI Connector

Direct read access to OSIsoft PI Data Archive via PI Web API or AF SDK. Tag subscription with configurable backfill for gap recovery after network interruptions.

InfluxDB

InfluxDB v1 and v2 line protocol, Flux queries, and bucket subscription. Supports both cloud and self-hosted deployments.

Configuration Example

Sample OPC-UA connection configuration.

The Twynvex agent reads a YAML configuration file on startup. Here is a minimal OPC-UA connector configuration for a distillation column process:

connectors:
  - id: column-c201-opcua
    protocol: opcua
    endpoint: opc.tcp://dcs-server-01.plant.local:4840
    security_mode: SignAndEncrypt
    security_policy: Basic256Sha256
    auth:
      type: certificate
      cert_file: /etc/twynvex/client.pem
    subscriptions:
      - node_id: ns=2;s=Plant.C201.TIC101.PV
        tag: c201_top_temp
        unit: degC
      - node_id: ns=2;s=Plant.C201.FIC201.PV
        tag: c201_reflux_flow
        unit: kg/h
      - node_id: ns=2;s=Plant.C201.PIC301.PV
        tag: c201_overhead_pressure
        unit: kPa
    scan_interval_ms: 1000
    reconnect_backoff_s: 15

The agent validates the configuration on startup, tests the OPC-UA connection, and confirms each node subscription before reporting ready to the twin engine. See the Quickstart Guide for full configuration reference.

Have an unusual protocol or historian?

If your plant runs something not on this list, talk to us. We've integrated with most of the installed base in continuous-process facilities. We'll tell you honestly whether it's feasible.

Request Pilot Access API Reference