A Statistics
August 2010 AS3690 Operator Manual A-9
Unexpected Piece at
Bin 2 Sensor
Results when a piece is detected at the bin 2 sensor that the software was
not expecting. A gate that did not fire properly usually causes this to occur.
Unexpected Piece at
Bin 3 Sensor
Results when a piece is detected at the bin 3 sensor that the software was
not expecting. A gate that did not fire properly usually causes this to occur.
Unexpected Piece at
Bin 4 Sensor
Results when a piece is detected at the bin 4 sensor that the software was
not expecting. A gate that did not fire properly usually causes this to occur.
Unexpected Piece at
Bin 5 Sensor
Results when a piece is detected at the bin 5 sensor that the software was
not expecting. A gate that did not fire properly usually causes this to occur.
Invalid Piece
Complete Response
Results when an invalid piece id is received from CertainScan upon piece
completion.
Piece Thickness
Sensor Null Below
Minimum
Results when the thickness sensor is lower than the minimum null defined
in the machine parameters.
Piece Thickness
Sensor Null Above
Maximum
Results when the thickness sensor is greater than the maximum null
defined in the machine parameters.
Piece Thickness
Sensor Runout
Problem
Results when the thickness sensor runout is greater than the maximum
runout defined in the machine parameters.
Missing Piece at
Straight Through
Path
Results when the piece was supposed to go to the stacker bypass bin but
didn't.
Batch Manager has
an Internal Error
Results when there is an internal error within Batch Manager.
Detected a File Write
Error
Results when the software detects a problem with writing image or batch
files to the specified directories.
ScanLink Plug-in
Failed
Results when there is a failure sending information to the ScanLink plug-in.
ScanLink Plug-in
Requested a Jam
Results when the ScanLink Plug-in has requested a jam.
Host to Controller
Report Missing
Results when the controller is expecting piece information from
CertainScan and does not receive it within the expected time window. This
is frequently caused by pushing the system to its limits or by something
causing the system to get out of sync.
Jam Caused by
Reject
Results whenever a reject other than Jamsorts occurs. Thus every reject
other than Jamsorts is counted as a jam under this category. The Job
Parameter "Stop Machines for Rejects" must be set to something other
than "No" for rejects to jam the machine. Otherwise, rejects will be directed
to the reject bin and processing will continue.
TABLE 6: Reasons for jams (Continued)
To Next Page
Loading...
