https://www.winccoa.com/fileadmin/image ... calize.png I did some experimenting with the localization behavior of the Win CC OPC UA server and got some unexpected results.
I am not sure if this is a bug or if I am not understanding something here.
Here is the story:
I have a WinCC 3.14 project configured in multiple languages. The main language is English, others are Chinese, German and Spanish
In my tests I have translated a data point description in each of the above languages as can be seen from the para screenshot on the left side of the attachment.
When I start an OPC UA server and look at the node that corresponds to the above mentioned datapoint using UaExpert (a similar tool to para, but for OPC UA nodes)
I can see the description in English, together with the code "en" for English, as can be seen in the top right frame of the attachment.
When I start another OPC UA server with the command line option -lang zh_CN.utf8 and look at the same node again with UaExpert
I still see the description in English, but the code "zh" for Chinese, as can be seen in the bottom right frame of the attachment.
Though it appears that the WinCC OPC UA manager recognized the Chinese command line option (as indicated by the codee "zh")
I would have expected to now see the Chinese description instead of the English one.
Any ideas why?
OPC UA Server Localisation Behaviour
- RudiKreiner
- Posts:198
- Joined: Mon May 16, 2011 2:10 pm
Re: OPC UA Server Localisation Behaviour
Another try to upload the attachment https://www.winccoa.com/fileadmin/image ... calize.png
I keep getting this error message when I try to view the attachment:
The requested URL /images/fbfiles/files/OpcUaServerLocalize.png was not found on this server.
It does not appear to be uploading properly
I keep getting this error message when I try to view the attachment:
The requested URL /images/fbfiles/files/OpcUaServerLocalize.png was not found on this server.
It does not appear to be uploading properly
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: OPC UA Server Localisation Behaviour
I had a look at this issue.
Right now I could not find a solution to transfer the description in a specific language.
Our development department will have a look at it.
Best Regards
Leopold Knipp
Senior Support Specialist
Right now I could not find a solution to transfer the description in a specific language.
Our development department will have a look at it.
Best Regards
Leopold Knipp
Senior Support Specialist
- RudiKreiner
- Posts:198
- Joined: Mon May 16, 2011 2:10 pm
Re: OPC UA Server Localisation Behaviour
Usually we set the active language to english, then add any other languages we need as required.
But to test the behavior I reported here, I created a new project with the languages the other way around, like this:
lang = "zh_CN.utf8"
langs = "zh_CN.utf8"
langs = "en_US.utf8"
The results were as expected.
When I start a WinCC OPC UA Server like this
WCCOAopcuasrv -num 4 -log +stderr
then look at the nodes with my UaExport Client, I see that the node description has the key zh and shows the Chinese value.
When I start a WinCC OPC UA Server like this
WCCOAopcuasrv -num 4 -lang en_US.utf8 -log +stderr
and look at the nodes with my UaExport Client, I see that the node description has the key en bit still shows the Chinese value.
This experiment confirms my suspicion that the WinCC OPC UA server actually does read the command line language setting
because the client is seeing langString attributes like the Description in en instead of zh
but ignores this setting when publishing the langString attributes, so that they are always in the project's active language (Chinese in this example)
But to test the behavior I reported here, I created a new project with the languages the other way around, like this:
lang = "zh_CN.utf8"
langs = "zh_CN.utf8"
langs = "en_US.utf8"
The results were as expected.
When I start a WinCC OPC UA Server like this
WCCOAopcuasrv -num 4 -log +stderr
then look at the nodes with my UaExport Client, I see that the node description has the key zh and shows the Chinese value.
When I start a WinCC OPC UA Server like this
WCCOAopcuasrv -num 4 -lang en_US.utf8 -log +stderr
and look at the nodes with my UaExport Client, I see that the node description has the key en bit still shows the Chinese value.
This experiment confirms my suspicion that the WinCC OPC UA server actually does read the command line language setting
because the client is seeing langString attributes like the Description in en instead of zh
but ignores this setting when publishing the langString attributes, so that they are always in the project's active language (Chinese in this example)