; $Name: r$Date: 2025-01-10 09:51:54 -0700 (Fri, 10 Jan 2025) $ $Rev: 98407 $ $
; comment
; 1. It appears that a quirk of errfilter makes it necessary to have a "filter" 
;    command that has to be ignored.
; 2. Some messages have to be first, like Assertion failed, because the text
;    in the message is not to be worried about by the client.
; 3. [NOT] refers to messages not converted for 10.5
;
:verbose
:filter "-" "not found (not configured)"
;
; T1340
;"[000]" "[004]" "[005]" "[013]" "[016]" "[017]" "[027]" "[039]" "[040]" "[045]" "[053]" "[066]"  "[177]" "[206]" "[314]" "[308]" "[312]" "[313]" "[315]" "[316]" "[317]" "[318]" "[319]" "[320]" "[321]" "[322]" "[323]" "[324]" "[325]" "[326]" "[327]" "[328]" "[333]" "[334]" "[335]" "[336]" "[338]" "[339]" "[340]" "[341]" "[342]" "[343]" "[344]" "[345]" "[346]" "[347]" "[348]" "[10004]" "[10005]" "[10006]" "[10013]" "[10014]" "[10026]" "[10044]" "[10045]"
:handled "-INTERNAL_UNDOCUMENTED" "Missing LBR Report" "Failed to read in record" "Failed to reseek to start" "Failed to read library" "Unknown hotspot type" "Unexpected function code" "Unable to parse node" "Regex compilation error" "Regex execution error" "Repeated problems communicating with hardware key" "Illegal value for module parameter" "has derivative lag spec " "Outdated file format" "Failed to handle line" "does not have a target defined"
:handled "-NUMBERED1" "Unknown exception in file" "will update to NVRAM every cycle" "SQLite FTS" "Possibly corrupt GPI" "must be FC" "is already linked to" "cannot link more than 4" "cannot be linked to itself" "Possibly corrupt" "Block number too high" "Unexpected control character" "Chained function block link" "Unhandled calculation" "Non-orthogonal rotation: " "Shortcut graphic name"
:handled "-NUMBERED2" "but may have been meant to be spare" "imports nonexistent" "imports out-of-range" "Unknown AC 800M block type" "Unconnected wire end" "Completely unconnected wire" "Unhandled complex source configuration" "to unconfigured variable" "Unsupported non-literal tag name" "Unresolved connection to" "Broken connection to" "Unsupported ST syntax" "Cannot determine target"
:handled "-NUMBERED3" "Inhibit tag for" "Legacy warning message" "Legacy err message" "Legacy fatal message" "DIOFCSpec associated with" "CADNames cannot be opened" "which is not supported in CFCs" "could not parsed line" "Unknown mimic file" "Unknown Bin File"
;
:handled "-CHECK_NEGATIVE_BLOCK" "Negative block number " "[037]" " Block -" " block -"
:handled "-INTERNAL_ASSERTION_FAILED" "Assertion failed" "[080]"
:handled "-INTERNAL_SQLITE_MESSAGE-PARTIAL" "SQLite step " "SQLite bind " "[081],[207],[208]"
:handled "-INTERNAL_PG2-PARTIAL" "Target is " "[291]"
:handled "-COSMETIC_NO_BORDER" "Increasing width" "Increasing height" "[022],[023]"
:handled "-CHECK_SPARE_BLOCK_USED" "Spare block imported by " "[168]"
:handled "_IREF_DOES_NOT_MATCH_MODULE" "does not match module" "does not match Module" "[10021], [10038]"
:handled "-CHECK_UNKNOWN_ATOM" "Unknown atom " "Tag atom " "[047],[264]"
:handled "-CHECK_GRAPHICAL_EXPRESSION-PARTIAL" "Only handling first tag in expression" "[048]"
:handled "-INTERNAL_BAD_DBDOC_FILE" "Parse error in file " "Missing definitions file" "[115],[292]"
:handled "-INFO_CLD_FILES_NOT_COMPILED" "Uncompiled CLD file " "[10022]"
:handled "-CHECK_CFG_FILE_TIMESTAMPS-PARTIAL" "[10034],[10035]" "**NOT IN WIKI - severity=1 (suppressed)"
:handled "-INTERNAL_GET_BLOCK" "Internal error: get_block() called on non-block tag" "[049]"
:handled "-INFO_VERTICAL_TEXT" "Vertical text " "[050]"
:handled "-BUILD_SKIPPING" "All further CAD files will be skipped" "[012]"
:handled "-INTERNAL_SKIPPING-PARTIAL" " contains no records" "Error parsing " "Invalid header or bad magic number" ": skipping" " -- skipping" "[052], [054], [055], [056], [057], [058], [059], [10011], [10012]"
:handled "-INTERNAL_MISSING_FMT" "Failed to find matching format" "[209],[210]"
:handled "-INFO_ADAPTED_COORDINATE" "ordinate adapted" "Adapted coordinates out of order" "Adapted co-ordinates out of order" "[029],[030],[032]"
:handled "-INFO_ADAPTED_RUNG" "Adapted rung spec:" "[061]"
:handled "-CHECK_ADAPT_PAGE" "Adapted block on different page:" "[044]"
:handled "-CHECK_TSTALM_PAGE" "Tested block on different page:" "[211]"
:handled "-CHECK_TSTALM_SUBSEQUENT" "checks subsequent block " "checks subsequent Block " "[212]"
:handled "-CHECK_ADAPT_PREVIOUS" "adapts previous Module" "[118]"
:handled "-INFO_GAIN_SPEC_ADAPTED" "gain spec is adapted" "Gain spec is adapted" "[119], [120]"
:handled "_ADAPT_EXECUTE_ERROR-PARTIAL" "illegally adapted" "Block 0 adapted by Block" "Block 0 adapted by Module" "Adapted block 0 does not exist" "[021], [082], [083]" 
:handled "_ADAPT_BLOCKS-PARTIAL" "Adapt " "adapt " "adapted" "adapts " "[021], [014], [176], [019], [020], [116], [117], [169]"
:handled "-CHECK_TSTQ" "tests quality on executive block" "(FC 2), which does not have quality" "(FC 50), which does not have quality" "(FC 51), which does not have quality" "(FC 52), which does not have quality" "[156]"
:handled "_TSTQ" "tests quality on " "which does not have quality" "which is not propagating quality" "[063],[071]"
:handled "_TSTALM" "tested by multiple TSTALM blocks" "Multiple TSTALM:" "[084]"
:handled "_RESTORE_BLOCK" "RESTR block Module" "[065]" "will *never* save because" "[309]"
:handled "_ADVANCED_PID" "Advanced PID " "[085],[086],[087]"
:handled "_TUNING_CONSTANTS" "active tuning constants " "has primary gain spec" "[172],[173]"
:handled "-INFO_PID_GAIN-SPAN" "product is greater than" "product is less than" "uses derivative with PV from discontinuous input" "and APID Module " "and PID Module " "[178],[179],[307]"
:handled "_AMBIGUOUS_WIRING" "Ambiguous wiring" "[121]"
:handled "-BUILD_BOGUS_BLOCK_ZERO" " for block zero on "  "[180]"
:handled "-CHECK_NESTED_INHIBIT" "Nested inhibit: tag" "[069]"
:handled "-CHECK_CIRCULAR_INHIBIT" "Circular inhibit:" "[181]"
:handled "-COSMETIC_SPACE_IN_FILENAME" "contains a space in its name" "[213]"
:handled "-CHECK_CIRCULAR_REFERENCE" "Circular reference: IREF " "[184]"
:handled "-CHECK_CIRCULAR_SYMBOL_INCLUSION" "Circular symbol inclusion" "[182],[183]"
:handled "-CHECK_CASE_DIFFERENCE" "differ in case only:" "[185]"
:handled "_DAANG_SPECS" "Multilevel alarms configured but disabled" "verify period for time-based alarms" "check for mis-configuration" "return alarm overrides" "[062],[089],[090],[091]"
:handled "-CHECK_INPUT_WIRING" "should only be wired by same function code" "Harmony I/O FC" "[186],[187]"
:handled "-INFO_FILE_SELECTION" "already defined in chapter" "[188]"
:handled "-CHECK_DUPLICATE_GLOBAL_OREF" "Duplicate global OREF" "Duplicate local OREF" "[190]" "[296]"
:handled "_DUPLICATE_SOURCE" "Duplicate source" "[092]"
:handled "-INFO_DUPLICATE_STATION_TAG" "Duplicate station tag" "[189]"
:handled "_FROZEN_EXCEPTION_REPORT_INPUT" "Duplicate off-module reference" "[093]"
:handled "_COMPOSER_SPECS-PARTIAL" "integer value" "oo small for float" "oo big for float" "[10009], [10023], [10024], [10025], [10027], [10028]"
:handled "_IREF_HAS_NO_INPUT" "does not have an input" "[096]"
:handled "-INFO_MULTIPLE_MACROS-PARTIAL" "registered multiple times" " is present in both " "[10031], [10039]"
:handled "_CHAINED_FC_PROBLEM" " wired from IREF " " part of a chain controlled by " "[095]" "[311]"
:handled "-COSMETIC_NO_WIRED_INPUT-PARTIAL" "No wired input:" "[097],[098]"
:handled "-INTERNAL_INVALID_CAD_FILE-PARTIAL" "Bad CAD magic number" "Invalid CAD file: " "Invalid record" "[002],[003],[009],[010]"
:handled "-IGNORE_INVALID_TREND-PARTIAL" "Trend:" "Trend definition trend:" "[196]"
:handled "-INTERNAL_REQUESTED_INDEX" "Requested color index " "Requested font index " "[193]"
:handled "-BUILD_FONT_PROBLEM-PARTIAL" "Font file " "font definition file" "[191],[192]"
:handled "-INFO_UNREFERENCED_GRAPHIC" "Unreferenced graphic:" "[214],[215]"
:handled "-CHECK_MISSING_DISPLAYS-PARTIAL" "references unknown graphic" "not found (not configured)" "M1 display file graphic:" "[194], [195], [196], [197], [198], [216], [267]"
:handled "_MULTIPLE_INPUT" "More than one input to connector" "[106]"
:handled "-CHECK_TSTQ_COMMUNICATION_ONLY" "tests communications quality only" "[70]"
:handled "-CHECK_REDAI_REDDI" "REDAI Module" "REDDI Module" "[072],[073],[074],[075],[076],[077],[079],[175]"
:handled "-COSMETIC_MULTIPLE_WIRES-PARTIAL" "Multiple wires at a source:" "[219]"
:handled "-CHECK_MISMATCHED_TAGNAME" "Mismatched tagname -- using" "[204],[205]"
:handled "_TAG_TYPE_MISMATCH" "Tag type mismatch:" "[102]"
:handled "_PCV_ILLEGAL_TAGNAME" "is illegal in PCView" "[104]"
:handled "_PCV_TREND_MISMATCH" "Tag/trend mismatch:" "does not have matching tag" "[105],[107]"
:handled "_TAG_MISMATCH-PARTIAL" "Tag mismatch for" "Duplicate tag" "[101],[103]"
:handled "-INTERNAL_ELEMENT_OUTSIDE_BOUNDS" "is outside configured bounds" "[202]"
:handled "-INTERNAL_UNRESOLVED_REFERENCE-PARTIAL" "GUID-named dependency" "[203]"
:handled "-INTERNAL_UNKNOWN_PICTURE_TYPE" "Unknown picture type" "[218]"
:handled "-INTERNAL_MULTIPLE_800XA_CONSOLES" "Building multiple 800xA consoles into one project file not yet supported" "[200]"
:handled "-INTERNAL_MISSING_800xA_COLOR-PARTIAL" "Unable to find PPA color" "Unable to find 800xA color" "[201]"
:handled "-INTERNAL_GRAPHIC_PRIMITIVE-PARTIAL" "Unsupported graphic primitive" "[217]"
:handled "-CHECK_LIVE_WIRE" "Live wire from "  "[199]"
:handled "-BUILD_MISSING_SYMBOL-PARTIAL" "Missing symbol or sub" "Unable to find bitmap" "[099], [100]"
:handled "-COSMETIC_LIBRARY_NOT_FOUND" "Never found library file" "missing: included " "[011],[026]"
:handled "-IGNORE_UNUSED_RUNG_SPEC" " value 002" " value 012" " value 021" " value 03" " value 04" " S2 value 01" " S2 value 021" "[124],[125],[127]"
:handled "-IGNORE_UNUSED_BLOCK_0" " is wired (block 0) but unused" "[124]"
:handled "_RUNG_BLOCK-PARTIAL" "Rung block" "[124],[125],[126],[127],[306]"
:handled "_LPM_REFERENCE_PROBLEM-PARTIAL" "Inconsistent LPM data " "[10020]"
:handled "-BUILD_NO_TAG_DATABASE" "No tag database " "[108]"
:handled "-BUILD_NO_XDC_FILE" "No valid sections found in XDC file" "[109]"
:handled "-BUILD_DATABASE_FIELD" "Failed to locate field" "Fewer fields than " "Fewer substitutions than" "[220],[221],[222],[223]"
:handled "-CHECK_MISSING_EXTERNAL_OREF" "External output reference does not exist" "[10008]"
:handled "_UNREACHABLE_OREF" "External output reference is unreachable" "attempts to read value in other " "[10015],[10016],[10017],[10018]"
:handled "_BLOCK_IMPORTED_SOURCE_NOT_FOUND" "imported - module built" "[110]"
:handled "_BLOCK_IMPORTED_MODULE_NOT_BUILT" "imported - module not built" "[265]"
:handled "_TAG_DISPLAYED_SOURCE_NOT_FOUND" "used in display - module built" "[111]"
:handled "_TAG_DISPLAYED_MODULE_NOT_BUILT" "used in display - module not built" "[266]"
:handled "-COSMETIC_NO_SOURCE_VERIFY" "No source: Verify: " "[112]"
:handled "_NO_SOURCE_OTHER" "No source" "[113]"
:handled "-INTERNAL_NON-ORTHOGONAL_ROTATION" "Non-orthogonal rotation:" "[038]"
:handled "-CHECK_OVERLAID" " overlaid at " "[225],[226]"
:handled "-INFO_OVERRIDE-PARTIAL" "Override on input" "[122]"
:handled "-CHECK_NON-ALARMING_DIGITAL" "Non-alarming digital" "[078]"
:handled "-INTERNAL_NON-LOCAL_EXIT-PARTIAL" "Got lost parsing file: expected a C record and got" "Missing string introducer" "Non-local exit" "Negative string length" "[060],[10040],[10041],[10042],[10043],[10007]"
:handled "_IMPORT_FROM_SAME_PCU" "Reference imports from same PCU:" "Reference imports Module" "Import from same PCU:" "[128]"
:handled "_SLAVE_CONFIGURATION" "see slave report " "Multiple slave FCs " "[153],[154],[155]"
:handled "_SOURCE_IN_SAME_MODULE" "Source in same module" "[157]"
:handled "_SOURCE_TO_SOURCE" "Source may be wired to another source:"  "[158]"
:handled "_TAG_INDEX-PARTIAL" "Tag index " "[159],[272]"
:handled "_REMSET_LIMITS_OUT_OF_ORDER" "REMSET limits out of order:" "[261]"
:handled "-CHECK_TAGATOM_MISMATCH" "TagAtom mismatch " "[229]"
:handled "-COSMETIC_RENAMING_BLANK_TAG" "Renaming blank tag to" "[230]"
:handled "-COSMETIC_DYNAMIC_BAR_SPAN_ZERO" "Span is zero for dynamic bar" "[231]"
:handled "_TAG_FOUND_IN_OTHER_DATABASE" "(defined in "  "[068], [288]"
:handled "_TAG_NAME_NOT_UPPER_CASE" " should be upper case" "[263]"
:handled "_TAG_NAME_NOT_FOUND" "Tag name " "not found in any database" "[067],[123],[160],[284]"
:handled "_SPEC_INPUT_INDEX" "Spec input index out of range " "[018]"
:handled "_SPEC_OUT_OF_RANGE" " out of range" "[88],[164],[165],[166],[167]"
:handled "_TOO_MANY_OUTPUTS" "Too many outputs: expected " "[137]"
:handled "-INTERNAL_UNUSED_EXTRA_INPUTS" "Unused extra inputs " "[136]"
:handled "-INTERNAL_DYNAMIC_BAR" "Unknown dynamic bar direction " "[232]"
:handled "-INTERNAL_UNHANDLED_ENTITY-PARTIAL" "Unhandled pe " "Unhandled data " "Unhandled LPM " "Unhandled Escape " "Unhandled ei " "[233],[234],[235],[236]"
:handled "-INTERNAL_UNSUPPORTED_FUNCTION" "Unsupported function" "[238]"
:handled "_UNKNOWN_SHAPE" "Unknown shape" "(missing library " "(not in library " "[041],[042],[043]"
:handled "-INTERNAL_UNSUPPORTED_RECORDS" "Unsupported Dynamic Symbol" "Unknown record type " "Unknown subtype " "[239],[240],[241],[242]"
:handled "-INTERNAL_STRANGE_ARGUMENTS-PARTIAL" "non-string second argument" "called with numeric second argument" "[243],[244]"
:handled "-INFO_OVERRIDDEN_SPEC" "instead of Module" "[10019]"
:handled "-CHECK_XREFOBJID" "for XRefObjID" "[10029],[10030]"
:handled "-CHECK_DUPLICATE_DESCRIPTOR" "Both 0 and 1 values have the same descrip" "[064]"
:handled "-INTERNAL_UNKNOWN_LOGIC_STATE" "logic state" "[245]"
:handled "-BUILD_FILE_OPEN_FAILURE-PARTIAL" "Failed to read header" "Can't open DBF file" "Failed to open file" "Database cannot be opened" "[001],[006],[10001],[290]"
:handled "-INTERNAL_INVALID_NUMBER" "Invalid block number" "Invalid loop number" "[246],[247],[248]"
:handled "_ILLEGAL_IMPORT" "Illegal import" "Data type mismatch" "[094],[129],[130],[131]"
:handled "-CHECK_ILLEGAL_IMPORT" "Extended status not imported" "[132]"
:handled "-BUILD_TOO_MANY_TAG_DATABASES" "tag databases for tagmap" "[249]"
:handled "_X_COORDINATES_OUT_OF_ORDER" "X co-ordinates out of order for F(x)" "X coordinates out of order for F(x)" "[033]"
:handled "-CHECK_DISCONTINUOUS_FUNCTION" "F(x) discontinuity (step)" "X value of 400000" "X value of 100000" "X value of 3999898" "X value of 922323" "X value of 4190208" "[031]"
:handled "-COSMETIC_MISSING_PNT_TAG" "referenced in PNT database has no LPMB info" "has no description" "[250],[251]"
:handled "-BUILD_BATCH_NO_INCLUDE_FILE" "Could not locate batch include file" "[252]"
:handled "-BUILD_ERRORS_LIMITED" "Error count for Error" "System maximum error count exceeded" "[60000],[60001]"
:handled "-COSMETIC_UNWIRED_FLAT_FUNCTION" "graph is flat but unwired" "[036]"
:handled "-INFO_FLAT_FUNCTION" "graph is flat" "[035]"
:handled "_ENHANCED_TREND" "Enhanced Trend: "  "[024],[025]"
:handled "-CHECK_INCLUDED_FILE-PARTIAL" "Included image " "[294]"
:handled "-CHECK_FORCED_OUTPUT" " output forced to " "[279],[280],[281],[282],[283]"
:handled "_TRIP_ON_FAULT" "Trip on fault: " " (FC 132) has S3 zero " "[147],[148]"
:handled "-CHECK_AIS_NON-FUNCTIONAL_STATUS" "(FC 132) is wired but non-functional" "[174]"
:handled "-INFO_OVERRIDE_ON_OUTPUT" "Override on output: "  "[150],[151],[152]"
:handled "-INTERNAL_UNKNOWN_TAG_TYPE" " has unknown tag type " "Unknown tag type "  "[259]"
:handled "-INTERNAL_ERROR_DATABASE" "Cannot import Error Database" "[289]"
:handled "-CHECK_EMPTY_REFERENCE" "put reference descriptor empty" "[015]"
:handled "-CHECK_BLOCK_WITH_ZERO_GAIN" "means that Block " "means that constant " "[262]"
:handled "-INTERNAL_COMPOSER_WIRING-PARTIAL" "Wired in drawing only:" "Wired in Composer only:" "[170],[171]"
:handled "_FUNCTION_DISABLED" "disabled by spec values" "disabled by S"  "[297], [298]"
:handled "-INTERNAL_SPLUS-PGP-PARTIAL" "Tokenization " "tokenization " "Possible dynamic definition" "no link target" "Type Code " "Associated dynamics file" "Associated variable file" "Dynamic import" "not found by name, searching by index" "[269], [270], [271], [273], [274], [275], [276], [277], [278], [285], [286], [287], [293]"
:handled "-INFO_QOR_USED_AS_NOR" "QOR being used as a NOR:"  "[134]"
:handled "_LARGE_SPECS_USED" "uses large spec values:" "[034]"
:handled "-INFO_QOR_OUTPUT_FORCED" " wired, 0 required" "QOR output forced to" "[135]"
:handled "-IGNORE_UNWIRED_QOR" "Insufficient number of inputs (0 wired, " " required) in unused FC 36 Module " "[133]"
:handled "_TOO_FEW_INPUTS" "Insufficient number of inputs " "[133]"
:handled "_ALARMVECTOR" "AlarmVector tag "  "[138],[139],[140]"
:handled "_HISTORY_TAG" "History tag " "Trend tag "  "[161],[162],[163],[253]"
:handled "-COSMETIC_EMPTY_TREND" "referenced, but no tags configured in any database" "[254]"
:handled "_IMPORT_STATION_PV_NOT_OUTPUT" "imports station PV " "[255]"
:handled "_TAG_NOT_EXCEPTION_REPORTED" "Tag used in graphic but not exception-reported" "[141]" "Tagged but not exception-reported" "[256]"
:handled "-CHECK_UNUSED_TREND_BLOCK" "not used on any graphics or archived" "[257]"
:handled "-COSMETIC_CONSTANT_TREND_TAG" "FC 66 is wired from constant block " "FC 179 is wired from constant block " "[258]"
:handled "_UNDEFINED_TREND_INDEX" "does not reference a trend in any associated trend database" "[142],[143]"
:handled "_RENAMED_BLOCK" "renames Module" "[144]"
:handled "-INFO_SEGMENT_CONTROL_BLOCKS" "auto-sequencing enabled" "[302]"
:handled "_ILLEGAL_SPEC_VALUE" "Illegal spec value " "out of the valid range" "Segment Control Block Module " "does not test base block" "[146],[149],[299],[300],[301],[303],[304],[305],[310]"
:handled "_CONTINUOUS_EXCEPTION_REPORTS" "Continuous exception reports generated" "[145]"
:handled "_COMPOSER_SPECS" "Floating-point value" "Integer value" "[10026]"
;
:filter "-INTERNAL_SQLITE_MESSAGE" "SQLite prepare " "SQLite execute " "[NOT]"
| 
|                     DBDOC-INTERNAL_SQLITE_MESSAGE.ERR
| 
| Examples:
|
| SQLite prepare error: out of memory
| SQLite execute error: PRIMARY KEY must be unique at wiring_quality.cpp line 418
| 
| Explanation:
| 
| Our programs use SQLite in internal processing.  These messages
| are indications that our compiler encountered data that violated 
| our programming assumptions.
| 
| We might need to ask for files that cause these messages for analysis.
|________________________________________
:filter "-IGNORE_SCALEMODE" "Drawing line with scalemode " "[NOT]" "**case 10296 **"
| 
|                     DBDOC-IGNORE_SCALEMODE.ERR
| 
| Example:
|
| Drawing line with scalemode 0, scale factor 15.00, raw coords (747,952)-(461,952)
| 
| Explanation:
| 
| These messages are indications that our compiler encountered data that violated 
| our programming assumptions.
| 
| We might need to ask for files that cause these messages for analysis.
| 
|________________________________________
:filter "-CHECK_CFG_FILE_TIMESTAMPS" ".CFG Sun " ".CFG Mon " ".CFG Tue " ".CFG Wed " ".CFG Thu " ".CFG Fri " ".CFG Sat " ".CFG (not found)" "[NOT]"
| 
|                     DBDOC-CHECK_CFG_FILE_TIMESTAMPS.ERR
| 
| Examples:
|
|   1  10  2  EBY3866.CFG Mon Oct 09 17:34:28 2000
|  15  77  4  EBY5910.CFG (not found)
|
| Explanation:
| 
| This shows that Loop PCU Module and compile date and time for each
| CFG file known to be in use by Composer.  We have noticed that unused
| .CFG files can often be found in the Composer project for reasons
| people will have to tell us about.
|________________________________________
:filter "-CHECK_GRAPHICAL_EXPRESSION" "Unable to handle all tags in expression" "[NOT]"
| 
|               DBDOC-CHECK_GRAPHICAL_EXPRESSION.ERR
|
| Examples:
|
| Unable to handle all tags in expression
|
| Explanation:
|
| The graphical expresion only has a link generated for the first tag in the
| expression.  If there are other tags, there is no link in DBDOC.
|________________________________________
:filter "-BUILD_OBSOLETE_LINK" "superseded by copy from database" [NOT]
| 
|               DBDOC-BUILD_OBSOLETE_LINK.ERR
|
| Example:
|
| File NSTAT051.DIS superseded by copy from database -- skipping
|
| Explanation:
|
| In a Composer project supporting Conductor VMS graphics, 
| the global form of the graphic is used instead of a local 
| version of the file.
|________________________________________
| 
|                         DBDOC-BUILD_SKIPPING.ERR
|________________________________________ 
:filter "-INTERNAL_800XA_PROCESSING" "Following type 2 " "Found an xml file at" "More than one .lcd file" "More than one .bin" "Exception at offset" "called on non GUID" "Unknown index type" "Aspect is" "Discrepancy: aspect: " "[NOT]"
| 
|                     DBDOC-INTERNAL_800XA_PROCESSING.ERR
| 
| Examples   
|
| Following type 2 at offset 0x14925F27
| Found an xml file at offset 0x00270087.
| More than one .lcd file in object!
| More than one .bin file in object!
| Non-local exit: Exception at offset 0x7296DFB7.
| read_guid() called on non GUID quantity at offset 0x00003B8C.
| Unknown index type on line 2259:
| Discrepancy: aspect: ..., tooltip: ..., using aspect
| Aspect is NULL, tooltiptext is NULL
|
| Explanation:
| 
| This message means the 800xA file could not be handled for the reason given.
| Some problems may be resolved in the future.
|________________________________________
:filter "-INTERNAL_SKIPPING" " record on line " "Skipping" "Can't find file" "Blank " "also case11014" "does not exist - skipping" "[NOT]"
| 
|                         DBDOC-INTERNAL_SKIPPING.ERR
| 
| Examples:
|
| Blank MTEXT record on line nnnn -- skipping
| Skipping database TRUSAGE.DBF
| Can't find file .tif: O/S Error 87
| Skipping structured file
| File ... does not exist - skipping
|
| Explanation:
| 
| This message means we cannot handle a file.  Please look at it with
| the real tools and determine if it seems legitimate.  If so, send it
| to us.  There are still surprises out there.
|________________________________________
:filter "_ADAPT_EXECUTE_ERROR" "Adapt block reference does not exist" "Failed to find target block for adapt block" "[NOT]"
| 
|                         DBDOC_ADAPT_EXECUTE_ERROR.ERR
|
| Examples:
| 
| Adapt block reference does not exist
| Failed to find target block for adapt block
|
| Explanation:
| 
| We check that parameters are legal targets for adapt blocks and tell
| you if illegal ones are used.  We check that adapt blocks are targetting 
| adaptable specifications and tell you if ones that are documented as 
| not being adaptable are used.
| 
| If you compile these blocks, you will get no errors.  However, when you
| download and change mode to Execute, the module will go into Error mode
| (flashing Green status LED) showing one of these error indications:
|
| LED 1+3 ON. Module Status Report: Config Error - Undefined Block, or
| LED 2+3 ON. Module Status Report: Config Error - Input Data Type Incorrect,
| with xx = Block # Making Reference (xx = Block Number of the Adapt).
|
| Solution: 
| Change mode to Configure and correct the error, compile and download again.
| Of course, take care of all errors of this class first.
|________________________________________
:filter "_ADAPT_BLOCKS" "Unwired adapt block" "[NOT]"
| 
|                         DBDOC_ADAPT_BLOCKS.ERR
| 
| Examples:
|
| Unwired adapt block ... Block nnnn adapts Block mmmm
| 
| Explanation:
| 
| Adapt block problems reported here include places where two adapt blocks 
| adapt the same specification, and other adapt block issues.
| 
| Whenever a specification is adapted by more than one block, you should
| verify that is the intent.
| 
| Testing by a client confirmed that an adapt block continues to adapt its
| target block / spec, even if it has no input.  Since block types cannot
| be changed, the unintentionally adapted spec is legal, but not likely correct.
| 
| The "type mismatch" messages often accompany other errors, so the same block can
| have multiple errors.  Also, adapt blocks are very flexible, so mismatches "work".
| However, these messages may be the only indication of an otherwise impossible to
| detect error.
|________________________________________
:filter "-BUILD_FONT_PROBLEM" "Need to locate font:" "ttfFileNameByDescriptor failed" "getPreferableFont" "[NOT]"
| 
|                      DBDOC-BUILD_FONT_PROBLEM.ERR
|
| Examples:
|
| Need to locate font: <romans.ttf>
| ttfFileNameByDescriptor failed for: <romans>
| getPreferableFont: unknown type 4
|
| Explanation:
|
| These messages relate to Microstation fonts that may be missing from the build.
|____________________________________
:filter "-CHECK_VERY_LARGE_HOTSPOT" "Very large hotspot" "WILL NOT BE CONVERTED Case10296" "[NOT]"
| 
|                    DBDOC-CHECK_VERY_LARGE_HOTSPOT.ERR
| 
| Example:
|
| Very large hotspot 'VB.IMAGE Unconfigured submodel reference' bounds {0,0,241,181} drawing bounds {0,0,241,181}
| Very large hotspot 'LI8062 Module 1,08,03 Block 28920 CENTRATE WET    WELL LEVEL Centrate Wet Well
|    trend:886' bounds {100,791,9900,7409} drawing bounds {0,0,10000,7500}
|
| Explanation:
| 
| This message means that a section of a graphic seems to take up most of the graphic.
| In the case of a submodel, it often simply means we built a submodel erroneously as
| if it were a graphic.  In the case of a graphic, it can mean that DBDOC does not yet
| understand some part of 800xA yet.
|________________________________________
:filter "-IGNORE_INVALID_TREND" "trend:" "[NOT]"
| 
|                     DBDOC-IGNORE_INVALID_TREND.ERR
| 
| Example:
|
| Vector to invalid gms graphic: 'trend:'
| 
| Explanation:
| 
| 
| This type of command in Conductor NT is being worked on.  We plan eventually 
| to link the trend graphics to DBDOC documents.
|________________________________________
:filter "-CHECK_MISSING_DISPLAYS" "DT display file " "Vector to invalid " "[NOT]"
| 
|                      DBDOC-CHECK_MISSING_DISPLAYS.ERR
| 
| Examples:
|
| DT display file xxxxxxx not found (not configured)
| Vector to invalid gms graphic: 'graphic:'
|
| Explanation:
| 
| A link on the graphic has been specified on a display that was not found 
| in GRAPHCFG.XDC.  Either the file itself was not included in the DBDOC 
| build or the graphic has not been updated.
| 
| The graphic calls for another graphic xxxxxxx, which was not found.  This
| is not really an error, but is a weakness for the operators using the 
| graphic system.
| 
| The usual sources of this error are:
|    1. Failure to build all graphics in the DBDOC document.  If the graphic
|       is not built, the DBDOC process will not find it.  This is normally the 
|       case when there are a lot of messages in this file.
|    2. Graphics becoming obsolete and being eliminated, without correction
|       of other graphics that call for the obsolete graphic.
|    3. Graphics being planned and anticipated that have not yet been built
|       or installed.
|    4. Errors in pop-ups.
|________________________________________
:filter "-CHECK_800XA_SUBMODEL" "No tag/graphic found with the name" "No tag found in string" "WILL NOT BE CONVERTED Case10296" "[NOT]"
| 
|                      DBDOC-CHECK_800XA_SUBMODEL.ERR
| 
|
| Examples
|
| No tag/graphic found with the name Operator Help (execute_ppa_submodel)
| No tag/graphic found with the name FC (execute_ppa_submodel)
| No tag/graphic found with the name 31-HIC -4346 (execute_ppa_submodel)
| No tag found in string 8LTLS125 (ppa_dynamic_bar)
| 
| Explanation:
| 
| The graphic calls for another graphic, entity or tag that was not found or
| that the DBDOC support has not yet been implemented for.  We use this
| to help us find new and wonderful methods invented by 800xA specialists to
| to the jobs they have undertaken.
|____________________________________
:filter "-INTERNAL_INVALID_CAD_FILE" "Invalid spec" "(Unknown) Layer" "case10668/11014#10" "[NOT]"
| 
|                   DBDOC-INTERNAL_INVALID_CAD_FILE.ERR
| 
| Examples:
|
| Invalid spec length
| + 25 Type 0 (Unknown) Layer 12
|
| Explanation:
| 
| [002]
| This message means that a CLD/CAD file was found that we cannot process due 
| to a bad magic number value.
|
| Please try to open the file with your Composer or CAD system. If the file
| seems to be fine, please send it to us for analysis. 
|
| This error can be a symptom of a failure in the blue DBDOC dongle, or in
| its USB port. Simply moving the dongle to another port might make the error
| disappear, signalling a USB port failure. If another dongle is available,
| substitute it and try again. If that works, the dongle has failed and will
| be replaced free of charge. You can ask GMCL for a replacement dongle at
| any time at no charge (except for courier cost, if you want it quickly).
| 
| [003][009]
| This message means that a CLD/CAD file was found that we cannot process. 
| Please try to open the file with your Composer or CAD system. If the file
| seems to be fine, please send it to us for analysis.
| 
| [010]
| This message means that a CLD/CAD file was found that we cannot process 
| because the CLD/CAD file is too short.
| Please try to open the file with your Composer or CAD system. If the file
| seems to be fine, please send it to us for analysis.
|________________________________________
:filter "-COSMETIC_NO_WIRED_INPUT" "does not have a wired input" "has no wired input" "FC 1 does not have an input" "[NOT]"
| 
|                       DBDOC-COSMETIC_NO_WIRED_INPUT.ERR
| 
| Example:
|                            
| Module 1,17,31 Block 25997 FC 66 does not have a wired input
| Module 22,10,31 Block 22203 FC 1 does not have an input
| Module 1,01,31 Block 22783 FC 1 has no wired input, static input from block 0 (should be 5)
| Module 6,18,31 Block 21793 FC 179 does not have a wired input
|
| Explanation:
| 
| This message means that a block has been found that has no input attached 
| to it. You normally can ignore these messages as a cosmetic issue.
| 
| We have seen that this condition can be caused in WinCAD and DOS CADEWS 
| by connecting a source to a F(x) block, then deleting the line. The result 
| is that S1 has a value 0. Composer restores the value to 5.
| 
| With some older firmware revisions, it is possible that the configuration 
| will compile cleanly, but will not run when it is loaded into the module. 
|_______________________________________
:filter "-INFO_MULTIPLE_MACROS" "internal name not found" "[NOT], [case 11328]"
| 
|                         DBDOC-INFO_MULTIPLE_MACROS.ERR
| 
| Examples:
|
| Non-External User macro: file sym\SYM00357.mcr, internal name not found in database
| 
| Explanation:
| 
| This message is designed to guide the development of DBDOC in understanding
| duplicated macros and shapes.  If you look at the messages for your system
| and can explain how they got there, what they mean and/or if they show you
| something you would like to change, please let us know about it.
|
|____________________________________
:filter "-IGNORE_UNCONNECTED_WIRE" "(FC 29) does not connect to anything at " "(FC 44) does not connect to anything at " "WILL NOT BE CONVERTED Case10296" "[NOT]"
| 
|                         DBDOC-IGNORE_UNCONNECTED_WIRE.ERR
| 
| Examples:
|
| Live wire from Block 22211 (FC 29) does not connect to anything at 2660,2140
| Live wire from Block 22231 (FC 44) does not connect to anything at 2660,2140
| 
| Explanation:
| 
| This message simply says that the output of an analog output block is shown
| as being directed to a diagram in the external termination scheme.  The only
| actual use of the output is for Test Quality, but this use is harmless.
|________________________________________
:filter "-BUILD_MISSING_SYMBOL" "Missing submodel {" "[NOT]"
| 
|                    DBDOC-BUILD_MISSING_SYMBOL.ERR
| 
| Examples:
|
| Missing submodel {696627A6-5D4B-42A0-B473-9B6C7EBA2AB8}.ctl - not extracted in INFI90Harmon583DA1C9C23D4A.StationRead_
|
| Explanation:
| 
| This message means that a call was found for a symbol or sub-model DBDOC 
| did not find when the graphic was being compiled. Our DBDOC picture of 
| the graphic may not be valid if you have missing symbols or submodels.
| 
| The usual sources of this error are:
| 
|    1. Failure to include all symbols used in the DBDOC paths
|    2. The symbol may be obsolete, but the graphics using it are unchanged
|    3. The symbol may have been lost or not shipped by a supplier 
| 
| We suggest you find these missing symbols and then rerun the wizard to 
| include the symbols into the system. 
|________________________________________
:filter "-INTERNAL_GRAPHIC_PRIMITIVE" "Unsupported PPA primitive" "Unsupported 800xA primitive" "Case11014#9" "[NOT]"
| 
|                    DBDOC-INTERNAL_GRAPHIC_PRIMITIVE.ERR
| 
| Example:
|
| Unsupported 800xA primitive ADVBPOPRIMITIVESLibCtl.AdvantPie used 78 times
|
| Explanation:
| 
| This message means that a call was found for a graphic primitive that DBDOC
| does not yet support.
|________________________________________
:filter "-INTERNAL_MISSING_800xA_COLOR" "Missing PPA color" "Missing 800xA color" "Case11014#11" "[NOT]"
| 
|                    DBDOC-INTERNAL_MISSING_800xA_COLOR.ERR
| 
| Examples:
|
| Missing 800xA color GSLBADQFC used 18 times
|
| Explanation:
| 
| This message means that a call was found for a color in an 800xA graphic that DBDOC
| did not resolve.
|________________________________________
:filter "-INTERNAL_UNRESOLVED_REFERENCE" "Unable to resolve reference to" "[NOT]"
| 
|                    DBDOC-INTERNAL_UNRESOLVED_REFERENCE.ERR
| 
| Examples:
|
| Unable to resolve reference to INFI90Harmon9982C1A810D74B.DIGITAL_READ: multiple submodels with this ProgID exist
|
| Explanation:
| 
| This message means that a reference could not be resolved. 
| 
| Contact us for assistance resolving this message. 
|________________________________________
:filter "-CHECK_800xA_DYNAMIC_BAR" "in PPA dynamic bar in "  "NOT CONVERTED CASE 10296" "[NOT]"
| 
|                    DBDOC-CHECK_800xA_DYNAMIC_BAR.ERR
| 
| Example:
|
| Reference to undefined tag 8LTED201 in PPA dynamic bar in INFI90Harmon4863DF81CF8B40.AnalogRead_D
|
| Explanation:
| 
| This message means that a dynamic bar could not be given a range because the tag was not found.
|
|________________________________________
:filter "_TAG_MISMATCH" "Duplicate tag name" "[NOT]"
| 
|                    DBDOC_TAG_MISMATCH.ERR
|
| Examples:
|
| Duplicate tag name xxxxxxx: Module ...
| 
| Explanation:
| 
| This message means that during the scanning of the various databases 
| a duplicate tagname was found. DBDOC depends on a unique tagname 
| corresponding to a unique block number in a module.
| 
| Often, you will find that Composer or WinCAD actually have the correct 
| definition of the tag. The reason for this is that they automatically 
| generate a tag definition when an exception report block is created. 
| In the console, on the other hand, the correct parameters have to 
| entered manually. 
|________________________________________
:filter "-CHECK_DUPLICATE_LABEL" " refers to both Module "  "NOT CONVERTED YET CASE 11014#23" "[NOT]"
| 
|                    DBDOC-CHECK_DUPLICATE_LABEL.ERR
|
| Example:
|
| Label heater1-1 refers to both Module 2,170,31 Block 23200 and Module 2,170,31 Block 23000
| 
| Explanation:
| 
| This message means that during the scanning of a .AB file, the label 
| assigned to the block was found to duplicate one that was already used
| in that module.  You can ignore this, but unique labels strengthen your 
| system documentation.
|________________________________________
:filter "_AMBIGUOUS_POINT_NAMES" "Ambiguous point name" "NOT CONVERTED CASE 10296" "[NOT]"
| 
|                    DBDOC_AMBIGUOUS_POINT_NAMES.ERR
|
| Examples:
|
| Ambiguous point name: tag RPVOLTS_RMSC describes both
|  Module 1,03,31 Block 22115 and Module 1,03,31 Block 22116
| 
| Explanation:
| 
| This message means that during the scanning of the various databases, a
| point in a Wonderware database was found that was defined which was
| inconsistent in the block number that it defined.  DBDOC depends on a 
| unique tag identifier corresponding to a unique block number in a module.
|________________________________________
:filter "_MULTIPLE_TAG_NAMES" "Multiple tag names for " "NOT CONVERTED CASE 10296" "[NOT]"
| 
|                    DBDOC_MULTIPLE_TAG_NAMES.ERR
|
| Example:
|
| Multiple tag names for Module 1,11,31 B 24684: 251A322 and 641A322
| 
| Explanation:
| 
| This message means that during the scanning of the various databases, a
| block was found that was defined with different tagnames in two 
| databases as indicated.  This includes Wonderware tag processing.
| DBDOC depends on a unique tagname corresponding to a unique block number
| in a module.
|________________________________________
:filter "-COSMETIC_MULTIPLE_WIRES" "Multiple wires at a live wire end:" "CASE 11014#21" "[NOT]"
| 
|                    DBDOC-COSMETIC_MULTIPLE_WIRES.ERR
| 
| Examples:
|
| Multiple wires at a live wire end: assuming connector at 1500,2100
| 
| Explanation:
| 
| These messages may be cosmetic.  We would welcome feedback on what 
| you find this message to really mean.  We will discard a message if
| it proves to be specious.
| 
| There are often a few places worth checking with WinCAD. They 
| represent unusual wiring, but we cannot tell if they show a problem. 
| We would welcome feedback on what you find this message to really mean. 
|________________________________________
:filter "_LPM_REFERENCE_PROBLEM" "No legal LPM match found " "[NOT] case 11446"
| 
|                         DBDOC_LPM_REFERENCE_PROBLEM.ERR
| 
| Examples:
|
| No legal LPM match found for IREF X09TT0527 on output 2
| 
| Explanation:
| 
| These messages cover situations where IREF text exists on an off-module
| input, but the reference text is already used as a local OREF reference.
| 
| This can arise in a conversion from WinCAD, for example, when the text
| on an AI/I reference is the same as that on the OREF that distributes
| its value through the module.  In WinCAD, the text on the import function
| code was not looked at, but in Composer it is.
|________________________________________
:filter "-INFO_OVERRIDE" "override on input" "[NOT]"
| 
|                         DBDOC-INFO_OVERRIDE.ERR
| 
| Examples:
|
| Warning, override on input bFLMDTCT, Module 2,07,10 Block 24125
|
| Explanation:
| 
| In a ladder system, this message shows that the configuration loads the
| variable shown as being in override.  This may not be a problem, but gives
| you a simple checklist.
|
| In a CAD or Composer system, this message is generated by our rung
| block processing.  You will want to verify that the logic makes sense.
|________________________________________
:filter "-CHECK_POSSIBLY_CORRUPT" "possibly corrupt file" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                      DBDOC-CHECK_POSSIBLY_CORRUPT.ERR
| 
| Example:
|
| Skipping possibly corrupt file WDA23.DWG
| 
| Explanation:
| 
| This message means that an AutoCAD or MicroStation file appears to
| be corrupt, so it is skipped.  We have found that processing these
| files generally gives an unsatisfactory result, functionally, or
| causes a failure in our programs.
| 
| A client has found that opening the files in AutoCAD, zooming the drawing 
| to its "extents" and saving the file fixes the problem.
|____________________________________
:filter "-INTERNAL_NON-LOCAL_EXIT"  "Non-local exit:" "Non-local exit " "[NOT]"
| 
|                      DBDOC-INTERNAL_NON-LOCAL_EXIT.ERR
| 
| Examples:
|
| Non-local exit: Unknown file version 0x3938 at offset 0x00000100
| Non-local exit from file D:\U1TOPBAR.m1
|
| Explanation:
| 
| This message means that a file contains information we cannot 
| handle.  Please send us an example or two with this error.
|____________________________________
:filter "-IGNORE_PRIMARY_DISPLAY" "primary display" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                      DBDOC-IGNORE_PRIMARY_DISPLAY.ERR
| 
| Examples:
|
| Tag P10021002 not used on primary display
|
| Explanation:
| 
| These messages can be ignored.  There are numerous valid reasons
| for tags not to be on the graphics they identify as their 'primary
| display', so the message is not useful and is being eliminated.
|____________________________________
:filter "-CHECK_ALARM_VECTOR" "has alarm vector" "NOT YET CONVERTED CASE 11014#22 AND 10296" "[NOT]"
| 
|                      DBDOC-CHECK_ALARM_VECTOR.ERR
| 
| Examples:
|
| Tag SP1-CONT-PWR has alarm vector to graphic
|  BW_DY_DRAWOFF_OVERVIEW.M1 (number 120) but is not used on it
| Graphic:800 not defined in GraphicAssignments but has alarm vectored tag(s)
|
| Explanation:
| 
| These messages suggest inconsistencies in your Conductor NT
| AlarmVector data.  A tag is not on the graphic that is supposed
| to be called up when it goes into alarm. 
|____________________________________
:filter "-IGNORE_MULTIPLE_DYNAMIC_BARS" "Multiple dynamic bars defined in record" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                      DBDOC-IGNORE_MULTIPLE_DYNAMIC_BARS.ERR
| 
| Example:
|
| Multiple dynamic bars defined in record - ignoring all but first in EBb_DBAR02V
| 
| Explanation:
| 
| This is a diagnostic message for us to understand one our our features. We will ask
| you for more information, copies of models and submodels and so on if we find a problem.
|________________________________________
:filter "-IGNORE_LINK_TO_TAG" "Link to tag "  "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                     DBDOC-IGNORE_LINK_TO_TAG.ERR
| 
| Example:
|
| Link to tag 1HJF01 CP011 in trend U1-AuxFiring-HeaderPressure
| 
| Explanation:
| 
| This is a diagnostic message for us to understand one our our features. We will ask
| you for more information, copies of models and submodels and so on if we find a problem.
|________________________________________
:filter "_RUNG_BLOCK" "too few operands" "[NOT]"
| 
|                        DBDOC_RUNG_BLOCK.ERR
| 
| Examples:
|
| Rung block Module 1,02,02 Block 21478 S5 value 001 has too few operands
|
| Explanation:
| 
| Rung blocks can have parameters that appear incorrect.  Wired inputs may have 
| controlling parameter values of 0, so they are unused.  Unwired inputs may have 
| non-zero parameter values, as if they were to be used.  The logic implied by the 
| specifications may appear to be in error.
|________________________________________
:filter "_TAG_INDEX" "DT tag index " "[NOT]"
| 
|                      DBDOC_TAG_INDEX.ERR
| 
| Examples:
|
| DT tag index nnnn not found
| 
| Explanation:
| 
| This is a message that should always be investigated. It means that 
| graphics are being controlled by tag index with blank tagnames 
| (except in OIS 20 and MCS systems). This is dangerous because 
| maintaining a correct set of tag index values proves difficult over 
| the long run.
| 
| In most SODG systems, any tag index message means that the tagname 
| is blank. You should consider this to be worth a lot of attention, as 
| it means that you can lose the connection to the intended tag easily.
| 
| The value of this message for pop-ups is substantial, as it is the 
| easiest way to find out that pop-ups that have been keyed by index 
| refer to tags that no longer exist. 
|________________________________________
:filter "-IGNORE_BLANK_TAG_IN_GRAPHIC" "used with blank tag - defining BLANK_TAG" "Defining blank undefined tag" "WILL NOT BE CONVERTED" "Variable definition: blank variable name" "Variable definition: NULL value" "[NOT]"
| 
|                     DBDOC-IGNORE_BLANK_TAG_IN_GRAPHIC.ERR
|
| Example:
|
| Tagatom PV/SIG used with blank tag - defining BLANK_TAG_069 in EBbUI_VLVC01U
| Variable definition: blank variable name
| Variable definition: NULL value for variable 133IX284#dPV/SIG in CU_value_RT
|                
| Explanation:
| 
| This message means that DBDOC means that a reference was found to a blank tag
| in a Process Portal B graphic.  The tags is defined so that you can track it
| down reasonably easily.
|
:filter "-CHECK_INVALID_RECORD_LENGTH" "ecord length" "NOT YET CONVERTED CASE11014#24" "[NOT]"
| 
|            DBDOC-CHECK_INVALID_RECORD_LENGTH.ERR
|
| Examples:
|
| Embedded record length 4552 too long: truncating at 30
| Record length 1163149644 out of range at offset 0x0000AAF4
|
| Explanation
|
| The record length appears too long. We have been unable to handle it. Please 
| check this file with the appropriate graphic tools and send the file to
| us if it appears to be valid.
|__________________________________________
:filter "-CHECK_CLD_PARSING_PROBLEM" " block out of range" "NOT YET CONVERTED CASE10296" "[NOT]"
| 
|            DBDOC-CHECK_CLD_PARSING_PROBLEM.ERR
|
| Examples:
|
| Small block map element 0 references block 5177411: small block out of range
| Large block map element 128 references block 245107590 (0x0E9C0B86): large block out of range
|
| Explanation
|
| The record pointers appears wrong. We have been unable to handle the CLD file.
| Please check this file with Composer and send the file to us if it appears to be valid.
|__________________________________________
:filter "-CHECK_LINKED_GLOBAL_GRAPHIC" "Linked global graphic" "[295]"
| 
|            DBDOC-CHECK_LINKED_GLOBAL_GRAPHIC.ERR
|
| Examples:
|
| Linked global graphic ...DIS not found
|
| Explanation
|
| It may be necessary to rebuild, including GLOBAL graphics in the Wizard.
|__________________________________________________________________________________
:filter "-INTERNAL_UNHANDLED_ENTITY" "Unhandled embedded "  "Unhandled following type " "Hotspot limit exceeded: " "[NOT]"
| 
|                    DBDOC-INTERNAL_UNHANDLED_ENTITY.ERR
|
| Unhandled embedded record type 92
| Unhandled following type 65536 at offset 0x07EC3471.
| Hotspot limit exceeded: Some hotspots will not be generated
| 
| Explanation:
| 
| A record has been found in a file that we do not know how to handle. 
| This usually occurs when an obscure and rarely used function is encountered, 
| or when a new version of the graphics system introduces new functionality.
| Exceeding a hotspot limit indicates the graphic contains more than 5000 hotspots, and some will not be generated.
| Send us the file and any related documentation you can find.
|____________________________________
:filter "-IGNORE_COMPACTING_RTF_TITLE" "Compacting rtf_title from " "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                    DBDOC-IGNORE_COMPACTING_RTF_TITLE.ERR
| 
| Example:
|
| Compacting rtf_title from <PROJECT MODELS SUBMODELS\\SUBMODELS Process
|   Portal B (Operate IT) M1 SubModels -- RFLA_LOUVER_ACTUATOR_STDCUR
|   Conductor Graphic> to <PROJECT MODELS SUBMOD...\SUBMODELS Process Portal B
|  (Operate IT) M1 SubModels -- RFLA_LOUVER_ACTUATOR_STDCUR Conductor Graphic>
| 
| Explanation:
| 
| The titles created by DBDOC can get too long, so we compress them if needed.
| We use this message to see if we are handling this well.
|____________________________________
:filter "-IGNORE_UNIMPLEMENTED" "Unimplemented "  "NOT YET CONVERTED CASE10296" "[NOT]"
| 
|                    DBDOC-IGNORE_UNIMPLEMENTED.ERR
| 
| Example:
|
| Unimplemented record type STRUCTEXPR
| 
| Explanation:
| 
| This type of command in GRAPHX is being worked on.  Any help in
| resolving it would be appreciated.
|________________________________________
:filter "-INTERNAL_STRANGE_ARGUMENTS" "strange second argument" "[NOT]"
| 
|                    DBDOC-INTERNAL_STRANGE_ARGUMENTS.ERR
| 
| Examples:
|
| doVector called with strange second argument (dump follows)
| 
| Explanation:
| 
| The file contains submodels that we do not understand enough.
| You are welcome to send us information to help us add the support needed.
|________________________________________
:filter "-CHECK_CIRCULAR_SUBMODEL_INCLUSION" "Circular submodel inclusion" "[NOT]"
| 
|                         DBDOC-CHECK_CIRCULAR_SUBMODEL_INCLUSION.ERR
|
| Example:
|
| Circular submodel inclusion in MS_DY_MOTOR_3D
|
| Explanation:
|
| A submodel includes itself.  We have seen this in submodels 
| that we build for documentation even if they are not being used. 
| Please let us know more about these submodels that include 
| these submodels that include these submodels that include 
| these submodels that include these submodels that...
|________________________________________
:filter "-CHECK_FILE_INCLUSION" " inclusion of file "  "NOT YET CONVERTED CASE11014#1 CASE8680" "[NOT]"
| 
|                         DBDOC-CHECK_FILE_INCLUSION.ERR
|
| Examples:
|
| XREF: inclusion of file FP_DYvalue cannot be uniquely resolved
| XREF: inclusion of file YW_CheckValve_01 cannot be uniquely resolved
|
| Explanation:
|
| The DBDOC build is unable to include a file because there are
| multiple copies.  Please let us know more about these errors.
|________________________________________
:filter "-CHECK_UNEXPECTED_END_OF_LINE" "Unexpected end of line" "NOT YET CONVERTED CASE11014#26" "[NOT]"
| 
|           DBDOC-CHECK_UNEXPECTED_END_OF_LINE.ERR
|
| Example
|
| Unexpected end of line on line 35
|
| Explanation
|
| There is an unexpected end of line character in the file mentioned.
| Please check the file with the appropriate graphic tools and send 
| the file to us if it appears to be valid.
|________________________________________
:filter "-CHECK_UNEXPECTED_END_OF_BLOCK" "Unexpected end of block" "NOT YET CONVERTED CASE11014#30" "[NOT]"
| 
|           DBDOC-CHECK_UNEXPECTED_END_OF_BLOCK.ERR
|
| Example
|
| Unexpected end of block statement on line 870
|
| Explanation
|
| A block statement in a B90 file ended unexpectedly.  Please check the B90 
| file with the appropriate tools and send the file to us if it appears to
| be valid.
|________________________________________
:filter "-CHECK_UNKNOWN_WONDERWARE_VERSION" "Bad magic number" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|           DBDOC-CHECK_UNKNOWN_WONDERWARE_VERSION.ERR
|
| Example:
|
| Bad magic number
|
| Explanation
|
| This message arises when an unknown version of WonderWare is used.  Please
| communicate with us so we can resolve the error.
|_________________________________________
:filter "-CHECK_BINARY_LINKS" "binary_links" "NOT YET CONVERTED CASE10296"
| 
|           DBDOC-CHECK_BINARY_LINKS.ERR
|
| Example:
|
| binary_links command on line 5 is obsolete
|
| Explanation
|
| This message is the result of old versions of Wizard.  To resolve this  
| message please run your build again from the Wizard stage to update the
| *.raw files.
|__________________________________________
:filter "-IGNORE_ERROR_COMPRESSING_FILE" "Error compressing "  "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|                     DBDOC-IGNORE_ERROR_COMPRESSING_FILE.ERR
| 
| Examples   
|
| Error compressing rtf\hv_external_blocks.txt in thread (will retry):
|  Unable to open file rtf\hv_external_blocks.txt for compression: No such file or directory
|
| Explanation:
| 
| Sometimes, files are locked in processing threads.  We indicate this by intermittently
| issuing this error so that we can diagnose problems.  You can ignore this message.
|________________________________________
:filter "-IGNORE_FILE_OPEN_FAILURE" ": No such file or directory" "NOT YET CONVERTED CASE11014#19" "[NOT]"
| 
|                     DBDOC-IGNORE_FILE_OPEN_FAILURE.ERR
| 
| Examples   
|
| Can't open file C:\CLIENT~1\ABBAUS~1\Composer\: No such file or directory
|
| Explanation:
| 
| This message indicates that the user macros feature of Composer is not used, so a 
| table we are trying to build is empty.  It can be ignored.
|________________________________________
:filter "-BUILD_FILE_OPEN_FAILURE" "Error opening file" "input file" "Unable to open file" "open DBF file" "loading file" "open symbol table" "open application" "open format file" "open module header" "SOME NOT YET CONVERTED CASE10783, 11014#3" "[NOT]"
| 
|                     DBDOC-BUILD_FILE_OPEN_FAILURE.ERR
| 
| Examples   
|
| Error opening file: Can't determine file type
| Error opening file: Error in DXF block
| Error loading file: Error in DXF block
| Error loading file: Can't determine file type
| Failed to open input file:  HG-15A.DWG
| Failed to read input file header
| Can't open file ...\EBY6630.CLD: No such file or directory
| Failed to open DBF file, C:\DIRECTORIES\DRDIR.DBF
| Failed to open symbol table extension file
| Failed to open application file
| Failed to open format file : No such file or directory
| Failed to open module header file:
| Failed to open DBF file
| Unable to open file: No such file or directory
|
| Explanation:
| 
| This message means the file could not be opened for the reason given.
| Sometimes this message may be resolved if the project is rebuilt. If a 
| rebuild does not correct the issue, please check the file with the 
| appropriate tools and send the file to us if it appears to be valid. 
|________________________________________
:filter "-IGNORE_INVALID_FILE_HANDLE" "Invalid file handle" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|          DBDOC-IGNORE_INVALID_FILE_HANDLE.ERR
|
| Example:
|
| Invalid file handle
|
| Explanation:
|
| This message appears when DBDOC detects an invalid file handle. 
| Please check the file with the appropriate tools and send the file  
| to us if it appears to be valid.  If not, you can take care of it.
|________________________________________
:filter "-CHECK_IGNORED_FUNCTION" "Ignored function" "NOT YET CONVERTED CASE10296" "[NOT]"
| 
|            DBDOC-CHECK_IGNORED_FUNCTION.ERR
| 
| Example:
|
| Ignored function ButtonHilite( "18", "17" ) in valve_pop
| 
| Explanation:
| 
| This function is ignored by our processing.    
|___________________________________________ 
:filter "-CHECK_NO_PEN_STYLE" "No pen style available" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
| 
|            DBDOC-CHECK_NO_PEN_STYLE.ERR
| 
| Example:
|
| No pen style available - using PS_SOLID in pump_rt_std
| 
| Explanation:
| 
| There is no pen style available so we are using a default of PS_SOLID.  
|___________________________________________ 
:filter "-CHECK_DEFAULT_SPECS_USED" "uses default spec values:" "WILL NOT BE CONVERTED" "[NOT]"
| 
|            DBDOC-CHECK_DEFAULT_SPECS_USED.ERR
| 
| Example
|
| F(x) Module 1,01,31 Block 22159 uses default spec values: output for large input values may be unexpected
| 
| Explanation:
| 
| The function generator uses large spec values in the Y entries.
| These values are used and the result is often not what people
| expect.  You should check that the function is not intended to
| clamp the output, for example, as this message usually means 
| that the output approaches the input value as the inputs get larger.
| This may not be what you want.
|___________________________________________ 
:filter "-CHECK_UNEXPECTED_VALUE" " unexpectedly " "WILL NOT BE CONVERTED" "[NOT]"
| 
|                         DBDOC-CHECK_UNEXPECTED_VALUE.ERR
| 
| Example:
| 
| Unknown 2 unexpectly 132 at 0x00001A34
|
| Explanation:
| 
| This means that a value was found that was not what we expected.
| Please verify that the file works in your system and, if so, send it
| to us with any ideas you have about new features or rare ones that
| it might be using.
|________________________________________
:filter "-CHECK_UNTAGGED_TREND_BLOCK" "not referenced by any database trend tags"  "WILL NO BE CONVERTED CASE10296" "[NOT]"
|
|            DBDOC-CHECK_UNTAGGED_TREND_BLOCK.ERR
| 
| Example:
|
| Trend block Module 4,04,31 Block 21010 FC 66 is not referenced by any database trend tags
| 
| Explanation:
| 
| A trend FC has been configured in a controller.  However, it is not used on any
| graphic, nor in the Trend database, so it might be causing undue controller
| processor utilization load and could be deleted.
|___________________________________________ 
:filter "-CHECK_FUNCTION_HOTSPOT" "Failed to handle function hotspot" "Unsupported input hotspot" "NOT YET CONVERTED CASE11014#8 & #28" "[NOT]"
|
|            DBDOC-CHECK_FUNCTION_HOTSPOT.ERR
| 
| Example:
|
| Failed to handle function hotspot for function 0
| Unsupported input hotspot type 86
| 
| Explanation:
| 
| Please let us know if you get this error.  It indicates a mismatch 
| on the verson of SHAPE.LBR and the function codes in the CLD/CAD drawings. 
| It may be our problem.
|___________________________________________ 
:filter "_UNKNOWN_TAG" "Unknown tag " " references unknown tag or sub-model " "NOT YET CONVERTED CASE10296" "[NOT]"
|
|            DBDOC_UNKNOWN_TAG.ERR
| 
| Examples:
|
| Unknown tag MFP41102.C_DPV in PEP_a_MFP_SINGLE
| EbSelTag references unknown tag or sub-model RTDS1_HarmServ
| 
| Explanation:
| 
| The reported tag has a tag type that we do not yet support.
| Let us know what function code it describes.
|___________________________________________ 
:filter "-CHECK_SIMILAR_TAGS" "Tags that differ in separators only: " "Tags that might be easily confused: "  "NOT YET CONVERTED CASE11014#14 & EMAIL" "[NOT]"
|
|            DBDOC-CHECK_SIMILAR_TAGS.ERR
| 
| Examples:
|
| Tags that might be easily confused: T0-AI-7973, TO-AI-7973 [second tag is "to-ai-7973"]
| Tags that differ in separators only: 2-TI-1079-A, 2-TI-1079A
| Tags that differ in separators only: AMB_CAL_REPORT_NO_NO2 SPAN1, AMB_CAL_REPORT_NO_NO2SPAN1
| 
| Explanation:
| 
| The indicated tags have names that seem functionally identical.
| Such tags can easily be confusing.
| 
| We look both for separators and for letter / number pairs that can cause confusion.
|   Letter "O" and numeral "0" are flagged.
|   Letters "I", "l" and numeral "1" are flagged.
|___________________________________________ 
:filter "-IGNORE_MS_ACCESS_WILDCARD_CHARS" "h any)   : 0" "h number): 0" "h all)   : 0" "r class)  : 0" "(special)     : 0"  "NOT YET CONVERTED CASE11014#20" "[NOT]"
|
|            DBDOC-IGNORE_MS_ACCESS_WILDCARD_CHARACTERS.ERR
| 
| Examples:
|
| --Access Wildcard Report 
| ST:Names containing wildcard '_' (match any)   : 0
| ST:Names containing wildcard '#' (match number): 0
| ST:Names containing wildcard '*' (match all)   : 0
| ST:Names containing wildcard '%' (match all)   : 0
| ST:Names containing wildcard '[' (char class)  : 0
| ST:Names containing wildcard ']' (char class)  : 0
| ST:Names containing wildcard '$' (special)     : 0
| 
| Explanation:
| 
| The report lists wildcard characters that were not encountered.
|___________________________________________ 
:filter "-CHECK_MS_ACCESS_WILDCARD_CHARS" "h any)   :" "h number):" "h all)   :" "r class)  :" "(special)     :" "wildcards"  "NOT YET CONVERTED CASE11014#12" "[NOT]"
|
|            DBDOC-CHECK_MS_ACCESS_WILDCARD_CHARACTERS.ERR
| 
| Examples:
|
| --Access Wildcard Report
| ST:Names containing wildcard '_' (match any)   : 464
| ST:Names containing wildcard '#' (match number): 98
| ST:Names containing wildcard '*' (match all)   : 0
| ST:Names containing wildcard '%' (match all)   : 37
| ST:Names containing wildcard '[' (char class)  : 9
| ST:Names containing wildcard ']' (char class)  : 9
| ST:Names containing wildcard '$' (special)     : 101
| Document TD_OIS3B_1.DBF defines 164 names containing access wildcards
| Document TD_U3OIS43_1.DBF defines 164 names containing access wildcards
| Document 15202Y4 defines 16 names containing access wildcards
| Document 1540806 defines 16 names containing access wildcards
| 
| Explanation:
| 
| The indicated tags and references use characters that can cause Composer
| problems when using Microsoft Access manipulation of tags or references.
|
| The report lists every document that defines more than ten problematic names.
|
| Composer operations including cloning logic and modifying tags and references
| can be negatively impacted by these tags and labels. 
|___________________________________________ 
:filter "-CHECK_NON-TREND_BLOCK" "Non-trend block in trend database:" "WILL NOT BE CONVERTED CASE10296" "[NOT]"
|
|            DBDOC-CHECK_NON-TREND_BLOCK.ERR
| 
| Example:
|
| Non-trend block in trend database: ABC123 Module 1,19,23 Block 23432 FC 30
| 
| Explanation:
| 
| Trend database entries must come from either
|   FC 66  - Analog trend or 
|   FC 179 - Advanced trend.
|___________________________________________ 
:filter "-CHECK_INCLUDED_FILE" "Included file " "Image support: unable to find" "NOT YET CONVERTED CASE10296" "[NOT]"
|
|            DBDOC-CHECK_INCLUDED_FILE.ERR
| 
| Example:
|
| Included file xxxxxxxxx.dwg not found
| Included image xxx.jpg was not found
| Image support: unable to find xxx.bmp
| 
| Explanation:
| 
| DBDOC was unable to find the indicated file.
|___________________________________________ 
:filter "-INTERNAL_COMPOSER_WIRING" "Composer wiring problem:" "Reference " "NOT YET CONVERTED CASE10924 CASE11014#16" "[NOT]"
| 
|                     DBDOC-INTERNAL_COMPOSER_WIRING.ERR
| 
| Examples:
|
| Composer wiring problem: references with downstream connections never got a block source
Reference LP SECONDARY ALARM 1B: 1
|
| Explanation:
| 
| We have found a situation in the Composer wiring tables we cannot reconcile.
|
| The message with "Wired in Composer only" can show a place where DBDOC did 
| not make a connection. The only examples we have found so far involve lines 
| that have a connector on the end of an input arrow, or that have 
| an output directly connected to an input with no line connecting them.
|___________________________________________ 
:filter "-INTERNAL_SPLUS-PGP" "Unknown Symbol: " "S+ Scripting Error" "[NOT]"
| 
|                     DBDOC-INTERNAL_SPLUS-PGP.ERR
|
| Examples:
| Unknown Symbol: '
| S+ Scripting Error: Unsupported Tag Atom 
|
| Explanation:
|
| An unknown symbol was identified while processing graphics.
| An unsupported tag atom was identified in S+ graphics
|_______________________________________ 
:filter "-INTERNAL_PG2" "Unknown pseudotype: " "dynamic scale used " "Unhandled substitution:" "text hotspot record too long" "assigning PST_" "New rotation value for element" "Generate dynamic bar" "Unassigned pseudotype" "No processing available for:" "assigning PST_" "PG2_LIVE_DATA (or variant) - discarding record" "PG2 record element " "possible pseudotype?" "pg2_lookup_submode" "category: " "[NOT]"
|
|                     DBDOC-INTERNAL_PG2.ERR
|
| Examples:
| Unknown pseudotype: <"PV/UNITS"> INFI 90 Harmony ENH Analog Out:G3a_EngValue0116.b_UNITSATOM_cv
| 2TY16003_MA: dynamic scale used in combination with dynamic bar record type, generate PG2_STATIC type at <2554,1064>
| Unhandled substitution:
| text hotspot record too long, skipping
| New rotation value for element:
| Generate dynamic bar for 21LIC373@PV Module 5,11,02 Block 660 with zero: 0.000000, span: 100.000000
| Unassigned pseudotype for FC1121 Module 2,02,02 Block 146 DONOR NAAR A1210 from ip_valuetype: Ratio
| No processing available for: FO1_Analog_Tag_Atom
| assigning PST_PROCESS_VARIABLE to TIC60705 Module 1,03,06 Block 1900 E-6205 EFFL. TEMP. CONTROL
| PG2_LIVE_DATA (or variant) - discarding record
| PG2 record element is NULL
| possible pseudotype? <if $'pr::OPC_ABB_Flame_Scanner:General Properties:BQ' && ev::v_BadQuality_A then "BQ" else FormatReal($'pr::OPC_ABB_Flame_Scanner:Control Connection:A FREQUENCY', ev::m_numdec)>
| pg2_lookup_submodel (from m_pnLibrary_Records): AUP_PVValue PG2 (add PG2 to desc)
|    category: INFI 90 Harmony Analog Read:AUP_PVValue PG2
|
| Explanation:
|
| An unknown pseudotype indicates an element was identified by DBDOC as a pseudotype but is not yet a supported type.
| Dynamic scale used in combination with dynamic bar record type appears to indicate that dynamic scale was used to define a dynamic bar, which causes the dynamic bar to be generated over top of the scale region
| New rotation value for element identifies rotation values that are not intepreted and may affect hotspot placement.
|______________________________________ 
:filter "-INTERNAL_MESSAGE" "IRefRes table: description set to blank" "Microstation attribute: linking to " "Branch List is of incorrect type: Missing List Elements" "No pnSpec - initializing variable name and label" "Cannot embed PDF file due to PDF security settings" "[NOT]"
| 
|                     DBDOC-INTERNAL_MESSAGE.ERR
|
| Examples:
| IRefRes table: description set to blank
| Microstation attribute: linking to 
| Branch List is of incorrect type: Missing List Elements
| No pnSpec - initializing variable name and label
|
| Explanation:
| These messages are new to DBDOC and do not yet appear in the error browser.
|___________________________________________ 
|
:suppress "doesn't match function block number 10, function code 81"
;
; The CADEWS package, under certain circumstances, places the value 0 into the
; location storing the output block number 10.  This deficiency has no effect
; on the operation of the Infi90 system and may be ignored.
;
:suppress "NULL node"
;:suppress " mapped to type "
:suppress "refcount"
:suppress "More than 10 points with no source -- cutting off messages"
:suppress "VAL_ATOM"
:suppress "Linking to "
:suppress "Missing alarmvector graphics report for console"
:suppress "files to be compressed"
:suppress "Generating wiring file"
:suppress "800xA type:"
:suppress "800xA type statistics"
:suppress "Unknown dominance type"
:suppress "  (0x"
:suppress "}"
:suppress ": {"

