
Under improvement · barcode in, rules applied
Prober Barcode Entry and LOT Handling
When the LOT number is typed into the prober by hand, one wrong character files a whole batch under someone else's name. This project feeds a USB scanner into the prober's native barcode port: the relay writes the barcode at the port's own serial settings, a rule engine pulls the LOT segment out of the full barcode and checks it against the machine's own field rules, and anything that fails is logged rather than sent. The project is under improvement, proven on our own engineering machine, with no customer delivery yet.
Applications
Designed for the following probe card manufacturing, test and maintenance tasks.
Replacing manual LOT entry
Scan instead of typing to cut batch-number mistakes.
Extracting from mixed barcodes
Take only the LOT out of a long code that also carries wafer and date fields.
Scan traceability
Every scan stays in the relay log, so the raw barcode behind each entry can be traced.
Specifications
The final configuration follows the card, interfaces, site conditions and acceptance items.
| Item | Specification / configuration | Notes |
|---|---|---|
| Project stage | Under improvement, in-house | Validated on our own machine; no customer delivery |
| Integration path | USB scanner to relay to the prober's native barcode port | No keystroke-emulation route |
| Serial settings | 9600 8N1 with CRLF terminator | Fixed by the machine interface |
| Scanner compatibility | Any USB HID keyboard-mode scanner | No brand lock-in, with auto-detection |
| Framing | Enter or Tab terminates, or a 900 ms idle flush | Multiple inputs and hot-plug supported |
| Rule model | Regex pattern, replacement, priority, case and trim | Highest-priority match applies |
| Rule authoring | Scan once, drag-select the LOT, rule is generated | With live preview and a test field |
| LOT validation | Up to 18 characters, A-Z 0-9 and . _ -, alphanumeric first character | Aligned with the prober's own LOT field |
| Failure policy | No rules means pass-through; a match that fails validation is not sent | Rejected scans are logged only |
| Rule deployment | Atomic snapshot replacement, hot-reloaded by the relay | No service restart to change rules |
| Traceability record | Barcode, LOT, wafer, device, operator, disposition | Records are written by the collector only |
Workflow
Interface check
Confirm the barcode port, serial settings and the scanner on site.
Rule setup
Scan real barcodes, drag-select the LOT and preview the generated rule.
Trial run
Validate extraction and checking against real batches and watch the rejects.
Delivery definition
Set deployment scope and support model from the trial results.
Project delivery
Sample evaluation
Confirm the object, interfaces, current state, failure modes and available validation samples.
Technical agreement
Define configuration, measurement method, limits, takt, data interfaces and responsibilities.
FAT
Verify functions, repeatability, reporting and exception handling with agreed samples.
SAT
Complete site integration, training, upstream/downstream interfaces and issue closure.
Configuration and acceptance
System configuration, optional items and acceptance conditions are summarized below.
Stage and evidence
The implementation, deployment scripts and four-language operator screens all exist, and our own engineering machine holds real scan records; the item is not yet in the company's external product catalogue, so it is marked under improvement.
Integration boundary
Only the machine's native barcode port is written to; the prober's own control software is untouched. Applicability depends on the model having that port.
Data boundary
Scan records are written by the collector and cannot be entered by hand; whether the machine accepted a LOT is decided by the machine's own record.
Share the card, interfaces and target
Send the sample, installed equipment, current issue and target takt. We will acknowledge receipt within one business day.
