Micromod MOD: MODCELL Application Builder Software - Manual (Page 91)

Application Builder
APPENDIX A
APPENDIX A
DOS CONFIGURATION FILENAME EXTENSIONS
The following are the filename extensions assigned by the Application Builder
when the save and compile activities are invoked. The
filename, as described
below, is the tag name you assign during configuration.
Extension Description of Extensions
Filename .CDB = Configurator data base file for the strategy after the SAVE
DATABASE activity is invoked.
Filename = Strategy
Name.
Filename .ID1 = Instrument data base file after the COMPILE activity is
completed successfully (file is used for download to
instrument). The exact configured data base size is
displayed after a successful compile on the bottom line or it
can be determined by checking the size of this DOS file.
Filename = Instrument Tag Name.
Filename .ID2 = LCP data base file name.
Filename .BAK = At the start of compile, the ID1 file, if it exists, is renamed
with the BAK extension. If the compile is successful, a new
ID1 file is produced and the BAK file is deleted. If the
compile is unsuccessful, the BAK file is retained as a
backup. The BAK file is retained until the next successful
compile.
Filename = Instrument Tag Name.
Filename .TIF = Tagged interface file. After the COMPILE activity is
completed successfully, you are given the option of creating
this file. This file is used with PC-30.
Filename =
Instrument Tag Name.
Filename .MIF = MOD interface file (Version 3 or later). After the COMPILE
activity is completed successfully, you are given the option
of creating this comma separated text file that can be used
with any third party software that is able to interpret the
MIF.
Filename = Instrument Tag Name.
Filename .ERR = Error file after the COMPILE activity is completed with or
without errors. This file lists the latest compile errors,
warnings and informational messages such as current
consumption.
Filename = Instrument Tag Name.
A-1