Start with the Table of Contents - Miscellaneous Indices chapter. Click on Function Codes. In the Index to all Function Codes, click on the Function Code 30 entry to get to the list of all FC 30 blocks in your system.
You are now at a list of all the FC 30 blocks in the system. Scroll down the list until you get to the module you want, in this case, Loop 11, PCU 10, Module 2 (Module 11,10,02 in DBDOC terms) and click on the highlighted entry to call up that block. You will see the block in the CLD or CAD sheet, usually with a line showing it is (probably) used. If you turn on "attributes" with the "A" key, you will see if the block has a tag. You should, at least for a start, assume that it is used if it has a tag or if it has an output reference.
The example shows that the first block is tagged "1-TI-2241" and that it has a line carrying its value someplace to boot. Probably used, eh?
Now you simply walk through the FC 30 blocks with the "L" key ("shift L" to go up). The same functionality is given by
and
in the icons.When you get to one that has no line and no tag, you have found a candidate spare block.
Clicking on the block number (1501) brings up the index of all the places in the world where this block is purported to be used, hopefully only its source right here. This one certainly seems to be unused.
It makes sense to be satisfied that you have a good enough DBDOC build that you can count on the fact the block is not used. For example, it is possible that it is imported by some other project, and you did not build all the projects together in your DBDOC build. If that could be the case, you should do further analysis.
However, no other tools can get you this far this fast. We are always ready to help you be sure you have a good DBDOC build that resolves everything. You have a candidate spare block and it really did not take very long.
What do you do if you walk right through Module 11,10,02 without finding a spare? You can go back through the blocks and click on the output block number, looking for blocks that are not used in any graphics. Although these might be in your history system, you can go after that usage and perhaps find that the block can be re-purposed with no problem.
When you are walking through the blocks checking for how they are used, the key sequence is easy enough to do semi-automatically:
- click on output block number
- back-space to get back to the function code index
- type "L" (or "l") to get to the next linked block and repeat
There are, of course, other ways to do this. It is very nice when all spare blocks get put into boneyard pages. However, that is not always the case. When you have to find one and see how it is used or not, this DBDOC technique will certainly help you.
This comment has been removed by the author.
ReplyDeleteHi Geoff
ReplyDeleteIt is possible that a block without a wire out and without a tag from an HMI database is still used. We have third party systems such as OSIsoft PI that look at exception reporting blocks that are only for its use only. That is why it is important to build into each build all applicable databases that use the DCS configuration. When you include the PI database into the build the table of contents for that block shows the PI database entry if it has one. Manipulation of both the xls file name and the worksheet name of the PI database export allows a user to easily identify the TOC entry as to where the block is used.
Cheers
Andrew
Specialist Process Engineer
CHH Tasman, Kawerau
Just another comment Geoff about spare blocks if I may. The identification and management of spare blocks is very important for those of use with Network 90 and Infi 90 MFC or MFP controllers. Spare blocks cannot be deleted with a controller in execute mode. Therefore these spare blocks must be put away or identified appropriately as you so rightly say. However as you know there are various function codes that must be tied to some other block otherwise the config can either not be compiled or not downloaded to the backup module. I had a discussion with others on the Infi 90 users forum at the following link about this topic. (Login may be required)
ReplyDeletehttp://infi90users.com/index.php/forum/4-need-help/184-function-codes-that-must-be-connected-when-spare
This discussed which blocks require tying to others when spare or removed from functioning configurations so that we can compile or download. A definitive list was not established and the conversation ended. This brings me to my point about how to indentify clearly that spare blocks that have to be tied to others are in fact spare or not.
Also entire sections of configuration can often be cut and pasted to boneyards or spares sheets for later use and they may also show up as being used and not in fact spare either.
Another conundrum I found was the use of Adapt blocks. If an adapt block is placed on a spares sheet and is tied to a constant block or other analog blocks the block may still be adapting working configuration unbeknownst to the user. Despite the appearance of the block as being on a spares sheet and available for use it may not be identified in some automatic spares identification algorithm. Again care must be taken.
Cheers
Andrew
Specialist Process Engineer
CHH Tasman, Kawerau