A conveyor system spans 200 meters across a distribution center. The traditional design places all VFDs in a central air-conditioned cabinet, then runs a 200-meter shielded motor cable to the farthest drive. At 200 meters, the cable capacitance alone draws enough leakage current to nuisance-trip the drive's ground-fault protection. The fix: a shielded output reactor ($400) plus a sine-wave filter ($900) per drive — components that exist solely because the drive is far from the motor. An IP66 wall-mount VFD bolted directly to the conveyor frame near the motor eliminates the long cable, the filters, and the cabinet space. It also eliminates the air conditioner.
The enclosure decision is not a protection-class question. It is an architecture question: where does the drive physically belong in the machine?
The IP20 assumption: why drives traditionally live in cabinets
IP20 (protected against solid objects >12.5 mm, no water protection) is the default enclosure rating for general-purpose VFDs. An IP20 drive must be mounted inside a secondary enclosure — a control cabinet — that provides the environmental protection (dust, water, mechanical impact) and the touch-safe barrier (IP20 terminals are finger-safe but not tool-safe in public areas). The cabinet also provides a managed thermal environment: intake filters, exhaust fans, and sometimes air conditioning maintain an internal ambient below the drive's rated maximum (typically 40–50°C). The IP20 assumption is so deeply embedded in panel design workflows that many engineers never question it — the drive goes in the cabinet because drives have always gone in the cabinet.
What makes an IP55/IP66 drive different, structurally?
An IP55 or IP66 VFD is not an IP20 drive in a gasketed box. The entire thermal design is different. An IP20 drive cools itself by drawing ambient cabinet air through a heatsink tunnel with a fan. An IP66 drive must reject heat to the outside environment through its enclosure walls — typically via a rear-mounted finned aluminum heatsink that is sealed against the enclosure with a gasket, so the electronics are fully enclosed but the heatsink fins are exposed to ambient air. No internal airflow crosses the electronics compartment; no external contaminant enters. This "through-wall" thermal path determines the drive's current derating curve at elevated ambient temperatures — a parameter most critical when the drive is mounted outdoors in direct sunlight in Arizona or Saudi Arabia.
The architecture decision: cabinet-mount vs machine-mount
| Decision Factor | IP20 Cabinet-Mount | IP66 Wall/Machine-Mount |
|---|---|---|
| Motor cable length | 10–300 m (filters often required >50 m) | 1–20 m (filters rarely needed) |
| Cabinet cost (space + cooling) | $800–$3,000 per drive bay | $0 (no cabinet) |
| Ambient temperature tolerance | Controlled (AC maintains 35°C max) | -20 to 55°C (derate above 40°C) |
| EMC compliance effort | Shielded motor cable + EMC gland at both ends | Short cable = lower radiated EMI |
| Access for commissioning | Open cabinet door, connect laptop | Walk up to drive; Bluetooth/app on newer models |
| Dust/washdown protection | Depends on cabinet IP rating | Native (IP55 = dust-protected + low-pressure jets; IP66 = dust-tight + powerful jets) |
When does cabinet-mount (IP20) remain the right answer?
IP20 cabinet-mount is still the correct choice in four scenarios. First, high-density multi-drive installations — a panel with 12 drives powering 12 closely spaced motors on a packaging machine — where the cable runs are short and the cabinet consolidates power distribution, fusing, and control wiring at one point. Second, environments above 55°C ambient (steel mill, foundry, glass plant) where no sealed drive can reject heat fast enough and a climate-controlled cabinet is the only way to keep the drives alive. Third, ATEX/IECEx Zone 1 or 2 installations where the drive must be outside the hazardous area regardless of IP rating — the cabinet is in the safe area, and only the motor is in the classified zone. Fourth, applications with frequent drive access for parameter changes, where opening a cabinet door is easier than navigating to a drive mounted 15 feet up on a machine frame.
When does machine-mount (IP66) win on total installed cost?
Machine-mount wins when the motor is physically distant from the control panel (conveyor systems, pump skids, outdoor HVAC condenser fans, remote irrigation pumps), when cabinet space is at a premium and adding another bay costs $2,000+ in enclosure, cooling, and labor, or when a decentralized drive architecture is already part of the machine concept — the drive is one node on the machine's fieldbus, not one card in a central rack. The installed-cost savings come from three line items: no cabinet bay, no long motor cable, no output filters.
The Siemens SINAMICS G115D is a wall-mounted distributed drive available in IP65 with PROFINET and full-featured I/O — designed to be mounted directly on the machine near the motor, eliminating the cabinet entirely.
What about maintenance access and service life?
The objection to machine-mount drives is often maintenance: "If the drive is on the machine, a technician has to climb onto the equipment to service it." The counterpoint is that an IP66 drive in a clean electrical cabinet would have lasted 15 years, but on a machine frame exposed to vibration, thermal cycling, and occasional washdown, the same drive might last 8 years. This is true — and it is priced into the decision. A machine-mount drive is a consumable with an 8–10 year service life, not a permanent installation. The TCO comparison must include one mid-life replacement for the machine-mount drive against the cabinet cost (which is a one-time capital expense). For a single remote drive, the machine-mount TCO is lower; for a cluster of 12 drives in one cabinet, the cabinet-mount TCO is lower.
The enclosure IP rating is the least interesting part of this decision. The real decision is: centralized or decentralized? If the machine architecture already puts I/O blocks, solenoid valves, and sensors on the machine frame, the drive belongs there too — and the IP rating follows from that architectural choice, not the other way around.
