Connectivity

Edge & OT connectivity

Every Shop-Floor Protocol, One Gateway

The Fuuz Device Gateway is a proprietary on-premise software agent that provides bidirectional communication between the Fuuz cloud and local industrial equipment — remote configuration, automatic updates, and store-and-forward during network interruptions. Every major MES, SCADA, historian, PLC, robot and industrial gateway platform is reachable through it, either with a native driver or a validated bridge.

Edge vs. cloud. This page covers on-premise and shop-floor integration — PLCs, SCADA, sensors, historians, on-prem databases. For cloud-based SaaS and enterprise application connectivity (ERP, CRM, eCommerce, AI), see IT & Cloud Connectors.

Featured — recently added

The Fuuz Ignition Module

Ignition is already the best protocol match for Fuuz of any industrial platform — every Fuuz driver connects to it directly over OPC UA, MQTT, Sparkplug B, Modbus, HTTP and SQL. The Fuuz Ignition Module goes a step further.

Lives inside the gatewayAdvanced

Rather than an external client polling Ignition's OPC UA server, the Fuuz module installs directly inside the Ignition Gateway itself — the same architecture pattern as any other Ignition Gateway module, running alongside Ignition's own OPC UA, Sparkplug and tag systems rather than in front of them.

Creates the subscription, not just the read

A generic OPC UA browse-and-subscribe client only ever sees tags. The Fuuz Ignition Module creates the Fuuz-side DeviceSubscription directly from inside the gateway, so tag discovery and subscription management happen where the tag data already lives, not from a second hop outside it.

Same platform, less to run

No separate OPC UA client process to deploy, monitor and restart alongside Ignition. One module, installed once, inside the gateway you already operate.

The Fuuz Device Gateway

Native Drivers

Pluggable drivers on the gateway. Most industrial connectivity runs on OPC UA, MQTT and EtherNet/IP; the rest cover legacy PLCs, direct database access, and plain files.

DriverConnects toHow it works
OPC UA ClientOPC UA servers on PLCs, SCADA, historians, gatewaysConnects to any OPC UA server — the backbone of most industrial paths below.
EtherNet/IPAllen-Bradley / Rockwell PLCsReads and writes PLC tags directly via EtherNet/IP.
PCCCLegacy Allen-Bradley SLC/MicroLogixLegacy DF1/PCCC protocol for older controllers.
Modbus TCPAny Modbus TCP device — PLCs, sensors, meters, drivesDirect connection to Modbus TCP endpoints.
MQTT Client / BrokerMQTT brokers and endpointsSubscribes to and publishes on MQTT brokers — standard IoT messaging.
MQTT Sparkplug BSparkplug B compliant systemsThe standardized MQTT payload format defined by the Eclipse Sparkplug spec.
SAP RFCSAP systemsDirect SAP Remote Function Call — invokes BAPIs without middleware. See IT & Cloud for the separate SAP Cloud (S/4HANA) connector.
Microsoft SQL / MySQL / Oracle DB / IBM DB2On-premise databasesNative protocol per engine (TDS, MySQL protocol, Oracle Net, DRDA); Oracle requires the Oracle Instant Client.
HTTP Client / ServerREST/HTTP APIs; local webhook receiversCalls external endpoints, or receives HTTP POST requests and relays them into a data flow.
TCP Socket / ServerCustom protocol devices; inbound TCPRaw TCP communication, or subscribes to a port for incoming data.
Local FileThe file systemReads and writes CSV, XML, JSON and other flat files on the local machine.
Native Printer / TCP PrinterSystem and network printersOS print spooler, or a direct TCP port 9100 connection (Zebra, SATO, etc.).

Coverage

Key Industrial Platforms

OPC UA, MQTT and EtherNet/IP form the backbone. Every major SCADA, historian and MQTT platform is reachable through the drivers above.

