Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Server - Address Space standards
June 25, 2014
9:32, EEST
Avatar
asel
Member
Members
Forum Posts: 5
Member Since:
June 25, 2014
sp_UserOfflineSmall Offline

Hello,

I’m new to OPC, so my question might be stupid, but I was wondering if there are any standards or best practices of how to set up Address Space (nodes) on server. I’m not going to set up server Address Space nor even manage the server myself, but I’m trying to find out the best way or provide the easiest way to define what nodes the client will read or be able to recommend a specific settings.

Let me give you an example. I have 3 machines with some common attributes (lets say temperature, pressure and state).
1) Should every attribute be stored in separate node?
2) Should the nodes be in specific hierarchy, for example:
– Machine 1
– Temperature
– Pressure
– State
– Machine 2
– Temperature
– Pressure
… etc
3) Should the name convension of nodes (node IDs) reflect its hierarchy?
4) Are there any performance advances in specific heirarchy / Address Space settings?
5) Are there any standards reflecting my questions? Smile

Thank you in anvance,
Best Regards,
Ladislav Asenbrener

June 25, 2014
13:15, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 1009
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

1) Yes, every variable needs it’s own node, which can be a DataVariable or Property. They are both Variable nodes (NodeClass=Variable)

2) Yes, that looks good. A good convention is to define an ObjectType (for example YourMachineType) that defines a common structure. The Object instances (i.e. Machines) can then refer to the type using a HasTypeDefinition reference and tell the client applications what type of objects they are.

3) The NodeIds can be assigned freely. Often they are composed using the hierarchy, to ensure that they are unique. But you can also use for example random GUID identifiers (although they are harder to recognise and memorise for yourself).

4) No, I wouldn’t say so

5) The DI, ADI and FDI specifications, for example define standard device types. DI also defines some standards for the address space structuring: for example DeviceSet folder in which the devices should be located in the address space.

https://opcfoundation.org/developer-tools/specifications-unified-architecture

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
22 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 135

pramanj: 86

Francesco Zambon: 81

ibrahim: 75

rocket science: 75

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

fred: 41

Member Stats:

Guest Posters: 0

Members: 707

Moderators: 16

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1466

Posts: 6253

Newest Members:

christi10l, ahamad1, Flores Frederick, ellenmoss, harriettscherer, shanonhumphreys, KupimotoblokfuB, tamhollander5, paulinafcf, bridgette18l

Moderators: Jouni Aro: 1009, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 982, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 319, Lusetti: 0, Ari-Pekka Soikkeli: 5

Administrators: admin: 1