We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug According to the standard the server should reply to a read of an array that defines AttributeIds.IndexRange with a sub array of the given range, however the server always replies with the full array. see: https://reference.opcfoundation.org/v104/Core/docs/Part4/7.24/ https://reference.opcfoundation.org/v104/Core/docs/Part4/7.22/
AttributeIds.IndexRange
To Reproduce
Value
IndexRange
Expected behavior Client receives an array that matches the requested range
Screenshots
Version Python-Version:3.8 opcua-asyncio Version (e.g. master branch, 0.9):at least 0.8.2 and above
Check the server and client in the attachment. indexrange_issue.zip
I have identified a potential solution by changing:
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
According to the standard the server should reply to a read of an array that defines
AttributeIds.IndexRange
with a sub array of the given range, however the server always replies with the full array.see:
https://reference.opcfoundation.org/v104/Core/docs/Part4/7.24/
https://reference.opcfoundation.org/v104/Core/docs/Part4/7.22/
To Reproduce
Value
attribute of the array giving alsoIndexRange
attribute with a valid rangeExpected behavior
Client receives an array that matches the requested range
Screenshots
Version
Python-Version:3.8
opcua-asyncio Version (e.g. master branch, 0.9):at least 0.8.2 and above
Check the server and client in the attachment.
indexrange_issue.zip
I have identified a potential solution by changing:
The text was updated successfully, but these errors were encountered: