User guide

The Configuration File
5-16: Creating and Updating BOMs
The Configuration File
The config file determines where
bn_bomprocess
finds the current BOM; the
include, change, and depop files; what types of information to generate, etc. Many
of the command-line switches previously used have been replaced (for most users)
by settings that you make in the configuration file.
Creating and Specifying a Configuration File
You can create and specify a config file in two different ways:
• If you’re using
mechbom
or
xcelbom
, they will create the config file for you,
with the proper settings so it will work right when they run
bn_bomprocess
internally. (It appears in your directory as
config.ini
or
xcelconfig.ini
.)
• If you’re using
bn_bomprocess
directly, the easiest way to create a config
file is by running
bn_bomprocess
and specifying a schematic name, project
name, or part number, without using the -
config
parameter, for example:
bn_bomprocess
ProjectName
This will create a file named
ProjectName
.
cfg
, as well as a log file, in your
working directory. The file might be named
mantaray.cfg
, or
115779-A.cfg
.
Note:
Typically, most people will be extracting parts from a schematic. In this case, you’ll create a
config file for a schematic, so use the schematic name where
ProjectName
is shown.
You may now edit and rename this config file as you wish. After you have
created the file, use the following command to create a BOM from it:
bn_bomprocess
ProjectName
-config
ConfigFileName
Using Configuration Files for Different Purposes
The
bn_bomprocess
utility contains a fair amount of heritage and legacy
capability. Some of this is reflected in the config file.
You can use the config file, for example, to:
• Create a BOM for mechanical parts without a schematic being present.
• Create a BOM where the include file for mechanical parts and the schematic
itself are or are not in the same working directory.
• Compare two BOMs.