No source: Module 1,01,02 Block 1001 imported - module not built
This message means that a block is being imported from a module that was not built.
Blocks may be from modules that you have not included in this build, in which case this file gives you a check list.
External systems may put values on blocks that are seen by the loop as coming from an indicated module that does not actually exist.
There are three circumstances that generate this message:
1. The block comes from an external source like PI or FDI.
Example:
--Generating index: Module 2,01,08 Block Index - module not built No source: Module 2,01,08 Block 1350 imported - module not built No source: Module 2,01,08 Block 3131 imported - module not built No source: Module 2,01,08 Block 3220 imported - module not built No source: Module 2,01,08 Block 3222 imported - module not built No source: Module 2,01,08 Block 3227 imported - module not built No source: Module 2,01,08 Block 3229 imported - module not built No source: Module 2,01,08 Block 3236 imported - module not built No source: Module 2,01,08 Block 3239 imported - module not built No source: Module 2,01,08 Block 3275 imported - module not built No source: Module 2,01,08 Block 5017 imported - module not built
Here we can see that the first and last blocks are well off on their own, meaning they may be orphans, and potential errors. The middle section of consecutive blocks are probably correct, but should be checked anyway.
2. The block comes from a module that was not built.
Sometimes there are multiple INFI 90 systems in a plant. When you build all your systems together, DBDOC will check them against each other and many of these messages will disappear.
3. The error block has an incorrect specification.
In BuildPlus, use BuildPlus/Tools/Project Options/Define Blocks with External Sources to define blocks that do not exist to eliminate the messages if they are valid references. 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.