How to
From PlcWiki
(Difference between revisions)
Line 7: | Line 7: | ||
When invalid part is scanned red alert appears in log frame … | When invalid part is scanned red alert appears in log frame … | ||
+ | |||
''Solution:'' | ''Solution:'' | ||
- Scan correct part. | - Scan correct part. | ||
Line 15: | Line 16: | ||
Client doesn’t recognize scanned barcode at all. Wasn’t able to assign input to any operation. | Client doesn’t recognize scanned barcode at all. Wasn’t able to assign input to any operation. | ||
+ | |||
''Solution:'' | ''Solution:'' | ||
Ensure that part being used is correct part. Most probably this barcode is not covered by SelectPattern in operations’ configuration. Has to be fixed in Clea. | Ensure that part being used is correct part. Most probably this barcode is not covered by SelectPattern in operations’ configuration. Has to be fixed in Clea. |
Revision as of 07:05, 26 October 2018
Issues
To bypass these issues temporarily one of the emergency barcodes PLCIL or PLCABCNEXT can be used.
When invalid part is scanned red alert appears in log frame …
Solution: - Scan correct part. - “Part equivalence” can be used in case that part is equivalent to requested. Barcode PLC temporarily can be used in emergency. Alternatively, Part equivalence module can be used.
Unknown barcode PIC:
Client doesn’t recognize scanned barcode at all. Wasn’t able to assign input to any operation.
Solution: Ensure that part being used is correct part. Most probably this barcode is not covered by SelectPattern in operations’ configuration. Has to be fixed in Clea.