WorkstationST* Device Manager Gateway

Transcription

1 GEI G WorkstationST* Device Manager Gateway Instruction Guide Dec 2016

2 These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency to be met during installation, operation, and maintenance. The information is supplied for informational purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications, and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced herein. GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not provide any license whatsoever to any of these patents. Public This document is approved for public disclosure. GE provides the following document and the information included therein as is and without warranty of any kind, expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness for particular purpose. For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative. Revised: Dec 2016 Issued: May General Electric Company. * Indicates a trademark of General Electric Company and/or its subsidiaries. All other trademarks are the property of their respective owners. We would appreciate your feedback about our documentation. Please send comments or suggestions to controls.doc@ge.com

3 Document Updates Location HART Messages FDT Frame Applications Throughout the document Description Added three additional I/O packs that support HART devices: YSIL, PUAA, and YHRA, and updated the figures to reflect all I/O packs that support HART devices Changed references to PHRA I/O pack to generic term I/O packs to include all I/O packs that support HART devices Acronyms and Abbreviations DM DME FDT HMI MUX OS PDH UDH Device Manager Device Manager Essentials Field Device Tool Human-Machine Interface Multiplexer Operating System Plant Data Highway Unit Data Highway GEI G Instruction Guide 3

4 Safety Symbol Legend Warning Indicates a procedure or condition that, if not strictly observed, could result in personal injury or death. Caution Indicates a procedure or condition that, if not strictly observed, could result in damage to or destruction of equipment. Attention Indicates a procedure or condition that should be strictly followed to improve these applications.

5 Control System Warnings Warning To prevent personal injury or damage to equipment, follow all equipment safety procedures, Lockout Tagout (LOTO), and site safety procedures as indicated by Employee Health and Safety (EHS) guidelines. Warning This equipment contains a potential hazard of electric shock, burn, or death. Only personnel who are adequately trained and thoroughly familiar with the equipment and the instructions should install, operate, or maintain this equipment. Isolation of test equipment from the equipment under test presents potential electrical hazards. If the test equipment cannot be grounded to the equipment under test, the test equipment s case must be shielded to prevent contact by personnel. Warning To minimize hazard of electrical shock or burn, approved grounding practices and procedures must be strictly followed. Warning To prevent personal injury or equipment damage caused by equipment malfunction, only adequately trained personnel should modify any programmable machine. Warning Always ensure that applicable standards and regulations are followed and only properly certified equipment is used as a critical component of a safety system. Never assume that the Human-machine Interface (HMI) or the operator will close a safety critical control loop.

6 Contents 1 Overview Third-party Asset Management Software FOUNDATION Fieldbus Messages HART Messages Configuration (Quick Start) Enable the Device Manager Gateway Enable the Foundation Fieldbus Message Server Enable the HART Message Server Configure HART Communications in Emerson AMS Configure HART Communications in Yokogawa Plant Resource Management (PRM) Configuration Changes and Management FOUNDATION Fieldbus Configuration Changes HART Configuration Changes Monitor Status WorkstationST Status of Features Windows Event Viewer Device Manager Gateway Status Viewer Systems with Multiple UDH Networks Common Asset Management System Performance and Limitations Device Manager Gateway Asset Management System Systems with a Remote Asset Management System FOUNDATION Fieldbus Device Support HART Device Support FDT Frame Applications Configure FDT/DTM Support in the Device Manager Gateway Device Manager Gateway Security System Security Open System Operation Secure System Operation SDI Connection Issues Controller Offline SDI Connection Failure Security Failures During Initialization Missing Device Manager Gateway Feature Certificate Insufficient Device Manager Gateway Feature Certificate Privileges Appendix A Add a HSE Network to an Emerson AMS Appendix B Add HART Multiplexers to an Emerson AMS Appendix C Loopback Adapter Configuration Appendix D Startup Errors Unable to Locate FOUNDATION Fieldbus Virtual HSE Adapter FOUNDATION Fieldbus Virtual Linking Device Limit GEI G WorkstationST Device Manager Gateway

7 8.3 FOUNDATION Fieldbus Virtual HSE Address Collision Appendix E UDH Partitioning Appendix F Create a Virtual HSE Network Appendix G Enable Write Access to FOUNDATION Fieldbus Device Parameters Appendix H HART Message Server Upgrade Issues Appendix I Add HART Multiplexers to Yokogawa GEI G Instruction Guide 7

8 Notes 8 GEI G WorkstationST Device Manager Gateway

9 1 Overview The Device Manager Gateway is a WorkstationST* feature that enables communication between the asset management system and fieldbus devices. The gateway handles FOUNDATION fieldbus, HART, and PROFIBUS devices. The Device Manager Gateway allows communication with third-party device management software that can modify the I/O device configurations at any time. Warning Follow all safety procedures provided by the third-party device manager and device manufacturers when modifying any I/O device configuration. Failure to follow safety precautions when modifying device configurations could potentially cause equipment mis-operation, which could lead to injury or death. WorkstationST Computer with Device Manager Gateway and Asset Management System (AMS) Note Only Mark* VIe controllers support the FOUNDATION fieldbus, HART, and PROFIBUS device pass-through capabilities required by the Device Manager Gateway. Overview GEI G Instruction Guide 9

10 The Device Manager Gateway enables communication with FOUNDATION fieldbus and HART devices using native communication interfaces supported by third-party asset management software. The Device Manager Gateway also enables communication with HART and PROFIBUS DPV1 capable devices in Field Device Tool (FDT ) frame applications using GE supplied communication device type managers (DTMs) hosted by the frame applications. Metso Fieldcare, PACTware, and Yokogawa DTM Works are examples of FDT frame applications. The following table lists the device types and software supported. Third-party Asset Management Support Device Emerson AMS Yokogawa PRM Yokogawa DTM Works FDT Frame Application HART Yes Yes Yes Yes FOUNDATION Fieldbus Yes No No No PROFIBUS DPV1 No No Yes Yes 10 GEI G WorkstationST Device Manager Gateway

11 2 Third-party Asset Management Software The Device Manager Gateway uses virtual hardware interfaces to communicate with third-party asset management software by emulating physical devices connected to the virtual interfaces. It enables Emerson AMS communication with FOUNDATION Fieldbus devices. The gateway also enables communication with HART devices for both Emerson AMS and Yokogawa PRM. 2.1 FOUNDATION Fieldbus Messages The asset management system is physically separated from the FOUNDATION fieldbus linking devices. The Device Manager Gateway uses the Virtual High-speed Ethernet (HSE) network and virtual linking device communication objects to make the system act as a set of physical linking devices on a local HSE network. Third-party Asset Management Software GEI G Instruction Guide 11

12 WorkstationST Computer with Device Manager Gateway, Asset Management System, and FOUNDATION Fieldbus 12 GEI G WorkstationST Device Manager Gateway

