This page covers KLA platforms, including Puma and SP model pages plus a Voyager reference entry for cases where the family is known but the detailed model still needs confirmation.
Choose the KLA family or device page that matches the platform you are working with. If you only know the model name, go straight to the device page.
Puma is one of the clearest KLA repair sections today, with two model-specific pages already linked to confirmed laser references.
SP2 and SP5 are available as dedicated model pages. If you know the tool model but not every laser detail, these pages are the right place to start.
Voyager remains listed for KLA-related cases where the family is known and the exact model still needs to be confirmed.
For KLA-linked cases, the fastest route is usually to confirm the tool family, visible model name, and current operating behavior before trying to map every source-side detail.
Equipment family and model labels are usually the clearest public identifiers and help place the case on the right support path quickly.
Short notes on how the system is behaving now are often enough to narrow whether the case needs bench repair, source review, or replacement planning.
If the model is already known, open that model page directly. If not, send the KLA platform name, visible labels, and current symptoms so the review can start without delay.
You do not need complete laser-source information before contacting us. A KLA platform reference, the equipment model, and clear fault notes are enough to begin review.
These details help narrow the section quickly and make it easier to validate any paired laser reference when it is relevant.
Photos of labels, laser sections, and alarm behavior usually accelerate both repair assessment and replacement-path decisions.
These public-facing notes convert recent field feedback into intake guidance. They are not a final diagnosis; they help buyers prepare a clearer first review.
When these symptoms appear, describe the operating state, recent change, alarm behavior, output condition, and whether the issue is intermittent or repeatable.
Voyager should stay as configuration guidance on the KLA family page until the exact public model structure is confirmed.
If not, send the platform name, visible labels, and current system state through the RFQ form and we will help review the case.