index.rst 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. Introduction
  2. ============
  3. open62541 (http://open62541.org) is an open source implementation of OPC UA
  4. (short for OPC Unified Architecture). open62541 is a C-based library (linking
  5. with C++ projects is possible) with all necessary tools to implement dedicated
  6. OPC UA clients and servers, or to integrate OPC UA-based communication into
  7. existing applications. open62541 is licensed MPLv2. So the *open62541 library can be used in projects that are
  8. not open source*. However, changes to the open62541 library itself need to
  9. published under the same license. The plugins, as well as the provided example
  10. servers and clients are in the public domain (CC0 license). They can be reused
  11. under any license and changes do not have to be published.
  12. OPC Unified Architecture
  13. ------------------------
  14. `OPC UA <http://en.wikipedia.org/wiki/OPC_Unified_Architecture>`_ is a protocol
  15. for industrial communication and has been standardized in the IEC 62541 series.
  16. At its core, OPC UA defines
  17. - an asynchronous :ref:`protocol<protocol>` (built upon TCP, HTTP or SOAP) that
  18. defines the exchange of messages via sessions, (on top of) secure
  19. communication channels, (on top of) raw connections,
  20. - a :ref:`type system<types>` for protocol messages with a binary and XML-based
  21. encoding scheme,
  22. - a meta-model for :ref:`information modeling<information-modelling>`, that
  23. combines object-orientation with semantic triple-relations, and
  24. - a set of 37 standard :ref:`services<services>` to interact with server-side
  25. information models. The signature of each service is defined as a request and
  26. response message in the protocol type system.
  27. The standard itself can be purchased from IEC or downloaded for free on the
  28. website of the OPC Foundation at https://opcfoundation.org/ (you only need to
  29. register with a valid email).
  30. The OPC Foundation drives the continuous improvement of the standard and the
  31. development of companion specifications. Companion specifications translate
  32. established concepts and reusable components from an application domain into OPC
  33. UA. They are created jointly with an established industry council or
  34. standardization body from the application domain. Furthermore, the OPC
  35. Foundation organizes events for the dissemination of the standard and provides
  36. the infrastructure and tools for compliance certification.
  37. open62541 Features
  38. ------------------
  39. open62541 implements the OPC UA binary protocol stack as well as a client and
  40. server SDK. It currently supports the Micro Embedded Device Server Profile plus
  41. some additional features. Server binaries can be well under 100kb in size,
  42. depending on the contained information model.
  43. open62541 adheres to the OPC UA specification as closely as possible and the
  44. released features pass the official Conformance Testing Tools (CTT). However,
  45. the library comes without any warranty. If you intend to use OPC UA in a
  46. mission-critical product, please consider talking to a commercial vendor of OPC
  47. UA SDKs and services.
  48. - Communication Stack
  49. - OPC UA binary protocol
  50. - Chunking (splitting of large messages)
  51. - Exchangeable network layer (plugin) for using custom networking APIs (e.g. on embedded targets)
  52. - Information model
  53. - Support for all OPC UA node types (including method nodes)
  54. - Support for adding and removing nodes and references also at runtime.
  55. - Support for inheritance and instantiation of object- and variable-types (custom constructor/destructor, instantiation of child nodes)
  56. - Subscriptions
  57. - Support for subscriptions/monitoreditems for data change notifications
  58. - Very low resource consumption for each monitored value (event-based server architecture)
  59. - Code-Generation
  60. - Support for generating data types from standard XML definitions
  61. - Support for generating server-side information models (nodesets) from standard XML definitions
  62. Features still missing in the 0.2 release are:
  63. - Encryption
  64. - Access control for individual nodes
  65. - Events (notifications emitted by objects, data change notifications are implemented)
  66. - Event-loop (background tasks) and asynchronous service requests in the client
  67. Getting Help
  68. ------------
  69. For discussion and help besides this documentation, you can reach the open62541 community via
  70. - the `mailing list <https://groups.google.com/d/forum/open62541>`_
  71. - our `IRC channel <http://webchat.freenode.net/?channels=%23open62541>`_
  72. - the `bugtracker <https://github.com/open62541/open62541/issues>`_
  73. Contributing
  74. ------------
  75. As an open source project, we invite new contributors to help improve open62541.
  76. Issue reports, bugfixes and new features are very welcome. Note that there are
  77. ways to begin contributing without deep knowledge of the OPC UA standard:
  78. - `Report bugs <https://github.com/open62541/open62541/issues>`_
  79. - Improve the `documentation <http://open62541.org/doc/current>`_
  80. - Work on issues marked as `easy hacks <https://github.com/open62541/open62541/labels/easy%20hack>`_