Connectivity
Speaks your factory’s language.
TAP connects the equipment you already have — over the industrial protocols it already speaks. No forklift upgrades, no proprietary gateways.
Protocol catalog
The protocols TAP connects.
Core protocols are first-class and proven in production. Extended protocols are part of the catalog and delivered as connectors on request.
Field & fieldbus
- Modbus TCP
PLCs, drives, power meters and I/O over Ethernet.
Supported - Modbus RTU
Serial RS-485 sensors, meters and legacy controllers.
Supported - OPC-UA
Modern PLCs and SCADA servers with typed address spaces.
Supported - MQTT
Edge devices and brokers publishing telemetry topics.
Supported - Profinet
Siemens and other Profinet-IO field devices.
On request - EtherNet/IP
Allen-Bradley / Rockwell controllers and CIP devices.
On request - OPC-DA / Historian
Classic OPC servers and existing plant historians.
On request - LoRaWAN
Long-range battery sensors via a LoRaWAN network server.
On request
Building automation
- BACnet/IP
HVAC, chillers, metering and BMS points.
On request
Database & API
- REST API
HTTP/JSON endpoints from apps, MES and third-party services.
Supported - SQL Server
Poll tables and views from Microsoft SQL Server.
Supported - PostgreSQL / MySQL
Read from existing relational production databases.
Supported - File / CSV / Excel
Watched folders, exports and spreadsheet drops.
Supported
Utility & power
- DNP3
Substation RTUs and SCADA in utility networks.
On request - IEC 61850
Protection relays and IEDs in electrical substations.
On request - SNMP
Network gear, UPS and infrastructure health.
On request
How connectors work
Poll. Normalise. Publish.
Every connector follows the same three moves — so the platform sees one clean stream, whatever the equipment underneath.
The Gateway polls the device
On a fixed scan cycle, the TAP Gateway reads registers or points straight from the equipment — over its native protocol, no rip-and-replace.
It normalises the reading
Each raw value is scaled, typed and tagged into one consistent shape — so a Modbus register and an OPC-UA node look identical downstream.
It publishes to the platform
The normalised reading is published to the MQTT broker on a tenant-isolated topic, ready for storage, alarms and live dashboards.
Connectors on request
Don’t see your protocol?
We build connectors on request. Tell us the equipment and the protocol it speaks, and we’ll scope a connector that lands its data in the same clean stream as everything else.
Your equipment already speaks. TAP listens.
Bring the protocols you run today. We'll show TAP reading them live in 15 minutes.