|
|
|
Whitepapers & Articles
0x80040202 error appears in the OPC Client application when it fails to receive a callback from the OPC Server. Read the full article to troubleshoot and repair this DCOM error.
 Read more.
The 0x800706BA DCOM error appears in the OPC Client application when the OPC Client "believes" that it has a live connection to the OPC Server, but truly does not. This can happen under several conditions. Read the full article to troubleshoot and repair this DCOM error.
Read more.
DCOM Error 0x80070005 appears in the OPC Client application when it succeeds in launching an OPC Server or OpcEnum, but fails to receive a reply from either of the applications. This error could be caused under several conditions. Read the full article to troubleshoot and repair this DCOM error.
Read more.
OPC is powerful industrial communication standard. However, OPC relies on having DCOM work properly. Luckily, DCOM problems can usually be overcome with relatively simple configuration changes as documented in this whitepaper.
Read more.
This whitepaper discusses the five steps to a simple and effective strategy to establish reliable DCOM communication. In addition, the whitepaper covers troubleshooting tips to identify common OPC and DCOM problems, their symptoms, causes, and how to solve them. This will help integrators set up reliable and secure OPC connections.
Read more.
Choosing to base their communications strategy on the core OPC standards, vendors have adopted approaches where the OPC communications is 'tunneled' within other communications layers or technologies. This has proven to be a very effective approach that both eliminates the need for DCOM, and provides for a more open communications system, and one that continues to evolve and improve as the OPC standards continue to evolve and improve.
Read more.
This paper is intended to show how .NET applications can access OPC servers. It explains the required .NET wrappers and additional features built into OPC .NET client components.
Read the full article here.
Today, process data is readily available at many levels, from instrumentation to higher-level data historians and OPC servers. Choosing the right platform can be key to successfully implementing robust and maintainable process calculations at your company.
Read the full article here.
.NET is the choice platform for most client applications and it’s also a good choice for the development of OPC servers. This whitepaper covers the differet components of .NET OPC servers.
Read the full article here.
Standards are intrinsically difficult to implement and adopt. In the industrial automation business, OPC is a unifying standard that allows true interoperability. It needs more end-user support and involvement.
Read the full article here.
The .NET platform required for XML DA is now widely used and OPC server and client applications are being developed on the .NET platform. However, still most applications are built as DCOM based OPC DA server/clients, using .NET wrappers. Despite the many difficulties with DCOM configuration the transition to web services based designs is slow. With most OPC talk being about the announced OPC Unified Architecture you may find it difficult to decide on how to approach new OPC projects. This paper tries to shed some light on the related factors. It focuses on the development of OPC clients and explains different approaches and products.
Read the full article here.
|
|
