APPLICATION NOTE. Advanced Diagnostic PRM Integration. COM port Packing and Field Device Tag Import

Size: px

Start display at page:

Download "APPLICATION NOTE. Advanced Diagnostic PRM Integration. COM port Packing and Field Device Tag Import"

Eileen Jennings
5 years ago
Views:

Tag Import This note is directed to users of

conjunction with the Yokogawa PRM System.

to the manual Advanced Diagnostic Solutions of

1 APPLICATION NOTE Advanced Diagnostic PRM Integration COM port Packing and Field Device Tag Import This note is directed to users of Pepperl+Fuchs Advanced Diagnostic Technology in conjunction with the Yokogawa PRM System. This document provides continuative information to the manual Advanced Diagnostic Solutions of Pepperl+Fuchs and TI 33Y05Q31-32E of Yokogawa 04/09/2008 TDOCT-1636_ENG

2 COM port Packing and Field Device Tag Import Table of Contents 1 COM Port Mapping Conditions Customized COM Port mapping Packing = 1. Each node refers to one COM port (default behavior) Packing = 2. Two nodes refer to one COM port Packing = 3. Three nodes refer to one COM port Packing = 4. Four nodes refer to one COM port Device Tag import into Diagnostic Manager Work steps Commissioning Wizard Additional Information

3 1 COM Port Mapping Conditions During the engineering procedure a mapping takes place to establish a relationship between the COM ports of the Advanced Diagnostic Module (ADM) and the appropriate PRM instance. A COM port converter connects all Advanced Diagnostic Modules on the same Diagnostic Bus to one Com port. By default each node is mapped to one COM port, depending on the real plant topology this behavior may be not ideal for any case. Therefore it is possible to change the mapping conventions of the COM ports during the engineering process, to customize the topology to the given conditions. By using the packing function it is possible to collect up to 4 nodes at one COM port. 1.1 Customized COM Port mapping You are able to choose the mapping method during the engineering procedure within the Merge Result Dialog. By default one node is mapped to one COM port. 3

4 4

5 1.1.1 Packing = 1. Each node refers to one COM port (default behavior) The figure below shows that each node is assigned to one COM port. 5

6 1.1.2 Packing = 2. Two nodes refer to one COM port The figure below shows the result. Node 01 and 02 are assigned to COM Packing = 3. Three nodes refer to one COM port 6

1.1.4 Packing = 4. Four nodes refer to one COM port The mapping always takes place in consecutive order; this means that the nodes are sorted by consecutive numbers. E.g. if packing method Four nodes per COM port is selected the nodes 1, 2, 3 and 4 are assigned to one COM port and the nodes 5 to 8 to the next COM port and so on.

7 1.1.4 Packing = 4. Four nodes refer to one COM port The mapping always takes place in consecutive order; this means that the nodes are sorted by consecutive numbers. E.g. if packing method Four nodes per COM port is selected the nodes 1, 2, 3 and 4 are assigned to one COM port and the nodes 5 to 8 to the next COM port and so on. Example: The device FCS0101 contains node 1 to 3 with three devices each and node 5 with one device. Node 4 is missing or does not contain FOUNDATION Fieldbus devices (see figure below left side) The result of the mapping is that the first 3 nodes are signed to the first COM port (COM020), but node 5 assigned to the next COM port (COM021). Within common installations only 31 Diagnostic Modules are allowed on one COM port. If four nodes with eight ALF 111 FF Communication Modules are used, 32 Diagnostic Modules may be assigned to one COM port. In this special case this assembly works fine. 7

1 Work steps Step 1: Open export dialog Choose File>Export>Maintenance Info Step 2: Select devices for export

8 2 Device Tag import into Diagnostic Manager The Diagnostic Manager provides a function to take over field device tag information from PRM to show the device tags also at the Diagnostic Module/Diagnostic Manager. 2.1 Work steps Step 1: Open export dialog Choose File>Export>Maintenance Info Step 2: Select devices for export Choose Browes within Device Selection Then choose Select and Class View. Select all Foundation Fieldbus devices and proceed with OK. 8

9 All FOUNDATION fieldbus device tag information has to be exported. Step 3: Select Export Items Choose Device within the Export Items area and proceed with OK. Export is in progress. Step 4: Import Tag Information into FDT Project Management Tool 9

$1. Start Yokogawa FDT project management tool (e.g. C:\PRM\Program\FMFieldMate.exe) 2.$ $Browse to folder C:\PRM\MaintenanceInfo\Export and choose file: PRM_MaintenanceInfo_YYYYMMDD.xml (file name contains date). Confirm message box with yes 6. Tag Information should now be shown.$

10 1. Start Yokogawa FDT project management tool (e.g. C:\PRM\Program\FMFieldMate.exe) 2. Open the project which contains the setup for the P+F ADM including the FieldConnex R Diagnostic Server (PRM) DTM. 3. Double click on node FieldConnex Diagnostic Server (PRM) 4. The Offline-parameterization Window appears. Choose Tab [FDS Topology Settings] 5. Press button [Import Device Tags]. Browse to folder C:\PRM\MaintenanceInfo\Export and choose file: PRM_MaintenanceInfo_YYYYMMDD.xml (file name contains date). Confirm message box with yes 6. Tag Information should now be shown. To take over tag information into the Diagnostic Manager a run-through of the Commissioning Wizard is required (see chapter 2.2). The figure below shows a comparison between PRM and Diagnostic Manager after Commissioning Wizard is completed, the field device tags now are consistent in both systems. Do not change field device tag information within Diagnostic Manager Changes can not be synchronized with PRM out of the Diagnostic Manager/Advanced Diagnostic Module. 10

2.2 Commissioning Wizard Additional Information During commissioning of the Advanced Diagnostic module with the Commissioning Wizard tool it is possible store the field device tag information within

11 2.2 Commissioning Wizard Additional Information During commissioning of the Advanced Diagnostic module with the Commissioning Wizard tool it is possible store the field device tag information within the Advanced Diagnostic Module. To do so it is necessary to press the button Read Tags within the Commissioning Wizard procedure. Do not change field device tag information within Diagnostic Manager Changes can not be synchronized with PRM out of the Diagnostic Manager/Advanced Diagnostic Module. 11

Tech Note. Page 1 of 34 TECHNICAL NOTE ADVANCED DIAGNOSTICS IN EMERSON ENVIRONMENT 11/03/2014 TDOCT-1558CENG

Tech Note. Page 1 of 34 TECHNICAL NOTE ADVANCED DIAGNOSTICS IN EMERSON ENVIRONMENT 11/03/2014 TDOCT-1558CENG Tech Note Page 1 of 34 TECHNICAL NOTE ADVANCED DIAGNOSTICS IN EMERSON ENVIRONMENT 11/03/2014 TDOCT-1558CENG Table of Content 1 Introduction... 3 2 Components of the Advanced Diagnostic System... 4 2.1