|
There was gateway software named OPCLink to connect the Wonderware FactorySuite product with the product for OPC so far. This gateway software had the mechanism that Request was received from the FactorySuite product with SuiteLink/DDE, the communication driver such as OPC servers was converted into OPC, and Request is done.
Having appeared in shape to enhance this gateway software further in the summer of 2004 is "FactorySuite Gateway". Accessing the tag data of InTouch/InSQL from various OPC clients by using FactorySuite Gateway and accessing the object symbol of IAS from the DDE client become possible.
|
Commentor / R.Takeuchi |
| |
Topical Utility!! FactorySuite Gateway |
 FactorySuite
Gateway is utility that converts four protocols (OPC/DDE/SuiteLink/MX) mutually, and operates as a universal protocol converter.
It is possible to make the FactorySuite A2 product function as OPC server by using this utility, and it comes to be able to use abundant OPC client products including Yokogawa Electric Works, Ltd. plant operation support software ExaPilot effectively.
Moreover, FSGateway can achieve effective use and a phased enhancing plant assets. For example, because FSGateway can offer the tag data of InTouch/InSQL and the object data of IAS to the case where the legacy system that can collect data only from the DDE server exists by the DDE interface, a new system can be introduced while attempting the life prolongment of an existing system.
The old InTouch product that doesn't support the MX protocol like InTouch7.1 can access Galaxy of IAS. (MX is a protocol used by communications with IAS in the abbreviation of "Message Exchange". )
FSGateway becomes a correlation like a right picture. Additionally, the main feature is as follows.
- It is possible to register by doing tag information that has been defined with the OPC server in brawsing.
- It is possible to register by doing tag information has been defined by specifying the application folder of InTouch in brawsing.
- It doesn't depend on NetDDE like OPCLink.
- The user interface is offered with SMC(System Management Consol).
- It is possible to operate as a service application of Windows.
Because FSGateway operates as DAServer, the user interface is offered in shape with two or more layered structures in SMC.
For example, when the OPC interface is used, the hierarchy of "OPC" is defined, and ProgID of the OPC server is set as shown in the above figure. The hierarchy of "PLC1" is defined under that, and the alias of the update cycle and tag can be defined. Similarly, the hierarchy is defined when DDE is used and the ArchestrA object is used, and it becomes shape to set the detail.
Notes FSGateway is used are as follows.
-
When DDE is used, the topic name becomes "Port name + "_" + group name". For example, the topic name becomes "New_OPC_000_New_OPCGroup_000" for port name "New_OPC_000" and group name "New_OPCGroup_000" of default
.
-
DDE and OPC cannot be used at the same time in many cases. The reason for OPC is that the process of the Inn operates by default though this should operate FSGateway for DDE in the out process. Only the OPC client application that can be Atattied can use DDE and OPC by specifying the out process specifying it when the server is connected simultaneously.
If it is used once by it, how about FactorySuite Gateway because of being flexibly developed to cooperate with SCADA systems other than the legacy system, the user application, and the Wonderware product like this. |
|
Inside MELSEC
Wonder World