Micromod MOD: MODCELL Application Builder Software User Manual
Page 67
Application Builder
CONFIGURATION
6.
Create loop compounds for the instrument, query each loop compound and
identify it, double click on loop compound to enter it, configure the loop
block, make function block choices, and configure blocks (Section 5.5).
Take the time to assign meaningful tag names.
7.
Compound function blocks as necessary to make application groups or
states (Section 5.6).
A strategy segment saved as a compound can be loaded for use
elsewhere in your strategy or in another instrument as long as the
functions are at an equivalent level. For example, a compound built
using loop level functions can only be placed in another loop.
8.
Make connections (Section 5.7).
9.
Connect to list blocks. For reports, open list blocks after all connections
are made so the block can “find” its connections (Section 5.8).
A list block requires the existence of the source blocks to make a
connection. A configured list may contain other configured lists unless
it is used to collect Modbus data. If the block with data base reports
connections is not opened and entered after connections are made the
connections will be reported as NONE.
10. Compile data base configuration and make fixes if required (Section 5.9).
A database that is successfully compiled can be downloaded to an
instrument and/or used to build a strategy for your PC based operator
displays. Compile as you build to check your work.
11. DOWNLOAD data base configuration to instrument (Section 5.10). Make
sure your serial ports are set up properly (Section 4.5).
12. Make a text file of database and print hard copy if desired (Section 4.13).
13. Optionally, make a backup copy of database configuration, using the Save
Database activity and specify an extension such as .SAV (Section 4.4).
14. Exit Application Builder (Section 4.2).
At this point you can configure your operator interface strategy. For
PC-30, use the TIF file created after a successful compile to build a
strategy (third party software is supported by the MIF file).
Any old data files can be deleted from disk while out of the Application
Builder. See Appendix A for a description of data files generated.
5-3