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

Roboflow + Kepware Server

Write detections, counts and pass or fail results into Kepware Server tags over OPC UA, so every device and client connected to Kepware can use them.

Kepware Server, sold as KEPServerEX before version 7, is PTC's industrial connectivity server. It connects to PLCs and devices through its drivers and organizes their data as channels, devices and tags, which it serves to other systems over OPC UA, on port 49320 by default.

Roboflow's OPC UA Writer Sink block writes a Workflow result, such as a reject flag or a defect count, to a tag on Kepware Server, logging in with a Kepware user name and password. Kepware sits between your software and your devices, so a value written to a device tag reaches that device through Kepware's own driver.

How to connect Kepware Server to Roboflow

6 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 Kepware host. Open port 49320 in the host's firewall.

  2. Enable a remote OPC UA endpoint

    In the OPC UA Configuration Manager, open Server Endpoints and enable an endpoint on a network adapter the edge device can reach. The endpoint created at install accepts local connections only.

  3. Create a user for Roboflow

    In the User Manager, add a user in a group with write access to the tags Roboflow will update. Anonymous OPC UA login is turned off by default, so the block logs in with this user.

  4. Pick the tags to write

    Add or choose the tags the Workflow will write, under the channel and device they belong to, with data types that match the values you will send.

  5. Add an OPC UA Writer Sink for each tag

    In the Workflow, add one OPC UA Writer Sink per tag. Enter Kepware's endpoint URL, the Kepware user name and password, the namespace and the tag's path (channel, device and tag name), and a value type that matches the tag.

  6. Check the values in Kepware

    Run the Workflow and watch the tag in Kepware's OPC Quick Client. The block's error status output shows whether each write succeeded.

What teams build with Kepware Server

  • Send a reject signal to any connected PLC

    Write a reject flag to a device tag and let Kepware deliver it to the PLC through the driver it already uses.

  • Share results with every Kepware client

    Make inspection results available to the SCADA, historian and MES systems that already read from Kepware.

  • Count output per shift

    Write running counts of good and rejected parts to tags that dashboards and reports already pull from.

Questions

No. Kepware's drivers handle the device protocol. Roboflow only speaks OPC UA to Kepware.

An OPC UA endpoint the edge device can reach, a user with write access to the tags, and the tags themselves. Anonymous login is off by default, so the block needs that user's name and password.

Yes. PTC renamed KEPServerEX to Kepware Server with version 7.0, and KEPServerEX 6 projects carry over to the new version.

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

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.