ToddySoft Connect
Industrial Protocol Drivers
Bridge the gap between legacy industrial systems and modern infrastructure with our comprehensive suite of protocol drivers.

Connect Any Industrial Device
ToddySoft Connect provides a unified interface for communicating with industrial equipment, regardless of the underlying protocol.
Industrial environments are complex, with equipment from different vendors using various communication protocols. ToddySoft Connect eliminates this complexity by providing standardized drivers that translate between these protocols and modern data formats.
Whether you're working with PLCs, SCADA systems, sensors, or other industrial devices, ToddySoft Connect gives you a consistent API to read and write data, monitor status, and receive events.
Apache PLC4X Compatible: All ToddySoft Connect drivers are API-compatible with Apache PLC4X. If your system already uses PLC4X, you can seamlessly integrate our commercial drivers as drop-in replacements.
Supported Protocols
A growing list of industrial protocols, with more being added regularly.
BACnet
In Progress
Building automation protocol for HVAC, lighting, and access control systems.
Beckhoff ADS
Direct communication with Beckhoff TwinCAT PLCs and I/O systems.
Bosch-Rexroth CtrlX
Integration with Bosch Rexroth CtrlX automation platform.
C-Bus
In Progress
Schneider Electric building automation protocol for lighting and HVAC control.
EtherCAT
Planned
High-performance industrial Ethernet technology for real-time automation.
EtherNet/IP
Connect to Allen-Bradley and other CIP-based devices over Ethernet.
Firmata
Protocol for communicating with microcontrollers like Arduino.
IEC 60870
In Progress
Telecontrol protocol for SCADA systems in power utility automation.
IO-Link
Planned
Point-to-point communication standard for sensors and actuators.
KNXnet/IP
Standard protocol for smart building and home automation systems.
Modbus
Support for Modbus TCP and RTU, connecting to a vast ecosystem of industrial devices.
OPC UA
In Progress
The modern standard for industrial interoperability with built-in security and information modeling.
Open Protocol
In Progress
Communication with Atlas Copco tightening controllers and tools.
Profinet
In Progress
Industrial Ethernet standard for factory automation and process control.
Siemens S7
Native communication with Siemens S7-300, S7-400, S7-1200, and S7-1500 PLCs.
Flexible Integration Options
Use ToddySoft Connect drivers in the way that best fits your needs.
License Drivers Directly: Integrate our protocol drivers into your own applications using the Apache PLC4X-compatible API. Perfect for custom software development and OEM integrations.
Pre-built Integration Modules: Get up and running quickly with ready-made modules for popular industrial platforms and data integration tools.
Platform Integrations
Ready-to-use modules for leading industrial and data integration platforms.
Apache Camel
Integration component for Apache Camel enterprise integration patterns.
Apache Kafka Connect
Connector for Apache Kafka distributed streaming platform.
Apache NiFi
Processors for Apache NiFi data flow automation.
Apache StreamPipes
Adapters for Apache StreamPipes industrial IoT analytics.
CodeSys
Planned
Integration for CodeSys-based automation systems.
CtrlX
Planned
App for Bosch Rexroth CtrlX automation platform.
Eclipse Ditto
Planned
Integration for Eclipse Ditto digital twin framework.
Eclipse Kura
Planned
Driver bundle for Eclipse Kura IoT edge framework.
Inductive Automation Ignition
In Progress
Module for Ignition SCADA platform.
Phoenix Contact PLCnext
Planned
App for Phoenix Contact PLCnext Technology platform.
Schneider Electric EcoStruxure
Planned
Integration for EcoStruxure Automation Expert.
Siemens Industrial Edge
Planned
App for Siemens Industrial Edge ecosystem.
Key Features
Unified API
One consistent interface for all protocols, reducing integration complexity.
High Performance
Optimized for industrial workloads with support for high-frequency data acquisition.
Secure by Design
Built-in support for authentication, encryption, and secure communication — implemented wherever the protocol supports it.