Eaton SC200 Operation Handbook

Also see for SC200: Installation and operation guide Installation and operation guide

SC200 Handbook102 Copyright © 2007-2011 Eaton Corporation. All Rights Reserved.IPN 997-00012-50H November 2011Problem Possible Cause Required ActionEthernet communicationsproblemIncorrect, disconnected or faultycable.Check a network patch cable is connectedfrom XS31 to a live network outlet.Replace faulty cable.Ethernet link is not active. On the Ethernet connector (XS31) check:Yellow LED is continuously lit to showlink is active.Green LED flashes to show traffic isreaching the SC200.See the diagrams on page 2 for positionof the Ethernet connector.Incorrect communicationssettings.See Ethernet Communications on page82.SC200 serial communicationsare disabled.Check S3P Access is enabled. See detailson page 95.Password required to changesettings (using DCTools orPowerManagerII).See Write Access Password on page 95.Web communicationsproblemEthernet communicationsproblem.See previous entry.Cannot connect to web server. Check IP address and other settings inSC200 are correct. Check correct IPaddress is used in web browser addressbar. See Ethernet Communications onpage 82.Check HTTP Access or HTTPS Access isenabled. See Web Access Security onpage 96.Cannot log on to web server. Incorrect Logon ID or Password, or noactive users setup.Use DCTools to set up an active user. SeeWeb Access Security on page 96.Web communications lost(Comms Lost error message).Check that the SC200 is operating.Check the Ethernet communicationsconnections. See previous entry.Check web browser type and version. SeeCompatible Software on page 4.Lost Logon ID and/orPassword.Use DCTools to set up a new Logon IDand/or Password. See Web AccessSecurity on page 96.Default User log on is notavailable.Default User is not setup or not active.Use DCTools to set up a Default User. SeeWeb Access Security on page 96.A user cannot change settings,Backup or Restore, ExecuteCommands, UpgradeFirmware, or Edit User List.Check the user's access levels. See WebAccess Security on page 96.