:obsolete "-CHECK_CANNOT_LOAD_FILE" "loading file"
:obsolete "-CHECK_CANNOT_OPEN_DBF_FILE" "open DBF file"
:obsolete "-CHECK_CHAINED" "Chained local reference"
:obsolete "-CHECK_COINCIDENT_VERTICES" "Coincident vertices in "
:obsolete "-CHECK_COLOR_INDEX" "Requested color index "
:obsolete "-CHECK_DUPLICATE_WIRE" "duplicated "
:obsolete "-CHECK_FONT_INDEX" "Requested font index "
:obsolete "-CHECK_GLYPH" "Glyph "
:obsolete "-CHECK_INVALID_LENGTH" "Invalid "
:obsolete "-CHECK_NO_SOURCE_DATABASE" "No source: Database"
:obsolete "-CHECK_PARSE_ERROR" "Parse Error:"
:obsolete "-CHECK_PARSING_TERMINATED" "Parsing terminated with non-null input buffer pointer"
:obsolete "-CHECK_REINTERPRETING_RECORD" "Reinterpreting record type"
:obsolete "-CHECK_SCALE_FACTOR" "scale factor"
:obsolete "-CHECK_UNKNOWN_RECORD_TYPE" "Unknown record type "
:obsolete "-CHECK_UNKNOWN_SUBTYPE" "Unknown subtype "
:obsolete "-CHECK_UNSUPPORTED_DYNAMIC_SYMBOL" "Unsupported Dynamic Symbol"
:obsolete "-IGNORE_BAD_SCALE_FACTOR" "Bad scale factor:"
:obsolete "-IGNORE_CONVERSION_ERROR" "Conversion Error:"
:obsolete "-IGNORE_FC29_WIRE" "(FC 29) does not connect to anything at "
:obsolete "-IGNORE_FC44_WIRE" "(FC 44) does not connect to anything at "
:obsolete "-IGNORE_INT_UNEXPECTED" "Int unexpectedly "
:obsolete "-IGNORE_NO_CLD_FILES" "No CLD files in "
:obsolete "-IGNORE_NO_SOURCE_SUMMARY" "No source summary:"
:obsolete "-IGNORE_POSSIBLY_CORRUPT" "Possibly corrupt DWG file"
:obsolete "-IGNORE_PROCESSING_MTEXT" "Processing MTEXT record "
:obsolete "-IGNORE_SAME_SIDE_OF_CHORD" "same side of chord"
:obsolete "-IGNORE_UNEXPECTED_TOKEN" "Unexpected token "
:obsolete "-IGNORE_UNKNOWN_ACTION" "Unknown action "
:obsolete "-IGNORE_VARREF_UNDEFINED" "VarRef "
:obsolete "_ATTRIBUTE_TAG_NOT_FOUND" "Reference to undefined tag:"
:obsolete "_CANNOT_OPEN_FILE" "t open file"
:obsolete "_CONDUCTOR_SUBMODEL" "Conductor sub-model "
:obsolete "_DUPLICATE_DOCUMENT_NAME" "Document name already in use"
:obsolete "_FILE_INPUT_FAILURE" "input file"
:obsolete "_FLOATING-POINT_VALUE" "Floating-point value"
:obsolete "_INTEGER_VALUE" "Integer value"
:obsolete "_NO_CONNECTION" "Line does not connect to anything"
:obsolete "_NO_LEGAL_LPM" "No legal LPM match "
:obsolete "_SPEC_HAS_NO_INPUT" "Output not located for input S"
:obsolete "_TAG_NOT_FOUND" "not found in database"
:obsolete "_UNDEFINED_LINE_CONTINUOUS" "undefined line type: CONTINUOUS"
:obsolete "_UNKNOWN_LINETYPE" "Unknown line type"
:obsolete "-CHECK_BLOCK_MATCH" " (block match)"
:obsolete "-IGNORE_INPUT_VARIABLE" "Input variable zzz:000"
:obsolete "-IGNORE_NULL_VALUE" " null value "
:obsolete "-CHECK_INPUT_VARIABLE" "Input variable "
:obsolete "-IGNORE_NO_BLOCK_MATCH" " (no block match)"
:obsolete "_NO_SOURCE_LADDER" "No source: Ladder"
:obsolete "-IGNORE_SCAN_TAG-IGNORED" " using DB tag of same name, diff"
:obsolete "_TREND_INDEX" "rend index "
:obsolete "_TREND_TAG_NAME" "rend tag name"
:obsolete "-CHECK_MISSING_AUTOCAD_REFERENCED_POINT" "Unable to find AutoCAD"
:obsolete "-CHECK_UNSUPPORTED_CHAR" "Unsupported character in string"
:obsolete "-IGNORE_SCAN_TAG" "Scanned tag"
:obsolete "-CHECK_DUPLICATE_FUNCTION" "Duplicate F(X)"
:obsolete "_INPUT_SHAPING" "Input shaping"
:obsolete "-CHECK_REFERENCED_UNDEFINED_TAG" "references undefined tag";
:obsolete "_SCOPE" "No match in scope found"
:obsolete "-CHECK_PCU_MODULE_ZERO" ",00,00"
:obsolete "-CHECK_REMSET_OUTSIDE_LIMITS" "is outside configured limits of"
:obsolete "-CHECK_ILLEGALLY_ADAPTED_ERROR" "illegally adapted"
:obsolete "-IGNORE_INVALID_GRAPHIC_0" "graphic:0 "
:obsolete "-CHECK_NON-ALARMING_DIGITAL_GROUP_99" " is in Alarm Group 99 in database"
:obsolete "-IGNORE_CONSTANT_TREND_BLOCK" "FC 66 is wired from constant block " "FC 179 is wired from constant block "
:obsolete "-CHECK_AIS-FBS_TRIP_ON_FAULT" " (FC 132) has S3 zero "
:obsolete "-CHECK_CONSTANT_WITH_ZERO_GAIN" "means that constant "
:obsolete "-INFO_PRIMARY_DISPLAY" "Primary display" "[227]"
:obsolete "-COSMETIC_ZERO_LENGTH_WIRE" "Creating zero length wire:" "[224]"
:obsolete "-IGNORE_DUPLICATE_WIRE" "duplicated "  "removed in case 12532" "[NOT]"
:obsolete "-IGNORE_INPUT_SHAPING" "Input shaping on " "removed in case 11756" "[NOT]"
:obsolete "-COSMETIC_TAG_NOT_EXCEPTION_REPORTED"
; The missing indexes will be created in the next pass.
;
:rest "_RESIDUAL"
