How to deal with LocaleIDs for state-machine state-names?|OPC UA Companion Standards|Forum|OPC Foundation

Avatar
sp_LogInOut Log In
sp_Search Search
Advanced Search
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
sp_Search Search
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
How to deal with LocaleIDs for state-machine state-names?
Avatar
Patrick Berger
Member
Members
Forum Posts: 18
Member Since:
02/22/2022
sp_UserOfflineSmall Offline
1
11/10/2025 - 01:21
sp_Permalink sp_Print

Hi all

We have once more some problems with unclear specifications and behaviours: various companion specifications define LocalizedText for state machine state names - but with no informations regarding LocaleID.

E.g. MachineryItemState, MachineryOperationMode: defines different state and uses CurrentState[LocalizedText]

E.g. ISA95JobStateDataType uses StateText[LocalizedText]

 

But both of them in addition to the Part-16 doens't provide any information how to deal with localeID. The only one I've found is PackML - but they don't define a invairant locale.

 

What should we define/implement? Are the provided StateNames from the specifications implicit defined as invariant locale?

 

Best regards

Patrick

Avatar
Randy Armstrong
Admin
Forum Posts: 1656
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
11/11/2025 - 07:10
sp_Permalink sp_Print

If a DisplayName is missing for a Node the default DisplayName should be the BrowseName with invariant locale.

Any Server vendor is free to add additional locales for LocalizedText values.

sp_Feed
Go to top
Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 20
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1508
Posts: 5103