Automatic Single Socket Outlet, 250VAC, 10A, 1 Pole

White Electric | Automatic Single Socket Outlet, 250VAC, 10A, 1 Pole

Automatic Single Socket Outlet, 250VAC, 10A, 1 Pole

Item Number: 10-WE



Qty UoM EAN Colour



Range of product

Standard Series

Product or component type


Product brand


Sustainable offer status

Green Premium product


Quantity per set

set of 1


without marking

Local signalling

without light indicator

Device mounting


Fixing mode

by screws

[In] rated current

10 A

[Ue] rated operational voltage

250 V AC


16 mm


115 mm


73 mm

Fixing center

84 mm

Number of poles



  • AS/NZS 3100
  • AS/NZS 3112
  • AS/NZS 3133:approval number S/1

REACh Regulation

Reference contains Substances of Very High Concern above the threshold

EU RoHS Directive


Mercury free


China RoHS Regulation

Product out of China RoHS scope. Substance declaration for your information

RoHS exemption information


Environmental Disclosure



Package 1 Bare Product Quantity


Cover type

full cover plate

Unit Type of Package 1


Number of Units in Package 1


Package 1 Height

3 cm

Package 1 Width

7 cm

Package 1 Length

11.2 cm

Package 1 Weight

74 g

Unit Type of Package 2


Number of Units in Package 2


Package 2 Height

10.6 cm

Package 2 Width

12.2 cm

Package 2 Length

14.2 cm

Package 2 Weight

438 g

Unit Type of Package 3


Number of Units in Package 3


Package 3 Height

25.4 cm

Package 3 Width

34.8 cm

Package 3 Length

44.5 cm

Package 3 Weight

9.1 kg
Show all specifications

Documents & downloads

hide show
Filter items
  • All

  • Technical Data Catalogues

Frequently Asked Questions

hide show

Common issues found in ClearSCADA Mobile

This article goes over some common issues that one might encounter when configuring ClearSCADA Mobile and provides some basic steps to troubleshoot these issues. In addition, please familiarize yourself with ClearSCADA Mobile system requirements  to make sure your ClearSCADA Mobile runs in the  supported environment.

Connection to ClearSCADA Mobile times out or an internal error reported:

This may be caused by the following issues:

1. The mobile device is not on the same network or routing is not implemented/configured correctly. One could check the Internet Information Server (IIS) log files which are usually located in "C:\inetpub\logs\LogFiles". The IIS logs should record connection attempts similar to below with timestamp in UTC if the mobile device is able to reach Mobile Server. Due to the way the IIS logs operate, new entries might be delayed for up to a few minutes.

2015-10-29 15:09:40 GET /mobile/service.svc/v1/..................

To resolve this issue, make sure that mobile devices are connected to the same network as ClearSCADA Mobile if no routing is implemented. If there is routing in place, check the configuration of the router(s).

2. Incorrect connection information is provided. Make sure the connection information the mobile device is configured to follow the general format below. Depending on the situation, one either needs to specify the IP address/Name and the port of the server running ClearSCADA Mobile or the IP address/Name and the port of the router.

  • <server IP or server name or URL>:port 

3. Communication ports get blocked by a firewall. Make sure the ClearSCADA Mobile port and the listening port between ClearSCADA Mobile and ClearSCADA Mobile Companion Server are both configured to allow communication. To find out what ports ClearSCADA Mobile uses check the following:

  • Launch Internet Information Services (IIS) Manager on the machine hosting ClearSCADA Mobile, select ClearScadaMobile site (ClearSCADA if using ClearSCADA 2015 R1) and click on Bindings. The HTTPS port displayed in Bindings is being used for communication between mobile devices and ClearSCADA Mobile. The default port is 443 in all versions of ClearSCADA except for ClearSCADA 2015 R1. It is port 453 in ClearSCADA 2015 R1.
  • Right click on the ClearSCADA Server Icon found on the machine hosting ClearSCADA Server itself, navigate to Configuration -> System Configuration -> Mobile and locate Port. This port is being used for communication between ClearSCADA Mobile and ClearSCADA Mobile Companion Server. The default port is 8008.

4. The ClearScadaMobile web-site is not running on the server. Launch Internet Information Services (IIS) Manager and make sure the ClearScadaMobile site is running as shown below.

5. Check whether the "ClearSCADA Mobile Settings Service"  (named "ClearSCADA Mobile Server" in ClearSCADA 2014 and 2013, and "ClearSCADA Web and Mobile Settings Service" in ClearSCADA 2015 R1) service is running on the machine hosting ClearSCADA Mobile. In addition, make sure the "ClearSCADA Mobile Companion Server" service is running on the machine hosting ClearSCADA Server. If ClearSCADA Mobile and ClearSCADA Server run on the same machine, both services should be present on it.

