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
OPC UA Client Compatibility Issues after upgrade SDK from 4.6.0 to 4.8.0
June 8, 2022
13:41, EEST
Avatar
hbrackel
Member
Members
Forum Posts: 144
Member Since:
February 21, 2014
sp_UserOfflineSmall Offline

Hi,

I recently upgraded my server applications from version 4.6.0 of the Prosys SDK to version 4.8.0. Alongside this upgrade, I regenerated code from several custom OPC UA nodesets.

After the update, some external (3rd party) clients struggle to understand the latest 1.0.4.10(?) OPC UA data types, coming with the updated generator nodesets in version 4.7.0. The problem is about the subtypes of structured data types.

If the external clients cannot be fixed, is it possible to revert the nodesets for the 4.8.0 generator to those from the 4.6.x generator (plus regenerating the code on 4.8.0)?

Thanks,
Hans-Uwe

June 8, 2022
17:09, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 1026
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

The OPC Foundation added 2 new https://reference.opcfoundation.org/v104/Core/DataTypes/StructureType/ values in the 1.04.10 errata:
-StructureWithSubtypedValues 3
-UnionWithSubtypedValues 4

and swapped some PubSub-related configuration Structures to use the those. Other than those being visible in the addresspace Types part, that should be the only change (as we do not use them yet in anything). Are the clients failing just due to that, or something else?

Can also be our bug due to the changes, but I need more info.

As for the ‘revert’, not exactly (i.e. not supported yet, might be technically doable). We have never tried, but technically the base information NodeSet XML is inside the SDK jar; it is loaded during server initialization. Thus “downgrading” that might work, though the code around would assume the newer, but it might not be a problem. We might need to continue via email about this.

Also it should be noted that Codegen is also sort of locked to a particular base information model (as there is 2 of them, one has services info as addition stuff, that is embeded and the 2 must match, some improvements could be made in the future), plus the base information model outputs are edited by us in the XXXTypeNode classes (e.g. Method implementations).

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 1919

Currently Online:
14 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: 737

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1524

Posts: 6451

Newest Members:

jonathonmcintyre, fannielima, kristiewinkle8, rust, christamcdowall, redaahern07571, nigelbdhmp, travistimmons, AnnelCib, dalenegettinger

Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1026, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0

Administrators: admin: 1