We have a new DeltaV system with version 14.3 PK750 controllers. I am also using Beijer iX developer software to intregrate some Beijer x2 pro 10 HMI's to the system.
We want to display string, floating point, integer, and binary data on the HMI from the PK750 controllers using OPC UA. Using the Beijer developer tool, I can see the all types of tags in the controller such as floating point, integer, and binary data. However, I can see string data in the controller.
Is the PK750 controller restricted from transmitting string data over OPC UA or Ethernet to other systems such as HMI's or PLC's?
I have attached screenshots of the Beijer navigation tool and the DeltaV screens.
In the screenshots, you will see these parameters:
NAME TYPE VALUE
BATCHID STRING "itworked"
TESTBATCHID STRING "testbatchid"
TESTNUMBER FLOATING POINT 3.1414
The screenshot "OPC_DATA_DEVELOPER_28DEC20" shows the Developer navigation tool before I added the TESTBATCHID and TESTNUMBER parameters, but it did show the TESTNUMBER parameter. I could display the TESTNUMBER value on the Beijer HMI as 3.1414.
In reply to AdrianOffield:
In reply to Lun.Raznik:
In reply to Bruce Greenwald:
Andre Dicaire
In reply to Andre Dicaire:
Adrian, External references will work the same way as if you added a new controller to the system. All existing nodes will be flagged as a new node will exist in the system and the Node table will need to be downloaded, which would be a "Changed setup" download. The Workstations will also get the changed Module table as part of that download, and any other system changes such as new Named Sets or Alarm definitions, etc. that might have been created in the standalone configuration. If the PK configuration followed the site database library, there would be minimal changes to be downloaded. The Merge tool evaluates any "conflicts" so that they can be resolved prior to integration.
For remote references, the location of the remote module involves the Directory Services running in the Pro Plus (or the next Workstation as determined by an election when the Pro Plus is unavailable). Upon download, or when the remote reference becomes active, as in the case of a dynamic reference that defines $REF at some later time, the referenced module is determined to be external to the controller the from which the reference is being initiated. If the module is not already communicating to this controller, i.e. it has a Proxy Client defined, the controller sends a request to identify the location of the required module. Once this is known, a device connection is made, if it does not exist, and then the Proxy client and Server are created, to which the requested parameter path is added and communications start. This requires the node table and Module tables to be downloaded to the Pro Plus and is propagated via Auto Update service to all the Workstations.
AS for the controllers, a download of Setup Data reveals the following items are sent to controlles:
The Node Table will flag a required download of Changed Setup data to all nodes so they know of the new controller. Alarm Anunciation Tale and Enumeration Sets (Named sets) may or may not be flagged as changed. The balance of Items I don't think would change for any other nodes. Without the Node Table, downloaded to a controller, it would not be able to "locate" the new PK controller if a remote reference were added to a module assigned to the PK.
The Changed Setup data download can be done on line.
2: As for support of OPC UA in OPC Mirror, I don't know that I can speak to any product changes or enhancements that my or may not be made. The question that has to asked is whether the current OPC DA solution requires a move to OPC UA for cyber security reasons, such as better management of Firewalled connections or use of Encryption. For integration purposes to DeltaV with OPC UA, the preferred method would be to use the OPC UA Client, which bypasses the OPC DA Server altogether. The client connects directly to the 3rd party OPC UA server and OPC Mirror is no longer required. If the 3rd party application moves to support an OPC UA Client it would access OPC UA server data directly from DeltaV.
So I'm not sure that OPC Mirror needs to become an OPC UA compliant product. There are multiple companies out there that offer OPC UA wrappers for both OPC DA clients and servers, allowing users to move to OPC UA. I believe Emerson lists Integration Objects as an Alliance partner with these solutions.
Here's what I like about the OPC UA Client vs OPC DA Mirror. With OPC DA, DeltaV cannot guarantee a client connection will be successful in adding all items because it is a first come, first served scenario. the OPC DA license is consumed as tags are added and when limit is reached, all subsequent connections are denied. You have to manage these connections externally. And there is the whole issue with Ports on firewalls. OPC Mirror does not alleviate any of this. With OPC UA Client, connections are managed by the Client configuration and no external behavior can come in and break valid connections. Also, the communication can be set up with Authentication certificates as well as encryption. And finally, the OPC UA protocol plays nicely with firewalls. And it is the IIoT defacto protocol for Digital Transformation.
I would be looking to move away from OPC Mirror and OPC DA servers, but I would not do so without some clear benefits or requirements that cannot be met with the existing solution. Adding encryption and Cyber security features to OPC Mirror would have costs. It also doesn't seem to be the right solution given the architecture of OPC UA. I don't know if other companies like Kepware or Integration Objects etc have any such OPC UA multi ported clients that would do what OPC Mirror does, or if Emerson is planning to support such a solution with UA, I'm not so sure that it is needed.