Engineering prototype · bolt-on acquisition
Prober Information Box
The probers that have run a fab's back end for fifteen or twenty years still work; they just cannot hand you any data. The information box is a bolt-on acquisition unit: one link to the machine, another to the plant network, nothing changed inside the prober, and wafer geometry, test counters and probe-card touchdown and cleaning counts read out of the machine's own configuration card and running memory, with the screen and controls available in a browser. Its defining habit is refusal: every page states the grade of its source, and a page whose source is not connected locks itself rather than filling in a plausible number. The product is at engineering-prototype stage, running continuously on our own machine, with no customer delivery yet.
Prober category visual. The unit's form and integration follow the machine model on site.
Equipment and engineering solution
Applications
Designed for the following probe card manufacturing, test and maintenance tasks.
Data for legacy tools
Give in-service probers without modern data interfaces a readable set of run facts.
Probe-card usage history
Read accumulated touchdown and cleaning counts to support card change and cleaning decisions.
Remote status view
Watch the machine screen and counters from the plant network instead of walking to the tool.
SPECIFICATIONS
Specifications
The final configuration follows the card, interfaces, site conditions and acceptance items.
| Item | Specification / configuration | Notes |
|---|---|---|
| Product stage | Engineering prototype, in-house | Runs continuously on our own machine; no customer delivery |
| Integration | Bolt-on acquisition unit; the machine's control software is untouched | One link to the tool, one to the plant network, physically separate |
| Screen and control | The machine screen is captured and served to a browser, with input returned | Both paths are external interfaces, not machine software |
| Wafer geometry | Size, X/Y index, rows and columns, active dies | From the machine's configuration-card snapshot |
| Test counters | Total, tested, pass, fail, retest, skip, mark | From the machine's running memory, marked live |
| Probe-card counters | Accumulated touchdown and cleaning counts | Decoded losslessly, parameter by parameter |
| Barcode entry | USB scanner relayed into the machine's native barcode port | See the barcode entry project |
| Source grading | Each page marked live, machine-config snapshot, local config, offline or reference | Reference pages disable their controls |
| Module honesty contract | Each module declares what is implemented, what is not inferred and what it depends on | Metrics that cannot be computed say so instead of approximating |
| Interface languages | Chinese, Japanese, English, Korean | For multilingual floors |
| Hardware form | ARM64 embedded compute unit with capture and serial peripherals | Exact model and deployment form confirmed per site |
WORKFLOW
Workflow
Machine and interface survey
Confirm the model, the usable interfaces and the plant network conditions.
Source validation
Verify the configuration card, run counters and barcode paths one by one.
On-site trial
Observe data and stability at real production rhythm.
Delivery definition
Set acquisition scope, deployment form and support from the trial results.
FAT / SAT
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
Configuration and acceptance
System configuration, optional items and acceptance conditions are summarized below.
Stage discipline
Our own engineering machine runs continuously and produces real records - probe-card touchdown and cleaning counts, wafer geometry and live counters - but nothing has been delivered to a customer site, so the page presents an engineering prototype.
Integration boundary
Acquisition is bolt-on and does not modify the machine's control software; what can be read depends on the model and its interfaces and is confirmed machine by machine.
Data boundary
Pages are graded by data source and unconnected modules stay locked. Inferred values never stand in for measured ones, and no compliance certification or factory-system reporting on the machine's behalf is claimed.
Share the card, interfaces and target
Send the sample, installed equipment, current issue and target takt. We will acknowledge receipt within one business day.