Once the certifications have been trusted, we can test our connection. Go to the OPC UA Configuration Manager - Trusted Clients Tab. Importing Client certificates and Testing Connectionīack at KepServerEx, import the two certificates created in the previous section. The same procedure must be repeated for the \fs-9.1\TRunModule.exe application. Fill in the remaining parameters accordingly. In Devices > Nodes, paste the OPC URL (copied from the previous section) in the PrimaryStation configuration popup. In your Project, navigate to Devices > Channels and create a new OPC UA channel. On the Instance Certificates page, click on the Export Button and select a folder to save the certificate for the OPC UA Server. In the Server EndPoints tab, configure the endpoint parameters (network adapter, port number, and security policies) and copy the URL because it will be used later.įor the security policies configuration, you need to enable one (or both) of the following: Use the command “Reinitialize” after changing the settings so they can be applied. Importing client certificates on OPC UAĪt KepServerEx project properties, enable support for OPC UA.Creating certificates for Engineering and Runtime.KepServerEx OPC UA Server Configuration.The procedure for a successful OPC UA connection is divided into three main steps. In addition, Kepware’s Advanced Tags Plug-In was essential for centralized data processing by the communications server, ensuring that all the data efficiently arrived where it should, when it should, and in the form it should.To make use of this feature, the following system requirements need to be matched.
#Kepware system requirements full
By developing a tool that could create a full configuration XML file to match the configuration within the ICSS, updating the KEPServerEX configuration to the current ICSS configuration took mere minutes and was completely reliable. In order to overcome the difficulties involved in the rapidly expanding infrastructure, ABB made extensive use of the ability to import and export KEPServerEX configuration information in an easy-to-understand XML format. Of particular value to ABB was Kepware’s Modbus TCP/IP Ethernet Driver, which provides data exchange between OPC clients and Modbus protocol compliant controllers.
![kepware system requirements kepware system requirements](https://oice-automation.com/wp-content/uploads/Kepware-New-Logo.png)
KEPServerEX includes a library of over 150 PLC, RTU, and other device-type drivers, as well as database and application-specific drivers.
#Kepware system requirements drivers
In conjunction with ABB’s flagship 800xA Integrated Control and Safety System (ICSS), KEPServerEX allows ABB to add multiple OPC drivers within a single communications platform without worrying about learning new communications protocols or spending time understanding new applications. With over 150 drivers and a single, consistent interface, KEPServerEX provides ABB with all the connectivity tools it requires in an easy-to-use package. To handle these requirements, ABB needed an automated communications platform that was highly reliable and that could easily scale and communicate massive amounts of data back for visualization and long-term storage in an enterprise historian.Īfter an exhaustive review of data communications solutions, ABB selected Kepware’s KEPServerEX as the best choice to handle the high demands of the groundbreaking project. All this meant that the automation of data collection was a huge undertaking, since the project infrastructure was immense and constantly in flux. It also needed to be able to reliably retrieve vast amounts of data from distant locations. With several new wells being introduced every day, ABB needed to be able to bring them on and off line in a highly streamlined and efficient manner furthermore, the method of configuring them needed to be simple, fast, and very reliable. Each of these wells have between 50 and 70 data points being scanned on a 30-second cycle time.
![kepware system requirements kepware system requirements](https://img.directindustry.com/pdf/repository_di/53903/clientace-449407_1mg.jpg)
The project called for between 1,000 and 1,500 well sites to come online in 2014, and beyond 6,000 by 2030, over an area of more than 4,500 km². One of the biggest technical challenges ABB faced with this project was automating the collection of well data.