17:11, EEST
April 5, 2022
Dear Support,
the features section on your website states:
Prosys OPC UA SDK for Java supports OPC UA version 1.04 and earlier
Can the server be configured to serve a specific version? Meaning that if I want the server to run with OPC UA 1.03 specification, can this be configured?
And is the OPC UA Version published somewhere, so that I can check the used version when connecting to a server?
Thank you
Raphael
12:23, EEST
April 3, 2012
Hi,
No, the page (https://www.prosysopc.com/products/opc-ua-java-sdk/technical-details/) reads “Prosys OPC UA SDK for Java supports OPC UA version 1.04 and earlier, including the following features”. The “including the following features” part is very important. Though, I’ll probably have to talk to marketing as it could maybe be written a bit differently (though this matter is extremely complicated and to explain it properly I would need like 10s pages of text, which probably would not be “very marketingy”).
Basically it means, when looking at the OPC UA Specification version 1.04 or earlier, we support these (and only these!) things (Profiles and Facets, listend on the page) from it (some require user code). It is a bit of a separate talk of how “backwards and futurewards” compatible OPC UA is, but on a basic level 1.04 client to 1.01 server and 1.01 client can connect to 1.04 server, though it might not understand all data (transferring of it however would work).
There is not a single version label that could describe the capabilities of an OPC UA application, the profiles and facets do that instead. Also on top of that is the information modelling, the server always has the base/standard information model, but more likely it has much more, and each of these have their own versions as well.
Thus, there is no way to get “version info” per se as you describe it from the server nor there isn’t a way to “select specification version” with the SDK. You can load different information model versions, though it should be noted that the base information model is effectively locked to the version of the SDK (it is not per se user-updateable).
P.S.
On the opc.tcp protocol level there is a “protocol version”, but that has never in OPC UA’s history been incremented and is still at 0, thus also meaning that the fundamental binary protocol is still the same as it was in the first version of the specification.
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: 728
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1529
Posts: 6471
Newest Members:
ellis87832073466, zkxwilliemae, gabriellabachus, Deakin, KTP25Zof, Wojciech Kubala, efrennowell431, wilfredostuart, caitlynfajardo, jeromechubb7Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0
Administrators: admin: 1