TDK Load Port Acceptance: The 7-Point Checklist I Use Before a Module Reaches the Tool

I work as a quality manager at an automation company that integrates clean-transfer modules for semiconductor tools. When people search for TDK Japan, they usually mean the manufacturer behind the parts we use every day. But in my job, that is only the starting point. I sign off on every load-port order before it reaches our build floor, reviewing roughly 130 line items a year. Maybe a little more; I would have to check the 2024 log. Around 12 percent of first deliveries get rejected for something I can put in writing.

Before this role, I inspected incoming parts at a home-health device company. Our flagship product was a Platinum blood pressure monitor sold through pharmacies. We learned the same lesson there: the component quality inside a product determines whether customers trust the product. That experience still shapes how I look at parts that arrive here.

This checklist is for anyone who receives or integrates TDK load ports, whether you are an OEM building wafer equipment or a factory doing incoming acceptance. It gives you seven concrete checks. No theory, just the order I run them in.

When to use this checklist

Use it before first installation, before a module goes into a process tool, or whenever a supplier changes. I do not use the same checklist for a fuse or a ferrite core. A load port is a module with motors, sensors, firmware, and mechanical parts. It deserves a full acceptance procedure, not a quick visual check.

Check 1: Verify which company you are really buying from

The words TDK and TDK Japan are not evidence by themselves. The real company is TDK Corporation, based in Japan. Around it there are authorized subsidiaries, brand badges like TDK Electronics and TDK-Lambda, and a long list of traders who put TDK in a description to close a sale.

We had one shipment in 2023 where the label looked almost correct. The logo was right, the country of origin matched, but the model number had an extra dash and the serial range did not follow TDK packaging conventions. The supplier insisted the units were factory overruns. Maybe they were. We still returned them. It cost us about two weeks and a fair amount of frustration. Now every purchase order states the full TDK legal entity, manufacturing location, and expected serial-number format.

That step matters more than people think. If a company cannot tell you exactly which legal entity made the item, you have no clear path for warranty, documentation, or technical support.

Check 2: Verify the exact product revision, not just the part number

Part-number matching is the baseline. It is not enough. Load-port modules get revised over time. A change in firmware, door mechanism, or connector layout can make an older revision unsuitable for your tool, even when the main part number is identical.

Before doing any physical test, pull the product drawing and confirm:

• Model and revision code
• Power and pneumatic requirements
• Carrier type the module is designed for
• Firmware version loaded at the factory
• Documented interface pinout

I have seen teams skip firmware checks because software can be updated later. That is true, but later is not free. Re-flashing a module while it sits in a cleanroom costs time, and any mismatch raises the chance of a configuration error.

Check 3: Run a real door-cycle test with a test carrier

A load port can look clean and still have a mechanical alignment problem. I do not trust paperwork for this part. I trust cycles.

Use a test FOUP or carrier that you are willing to sacrifice. Do not use a production carrier. Run at least 100 automatic door open and close cycles. Measure latch position, door seal compression, and cycle time at the beginning, middle, and end of the run.

In Q1 2024 we found a module that passed every electrical check but started drifting after about 60 cycles. The door still closed, but the latch position moved outside the documented tolerance. The vendor said it was within industry standard. We rejected the module anyway. Our customers do not accept that kind of drift, so neither should we.

Check 4: Test the handshake through your actual controller

Bench testing with a PLC simulator is useful, but it does not always show how a load port behaves when it talks to your tool. We once accepted a module that worked perfectly on a test bench and then failed during integration because one handshake signal was pulled in the wrong direction.

If your tool uses SEMI E84 parallel I/O for carrier handoff or E87 messaging for carrier management, make sure the test setup reflects that. A generic statement like meets SEMI requirements is not enough. The supplier should specify which standards were tested. If they cannot name the standards, ask for more evidence before you approve the unit.

Check 5: Test the reset and recovery path honestly

People call us and ask how do you reset a phone when their device misbehaves. With a consumer phone, the answer is often: hold the button and try again. A load port in a fab is different. You do not want a factory-reset mentality when a module is holding a carrier mid-transfer.

Run these scenarios before acceptance:

• Power loss during door-open state
• Communication loss during carrier handoff
• E-stop activation and restart
• Fault recovery after a sensor timeout

The module should return to a defined state. It should not drop the carrier, and it should not require an operator to manually force the mechanism back home. If a supplier tells you to just cycle power and see what happens, that is a warning sign.

Check 6: Demand a serialized test report with the shipment

A certificate of conformity is not the same as a test report. A generic certificate says the product meets a specification in theory. A serialized test report shows what was actually measured on the unit you received.

For every load port, we request:

• Serial number and test date
• Measured door-cycle results
• Electrical handshake pass or fail status
• Firmware version present during testing
• Leak or pressure test results

This saved us from a costly mistake last year. A supplier sent a module with a clean certificate but the test report did not match the serial number range. That discrepancy alone was enough to stop the shipment until they explained it.

Check 7: Compare the total cost, not the unit price

My view on procurement is simple: the lowest quote is not the cheapest option once you include installation, downtime, and rework. This is not a slogan. I have watched a $1,700 price difference on a load-port order turn into a $14,000 problem when the module failed during integration and we had to pull a technician from another project.

When you evaluate a TDK load-port supplier, include these costs:

• Lead time and shipping method
• Availability of commissioning support
• Documentation language and completeness
• Return process if rejection happens
• Cost of a module failure after it is installed

Buying from an authorized TDK distribution channel usually costs more than a no-name broker quote. In my experience, that difference is often worth it. The broker disappears when there is a problem. The authorized channel has a process for it.

Three mistakes I still see

First, people treat the reset test as a quick power cycle. Do that, but also test recovery after an E-stop. That is where hidden faults show up.

Second, people skip the door-cycle test because the load port looks new. New modules can still have alignment issues after transport. We once received a unit with a visibly normal exterior and a door latch that was off by almost two millimeters after shipping.

Third, people let a low price shorten the acceptance process. I understand the pressure. But the cost of rejecting a module before installation is small compared to the cost of pulling it out of a production tool later.

The best load-port deliveries are the boring ones. The paperwork matches, the cycles are stable, the handshake works, and the recovery path behaves. When that happens, you can install the module and move on to the next problem. That is the outcome this checklist is designed to create.