OPC UA
Secure sessions, namespace browsing, high-frequency subscriptions, and write operations for any OPC UA server.
Industrial IoT Gateway Software for Equipment Connectivity
IoTAutoGen solution
Connect mixed equipment once, and use the data everywhere.
Most plants run equipment from many makers and many years. IoTAutoGen puts a gateway at the edge that speaks their protocols, keeps data safe when the network drops, and passes clean, consistent data to the systems that use it.
Edge gatewayOne gateway for many protocols.OPC UA, SECS/GEM, Modbus, Profinet, MQTT, and serial.
The Challenge
Why connecting mixed equipment is hard
A single plant can have PLCs, sensors, serial devices, and modern machines, each with its own protocol and data format. Point-to-point connections multiply, and every new system needs its own adapter.
Networks drop, firewalls limit inbound access, and cloud services expect a different format than the equipment sends. Data gets lost, or arrives without the context needed to use it.
How It Works
A protocol gateway built into the platform
The gateway engine in IoTAutoGen is part of the platform, not a separate connector product. It translates OPC UA, SECS/GEM, Modbus, Profinet, EtherNet-IP, MQTT, and serial protocols into one data model in a single process, with no middleware required.
Runs on edge hardware, an industrial PC, or a gateway appliance
Store-and-forward buffering keeps messages in order during network loss
Edge pre-processing filters and aggregates data before it leaves the site
Forwards data over AMQP, MQTT, or HTTPS to cloud or on-premises targets
Capabilities
What is included
SECS/GEM
SECS/GEM message handling, the GEM state model, recipes, alarms, events, and host commands.
Modbus TCP and RTU
Poll and write registers across PLCs and field devices, with configurable scan rates and address translation.
Profinet and EtherNet-IP
Cyclic and acyclic data exchange with Profinet IO and EtherNet-IP devices.
MQTT
Bidirectional MQTT messaging with QoS control, topic mapping, and TLS.
Serial and legacy
RS-232 and RS-485, vendor protocols, and custom adapters for equipment with no standard interface.
Deployment
Integration and deployment considerations
Deployment modes. Run IoTAutoGen as the operational layer where there is no MES, connect it over your existing MES, SCADA, historian, ERP, and CMMS, or use a hybrid of both.
Security. Data in transit is encrypted, with certificate-based authentication and no inbound firewall ports required.
Remote management. Configure, update, and monitor edge agents without site visits.
Cloud targets. Forward data to Azure IoT Hub, AWS IoT Core, or a custom endpoint.
Equipment-specific adapters. Standard protocols are configured. Equipment with no standard interface may need an adapter that we validate or build during the project.
What Teams Get
Practical outcomes
One data model. Old and new equipment feed the same model, so downstream systems connect once.
Data without gaps. Buffered data is forwarded in order after a network loss.
Less cloud traffic. Filtering and aggregation at the edge send only meaningful events.
Start small. Connect a few machines first and expand at your own pace.
Use Cases
Where it fits
Collecting data from legacy equipment with no standard interfaceFeeding MES, analytics, or a historian from mixed equipmentConnecting remote sites with unreliable networksSending equipment data to a cloud IoT serviceRunning AI inference at the edge without sending raw data off site
Questions
Frequently asked questions
What protocols does the gateway support?
OPC UA, SECS/GEM, Modbus TCP and RTU, Profinet, EtherNet-IP, and MQTT, plus serial and legacy interfaces through custom adapters.
What happens when the network goes down?
The edge agent buffers data locally in order and forwards it without gaps when the connection returns. Buffer size and retention are configurable per deployment.
Does it need inbound firewall ports?
No. Data in transit is encrypted, and no inbound firewall ports are required.
Can it connect equipment with a proprietary interface?
Often yes, through serial and legacy support or a custom adapter that we validate for that equipment. We do not promise plug-and-play connectivity for every device.
Do I need to replace my MES or SCADA?
No. IoTAutoGen can sit alongside your existing MES, SCADA, historian, and ERP, or act as the operational layer where none exists.
Related
Keep exploring
SECS/GEM Integration
One host layer for fab tools from many makers.
View solutionPredictive Maintenance
Early warnings that come with the context to act on them.
View solutionIoTAutoGen
The product behind this solution.
Explore IoTAutoGenRead: From SCADA to LLMs, practical AI in operations
From the TCAIGV blog.
Read the articleTalk to us about your setup.
Tell us what you run today. We will show how this fits and what it would take.