AutoPLANT P&ID Valve labels composed of various data

[Tomek]

We need to place in the label of Valve some data that origin from other tables, like Area, Line Number. How to set it up?

We found that size is copied from Line data, when label is being built, however it is not written into the Valve table. Why is it so?

Also, we found that Valve size label component reads dynamically data from line size, and when it is written manually into the table (using catt...), the label component is updated instantly.

What is your advise if we need to build the label from components: Area-LineNumber-ValveTag?

Thanks in advance!

[Rijkwerd]

To make a label visible. Select 'Attribute visibility' in the menu P&ID Tools>>Update. Select the block and the field you would like to see.

If the attribute is not threre than you should add the attribute to the drawing by choosing 'Annotation Tool' in the P&ID Tools menu. Here you can place any field available in the database.

The line size left empty means that the size will be copied from the pipesize. Fill to overwrite or clear to link automatic. Both in the database as the CATT dialog screens.

My advice to create the 'Area-LineNumber-ValveTag' is to insert that with the annotation tool. You can add different fields together in one text. If you need this done in the standard tagging of the valve you should addapt the xdhv block. And if the shape and length of the fields have to much variation you should create and extra field in the database, and have this updated with the field values Area, LineNumber and ValveTag.

[PartRidge]

If you adjust the System View for Manual Valves you can then modify the valve annotating block used by p&id to place the values automatically if the values exist. The only value you may have trouble getting to populate automatically is the Valve Area field. This could be setup in the pidsup if I remember correctly. You will need to modify a few blocks for the annotation since it uses different blocks depending on it being an angle valve or not. Remember any modified block then needs to be placed in a custom symbol directory and then any existing definitions replaced or updated in the p&id.