How to configure a TeSys T with EHDCS - Knowledge Base

Knowledge Base

How to configure a TeSys T with EHDCS

Francisco José Chito Rodríguez

Rev 1.0 25 February 2020

Knowledge Base - How to configure a TeSys T with EHDCS

2

Disclaimer

© 2020 Schneider Electric. All rights reserved.

Trademarks

Schneider Electric has made every effort to supply trademark information about company names, products

and services mentioned in this manual. Trademarks shown below were derived from various sources.

EcoStruxure Control Expert, EcoStruxure Hybrid DCS, So Move, TeSys T are trademarks owned by

Schneider Electric or its affiliated companies. All other trademarks are the property of their respective

owners.

General Notice:

Some product names used in this manual are used for identification purposes only and may be trademarks

of their respective companies.


3

Table of Contents

1 INTRODUCTION....................................................................................................................................... 4

2 CASE STUDY DESCRIPTION ................................................................................................................. 5

Installation of the TesysT library in EHDCS .................................................................................... 5

Creating the TesysT in the Topology Manager ............................................................................... 6 2.2.1 Unlock manually the pins ............................................................................................................... 10 2.2.2 Modification of the GPL Template .................................................................................................. 13 2.2.3 Test of the Device DTM .................................................................................................................. 15

3 CONCLUSION ........................................................................................................................................ 19


4

1 INTRODUCTION

When a TeSysT is created in EHDCS from the Topology Manager, the DTM of the Generic Modbus Device is automatically added. This cannot be used to parametrize the TeSysT inside EHDCS and other tools such as web client or SoMove are required for this purpose.

The objective of this KB is to describe the necessary steps to integrate the TeSysT Device DTM in EHDCS and connect it to the GPL TeSysT DFB. Hence, we will be able to parametrize the TeSysT as if it were with SoMove.


5

2 CASE STUDY DESCRIPTION

Installation of the TesysT library in EHDCS It is necessary to install the TeSysT library in EHDCS so that the DTM is available. This can be done in the System Server Configuration Wizard by adding the extension browsing to the install wizard of the TeSysT DTM supplied by Schneider Electric. As the installation wizard is not compatible with silent installation, the selection of the mode should be “Manual”. If not, the installation process will be stopped in background waiting for user interaction and it will not finish.

Startup the System Server. The InstallShield Wizard of the EcoStruxure Hybrid DCS virtual machine will

appear. Follow the instructions to complete the installation.


6

Creating the TeSysT in the Topology Manager Configure the M580 from the topology manager. Add the TeSysT DTM by right click in the CPU or in a NOC.

For a TesysT with Modbus TCP capabilities, select any reference like LTMRxxxexxx, eg: LTMR08EBD.

Later, in the Parameter List tab, Process Data, select any of the first two options. In our case, EIOS_TeSysT:


7

Finally, set the proper Address and Request settings by configuring the DTM in the CPU or NOC:


8

The Unit ID is by default 255. With a real TeSysT tested in the lab, the default Unit ID configured in the device is 1. We recommend setting also 1 in the DTM as shown in the snapshot. Now refine the control project and click on “Access to unmapped hardware (Device DDTs)”

Click on Next and add the TeSysT DDT which was previously defined in the Topology Manager. Click OK to finish.

Now the Device DDT will be available in the control project.


9

Now we instantiate the TeSysT from the GPL. For this example, we choose the $TesysTE. We also instantiate for example a $Motor2, and link it to the $TesysTE instance:


10

After assigning and generating, we refine the control project and open the section where these instances are assigned to locate the TeSysTE DFB (called EIOSTESYST)

By default, the pins “IOScannerStatus” and “Inputs” from the GPL DFB EIOSTESYT are connected to DDTs prepared to be addressed by the Generic Modbus TCP DTM. They come this way since the template definition, so they are locked from the template. For the DFB to work with the TeSysT Device DTM, we connect the “DTMInputs” and “DTMOutputs” to the TeSysT Device DTM. Also, we connect the “IOScannerStatus” to the Freshness variable of the TeSysT Device DTM. The GPL Instance $TesysTE (and the similar ones of the GPK) does not offer the possibility of not connecting those pins “DTMInputs” and “IOScannerStatus”, so there are two options: 1) We unlock manually the pins and connect them to the TeSysT Device DTM. We will use this option for

testing purposes in the case when not many TeSysT instances are needed.

2) We modify the template and create a new version with those pins disconnected. This option will be suggested when many TeSysT are needed, so as not to unlock manually the pins.

2.2.1 Unlock manually the pins

We right click on the TesysTE_v2_TesysT_IData^ variable to unlock it and delete it. We do the same with TesysTE_v2_TesysT_IOSSts^


11

Connect the “IOScannerStatus”, “DTMInputs” and “DTMOutputs” pins to the Device DTM which we had imported previously with the option “Access to unmapped hardware (Device DDTs)” as per the snapshot below:


12

Now we click on check consistency to declare this section as inconsistent and therefore unlink the facet.

In the Check Consistency window, click Unlink:

Now the $TesysTE_UL facet will be marked as unlinked so it will not be overwritten with further generation operations from EHDCs.


13

2.2.2 Modification of the GPL Template In the case when multiple instances of TeSysT are required, it is less time consuming to create a customized $TesysTE_UL template with the corresponding pins of the DBF already disconnected. We edit the $TesysTE_UL from the Global Template Editor. It is located under “General Purpose Library”, “Devices”, “Control Services”, “Control Logic”:

Click on “Templatizer”:

Click on the arrow icon to open the Control Expert participant and afterwards focus in the EIOSTESYST DFB:


14

Disconnect the pins “IOScannerStatus” and “Inputs”

Save the UL composite with a different name than the default GPL library. Also, save all the upper composites in the same way so as not to be overwritten by future releases of the GPL library.


15

Now using this template, the pins will by disconnected by default. Still, the pins DTMInputs and DTMOutputs would need to be manually connected.

2.2.3 Test of the Device DTM Once the control logic project is built and deployed, we can configure it from the topology manager in order to get access to the Device DTM. Open the DTM Browser, right click on the TeSysT DTM and connect.

Once connected, open it by double click.


16

Click in the icon to switch to synchronized mode. Press Alt+F in the following pop up:


17

The Device DTM will appear as synchronized and connected. Now all the information is live data, with the possibility of modifying it.


18

If we include a supervision page with the TeSysT and start it, we will be able to confirm that the information from the Device DTM is correctly mapped to the EIOSTESYST DFB:


19

3 CONCLUSION

There are three disadvantages of instantiating the TeSysT Device DTM.

1) A Control Expert participant is required just for doing an operation in the asset, causing the need to use the DCS engineering interface. However, a user with just an asset profile connects directly to the asset without accessing the DCS.

2) The mapping is done manually by refining the control logic instead of benefiting from the mapping services of EHDCS.

3) If there are many Device DTMs instantiated, the size of the Control Expert application may increase significantly.

As a result, this KB is suggested for not large applications where the customer has specifically asked still to be able to use the Control Expert interface to parametrize the TeSysT devices. This way, it is not needed to install any additional tool like SoMove.

How to configure a TeSys T with EHDCS - Knowledge Base

Documents

Transcript of How to configure a TeSys T with EHDCS - Knowledge Base