Manufacturing Automation Interface for Diagnostics in Diagnostic Control Program
Original Publication Date: 1996-Dec-01
Included in the Prior Art Database: 2005-Apr-01
Kritt, B: AUTHOR [+2]
AUTOEXEC, TEST.CTL, MFGCODE.EXE, CMD.COM and DIAGS.COM make the manufacturing environment. (AUTOEXEC, TEST.CTL, MFGCODE.EXE are modules developed by manufacturing. CMD.COM and DIAGS.COM are DCP modules.)
Manufacturing Automation Interface for Diagnostics in
AUTOEXEC, TEST.CTL, MFGCODE.EXE, CMD.COM and DIAGS.COM
manufacturing environment. (AUTOEXEC, TEST.CTL, MFGCODE.EXE are
modules developed by manufacturing. CMD.COM and DIAGS.COM are DCP
are developed by Engineering Software with the
purpose of aiding CEs and customers in the detection of hardware
failures. These diagnostics are also used by manufacturing for
There is a
need to reduce manufacturing cost and product cycle
time during manufacturing. The problem is that manufacturing has to
modify every one of these diagnostics in order to be able to run in a
manufacturing environment. An interface between the manufacturing
driver code and the Diagnostic Control Program (DCP) can be included
in the next release of DCP such that manufacturing can feed
predefined keystrokes to the diagnostic via DCP. This interface will
also reduce run time in this environment and eliminates the need of
having an operator to input responses to diagnostic messages on every
system. Every PC unit in the assembly line can be tested by this
process; it only requires one operator to read the error log and
determine the acceptance or rework of the unit.
Interface - The idea is to make some basic
changes to the Diagnostic Control Program (DCP) to make it
Manufacturing communicates with DCP via software
When DCP runs in manufacturing mode the following takes place:
o DCP runs in the Advanced level mode under DOS
o Upon completion DCP returns to DOS
o DCP runs without prompting the operator for responses
o Runs single pass on all devices (attended)
o DCP communicates with manufacturing interface at
selected points through the DCP logic
- before each diagnostic runs
- after each diagnostic completes
- during screen/keyboard interactions
o logs all errors to default disk
Some of these terms are manufacturing
related and it is not the
intent of this document to elaborate on the manufacturing interface.
1. Unit in run-in powers up and runs AUTOEXEC.
AUTOEXEC or existing DCP calls MFGCODE.EXE (Manufacturing
2. MFGCODE.EXE sets up some MFG unique SW INTS which will be
called by the DCP at strategic points in DCP execution.
MFGCODE.EXE also opens and reads in TEST.CTL (a text control
file which determines which diagnostics to run and any
parameters or screen responses required by the diagnostics).
3. MFGCODE.EXE loads and executes advanced diagnostic CMD.COM
/M (CMD.COM is the executable name for the advance diagnostic
DCP. The /M is a manufacturing mode command line parameter).
4. CMD.COM executes but...