Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes

How-to guide · for Engineers, Operators

Find a tag and its path

Search the Unified Namespace for a device, read a tag's live value and quality, copy its path and open its trend.

At the end of this guide you have found a tag in the Unified Namespace, checked its value and quality, copied its path and opened its trend.

Before you start

  • The device is set up and sends data. See Add a device.
  • Your role may read that part of the namespace.

Find the tag

  1. Open Organize > UNS Explorer.
  2. Type the device name (or part of it) in Search... and press Enter. Here: MFB_RTM_L1_FILLER.
  3. Right-click the top node and choose Expand All.
  4. Select the tag.

The panel on the right shows the tag's value, its quality, when it was updated, its data type, its device and its tag key. Good means the device delivered the value without an error.

The tree filtered to MFB_RTM_L1_FILLER and expanded, with the Speed tag selected and its value, quality and details in the panel
  1. The search box.
  2. The device, at its place: enterprise Meridian, site Rotterdam_Beverage_Plant, area Filling, cell Line_1.
  3. The tag Speed.
  4. The panel with the tag's details and its path.
  5. Open trend.

Copy the path

  1. In the panel, select Copy next to the path.

The path is the tag's address in the namespace, such as Meridian/Rotterdam_Beverage_Plant/Filling/Line_1/MFB_RTM_L1_FILLER/Speed. Use it where Proxus or another program asks for a UNS path, for example in a role's UNS permissions or when subscribing over MQTT.

Open the trend

  1. Select Open trend.
The trend panel of the Speed tag with range buttons, a one hour chart with a state band, the last, average, minimum and maximum, and the Open in workspace button
  1. The range: 15 min, 1 h, 8 h or 24 h.
  2. Open in workspace opens the tag in the Trend Workspace, where you can add other tags, compare periods and export.

What's next

Was this page helpful?

Evaluating Proxus? See it on your own machines in a 30-minute technical session.