sock auto sing dp 10a lt shutt

Automatic Single Switch Socket Outlet 250VAC, 10A, Round Earth PIN, with Shutter

Catalogue Number: 10DLS
sock auto sing dp 10a lt shutt
RRP (Inc. GST)
Colour White Electric (WE)
  • White Electric 1 PCE


hide show
Range of product
Standard Series
Product brand
Quantity per set
set of 1
Cover type
full cover plate
without marking
Protection type
Local signalling
without light indicator
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
  • AS/NZS 3100
  • AS/NZS 3112
  • AS/NZS 3133:approval number S/1
    • Unit Type of Package 1
      Number of Units in Package 1
      Package 1 Weight
      82 g
      Package 1 Height
      25 mm
      Package 1 width
      70 mm
      Package 1 Length
      115 mm
      Unit Type of Package 2
      Number of Units in Package 2
      Package 2 Weight
      0.5 kg
      Package 2 Height
      117 mm
      Package 2 width
      102 mm
      Package 2 Length
      138 mm
      Unit Type of Package 3
      Number of Units in Package 3
      Package 3 Weight
      5 kg
      Package 3 Height
      157 mm
      Package 3 width
      305 mm
      Package 3 Length
      445 mm
      Sustainable offer status
      Green Premium product
      EU RoHS Directive
      Mercury free
      RoHS exemption information
      China RoHS Regulation
      Product out of China RoHS scope. Substance declaration for your information
      Environmental Disclosure

      Frequently Asked Questions

      hide show

      Does the Sepam 100LD have communications?

      No, the Sepam 100LD does not have any type of communications.


      Legacy KB System (APS) Data: RESL210681 V1.0, Originally authored by DaFr on 02/15/2013, Last Edited by DaFr on 02/15/2013
      Related ranges: Others protection relays

      How to enable 100ms Frequency monitoring on a CM4000 series meter

      Enabling 100ms frequency monitoring on a CM4000

      Product Line

      High Speed Monitoring

      By default 100ms frequency monitoring is not enabled

      100ms Frequency monitoring is disabled by default on the CM4000 series meters. To enable this feature, the following command writes must be executed to the meter:

      Write 9020 to register 8000
      Write 11 to register 3239
      Write 1 to register 8001
      Write 9021 to register 8000

      This will enable 100ms Frequency monitoring. The value is stored in register 1080 (Units - 0.01 Hz).

      What is the part number for the Input Simulator for a 10DRF Twido Compact Controller?

      The part number is TWDDXSM6

      Legacy KB System (APS) Data: RESL173962 V1.0, Originally authored by on , Last Edited by on
      Related ranges: Twido

      What is the 15 amp version of the 10DWP?

      The 15 amp version of the 10DWP is the 10DWP15.

      For more information, please refer to the link:

      3720ACM responds to every other request in a modbus network

      Goals and Symptoms

      In a Modbus master-slave network, legacy meter responds only to every other request and ignore the others.

      Causes and Fixes

      In Modbus RTU communication topology, messages start with a silent interval of AT LEAST 3.5 characters. This is most easily implemented as a multiple of character times at the baud rate that is being used on the network. In legacy Power Measurement meters, depending on the network, the silent interval may exceed 3.5 characters. On a healthy network with baud rate 9600 this gap should be equal to ~3ms, which is too fast for the legacy devices to catch. On a newer network like this any message sent will hit the silent interval on the 3720, so the meter will not respond. However, the following request will be received after enough silent duration and the meter will respond. This will carry on so the meter will only respond to every other request.
      Adjusting the RTS (Request To Send) interval greater than 100ms (or longer) on the master side will enable the meter to catch all the request packages sent to the network. This adjustment will manipulate the master to hold 100 ms in between every request which will give enough time to the legacy meters.

      Last Revised: April 10, 2008
      Applies To: 3720 ACM
      Original Author: KG
      All content © 1992-2008 Schneider Electric

      Legacy KB System (APS) Data: RESL191660 V1.0, Originally authored by KBAdPM on 04/11/2008, Last Edited by KBAdPM on 04/11/2008
      Related ranges: 3720 ACM

      SEPAM series 80 with MES120 Normally Closed Input trips upon loss of supply power

      Goals and Symptoms


      • Configuration : Sepam series 80 using a MES120 digital input set as tripping order and normally closed contact (negative case is ticked off )
      • Sepam trips when auxiliairy power supply interrupted.
      • After clearing trip on Sepam, the Sepam units comes to normal operating condition without changing the state of input .

      Facts and Changes

      Key Words and Phrases
      Input state change from loss of supply power, loss of supply power triggers state change,ride-through power, delayed power loss, delayed power cycle

      Causes and Fixes

      This will append when digital inputs and Sepam base unit share the same power supply.
      Because the Sepam unit has an enough ride-through energy reserved to allow for momentary outages of up to 100ms without power cycling, the Sepam will detect the logical input falling down to zero due to power loss before losing its own energization. This functionning is quite normal if no precautions are taken to prevent it .

      Note : Sepam series 20 and 40 don't show that behaviour because they have a faster shut down.


      As a precaution against this behavior, it is suggested to :

      - if application makes it possible, delay the tripping of normally closed contact inputs via logical equation for 200ms

      - if delay is not applicable, use another input as "presence of voltage" and combine it with logical equation.

      For example :
      I105 = external trip NC
      I106 = presence of voltage
      equations : LATCH VL1 (optional)
      V1 = I105 AND I106
      V_TRIPCB = V1
      Link a message like "external trip" to V1

      - otherwise, to avoid trip at voluntary shut down, add a warning near the auxiliairy circuit breaker.

      Re-published to revised security level: 20 June 2008 by DRM

      Applies To: Sepam 80


      All content © 1992-2008 Schneider Electric

      Legacy KB System (APS) Data: RESL177113 V2.0, Originally authored by KBAdPM on 11/05/2007, Last Edited by DaMi on 06/21/2008
      Related ranges: Sepam series 80

      Planning Your StruxureWare Power Monitoring 7.0 Upgrade

      This article provides links to upgrade documentation, recommendations and Frequently Asked Questions. This article will also be updated updated frequently with the latest upgrade information.

      Consider the following upgrade recommendations to minimize required storage space and reduce system downtime.

      • *
        Ensure you have enough hard drive space available on your database server
        Have an external hard drive available for storing database upgrade backup files
        Plan an ION-Enterprise system downtime window
        Consider archiving data (with Trim) to reduce system downtime

      Upgrade Documentation
      Read these documents before upgrading your software.
      Determine Your Upgrade Type (RESL#207578)
      Read the Database Upgrade FAQ (RESL#206536)
      Consult the relevant upgrade guide(s):
      In-Place Upgrade Guide (RESL#207603)
      Side-By-Side Upgrade Guide (RESL#207604)
      SQL Server 2005 Express Edition Upgrade Guide (RESL#207643)
      SQL Server 2005 Standard Edition Upgrade Guide (RESL#207632)
      SMS Migration
      The migration from PowerLogic SMS to StruxureWare Power Monitoring 7.0 is a specialized upgrade path. Please contact technical support for more information on an SMS migration.

      New Software Install
      If you're installing a new StruxureWare Power Monitoring 7.0 system, this guidance does not apply. Consult StruxureWare Power Monitoring 7.0 Installation Guide (7EN02-0308-00).

      Known Issues
      Articles related to issues with upgrading your software to StruxureWare Power Monitoring 7.0 are listed below.
      SPM 7.0 - Error while installing Report Packs from previous versions
      StruxureWare Power Monitoring 7.0: Database Manager - alarm functionality removed
      StruxureWare Power Monitoring 7.0: Installer fails at 'check 64-bit server' step
      StruxureWare Power Monitoring 7.0: Side By Side upgrade - reports missing after restore
      StruxureWare Power Monitoring 7.0: why do saved reports show different results after the upgrade?
      StruxureWare Power Monitoring 7.0: Upgrade fails at 'Configure SQL' step
      StruxureWare Power Monitoring 7.0: 100ms report - saved measurement selector empty after upgrade
      StruxureWare Power Monitoring 7.0: where do I find the most recent version of the SBS Upgrade Utility
      StruxureWare Power Monitoring 7.0: The SBS Upg Utility fails on 'Restore Config Folder'
      StruxureWare Power Monitoring 7.0: Migrating saved/custom reports when using the SBS Upgrade Utility

      Legacy KB System (APS) Data: RESL204865 V7.0, Originally authored by JaMc on 03/19/2011, Last Edited by JaMc on 05/17/2012
      Related ranges: Power Monitoring 7.0

      Performance Effects of 10Mb/s vs. 100 Mb/s on Ethernet cable from a NOE Module to the Switch

      Goals and Symptoms

      This document will outline factors related to performance including, PLC CPU scan time, Modbus data types and Ethernet Line bandwidth. It will become apparent that in an automation network the speed of the wire is not the hindering factor when it comes to performance.

      Facts and Changes

      Quantum Platform, SCADA system, 10/100 MB Ethernet cables, Unity Pro, Concept, Proworx NxT, Proworx 32

      Causes and Fixes

      The number of Modbus requests serviced by the NOE module will vary by the NOE module Exec version and the CPU that it is attached to. But in a maximum case the module can service 12 Modbus requests per PLC scan.
      In the example below, we calculate the time it takes to send 1 Modbus query to read 100 holding registers (4x) and receive 1 Modbus response to that query on a 10 Mbs Ethernet link.

      As a reminder, in this resolution the actual Ethernet cables speed is
      At 10 Mb/s transfer rate it can carry 10 * 1,000,000 = 10,000,000 bits/second
      At 100 Mb/s data transfer rate, it can carry 100 * 1,000,000 = 100,000,000 bits/second

      Modbus query of reading 100 4x holding registers is 82 bytes
      MAC 18 bytes (6 Destination MAC, 6 Source MAC, 2 Ether type, 4 FCS)
      IP Header 20 bytes
      TCP Header 20 bytes
      MB Header 7 bytes (2 XID, 2 Protocol version, 2 length, 1 unit ID,)
      MB PDU 5 bytes (1 byte function code, 2 start reference, 2 no of words to read)
      IPG 12 bytes
      Query Total 82 bytes
      656 bits of data

      On a 10 Mb/s link 656 bits/10,000,000 bits/s = 0.0656 ms
      On a 100 Mb/s link 656 bits/100,000,000 bits/s = 0.00656 ms

      Sending 12 of such messages on a 10 Mb/s link will only take about 0.7872 ms and the same message sent on a 100 Mb link will take 0.07872 ms. As you can see the time difference is insignificant when compared to the actual CPU scan.

      Modbus response to that query is 279 bytes
      MAC 18 bytes (6 Destination MAC, 6 Source MAC, 2 Ether type, 4 FCS)
      IP 20 bytes
      TCP 20 bytes
      MB Header 7 bytes (2 XID, 2 Protocol version, 2 length, 1 unit ID,)
      MB PDU 202 bytes (1 function code, 1 byte count, 100 words response data)
      IPG 12 bytes
      Response Total 279 bytes
      2232 bits

      On a 10 Mb/s link 2232 bits/10,000,000 = 0.2232 ms
      On a 100 Mb/s link 2232 bits/100,000,000 = 0.02232 ms

      Note: Message size does have bearing on overall transmission time and it takes longer to transmit the response than to send a query.

      Sending 12 of such message on a 10 Mb/s link will take 2.6784 ms and the same message sent on a 100 Mb/s link will take 0.26784 ms.

      For an average CPU you will have a 35 ms scan time. Therefore any delay to link speed being either 10 MB or 100 MB is reasonably insignificant compare to CPU scan.

      Application Example for Network utilization:

      In this example the CPU is executing 10 Modbus Query/Response transactions as outlined above to simulate IO Scanning 100 registers at a 100ms Repetition Rate.

      0.000656 % TX Load @ 10 Mbs
      0.002232 % RX Load @ 10 Mbs

      0.0000656 % TX Load @ 100 Mbs
      0.0002232 % RX Load @ 100 Mbs

      The link speed comparison is insignificant on Application Response Time compared to other factors:

      o CPU scan
      o Datatypes requested (4x register vs. none 4x)
      o Half duplex operation
      o Slave device response time delay

      Note: Half duplex can be a significant factor at either 10 or 100 Mb/s due to collisions which will result in communication delays. Typically devices operating at 10 Mb are usually operating at half duplex and therefore subject to collision.

      I/O Scanner
      I/O Scanner messages are serviced at the end of CPU scan. Each IO Scanner entry requires 0.3 ms to process. IO Scanners response time also depends on the response time of the remote device being IO Scanned.

      For example one I/O scanner entry that reads/writes 10 words (~115 bytes or 920 bits) takes approximately 0.092 ms to send on 10 Mbs link, versus 0.0092 ms to process on a 100 Mbs link. The actual time difference related to the connection speed in this example is less than 1 millisecond at 0.0828 ms.

      In summary the CPU scan and remote devices response time have more impact on I/O Scanner response time than the link speed. Regardless of the link speed the difference is minute.

      Legacy KB System (APS) Data: RESL181788 V2.0, Originally authored by BeCh on 01/27/2007, Last Edited by BeCh on 02/06/2007
      Related ranges: Modicon Quantum NOE - TR