Eaton S611 User Manual

Also see for S611: Installation leaflet Quick start installation guide Installation leaflet

Contents

S611 Soft Starter MN03902011E—May 2012 www.eaton.com 77S611 Fault CodesCode Fault Condition Solution3 Watchdog • Firmware fault —5 Internal Memory • Internal FRam memory error • Component failure on printed circuit board• Contact EatonCare for service6 User Interface CommunicationsFailure• Communications to UI have beeninterrupted• Possible hardware failure• Firmware is not communicating internally• Cycle 120 Vac control voltage power to attempt toclear problemNote:The User Interface module is not required (default) for operation of the S611 after the parameters have been set. The S611 may be configured to fault ifthe User Interface module is removed by enabling the User Interface Comm Loss Fault parameter setting in the Advanced Config. menu. To reinstall a UIthat has been removed, remove 120 Vac control power, reinstall the UI, then restore 120 Vac control power.7 Internal Program Memory • Corrupted firmware or memory• Flash CRC• Cycle 120 Vac control power to the S611• Contact EatonCare for serviceNote:Internal memory issues may be either a hardware or firmware failure. In the event of a firmware problem, cycling 120 Vac control power may restoreproper operation to the S611. If cycling power does not correct the fault condition, contact EatonCare for service.8 Voltage Zero Cross Lost • Mains voltage lost• Phase L1 or L3 lost• Load disconnected• Restore mains or lost phases• Verify that the load is connected and any disconnectdevices are properly engaged• Contact EatonCare for serviceNote:The SCRs are unable to fire if there is no source voltage and/or load on the unit. Verify that all mains control devices are properly connected and poweredprior to initiating a START command.9 Communications Loss Port A • Communications to a remote networkcontroller was lost during run cycle• Device disconnected• Connection lost• Reattach network controller, verify that the unit isrecognized by the system controllerNote:This fault corresponds only to network communications. It does not relate to internal communications among components on the printed circuit board(PCB).10 Communications Loss Port B • Communications to a remote networkcontroller was lost during run cycle• Device disconnected• Connection lost• Reattach network controller, verify that the unit isrecognized by the system controller• Comms Port B adapter module failed or disconnectedNote:This fault corresponds only to network communications. It does not relate to internal communications among components on the printed circuit board(PCB).www.comoso.com