13 The following diagram illustrates the system from the asset management system perspective. The asset management system is not aware of the Device Manager Gateway and thinks that it is talking directly to the linking devices. Virtual System Topology Presented to the Asset Management System by the Gateway Third-party Asset Management Software GEI G Instruction Guide 13

14 2.2 HART Messages The Device Manager Gateway has the ability to enable communication between the asset management system and HART devices. The Device Manager Gateway creates a set of virtual COM ports to communicate with the asset management system. It emulates physical multiplexer (MUX) networks on the asset management system side and has the controller exchange messages with the actual HART devices using messages to and from the PHRA, YHRA, YSIL, and PUAA I/O packs. Note YHRA will be identified as a PHRA. WorkstationST Computer Asset Management System HART Messages SDI Wrapped HART Messages Virtual COM Ports Device Manager Gateway UDH Network Mark VIe Controller Mark VIeS Controller IONet Network PHRA PUAA YSIL YHRA HART Device HART Device HART Device HART Device HART Device HART Device HART Device HART Device Workstation with Device Manager Gateway, Asset Management System, and HART Message Server 14 GEI G WorkstationST Device Manager Gateway

15 2.3 Configuration (Quick Start) A common system consists of the asset management system and Device Manager Gateway running on a single WorkstationST computer on a single UDH Network. Refer to the figure WorkstationST Computer with Device Manager Gateway and Asset Management System. Configure the Device Manager Gateway as follows: Install the asset management system on a WorkstationST computer with a connection to the UDH network. Enable the gateway on the WorkstationST computer with the asset management system installed. Enable the FOUNDATION Fieldbus Message Server property and configure the Loopback Adapter if the system has FOUNDATION fieldbus devices. Configure an HSE network in the asset management system using the loopback adapter. Enable the HART Message Server property if the system has HART devices. Configure the asset management system as specified by the Device Manager Gateway Status Viewer. Third-party Asset Management Software GEI G Instruction Guide 15

16 2.3.1 Enable the Device Manager Gateway Note There are no dependencies between the Device Manager Gateway and the other WorkstationST Features. To enable the Device Manager Gateway 1. From the Start menu, select Programs, GE ControlST*, ToolboxST, and ToolboxST to display the ToolboxST System Editor. 2. From the Tree View, double-click the WorkstationST component (such as EWS1) to display the Component Editor. From the General tab, select Features. From the Summary View, select Device Manager Gateway and set to True. The Device Manager Gateway allows communication with third-party device management software that can modify the I/O device configurations at any time. Enable the Device Manager Gateway Feature only when there is a specific need to interface to third-party device management software. Warning When the Device Manager Gateway feature is enabled, follow all safety procedures provided by third-party device manager and device manufacturers when modifying any I/O device configuration. Failure to follow safety precautions when modifying device configurations could potentially cause equipment mis-operation, which could lead to injury or death. 16 GEI G WorkstationST Device Manager Gateway

17 2.3.2 Enable the FOUNDATION Fieldbus Message Server Note For help with common FOUNDATION fieldbus questions, refer to Appendix D Startup Errors. To enable the FOUNDATION Fieldbus Message Server 1. Enable the FOUNDATION fieldbus DTM Message Server property. From the Device Manager Gateway tab, select Device Manager Gateway Configuration. From the Property Editor, set Enable Foundation Fieldbus DTM Message Server to True. Third-party Asset Management Software GEI G Instruction Guide 17

18 Referenced device list, all devices are selected by default. False (read only mode) is selected by default. IP Address of the physical Virtual HSE Adapter (or Loopback Adapter). The default settings are optimal and do not need to be changed. Attention 2. Configure the loopback adapter to enable the communication between the asset management system and Device Manager Gateway. Refer to Appendix C Loopback Adapter Configuration for the procedure. Note For Emerson AMS, to allow write access to FOUNDATION fieldbus device parameters, refer to Appendix G Enable Write Access to FOUNDATION fieldbus parameters. 3. Perform a Build and Download the WorkstationST computer to make the configuration active. 4. Configure the asset management system. Refer to Appendix A Add an HSE Network to an Emerson AMS for the procedure. 18 GEI G WorkstationST Device Manager Gateway

19 Third-party Asset Management Software GEI G Instruction Guide 19

20 2.3.3 Enable the HART Message Server Note Refer to Appendix H HART Message Server Upgrade Issues. To enable the HART Message Server From the Device Manager Gateway tab, select Device Manager Gateway Configuration. From the Property Editor, set Enable HART Message Server to True. 20 GEI G WorkstationST Device Manager Gateway

21 Referenced device list; all devices are selected by default. Device Manager Software Type ; select the type of Device Manager being used. DTM Communication Timeout Period (Minutes); sets the length of time the Device Manager Gateway will wait before closing the connection to a client that is inactive (not sending messages). The Device Manager Gateway will close the connection when there is no client activity and wait for the client to reconnect when further communications are desired. Enable FOUNDATION Fieldbus Message Server when True, enables communication with FOUUNDATION Fieldbus devices. AMS computer Host or IP Address of remote AMS computer, or localhost if the AMS is on the same workstation. Enable HART Message Server when True, enables communication with HART devices. Enable HART Module Type Translation when True, enables the translation of the HART Module Device Type to a type supported by Emerson AMS. (This parameter only applies when Emerson AMS is selected as the Device Manager Software Type, and it is hidden when any other type is selected.) Maximum Virtual Port Value is the maximum COM Port number the gateway is allowed to use. Minimum Virtual Port Value is the minimum COM Port number the gateway is allowed to use. (Used to establish communications to the AMS.) Note When the Yokogawa PRM is selected as the Device Manager Application, the Maximum Virtual Port Value must be set to 99, and the Minimum Virtual Port Value should be set to 5. The default settings are optimal and should not be changed. The asset management system software must be configured to match the gateway configuration and the HART device configuration in the controllers. Third-party Asset Management Software GEI G Instruction Guide 21

22 2.3.4 Configure HART Communications in Emerson AMS To configure HART communications in the Emerson AMS 1. From the Start menu, select Programs, GE ControlST, WorkstationST, and Device Manager Gateway Status to start the Device Manager Gateway Status Viewer. 2. Add a HART Multiplexer for each MUX Network entry. Refer to Appendix B Add HART Multiplexers to Emerson AMS. Note The asset management system configuration for HART devices is uploaded from the controllers when the Device Manager Gateway starts up. The controllers must be online for the Upload command. The controllers can be added to the system incrementally, however, the final asset management system configuration cannot be determined until all controllers have been uploaded. The configuration must be updated each time a new controller is added, or a controller's HART configuration changes. 22 GEI G WorkstationST Device Manager Gateway

