However, before we dive in our OPC UA super complete tutorial, let’s review some important concepts:<\/p>\n\n\n\n
<\/span>What is OPC UA?<\/span><\/h2>\n\n\n\nBasically, we can say OPC<\/strong> U<\/strong>nified A<\/strong>rchitecture (OPC UA) is an industrial automation standard for moving data between the factory floor and the enterprise.<\/p>\n\n\n\nFor a longer definition, we can say OPC UA is a platform-independent interoperability standard interface through which various kinds of systems and devices can communicate to each other over various types of networks. OPC UA is applicable to components in all industrial domains, such as industrial sensors and actuators, control systems, Manufacturing Execution Systems and Enterprise Resource Planning Systems, including the Industrial Internet of Things (IIoT), Machine To Machine (M2M) as well as Industrie 4.0 and China 2025.<\/p>\n\n\n
\n![\"OPC](\"https:\/\/joseamaita.com\/en\/wp-content\/uploads\/sites\/2\/2021\/02\/img_p_03_002.png\")
<\/figure><\/div>\n\n\n<\/span>Why an OPC UA super complete tutorial?<\/span><\/h2>\n\n\n\nFirstly, I want you to build something, which can be a completely practical project. Consequently, you will apply the quote “learn by doing” and a guide like this could help you to achieve this goal. Therefore, the main idea here is to design and implement a real-world OPC UA software application, one step at a time.<\/p>\n\n\n\n
<\/span>What will we need?<\/span><\/h2>\n\n\n\nWe’ll need several software components:<\/p>\n\n\n\n
- Microsoft Visual Studio<\/strong>, an IDE from Microsoft.<\/li>
- Git<\/strong>, a free and open source distributed version control system.<\/li>
- Git repositories, usually from GitHub<\/a>.<\/li><\/ul>\n\n\n\n
<\/span>Designing for OPC UA<\/span><\/h2>\n\n\n\n<\/span>Integrated<\/span><\/h4>\n\n\n\nOPC UA provides a consistent, integrated AddressSpace<\/em> and service model. This allows a single Server<\/em> to integrate data, Alarms<\/em> and Events<\/em>, and history into its AddressSpace<\/em>, and to provide access to them using an integrated set of Services<\/em>. These Services<\/em> also include an integrated security model.<\/p>\n\n\n\n<\/span>Openly browsable and dynamic<\/span><\/h4>\n\n\n\nOPC UA also allows Servers<\/em> to provide Clients<\/em> with type definitions for the Objects<\/em> accessed from the AddressSpace<\/em>. Additionally, information models describe the contents of the AddressSpace<\/em>. OPC UA exposes data in many different formats, including binary structures and XML or JSON documents. Moreover, the OPC Foundation, other standard organizations or vendors may define the format of the data. Through the AddressSpace<\/em>, Clients<\/em> can query the Server<\/em> for the metadata that describes the format for the data. In many cases, Clients<\/em> with no pre-programmed knowledge of the data formats will be able to determine the formats at runtime and properly utilize the data.<\/p>\n\n\n\n<\/span>Flexible hierarchy for multiple applications<\/span><\/h4>\n\n\n\nOPC UA adds support for many relationships between Nodes<\/em>, which could be much more than a single hierarchy. In this way, a Server<\/em> may present data in a variety of hierarchies tailored to the way a set of Clients would typically like to view the data. This flexibility, combined with support for type definitions, makes OPC UA applicable to a wide array of problem domains. In addition to this, OPC UA aims not just the SCADA, PLC and DCS interface, but to provide greater interoperability between higher level functions.<\/p>\n\n\n\nNow, let’s see the scope of some OPC UA target applications:<\/p>\n\n\n
\n![\"\"](\"https:\/\/joseamaita.com\/en\/wp-content\/uploads\/sites\/2\/2021\/02\/img_p_03_001.png\")
<\/figure><\/div>\n\n\n<\/span>Robust communication<\/span><\/h4>\n\n\n\nOPC UA provides robustness of published data. A major feature of all OPC servers is the ability to publish data and Event Notifications<\/em>. OPC UA provides mechanisms for Clients<\/em> to quickly detect and recover from communication failures associated with these data transfers. In doing so, there is no need to wait for long timeouts provided by the underlying protocols.<\/p>\n\n\n\n<\/span>Scalable<\/span><\/h4>\n\n\n\nOPC UA supports a wide range of Servers<\/em>, from plant floor PLCs to enterprise Servers<\/em>, all of them with a broad scope of size, performance, execution platforms and functional capabilities. Therefore, OPC UA defines a comprehensive set of capabilities, and Servers<\/em> may implement a subset of these capabilities. To promote interoperability, OPC UA defines subsets, referred to as Profiles<\/em>, to which Servers<\/em> may claim conformance. Clients<\/em> can then discover the Profiles<\/em> of a Server<\/em>, and tailor their interactions with that Server<\/em> based on the Profiles<\/em>.<\/p>\n\n\n\n<\/span>Stable core<\/span><\/h4>\n\n\n\nThe OPC UA specifications layers isolate the core design from the underlying computing technology and network transport. This allows future technologies to map OPC UA when necessary, without negating the basic design. According to the standard, we will use three data encodings:<\/p>\n\n\n\n
- XML\/text<\/li>
- UA Binary<\/li>
- JSON<\/li><\/ul>\n\n\n\n
Furthermore, we will use several protocols:<\/p>\n\n\n\n
- OPC UA TCP<\/li>
- HTTPS<\/li>
- WebSockets<\/li><\/ul>\n\n\n\n
<\/span>Business-conscious<\/span><\/h4>\n\n\n\nOPC UA Applications<\/em> that support multiple transports and encodings will allow the end users to make decisions about trade-offs between performance and compatibility at the time of deployment, rather than determined by the OPC vendor at the time of product definition.<\/p>\n\n\n\n<\/span>Backward compatibility<\/span><\/h4>\n\n\n\nOPC UA is the evolution or migration path for OPC clients and servers that are based on Microsoft COM technology. With great care in the design, existing data exposed by OPC COM servers (DA, HDA and A&E) can easily match OPC UA. Evidently, vendors may choose migrating their products natively to OPC UA or use external wrappers to convert from OPC COM to OPC UA and viceversa. Besides, each of the previous OPC specifications defined its own address space model and its own set of Services<\/em>. Consequently, OPC UA unifies the previous models into a single integrated address space with a single set of Services<\/em>.<\/p>\n\n\n\n<\/span>Additional messaging pattern<\/span><\/h4>\n\n\n\nUnlike OPC UA Client Server<\/em>, OPC UA PubSub<\/em> opens new application fields for OPC UA. The following are some example uses for PubSub<\/em>:<\/p>\n\n\n\n- Configurable peer to peer communication between controllers and between controllers and HMIs. There is no need for the peers to stay directly connected and do not even need to know about the existence of each other. The data exchange often requires a fixed time-window and it may be point-to-point or a multi-point connection.<\/li>
- An order processing application can place an order on a message queue or an enterprise service bus (asynchronous workflow). Thence, one or more workers can process such orders.<\/li>
- Sensors or actuators that write logs to a monitoring system, an HMI, an archive application for later querying.<\/li>
- Servers<\/em> representing services or devices that stream data to applications hosted in the cloud such as backend servers, big data analytics for system optimization and predictive maintenance.<\/li><\/ul>\n\n\n\n
Certainly, various different messaging systems can implement PubSub<\/em>. Let’s see this with two examples:<\/p>\n\n\n\n- Production environments with frequent transmissions of small amounts of data can easily use PubSub<\/em> with UDP. It also allows data exchange in one-to-one and one-to-many configurations.<\/li>
- The use of established messaging protocols (e.g. the ISO\/IEC AMQP 1.0 protocol) with JSON data encoding supports the cloud integration path and readily allows handling of the information in modern stream and batch analytics systems.<\/li><\/ul>\n\n\n\n
<\/span>Basic exercises<\/span><\/h2>\n\n\n\nAs I wrote in the beginning, you will understand this technology with examples. Then, let’s complete some basic exercises from the OPC Foundation Unified Architecture Technology Samples<\/a>:<\/p>\n\n\n\n<\/span>Launching the OPC UA Server & Client<\/span><\/h3>\n\n\n\n- Go to the “UA-.NETStandard-Samples” GitHub repository here<\/a>.<\/li>
- Download or clone the repository to your workspace.<\/li>
- Open the “UA Quickstart Applications.sln” solution file using Visual Studio.<\/li>
- Wait until all projects load.<\/li>
- Once in Visual Studio, compile the entire solution (Build -> Build Solution).<\/li>
- Notice that compiled applications are within “..\/bin\/Debug” folder.<\/li>
- Firstly, go to that folder and launch the DA server by running “Quickstarts.DataAccessServer.exe”.<\/li>
- Secondly, launch the DA client by running “Quickstarts.DataAccessClient.exe”.<\/li>
- Finally, you should see both applications open on-screen.<\/li><\/ul>\n\n\n\n
![\"OPC](\"https:\/\/joseamaita.com\/en\/wp-content\/uploads\/sites\/2\/2021\/03\/img_p_03_003.png\")
<\/figure><\/div>\n\n\n![\"OPC](\"https:\/\/joseamaita.com\/en\/wp-content\/uploads\/sites\/2\/2021\/03\/img_p_03_004.png\")
<\/figure><\/div>\n\n\n<\/span>External resources<\/span><\/h2>\n\n\n\nTo experience the OPC UA super complete tutorial better, make sure to check these external resources:<\/p>\n\n\n\n
- OPC Foundation website<\/a><\/li>
- Featured books recommended by the OPC Foundation<\/a><\/li>
- Book “OPC Unified Architecture | Wolfgang Mahnke | Springer”<\/a><\/li><\/ul>\n\n\n\n
For other articles like this one in English, click here<\/a>. To see them in Spanish, click here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Welcome! You are about to begin a tour to learn how to design and create OPC UA applications using a super complete tutorial. Here, I present several application samples to demonstrate the use of OPC UA specifications and technology. Finally, you’ll be ready to start implementing real-world OPC UA applications. To sum up, below is… Read More »OPC UA Super Complete Tutorial<\/span><\/a><\/p>\n
For a longer definition, we can say OPC UA is a platform-independent interoperability standard interface through which various kinds of systems and devices can communicate to each other over various types of networks. OPC UA is applicable to components in all industrial domains, such as industrial sensors and actuators, control systems, Manufacturing Execution Systems and Enterprise Resource Planning Systems, including the Industrial Internet of Things (IIoT), Machine To Machine (M2M) as well as Industrie 4.0 and China 2025.<\/p>\n\n\n
<\/figure><\/div>\n\n\n<\/span>Why an OPC UA super complete tutorial?<\/span><\/h2>\n\n\n\nFirstly, I want you to build something, which can be a completely practical project. Consequently, you will apply the quote “learn by doing” and a guide like this could help you to achieve this goal. Therefore, the main idea here is to design and implement a real-world OPC UA software application, one step at a time.<\/p>\n\n\n\n
<\/span>What will we need?<\/span><\/h2>\n\n\n\nWe’ll need several software components:<\/p>\n\n\n\n
- Microsoft Visual Studio<\/strong>, an IDE from Microsoft.<\/li>
- Git<\/strong>, a free and open source distributed version control system.<\/li>
- Git repositories, usually from GitHub<\/a>.<\/li><\/ul>\n\n\n\n
<\/span>Designing for OPC UA<\/span><\/h2>\n\n\n\n<\/span>Integrated<\/span><\/h4>\n\n\n\nOPC UA provides a consistent, integrated AddressSpace<\/em> and service model. This allows a single Server<\/em> to integrate data, Alarms<\/em> and Events<\/em>, and history into its AddressSpace<\/em>, and to provide access to them using an integrated set of Services<\/em>. These Services<\/em> also include an integrated security model.<\/p>\n\n\n\n<\/span>Openly browsable and dynamic<\/span><\/h4>\n\n\n\nOPC UA also allows Servers<\/em> to provide Clients<\/em> with type definitions for the Objects<\/em> accessed from the AddressSpace<\/em>. Additionally, information models describe the contents of the AddressSpace<\/em>. OPC UA exposes data in many different formats, including binary structures and XML or JSON documents. Moreover, the OPC Foundation, other standard organizations or vendors may define the format of the data. Through the AddressSpace<\/em>, Clients<\/em> can query the Server<\/em> for the metadata that describes the format for the data. In many cases, Clients<\/em> with no pre-programmed knowledge of the data formats will be able to determine the formats at runtime and properly utilize the data.<\/p>\n\n\n\n<\/span>Flexible hierarchy for multiple applications<\/span><\/h4>\n\n\n\nOPC UA adds support for many relationships between Nodes<\/em>, which could be much more than a single hierarchy. In this way, a Server<\/em> may present data in a variety of hierarchies tailored to the way a set of Clients would typically like to view the data. This flexibility, combined with support for type definitions, makes OPC UA applicable to a wide array of problem domains. In addition to this, OPC UA aims not just the SCADA, PLC and DCS interface, but to provide greater interoperability between higher level functions.<\/p>\n\n\n\nNow, let’s see the scope of some OPC UA target applications:<\/p>\n\n\n
\n<\/figure><\/div>\n\n\n<\/span>Robust communication<\/span><\/h4>\n\n\n\nOPC UA provides robustness of published data. A major feature of all OPC servers is the ability to publish data and Event Notifications<\/em>. OPC UA provides mechanisms for Clients<\/em> to quickly detect and recover from communication failures associated with these data transfers. In doing so, there is no need to wait for long timeouts provided by the underlying protocols.<\/p>\n\n\n\n<\/span>Scalable<\/span><\/h4>\n\n\n\nOPC UA supports a wide range of Servers<\/em>, from plant floor PLCs to enterprise Servers<\/em>, all of them with a broad scope of size, performance, execution platforms and functional capabilities. Therefore, OPC UA defines a comprehensive set of capabilities, and Servers<\/em> may implement a subset of these capabilities. To promote interoperability, OPC UA defines subsets, referred to as Profiles<\/em>, to which Servers<\/em> may claim conformance. Clients<\/em> can then discover the Profiles<\/em> of a Server<\/em>, and tailor their interactions with that Server<\/em> based on the Profiles<\/em>.<\/p>\n\n\n\n<\/span>Stable core<\/span><\/h4>\n\n\n\nThe OPC UA specifications layers isolate the core design from the underlying computing technology and network transport. This allows future technologies to map OPC UA when necessary, without negating the basic design. According to the standard, we will use three data encodings:<\/p>\n\n\n\n
- XML\/text<\/li>
- UA Binary<\/li>
- JSON<\/li><\/ul>\n\n\n\n
Furthermore, we will use several protocols:<\/p>\n\n\n\n
- OPC UA TCP<\/li>
- HTTPS<\/li>
- WebSockets<\/li><\/ul>\n\n\n\n
<\/span>Business-conscious<\/span><\/h4>\n\n\n\nOPC UA Applications<\/em> that support multiple transports and encodings will allow the end users to make decisions about trade-offs between performance and compatibility at the time of deployment, rather than determined by the OPC vendor at the time of product definition.<\/p>\n\n\n\n<\/span>Backward compatibility<\/span><\/h4>\n\n\n\nOPC UA is the evolution or migration path for OPC clients and servers that are based on Microsoft COM technology. With great care in the design, existing data exposed by OPC COM servers (DA, HDA and A&E) can easily match OPC UA. Evidently, vendors may choose migrating their products natively to OPC UA or use external wrappers to convert from OPC COM to OPC UA and viceversa. Besides, each of the previous OPC specifications defined its own address space model and its own set of Services<\/em>. Consequently, OPC UA unifies the previous models into a single integrated address space with a single set of Services<\/em>.<\/p>\n\n\n\n<\/span>Additional messaging pattern<\/span><\/h4>\n\n\n\nUnlike OPC UA Client Server<\/em>, OPC UA PubSub<\/em> opens new application fields for OPC UA. The following are some example uses for PubSub<\/em>:<\/p>\n\n\n\n- Configurable peer to peer communication between controllers and between controllers and HMIs. There is no need for the peers to stay directly connected and do not even need to know about the existence of each other. The data exchange often requires a fixed time-window and it may be point-to-point or a multi-point connection.<\/li>
- An order processing application can place an order on a message queue or an enterprise service bus (asynchronous workflow). Thence, one or more workers can process such orders.<\/li>
- Sensors or actuators that write logs to a monitoring system, an HMI, an archive application for later querying.<\/li>
- Servers<\/em> representing services or devices that stream data to applications hosted in the cloud such as backend servers, big data analytics for system optimization and predictive maintenance.<\/li><\/ul>\n\n\n\n
Certainly, various different messaging systems can implement PubSub<\/em>. Let’s see this with two examples:<\/p>\n\n\n\n- Production environments with frequent transmissions of small amounts of data can easily use PubSub<\/em> with UDP. It also allows data exchange in one-to-one and one-to-many configurations.<\/li>
- The use of established messaging protocols (e.g. the ISO\/IEC AMQP 1.0 protocol) with JSON data encoding supports the cloud integration path and readily allows handling of the information in modern stream and batch analytics systems.<\/li><\/ul>\n\n\n\n
<\/span>Basic exercises<\/span><\/h2>\n\n\n\nAs I wrote in the beginning, you will understand this technology with examples. Then, let’s complete some basic exercises from the OPC Foundation Unified Architecture Technology Samples<\/a>:<\/p>\n\n\n\n<\/span>Launching the OPC UA Server & Client<\/span><\/h3>\n\n\n\n- Go to the “UA-.NETStandard-Samples” GitHub repository here<\/a>.<\/li>
- Download or clone the repository to your workspace.<\/li>
- Open the “UA Quickstart Applications.sln” solution file using Visual Studio.<\/li>
- Wait until all projects load.<\/li>
- Once in Visual Studio, compile the entire solution (Build -> Build Solution).<\/li>
- Notice that compiled applications are within “..\/bin\/Debug” folder.<\/li>
- Firstly, go to that folder and launch the DA server by running “Quickstarts.DataAccessServer.exe”.<\/li>
- Secondly, launch the DA client by running “Quickstarts.DataAccessClient.exe”.<\/li>
- Finally, you should see both applications open on-screen.<\/li><\/ul>\n\n\n\n
<\/figure><\/div>\n\n\n<\/figure><\/div>\n\n\n<\/span>External resources<\/span><\/h2>\n\n\n\nTo experience the OPC UA super complete tutorial better, make sure to check these external resources:<\/p>\n\n\n\n
- OPC Foundation website<\/a><\/li>
- Featured books recommended by the OPC Foundation<\/a><\/li>
- Book “OPC Unified Architecture | Wolfgang Mahnke | Springer”<\/a><\/li><\/ul>\n\n\n\n
For other articles like this one in English, click here<\/a>. To see them in Spanish, click here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Welcome! You are about to begin a tour to learn how to design and create OPC UA applications using a super complete tutorial. Here, I present several application samples to demonstrate the use of OPC UA specifications and technology. Finally, you’ll be ready to start implementing real-world OPC UA applications. To sum up, below is… Read More »OPC UA Super Complete Tutorial<\/span><\/a><\/p>\n
We’ll need several software components:<\/p>\n\n\n\n
- Microsoft Visual Studio<\/strong>, an IDE from Microsoft.<\/li>
- Git<\/strong>, a free and open source distributed version control system.<\/li>
- Git repositories, usually from GitHub<\/a>.<\/li><\/ul>\n\n\n\n
<\/span>Designing for OPC UA<\/span><\/h2>\n\n\n\n
<\/span>Integrated<\/span><\/h4>\n\n\n\n
OPC UA provides a consistent, integrated AddressSpace<\/em> and service model. This allows a single Server<\/em> to integrate data, Alarms<\/em> and Events<\/em>, and history into its AddressSpace<\/em>, and to provide access to them using an integrated set of Services<\/em>. These Services<\/em> also include an integrated security model.<\/p>\n\n\n\n
<\/span>Openly browsable and dynamic<\/span><\/h4>\n\n\n\n
OPC UA also allows Servers<\/em> to provide Clients<\/em> with type definitions for the Objects<\/em> accessed from the AddressSpace<\/em>. Additionally, information models describe the contents of the AddressSpace<\/em>. OPC UA exposes data in many different formats, including binary structures and XML or JSON documents. Moreover, the OPC Foundation, other standard organizations or vendors may define the format of the data. Through the AddressSpace<\/em>, Clients<\/em> can query the Server<\/em> for the metadata that describes the format for the data. In many cases, Clients<\/em> with no pre-programmed knowledge of the data formats will be able to determine the formats at runtime and properly utilize the data.<\/p>\n\n\n\n
<\/span>Flexible hierarchy for multiple applications<\/span><\/h4>\n\n\n\n
OPC UA adds support for many relationships between Nodes<\/em>, which could be much more than a single hierarchy. In this way, a Server<\/em> may present data in a variety of hierarchies tailored to the way a set of Clients would typically like to view the data. This flexibility, combined with support for type definitions, makes OPC UA applicable to a wide array of problem domains. In addition to this, OPC UA aims not just the SCADA, PLC and DCS interface, but to provide greater interoperability between higher level functions.<\/p>\n\n\n\n
Now, let’s see the scope of some OPC UA target applications:<\/p>\n\n\n
\n<\/figure><\/div>\n\n\n<\/span>Robust communication<\/span><\/h4>\n\n\n\n
OPC UA provides robustness of published data. A major feature of all OPC servers is the ability to publish data and Event Notifications<\/em>. OPC UA provides mechanisms for Clients<\/em> to quickly detect and recover from communication failures associated with these data transfers. In doing so, there is no need to wait for long timeouts provided by the underlying protocols.<\/p>\n\n\n\n
<\/span>Scalable<\/span><\/h4>\n\n\n\n
OPC UA supports a wide range of Servers<\/em>, from plant floor PLCs to enterprise Servers<\/em>, all of them with a broad scope of size, performance, execution platforms and functional capabilities. Therefore, OPC UA defines a comprehensive set of capabilities, and Servers<\/em> may implement a subset of these capabilities. To promote interoperability, OPC UA defines subsets, referred to as Profiles<\/em>, to which Servers<\/em> may claim conformance. Clients<\/em> can then discover the Profiles<\/em> of a Server<\/em>, and tailor their interactions with that Server<\/em> based on the Profiles<\/em>.<\/p>\n\n\n\n
<\/span>Stable core<\/span><\/h4>\n\n\n\n
The OPC UA specifications layers isolate the core design from the underlying computing technology and network transport. This allows future technologies to map OPC UA when necessary, without negating the basic design. According to the standard, we will use three data encodings:<\/p>\n\n\n\n
- XML\/text<\/li>
- UA Binary<\/li>
- JSON<\/li><\/ul>\n\n\n\n
Furthermore, we will use several protocols:<\/p>\n\n\n\n
- OPC UA TCP<\/li>
- HTTPS<\/li>
- WebSockets<\/li><\/ul>\n\n\n\n
<\/span>Business-conscious<\/span><\/h4>\n\n\n\n
OPC UA Applications<\/em> that support multiple transports and encodings will allow the end users to make decisions about trade-offs between performance and compatibility at the time of deployment, rather than determined by the OPC vendor at the time of product definition.<\/p>\n\n\n\n
<\/span>Backward compatibility<\/span><\/h4>\n\n\n\n
OPC UA is the evolution or migration path for OPC clients and servers that are based on Microsoft COM technology. With great care in the design, existing data exposed by OPC COM servers (DA, HDA and A&E) can easily match OPC UA. Evidently, vendors may choose migrating their products natively to OPC UA or use external wrappers to convert from OPC COM to OPC UA and viceversa. Besides, each of the previous OPC specifications defined its own address space model and its own set of Services<\/em>. Consequently, OPC UA unifies the previous models into a single integrated address space with a single set of Services<\/em>.<\/p>\n\n\n\n
<\/span>Additional messaging pattern<\/span><\/h4>\n\n\n\n
Unlike OPC UA Client Server<\/em>, OPC UA PubSub<\/em> opens new application fields for OPC UA. The following are some example uses for PubSub<\/em>:<\/p>\n\n\n\n
- Configurable peer to peer communication between controllers and between controllers and HMIs. There is no need for the peers to stay directly connected and do not even need to know about the existence of each other. The data exchange often requires a fixed time-window and it may be point-to-point or a multi-point connection.<\/li>
- An order processing application can place an order on a message queue or an enterprise service bus (asynchronous workflow). Thence, one or more workers can process such orders.<\/li>
- Sensors or actuators that write logs to a monitoring system, an HMI, an archive application for later querying.<\/li>
- Servers<\/em> representing services or devices that stream data to applications hosted in the cloud such as backend servers, big data analytics for system optimization and predictive maintenance.<\/li><\/ul>\n\n\n\n
Certainly, various different messaging systems can implement PubSub<\/em>. Let’s see this with two examples:<\/p>\n\n\n\n
- Production environments with frequent transmissions of small amounts of data can easily use PubSub<\/em> with UDP. It also allows data exchange in one-to-one and one-to-many configurations.<\/li>
- The use of established messaging protocols (e.g. the ISO\/IEC AMQP 1.0 protocol) with JSON data encoding supports the cloud integration path and readily allows handling of the information in modern stream and batch analytics systems.<\/li><\/ul>\n\n\n\n
<\/span>Basic exercises<\/span><\/h2>\n\n\n\n
As I wrote in the beginning, you will understand this technology with examples. Then, let’s complete some basic exercises from the OPC Foundation Unified Architecture Technology Samples<\/a>:<\/p>\n\n\n\n
<\/span>Launching the OPC UA Server & Client<\/span><\/h3>\n\n\n\n
- Go to the “UA-.NETStandard-Samples” GitHub repository here<\/a>.<\/li>
- Download or clone the repository to your workspace.<\/li>
- Open the “UA Quickstart Applications.sln” solution file using Visual Studio.<\/li>
- Wait until all projects load.<\/li>
- Once in Visual Studio, compile the entire solution (Build -> Build Solution).<\/li>
- Notice that compiled applications are within “..\/bin\/Debug” folder.<\/li>
- Firstly, go to that folder and launch the DA server by running “Quickstarts.DataAccessServer.exe”.<\/li>
- Secondly, launch the DA client by running “Quickstarts.DataAccessClient.exe”.<\/li>
- Finally, you should see both applications open on-screen.<\/li><\/ul>\n\n\n
\n<\/figure><\/div>\n\n\n<\/figure><\/div>\n\n\n<\/span>External resources<\/span><\/h2>\n\n\n\n
To experience the OPC UA super complete tutorial better, make sure to check these external resources:<\/p>\n\n\n\n
- OPC Foundation website<\/a><\/li>
- Featured books recommended by the OPC Foundation<\/a><\/li>
- Book “OPC Unified Architecture | Wolfgang Mahnke | Springer”<\/a><\/li><\/ul>\n\n\n\n
For other articles like this one in English, click here<\/a>. To see them in Spanish, click here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Welcome! You are about to begin a tour to learn how to design and create OPC UA applications using a super complete tutorial. Here, I present several application samples to demonstrate the use of OPC UA specifications and technology. Finally, you’ll be ready to start implementing real-world OPC UA applications. To sum up, below is… Read More »OPC UA Super Complete Tutorial<\/span><\/a><\/p>\n
- Featured books recommended by the OPC Foundation<\/a><\/li>
- The use of established messaging protocols (e.g. the ISO\/IEC AMQP 1.0 protocol) with JSON data encoding supports the cloud integration path and readily allows handling of the information in modern stream and batch analytics systems.<\/li><\/ul>\n\n\n\n
- Production environments with frequent transmissions of small amounts of data can easily use PubSub<\/em> with UDP. It also allows data exchange in one-to-one and one-to-many configurations.<\/li>
- Git<\/strong>, a free and open source distributed version control system.<\/li>