6. HTTP Activation is not installed as a part of WCF Services as per below. 

ClearSCADA Mobile Connection Port used by another application:

An issue will arise when ClearSCADA Mobile is configured to use the same port that is already in use by another application. The default connection port for ClearScadaMobile is 443 in all versions of ClearSCADA except for ClearSCADA 2015 R1. It is port 453 in ClearSCADA 2015 R1. To check what port ClearSCADA Mobile is configured to, launch the Internet Information Services (IIS) Manager, select ClearScadaMobile site (it is called ClearSCADA in ClearSCADA 2015 R1), click Bindings and see what port is specified for HTTPS connections. If the port configured for the HTTPS connection is being used by another application, change the HTTPS port for ClearSCADA Mobile to a vacant port. Once the change to the port is made, the ClearScadaMobile site needs to be restarted. There might also be a need to reconfigure the SSL certificate for the newly assigned HTTPS port.

Mobile User not created in the ClearSCADA database:

Make sure that users configured in ClearSCADA Mobile have also been configured in the ClearSCADA database - the user names are case sensitive and must be match. Otherwise, users will not be able to access the ClearSCADA database when logging in through ClearSCADA Mobile.

Mismatch in System Name:

Make sure that the same System is specified in ClearSCADA Mobile Configurator and in "Server Configuration -> System Configuration -> Mobile".

Mobile Companion Server not installed (does not apply to ClearSCADA 2015 R1):

ClearSCADA Mobile Companion Server must be installed separately from ClearSCADA Mobile except for ClearSCADA 2015 R1. ClearSCADA Mobile Companion Server must be installed on the machine hosting the ClearSCADA database which might or might not be the same machine hosting ClearSCADA Mobile. To install ClearSCADA Mobile Companion Server, run ClearSCADA Installer and select "Install ClearSCADA" as opposed to "Install ClearSCADA Mobile". Select "Modify" and locate "Mobile Companion" under "Server" group. Continue with the installation process. Once the installation is completed, check to see if the ClearSCADA Mobile Companion Server service is running.

Configuration Mismatch in Listening Ports (applies to ClearSCADA 2013 and 2014 only):

It is possible that ClearSCADA Mobile and ClearSCADA Mobile Companion Server are configured to different listening ports which results in no communication between the two. The listening port of Mobile Companion can be checked from "ClearSCADA Configuration -> System Configuration -> Mobile -> Port".

The listening port configured in ClearSCADA Mobile can be checked as well. Go to ClearSCADA Mobile installation folder - the default directory is "C:\Program Files\Schneider Electric\ClearSCADA Mobile", go into "Server" and open up ClearScadaMobileServer.exe (with Notepad for example):

How to locate Schneider North America Dual Technology (Passive Infrared and Ultrasonic) Line Voltage Ceiling Mount Occupancy Sensor documentation?

When searching for Schneider Electric North America Dual Technology Ceiling Mounted Line Voltage Occupancy Sensor products documentation for a new or existing installation, assistance is available using online tools and local authorized distributors.

Product Line:
Schneider Electric North America  Dual Technology Ceiling Mounted  Line Voltage  Occupancy Sensor (SLSCLD2000) products

Schneider Electric North America Ceiling Mounted Line Voltage Occupancy Sensor (SLSCLD2000) products sold in the United States

Selecting the correct Dual Technology Ceiling Mounted Line Voltage Occupancy Sensor (SLSCLD2000) product documentation for a new and existing installation involves many factors. Both online and phone assistance are available to help you.

For help when searching for Dual Technology Ceiling Mounted Line Voltage Occupancy Sensor (SLSCLD2000) products documentation, use the following links:

Also Note: As of March 1, 2015 all US Lighting Control products (EXCEPT Powerlink and MVP panels) will enter their obsolescence phase and will no longer be purchasable for new orders. Management of the Prosumer Business has made a strategic decision to stop the Lighting Control initiative and concentrate our effort in new businesses with higher growth potential – Connected Home, Building Control in small buildings, and Electric Vehicle solutions. See FA241002 for details.

(1) Our Product web site, at this link.

(2) Our Online Digest, at this link, shows specific catalog numbers of many of our products.

(2a) Our Lighting Control section of the Online Digest, at this link, shows specific catalog number of our Lighting Control products.

(3) Further assistance is available from a local authorized Schneider Electric Distributor, using our Distributor Locator at the below link:

All the above tools may be found by visiting our US Home Page.

Video: How to recover the system on the HMIGTU Series?