23 2.3.5 Configure HART Communications in Yokogawa Plant Resource Management (PRM) To configure HART communications in the Yokogawa PRM 1. From the Start menu, select Programs, GE ControlST, WorkstationST, and Device Manager Gateway Status to start the Device Manager Gateway Status Viewer. 2. Add a HART Multiplexer to the asset management system for each MUX Network entry. Refer to Appendix I Add HART Multiplexers to Yokogawa PRM. Note The asset management system configuration for HART devices is uploaded from the controllers when the Device Manager Gateway starts up. The controllers must be online for the Upload command. The controllers can be added to the system incrementally, however, the final asset management system configuration cannot be determined until all controllers have been uploaded. The configuration must be updated each time a new controller is added, or a controller's HART configuration changes. Third-party Asset Management Software GEI G Instruction Guide 23

24 2.3.6 Configuration Changes and Management The Device Manager Gateway is self-configuring. However, differences in the way FOUNDATION fieldbus and HART devices are managed in the asset management system affect configuration changes in the controllers. Changes to the gateway configuration are detected as soon as the WorkstationST computer is downloaded. These changes cause the gateway to restart as soon as the download occurs. Modifications to the asset management system configuration may be necessary for it to accurately represent the state of the system. Using the AMS software, perform a Rebuild Hierarchy operation against the HSE network in the asset management system so it will detect the changes and re-configure itself. Note When AMS software is discussed, it is referring to the Emerson AMS Suite, which was used when testing the asset management system. AMS Rebuild Hierarchy Operation 24 GEI G WorkstationST Device Manager Gateway

25 To communicate with the HART devices, the Device Manager Gateway HART Multiplexer configuration must be updated to match the Status Viewer Configuration tab. Refer to the section Configure HART Communications in Emerson AMS or Configure HART Communications in Yokogawa Plant Resource Management (PRM). Device Manager Gateway Configuration Tab Third-party Asset Management Software GEI G Instruction Guide 25

26 2.3.7 FOUNDATION Fieldbus Configuration Changes Note This section only applies to the Emerson AMS. Yokogawa PRM support for FOUNDATION Fieldbus is not supported by the Device Manager Gateway. FOUNDATION fieldbus technology uses an Ethernet network with an automatic discovery type of architecture. The linking devices broadcast their presence on the HSE network and the asset management system uses these messages to discover the linking devices and query each linking device to determine the field devices connected to it. Any changes to the gateway configuration or the linking devices are automatically detected by the gateway and reflected to the HSE network through HSE annunciation messages. Using the AMS software, perform a Rebuild Hierarchy operation against the HSE network in the asset management system so it will detect the changes and configure itself. Rebuild Hierarchy Operation 26 GEI G WorkstationST Device Manager Gateway

27 If a Mark VIe controller is downloaded with a new configuration that changes the FOUNDATION fieldbus topology under it, the Device Manager Gateway detects the change and reinitializes the virtual linking devices accordingly. The gateway logs an event in the Windows Event Log whenever this type of change occurs. Windows Event Log This change is automatically reflected in the HSE annunciation messages sent to the asset management system. Perform a Rebuild Hierarchy operation in the AMS software against the HSE network so it will detect the changes and configure itself. Third-party Asset Management Software GEI G Instruction Guide 27

28 2.3.8 HART Configuration Changes Note Refer to the sections Configure HART Communications in Emerson AMS and Configure HART Communications in Yokogawa Plant Resource Management (PRM) for additional information. HART devices communicate with the asset management system through physical multiplexer devices connected to COM ports on the WorkstationST computer. All COM port connections must be configured by the user. This makes automatic configuration of the HART devices impossible at the asset management system level. Whenever a change is downloaded to a Mark VIe controller that affects associated HART devices, the WorkstationST Service shuts down and restarts the gateway. This updates all the controller s HART devices. The gateway logs an event to the Windows Event Log. Windows Event Log 28 GEI G WorkstationST Device Manager Gateway

29 2.4 Monitor Status WorkstationST Status of Features The Device Manager Gateway status displays in the WorkstationST Status Monitor: Features Status dialog box. The running status and any high-level error conditions are displayed. The gateway communicates with third-party device management software that can modify the I/O device configurations at any time. The WorkstationST Status Monitor displays the following warning if the gateway is already running when it is started (typically during user logon to the computer) and also whenever the gateway is started while the WorkstationST Status Monitor is already running (typically as a result of a WorkstationST configuration change). Third-party Asset Management Software GEI G Instruction Guide 29

30 2.4.2 Windows Event Viewer Device Manager Gateway startup and shutdown messages, as well as error conditions display in the Windows Event Viewer. Windows Event Viewer and Log Device Manager Gateway Status Viewer The Device Manager Gateway Status Viewer determines the configuration and status of the gateway and associated devices. It can be used to quickly diagnose configuration or device communication issues. The status viewer connects to the gateway running at the specified hostname or IP Address and displays live information. 30 GEI G WorkstationST Device Manager Gateway

31 Configuration Tab The Configuration tab displays the running gateway configuration. If the HART Message Server is enabled, it also displays the required Emerson AMS or Yokogawa PRM configuration. Configuration Tab for Emerson AMS HART Configuration Third-party Asset Management Software GEI G Instruction Guide 31

32 Device Manager Gateway Status Viewer Configuration Tab for Yokogawa PRM HART Configuration 32 GEI G WorkstationST Device Manager Gateway

33 Fieldbus Tab The Fieldbus tab displays both the physical topology from the controller point of view and the virtual HSE network topology as seen by the asset management system. Fieldbus Tab The physical linking devices and their IONet addresses display. The virtual PFFA connections also display. The Fieldbus tab displays the redundant linking device status and the status of the devices below them. For example, if a device in the asset management system is unresponsive, the Fieldbus tab information determines if the device and/or its hosting linking device is online and communicating with the gateway. Fieldbus Tab Third-party Asset Management Software GEI G Instruction Guide 33

34 A Detail View (selected from the View menu) displays low-level information for debugging purposes. The following figure displays the detail view of controller AnalogM6e, a single redundant linking device pair, and two FOUNDATION fieldbus devices. Fieldbus Tab Detail View The asset management system sees a virtual linking device at address , and the gateway is currently routing HSE messages to the linking device at the primary IONet address of Each linking device displays its IONet address and its redundancy role (primary or backup). Each device entry displays its online status and basic information about the device. In this example, the backup linking device is offline, and the link and device entries below it are grayed out to indicate that the information is not current. Note The same field devices display under each linking device in a redundant pair. 34 GEI G WorkstationST Device Manager Gateway

