-
Notifications
You must be signed in to change notification settings - Fork 106
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
Reading tags-UDTs #62
Comments
PR #25 has the code for reading UDTs. |
Hi @jhenson29 i tried your branch with udt-templates. Reading tags work's fine, but writing udt's causes error: { generalStatusCode: 31, extendedStatus: [ 258, 4099 ] }** Do you have any idea? |
I don't, off the top of my head. I have a test suite on my laptop that runs through reading/writing different types of tags, including UDTs (including deeply nested UDTs) against a real PLC. So, I think it should work in general. But I'm only reading UDTs in my production applications. I'm not writing to any, So, I don't have much testing outside of my test suite. A few things.
|
But when i will write tag like this it doesn't work:
Template is:
|
Did you try reading the tag first, and then writing? I'm not sure without going back through the code again, but a UDT tag's value structure may not be built correctly until after it is read once. Alternatively, you may try setting all of the values in the UDT manually before writing. Know that if you are writing a UDT tag like this, it will write ALL value in the UDT, not just the ones you set. It is read and written as a structure. |
Hey, yes i read first. Values read all successful, also setting all members causes this error |
Do you know what error codes mean? |
Good morning
I have read on the npm website that you will soon be able to read tags for UDTs.
My question is when this functionality will be active or if there is at this time any beta version that includes this.
My question is when this functionality will be active or if there is at this time any beta version that includes this.
Thanks for your help
The text was updated successfully, but these errors were encountered: