Topic RSS17:56, EET
October 17, 2013
OfflineHi I have a quick question to see if I have understood this correctly.
The way that OPC-UA works with hardware is not any more magic than:
Have one hardware driver module with an API.
Have one OPC-UA DataModel of the hardware that have accses to the API.
When on create a method within the datamodel, it basically calls the hardware api to make the hardware reacto on OPC-UA methods?
HardwareDriver—–>OPC-UA DataModell with variables, methods,alarms and so on—–>OPC-UA server.
OPC-UA Client browse the addresse space —-> calls method in OPC-UA hardware datamodell —-> GO THROUG THE OPC-UA WORLD —-> Hardware API —>Hardware reacts.
So its not like a magical thing that just suddenly can sense the hardware
?
Its just an abstraction of the hardware making it easier for a user to simply create a collected connection to multiple hardware?
1 Guest(s)

Log In
Register