35 HART Tab The HART tab displays the controllers and their configured I/O packs. The I/O pack communication and channel status is also provided. If a device is present on a channel, its ID displays. The virtual COM port connection for each set of I/O packs in a particular I/O cabinet (MUX network from the asset management system perspective) also displays. Communication issues between the asset management system and gateway devices are identified. For example, if a device is unresponsive in the asset management system, the HART tab information determines if the corresponding I/O pack is online and communicating with the Device Manager Gateway. Correlation of HART Tab to HART Topology Displayed by Emerson AMS Third-party Asset Management Software GEI G Instruction Guide 35

36 Correlation of HART Tab to HART Topology Displayed by Yokogawa PRM HART AMS Connection Tab The HART AMS Connection tab displays the status of the virtual COM ports created by the Device Manager Gateway. The ports pass HART messages between the gateway and the asset management system. HART AMS Connection Tab 36 GEI G WorkstationST Device Manager Gateway

37 2.5 Systems with Multiple UDH Networks Systems with multiple UDH networks require multiple Device Manager Gateways and potentially more than one asset management systems. Note Refer to Appendix E UDH Partitioning. The default Device Manager Gateway configuration supports systems with one asset management system/gateway pair per UDH network. With this configuration, each pair can see only the devices on its associated UDH network. Note The gateway configuration is limited to the UDH network connections of the host WorkstationST computer. One Asset Management System/Device Manager Gateway Pair per UDH Network Third-party Asset Management Software GEI G Instruction Guide 37

38 The gateway configuration allows the selection of the UDH Network. All devices on that network are visible to the asset management system by default. Note Refer to the section Configuration (Quick Start) for message server configuration options. 38 GEI G WorkstationST Device Manager Gateway

39 2.5.1 Common Asset Management System The Device Manager Gateway configuration supports multiple gateways sending information to a single asset management system. However, the asset management system must be installed on a separate computer. A physical HSE network supporting all computers is necessary if FOUNDATION fieldbus message support is required. The WorkstationST computer with the asset management system installed must also run the Remote HART Message Server Connection Server. Common Asset Management System for Multiple UDH Networks and its ToolboxST Configuration Third-party Asset Management Software GEI G Instruction Guide 39

40 FOUNDATION Fieldbus Message Server Configuration To configure the FOUNDATION fieldbus message server: from the ToolboxST System Editor, double-click the WorkstationST component (such as EWS1_FF) to display the Component Editor. From the Device Manager Gateway tab Tree View, select Device Manager Gateway. From the Property Editor, in the UDH Network text box, select the appropriate UDH network from the drop-down list. In the Virtual HSE Adapter IP Address text box, enter the address of the WorkstationST computer hosting a gateway. 40 GEI G WorkstationST Device Manager Gateway

41 HART Message Server Configuration To configure the HART Message Server: from the ToolboxST System Editor, double-click the WorkstationST component (such as EWS1_FF) to display the Component Editor. From the Device Manager Gateway tab Tree View, select Device Manager Gateway. From the Property Editor, in the AMS computer Host or IP Address text box, enter the PDH address of the asset management system computer for all gateways. Select Maximum Virtual Port Value and Minimum Virtual Port Value, and select a Virtual COM Port range in each Device Manager Gateway. Ensure the ranges do not overlap (for example one can use and another can use ). Note Refer to the section Systems with a Remote Asset Management System for further details about configuration options. Optionally, the Device Manager Gateways can be configured to send HART messages over the virtual HSE network by using the virtual HSE network address of the asset management system computer instead of its PDH address. Supporting both FOUNDATION fieldbus and HART message traffic on the virtual HSE network can degrade Device Manager Gateway performance. Third-party Asset Management Software GEI G Instruction Guide 41

42 HART Message Server Client Configuration Perform this procedure on the WorkstationST computer running the asset management system. To configure the HART Message Server Client: from the ToolboxST System Editor, double-click the WorkstationST component (such as EWS2) to display the Component Editor. From the Device Manager Gateway tab Tree View, select Device Manager Gateway. From the Property Editor, select Enable Remote HART Message Server Client and in the text box, select True from the dropdown menu. No further configuration is needed as the Remote HART Message Server Client waits for the gateways to connect and provide configuration information. 42 GEI G WorkstationST Device Manager Gateway

43 2.6 Performance and Limitations The Device Manager Gateway and the controller pass-through mechanism can delay overall asset management system performance. However, the effects should be negligible when compared to asset management system performance with connections to a true HSE network with physical linking devices. Combined performance depends primarily on the size of the system (number of linking devices and fieldbus devices) and the capability of the computer running them Device Manager Gateway Improve performance by: Dedicated WorkstationST computer Run the Device Manager Gateway on a WorkstationST computer with no other WorkstationST Features enabled and no other resource intensive software installed. All computer resources are then available to the gateway. Server class computer Run the Device Manager Gateway on a server class computer to maximize gateway performance with WorkstationST Features and multiple devices. Note Refer to Appendix E UDH Partitioning. Partition multiple gateways Partition the system into multiple gateways per UDH to reduce the number of field devices supported by each gateway. The Device Manager Gateway enforces a hard limit of 500 virtual linking devices per gateway. Systems with more than 500 virtual linking devices (stand-alone and redundant linking device pairs) must partition the system between multiple gateways Asset Management System Asset management system speed for performing high-traffic tasks such as rebuild hierarchy drops as the number of devices increases. Partition the system into multiple asset management system/gateway pairs per UDH to reduce the number of field devices supported by each asset management system. Third-party Asset Management Software GEI G Instruction Guide 43

44 2.7 Systems with a Remote Asset Management System The Device Manager Gateway supports FOUNDATION Fieldbus and/or HART communications between the ToolboxST application and a remote asset management system FOUNDATION Fieldbus Device Support Note Refer to Appendix F Create a Virtual HSE Network for additional information. A virtual HSE network connection between the asset management system computer and the WorkstationST computer running the Device Manager Gateway is necessary for communication. The gateway broadcasts the system topology on the virtual HSE network and the asset management system uses these messages to configure itself whenever a Rebuild Hierarchy command is issued. Remote Computer with Third-party Asset Management System and its ToolboxST Configuration HART Device Support Communications between a third-party asset management system computer and the Device Manager Gateway for HART devices requires the installation of the WorkstationST application on the remote computer, and an Ethernet connection between the asset management system computer and the gateway. Any Ethernet network can be used, including the virtual HSE network connection if FOUNDATION fieldbus support is also required. 44 GEI G WorkstationST Device Manager Gateway

45 Remote Computer Configuration Install the ToolboxST and WorkstationST applications on the asset management system computer and create a system with one WorkstationST component. Enable the Device Manager Gateway and the Remote HART Message Server Client properties Local Computer Configuration Enable the HART Message Server on the local WorkstationST computer. Configure as normal and enter the IP Address of the remote asset management system computer in the HART Message Server configuration. Remote Computer with Third-party Asset Management System and HART Message Server Third-party Asset Management Software GEI G Instruction Guide 45

