Visual Intelligence Summit: Oct 22 in San Francisco Get your ticket (opens in a new tab)

Roboflow + Matrikon OPC

Write detections, counts and pass or fail results to MatrikonOPC servers through Matrikon OPC UA Tunneller, so the devices and clients behind them can use them.

Matrikon, part of Honeywell, makes OPC servers for devices and systems such as Modbus, DNP3 and Allen-Bradley PLCs, along with Matrikon OPC UA Tunneller, which bridges OPC Classic and OPC UA. The Tunneller's UA-to-Classic Bridge exposes classic OPC DA servers as folders in an OPC UA address space.

Roboflow's OPC UA Writer Sink block writes a Workflow result, such as a reject flag or a defect count, to a tag in that address space, with an optional user name and password. The Tunneller passes the write to the MatrikonOPC server behind it, which sends it on to the device.

How to connect Matrikon OPC to Roboflow

5 steps
  1. Set up an edge device

    Run your Workflows on a device managed by Deployment Manager, or on a self-hosted Inference server with enterprise blocks, on a network that can reach the PC running Matrikon OPC UA Tunneller.

  2. Bridge your MatrikonOPC server to OPC UA

    In Matrikon OPC UA Tunneller, add your MatrikonOPC server to the UA-to-Classic Bridge, so it appears as a folder in the Tunneller's OPC UA address space.

  3. Allow writes

    Use the Tunneller's write-access controls to allow writes to the items the Workflow will update, and note its OPC UA endpoint URL and any user name and password it requires.

  4. Add an OPC UA Writer Sink for each tag

    In the Workflow, add one OPC UA Writer Sink per item. Enter the Tunneller's endpoint URL, the user name and password, the namespace and the path to the item (server folder and item name), and a value type that matches the item.

  5. Check the values

    Run the Workflow and watch the item in an OPC UA client. The block's error status output shows whether each write succeeded.

What teams build with Matrikon OPC

  • Send a reject signal through a MatrikonOPC server

    Write a reject flag to an item and let the MatrikonOPC server deliver it to the PLC or controller it already talks to.

  • Reach legacy devices over OPC UA

    Add vision results to devices served by OPC Classic without replacing the servers that run them today.

  • Count output per shift

    Write running counts of good and rejected parts to items that dashboards and reports already read.

Questions

No. Roboflow speaks OPC UA only, so classic OPC DA servers are reached through Matrikon OPC UA Tunneller, which exposes them over OPC UA.

For classic MatrikonOPC servers, yes. If a server already offers OPC UA, the OPC UA Writer Sink can write to it directly.

No. This integration sends results from Roboflow to the OPC server, and the OPC UA Writer Sink writes values without reading them.

No. The OPC UA Writer Sink runs on your own device or self-hosted Inference server, which needs a network route to the Tunneller.

The OPC UA Writer Sink is part of the Enterprise plan. Talk to our team to add it to your workspace.

Why are companies choosing Roboflow?

The end-to-end platform for vision AI: create datasets, train models and deploy to production.

  • Flexible deployment modes

    Move from a scalable cloud API to edge hardware like NVIDIA Jetson without managing complex dependencies.

  • Integrated workflow builder

    Combine multiple AI models, custom business logic and third-party integrations into one production-ready pipeline in a low-code editor.

  • Model monitoring and alerts

    Dashboards track confidence, inference time and request volume for your deployed models, and email alerts tell your team when confidence suddenly drops.

View all
Get started

Build on the Platform

For developers, engineers, and technical founders who want to get hands on. Try the free tier; the docs are open.

Bring it into your operation

For heads of AI, operations leaders, and enterprise teams. Bring a known problem, or work with us to find the first one worth taking on.