I would like to know if there's any experience with an OPC-UA toolkit/supplier which can be used in our self-developed subSystem to communicate OPC-UA with WInCC-OA 3.14/3.15?
The toolkit should at least be available for Linux, and language C++. Other languages would be nice.
The subsystem has a reasonable amount of data available for Scada but with low-to-medium update frequency.
Good and Bad experiences, pitfalls would be helpfull,
Things that i a can think of are,
- Hows the support from the Toolkit supplier?
- Is the toolkit fully compliant with WinCC-OA or Visa-Versa?
- How far is WinCC-OA comliant with OPC UA foundation definition?
- If not ( where's a Gap in compliancy )?
- More ideas
A good OPC-UA Toolkit to setup OPC-UA communication with WInCC-OA
- michel.eijgermans
- Posts:46
- Joined: Mon Aug 08, 2011 11:50 am
A good OPC-UA Toolkit to setup OPC-UA communication with WInCC-OA
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: A good OPC-UA Toolkit to setup OPC-UA communication with WinCC-OA
The WinCC OA OPC UA driver & server use the toolkit from Unified Automation.
Why do you want to use OPC UA for the communication between WinCC OA and your self-developed subsystem?
Why do you want to use OPC UA for the communication between WinCC OA and your self-developed subsystem?
- fmulder
- Posts:330
- Joined: Wed Feb 03, 2010 9:46 am
Re: A good OPC-UA Toolkit to setup OPC-UA communication with WInCC-OA
There are many ways why you'd want to use OPC UA. We have used the same and are quite happy about it.
- Customers do not like custom drivers whereas OPC UA sounds far more open and far more flexible
- There are many toolkits for OPC UA but there is just one toolkit for a WinCc Oa driver. It is easier to develop an UA driver
- We now can have developers writing our OPC UA drivers without them needing to know WinCC OA nor do they need a development environment
- The browsing and the items that you can recognize (because the adress is a readable string) are great to work with (in contrast with a numerical modbus or an S7 adress)
we're currently using the toolkit provided by the OPC Foundation but ... this is C# only (which is fine for us). We are currently working on our 5th OPC UA Server.
- Customers do not like custom drivers whereas OPC UA sounds far more open and far more flexible
- There are many toolkits for OPC UA but there is just one toolkit for a WinCc Oa driver. It is easier to develop an UA driver
- We now can have developers writing our OPC UA drivers without them needing to know WinCC OA nor do they need a development environment
- The browsing and the items that you can recognize (because the adress is a readable string) are great to work with (in contrast with a numerical modbus or an S7 adress)
we're currently using the toolkit provided by the OPC Foundation but ... this is C# only (which is fine for us). We are currently working on our 5th OPC UA Server.
- michel.eijgermans
- Posts:46
- Joined: Mon Aug 08, 2011 11:50 am
Re: A good OPC-UA Toolkit to setup OPC-UA communication with WInCC-OA
Thanks for the comments. I think the situation frenk describes is more or less common to ours,
Our subsystem 'sorter' is a stand-alone component ( developed by an internal department with minimal knowledge of Scada systems ). Nevertheless it needs to interface with different Scada-systems to give states of field-equipment and recieve commands. We don't want to use a propriety protocol for this. So we searching for a good solution.
Our subsystem 'sorter' is a stand-alone component ( developed by an internal department with minimal knowledge of Scada systems ). Nevertheless it needs to interface with different Scada-systems to give states of field-equipment and recieve commands. We don't want to use a propriety protocol for this. So we searching for a good solution.