| BOM_NO_POP_PROP |
DNI |
This Setting is used to pick a list of properties that excludes a reference designators from installation, but keeps the part in the BOM for purchasing
When the BOM is generated by the netlist convert routine, any parts with this property found to be true will be printed on a separate row. |
| BOM_NO_POP_TRUE_VALS |
TRUE,YES,1 |
This Setting is used to pick a property and value that excludes reference designators from installation, but keeps the part in the BOM for purchasing
When the BOM is generated by the netlist convert routine, any parts with this property enabled will be printed on a separate row.
###This was recently renamed from BOM_NO_PROP_TRUE_VALS and this setting is not yet Used |
| CAPACITANCE_DERATING |
90 |
Capacitance derating value (percentage). Used as the default derating value for capacitors in the power rail report.
Capacitors are multiplied by this value to determine the real capacitance value. |
| CAP_VOLTAGE_DERATING |
25 |
Capacitance voltage derating setpoint (percentage).
Used as pass/fail limit for calculated voltage derating
The calculated voltage derating shown in the rail capacitance tables is 100*(1-netVoltage/CapVoltage)
If the calculated voltage derating is less than this setpoint,
the capacitor on that rail will be flagged and added to overvoltage capacitor report
|
| DNI_TRUE_VALS |
TRUE,1,YES,DNI |
This is a list of the values that make the DO_NOT_INSTALL_PROP true (comma separated vals like:TRUE,1,YES) |
| DO_NOT_INSTALL_PROP |
VALUE,DNI |
This is a comma separated list of properties that will be used to determine if a part is not included in a BOM
Could look like BOM_IGNORE,DNI.
Any part with this Property found True will not be included in the BOM (unlike the BOM_NO_POP_PROP) |
| HIDE_EMPTY_REPORT_COLUMNS |
1 |
If a Property does not exist for all instances in a design (or sub-set of design instances like added nets) we will not add that property column to the reports even if the report is configured to use it. |
| HIDE_GLOBALLY_ABSENT_PROPERTIES |
0 |
When we compare Net Properties, Node Properties, or Part Properties between 2 designs, we will not create a difference if the Property exists in one design but is globally absent in the other design |
| IGNORE_NET_PROP_DIFFS |
0 |
Property names listed in this comma separated list
will be ignored when properties for the same NET_NAME in the 2 netLists are compared
The following properties are never compared so they should not need to be added
NET_NAME NET_CONNS NET_ID_FROM_PINS NET_ID_XCHECKED NL_INDEX NODE_LIST
HIER_NET_NAME LOGICAL_PATH C_SIGNAL
The user can look at the net_prop difference report and add any properties to this list
that they do not want to include in the comparison
|
| IS_BOM_COMPARE |
0 |
If set, NetBom will only Compare PartLists,
and the Netlist compare operation will be skipped.
NetBom will help detect this for the user on the first pass of a diff or convert opeartion
if one of the NETLIST files is a BOM spreadsheet.
If this is not set, the user will be asked if they want to set it when the operation is run. |
| KEY_PROP_IGNORE_LIST |
C_PATH,P_PATH,ALT_SYMBOLS,UNIQUE_NET_CONNS |
The BOM_DIFF engine will filter any of these props out of the KEY_PROP_LIST before
comparing part properties
it is entered as a single PropName or comma separated list of Propertieeslike:
MY_LIB,Validate_,GEOMETRY.HEIGHT
|
| KEY_PROP_LIST |
BODY_NAME,BOM_IGNORE,CDS_LIB,CDS_PART_NAME,CLASS,COLOR,CURRENT,C_TEMPERATURE,DCR,DESC,DESCRIPTION,DIELECTRIC,DOCUMENT,DRAWING,EXC_MNG_MATCHING,FREQ,HEIGHT,INSTANCE,IS_CAPACITOR,JEDEC_TYPE,J_TEMPERATURE,LIB_INFO,LOCATION,MANUFACTURER,MANUFACTURER_PN,MAX_CASE_DISS_LIMIT,MAX_POWER_DISS,MGTOL_VAR1,MGTOL_VAR2,MGTOL_VAR3,MULT_QTY,NAME,NOT_FEEDTHRU,OC_LIBRARY,OHM_LIMIT,OHM_RESISTANCE,ORIENTATION,PACK_TYPE,PAGE,PARENT_PART_TYPE,PARENT_PPT,PARENT_PPT_PART,PART_CAPACITANCE,PART_IN_LIB,PART_LIB_MODIFIER,PART_NAME,PART_NUMBER,PART_TYPE,PATH,PHYS_DES_PREFIX,PHYS_PAGE,PHY_DES_PREFIX,PN,POWER,PRIMITIVE,PRIM_FILE,REF_DES,REMOTE,REMOVE,REUSE_INSTANCE,REUSE_NAME,REUSE_PID,REVISION,ROOM,ROT,R_FREQ,SCH_MODIFIED_PART,SEC,SECTION_NUM,SECTION_PAGE_INFO,SEC_TYPE,SPEED,STOP_POWER_TRACE_REASON,SUBDESIGN_NAME,SUBDESIGN_SUFFIX,SYMBOL_NAME,TECH,TEMP,TH_JA_RES,TH_JC_RES,TOL,TYPE,TYP_POWER_DISS,VALUE,VARIANT,VENDOR,VENDOR_PN,VER,VIN,VOLT,VOLTAGE,VOUT,WX2_FPGA_VARIANT,XC2_FPGA_VARIANT,XY |
The BOM_DIFF engine will compare these properties for each refdes
in the 2 bom revisions and report if they are different...
it can be entered as a single propName or as a comma separated list like:
JEDEC_TYPE,VALUE,TYPE
If you leave this blank(New Default),
NetBom will gather all the part properties it detects and create the list for you
(while excluding any props in the KEY_PROP_IGNORE_LIST)
|
| NETLIST_REPORT_HEADER_PROPS |
0 |
This can add extra headers to the Netlist info report. Separate headers with commas. |
| NET_PROP_RENAME_RULES |
0 |
Comma Separated List of Was:Is rules to change Net Property Names in an existing netlist.
This
Example:
^_(.*):$1
This will remove a leading '_' from a property
_WebLink:WebLink will rename the _WebLink property to WebLink
|
| NET_TRACE_COMPONENT_STOP |
CONNECTOR,IC |
This comma-separated list of part types tells NetBom which nodes should stop the net trace when encountered.
By default it is assumed that connector/ic parts should be used.
These part types can be configured to be matched to parts in the Part Type Configuration GUI. |
| NET_TRACE_NET_NODE_LIMIT |
0 |
This setting governs the max number of pins that a net can have in a net trace before the trace stops. Use 0 in order to remove this limit.
A higher number represents more pins that the net trace will tolerate before it stops tracing.
Higher numbers means more complex traces, which can be desireable in some cases and undeseriable in other cases. |
| NET_TRACE_PINCNT_WARN_LIMIT |
15 |
If NetBom encounters a part that exceeds this number and isn't assigned one of the part types in NET_TRACE_COMPONENT_STOP, it will warn the user that a large part exists in the netlist that won't be stopped during net tracing. Large parts slow down the net tracing and should be avoided unless neccessary. |
| NET_TRACE_PIN_LIMIT |
0 |
This setting governs the max number of pins that a node can have in a net trace before the net trace stops. Use 0 in order to remove this limit.
The higher the pin limit, the further the net trace will go. Along with this, the higher the limit, the exponentially longer time the net trace will take.
If a net trace is taking too long, it may be because this number is too high. |
| NEW_NETLIST |
CET-1009-NetBom_FPGA_Endpoint_Verify\test_case_1_xilinx_lattice\packaged_20210921_02\pstxnet.dat |
NEW_NETLIST use for diffing and converting netlists.
For Orcad/AllegroHDL You choose the pstxnet.dat file and netBom will find the matching pstxprt.dat and pstchip.dat files
For Mentor, you can choose the .kyn or nets.fwd file
For EDIF netlists, you choose the .edf file |
| NEW_PART_TYPE_CONFIG_FILE |
part_type_config.json.txt |
This will point to the location of the part type settings file for New Designs. |
| NODE_PROP_RENAME_RULES |
0 |
Comma Separated List of Was:Is rules to change Node Property Names in an existing netlist.
This
Example:
^_(.*):$1
This will remove a leading '_' from a property
_WebLink:WebLink will rename the _WebLink property to WebLink
|
| OLD_NETLIST |
0 |
OLD_NETLIST for diffing BOMs and NETLISTS.
For Orcad/AllegroHDL You choose the pstxnet.dat file and netBom will find the matching pstxprt.dat and pstchip.dat files
For Mentor, you can choose the .kyn or nets.fwd file
For EDIF netlists, you choose the .edf file |
| OLD_PART_TYPE_CONFIG_FILE |
part_type_config.js.txt |
This will point to the location of the part type settings file for Old Designs. |
| PART_NUMBER_PROPS |
PART_NUMBER,ID,MPN |
The BOM_DIFF engine and NETLIST Creators will use this comma separated list of properties to search for the device part-number, It will use the first one it finds in this list
The property name is case insensitive. |
| PART_PROPVAL_RENAME_RULES |
0 |
Comma Separated List of Was:Is rules to change Part Property Values in an existing netlist.
This
Example:
^_(.*):$1
This will remove a leading '_' from a property
_WebLink:WebLink will rename the _WebLink property to WebLink
|
| PART_PROP_RENAME_RULES |
0 |
Comma Separated List of Was:Is rules to change Part Property Names in an existing netlist.
This
Example:
^_(.*):$1
This will remove a leading '_' from a property
_WebLink:WebLink will rename the _WebLink property to WebLink
|
| POLAR_CAP_PART_TYPES |
POLARIZED_CAP |
These part types will be considered polar capacitors when auditing for reversed voltage capacitors. |
| POLAR_CAP_VOLTAGE_DERATING |
25 |
This setting overrides the CAP_VOLTAGE_DERATING setting for part types identified as polar capacitors.
Polar capacitance voltage derating setpoint (percentage).
Used as pass/fail limit for calculated voltage derating.
The calculated voltage derating shown in the rail capacitance tables is 100*(1-netVoltage/CapVoltage).
If the calculated voltage derating is less than this setpoint,
the capacitor on that rail will be flagged and added to overvoltage capacitor report. |
| POWER_RAIL_CAP_PART_TYPES |
CAPACITOR,POLARIZED_CAP |
These are the part types that will be considered a capacitor when determining power rails. |
| POWER_RAIL_CAP_VALUE_MIN |
50 |
Minimum value (in pF) that a capacitor needs in order to be included in the power rail report.
Set to zero in order to have no minimum.
Example:
A rail is identified with three caps.
Capacitor 1: 1uf
Capacitor 2: 2.5uF
Capacitor 3: 45pF
If the minimum value is set to 50pF, then capacitor 3 will not be included in the report.
Furthermore, if POWER_RAIL_MIN_CAP_COUNT is set to 3 or more (the default is 3), then this will be excluded from the report entirely because it does not have enough capacitors. |
| POWER_RAIL_MIN_CAP_COUNT |
3 |
Minimum number of capacitors that a net needs in order to be considered a power rail.
This number is combined with net name voltage matching to determine which nets are power rails.
The voltage matching system can be configured through the VOLTAGE_MATCH_OVERRIDE CSET. |
| POWER_RAIL_RESISTOR_OHM_LIMIT |
10 |
This is the maximum value (in OHMs) that a resistor can have in order for it to be traced through when determining power rails.
When we are evaluating a potential power net, we check the number of caps that are connected to the net.
We trace through small components, including resistors, to find the capacitors, and this settings governs if we stop at a given resistor based on its OHM value. |
| POWER_RAIL_TOTAL_CAP_VALUE_MIN |
1 |
Minimum value (in uF) that the caps on a rail should have in order for the rail to be considered a power rail and
to be included in the power rail report.
For example, with the default miniumum of 1uF, if there is a power rail with five 0.1uF caps and no other caps,
the total cap value for the rail will be 0.5uF and will be excluded from the power rail report. |
| REFDES_RENAME_RULES |
0 |
Comma Separated List of Was:Is rules to change reference designators in an existing netlist.
This can be used when the user knows they are changing many refdes in the new NetList and they don't want them to show up in the difference reports
Example:
_57$:_S5_S7,_46$:_S4_S6,_02$:_S0_S2,_13$:_S1_S3
this will replace any location ending in
_57 with _S5_S7,
_46 with S4_S6,
_02 with S2_S2,
_13 with S1_S3,
|
| SINGLE_NODE_NET_FILTERS |
NC_,_NC,NC,^$UN |
This comma-separated list is used to validate single node nets.
If a net name of a single node net contains any of these matches it will not be included in the single node net reports. |
| USE_PSTCMDB_PROPS |
1 |
If enabled, this setting will make NetBom merge all net and part properties found in the PSTCMDB.dat file into the netlist and partlist databases. |
| VOLTAGE_MATCH_OVERRIDE |
customer_volt_match_rules.txt |
This will allow the user to have custom voltage matching algorithms beyond what is available in NetBom by default.
VOLTAGE_MATCH_OVERRIDE holds a file path to a txt file.
If this field is populated, NetBom will attempt to parse and use it instead of the default matching algorithms.
If the file is not found or is unable to be parsed, NetBom will use the default matching as a fall-back. |
