-
Notifications
You must be signed in to change notification settings - Fork 8
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
Integration with OPC-UA #19
Comments
@BeSeeTek This is something we would love to discuss with you, since you have much more insight what the implications would be regarding:
|
By the way: Does option one automatically include the agents' public interface to be OPC-UA compliant? At a second glance, it appears to me that we still would have to separately design the OPC-UA capability of the agents to the outside world with underlying OPC-UA mechanisms (i.e. without Pyro4 under the hood). |
For option one, I was thinking that OPC-UA clients will be able to view and connect to the agents (which are viewed as OPC-UA servers/clients themselves). Depending on how it turns out, it might still require external interface to OPC-UA or may not (the agents commands might be already be compatible to connect to OPC-UA). Nevertheless, after discussion with @BeSeeTek, it appears that the second option is recommended due to the work required, and is still OPC-UA compliant at the end of the day. |
Maybe it would be a good idea to start with an external interface which somehow internally can be connected to agents or vice-versa and from there, at a later point, go to integrate this external interface into the agents. |
As far as I can see, there is no use case for this anymore. I will close this issue for now, but feel free to open it up again, once you have a need for that! |
Will need to investigate whether which option is better and feasible:
The text was updated successfully, but these errors were encountered: