MASTER YOUR CASTLE with your new build or reno project
Enter competition
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
soc swt auto sing 10a 250v
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
soc swt auto sing 10a 250v
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V

2010

Automatic Single Socket Outlet, 250VAC, 10A

SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
soc swt auto sing 10a 250v
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
soc swt auto sing 10a 250v
SOCKET SWITCHED AUTO SWITCHED SINGLE 10A 250V
Colour: White Electric
Colour: Per UOM Std.
  • Black 1 PCE
  • Cream 1 PCE
  • White Electric 1 PCE
Added to cart
Successfully added, you can view your cart here

Key Features & Specifications

hide show
Range of product
Series 2000
Product brand
Clipsal
Quantity per set
set of 1
Cover type
full cover plate
Marking
without marking
Local signalling
without light indicator
Device mounting
flush
Fixing mode
by screws
Material
PVC (polyvinyl chloride)
Surface finish
glossy
[In] rated current
10 A
[Ue] rated operational voltage
250 V AC
Depth
31 mm
Length
116 mm
Width
76 mm
Fixing center
84 mm
Number of poles
1
Standards
  • AS/NZS 3100
  • AS/NZS 3112
  • AS/NZS 3133
  • AS/NZS 3000:approval number S/1
    • 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
      Circularity Profile
      N/A

      Documents & downloads

      hide show
      Filter items
      • All

      • Product Brochures

      • CAD Files and Packs

      • Technical Data Catalogues

      • Installation Instruction

      • Product Environmental

      • Operating Manuals

      • Specifications

      • Certificates (MSDS)

      Frequently Asked Questions

      hide show

      Is there an auto switched, single GPO in the 2000 series?

      Yes, we have the 2010 which is an auto switched, single GPO in the 2000 series.

      For more information, please refer to the link:
      https://www.clipsal.com/Trade/Products/ProductDetail?catno=2010 



       

      Was the NetShelter SX AR33xx roof redesigned in 2010?

      Issue:
      Newer NetShelter SX AR33xx cabinets have a different roof than older models.

      Product Line:
      NetShelter SX
       
      Environment:
      All versions and serial ranges.
       
      Cause:
      In 2010 the roof of the NetShelter SX AR33xx cabinets were redesigned to allow more room for cable access.
       
      Resolution:
      See attached file

      Is the PowerLogic BCPM (Branch Circuit Power Meter) compatible with NQ and NF panels?

      Issue
      Is the PowerLogic BCPM (Branch Circuit Power Meter) compatible with NQ and NF panels?

      Product Line
      Power Logic Branch Circuit Power Meter (BCPM)

      Environment
      Mounting considerations and installation

      Cause
      Compatibility between older BCM and newer BCPM meters in NQ, NF and NQOD panels.

      Resolution
      As of April 2010 the BCPM is fully compatible with the NQ and NF panels.  The NF panels are designed for 1" spacing and the NQ panels are designed for 3/4" inch spacing. The older BCM (Branch Current Meter) is only compatible with the NQOD panels.

      ION Enterprise 6.0 - Cannot run ad-hoc database trim from Database Manager if using SQL Server 2008

      ION Enterprise Database Manager allows a user to Trim data from the ION_Data database on an ad-hoc basis. If Trim... is chosen from the pop-up menu, it is possible to define a date range and select one or all of the three types of logged data - Interval, Waveform and Event. However, If ION Enterprise 6.0 SP1 is installed with SQL Server 2008, this operation will fail with an error indicating that TRUNCATE_ONLY is not supporter:

      The following error occurred:
      Error trimming database while truncating the transaction log
      'TRUNCATE_ONLY' is not a recognized BACKUP option.

      Database Manager uses PMLMSDEManager.dll to execute the TrimRecords stored procedure. This file needs to be updated so that it no longer uses the TRUNCATE_ONLY command. Versions of RS2008ConfigurationWizard.exe produced prior to December 23, 2010 will not update this file, however the most recent version of the tool will. RESL 203767 has been updated to include the most recent version of RS2008ConfigurationWizard.exe.

      There is a workaround. It is possible to run the stored procedure directly in SQL Server Management Studio as shown below: The two dates are a start and end date, and the bit flags are Data/Waveform/Event respectively. In the example below, Waveform and Event data from January 1 to January 2 2010 would be deleted.

      EXEC TrimRecordsSQL'2010-1-1','2010-1-2',0,1,1


      Last Revised: December 23, 2010

      All content © 1992-2011 Schneider Electric


      Legacy KB System (APS) Data: RESL203738 V5.0, Originally authored by JaMc on 10/19/2010, Last Edited by DaDu on 07/19/2012
      Related ranges: ION Enterprise V6.0

      What is the difference between an LUB12 32 & LUB120 320 Tesys U starter?

      What is the difference between an LUB12 32 & LUB120 320 Tesys U starter?
      The Tesys U non reversing starter controller offers two types of power base units in its range
      LUB12 & LUB120 (0 – 12A, 5.5kw at 400V)
      LUB32 & LUB320 (0 – 32A, 15kW at 400V)
       
      LUB12 & LUB32 power bases have gone through an evolutionary change.
      Pre 2010 wk36, the base unit was coloured black\white & the contact block LU9BN11 was removable.
      Post 2010 wk 36, the base unit is black, to denote power & the contact block LU9BN11 is now fixed.
       
       
      LUB210 & LUB320 will always be delivered with all slots empty (removable plastic covers) which will enable the customer to select their own contact \communication arrangements. Therefore, part No.: LU9BN11 is compatible
      Note:
      The LUB120 & 320 have also gone through the same colour change as previously mentioned
       
      Part No.: LU9BN11:
      Is a contact block comprising of, 1NO (13-14) & 1NC (21-22), which indicate the state of the main poles
       
       
      Note:
      Although, some customers are familiar with the model U bases with plug in units. It is worth a reminder that, the new pre wired contacts in the LUB12 & 32 arefixed & are not meant for removal.
      If they are removed (with some effort) it will render the base unit inoperable & a new one will have to be purchased.

      The LUB32 can be used in CAT 3 Safety applications as the contacts are mirrored and linked.
       

      Which protocols can be used on SLAN output (Fiber optic output) of ACE969FO-2?

      ACE969FO-2 SLAN output is a serial port only and therefore only supports serial protocols. In this case, these protocols are Modbus RTU, DNP3 and IEC60870-5-103 protocols. Since Modbus TCP/IP is an Ethernet protocol, it is obviously not supported by the ACE969FO-2 serial communications accessory.
      For more information, there is a chart in the "Communication Accessories" section of the Sepam 20, 40, 80 "Digital Protection Relays" catalogue. A copy of this chart from the 2010 version of this catalogues is reproduced below for convenience:




      Keywords: Ethernet communications, serial communications, fiber ethernet, fiber serial, fiber optic, connection port, support, Modbus RTU over Ethernet, DNP over Ethernet, IEC103, Modbus TCP

      AEDL3



       
      Legacy KB System (APS) Data: RESL199704 V3.0, Originally authored by DaMi on 08/26/2009, Last Edited by DaMi on 02/02/2010
      Related ranges: ACE 9XX

      Which protocols can be used on the SLAN output (Fiber optic output) of ACE969FO-2?


      Since the ACE969FO-02 does not have an Ethernet port, you cannot be connected to Ethernet using the ACE969FO-2. The S-LAN output of the ACE969FO-2 is a serial port that supports Modbus RTU or DNP3 or IECI 60870-5-103 protocols (but obviously not Modbus TCP/IP since this is an Ethernet protocol). To communicate Modbus TCP/IP, use the ACE850FO. For more information, there is a chart in the "Communication Accessories" section of the Sepam 20, 40, 80 "Digital Protection Relays" catalogue. A copy of this chart from the 2010 version of this catalogues is reproduced below for convenience:



      Keywords: Ethernet communications, serial communications, fiber ethernet, fiber serial, fiber optic, connection port, support, Modbus RTU over Ethernet, DNP over Ethernet, IEC103, Modbus TCP

      The substititution table for XB2B give : XB2BS8445 replaced by ZB4BS8445 But the reference ZB4BS8445t is unknown

      Goals and Symptoms

      The substititution table for XB2B give the reference ZB4BS8445 as substitution of the reference XB2BS8445.
      But this reference is not a valid reference.

      Facts and Changes

      XB2BS8445
      ZB4BS8445
      XB4BS8445

      Causes and Fixes

      There must be a mistake in the cross reference files and in the commercial data base because the logical cross reference of the XB2BS8445 is the XB4BS8445.
      The commercial data base has been updated in january 2010 the 11st but the cross reference list is still wrong.
      This information was given to the marketing activity.

      Energy Meter (EMB/EME) IR Communications Port Information

      Issue
      Does the EMB/EME come with an infrared port?

      Product Line
      Energy Meter EMB/EME

      Environment
      Infrared (IR) Communication Port - Energy Pulsing

      Cause
      The IR port used to come standard on the basic and enhanced models of the energy meter. This was used with the Palm OS organizer with IR capabilities (Palm 3, 5, 7, and Handspring Visor) and the software that was included with the Energy Meter, which provided information from the Energy Meter read via the infrared into the organizer. The organizer had to be within 12 inches and within a +/-20 degree angle of the IR horizontal to accept a reading.

      Resolution
      As of the early-2000s, IR communications capabilities were removed from production of the Energy Meters as newer Palm Pilot software discontinued its support for this application. Any Energy Meters manufactured after February 2010 will not have IR communications. The window on the top left of the unit is still present, but there is no IR diode behind the window.

      Additional questions can be answered by Veris Industries (1-800-354-8556 option 7).

      What is one way to tell if a drive is still under warranty?

      Issue:
      Warranty verification
       
      Product Line:
      Altivar variable frequency drives

      Environment:
      Open style
       
      Cause:
      None
       
      Resolution:
      The date of purchase indicated on the distributors invoice or receipt can be used to determine if the drive is in warranty.   The standard warranty is 18 months (see FAQ FA117023) .  If no receipt or invoice is available the date code of the drive can be used to determine if the drive is in warranty.  This date code is imbedded into the number that is located on the right side label of the drive below the bar code.  The first 2 digits indicate the manufacturing plant.  The next two digits indicate the last two numbers of the year it was manufactured and the next two digits indicate the week of that year.  The following numbers indicate the sequence of drive. 
       example:  8B 092124041 (8B = manufacturing location, 09 = year 2009, 21 = week).  The warranty ends November of 2010 (18 months from May 2009).
       

      Is SHA-1 secure hash algorithm use in PME 8.x?

      Issue:
       
      Does PME 8.x use SHA-1 secure hash algorighm?

      Product Line:
      Power Monitoring Expert (PME)

      Environment:
      Secure Hash Alhorithm and Power monitoring Expert


      Cause:
      Need to know if PME 8.x uses SHA-1 secure hash algorighm

      Relolution:
      PME 8.0 and PME8.1 does not use SHA-1 or SHA-2 for anything security-related.
      PME 8.2 does not use SHA-1 for any security related function.
      PME 8.2 uses SHA-2 (specifically a 512 bit hash) as a part of password protection.

      In cryptography, SHA-1 (Secure Hash Algorithm 1)
      is a cryptographic hash function designed by the United States National Security Agency and is a U.S.
      Federal Information Processing Standard published by the United States NIST.[3]
      SHA-1 produces a 160-bit (20-byte) hash value known as a message digest.
      A SHA-1 hash value is typically rendered as a hexadecimal number, 40 digits long.
      SHA-1 is no longer considered secure against well-funded opponents.
      In 2005, cryptanalysts found attacks on SHA-1 suggesting that the algorithm might not be secure enough
      for ongoing use,[4] and since 2010 many organizations have recommended its replacement by SHA-2 or SHA-3.
      Microsoft,Google, Apple[ and Mozilla have all announced that their respective browsers will stop accepting
      SHA-1 SSL certificates by 2017.











       

      Which M340 I/O modules require a terminal block for wiring?

      The following IO modules require a 20 pin plug in terminal block.
       

      Terminal Block Discrete Module Analog Module
      BMX FTB 2000 caged BMX DDI 1602 BMX AMI 0410
      BMX FTB 2010 screw terminals BMX DDI 1603 BMX AMO 0210
      BMX FTB 2020 spring clip BMX DDI 1604 T BMX AMO 0410
      text BMX DAI 1602 BMX AMO 0802
      text BMX DAI 1603 BMX AMM 0600
      text BMX DAI 1604 text
      text BMX DDO 1602 text
      text BMX DDO 1612 text
      text BMX DRA 0804 T text
      text BMX DRA 0805 text
      text BMX DRA 1605 text
      text BMX DAO 1605 text
      text BMX DAI 0805 text

      The following IO modules require a 28 pin plug in terminal block.
       
      Terminal Block Discrete Module Analog Module
      BMX FTB 2820 spring terminal NA BMX AMI 0800
      text text BMX AMI 0810
      text text text

      Legacy KB System (APS) Data: RESL212217 V1.0, Originally authored by DiSa on 08/01/2013, Last Edited by DiSa on 08/01/2013
      Related ranges: Modicon M340

      Non Zero Voltage Readings on ION6200 or Siemens Access 9200 Meters when nothing is connected to the meter's voltage inputs.

      Goals and Symptoms

      Problem:
      ION6200 or Siemens Access 9200 meters with the P24 low DC voltage power supply option will, in some cases, show readings of 1.5 - to 3.0 volts (Voltage Line to Neutral) for all phases, when nothing is connected to the voltage inputs.

      Confirming the Problem:
      If the ground cable is removed from the power supply module the line to neutral voltage reading returns to the correct reading of 0 Volts. Alternatively if you remove the Earth cable from the voltage input terminals the voltage reading returns to the correct reading of 0 Volts.

      Causes and Fixes

      Solution:
      ION6200 or Siemens Access 9200 meters with P24 low DC voltage power supplies will be shipped with ferrites that will cover and attach to the power supply cable. A document containing ferrite installation instructions will be available through the PowerLogic Website (https://www.powerlogic.com or https://www.global.powerlogic.com). All ION6200 or Siemens Access 9200 meters with P24 power supplies shipped after May 14, 2010 will include the ferrite and installation instructions. Those with previously installed ION6200 or Siemens Access 9200 meter types who experience this issue should install a ferrite using the installation instructions on the website. The ferrite information that we are using can be found below:

      Ferrite Information:
      Laird technologies
      Steward
      28A2024-0A2

      Please note:
      As suggested on page 11 of the ION6200 installation guide: Connect the power supply G (ground) terminal to the same point as the meter earth ground terminal.

      Attachments

      (Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/5b44489f905f7e23c12577160010bd53/fl_block_5/0.1AD6?OpenElement&FieldElemFormat=gif)
      Date Created: April 28, 2010
      Last Revised: April 30, 2010
      Public
      Original Author: SN
      All content © 1992-2010 Schneider Electric


      Legacy KB System (APS) Data: RESL202151 V1.0, Originally authored by MiNe on 05/01/2010, Last Edited by MiNe on 05/01/2010
      Related ranges: 9200, ION6200

      How to Install the MS Loopback Adapter in Windows XP


      Summary

      Microsoft Loopback adapter is required for the reliable operation of all ION Enterprise versions up until version 6.0. ION Enterprise 6.0 eliminated the need for the loopback adapter. The characteristic symptom associated with the absence or incorrect configuration of the loopback adapter is regular spontaneous shutting down of the ION Network Router service and its dependents.

      The ION Enterprise Commissioning Guide contains instructions for installing the MS Loopback Adapter for Window 2000, the procedure for Window XP users is very similar. The step-by-step instructions are given below.


      Keywords

      Windows XP

      MS Loopback Adapter

      TCP / IP


      Detailed Information

      Use the Add/Remove Hardware Wizard in the Control Panel to install the MS

      Loopback Adapter.

       

       

       

       

      1. Double-click on the Add/Remove Hardware Wizard and select YES, I have already connected the hardware. Click Next.

       

       

      2. Highlight Add a New Device from the list of devices, and click Next.

       

       

       

      3. Select Install the hardware that I manually selected from a list and click Next.

       

       

      4. Highlight Network Adapters from the list of hardware types, and click Next.

       

       

      5. Highlight Microsoft from the Manufacturers list, and select Microsoft

      Loopback Adapter from the Network Adapter list. Click Next.

       

       

      7. Click Next again to install the device. Click Finish.

       

       

      Please refer to the ION Enterprise Commissioning Guide for details on how to configure the MS Loopback Adapter after successfully installing it.

       

      Document Change History

      Date and Initials Comments
      2010-07-28 DRM * Increased the precision of the wording around when and why the loopback adapter is needed.
      * Updated the distribution level of the document to public
      * Associated the article with more ranges
       

       

      •  

        Original article#11255

        Last edited: 28 Jul 2010 by DRM on suggestion of EW

        Internal PMO/PMC

        All content © 1992-2007 Schneider Electric


      Legacy KB System (APS) Data: RESL190023 V2.0, Originally authored by KBAdPM on 12/04/2007, Last Edited by DaMi on 07/29/2010
      Related ranges: OS & related Third Party PRODUCTS for Power Mangement Systems, ION Enterprise V6.0, ION Enterprise V5.6, ION Enterprise V5.5, ION Enterprise V5.0, ION Enterprise V4.0, ION Enterprise V4.5

      Installing PowerLogic® ION Enterprise® on a Virtual Machine

      Goals and Symptoms

      Summary


      • This document provides guidelines and recommendations when you install PowerLogic ION Enterprise on a virtual machine. These guidelines can be used with PowerLogic ION Enterprise 5.6 and up.

        Successful deployment of any software in the virtual machine environment takes careful planning, and a consideration of many factors. It Is highly recommended that customers follow virtualization best practices as described by VMware, and consider system design carefully before proceeding with virtualization of their production environment.

        Schneider Electric provides these recommendations to help customers succeed in running PowerLogic ION Enterprise 5.6 in the virtual environment, and will support installations using VMware ESX Server 2.x or 3.x. ION Enterprise 6.0 and up is supported on ESX Server 4.0. For support of the virtual machine host environment installation, configuration, and on-going maintenance, please contact VMware.

      Causes and Fixes

      Before You Begin
      In addition to these notes, you should refer to the PowerLogic® ION Enterprise® Power Management Software Commissioning Guide that you received with your copy of the software.

      System Size
      In the Commissioning Guide, you will find a section titled Primary Server System Requirements. This section describes the minimum system requirements that are needed to successfully run a PowerLogic ION Enterprise system. When running as a virtual machine, the virtual machine, not the host system, must meet these minimum requirements. Your physical machine requirements will be installation-dependent and depend on the number of other virtual machines you intend to run in the host environment.

      Supported Virtual Machine Environments
      ION Enterprise 5.6 and up are supported running on VMware ESX Server 2.x or 3.x.
      ION Enterprise 6.0 and up are supported running on VMware ESX Server 4.0.

      Virtual Machine Settings
      It is recommended that VMwares guidelines and best practices be followed when configuring a virtual machine. VMwares Technical Support is the best source of information on how to optimally configure a production server running within VMware. Some considerations include:

        • ION Enterprise will require network connectivity to client machines, devices, and to SQL Server (in a distributed setup)
        • SQL Server can be disk-intensive. If SQL Server will be running inside the VM, consider pre-allocating disk space at virtual machine creation
        • The section Server Configuration Guidelines in the Commissioning Guide contains suggestions for partitioning the disk the guidelines provided within the Commissioning Guide should be followed, and applied to the virtual machine environment
        • If any serial devices will be used, there must be a physical serial port on the host computer that can be dedicated to the virtual machine
       

      Document Change History

      Date and Initials Comments
      2010-06-23 DRM * Republished to wider audience (public) since this document is referred to in the public document "System requirements for PowerLogic ION Enterprise 6.0"
      •  


        Last Revised: June 23, 2010 by DRM
        Applies To: ION Enterprise 5.6, ION Enterprise 6.0
        Internal PMO/PMC
        All content © 1992-2007 Schneider Electric

         

        Legacy KB System (APS) Data: RESL189843 V6.0, Originally authored by DaMi on 11/29/2007, Last Edited by DaMi on 06/24/2010
        Related ranges: ION Enterprise V6.0, ION Enterprise V5.6

      Scripting with APC by Schneider Electric Switched Rack Power Distribution Units (PDUs)



      Issue

      Looking for assistance with scripting or automating outlet control on Switched Rack PDUs.

       
      Product Line
       
      • AP79XX Switched Rack PDUs
      • AP86XX, AP89XX Switched Rack PDUs

      Environment
       
      • All serial numbers
      • All firmware versions
      • Scripting via Telnet, SSH, SNMP, or Local Console
      • Users using Network Port Sharing (sharing one IP address across up to (4) AP8XXX series Rack PDUs)
      • Users not using Network Port Sharing

      Cause

      Many users like to automate outlet control actions using scripting. The following information is available for AP79XX, AP86XX, and AP89XX Rack PDU devices.


      Resolution

      Please refer to the appropriate section for your PDU device type.


      AP79XX Switched Rack PDU Series

      APC by Schneider Electric Switched Rack PDUs, beginning with part number AP79XX offer a command line interface for easy scripting to automate outlet control.
      In order to access this interface, you must interface with the PDU via terminal (local access with the serial cable), telnet or SSH. Upon receiving a username and password prompt via one of these access methods, enter the following credentials:

      User Name : apc
      Password : apc<space>-c

      Note: 
      (Passwords usually show as *** or blank as you're typing for security purposes)

      You will then receive the following information upon accessing the PDU command line interface:
       
      American Power Conversion
      Rack PDU AP7900 v3.7.3
      AOS v3.7.3
      Outlets: 8
      (c) 2010 All Rights Reserved
      Unit ID: Rack PDU

      1: ON    : Outlet 1
      2: ON    : Outlet 2
      3: ON    : Outlet 3
      4: ON    : Outlet 4
      5: ON    : Outlet 5
      6: ON    : Outlet 6
      7: ON    : Outlet 7
      8: ON    : Outlet 8

      APC>


      Please see the attached document for all available commands and assistance with scripting in conjunction with the Switched Rack PDU. If you have any questions or concerns, please contact APC by Schneider Electric technical support.

      Alternatively, AP79XX Rack PDUs offer outlet control via Simple Network Management Protocol v1 or v3 (SNMP). The PowerNet MIB is available from apc.com as a downloadable file which contains all of the particular OIDs to control the outlets.



      AP86XX and AP89XX Switched Rack PDU Series

      AP86XX and AP89XX Second Generation Switched Rack PDUs offer backwards compatibility with the aforementioned scripting interface but also offer command line access to the embedded Network Management Card 2. These methods can be used on PDUs whether or not they are part of a Network Port Sharing group. Please refer to the Rack PDU's user's guide for available Rack PDU device commands. These are typically added to between firmware versions. https://www.schneider-electric.com/ww/en/download/ can be used to search by product for user's guides. For example, enter AP8941 which is the model of a PDU and all of the associated documents will be listed.


      Alternatively, AP86XX and AP89XX Rack PDUs offer outlet control via Simple Network Management Protocol v1 or v3 (SNMP). The PowerNet MIB is available from apc.com as a downloadable file which contains all of the particular OIDs to control the outlets. Any AP8XXX specific SNMP OID is located under .iso.org.dod.internet.private.enterprises.apc.products.hardware.rPDU2 / .1.3.6.1.4.1.318.1.1.26, where under rPDU2.rPDU2Outlet.rPDU2OutletSwitched /.1.3.6.1.4.1.318.1.1.26.9.2 is where you'll find the outlet control OIDs.
       
      Please note: Scripting outlet actions is not available on APC Metered Rack PDUs because they do not offer individual outlet control.

       

      How to reset the battery remaining counter on an ION7650 or ION7550.

      Goals and Symptoms

      In the Diagnostic Module, there is a register for Battery Remaining. Following is the information copied from ION Reference.

      With the new v355 firmware release the ION7550/7650 will have this register populated. The register always existed but was never populated with the information.

      Causes and Fixes

      Please note:

      In order to replace the battery:Refer to PowerLogic ION7550/7650 Battery Replacement Instructions Document # 70052-0253-00.

      After following the above document, the battery remaining register needs to be reset at this point.
       

      • Via Telnet (firmware older than v355)
      1. Open a DOS command prompt and type telnet <ip.address.of.meter>
      2. Login=7600 or 7500, Password:<front panel password>

      3. Press 9<Enter> to get into the debug parser.
      4. Type
      HN<Enter> to reset the battery counter

      • Via Telnet (firmware v355 and above)
      1. Open a DOS command prompt and type telnet <ip.address.of.meter>
      2. Login= 7650 or 7550, Password:<front panel password>
      3. Press 9<Enter> to get into the debug parser.
      4. Type BATCLEAR<Enter> to reset the battery remaining register.
      • Via Hyperterminal (firmware v355 and above)
      1. Change COMx protocol in meter to Factory
      2. Connect to COMx using Hyper Terminal
      3. Login= 7600 or 7500, Password:<front panel password>
      4. Press 9<Enter> to get into the debug parser.
      5. Type BATCLEAR<Enter> to reset the battery remaining register.
      • Via Hyperterminal (firmware older than v355)
      1. Change COMx protocol in meter to Factory
      2. Connect to COMx using Hyper Terminal
      3. Login= 7650 or 7550, Password:<front panel password>
      4. Press 9<Enter> to get into the debug parser.
      5. Type
      HN<Enter> to reset the battery remaining register



      For firmware v355 and above
      Use BATSETCAPACITY command to set the new capacity when using a battery not shipped from our factory.

      BATSTAT .....................………...Display Battery Stats
      BATCLEAR ................................Reset Battery Counters
      BATSETCAPACITY <mAh> ........Set Battery Capacity (mAh)
      Note: Default battery capacity is 1500mAh. 

      Use command to set the new capacity when using a battery not shipped from our factory.

      For firmware prior to v355

      HB .....................………...Display Battery Stats
      HN ...................................Reset Battery Counters
      BATSETCAPACITY <mAh> ........Set Battery Capacity (mAh)
      Note: Default battery capacity is 1500mAh.

      Warning:

      A dead battery or the act of changing/removing a battery may cause the following symptoms:
      1) possible incorrect time
      - resolved by performing a timesynch after as described in the Battery Replacement Instructions
      2) possible incorrect battery remaining statistics (because time is a factor)
      - resolved by following the steps in this document - the BATCLEAR or HN command
      3) possible corrupt interval data (600 error in the event log)
      - resolved by saving and restoring integrator data using ION Setup. Essentially the values in the integrator are copied manually and entered again.

      How to change a device name and associate the old data with the new device name in ION Enterprise 5.0/5.5/5.6/6.0.

      Goals and Symptoms

      Background: The ION Enterprise Management Console allows a user to easily change the name of a device. Until version 6.0, the user was given no indication of the effect that this would have on historical data access for the renamed device. If a device is renamed while the ION Log Inserter service is running, the Log Inserter will create a new source in the ION_Data database, and all historical data collected after the device is renamed is assigned to this new source name. If it is necessary to rename a device, it is best to shut down the ION Log Inserter first.
      This article describes the steps required to properly rename an existing device that is providing historical data. It assumes that the goal is to rename the device such that existing historical data will be assigned to this new meter name.

      CAUTION: This procedure requires manual changes to the databases. Backup the ION_Data and ION_Network databases before proceeding.

      Keywords: device, meter, rename, change name

      Facts and Changes

      The simplest way to rename a device such that pre-existing historical data is assigned to the new device name is to:

      1. Shut down the ION Log Inserter service,
      2. Rename the device in the Management Console, then
      3. Execute a series SQL queries to propagate this name change to specific database tables.

      If the Log Inserter is left running when the device is renamed in the Management Console, a more complicated series of steps is required to ensure that pre-existing historical data is associated with the new device name. This article describes both scenarios, and addresses all versions of ION Enterprise (5.0, 5.5, 5.6 and 6.0)

      Causes and Fixes

      It is very important that you enter the SQL commands described in this article correctly. Please read all of the instructions carefully before proceeding. Make sure that you backup the databasesbefore beginning this procedure.

      When instructed to execute SQL queries, you can use either the SQL Server Management Console (preferred) or the ION Database Manager SQL Editor.

      Scenario 1 - The ION Log Inserter service is shut down before the device is renamed.

      1. Shut down the ION Log Inserter and ION Query Server services.
      2. Take note of the original device name as it appears in the Management Console. For the purposes of these instructions, let's call it 'My.OldDeviceName'
      3. Start the Management Console and change the device name (in ION Enterprise 6.0, you will see a warning dialog. When asked if you want to proceed, choose Yes). For this example, let's rename it from My.OldDeviceName to My.NewDeviceName. Changing the device name in the Management Console will only change its name in the Device table in ION_Network. You will also need to change the name in the Source table in ION_Data, and in the IAS_Source table (ION Enterprise 5.5) or in the SRC_Source table (ION Enterprise 5.6 and greater)

      ION_Data Database - All ION Enterprise versions - Update device name in the Source table:
      Update the name in the Source table to reflect the name change by executing the following SQL query

      UPDATE Source SET name='My.NewDeviceName' where ID= ( SELECT ID FROM Source WHERE Name =
      'My.OldDeviceName')

      ION_Network Database - ION Enterprise 5.6 and greater - Update the device name in SRC_Source
      Update the name in the SRC_Source table in ION_Network by running the following SQL command against the ION_Network database:

      UPDATE SRC_Source SET name='My.NewDeviceName' where SourceID = (SELECT SourceID FROM SRC_SOURCE WHERE Name = 'My.OldDeviceName')

      ION_Network Database - ION Enterprise 5.5 only - Update the device name in IAS_Source
      Update the name in the IAS_Source table in the ION_Network database by running the following SQL command against the ION_Network database:

      UPDATE IAS_Source SET name='My.NewDeviceName' where SourceID = (SELECT SourceID FROM SRC_SOURCE WHERE Name = 'My.OldDeviceName')

      ION Enterprise 5.0 only - no changes are necessary in the ION_Network database.

      Final Steps:
      1. Restart the ION Log Inserter and Query Server services
      2. Use Vista to verify that the historical data from the before the device renaming is continuous with the historical data from after the renaming.
      3. You may have to do some Vista diagram edits to reflect the name change
      4. If you are using ION Enterprise as a data collection system for ION EEM, see RESL197993 on what needs to be done in ION EEM after renaming a device in ION Enterprise.

      Scenario 2 - The device is renamed in the Management Console while the ION Log Inserter service is running

      If a device is renamed in the Management Console while the Log Inserter is still running, a new source will be created in the Source table in the ION_Data database. Historical data uploaded from this device, once it has been renamed, will be assigned to this new source. It is necessary to run a series of SQL queries to connect the pre-existing data assigned to the old device name to the new data that will be assigned to the new source name. To proceed:
      1. Shut down the ION Log Inserter service.
      2. For this example, assume the the original device name was My.OldDevice and the new name is My.NewDevice

      All ION Enterprise versions:

      ION_Data
      1. Update the DataLogStamp/EventLog/WaveformLog tables to use the sourceID created for the new device name for the pre-existing historical data. Run the following SQL queries against the ION_Data database:

      UPDATE DataLogStamp SET SourceID = (SELECT ID FROM Source WHERE Name = 'My.NewDevice') WHERE SourceID = (SELECT ID FROM Source WHERE Name = 'My.OldDevice')
      //// NOTE: For SPM 7.0 up to but not including 7.2.2, change DataLogStamp to DataLog2 - for SPM 7.2.2 and newer, this operation is unnecessary ////

      UPDATE EventLog SET SourceID = (SELECT ID FROM Source WHERE Name = 'My.NewDevice') WHERE SourceID = (SELECT ID FROM Source WHERE Name = 'My.OldDevice')

      UPDATE WaveformLog SET SourceID = (SELECT ID FROM Source WHERE Name = 'My.NewDevice') WHERE SourceID = (SELECT ID FROM Source WHERE Name = 'My.OldDevice')

      2. Delete the obsolete source, i.e. My.OldDevice from the ION_Data database now that all of the historical data has been associated with the new device name - see RESL191111

      ION Enterprise 5.6 and greater:

      ION_Network
      1. Delete the obsolete source, i.e. My.OldDevice from the ION_Network database. The Log Inserter will have corrected all the required entries for the new source name - see RESL191111 - be sure to follow the steps corresponding to your version of ION Enterprise.

      Final Steps:
      1. Restart the ION Log Inserter service.
      2. Check the continuity of your data using Vista.
      3. Use Web Reporter to verify that only the new source name appears in the source list.

      It is important to note that even after a successful device rename that the tree file for the device is still present within the config/trees folder. This device will still appear within the Diagnostics viewer with a comment "Device does not exist in the system". The ION Services will need to be stopped and the tree file deleted or moved in order to remove it from the Diagnostics Viewer.

      BCPM Specific:
      A single BCPM device defined in the Management Console will have as many as 42 channels mapped as unique sources in the databases, thus the procedure for change the name of a BCPM device requires remapping many sources. The attached sql script file should make this process less painful, The script will need to be edited to reflect your specific devices names, both old and new.

      BCPM_name_Change.sql


      Date Created: November 13, 2007
      Last Revised: July 30, 2010 by JM
      Public
      Original Author: MN
      All content © 1992-2010 Schneider Electric

      Legacy KB System (APS) Data: RESL189159 V8.0, Originally authored by KBAdPM on 11/14/2007, Last Edited by ChMu on 11/15/2013
      Related ranges: ION Enterprise V6.0, ION Enterprise V5.6, ION Enterprise V5.5, ION Enterprise V5.0