Controller and CNC gateways
Read data from supported controllers and CNC systems and present it through standardized interfaces.
Expose controller, CNC, fieldbus and process data through governed industrial interfaces without replacing the installed automation layer.
PLCs, CNCs, fieldbus and device networks
Translate, aggregate and govern access
OPC UA, MQTT and industrial protocols
SCADA, edge applications and IT systems
The portfolio covers controller and CNC access, protocol gateways, OPC UA and MQTT software, hardware and containerized edge connectivity, industrial-network diagnostics, and embedded communication for OEM devices.
Read data from supported controllers and CNC systems and present it through standardized interfaces.
Bridge selected industrial protocols where installed assets and new systems must coexist.
Provide OPC UA, OPC Classic and related data services for supervisory and IT applications.
Deploy controller connectors and aggregation services on supported Docker-capable edge platforms.
Commission and troubleshoot industrial networks with protocol-aware test and monitoring tools.
Integrate industrial Ethernet and fieldbus functions into devices through modules, stacks and SDKs.
The same connectivity layer must expose useful controller data and provide the diagnostics needed to commission and maintain the underlying industrial network.
Aggregate data from supported PLC and CNC sources and provide standardized OPC UA and MQTT access from Windows, Docker or a dedicated gateway deployment.
Test cabling, physical signal quality and protocol communication, then retain the results as a practical commissioning or troubleshooting record.
Select the communication layer from the installed controllers, field networks, data consumers, timing requirements and cybersecurity policy.
Access legacy PLC and CNC information without adding logic changes solely for data extraction.
Translate plant data into OPC UA or MQTT for SCADA, MES, analytics and cloud services.
Provide parallel access to selected field information where the architecture permits it.
Add protocol support to controllers, instruments and gateways through embedded communication technology.
A gateway is selected by protocol role, data ownership and fault behaviour—not only by the connector or protocol list.
Connect supported PLC and CNC families and expose data through OPC UA or MQTT.
Translate between selected protocols such as PROFIBUS and Modbus where a direct device upgrade is not practical.
Read selected process-network data without moving control responsibility away from the established controller.
Define startup, reconnect, stale-data and communication-loss handling before deployment.
Controller connectivity turns proprietary or controller-specific data into a consistent interface for applications above the machine layer.
Use supported native drivers for PLC and CNC families where an existing OPC UA server is unavailable.
Expose only the tags and structure needed by the consuming application.
Separate monitoring-only access from authorized command paths and document write ownership.
Match scan time, tag count and update behaviour to controller resources and application needs.
OPC UA provides a structured industrial data interface with built-in security mechanisms when certificates, users and policies are configured correctly.
Publish controller and machine data to OPC UA clients using a defined namespace.
Collect data from multiple servers and normalize it for higher-level systems where supported.
Use certificates, encryption, authentication and role-based access appropriate to the deployment.
Preserve engineering units, status and equipment structure instead of exposing an unorganized tag list.
MQTT is suitable for event and telemetry transfer, while control and safety functions should remain within the deterministic automation architecture.
Exchange selected machine or process data through an MQTT broker.
Configure TLS, certificates and authentication for the chosen broker and network.
Use standards-based MQTT and a documented topic and payload model to reduce dependency on a specific private or public cloud platform.
Filter, aggregate and rate-limit published information at the edge.
Current edge deployments can use the Softing SDEX Suite across Windows, Docker or dedicated gateway environments, allowing the deployment model to follow the plant and IT architecture.
Run the integration layer on a supported host or appliance while keeping controller access and northbound data services within one managed configuration.
Use web and API interfaces to configure data sources, security and destinations.
Combine multiple controller connections before forwarding selected data upstream.
Plan container versioning, credentials, backups and update responsibility as part of operations.
Protocol-aware diagnostics help separate physical, timing, configuration and application faults during commissioning and maintenance.
Inspect signal, telegram and participant behaviour on supported networks.
Check topology, connection state and protocol events on supported Ethernet-based systems.
Capture baseline measurements after commissioning for comparison during later troubleshooting.
View Softing communication products →Use permanent monitoring where intermittent faults justify an installed diagnostic layer.
Device manufacturers can add industrial protocol functions through modules, software stacks or FPGA subsystems matched to the product architecture.
Use pre-engineered hardware to shorten device-level industrial Ethernet integration.
Integrate supported protocols into existing processors and operating systems.
Add deterministic communication blocks to supported FPGA platforms.
Include profile, certification and interoperability testing in the product development plan.
A reliable connectivity project starts with a source inventory, data model, access policy, security design and acceptance tests for normal operation and communication failures.
Record controller type, protocol, address model, tag count and permitted access.
Define names, units, quality, timestamps and equipment hierarchy.
Place gateways in the correct zone and manage certificates, users, ports and remote access.
Verify data accuracy, update time, reconnect behaviour and write restrictions end to end.