You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi, i am the author of device-opcua-go and i'd like to share some of my views.
I noticed you guys have put NodeId and Monitor info into deviceResources' artibution in DeviceProfile(DP), so here they are:
A DP can be thought of as a template of a type or classification of Device. Different devices may have different NodeId, thus DP shouldn't contains any of spec nodeid, shoule it? I suggest you can put these info into [DeviceList.Protocols.OPC-UA] of configuration.toml file.
" monitored: "True" " means you can monit this item but if user wants to stop or restart monitor, they need to delete, modifiy and re-update DP, which is very complex so i think it shouldn't be written into DP nor be same with all device.
Add subscribe function as a command to DP. As a result, user can use it at their needs just like other commands.
I've been doing these works in device-opcua-go recently. I'll attach my code when it is done!
Hope my ideas can be taken into your considerations!
The text was updated successfully, but these errors were encountered:
hi, i am the author of device-opcua-go and i'd like to share some of my views.
I noticed you guys have put NodeId and Monitor info into deviceResources' artibution in DeviceProfile(DP), so here they are:
configuration.toml
file.I've been doing these works in device-opcua-go recently. I'll attach my code when it is done!
Hope my ideas can be taken into your considerations!
The text was updated successfully, but these errors were encountered: