Wonderware Rockwell $sys Tags

 admin  
Wonderware Rockwell $sys Tags 5,8/10 1134 votes
  1. Wonderware Communication With Controllogix

The Wonderware Common Components must be installed on the same computer as KEPServerEX. Wonderware Common Components are automatically installed with any Wonderware software product, so these instructions are only applicable if Wonderware software is not installed. If you plan to use Kepware products on the same PC as Wonderware products. Wonderware is the software only, no hardware, so it uses what are called OPC drivers to talk to hardware made by other companies, i.e. Rockwell, Siemens, Mitsubishi, Omron etc. The others can do the same thing too, but its far easier to implement compatible hardware/software packages than it is to implement dissimilar ones.

RoviSys project experience using the Wonderware® System Platform includes everything from InTouch® systems with a few hundred tags to mission critical 24/7 campus solutions with more than 25,000 tags hosted on multiple redundant providers and engines.

Foam board extrusion line legacy migration

RoviSys designed and implemented a legacy migration solution for a foam board manufacturer with an aging extrusion line with 260 I/O points. The new ControlLogix® and redundant Wonderware® InTouch® system replaced an obsolete Eurotherm EM1 and pushbutton controlled system for which there was little or no electrical scheme documentation.

RoviSys remastered the old corporate HMI standard and developed a system easily deployable to other sites and processes. RoviSys worked closely with the electrical installation contractor during the demolition and installation of the new system to manage cutover per a detailed plan and avoid unplanned downtime.

We also implemented a Wonderware® IndustrialSQL process historian to collect and analyze production information.

Power utility DCS HMI replacement with Wonderware®

RoviSys replaced a legacy DCS Operator HMI system with the Wonderware® Archestra IAS platform for a power utility plant with five coal-fired electrical generation units. Migration was completed in phases: duplicating existing graphics, creating additional new graphics and performing operator training as the new Archestra system was integrated.

The project required migrating more than 300 architecture graphics, trend displays, faceplate displays and alarm summary graphics. It also included operator and engineering training on the new Archestra system and a new Wonderware® Historian server to provide data archival services for the plant. The project was completed in four months.

Graphic standards were designed in the initial phase. Onsite reviews with plant operations and engineering were conducted using Unit #1 graphics. Operators could control Unit #1 with either the new ArchestrA system or the legacy HMI system. Based on these graphics standards, RoviSys engineers completed the conversion of graphics for Unit #2 through #4, quickly obsoleting the legacy HMI.

Steel manufacturing InTouch® systems

RoviSys engineers designed and modified a variety of Wonderware® InTouch® systems at a large Midwestern steel manufacturing plant. InTouch® was used in several plant powerhouses and provided control and data acquisition interfaces for a variety of steam boilers, turbo-blowers and electrical generation systems.

IndustrialSQL Server®

RoviSys engineers designed and commissioned an IndustrialSQL historian system at a large Pennsylvania power utility plant with no previous data historian. We integrated the new IndustrialSQL system into a new Archestra system being added simultaneously to the plant. Historian training was performed by our engineering team for plant operators, engineers and management staff.

Powerhouse Bailey™ and pneumatic controls migration

A powerhouse boiler at a steel mill used seven outdated ABB Bailey™ Single Loop Controllers to control combustion. Two boilers were controlled with an obsolete Hagan pneumatic based system.

With parts becoming obsolete, the customer contracted RoviSys to upgrade to a Rockwell Automation ControlLogix® PLC control system with Wonderware® InTouch® operator stations. Scope included the boiler master, blast furnace gas flow control, natural gas flow control, 78” blast furnace gas flow control, forced draft fan control, induced draft fan control and feedwater flow control.

We provided design, implementation, testing and commissioning of the logic necessary to control all loops and functions. We configured new Wonderware® operator stations to interact with the new control systems.

Steel mill powerhouse ABB migration

A Midwestern steel mill was using ABB Bailey™ Infi90 distributed control and Single Loop Controllers for powerhouse boiler combustion, burner management, turbo blower, pressure reducing valve and plant master control while a 25-megawatt turbine/generator was managed with an ABB/Bailey™ TB5 condenser control system. Mill management elected to replace all the Bailey™ systems as they were no longer supported.

RoviSys provided engineering services to migrate these operations to Rockwell Automation’s ControlLogix® platform and develop new or interface to existing Invensys Wonderware® InTouch® operator graphics.

We provided design, implementation, testing and commissioning of the logic necessary to control all loops and functions. We either configured new Wonderware® operator stations or modified and interfaced to existing static Wonderware® graphics to support dynamic interaction with the new control systems.

RoviSys Wonderware® System Integrator product certifications

Wonderware® maintains strong ongoing relationships with certified integrators to ensure that they have in-depth knowledge on upcoming product releases, support updates and more. RoviSys is Wonderware® certified in:

  • ActiveFactory
  • Industrial Application Server
  • IndustrialSQL Server®
  • InTouch®

Wonderware® integration expertise

  • Batch Control Systems
  • Continuous process control
  • Instrumentation
  • Manufacturing Systems
  • SCADA

Issue

ArchestrA FSGateway OPC client connection with ClearSCADA OPC Data Server

Product Line

CLEARSCADA LIC

Environment

Windows OSes, Wonderware ArchestrA FSGateway, SCADA Expert ClearSCADA 2015 R2

Resolution

A Third Party OPC client can only connect to a ClearSCADA server if it has the ClearSCADA Data Components installed. Once installed, the Data Components will handle the communications between the Third Party OPC client and the ClearSCADA server using TCP/IP protocol, so the problems commonly associated with DCOM on OPC systems are avoided DCOM issues.

Wonderware Communication With Controllogix


RockwellFollow the below steps to Install Data Access Components on a Third Party OPC Client and configure the system connection:
  1. Run the ClearSCADA Setup.exe Installer file on OPC client PC.
  2. Select the Next button up to the fifth page of the Wizard, select the Data Access component to install.
  1. After install, use the Windows Start menu to access ClearSCADA’s Configure Connections option and run the ClearSCADA Client applet and create a new connection. The configuration you need to define is exactly the same as that for a ViewX - System connection:
  1. At the ClearSCADA server side, expand the System Configuration branch then select the Security entry to display the Client Access Control List section and add the OPC client that to be authorized to connect to the ClearSCADA server. Only the clients with the correct IP addresses and correct Client Types will have access to the server:

  1. From ArchestrA FSGateway the configured OPC Client is now connected to Serck.SCXV6OPCDA.<System Name>.<Server Name> which provides a connection to the current ClearSCADA OPC data as follows:

The firewall rules for Third Party OPC client - system connections are the same as those for ViewX, the use of firewalls is the reason why ClearSCADA uses a default port range of 5500 to 5509. This range is rarely used by other applications and it also makes it easy for you to set up a firewall, if you configure the firewall to allow the ports 5500 to 5509 as well as the port for the server’s incoming data (5481 by default), the connections should be able to be established.
   Coments are closed