Video: How to recover the system on the Harmony/Magelis HMIGTU Series?
Product Line:
The goal of this resolution is to provide the system recovery resource that can be used to backup and recover the Harmony/Magelis HMIG3U, HMIG3X, HMIG5U, HMIG5U2, and HMIG5U22. All the HMIGTU (except HMIG2U) series have their firmware stored on a System CFast or System SD Card.
1) Power off the HMIGTU.
2) Remove the System CFast or System SD card from the HMIGTU (this SD card slot is labeled "SYSTEM CARD" on the outer casing of the HMI).
3) Insert the CFast or System SD into a CFast (Type 1.0) or SD Card Reader on your office PC.
4) Launch the Backup Recovery Tool (BackupRecovery.exe).
5) In the "File Name" field, choose the recovery image file (.bin) for your type of HMIGTU.
6) Select the Drive Letter from the dropdown list to match that of your CFCard or SD Card that you inserted.
7) Click "Recovery" and then [Yes] when you are prompted to continue this process
8) The .bin image will be written to the CFast or SD card. Please wait and do not remove the CFast or SD Card during this time.
9) Once the process is done, a message will appear "Quit he application, and eject the disk from the PC."
10) Eject the CFast or SD card from your PC
11) Insert it back into the HMIGTU's system slot (the one close to the screen-mount side)
12) Power on the HMIGTU as per normal.
Attached are:
Backup Recovery Tool - "BackupRecovery.exe"
Backup Recovery User Manual - "Backup Recovery User Manual.pdf"
Pre-made image for HMIG3U saved in Vijeo Designer 6.2 SP8 - "HMIG3U.bin"
Pre-made image for HMIG3X saved in Vijeo Designer 6.2 SP9 - "HMIG3X.bin"
NOTE: HMIG5U, HMIG5U2, and HMIG5U22 images are too large to upload. Please contact support at to ask for a direct download ticket link.


Schneider Electric's Technical Support Policy for Older Versions of PowerChute Software

What is Schneider Electric software support policy?

Product Lines:
PowerChute Network Shutdown (PCNS),
PowerChute Business Edition (PCBE),
PowerChute Personal Edition (PCPE),
PowerChute Plus (PC+)

All supported OS


When new versions of software are released, Schneider Electric will continue to provide full technical support to customers for the previous version for a minimum of 1 year after the new version is released. In practice, Schneider Electric typically goes far beyond this stated commitment, but this 1-year policy is stated here so customers may take it into account for planning purposes.
  • The current shipping version of PowerChute Network Shutdown is 4.4.x It was release October 2020
    • NOTE: support is continuing for PCNS 4.2 for 32 bit systems, and PCNS v4.3 for 64-bit systems.
  • The current shipping version of PowerChute Business Edition is 10.0.5 It was release February 2022
    • NOTE: support is continuing for PCBE 9.5 for 32 bit systems. 
  • The current shipping version of PowerChute personal Edition is 3.1 It was release June 2019 
  • PowerChute Plus was discontinued March 2007

Video: How to Configure an automated Energy Reset on an ION meter

A user would like to configure an ION meter to reset energy values automatically every month.

Product Line
ION Meters
PM8000 series meter

ION Setup v3.0

ION meters do not automatically reset energy values by default.

*Warning: The following procedure contains customization of a device template. Take a backup of the current template prior to customization.

The following procedure details how to program the meter in ION Setup to reset energy values monthly:
  1. Add the device in ION Setup
  2. Right-click on the device > Properties > Tools > Select Show Advanced ION Setup
  1. Double click on Integrator Modules

  1. Select kWh del
