Socket Outlets Single Switch Horizontal, 250V, 10A

White Electric | Socket Outlets Single Switch Horizontal, 250V, 10A

Socket Outlets Single Switch Horizontal, 250V, 10A

Item Number: 2015-WE

Datasheet

Specifications

Design

Range of product

Series 2000

Product or component type

switched socket

Product brand

Clipsal

Surface finish

glossy

Sustainable offer status

Green Premium product

Physical

Control type

ON/OFF button

Number of gangs

1 gang

Pin number

3

Number of power socket outlets

1

Actuator

  • switch
  • rocker
    • Mounting position

      horizontal

      Fixing mode

      by screws

      Local signalling

      without light indicator

      [Ue] rated operational voltage

      250 V AC

      [In] rated current

      10 A

      Depth

      30 mm

      Length

      116 mm

      Width

      76 mm

      Fixing center

      84 mm

      Standards

    • AS/NZS 3100
    • AS/NZS 3112
    • AS/NZS 3133
      • Product certifications

        RCM

        REACh Regulation

        Reference contains Substances of Very High Concern above the threshold

        EU RoHS Directive

        Compliant

        Mercury free

        Yes

        RoHS exemption information

        Yes

        China RoHS Regulation

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

        Environmental Disclosure

        ENVPEP120506EN

        Material

        Material

        plastic

        Others

        Unit Type of Package 1

        PCE

        Number of Units in Package 1

        1

        Package 1 Weight

        30 g

        Package 1 Height

        33 mm

        Package 1 width

        84 mm

        Package 1 Length

        132 mm
        Show all specifications

        Frequently Asked Questions

        hide show

        ETL task not working when running as a service

        SUMMARY

        When creating the ETL task the "Run Once" works, but when configured to run as a service, it doesn't work and an error occurs.

         

        Here is an example of what you will see in the error log:

        2015-05-22 17:13:59,069 ERROR ETLEngine (TaskName) - Thread ID (119) - Power Monitoring Expert Load Task: Task Power Monitoring Expert Load Task failed

        System.ApplicationException: Failed to populate the MetaDataSet. ---> System.Data.SqlClient.SqlException: Cannot open database "ION_Data" requested by the login. The login failed.

        Login failed for user 'NT AUTHORITY\SYSTEM'.

         

        SITUATION

        ETL

        Power Monitoring Expert

         

        SYMPTOMS

        1. When testing the ETL task using "Run Once", the Windows account you are currently logged in with will be used to access the SQL database. When the task is then configured to run as a service, the account configured on the service will be used. By default that account is the built-in account 'NT AUTHORITY\SYSTEM'.
        2. The Position values for all of the mapped trend logs are set to an unreasonable timestamp. The timestamp is either very old of a data the proceeds the oldest values in the database. 

         

        ACTION

        Changing the Windows system account for the ETL service

        You can either give the system account access to the database, or you can change the account used to run the service.

         

         

        Correct/Adjust the timestamp values in Positions tab of ETL

        The timestamps can be changed all at once by setting the Intital value field at the top of the "Positions" window in the ETL tool. 

         

         

        eXL Hoist Change - 20154

        Issue:
        Is there any difference between the older generation and newer generation of the eXL Hoist controllers?

        Product Line:
        Wireless Joysticks - GIC Product

        Environment:
        US Product

        Cause:
        Product Characteristics

        Resolution:
        The eXL Hoist system was changed in late 2015 to incorporate a better battery than the older design.  Besides this change, there is no functional difference between the units.

        Is mech removable in part number 2015X?

        Yes, the mech in part number 2015X is removable.

        For more information on this part please refer to https://www.clipsal.com/Trade/Products/ProductDetail?catno=2015X


        User-added image

        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 192.168.159.149 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):

        Is there a C2015s with built in surge filter?

        No, we dont sell one complete, you would have to get a C2015XS take out the extra switch and put in a 30SFM.

        How to Use Local Time in SCADAPack E RTU Logic Applications

        Overview

        The SCADAPack E RTU can operate using UTC or Standard Time in the RTU Real Time Clock. When using the DNP3 protocol, UTC time is the recommended industry practice. When using UTC time, some logic applications may require local time and/or daylight savings time. The SCADAPack E RTU has the ability to display local time and control if daylight savings time needs to be applied

        SCADAPack E Configuration

        UTC & Standard Time

        When UTC Time is set in the SCADAPack E RTU real time clock, the Time Offset from UTC system point (float system point 63201) should be set appropriately (as per the installation of the RTU). Where Standard Time is set in the RTU real time clock, the Time Offset from UTC should be set to zero.

        The Time Offsett from UTC system point 63201 can be found on the General -> Controller Settings property page of SCADAPack E Configurator.

        Summer Time

        If summer time activities are required, it is not necessary to adjust the RTU Real Time Clock. Rather, the Time Zone Modifier system point (binary system point 50302) can be activated. This system point is also known as Apply Daylight Savings point. Setting this point is the responsibility of the SCADA Master or a combination of information from the SCADA Master and a user-created logic program.

        The Time Zone Modifier selects summer time on the RTU when the binary system point is active. The RTU immediately adjusts for summer time upon receiving a control message from the SCADA Master to set the point.

        When Summer Time is selected, certain RTU facilities receive local information from the RTU based on Standard Time + 1.0 Hours. When summer time is not selected, these facilities receive standard time.

        Example


        In the example below the RTU is located in Ottawa, Canada. The date is September 30th, 2015 UTC time is 8:14pm. Daylight Savings time is enforced, thus binary point 50302 is enabled from the SCADA Host. The Configuration is set to have a UTC time offset of -5. The TIMEDATE block in SCADAPack Workbench CAM5 will return the local time values. DNP3 events are still generated using UTC time, the SCADA host is configured for UTC time, yet logic can execute using local time. The adjustment of daylight savings time is facilitated using binary output point 50302 twice a year.


        Time Presentation


        Except where noted below, RTU facilities use UTC or Standard time (e.g. RTU Real Time Clock, Trends, and DNP3 Time-stamps).

        Summer Time (Daylight Savings) corrected time only affects RTU sub-systems that use Local Time. The following table indicates which SCADAPack E RTU facilities use Local times (UTC offset and Daylight Savings / Summer time adjusted) or UTC / Standard (Summer time independent) times.

        RTU Facilities Using UTC or STANDARD Time
        (Independent of Summer Time
        RTU Facilities Using LOCAL Time
        (Adjusted for UTC offset and Daylight Savings Time)
        RTU Real Time ClockProfiler Task
        Trend sample time-stampsISaGRAF TIMEDATE Function Block
        DNP3, IEC60870-5 protocol event time-stampsISaGRAF LOC_TIME Function Block
        ISaGRAF OS_TIME FunctionISaGRAF DAY_TIME Function
        Times shown in RTU diagnostics 

        More Examples

        Example 1 – SCADAPack E RTU clock set to UTC time, Daylight Savings not applied
        UTC Time = 11:15:10.5
        Time Offset to UTC = 10.0 hours
        Apply Daylight Savings = NO
        · Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
        · ISaGRAF OS_TIME returns seconds since Jan 1, 1970 UTC
        · Profiler control time = 21:15:10.5
        · ISaGRAF LOC_TIME & TIMEDATE function block indicates 21:15:10
        · ISaGRAF DAY_TIME function indicates 21:15:10
        Example 2 – SCADAPack E RTU clock set to UTC time, Daylight Savings applied
        UTC Time = 11:15:10.5
        Time Offset to UTC = 10.0 hours
        Apply Daylight Savings = YES
        · Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
        · ISaGRAF OS_TIME function returns seconds since Jan 1, 1970 UTC
        · Profiler control time = 22:15:10.5
        · ISaGRAF LOC_TIME & TIMEDATE function block indicates 22:15:10
        · ISaGRAF DAY_TIME function indicates 22:15:10
        Example 3 – SCADAPack E RTU clock set to Standard time, Daylight Savings not applied
        RTU Time = 11:15:10.5
        Time Offset to UTC = 0.0 hours
        Apply Daylight Savings = NO
        · Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
        · ISaGRAF OS_TIME returns seconds to 11:15:10 since Jan 1, 1970 standard time
        · Profiler control time = 11:15:10.5
        · ISaGRAF LOC_TIME & TIMEDATE function block indicates 11:15:10
        · ISaGRAF DAY_TIME function indicates 11:15:10
        Example 4 – SCADAPack E RTU clock set to Standard time, Daylight Savings applied
        RTU Time = 11:15:10.5
        Time Offset to UTC = 0.0 hours
        Apply Daylight Savings = YES
        · Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
        · ISaGRAF OS_TIME returns seconds to 11:15:10 since Jan 1, 1970 standard time
        · Profiler control time = 12:15:10.5
        · ISaGRAF LOC_TIME & TIMEDATE function block indicates 12:15:10
        · ISaGRAF DAY_TIME function indicates 12:15:10

        More Details

        To read more about UTC Time vs. Standard time in SCADAPack E, please consult the Reference Manual which may be selected from the Help menu of the E Configurator.

         
        Show More