UC-08 · Plant-standard protocols

Integration APIs

Vision data is only valuable when it reaches the system that acts on it — your PLC, your MES, your historian, your ERP. InspXion speaks the protocols those systems speak: OPC UA, MQTT, REST, SQL stored procedures, Profinet, EtherNet/IP, Modbus TCP. No middleware. No PC-as-bridge. No custom integration project.

REC INSPXION OV-03 LIVE INSPXION OV-03 · INTEGRATION APIS REAL-TIME 0% LOSS LIVE InspXion OPC UA MES · ERP MQTT HISTORIAN REST DASHBOARD SQL PROCEDURES SPEC PROTOCOLS OPC UA · MQTT PLC NATIVE PROFINET LATENCY <150 ms AUDIT 21 CFR P11 PASS · 4 / 4 OK EVENTS/MIN 1,218 LATENCY 138 ms UPTIME 99.94%
Why it matters

Most vision systems require a PC running a script to talk to your plant.

That PC becomes a single point of failure, a security exposure, and a maintenance burden. Native protocol support eliminates the PC entirely. The camera writes to your PLC, MES, or historian directly — using the standards your IT and OT teams already manage.

Two paths to the same outcome

Retrofit, or build it in from the start.

Retrofit · use what you have

If you have an existing vision system that needs better integration.

We provide a protocol gateway that sits between your existing vision system and your plant systems. The gateway translates vendor-proprietary outputs into OPC UA, MQTT, or your protocol of choice — without modifying the vision system itself. Your existing camera + AI + integration stack stays; we add the standards-compliant interface on top.

  • Gateway accepts inputs from major vision OEMs (Cognex, Keyence, Basler, Allied Vision)
  • Outputs: OPC UA · MQTT · REST · SQL · Profinet · EtherNet/IP · Modbus
  • ISA-95 conformant — slots into existing MES architectures
  • Zero modification to existing vision system
  • Hardened gateway: industrial DIN-rail mount, -10°C to +60°C, 24V DC
Greenfield · spec from scratch

If you're designing a new line from scratch.

Every InspXion camera is a first-class citizen on your plant network. Native OPC UA server, native MQTT publisher, native REST endpoint, native PLC protocol — all built into the camera firmware. Specify it in the protocol your IT team already supports; commission it with the tools your OT team already uses.

  • Native OPC UA server on every camera
  • Native MQTT publisher to your historian / IoT broker
  • Native PLC protocols: Profinet · EtherNet/IP · Modbus TCP
  • REST API for downstream systems and dashboards
  • Discoverable via OPC UA discovery, mDNS, BACnet/IP
How it works

Four steps from camera to verdict.

01

Detect

Vision system produces a verdict (pass/fail/measurement/count).

02

Translate

Verdict + metadata mapped to the target protocol's schema (OPC UA address space, MQTT topic, etc.).

03

Publish

Verdict written to the target system in real time. Multiple targets in parallel if required.

04

Confirm

Acknowledgment received from target system. Audit log written for traceability.

Compatible with

The InspXion stack for this use case.

Ready to put this into production?

Get a sized configuration in 48 hours.

Tell us your line, your existing equipment, and your tolerance window. We'll come back with a retrofit assessment, a greenfield specification, and a rough cost estimate within two business days.