Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OPC UA Adapter: Duplicate Field Runtime Names #3428

Open
MaD-DSD opened this issue Jan 16, 2025 · 4 comments
Open

OPC UA Adapter: Duplicate Field Runtime Names #3428

MaD-DSD opened this issue Jan 16, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@MaD-DSD
Copy link

MaD-DSD commented Jan 16, 2025

Apache StreamPipes version

dev (current development state)

Affected StreamPipes components

UI

What happened?

I am using the OPC UA Adapter to collect measurements from an OPC UA server. The SampleNodeIds of the measurements have the format S7-XXXX.YYYY.ZZZZ.

The adapter considers only the last part of the SampleNodeId (the ZZZZ section) for the "Field runtime name". This leads to problems when multiple measurements share the same ZZZZ value.

Example:
SampleNodeId 1: S7-1234.0102.0034 → Field runtime name: 0034
SampleNodeId 2: S7-1234.0105.0034 → Field runtime name: 0034

In the next step, multiple measurements with the same runtime name are available, making it difficult to distinguish between them.

In the preview of the adapter, only one of the measurements is displayed, even though multiple measurements share the same ZZZZ component in their SampleNodeId. This makes it harder to verify the data and can lead to missing measurements.

Image

How to reproduce?

  • Configure the OPC UA Adapter to collect measurements with similar SampleNodeIds. Ensure that multiple SampleNodeIds have the same last part (ZZZZ) and click on "Next".
  • verify the generated Field Runtime Names.
  • View the preview of the collected measurements

Expected behavior

Unique Field Runtime Names: The adapter should generate a more unique Field Runtime Name, for example, by considering the entire SampleNodeId.
Complete Preview Display: The preview should display all measurements, even if they share the same ZZZZ value in their SampleNodeIds.

Additional technical information

No response

Are you willing to submit a PR?

None

@MaD-DSD MaD-DSD added the bug Something isn't working label Jan 16, 2025
@dominikriemer
Copy link
Member

Hi @MaD-DSD I tried to reproduce the error with two Nodes and get this:

Image

What is the displayName of the nodes in your example? This is currently used for determining the runtime name.

@MaD-DSD
Copy link
Author

MaD-DSD commented Jan 23, 2025

Hi @dominikriemer ,

Thank you for looking into the issue!

In my example, the full names of the nodes are S7-RCB.DB1000.REAL164 and S7-RCB.DB904.REAL164.

@tenthe
Copy link
Contributor

tenthe commented Jan 24, 2025

@MaD-DSD, could you please check if the two nodes have the same DisplayName? In the current adapter implementation, the DisplayName is used for the runtimeName in StreamPipes.

If the DisplayName is indeed identical for both nodes, we might need to define a strategy to allow users to configure the value selected for the runtimeName in the adapter configuration.

@dsdbusch
Copy link

We use Softing OPC Server (V5.19 and V5.38) and for each variable i only get the last part. When i click "Edit field" and enter any text in "Field description" only the first line's data will be stored. Here all three items are shown as good although the middle one (MConIR...) is bad! If i change the order in the first step to MCon.. to be the last, all three items are shown as Bad. I use apachestreampipes/extensions-all-jvm:0.98.0-SNAPSHOT creation time 2025-01-23 17:09:17

Image

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants