Opex Sure Sort Traduction Des Instructions Originales page 292

5.3. Reject and Jam Definitions
5.3.1. Rejects
Reject codes are sent to the internal ELC piece database for tracking and to be
sent to RPM. These codes are not sent to the WMS back-end.
The .csv file that you export from the ELC screen will only display rejects if they
occurred during the selected time range in your report. The following is a list of
all possible rejects.
5.3.1.1. ELC Rejects
Reject message
Barcode Scanner
Timeout
Multiple Pieces
Triggered
Unexpected Piece
No Read
Not Found
Back-End Not
Connected
146
Description
When the ELC is expecting a barcode read from the
barcode plugin, but does not get it in time.
When there are pieces too close together and they
cross the imaging sensor. The ELC will not be able to
accurately pair the barcode to the correct piece so it
will reject them both. Overlaps with the Host 'Gap Too
Small' reject reason, so will not be triggered too often,
but remains as an added assurance.
The ELC expects pieces being inducted to pass
through the states in an expected order. When a piece
enters states out of order, usually due to a timing
issue, the ELC will reject it with this code.
The ELC received a blank read from the barcode
scanner plugin.
The barcode received by the ELC was not found in the
WMS back-end database, or the back-end returned a
blank destination in response to the ELC's barcode
request.
The WMS back-end is not connected to the ELC. Any
piece inducted while the back-end is not connected
will be rejected for this reason.
Sure Sort™ Operator Manual
OPEX Corporation
Statistics