Resources

Connect to Any Industrial Device

TwinEdge connects validated industrial source families including OPC UA, Modbus, MQTT, and file-based exchange. Additional protocol requirements are reviewed with your team during deployment planning.

Supported Protocols

OPC UA

Unified architecture for industrial automation with service-oriented design. Platform-independent with rich information modeling.

Transport:opc.tcp
Port:4840
Mode:Subscription + Polling

Modbus TCP

Industry-standard protocol for industrial electronic devices. Simple master-slave architecture with register-based data model.

Transport:TCP
Port:502
Mode:Polling

Modbus RTU

Serial variant of Modbus for legacy equipment and long-distance industrial networks. Compact binary encoding for efficiency.

Transport:Serial (RS-485)
Port:
Mode:Polling

MQTT

Lightweight pub-sub messaging protocol for IoT. Minimal bandwidth requirements with QoS levels and retained messages.

Transport:TCP
Port:1883 / 8883 (TLS)
Mode:Publish-Subscribe

File / CSV Exchange

Batch exchange for no-cloud or historian-export workflows where files are the practical integration point.

Transport:Local filesystem
Port:
Mode:Watch + batch publish

Protocol Comparison Matrix

ProtocolTransportPortSecurityData ModelModeCommon Devices
OPC UATCP4840X.509, Sign & EncryptObject-orientedSubscription + PollingSiemens, Rockwell, Kepware
Modbus TCPTCP502Network-levelRegister-basedPollingSchneider, ABB, Danfoss
Modbus RTUSerial RS-485PhysicalRegister-basedPollingLegacy PLCs, VFDs, Meters
MQTTTCP1883/8883TLS 1.2+Topic-basedPub-SubAWS IoT, Azure IoT, Custom
File / CSVLocal filesystemHost/share permissionsRecordsWatch + batchHistorian exports, lab files

Protocol Details

OPC UA

asyncua 1.1.0

Unified architecture for industrial automation with service-oriented design. Platform-independent with rich information modeling.

Use Cases

SCADA integration, multi-vendor interoperability, enterprise MES/ERP connectivity

Compatible Devices

Siemens SIMATIC, Rockwell FactoryTalk, Kepware servers, Ignition SCADA, B&R Automation

Transport: opc.tcp
Port: 4840
Security: None, Sign, SignAndEncrypt (X.509)
Data Model: Object-oriented, hierarchical namespace

Modbus TCP

pymodbus 3.6.2

Industry-standard protocol for industrial electronic devices. Simple master-slave architecture with register-based data model.

Use Cases

PLCs, RTUs, meters, sensors, VFDs, building automation

Compatible Devices

Schneider Electric, ABB, Danfoss, Siemens PLCs, Carlo Gavazzi meters, Phoenix Contact I/O

Transport: TCP
Port: 502
Security: Network-level
Data Model: Register-based (Coils, Discrete Inputs, Holding/Input Registers)

Modbus RTU

pymodbus 3.6.2

Serial variant of Modbus for legacy equipment and long-distance industrial networks. Compact binary encoding for efficiency.

Use Cases

Legacy PLCs, remote sensors, distributed I/O, serial-connected meters

Compatible Devices

Schneider Electric, ABB, Danfoss VFDs, Carlo Gavazzi energy meters, Watlow controllers

Transport: Serial (RS-485)
Port:
Security: Physical layer
Data Model: Register-based (Coils, Discrete Inputs, Holding/Input Registers)

MQTT

aiomqtt 2.0.0

Lightweight pub-sub messaging protocol for IoT. Minimal bandwidth requirements with QoS levels and retained messages.

Use Cases

Cloud connectivity, distributed sensors, edge-to-cloud sync, IoT device integration

Compatible Devices

AWS IoT Core, Azure IoT Hub, Ignition SCADA, MQTT brokers, custom IoT devices

Transport: TCP
Port: 1883 / 8883 (TLS)
Security: TLS 1.2+, Username/Password
Data Model: Topic-based publish-subscribe

File / CSV Exchange

TwinEdge collector profile

Batch exchange for no-cloud or historian-export workflows where files are the practical integration point.

Use Cases

Historian exports, lab files, batch reports, offline site uploads

Compatible Devices

File shares, historian export jobs, lab systems, operations folders

Transport: Local filesystem
Port:
Security: Host and share permissions
Data Model: File records normalized into source events

Protocol Features

Auto-Discovery

Deployment workflows support source discovery and profile-driven setup for supported connectors, with mapping reviewed during activation.

Secure Communications

OPC UA supports certificate-based security, MQTT can use TLS, and file exchange follows host and share-level controls.

Deployment-Scoped Performance

Polling, subscription, buffering, and batch settings are sized for the site, source system, network, and edge host.

Don't See Your Protocol?

Bring us your protocol requirements, security constraints, available drivers, and validation needs. We will confirm the best integration path before deployment.