• Replies 5 replies
  • Subscribers 581 subscribers
  • Views 344 views
  • Users 0 members are here
Options
Related

Update Equipment Process is Slow using a Custom Equipment Type Created in XML

Miguel

Hello

We are using Equipment Type "TESYS" that have about 400 elements in XML file.

The XML file are Created by Excel script

For testing, we create 2 instances of this type. The system works however is too slowly. 

Bellow we can find an example for a variable item. 

<output name="VARIABLE.5" file="variable.dbf" filter="'{equipment.type}={type.name}'">
<calculator name="MyAddrcalc1">{equipment.param_list[StartReadAddress]} + 6</calculator>
<field name="NAME" key="true">{equipment.TAGPREFIX}_Segundo</field>
<field name="TYPE">UINT</field>
<field name="UNIT">{equipment.IODEVICE}</field>
<field name="COMMENT">{equipment.COMMENT} - Data do Equipamento - Segundo</field>
<field name="CLUSTER" key="true">{equipment.CLUSTER}</field>
<field name="EQUIP">{equipment.name}</field>
<field name="ADDR">{MyAddrcalc1}</field>
<field name="ITEM">Segundo</field>
<field name="TAGGENLINK" load="true">TESYS.VARIABLE.5</field>
<field name="LINKED">1</field>
<field name="EDITCODE">3939343</field>
</output>

There is something wrong in this output that can be the source of slowness?

Parents
  • Unfortunately, the TAGGENLINK fields are necessary for the update equipment process. It uses this field to know which records in the variable.dbf need to be updated and which have to be ignored.

    The mechanism that the Update Equipment tool uses to read/write the dbf files is the main source of the slowliness.
    Therefore I often use project specific third-party tools (written by a customer in Visual Studio) to rebuild the dbfs from scratch.
    This tool updates a project in 3 seconds where Citect would take over 40 minutes.

    The major drawback with such a custom tool is that you cannot modify anything by hand anymore in these dbfs, because these changes will be overwritten the next time you run the tool.
Reply
  • Unfortunately, the TAGGENLINK fields are necessary for the update equipment process. It uses this field to know which records in the variable.dbf need to be updated and which have to be ignored.

    The mechanism that the Update Equipment tool uses to read/write the dbf files is the main source of the slowliness.
    Therefore I often use project specific third-party tools (written by a customer in Visual Studio) to rebuild the dbfs from scratch.
    This tool updates a project in 3 seconds where Citect would take over 40 minutes.

    The major drawback with such a custom tool is that you cannot modify anything by hand anymore in these dbfs, because these changes will be overwritten the next time you run the tool.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.