Log In
Register
Forum
Topic RSS
15:53, EET
November 29, 2024
Offline
I have professional version of simulation server and trying to set up a demonstration of using OPC-UA over MQTT.
the MQTT message generation are working as expected which is great đŸ™‚
however I need to have a way to relate the datasets to the OPC namespace. When i browse the OPC server namespace the datsets are not populated as per OPC part 14 (pubSub) section 9.
I can see the following structure:
Objects
>>servers
>> >> Publish Subscribe
>> >> >> PublishedDataSets
I would expect to see my published dataSet within that object but they are not present.
Any help appreciated
17:06, EET
April 3, 2012
Offline
Hi,
Unfortunately we do not support that (maybe some day in the future); I’m unaware has anyone implemented that yet. Multiple things related to PubSub is still under active specification work and things might change in the future, since e.g. a “Cloud Subscriber” would normally be unable to do a client-server (binary) connection to the data source (if it can, then most of “PubSub” is not needed anyway). Basically at the moment you sort of just need to use very descriptive Field names in the DataSets (e.g. NodeId or a BrowsePath) and then have some magic in the Subscriber side.
P.S.
The nodes in the address space are just a side-effect of us loading the core information model. Generally speaking there are a lot of those nodes related to features that basically no-one has implemented.
18:03, EET
November 29, 2024
Offline
Thanks for the reply.
Yes as you say – would be strange to have a need to find the published dataset if you have access to the server. I am maybe trying to do something which is slightly ahead of where the standard currently is….
What I am trying to do is to create a nodeset file with the namespace of the OPC device and host it somewhere – I believe this is the purpose of the UA cloud library. To provide an endpoint cloud subscribers can access to understand the address-space of the device which is publishing MQTT messages.
In part 14 section 5.1 it suggests a “directory” is going to fulfil this role but I suspect the cloud library is now fulfilling the role of allowing the MQTT data to be contextualized.
So I was hoping to populate the “PublishedDataSets” node – maybe I will do it manually for my demo to explain what it will likely be like in future
Most Users Ever Online: 1919
Currently Online:
10 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: 726
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1529
Posts: 6471
Newest Members:
gabriellabachus, Deakin, KTP25Zof, Wojciech Kubala, efrennowell431, wilfredostuart, caitlynfajardo, jeromechubb7, franciscagrimwad, adult_galleryModerators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0
Administrators: admin: 1
