Screen shot

Program description

Graybox OPC Server Toolkit lets the programmer to create robust and highly effective OPC Servers within the shortest possible time. This toolkit eliminates the necessity of implementing all of the numerous OPC interfaces and COM programming. Graybox OPC Server Toolkit supports OPC Common 1.00, OPC Data Access 1.00, OPC Data Access 2.05a, OPC Data Access 3.00 (not available in Graybox OPC Server Toolkit 2.x versions). Graybox OPC Server Toolkit is fully compatible with Windows NT4/2000/XP/2003. Windows 95/98/Me operating systems are not longer supported (starting from version 2.0). Toolkit can be used with any development environment supporting C++ language and dynamic linking. You can also use any .NET language via dotNET Wrapper included in the Toolkit and available in source code. You can use it with Microsoft Visual Studio 6.0/2003/2005, Borland C++ Builder, Borland Developer Studio, etc. Toolkit includes binaries for Windows CE. All the OPC-server functionality is implemented in a single C++ class featuring all of the mandatory OPC interfaces and methods, COM object class factory, OPC Server registration methods, OPC Server, groups, tags and properties managment methods, effective server access synchronization algorithms. Toolkit is compatible with other software development technologies (such as ATL, MFC, VCL). For example, the programmer can easily add OPC-server functionality into his already existing ATL-module. Toolkit installation package includes Graybox Software OPC Server development libraries, Graybox Software documentation, OPC Foundation specifications, OPC Server samples. You can download demo version free of charge.

What is new:
v3.0.3: fixed bug in IOPCItemIO::ReadMaxAge v3.0.4: minor fixes in samples v3.0.5: minor fixes in VC6 samples, fixed bug in GB_OPCDA.h v3.0.6: new OPC proxys v3.0.7: actual canonical types instead of VE_EMPTY. ready for .NET support. v3.0.8: dotNET Wrappe

Add your comment

Title of your comment:

Your comment (max. 1000 characters):

Your name/alias: Guidelines for writing a comment: Try to be as clear as possible. Write using plain text, although you can use the following html tags: <b> <i> <u> <ol> <ul> <li> <br> <p> <blockquote>. Do not use urls in the text. Do not use offensive language. If your comment is inappropriate it will not be used.

How would you rate this product? 5 - Excellent   4 - Very Good   3 - Good   2 - Fair   1 - Poor   0 - Rubbish