Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

OpcUaNodeId value is not set #4

Open
auslavs opened this issue Mar 10, 2020 · 0 comments
Open

OpcUaNodeId value is not set #4

auslavs opened this issue Mar 10, 2020 · 0 comments

Comments

@auslavs
Copy link

auslavs commented Mar 10, 2020

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Try to read a value from any OPC UA tag

Any log messages given by the failure

Server returns BadNodeIdUnknown every time
Result (ActionId: 000 ActionType: 'OpcReadAction', Endpoint: 'opc.tcp://{server}:{port}/' Node '{NodeId}'): BadNodeIdUnknown

Expected/desired behavior

The value read from the OPC Server

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful

In the OpcAction constructor, the OpcUaNodeId is set to null. if this is give the same value as the OpcNodeId it works perfectly.


Thanks! We'll be in touch soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant