-
Notifications
You must be signed in to change notification settings - Fork 366
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
client.export_xml fails with BadAttributeIdInvalid #1312
Comments
Your code fails when trying to read the
Please check if your server specifies this attribute. If not |
Hello Joel, I found only one node i=6010 that doesn't have a MinimumSamplingInterval: It belongs to an icon that seems to be autoadded if one creates a new namespace with the s7 management software. Can this maybe just throw a warning instead of quitting? |
Unfortunately this icon cannot be removed from the s7 management software side :( |
would it suffice to just patch line 271 of xmlexporter as follows? |
there is another one in common/node.py that needs patching for Siemens
|
Describe the bug
I have an interface on a production s7 system I would like to simulate and run tests against.
I tried to export the node layout via client.export_xml() but it fails with a not helpful error message.
To Reproduce
Connect to a s7 and attempt to dump the node layout:
Expected behavior
I would expect the xml to be successfully written. Alternatively I would expect the xml to be written without the incompatible node. At least I would expect to get informed which node/attribute caused the issue.
Screenshots
The debugger seems to point to that line if that is helpful:
Version
Python-Version: 3.10.6
opcua-asyncio Version (e.g. master branch, 0.9): asyncua-1.0.2
The text was updated successfully, but these errors were encountered: