• Replies 5 replies
  • Subscribers 581 subscribers
  • Views 342 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
  • Hi Patrick, I hope this request is not out of order, but would there be any chance of sharing such a tool? We have taken the approach that all of the configuration for a piece of equipment must be contained in the parameters or custom fields of the equipment, so the limitation of not being able to edit the result is not a problem for us. There are pros and cons to this approach when it comes to flexibility of course, however I have previously found that there are times when it is good to start again because the equipment update goes a bit wrong.
Reply
  • Hi Patrick, I hope this request is not out of order, but would there be any chance of sharing such a tool? We have taken the approach that all of the configuration for a piece of equipment must be contained in the parameters or custom fields of the equipment, so the limitation of not being able to edit the result is not a problem for us. There are pros and cons to this approach when it comes to flexibility of course, however I have previously found that there are times when it is good to start again because the equipment update goes a bit wrong.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.