Hardware Platform
The three inspection-cell configurations — Cobot Scanner, Gantry, and Rack-Mounted — and why the choice never changes your integration.
Every inspection cell is built on one of three base configurations, each modified and configured to the client's needs. They differ in how part and 3D scanner are brought together; everything above the metal — the programs, the Operator screen, the lifecycle events, the open REST API — is the same Cheetah software stack on every one.
Cobot Scanner#
The flagship configuration. A cobot carries the scanner through the program's motion sequence over the part — the arm brings the sensor to the geometry, giving the widest range of part shapes and approach angles.
Gantry#
The scanner traverses the part on a gantry — linear motion suited to scanning along a consistent axis.
Rack-Mounted#
The name describes the parts, not the scanner: the Rack-Mounted Hardware (RMH) Scanner inspects the modules that fill data-center racks — server and networking hardware, where connector damage, coplanarity across connectors, and dimensional conformity decide whether a unit ships. Parts load on magnetic quick-change trays over a ball-transfer surface, with bi-directional tray loading so the unit drops into a production line. Enclosure size and the scanning and vision hardware inside are configured per application.
One platform, whatever the metal#
The configuration decides how the scanner moves; it decides nothing else. Programs are authored the same way, operators see the same screen, and an integration built against the developer surface — events, API, SDKs — works unchanged on any configuration. Hardware is a deployment decision, not an integration decision.
Scanner and motion hardware are matched to your parts, tolerances, and throughput during scoping — the lineup above is the chassis, not the bill of materials. Talk to us about your geometry, or book a consultation to see the platform on your parts.