PartCheck logic
From PlcWiki
(Difference between revisions)
Jon (Talk | contribs)
(Created page with 'Also applies to RackPartCheck There is a plc_parts.OPID file on the client. It contains the following columns: 1) VIN 2) CLEVER part number 3) OPID 4) barcode, or part …')
Newer edit →
(Created page with 'Also applies to RackPartCheck There is a plc_parts.OPID file on the client. It contains the following columns: 1) VIN 2) CLEVER part number 3) OPID 4) barcode, or part …')
Newer edit →
Revision as of 12:35, 13 October 2020
Also applies to RackPartCheck
There is a plc_parts.OPID file on the client. It contains the following columns:
1) VIN 2) CLEVER part number 3) OPID 4) barcode, or part thereof
After scanning and pairing with the operation, the client searches for the scanned barcode, or part of it, in the specified file. Searches from the current cockpit line. If it does not find the end of the file, it continues from the beginning.
If it finds a matching barcode in the fourth column, it looks in the second column to get CLEVER the part number. The obtained part number is compared with the required one for the given cockpit.