PlatformVendorFuuz path
IgnitionInductive AutomationGateway OPC UA + MQTT + Sparkplug B + Modbus + HTTP + SQL, plus the Fuuz Ignition Module above — the best protocol match of any platform here.
AVEVA System PlatformAVEVAOPC UA, MQTT and Modbus via native drivers; Sparkplug B via the DataHub adapter.
Siemens WinCC / WinCC OASiemensOPC UA built in; MQTT via adapter; Modbus via driver.
GE Proficy HistorianGE DigitalOPC UA server built in — the Fuuz OPC UA driver connects directly.
OSIsoft PI (AVEVA PI)AVEVAPI Web API via the HTTP Client driver is the primary modern path.
KEPServerEXPTCThe Fuuz OPC UA driver connects to KEPServerEX's 160+ device drivers in one hop.
HiveMQHiveMQEnterprise MQTT broker; Fuuz MQTT and Sparkplug B drivers connect directly.
Cirrus LinkCirrus LinkAuthors of the Sparkplug B specification — native compatibility.
Opto 22 groov EPIC/RIOOpto 22Full driver coverage — native Sparkplug B, OPC UA, MQTT, REST and Modbus.

PLC manufacturers

ManufacturerPlatformFuuz path
Allen-Bradley / RockwellControlLogix, CompactLogixNative EtherNet/IP driver reads/writes CIP tags directly — the best PLC support Fuuz has.
SiemensS7-1200, S7-1500OPC UA built into the S7-1500; the proprietary S7 protocol needs an OPC UA bridge on older models.
Schneider ElectricModicon M340, M580Modbus, OPC UA and EtherNet/IP — Schneider invented Modbus, so this is a natural fit.
MitsubishiMELSEC iQ-R, iQ-FAn OPC UA module is available; native MC Protocol needs an OPC UA bridge.
OmronNX/NJ SeriesOPC UA built in — the Fuuz driver connects directly.
BeckhoffTwinCATOPC UA via TF6100; the proprietary ADS protocol needs an OPC UA bridge.
Phoenix ContactPLCnextExcellent coverage — every Fuuz industrial driver connects (OPC UA, EtherNet/IP, Modbus, MQTT).

Robots and gateway/bridge platforms

PlatformVendorFuuz path
FANUCRoboticsEtherNet/IP (R648) and OPC UA (R553) are paid FANUC options.
ABB RoboticsRoboticsBest coverage of any robot vendor — EtherNet/IP, OPC UA (RobotWare 7), MQTT via IoT Gateway, HTTP.
KUKARoboticsThe KUKA.OPC UA option is required; native KRL needs an OPC UA bridge.
Universal RobotsRoboticsModbus TCP built in; the URCaps ecosystem adds OPC UA/MQTT.
HMS AnybusGateway/bridgeBridges roughly 20 industrial networks, including PROFINET, DeviceNet and CC-Link, into OPC UA/MQTT/EtherNet/IP/Modbus.
Softing dataFEEDGateway/bridgeOPC UA specialist that also translates to MQTT.
Moxa / AdvantechGateway/bridgeProtocol conversion and serial-to-Ethernet, landing on OPC UA, Modbus, MQTT and EtherNet/IP.

Where a bridge is required

Protocols Fuuz Doesn't Speak Natively

Real, common protocols that need a translation step before they reach a Fuuz driver — usually landing on OPC UA or Modbus.

ProtocolCommon inRecommended bridge
PROFINETSiemens, European manufacturingHMS Anybus, Hilscher, or a Siemens OPC UA server → Fuuz OPC UA driver.
PROFIBUSLegacy Siemens, process industryPROFIBUS-to-Modbus gateway → Fuuz Modbus driver.
DeviceNetLegacy RockwellDeviceNet-to-EtherNet/IP gateway → Fuuz EtherNet/IP driver.
CC-LinkMitsubishi, Asian manufacturingCC-Link-to-OPC UA gateway → Fuuz OPC UA driver.
Siemens S7 nativeSiemens PLCsEnable OPC UA on the S7-1500 → Fuuz OPC UA driver.
FANUC FOCASFANUC CNC machinesKEPServerEX FOCAS driver → Fuuz OPC UA driver.
BACnetBuilding automationBACnet-to-Modbus or BACnet-to-OPC UA gateway.
HARTProcess transmittersHART-to-Modbus gateway or HART multiplexer → Fuuz Modbus driver.
KafkaStream processingKafka REST Proxy → Fuuz HTTP driver.
DNP3Utilities, electric SCADADNP3-to-Modbus gateway → Fuuz Modbus driver.
IEC 61850Power utility substationsIEC 61850-to-OPC UA gateway → Fuuz OPC UA driver.
Not on this list? If a device or platform speaks OPC UA, MQTT, Sparkplug B, EtherNet/IP or Modbus TCP anywhere in its stack — natively or through a vendor bridge — it reaches Fuuz through a driver already on the Device Gateway.