I will not introduce OPC, that is, then. Oh, huh.
Developing OPC is difficult to see if you want to master what extent. Let's write a few realm of shallow depth.
1. Super simple:? Use configuration software to implement ^ _ ^, please find a configuration software, press F1 to find this configuration software OPC-related help, join the server. Features: Simple and practical, easy to use. Disadvantages: The configuration is costly, the flexibility is very low. Time: Up to a half days. recommend
2. Simple: Use OPC? Active, find a control, join your project (VB or VC). Features: Simple is not practical, convenient but useless. Disadvantages: There are not many components, low flexibility. Time: Looking for a control N days, it is ok.
3. Simple: Use a rapid development package. Use the client's rapid development package. Features: Simple and practical, fast and convenient, flexible. Disadvantages: If you want money, it is dependent on the development package. Time: Look at the level of master.
4. Universal Simple: Use Opcdaauto.dll provided by the Foundation to programmatically program with VB with automation interface. This is the standard of the Foundation, there are many source code on the Internet (there are VBs also have Delphi). This method is recommended. Have the following advantages: a. It is an OPC standard without any dependencies (of course to rely on OPC) B. There is a good source code to refer to, and there is a relevant standard document. C. No other fees. d. As long as there is a little programming basis, you can master it. And the source code can be directly applied to system development.
????? Relevant information:
Kepware? The website has the source code of VB, VC.
http://www.kepware.comwww.kepware.comwwwign.com
Http://www.faWeb.net/us/opc/opclabs.html#opc_layeropc Cliet related code, simple application. VB simple and practical
OPC Foundation has related English documents
Data Access Automation Interface Standard Version 2.01
Books: "Getting Started with OPC Application" ---- Many people say that this book is very bad, in fact, it is a lot of English.
5. Universal is a bit difficult: Application VC Custom Development Interface. The difficulty of automated interface is increased, requiring a certain understanding of COM, and can apply VC development tools. It can be used under the VC. The advantage is that there is no need to use opcdaauto. DLL.
6. Abnormalities: Implementing Automation Interface, huh, this is the most variable practice, Kepware is doing this, their Kepdaauto.dll is this example, you can replace opcdaauto.dll is a giant change.
?????? Overall, the client development of OPC Cliet is not too big, especially if you don't need to understand COM-related knowledge. Just don't know much about it. There is no relevant professional website in China, only the work control OPC Forum can look. I can come to me blog to see. I will write related articles to everyone. I hope everyone will join ^ _ ^
http://blog.9cbs.net/freeboy20su
?
