Log In
Home
01/25/2017
Offline
Hello,
I new to OPC UA.
In OPC UA Specification: Part 6, 5.1.1,
This standard defines two data encodings: OPC UA Binary and OPC UA XML.
Can an OPC UA application support only 1 encoding?
Or it has to support at least OPC UA binary encoding?
Thank you,
Sang
04/01/2014
Offline
Sang you are allowed to have as many encodings as you need. UA binary is the most commonly supported encoding so it is wise to include it as well as XML but it’s your choice. Make sure you look at the profiles and mappings to understand which encodings go with which transports etc. Not all combinations are valid.
Regards,
Rod
Rod Stein Manager of Technology Matrikon OPC http://www.matrikonopc.com
01/25/2017
Offline
Hello Rod,
Thank you for quick reply.
If server app supports only binary encoding, I believe that client app with only xml encoding cannot communicate with the server.
This case the server is not a valid OPC UA application, right?
Thank you,
Sang
04/01/2014
Offline
You are correct when you say the two will not communicate. The transport, encoding, and security policy all have to match between client and server before they can effectively communicate.
In your scenario the UA server is not a valid UA application for the XML only UA client but it would be a valid UA application for a client that supports UA binary encoding.
Regards,
Rod
Rod Stein Manager of Technology Matrikon OPC http://www.matrikonopc.com
01/25/2017
Offline
Does Matrikon FLEX SDK supports both binary and xml?
Is Matrikon FLEX SDK for both server and client app? In the demo video, it only mention about server SDK.
Thank you,
Sang
04/01/2014
Offline
The Matrikon Flex SDK currently only supports the more common binary transport. You can talk to a representative at Matrikon about getting the XML transport. Contact info can be found at http://www.matrikonopc.com.
The Flex SDK is both a UA client and server as of R400.1 release made earlier this year.
Regards,
Rod
Rod Stein Manager of Technology Matrikon OPC http://www.matrikonopc.com
I would like to add a clarification:
All currently released profiles for Servers and Clients require the UA-TCP transport with binary encoding. All other transports are optional. Therefore Clients and Servers that comply with released profiles will always be able to interoperate.
07/05/2017
Offline
OPC Profiles define the available combinations of Encodings, Transports and Security settings – for a complete list see:
https://opcfoundation-onlineap…..reporting/
All certification is based on these profiles, which ensures that certified products will inter-operate. The current list of encodings is binary and XML, transports is TCP and HTTPS and there is a list of security profiles. Most clients and servers support most of the list of security profiles.
Paul
1 Guest(s)
Usage Policy