*Warning: Modifications to inputs and/or setup registers of the Integrator Modules will reset recorded data. Please ensure that all necessary information has been recorded prior to making any changes.
  1. Identify the location of the Reset pulse (For ION8650: Nrm Egy Reset), after localization “Cancel” to close here, then navigate to the Pulse Merge Modules .

  1. Navigate to the Pulse Merge Modules
  1. Double-click on the module corresponding to the Reset pulse (Module Name: Module Merger # - Label: Nrm Egy Reset)
  2. If prompted password requests, type “0” by default
  3. Click on Pulse In 2 and select Edit
  1. In the ION Input Selection: Pulse In 2 windows, navigate to Clock Modules > Clock 1 > CL1 New Month.

  1. Click on Ok and Send the change to the device

How do I configure my RADIUS server to authenticate my APC Network Enabled device?


RADIUS set up with APC Network Management Card enabled products.

Product Line

  • Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619

Devices with an embedded Network Management Card 1 include (but are not limited to): Metered/Switched Rack PDUs (AP78XX, AP79XX), Rack ATS (AP77XX, Environmental Monitoring Units (AP9320, AP9340, Netbotz 200)

  • Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH

Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP84xx, AP86XX, AP88XX, AP89XX), Rack ATS (AP44xx), Certain SmartUPS online (SRT) Certain Audio/Video Network Management Enabled products.

  • ​​​​​​​Network Management Card 3 (NMC3) - AP9640/AP9641/AP9643

Devices with an embedded Network Management Card 3 include (but are not limited to): Certain 2G Metered/Switched RackPDU's manufactured after 2021 (AP84xx, AP86xx, AP88xx, AP89xx), APDU9XXX RackPDU's, RackATS (AP44xxA), Certain SmartUPS online (SRT)

  • Network Management Card 4 (NMC4) - AP9644
​​​​​​​The Network Management Card 4 is supported on the Galaxy VS, Galaxy VL, and Galaxy PX units. These units also include a built-in network management card.

  • All serial numbers
  • Firmware versions v2.X.X and higher


Configuration can vary based on the RADIUS server being used. Below is a successful configuration taken from a FreeRADIUS server. Though this configuration worked through testing, APC by Schneider Electric cannot guarantee that this configuration will work on your RADIUS server. Configuring of your RADIUS server should be provided by your RADIUS server administrator.

Note: Further information on using the specific variety of FreeRADIUS (v2.1.10) included in Zentyal Linux 3.3 is also available in knowledge base article ID FA232648.


The three files that need to be edited in order for FreeRADIUS to authenticate properly are:

1) clients.conf
2) dictionary
3) users file

Below are examples of entries that should be entered into each file.

1) clients.conf

client (you would enter the IP address or IP address range of devices authenticating through RADIUS)
secret = radius
shortname = apc

2) dictionary



ATTRIBUTE APC-Service-Type 1 integer APC

VALUE APC-Service-Type Admin 1
VALUE APC-Service-Type Device 2
VALUE APC-Service-Type ReadOnly 3

3) users

# APC local radius authentication (working)
apcradius (username) Auth-Type := Local, User-Password == "apcradius"
     APC-Service-Type = 1

Once these entries are made, you should be able to access your APC product via RADIUS authentication.

In some cases, you do need to specify Vendor Specific Attributes. For example, APC part number AP7900 (Switched Rack PDU) uses the same login accounts as listed in the previous example. However, the AP7900 also allows specific outlets to have their own separate accounts/logins. Therefore, you must create additional entries in the event that a user has a login for specific outlets.

1) clients.conf

client {IP address or IP address range of devices using RADIUS authentication}
secret = radius
shortname = ap7900

2) dictionary



ATTRIBUTE APC-Service-Type 1 integer APC
ATTRIBUTE APC-Outlets 2 string APC

VALUE APC-Service-Type Admin 1
VALUE APC-Service-Type Device 2
VALUE APC-Service-Type ReadOnly 3
VALUE APC-Service-Type Outlet 4

3) users

VSAAdmin Auth-Type = Local, Password = "admin"
     APC-Service-Type = Admin

VSADevice Auth-Type = Local, Password = "device"
     APC-Service-Type = Device

VSAReadOnly Auth-Type = Local, Password = "readonly"
     APC-Service-Type = ReadOnly

userA Auth-Type = Local, Password = "apc"
     APC-Service-Type = Outlet, APC-Outlets = "1,3,5"

userB Auth-Type = Local, Password = "apc"
     APC-Service-Type = Outlet, APC-Outlets = "1,2,3,4,5,6,7,8"

UserA will now have access to outlets 1,3,5 and userB will have access to outlets 1,2,3,4,5,6,7,8.

RADIUS and Network Port Sharing with Switched Rack PDU 2G (AP86XX, AP89XX)

Note: See the Security Handbook for APC Network Management Cards for more information on using RADIUS.

For RADIUS users file with VSAs, outlets on guest Rack PDUs can be associated to RADIUS users by using the following method.

# give user access to outlets 1, 2, and 3 on PDU 1,
# outlet 7 on PDU 2, outlets 1 through 6
# on PDU 3, and outlets 1,2,4 through 6, 7 through 10,
# and 20 on PDU 4

newOutletUser Auth-Type = Local, User-Password = "newoutlets"
APC-Service-Type = Outlet,
APC-Outlets = "1[1,2,3];2[7];3[1-6];4[1,2,4-6,7-10,20];"

If you have trouble configuring your RADIUS server, it is advised that you contact your RADIUS server vendor for assistance.

NOTE: To create a "network only" user for supported AOS files, the following line must be added to the dictionary file: VALUE APC-Service-Type NetworkOnly 6

Show More