SCP / TRISIM Automatic Cross Reference Merge Utility Tool

Field Device System Integrator Modules (FDSI) Triconex Integrator Driver integrates Triconex Tricon/Trident controller modules with Foxboro Evo FBMs 232/233 through a Triconex System Access Application (TSAA) protocol that reads and writes to TriStation tag names or Modbus aliases from an operator interface. The SCP/ TRISIM Automatic Cross Reference Merge utility tool is an application to configure equivalent communication between controls executing within SCPEngine and TRISIM engines. DYNSIM 5.2 and later installs this utility with the Control Emulations option selected during install. After successful installation of the utility, complete the following procedure to set a cross reference between SCPEngine and TRISIM I/O. This tool can be invoked when the simulation is loaded into memory and contains both SCP and TRISIM engines.

1. Deploy the SCP controls. Depending on the configuration of the controls, refer to the following sections for details of loading controls:

   • Loading Controls through the ICC

   • Validating and Downloading CPs in IACC

   • Deploying controls in Foxboro Evo

2. From DYNSIM GUI, load the Simulation with DYNSIM-L engine, SCP engine, and TRISIM Engine.

3. Load the simulation, run it for a few seconds (to process the controls), and freeze it.

   Generate a Cross Reference list. A related procedure is available in the SCP Getting Started Guide in the Cross Referencing section. This step will automatically generate a file, CrossRef.txt, in the simulation directory where the SCP engine is running.

4. Review CrossRef.txt and search for IP Addresses listed in Extra Column 5. These IP Addresses correspond to the Triconex PT2 file IP Addresses.

5. Determine the IP Address that corresponds to the PT2 file.

   • In TriStation, open each PT2 file.

   • Select Controller / Configuration / TriStation Communication.

   • Note the IP Address.

   • Correlate this IP Address with the name of the corresponding TRISIM engine name.

6. For each PT2 file, export the Tagname database.

   • In TriStation, change to the Application Workspace Pane.

   • Right-click the Tagname Declarations.

   • Select Export.

   • Type in a file name and navigate to the required location.

   • Change the Type to Comma Delimited Text Files (*.txt).

   • Select Export.

7. In the DYNSIM GUI, edit each TRISIM engine’s configuration and verify that the Path and file to X-Ref Auto-gen output is set to the name and location of the file generated in the previous step. If a change is made, shutdown and restart the simulation.

8. In the DYNSIM GUI, click Update XREF with Foxboro / Triconex I/O on the Tools menu. The Cross Reference Update display opens.

9. Select the Merge SCP TRISIM checkbox and select the Merge new data with existing XREF radio button.

   

10. The Cross Reference Merge graphical user interface appears as shown below.

    

11. In FSIM XRef Data, browse to the cross reference output file (CrossRef.txt) that contains the SCP engine I/O. The application automatically displays the available SCP engines in the text box next to the FSIM Xref Data field.

12. From the TRISIM Engine drop-down menu, select the name corresponding to the equivalent Triconex PT2 file IP address (determined in step 4).

13. In the TRISIM Tag Declaration Data text box, browse to the Tag Export file that is generated from the TriStation Application (determined in step 5).

14. In the Merged XRef Data text box, provide the output file path.

15. Click the Start button.

16. The SCPEngine-TRISIM cross reference file is generated in the path mentioned in the Merged XRef Data text box.

17. In DYNSIM GUI, Navigate to File → Import → X-Refs to invoke ‘Import X-Refs’ window. Select Replace all existing xrefs in database and click Import. Verify in the Xref table that the SCP engine’s FBM232/233 I/O points are cross referenced to the TRISIM points with the corresponding alias name.