|
Anomaly Guide#42 Unexpected Garment on Loading Hook (BiDir/UTransfer) |
| Related Pictures |
|
First determine which device triggered the anomaly by examining the anomaly message on the application's computer console (within the Metalprogetti B2K/BAM application).
For Uniform Conveyor Systems running B2K
The anomaly record will contain both the CONVEYOR number as well as a POINT description which indicates the faulting device (arm, gate, etc).
For Storage Systems running BAM
The device ID is made up of 4 digits - the first 2 indicate the conveyor ID, the second 2 indicate the device ID.
In the following examples, XX represents conveyor ID while the last 2 digits represent the device.
Main conveyor anomalies will always be XX-00,
extraction arm anomalies will always be XX-01 through XX-10 depending on how many arms are installed,
and feedrail anomalies will always be XX-11 as demonstrated below.
|
| Possible Causes | Checks to Perform |
| Garment is actually still on loading hook | This anomaly is usually legitimate and can be caused by any of the following: -Garment failed to load onto conveyor because it was off-center on hanger -Garment failed to load onto conveyor because hanger tip was malformed -Garment failed to load onto conveyor because spreaders were tangled |
| False whisker switch signal or other electrical fault | Contact Metalprogetti Support department for further assistance. |