You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
@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.
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
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.
How to reproduce?
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
The text was updated successfully, but these errors were encountered: