Displayed tag has no source - module not built [ERROR 266]

No source: Module 1,01,02 Block 1001 (TAGNAME, TAGNAME2) used in display - module not built

This message means that the tags indicated are used on graphics, but the source modules for them were not built from the CLD/CAD files.

This message is caused by:

  1. The block comes from an external source like PI or FDI that you have not defined to be external.
  2. The block comes from a module that was not built.
  3. Some element of the loop, PCU or module (and block), or a combination of these, defined for the tag is incorrect.

You should make sure that the blocks exist first. In the third case above, it is often the case that the error is in the definition of the tag and the block, in fact, does exist. Typing errors can be the cause of these messages. Also, you should check groups of blocks to make sure that the rules that define blocks that are external are being followed.

Note also that you can mark the blocks as being available for monitoring only in case 3. In cases 1 and 2, DBDOC cannot get a value for the block, which is the same as Composer and WinTools, because the source is not actually a module within a real PCU.

If there is no external source for these tags, the operator graphics cannot display a correct value for them.

Example: 

 No source: Module 4,01,02 Block 133 (06-TC-5304) used in display - module not built
 No source: Module 4,01,02 Block 1001 (B12BREAKER) used in display - module not built
 No source: Module 4,01,02 Block 1002 (890STEAM) used in display - module not built
 No source: Module 4,01,02 Block 1003 (B1BREAKER) used in display - module not built
 No source: Module 4,01,02 Block 1004 (BBUSLESS) used in display - module not built
 No source: Module 4,01,02 Block 1005 (B11BREAKER) used in display - module not built
 No source: Module 4,01,02 Block 1006 (RCMLOADSHED) used in display - module not built

Here we can see that the first block is well off on its own, meaning it may be an orphan, and a potential error. The big section of consecutive blocks is probably correct, but should be checked anyway.

In BuildPlus, use Tools/Project Options/Define Blocks with External Sources to define blocks that do not exist to eliminate the messages if they are valid references. The dialog allows you to input the Loop, PCU, Module and Block Range info for external blocks that actually exist.

This message is likely to show an error in the system configuration. It should be reviewed. The issue raised may be in unused logic or graphics, or have other realities that make it a non-issue.

Please contact us for help resolving your error messages.