

17:56, EET
October 17, 2013

Hi 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?
Most Users Ever Online: 1919
Currently Online:
36 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 796
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
rubinramsbotham, SandraVen, lisa40301214436, AndrewLed, georgianaweis51, sophiadavis, Waynegalse, Phillipbus, Oscarsat, WilliamJerModerators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1