Schneider LUB32: application decision record for TeSys Ultra power base
Use the exact LUB32 marking when enquiring about this TeSys Ultra power base. The category picture is a shared reference image, not a photograph proving the precise LUB32 configuration. The decision points below separate confirmed data from checks that remain site-specific.
Technical data to verify first
| Technical item | Verified value / selection note |
|---|---|
| Complete designation | LUB32 |
| Product identification | TeSys Ultra power base |
| Current class | 32 A |
| Connection | Screw-clamp control |
| Function | Basic motor-starter control |
Receiving inspection
A buyer should copy LUB32 without abbreviation and request a picture of the actual label. If the shipment differs from LUB32, hold it for technical review rather than relying on a similar catalogue illustration.
Site decision
Select the compatible control unit and verify motor duty. Treat a visually close code as a separate configuration until the manufacturer documentation confirms it.
Installation and handover
The responsible engineer should isolate the equipment and follow the current instructions for LUB32. Record settings, wiring, dimensions, software revision, battery state, calibration or protection-test results as relevant to TeSys Ultra power base. A commissioning note should explicitly identify the installed LUB32.
Store the LUB32 data sheet revision, site test report and accessory list with the asset file. This is especially important if a later repair request cites only LUB32 without the complete fitted assembly details.
Similar-looking catalogue codes
The 1 references below resemble the LUB3 pattern and are indexed on this representative LUB32 page rather than receiving separate pages. This is a visual search grouping only: their ratings, functions and compatibility may differ from LUB32.
Procurement handoff
Place LUB32 in the request title and repeat LUB32 in the line-item description. Ask the supplier to confirm the exact reference, quantity, documentation and delivery condition. The purchasing record for LUB32 should preserve any approved deviations in writing.
