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
Is your feature request related to a problem? Please describe.
Yes..Its really very hard to get the OPCUA NodeIDS manually and input the same in configmap Yaml file. Assume if there are 100s of devices cosists 20 tags per each ,in this case 2000 node id's need to get manually.
Describe the solution you'd like
OPCUA NodeID Browsing on Shifu
Describe alternatives you've considered
Provided Manually using other client tool like OPCUA expert etc.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I have faced this issue while I'm fetching data from kepware OPC UA server. that server is having 100's of devices which is hard to get all those node Id's Manually
Hi @MaheshDevulapally, thank you for creating this feature request!
Can you please provide more detail on the request by filling in the template above?
Hi @MaheshDevulapally , thank you for updating the issue. We have added it to our queue with high priority to ensure a timely resolution.
To better understand your request and provide you with the best possible solution, could you please send an email to [email protected]?
We can also arrange a short meeting to discuss the issue in more detail.
Is your feature request related to a problem? Please describe.
Yes..Its really very hard to get the OPCUA NodeIDS manually and input the same in configmap Yaml file. Assume if there are 100s of devices cosists 20 tags per each ,in this case 2000 node id's need to get manually.
Describe the solution you'd like
OPCUA NodeID Browsing on Shifu
Describe alternatives you've considered
Provided Manually using other client tool like OPCUA expert etc.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: