Technical Specifications

FAQ

1. What is the main function of the Schneider ATV650D37N4E?
The ATV650D37N4E is a 37 kW Altivar Process variable-speed drive designed for speed and torque control of industrial motors. It supports asynchronous and synchronous motor applications and can be used for pumps, fans, compressors, conveyors, and other industrial process equipment. The integrated disconnect switch provides a convenient means of isolating the drive during maintenance and servicing.

2. What are the normal-duty and heavy-duty ratings of the ATV650D37N4E?
The ATV650D37N4E provides a 37 kW / 50 HP rating for normal-duty applications and a 30 kW / 40 HP rating for heavy-duty applications. At a 4 kHz switching frequency, the continuous output current is 72 A for normal duty and 59 A for heavy duty. Selection should be based on the motor rated current, load torque, acceleration requirements, and actual duty cycle rather than relying only on the motor’s nominal power.

3. What power supply is required for the ATV650D37N4E?
The drive operates from a three-phase 380–480 VAC supply at 50–60 Hz. Typical normal-duty input current is 66.2 A at 380 V and 45.9 A at 480 V, while the heavy-duty values are approximately 40.5 A and 35.8 A respectively. The upstream breaker, fuse, disconnect equipment, and power cables should be selected according to the actual installation current, short-circuit level, and applicable electrical requirements.

4. Which motor types are supported by the ATV650D37N4E?
The ATV650D37N4E supports both asynchronous and synchronous motors. Asynchronous motor control includes constant-torque, variable-torque, and optimized-torque operation, while synchronous applications include permanent-magnet and synchronous reluctance motors. During commissioning, accurate motor nameplate information should be entered so that the drive can establish appropriate current, torque, and speed control parameters.

5. What should be checked if the motor does not start?
First check the incoming three-phase power and confirm that no active drive fault is present. Then verify the run command source, frequency reference, control terminals, communication commands, start permissives, emergency-stop circuits, and external interlocks. If the drive indicates a valid run command but the motor does not rotate, inspect the motor output wiring, motor parameters, PLC logic, and any active control restrictions.

6. How can an overcurrent fault on the ATV650D37N4E be diagnosed?
Overcurrent can result from excessive mechanical load, motor faults, incorrect motor parameters, damaged cables, loose terminals, or overly aggressive acceleration. Check the motor and driven equipment for mechanical blockage or excessive torque demand, and inspect the motor cable and insulation condition. The acceleration time, torque settings, motor data, and selected normal-duty or heavy-duty operating mode should also be reviewed to ensure that the drive rating matches the application.

7. What should be done if the ATV650D37N4E trips repeatedly?
Start by recording the exact fault code and the operating conditions when the fault occurs, including output frequency, current, load condition, and operating stage. Determine whether the trip happens during startup, acceleration, constant-speed operation, or deceleration, then inspect the relevant power supply, motor, mechanical load, cooling system, wiring, and parameter settings. Avoid repeatedly resetting the drive without diagnosing the underlying cause, particularly when the same fault occurs under similar operating conditions.

8. What communication and monitoring functions does the ATV650D37N4E provide?
The ATV650D37N4E supports Ethernet, Modbus Serial, and Modbus TCP for communication with PLCs, HMIs, SCADA systems, and other automation equipment. It also provides process monitoring and control, power measurement, energy management, asset monitoring, and operating-drift monitoring. When communication problems occur, check the physical network connection, communication parameters, addressing, PLC or SCADA configuration, and the drive’s diagnostic information to determine whether the problem is caused by the network or by the control configuration.