46 Remote HART Message Server Client Status The HART AMS Connection tab of the Device Manager Gateway Status Viewer displays connection and virtual COM port status. 46 GEI G WorkstationST Device Manager Gateway

47 3 FDT Frame Applications FDT technology is an interoperability standard that standardizes the communication and configuration interface between all field devices and host systems. FDT provides a common environment for accessing the devices most sophisticated features. Any device can be configured, operated, and maintained through the standardized user interface, regardless of supplier, type, or communication protocol. Refer to the FDT Group Web site ( for a complete description of FDT technology. To support a broader set of field devices and device management/asset management applications, GE has leveraged the benefits of FDT technology by developing a set of FDT Group certified DTMs to provide HART over Ethernet and PROFIBUS DP-V1 over Ethernet Device Manager capability in coordination with the Device Manager Gateway. The DTMs allow management of HART and PROFIBUS DP-V1 devices from any FDT frame application from virtually any computer. For further details, refer to the Device Manager User Guide (GEH-6821). GE has also developed the Device Manager Essentials FDT frame application that provides basic device management capabilities. More advanced device management and asset management capabilities can be realized by using more fully featured third-party software such as Metso Fieldcare or PACTware. FDT Frame Applications GEI G Instruction Guide 47

48 FDT Container (fdt Container, Fieldcare) DM Gateway HART Communication DTM PHRA DTM DM Gateway PROFIBUS Communication DTM DM Gateway FOUNDATION Fieldbus Communication DTM Device DTM Device DTM PPRF DTM Device DTM PFFA DTM Device DTM PDH Network GE ControlST Device Manager Gateway UDH Network Mark VIe Controller I/O Network IONet Switch Mark VIes Controller PHRA Module PUAA Module PPRF Module PFFA Module I/O Network IONet Switch HART Devices HART Devices HART Devices HART Devices PROFIBUS DPV1 Devices FOUNDATION Fieldbus Devices YHRA Module YSIL Module PPRF Module PFFA Module HART Devices HART Devices HART Devices HART Devices PROFIBUS DPV1 Devices FOUNDATION Fieldbus Devices WorkstationST Computer with Device Manager Gateway and FDT Frame Application 48 GEI G WorkstationST Device Manager Gateway

49 As shown in the previous figure, the Device Manager Gateway WorkstationST Feature runs on a WorkstationST computer with UDH network connectivity to the Mark VIe controllers. The FDT frame application can run on this or any other WorkstationST computer, or even a customer computer that does not have the WorkstationST application installed; provided that it has network connectivity (typically over the PDH network) to the WorkstationST computer running the Device Manager Gateway Feature. The DTMs are installed on the computer hosting the FDT frame application. An instance of the communication DTM is added to the FDT frame application, and the communication DTM requests the ToolboxST system topology from the Device Manager Gateway and automatically creates instances of the corresponding I/O module DTMs. The I/O module DTMs are then used to scan for devices connected to them, and instances of the corresponding device DTMs are automatically created. The GE DTMs are software components running in a FDT frame application that provide a consistent interface between the frame application and the Device Manager Gateway. The same communication code runs in every Frame Application regardless of the vendor, eliminating vendor specific issues associated with native interfaces. Providing DTMs and a TCP/IP interface between the communication DTM and the Device Manager Gateway provides compatibility with the wide array of FDT frame applications available on the market and provides the freedom to run that software from virtually anywhere on any computer. FDT Frame Applications GEI G Instruction Guide 49

50 3.1 Configure FDT/DTM Support in the Device Manager Gateway Enable the Device Manager Gateway Feature in a WorkstationST computer that has UDH network connectivity. Note Large systems or systems with multiple UDH networks may require multiple Device Manager Gateways running on different workstation computers. Refer to Appendix E UDH Partitioning for more information. To configure the Device Manager Gateway 1. From the Start menu, select Programs, GE ControlST, ToolboxST, and ToolboxST to display the ToolboxST System Editor. 2. From the Tree View, double-click the WorkstationST component (such as Wkstn) to display the Component Editor. From the General tab, select Features. From the Summary View, select Device Manager Gateway and set to True. 50 GEI G WorkstationST Device Manager Gateway

51 From the Device Manager Gateway tab Tree View, select the Device Manager Gateway item. From the Property Editor, select Device Manager Software Type and from the drop-down list select the type to use. FDT/DTM support will be enabled if the type selected represents an DFT frame application. Note The list includes all of the tested Device Manager application types. The Emerson_AMS and Yokogawa_PRM_Native types use virtual COM ports to provide the communication interface. All other types are FDT frame applications and selecting them enables the DTM communication interface. If the software type being used is an FDT frame application not in the Device Manager Software Type drop-down list, select Other_FDT_Frame_Application. FDT Frame Applications GEI G Instruction Guide 51

52 From the Property Editor, select DTM Communication Timeout Period (Minutes) and enter the time (refer to the definition). From the Property Editor, enable the Foundation Fieldbus, HART, and/or Profibus Message Server as needed. 52 GEI G WorkstationST Device Manager Gateway

53 After enabling a server, you are offered the option of selecting Referenced devices. 3. Build and download the workstation. FDT Frame Applications GEI G Instruction Guide 53

54 Optional steps: a. From the WorkstationST Status Monitor, right-click the Device Manager Gateway Feature and select View Device Manager Gateway Status from the shortcut menu to display the Device Manager Gateway Status Viewer. b. The Configuration tab displays the running configuration of the Device Manager Gateway. From the Configuration tab, the downloaded configuration displays. Verify that the HART Message Server and HART Communication DTM Interface are enabled. Verify the state of the PROFIBUS Message Server and FOUNDATION Fieldbus Interfaces match the configured state. 54 GEI G WorkstationST Device Manager Gateway

55 c. The HART tab displays the physical topology of the system from the HART perspective by listing all of the controllers referenced by the Device Manager Gateway, and the status of the I/O modules and connected devices beneath them. Example HART PHRA I/O Pack Topology d. The PROFIBUS tab displays the physical topology of the system from the PROFIBUS perspective by listing all of the controllers referenced by the Device Manager Gateway, and the status of the PPRF modules and devices on their respective PROFIBUS networks. e. The Foundation Fieldbus DTM tab displays the physical topology of the system from the FOUNDATION fieldbus perspective by listing all of the controllers referenced by the Device Manager Gateway, and the status of the PFFA modules and devices. FDT Frame Applications GEI G Instruction Guide 55

56 f. The CommDTM Connections tab displays all of the active Device Manager Gateway connections to PROFIBUS, HART, and FOUNDATION Fieldbus communication DTMs running in FDT Frame Applications. 56 GEI G WorkstationST Device Manager Gateway

57 4 Device Manager Gateway Security The Device Manager Gateway feature has been enhanced in ControlST V and higher to communicate over secure SDI connections with the Mark VIe controllers in secure systems. The following diagram shows how the Device Manager Gateway feature uses the certificate found in the certificate store of the PC it is running on, and uses that certificate to authenticate with the controller in order to establish a secure SDI connection. Device Manager Gateway Security GEI G Instruction Guide 57

58 Workstation Device Manager Application Certificate Store Device Manager Gateway Secure SDI Connection CA Server Mark Vie Controller IO Modules Field Devices The controllers use the secure SDI connections to prevent unauthorized software from connecting to and exchanging data with the controllers. Refer to the ToolboxST User Guide for Mark Controls Platform (GEH-6700), the section Security for additional information on secure system configuration and certificate management. 58 GEI G WorkstationST Device Manager Gateway

59 4.1 System Security The Device Manager Gateway uses the CA Server Full Name and CA Server IP Address system level properties to determine whether it is running in a secure system. If CA Server Full Name and CA Server IP Address are specified (not empty) then DMG will operate in secure mode, otherwise DMG will operate in Open mode. Device Manager Gateway Security GEI G Instruction Guide 59

60 4.2 Open System Operation Device Manager Gateway reads the CA Server Full Name and CA Server IP Address values during its initialization. If the Security Server properties are empty, DMG will start up and operate in Open mode. The Configuration tab of the Device Manager Gateway Status Viewer displays the configured System Security mode detected by the DMG at startup. The following figure shows an example where System Security has not been configured and DMG will operate in Open mode. 60 GEI G WorkstationST Device Manager Gateway

61 DMG and the controllers will operate in Open mode in a system without a configured Security Server. There is no change in operation from previous versions of Device Manager Gateway in Open mode. Certificates are not used and are not needed in an Open system. DMG will use Open SDI connections to exchange data with the controllers. The fieldbus tabs of the Device Manager Gateway Status Viewer show the state of the SDI connections to the controllers. The following figure shows the SDI connections to three controllers under the HART tab. All of the SDI connections are established and actively exchanging data (indicated by the <CONNECTED> status). The SecurityState value indicates the Security State of the controller, and in this example system security is not enabled, so all of the controllers are in Open mode. The Directive value indicates the security level that DMG is using to establish the connection. DMG will use an Open SDI connection type whenever the controller Security State is Open, which is the only possible security state for the controller in an Open system. Device Manager Gateway Security GEI G Instruction Guide 61

62 4.3 Secure System Operation The Security Servers properties will be filled out as part of the configuration of a secure system. A certificate named GeCssDeviceManagerGateway must also be created and assigned to the My substore under the LocalMachine location in the Certificate Store of the PC running the DMG. The Feature Certificates tab of the WorkstationST Certificate Manager (which is launched from the Tools item of the main menu in WorkstationST Status Monitor) can be used to view the feature certificates and their properties in the local PC Certificate Store. When DMG starts up, it examines the Security Servers properties to determine if it is running in a secure system. If it determines that it is running in a secure system it will search the Certificate Store on the local PC to locate the required Device Manager Gateway feature certificate. If the GeCssDeviceManagerGateway certificate is found, DMG displays the Security Servers values and the Device Manager Gateway feature certificate information on the Configuration tab of the Device Manager Gateway Status Viewer. 62 GEI G WorkstationST Device Manager Gateway

63 Note If the feature certificate cannot be found in the store, DMG will report the missing certificate error and suspend its operation until a valid certificate is imported into the Certificate Store and the feature is restarted. DMG will also report an error and suspend operation if the feature certificate that it finds does not provide at least the minimum capability level required to perform all secure Read and Write operations over a Secure SDI connection. Refer to the Security Failures During Initialization section for more information. Once Device Manager Gateway initialization is complete, the fieldbus tabs of the Device Manager Gateway Status Viewer show the state of the SDI connections to the controllers. The screen shot below shows the SDI connections to three controllers under the HART tab. Device Manager Gateway Security GEI G Instruction Guide 63

64 All of the SDI connections are established and actively exchanging data (indicated by the <CONNECTED> status). The SecurityState value indicates the security state of the controller and in this example system security is enabled and all of the controllers are in Secure mode. The Directive value indicates the security level that DMG is using to establish the connection. DMG uses the AuthenticateAndEncrypt security directive to establish the SDI connection whenever the controller Security State is Secure. Note A controller in a secure system can be taken out of Secure mode and put in Open mode. DMG determines which directive to connect with based on the controller s security state. DMG will use the Open directive if the controller is in Open mode, and DMG will use the AuthenticateAndEncrypt directive if the controller is in Secure mode. Based on this criteria, DMG will connect using the Open directive when the controller is in Open mode in a secure system, which is a valid and supported mode of operation. In the invalid and essentially impossible case where the controller is in Secure mode in a system where the Security Servers properties are not filled out, DMG will attempt to connect with the AuthenticateAndEncrypt directive and will fail to connect because it will not have the necessary certificate information to establish a secure SDI connection with the controller. 64 GEI G WorkstationST Device Manager Gateway

65 4.4 SDI Connection Issues Controller Offline The controller connection status is shown as <OFFLINE> in the Device Manager Gateway Status Viewer if the controller is not responding on the network SDI Connection Failure If there is a security failure when attempting to establish an SDI connection to the controller the connection status will be shown as < CONNECT ERROR> in the Device Manager Gateway Status Viewer. Hovering over the connection with the mouse will bring up a tooltip with additional information about the cause of the failure. In the example above, the Security Servers properties were cleared and the controllers were left in secure mode. The tooltip text contains the following message, which clearly indicates that the certificate information is not available to establish the SDI connection: Secure Connection failed: cannot create a secure connection. Missing system level data like CA Server name and domain, and/ or user login name Device Manager Gateway Security GEI G Instruction Guide 65

66 4.5 Security Failures During Initialization Device Manager Gateway relies on the GeCssDeviceManagerGateway certificate to be able to connect to the controllers in secure mode in a secure system. Device Manager Gateway detects issues with its feature certificate and suspends its operation during its initialization phase if a valid certificate cannot be found Missing Device Manager Gateway Feature Certificate When Device Manager Gateway starts up, it examines the Security Servers properties to determine if it is running in a secure system. If it determines that it is running in a secure system it will search the Certificate Store on the local PC to locate the required Device Manager Gateway feature certificate. If the GeCssDeviceManagerGateway certificate is not found, Device Manager Gateway will suspend its operation and report the error in both the WorkstationST Status Monitor and the Windows Event Log. Note The Device Manager Gateway Status Viewer will not be able to connect to the Device Manager Gateway Feature in the certificate not found state because the feature operation has been suspended. The figure above shows the Error reported by the Device Manager Gateway feature when the certificate cannot be found. The full text of the error message is: A Certificate named GeCssDeviceManagerGateway could not be found in the Certificate Store- Device Manager Gateway feature operation will be suspended until a certificate is provided and the feature is restarted. 66 GEI G WorkstationST Device Manager Gateway

67 The error is also reported to the Windows event log as follows: The Feature Certificates tab of the WorkstationST Certificate Manager can be used to view the contents of the LocalMachine \My certificate store. The WorkstationST Certificate Manager can be launched from the Tools Menu of the WorkstationST Status Monitor utility. To restore Device Manager Gateway operation, import the GeCssDeviceManagerGateway feature certificate into the LocalMachine location My substore and restart the Device Manager Gateway feature. Device Manager Gateway Security GEI G Instruction Guide 67

68 4.5.2 Insufficient Device Manager Gateway Feature Certificate Privileges When Device Manager Gateway starts up, it examines the Security Servers properties to determine if it is running in a secure system. If it determines that it is running in a secure system it will search the Certificate Store on the local PC to locate the required Device Manager Gateway feature certificate. If the GeCssDeviceManagerGateway certificate is found, Device Manager Gateway will determine the certificate s configured Capability level. Device Manager Gateway requires a Capability level of Set or higher to operate correctly. If the GeCssDeviceManagerGateway certificate has only Base level Capability, Device Manager Gateway will suspend its operation and report the error in both the WorkstationST Status Monitor and the Windows Event Log. Note The Device Manager Gateway Status Viewer will not be able to connect to the Device Manager Gateway Feature in the certificate not found state because the feature operation has been suspended. The figure above shows the Error reported by the Device Manager Gateway feature when the GeCssDeviceManagerGateway feature certificate has insufficient capability. The full text of the error message is: The Device Manager Gateway feature certificate does not have sufficient Capability to support secure data exchanges with the controllers. The supplied certificate has Base Capability, while a certificate with a minimum of Set Capability is required. Feature operation will be suspended until a certificate with sufficient capability is provided and the feature is restarted. 68 GEI G WorkstationST Device Manager Gateway

69 The error is also reported to the Windows event log as follows: The Feature Certificates tab of the WorkstationST Certificate Manager can be used to view the contents of the LocalMachine \My certificate store. The WorkstationST Certificate Manager can be launched from the Tools Menu of the WorkstationST Status Monitor utility. Device Manager Gateway Security GEI G Instruction Guide 69

70 70 GEI G WorkstationST Device Manager Gateway

71 5 Appendix A Add a HSE Network to an Emerson AMS Perform the following procedure to add the HSE network to a computer with the Emerson AMS software. To add a HSE network to an Emerson AMS computer From the Start menu, expand AMS Device Manager and select Network Configuration. Appendix A Add a HSE Network to an Emerson AMS GEI G Instruction Guide 71

72 72 GEI G WorkstationST Device Manager Gateway

73 Appendix A Add a HSE Network to an Emerson AMS GEI G Instruction Guide 73

74 Notes 74 GEI G WorkstationST Device Manager Gateway

75 6 Appendix B Add HART Multiplexers to an Emerson AMS The Device Manager Gateway creates several COM ports for Multiplex networks. The Device Manager Gateway Status Viewer Configuration tab displays the MUX networks at the bottom of the window. Perform the following procedure to add the MUX Network specified in the Device Manager Gateway Status Viewer to an Emerson AMS. In the following figure, the networks GT1_WrkStn and SIL1_Cab1 have been created. For this example, use the AMS Network Configuration to add Multiplexer Networks named GT1_WrkStn at COM10 and SIL1_Cab1 at COM11. Appendix B Add HART Multiplexers to an Emerson AMS GEI G Instruction Guide 75

76 Device Manager Gateway Status Viewer Configuration Tab Note The name of the Device Manager is based upon the individual computer or site naming conventions. 76 GEI G WorkstationST Device Manager Gateway

77 To add a Multiplexer Network to an Emerson AMS: from the Start menu, expand AMS Device Manager and select Network Configuration. From the AMS Network Configuration dialog box, click Add to select a network type. Select the network type to install (Multiplexer Network is selected for this example ), then click Install. Appendix B Add HART Multiplexers to an Emerson AMS GEI G Instruction Guide 77

78 Click Next to begin installation. Enter the network name ( and click Next to continue. 78 GEI G WorkstationST Device Manager Gateway

79 Continuing with our example, COM10 was listed as a MUX network and the Multi-drop Range was listed as 0 to 2. (Refer to the figure Device Manager Gateway Status Viewer Configuration Tab.) Select COM10 for the COM Port and select 0 to 2 for the RS485 Address from / to range. Click OK to complete the conection. Appendix B Add HART Multiplexers to an Emerson AMS GEI G Instruction Guide 79

80 Notes 80 GEI G WorkstationST Device Manager Gateway

81 7 Appendix C Loopback Adapter Configuration To configure a Microsoft Loopback Adapter 1. From the Control Panel, select Add Hardware. 2. From the Add Hardware Wizard, click Next and select Yes, I have already connected the hardware. Click Next. 3. Select Install the hardware that I manually select from a list (Advanced) and click Next. 4. From the Hardware type dialog box, select Network Adapters and click Next. The list of hardware manufacturers and drivers displays. Appendix C Loopback Adapter Configuration GEI G Instruction Guide 81

82 Notes 82 GEI G WorkstationST Device Manager Gateway

83 8 Appendix D Startup Errors 8.1 Unable to Locate FOUNDATION Fieldbus Virtual HSE Adapter The Device Manager Gateway uses the Virtual HSE Adapter IP Address property value to locate the physical or loopback adapter acting as the Virtual HSE Network Adapter for the WorkstationST computer. This address is sometimes referred to as the base address, and is used in calculating the Virtual Linking Device IP Addresses used by the gateway. Device Manager Gateway Tab Description An adapter with the Virtual HSE Adapter IP Address cannot be found and the Device Manager Gateway sends an error to the Windows Event Log and shuts down. Possible Cause The base address was not entered, or was entered incorrectly Solution Add the base address to the Virtual HSE Network Adapter in the WorkstationST computer, or enter the correct Virtual HSE Network Adapter base address in the Virtual HSE Adapter IP Address field. Appendix D Startup Errors GEI G Instruction Guide 83

84 8.2 FOUNDATION Fieldbus Virtual Linking Device Limit Description The Device Manager Gateway has an internal limit of 500 virtual linking devices. The number of virtual linking devices created by the Device Manager Gateway Consumed Devices list exceeds the internal limit, an error is sent to the Windows Event Log and the gateway shuts down. Possible Cause More than 500 virtual linking devices are required for the configuration Solution Partition the linking devices between multiple Device Manager Gateways on the target UDH network. Refer to Appendix E UDH Partitioning for additional information. 8.3 FOUNDATION Fieldbus Virtual HSE Address Collision Description The Device Manager Gateway detects that one or more of the virtual linking device addresses that it is attempting to use is already in use on the virtual HSE network. An error message is sent to the Windows Event Log and the gateway shuts down. The error message includes the address or addresses where the collision has occurred. Note This should not occur when the gateway and asset management system communicate over a loopback adapter on the same computer. Possible Cause When the gateway and asset management system are running on separate computers connected by a physical virtual HSE network, the cause is typically improper partitioning between multiple gateways. If multiple gateways reference the same device, the virtual linking device addresses for the devices under them will coincide, causing address collisions on the network. Solution Verify by opening an instance of the Status Viewer for each gateway and compare the Consumed Devices list for devices consumed by multiple gateways. Fix the partitioning overlap and manually delete the virtual linking device addresses from the gateway virtual HSE adapters before restarting them. The collision could be the result of third-party devices on the virtual HSE network. The network is intended to be completely isolated between the asset management system and gateway computers, and should not have additional devices connected. If this cannot be avoided, use a different base address for the virtual HSE network adapter in the gateway. The gateway uses the first octet of the base address as the first octet in the virtual linking device addresses that it creates. For example, if there is a collision at address with the default base address of , change the base address to to move the virtual linking device address to GEI G WorkstationST Device Manager Gateway

85 9 Appendix E UDH Partitioning The Device Manager Gateway consumes all controllers on the UDH by default. The configuration allows consumed device selection at the controller level to allow the controllers on the UDH network to be partitioned between multiple gateways running on multiple WorkstationST computers. The partitioning is accomplished by selecting a mutually exclusive set of controllers in each configuration. An overlap between the consumed device lists is not allowed. UDH Partitioning with Mutually Exclusive Consumed Device Lists Appendix E UDH Partitioning GEI G Instruction Guide 85

86 Notes 86 GEI G WorkstationST Device Manager Gateway

87 10 Appendix F Create a Virtual HSE Network The Device Manager Gateway and the asset management system typically exist on the same computer configured with the Workstation ST application, and communicate using the loopback adapter. When they exist on different computers, a physical virtual HSE network is required. This network must be dedicated to the message traffic between the two, and be physically isolated from all other networks and devices. Virtual HSE network constraints include: A physical adapter in each gateway and asset management system computer connected only to the virtual HSE network Physically isolated network switches or hubs (or even a single crossover cable if computer proximity allows it) that is not part of or connected to the existing site switch No device or computer connections other than the WorkstationST computers hosting the gateway and asset management system software Appendix F Create a Virtual HSE Network GEI G Instruction Guide 87

88 Notes 88 GEI G WorkstationST Device Manager Gateway

89 11 Appendix G Enable Write Access to FOUNDATION Fieldbus Device Parameters Note This option is only available when using the Emerson AMS gateway. The Device Manager Gateway allows read-only access to FOUNDATION fieldbus device parameters by default. Appendix G Enable Write Access to FOUNDATION Fieldbus Device Parameters GEI G Instruction Guide 89

90 Note The Enable FOUNDATION Fieldbus Device Configuration Messages property allows or denies access to all FOUNDATION fieldbus device parameters. Access to the HART devices is configured at the I/O pack input/output level, and access to the HART device is unrestricted if HART is enabled on the input or output to which it is connected. Example of PHRA Output with HART Enabled 90 GEI G WorkstationST Device Manager Gateway

91 12 Appendix H HART Message Server Upgrade Issues Sites that upgrade to ControlST V04.03 and later, and use a stand-alone HART Message Server, can transition the HART Message Server functionality to the Device Manager Gateway or use an option where the stand-alone HART Message Server product continues to act as the gateway for HART messages while the Device Manager Gateway manages the FOUNDATION fieldbus devices. Upgrading to the Device Manager Gateway is recommended for long-term support reasons. If the asset management system software is installed on a WorkstationST computer, enable the Device Manager Gateway, add a loopback adapter, and configure the FOUNDATION Fieldbus Message Server property as previously described. Leave the HART Message Server property of the Device Manager Gateway disabled to avoid conflicts with the stand-alone HART Message Server. Modified Asset Management System and Device Manager Gateway System If the asset management system software is installed on a computer not in the ToolboxST application, it must be added to the system configuration. Install the WorkstationST application on it, and enable and configure the Device Manager Gateway for FOUNDATION Fieldbus Message Server functionality only. Add the computer to the ToolboxST application, and install the WorkstationST application on it. Uninstall the stand-alone HART Message Server product. On the Device Manager Gateway, enable the HART Message Server property (and FOUNDATION Fieldbus Message Server property if appropriate) and build and download the WorkstationST computer. Appendix H HART Message Server Upgrade Issues GEI G Instruction Guide 91

92 Notes 92 GEI G WorkstationST Device Manager Gateway

93 13 Appendix I Add HART Multiplexers to Yokogawa The Device Manager Status Viewer Configuration Tab displays the configuration necessary for the Yokogawa PRM to communicate with HART devices through the Device Manager Gateway. The gateway creates virtual COM ports, which make the I/O packs appear to be HART multiplexers directly connected to the COM ports. The Device Manager Gateway recommends the multiplexers be grouped under projects with names based on the Mark VIe controller and I/O cabinet that they are physically located under. The PRM only supports COM port numbers 1 through 99, so the gateway configuration must limit the available COM ports to this range. Also, the PRM has an 8-character limit on the recommended names, so the project names may need to be shortened. To add a HART multiplexer to the PRM 1. Open the Device Manager Gateway Status Viewer and select the Configuration tab. Appendix I Add HART Multiplexers to Yokogawa GEI G Instruction Guide 93

94 2. Open the PRM Setup Tool. 3. From the Tree View, expand Field Communication and Device Path, and select the Local communication path. 4. Right-click LOCAL network and select New to create a new project. 5. In the Project Name text box, enter the project name specified in the Device Manager Gateway Status Viewer Configuration tab (in this case AnalogM6e_Cab1, shortened to AM6eCab1). Click OK. 6. Right-click the new project and select New. 94 GEI G WorkstationST Device Manager Gateway

95 7. In the IOM Type text box, select MTL4840 from the drop-down list and click OK. 8. Add any additional multiplexers specified in the Device Manager Gateway PRM Configuration tab. Appendix I Add HART Multiplexers to Yokogawa GEI G Instruction Guide 95

96 9. Click the Restart Field Comm. Service button to make the changes available to PRM. 96 GEI G WorkstationST Device Manager Gateway

97 10. Start the PRM if it is not already running. Appendix I Add HART Multiplexers to Yokogawa GEI G Instruction Guide 97

98 98 GEI G WorkstationST Device Manager Gateway