-
Notifications
You must be signed in to change notification settings - Fork 89
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
Could it cread ModellingRule? #46
Comments
I do not remember what modelling rules are. Can you show example?
…On Tue, May 16, 2017, 13:04 yealfor ***@***.***> wrote:
I created my address space, but there is no ModellingRule in the xml. When
I implement the new model with open62541(a opc ua sdk), it can't present
the correct variant , because that variant has no ModellingRule. So help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#46>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACcfzmI1dOuhSmbjjUfrIdquRW3tiG8hks5r6YKzgaJpZM4NcVB4>
.
|
I also do not know how to use ModellingRule. If you can explain we can probably add it. |
This is a variant which can be implemented in address space: |
OK, HasModellingRule is a type reference and reference editor is not implemented yet. But this is very high on my todo list. Should have a look.. |
Do you have anything started with this? If you have some code already I might have time to help out with this. |
I have a lot of copy paste code. I need to make the basic work, then I can publish for testing/improvement |
started work here. FreeOpcUa/opcua-widgets#8 |
I'll take a look at it. |
ready for testing now. I have not tested much myself, but it should work. suggestions to improve and PR are welcome |
and merged to master. So now it is easy to test |
I created my address space, but there is no ModellingRule in the xml. When I implement the new model with open62541(a opc ua sdk), it can't present the correct variant , because that variant has no ModellingRule. So help!
The text was updated successfully, but these errors were encountered: