C120H circuit breaker, 1-pole, with screw cap

Multi 9 C120 Screw Shield Sealable and Divisible, for C120, Set 8

Catalogue Number: 18527
C120H circuit breaker, 1-pole, with screw cap
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range of product
C120
Product or component type
screw shield
Accessory / separate part category
insulation accessory
Quantity per set
set of 8
Range compatibility
  • Multi 9 C120
  • Multi 9 C120 C120NA-DC
    • Poles description
    • 4P
    • 3P
    • 1P
    • 2P
      • Compatibility code
        C120
        REACh free of SVHC
        Yes
        EU RoHS Directive
        Compliant
        Toxic heavy metal free
        Yes
        Mercury free
        Yes
        RoHS exemption information
        Yes
        China RoHS Regulation
         Pro-active China RoHS declaration (out of China RoHS legal scope)
        Circularity Profile
        N/A
        WEEE
        The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
        Warranty
        18 months

        Documents & downloads

        hide show
        Filter items
        • All

        • Product Brochures

        • CAD Files and Packs

        • Catalog Page

        • Technical Data Catalogues

        • Product Environmental

        • Installation Instruction

        • End of Life Manual

        • Operating Manuals

        • Specification for Tender

        • Application Solutions

        • Certificates (MSDS)

        • Declaration of Conformity

        Frequently Asked Questions

        hide show

        Are EasyPact MVS circuit breakers for sale in the USA or Canada?

        Issue:
        Where can I buy a EasyPact MVS breaker?

        Product Line:
        EasyPact MVS circuit breakers

        Resolution:
        There are no plans for a general release of the EasyPact MVS circuit breaker line in the US.
         

        What is the replacement for a NC100H 3P 40A 

         The part code 18421

        NetBotz post-only mode fails when entering only hostname of Central server.

        Issue:
        NetBotz post-only mode fails when entering only hostname of Central server

        Product Line:
        StruxureWare Central/Data Center Expert
        NetBotz

        Environment:
        StruxureWare Central / Data Center Expert any version
        NetBotz any version.

        Cause:
        Lack of DNS info or fully qualified name.

        Resolution:
        When entering server information into the "InfraStruxure Central IP/Hostname" field of the Advanced View POST-only-mode configuration window, you must enter either an IP for the Central server or it's fully qualified domain name. Entering in only the host name without the domain information will cause the posts to fail. Additionally, if you do not add the proper DNS entries into the NetBotz configuration, posting will fail as well.
         

        What is alternative for Schneider part no 18426

        Alternative part no is A9N18426

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

        What is the part code for a pulse relay 16Amp 2P 240V ac coil voltage

        Use a 15520

        What is the replacement part number for the 15270 time clock?

        The replacement part number for the 15270 is now the CCT15940
        for more information see the link....
        https://eshop.schneider-electric.com/product.aspx?org=21&lang=1&dist=276&prod_id=cct15940
        User-added image

        Do you have an active link that takes 185mm cable?

        No, unfortunately we don't have an active link that takes 185mm cable.
        The largest we have is the L13/150R which accommodates 2 x 150sq mm.

        Some of the key features are:
        • 13 hole Front wiring
        • Red base and cover

        For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=L13/150R
         

         

        What is the difference between the Surge Arresters reference 15597 and 16447

        The difference between the Surge Arrester references 15597 and 16447 is as follows:

        1.) 15597 is a PF20 3Pole Fixed type Type 2 LV Surge Arrester.
        2.) 16447 is a PRD20 3Pole Withdrawable type Type 2 LV Surge Arrester. 

        Both are suitable to be used in low risk level and for use in TNC Earthing systems.

        The difference is that 15597 at its end of life needs to be replaced as it is Fixed type, while 16447 at its end of life can be reused by simply replacing the cartridge as it is Withdrawable type, and the other major advantage is that the wiring does not get disturbed.

        When configuring the 140DRC83000, which bits are used of the User Defined Timeout State field?

        For the User Defined Timeout State of the 140DRC83000, only the bits of the low byte or right most byte are used.
        For example a value of 00FF Hex, will set all outputs high on a timeout condition.

        What is the difference between 9001KA21 and 9001KA1 contact blocks?

        Issue:
        Difference between 9001KA21 and 9001KA1.

        Product Line:
        Harmony Pushbuttons

        Environment:
        All Products

        Resolution:
        9001KA21 has binder head screws and is not finger-safe. 9001 KA1 has cable clamps and is finger safe.
         

        UPS Signalling Bundle for IBM AS/400 & IBMi (IBM Power Systems)



        Issue

        UPS Signalling Bundle for IBM AS/400 & IBMi (IBM Power Systems) - General Information and Troubleshooting steps



        Product Line

        • UPS Device Management
          • AP98275 - UPS Signalling Bundle for IBM AS/400 & IBMi (IBM Power Systems)
          • Most APC branded UPS Models - Single or Three Phase


        Environment
         
        • Users with IBM iSeries or AS/400 servers looking for graceful shutdown options
        • Troubleshooting scenario
        • All UPS firmware versions (unless otherwise noted)


        Cause

        This article provides general information outlining the AP98275 and any steps required for the configurations to work between APC UPS models and IBM iSeries and AS/400 model IBM devices using the AP98275 cable bundle.


        Resolution


        Please refer to the following user's guide linked below outlining the AP98275 bundle and supported IBM server models. Please note we do not currently support any system beyond Power Series 7

        https://www.apc.com/salestools/SMAN-946MPK/SMAN-946MPK_R2_EN.pdf

        The AP98275 kit includes the following cables, as noted in the Inventory section of the user's guide:






        This document also reviews installation, supported APC UPS systems, system requirements, and set up.


        Important Configuration Information
         


        As noted in IBM Software Technical Document 467390013, most users may be using D/A/D in SST within the IBM OS to determine if a UPS is detected by the IBM server.



        What does the number indicate?
         
        • If the value is 0 - no UPS is detected.
        • If the value is 8 - UPS detected and everything is normal.
        • If the value is 9 - UPS detected and battery is low.
        • If the value is A - UPS detected and in bypass mode.
        • If the value is B - UPS detected, in bypass mode, and battery is low.
        • If the value is C - UPS detected and power has failed.
        • If the value is D - UPS detected, power has failed, and battery is low.


        Use of the 940-0274 Cable

        You will NOT receive a UPS-detected signal when using the 940-0274 cable. Instead, a “0” bit character is displayed when this 940-0274 cable is used in place of 940-0031 and IBM f/c 1827. The recommended configuration to replace the 940-0274 cable is to use the 940-0031 cable with an IBM f/c 1827 adapter. This configuration correctly reports that a UPS is detected, power has failed, etc.

        If this does not work, make sure to verify the following items:

        • The cable connector end labeled "UPS" is connected to the UPS (or the 940-3000 dongle if required).
        • Power is applied to the IBM server in the correct way to configure the server serial port for UPS use.

        Note: The 940-0274 cable returns incorrect values due to the IBM reporting. Per IBM Technical Document “467390013”, the highlighted value should be ‘C’ for a “UPS detected and power has failed” instance. Had the value originally been ‘8’, 8+4=C in hex. Therefore, the user cannot rely on a MISR value of ‘8’ to indicate whether the UPS is detected within the IBM tool.
         

        It is important to test that your system is operating correctly.

        To verify connectivity with the 940-0274 cable configuration specifically, perform the following steps:
         
        1. Attach the UPS to the system on the port specified by IBM, for example “T2” or “S2”.
        2. Ensure that the system is set to a restricted state, to minimize a possible outage if the UPS does not provide continuous power.
        3. Verify that “WRKSYSVAL QUPSDLYTIM” is not set to zero or a low value.
        4. To place the UPS into battery operation, remove AC power to the UPS by unplugging the power connection. 
          •   Do not turn off the UPS with the “off” button.
        5. If power is removed for longer then “QUPSDLYTIM,” the system will start to shut down.
        6. Restore AC utility power to the UPS.
        7. Check the “QSYSOPR” message queue for the Utility Power Failed and Utility Power Restored messages.


           

        What is the part number for a 4 channel timer?

        The part number for a 4 channel timer is 15270 which is now replaced by CCT15940

        For further information see:
        https://eshop.schneider-electric.com/product.aspx?prod_id=CCT15940&org=21&lang=1&dist=276&tab=10&ses_id
         

        What is the difference between an alarm contact and an auxiliary contact when used in a circuit breaker?

        Product Line:
        Circuit Breakers

        Environment:
        Electrical Distribution Equipment

        Resolution:
        The auxiliary contact changes state when the circuit breaker contacts change state (breaker opens or closes). The alarm contact changes state only when the circuit breaker goes to the tripped position (or is reset).
         

        Is there a list of NetShelter CX spare parts and accessories available, with photos?

        Issue:
        A list of NetShelter CX and CX2 spare parts and accessories is requested.

        Product Line:
        NetShelter CX
         
        Environment:
        All versions and serial ranges.
         
        Cause:
        Spare part and/or accessory identification is required.
         
        Resolution:
        See attached file.

        What is the replacement for the 18464?

        Part # 18464 - C120 - circuit breaker - C120H - 3P - 32A - C curve Has been discontinued and there is no direct replacement.

        Customer can go for Part # 18727 - 3 Poles 32 Amps C Curve NG125H Breaker but it won't fit the same chassis.

        https://www.schneider-electric.com.au/en/search/18727

        What is the part number for a 7 day Timer?

        The part number is TC32V7D.
        Some of its key Features are:
        • 7 days timer
        • Size: 115 mm length x 73 mm width x 62 mm depth
        • 84 mm apart Mounting centre
        For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=TC32V7D


         

        How can I carry out a Reset on an ITM Multifunctional Time Switch, part number 15270.

        To reset the ITM, follow these instructions:
        • Replace the security code 111 with 753
        • Switch off the power supply
        • Restore the power supply to the product
        • After following these instructions, the ITM can then be reprogrammed (because its memory is empty)

        Alert History not purged in InfraStruXure Central.

        Issue:
        Alert History not purged in InfraStruXure Central.

        Product Line:
        InfraStruxure Central
        StruxureWare Data Center Expert

        Environment:
        Any version

        Cause:
        Alert History is currently not purged in ISXC. The Alert Binary Data, which can be purged, references camera clips captured as part of an alert but not the actual alert text information.

        Resolution:
        The actual text of the alert does not take up much memory and has not been seen to cause a problem yet this issue may be addressed in a future revision of ISXC.
         

        Spaces in a NetBotz user name causes SNMP version 3 to fail.

        Issue:

        Spaces in a NetBotz user name causes SNMP version 3 to fail

        Product Line:

        NetBotz

        Environment:

        NetBotz version 3.

        Cause:
        Spaces in user name.

        Resolution:

        SNMP version 3 on a NetBotz appliance uses the user name for your SNMP authentication. It has been seen where using a user name with a space in it causes the authentication to fail. To avoid this issue, choose another user name without a space or, instead of a space, use another character such as a dash or underscore.

        This issue may be addressed in a future revision of NetBotz firmware.

        Problem: Cannot establish communications via USB with the SMT or SMX UPS after installing PowerChute Agent.

        Issue: Cannot establish communications via USB with the SMT or SMX UPS after installing PowerChute Agent.

        Product Line:
        PowerChute Business Edition

        Environment:
        All supported OS

        Cause:
        USB cable not connected during software installation

        Solution:

        If you installed the PowerChute Agent without the USB communications cable connected to the UPS, then you cannot subsequently establish communications. You need to correctly connect the USB communications cable from the computer to the UPS and then re-install the Agent.

        If the USB cable was connected during installation please review knowledge base document FA163608

        PowerChute Personal Edition 3.X "has stopped working" on Windows Vista or Windows 7.

        Issue:
        PowerChute Personal Edition 3.X "has stopped working" on Windows Vista or Windows 7.

        Product Line:
        PowerChute Personal Edition version 3.X

        Environment:
        All supported Windows OS

        Cause:
        If you see "PowerChute has stopped working" on Windows Vista or Windows 7

         

        the reason is missing Arial font/s on your system. To check to see if Arial.ttf and or Arialbd.ttf are missing look in C:\Windows\Fonts\Arial

        Solution:

        If they are missing you can load the Arial fonts - font family from you system CD, system back-up drive, or back-up CD. You may also download the fonts from Microsoft.com

        How to Load VMware vSphere Client onto a PC

        Issue:
        How to Load VMware vSphere Client onto a PC

        Product Line:
        VMware vSphere Client

        Environment:
        Microsoft Windows XP, Vista, Win 7, Win8, Win8.1, Win 10
        NOTE: vSphere Client requires .Net Framework 3.5 be present before it will install properly. Windows XP, 8.x, and 10.x do not ship with .Net Framework 3.5 so it must be installed prior to installing vSphere client. See Microsoft forum post https://answers.microsoft.com/en-us/windows/forum/windows8_1_pr-networking/when-installing-the-vmware-vsphere-51-client-i-get/8cfa9152-fb46-432e-99f3-3ba3558f3845 for more information.

        Cause:
        Informational

        Solution:

        Please review the attached PDF.

        NetBotz wireless pod data loss if NBPD0180 coordinator is disconnected.

        Issue:

        NetBotz wireless pod data loss if NBPD0180 coordinator is disconnected

        Product Line:

        NetBotz

        Environment:

        NetBotz version 3 appliances
        NBPD0180

        Cause:
        You will lose data for any sensor connected to the wireless coordinator if it is disconnected from the NetBotz appliance.

        Resolution:

        If you follow the steps below, you can prevent data loss from the router or end devices that are also being monitored.

        1. Once the coordinator is disconnected go to serial devices and remove it from the list
        2. Plug the coordinator back into the bot
        3. Go to serial devices and set it as a coordinator again (APC Wireless Sensor Pod 180 option)
        4. Wait for the end devices and routers to report back into the coordinator and they should come back online in the bot, all previous data should be available to graphs / reports.

        Any pod deleted from advanced view will also have it's data deleted. Following the above instructions will cause the coordinator to be removed but any router or end device should remain.
         

        The ESXi host running the free edition of VMware is not shutting down when commanded to by PowerChute Network Shutdown.

        Issue:
        VMware ESXi host, which is running the free edition of VMware, is not shutting down when commanded to by PowerChute Network Shutdown.

        Product Line:
        PowerChute Network Shutdown (PCNS) version 2.2.3, 2.2.4, 3.0, 3.0.1, 3.1, 4.x

        Environment:
        VMware ESXi versions 3.5, 4.x, 5.x, 6.x

        Cause:
        The free edition of VMware ESXi provides read-only access to the API functions. Without write access to the API functions, PowerChute cannot issue a command to shut down an ESXi host.
        To review a list of supported VMware ESXi versions see Kbase FA278213

        Resolution:
        To make PowerChute Network Shutdown work properly you will need to purchase a license for ESXi. 

        If PowerChute is running on vMA 4.1 or 5.x please review Kbase FA159783

        "VMware ESXi host is not shutting down when commanded to by PowerChute Network Shutdown running on 4.1 & 5.x."

         

        You can also find more information in Kbase FA159768 "Shutdown VMware ESXi 4.1 unlicensed server with PowerChute Network Shutdown"

         

        What is the ratio n between the peak value and the root mean square value of the short-circuit current

        Product standard BS EN 60947-1 defines the ratio n between the peak value and the rms value of the short-circuit current (table 16 on page 106). The rms value must be taken into account for the thermal effect, and the peak value must be taken into account for the electrodynamic effect. The value of n is:

        1.41 for I <= 1500.
        1.42 for 1500 < I <= 3000.
        1.47 for 3000 < I <= 4500.
        1.53 for 4500 < I <= 6000.
        1.7 for 6000 < I <= 10,000.
        2.0 for 10,000 < I <= 20,000.
        2.1 for 20,000 < I <= 50,000.
        2.2 for 50,000 <; I.

        For information: In the circuit breaker standard BS EN 60947-2, these values (Icu/Icm) are given in table 2 on page 19.

        Information on Obsolete AD module power supply for Micrologic

        Issue:
        Obsolete AD module power supply for Micrologic

        Product Line:
        Circuit Breakers

        Environment:
        Micrologic Trip Unit

        Resolution:
        These are now obsolete; information for installed base only

          The following are the catalog numbers of the various power supplies. All produce a 24 Vdc output. 
        Cat. No. Input Output
        685823 24–30 Vdc  
        24 VDC, 1 A
        (all have this same output)
        685824 48–60 Vdc
        685825 100–125 Vdc
        685826 110–130 Vac
        685827 200–240 Vac
        685829 380–415 Vac

        See instruction bulletin, S1A80373.
        As an example this is a picture of the 685826.

        LUA1C vs LUFN What's the difference and how many blocks can we add in to the Tesys U line base?

        Issue:  What is the difference between the LUA1C and LUFN contact blocks? And how many can be used in the tesys U starter?


        Product Line:
        All Schneider Electric products

        Environment:
        Products sold and used in the United States

        Cause: Selecting auxiliary contact modules for the tesys u motor starter line.

         
        Resolution: The LUA1C modules will have aready condition contact and a fault condition contact, while the LUFN has contacts that are both pole state contacts. For example the LUA1C20 has a ready condition and a fault condition contact; one contact is closed in ready and run, the other one is open in off ready and run but closed in short circuit trip or overload trip. The LUFN20 are both pole state contacts; if the coil is powered and the poles are closed these contacts are closed. There is a table (18.115) on page 18-28 of the digest 176 to illustrate this.



        Keywords
         
         

        PowerChute Network Shutdown 2.2.4 and 4.5G and 5G Smart UPS Behavior


        Issue

        When using Powerchute Network Shutdown 2.2.4 and Network Management Card 2 UPS application firmware revision apc_hw05_sumx_v5.0.3 (SFSUMX503), selecting the option to turn off the UPS via PowerChute Network Shutdown is supported for only the 'On Battery' and 'Low Battery' UPS events on certain Smart-UPS models.

        Should a user attempt to use the turn off UPS functionality via PowerChute Network Shutdown for other events, the UPS will not turn off. Furthermore, should the user restart the server running PowerChute Network Shutdown, the server will shutdown immediately.



        Product Line
         
         

        • Smart-UPS Models:
          • SMT750
          • SMT1000
          • SMT1500
          • SMT2200
          • SMT3000
          • SMX750
          • SMX1000
          • SMX1500RM2U
          • SMX1500RM2UNC
          • SMX2000RMLV2U
          • SMX2200RMLV2U
          • SMX3000RMLV2U
          • SMX3000RMLV2UNC
        • UPS Network Management Card 2
          • AP9630
          • AP9631



        Environment

        • AP9630/31 sumx application v5.0.3
        • All serial numbers


        Cause

        This is due to the initial implementation of v5.0.3 sumx application for particular UPS models.



        Resolution

        It is recommended that users upgrade to SUMX application 5.1.1 or higher to resolve this issue at https://www.apc.com/tools/download.

        In order to rectify the server restart/shutdown situation without upgrading, the user must manually turn off the UPS and then turn it back on.




        Please note: Any prior version of PowerChute Network Shutdown will not work with the aforementioned UPS models.



        PowerChute Business Edition server installation hangs while trying to create the server service when no network is configured or present on Windows OS.

        Issue:
        PowerChute Business Edition Server installation hangs while trying to create the server service when no network is configured or present on Windows OS.

        Product Line:
        PowerChute Business Edition Server

        Environment:
        All supported Windows OS

        Cause:
        No configured network on the system

        Solution:
        1. If not done at the time of installation configure your network or enable the network to allow the installation to proceed.

        Note:  
        If this does not address the issue the PCBE Server will need to be reinstalled. Before reinstalling the PCBE Server complete the following steps will need to be completed:
         
        a. Terminate the Installation process by going into Task Manager and stopping the PCBE installation application.
        b. Go to the Registry and select 'Computer', then search for PowerChute and delete any keys containing PowerChute.
        Warning:  Editing the Registry incorrectly can cause serious system wide problems that may require you to reinstall Windows to correct them.  APC and Microsoft can not guarantee that any problems resulting from editing the Registry can be solved.
        c. In the Registry, select 'Computer, then search for any keys containing APCPBEServer. Both of these keys should be deleted completely not just the branches.
        d. Then reboot the PC.

        Schneider Electric Rack LCD products and perceived "Image Burn In" / Dead Pixel Policy



        Issue

        Screen or image "burn in" on a Rack LCD product; appearance of a "ghost" image

        Dead pixel policy


        Product Line

        Rack LCD Console models:
        • AP5808
        • AP5818
        • AP5717
        • AP5719


        Environment

        • All serial numbers
        • All firmware revisions



        Cause

        The models listed above have a Liquid Crystal Display. By nature, LCD's are not susceptible to "burn in" technically but "image persistence." Leaving the screen on 24/7 is not considered proper operation and will void any warranty replacement terms. This is considered negligence in most cases. For your particular unit, reference the warranty terms at the end of the product's user guide. 

        Furthermore, a user may experience "dead pixels" which do not disappear, even after massaging the LCD.


        Resolution

        1. Do not leave the monitor on more than 24 hrs without any operation or movement on the screen (such as a screen saver). It's the main reason resulting in perceived burn in or image persistence.
        1. To effectively prevent the said operation error, turn off the LCD screen using the "LCD Turn Off" button or close the lid when not in use. Please note, closing the lid will only turn off the backlight (but keep the signal active) on the LCD and the "LCD Turn Off" button should be utilized for long periods of inactivity. On the AP5808 or AP5816 units with an integrated KVM switch, there is also a screen blanker feature that can be utilized. To enable this, press F3 and configure the SCREEN BLANK:OFF(0) option to between 1-30 minutes.
        1. If the unit is already experiencing this issue, create a 1280 x 1024 completely white image file (.gif, .tiff, etc) on the screen or for use as a screen saver. Leave the image up when not in use or configure a screen saver to run after 2-5 minutes of non use. After a few days, the monitor should not experience image persistence any longer. Refer to items #1 and #2 above to prevent any further issues.


        Dead Pixel Policy

        Schneider Electric's dead pixel policy requires at least (4) dead pixels in order to be covered under the two year repair or replace factory warranty. 

         

        How to set the IO Board Parameters in Scadapack Workbench?

        The module_address parameter defines the module address of the sp5607 I/O module.

        The address on the module is selected via dip switches on the module. A maximum of eight SCADAPack 5607 I/O type modules may be added to a system

        The ain0_type parameter sets the analog input type for analog input channel 1.

        There are four input types available.

        • An ain_type of 0 sets the input type to measure 0 to 5V input signals.
        • An ain_type of 1 sets the input type to measure 0 to 10V input signals.
        • An ain_type of 2 sets the input type to measure 0 to 20mA input signals.
        • An ain_type of 3 sets the input type to measure 4 to 20mA input signals.

        The ain_filter Parameters:

        • An ain_filter value of 0 sets the input filter for 3Hz and the response time to 155ms at 60Hz and 185ms at 50Hz.
        • An ain_filter value of 1 sets the input filter for 6Hz and the response time to 85ms at 60Hz and 85ms at 50Hz.
        • An ain_filter value of 2 sets the input filter for 11Hz and the response time to 45ms at 60Hz and 55ms at 50Hz.
        • An ain_filter value of 3 sets the input filter for 30Hz and the response time to 30ms at 60Hz and 30ms at 50Hz.

        The scan_freq parameter sets the input scan rate for analog inputs. AC noise rejection is improved at the correct frequency. If the module is used in a DC environment, the 60 Hz setting will yield slightly faster response time.

        • A scan_freq value of 0 synchronizes the input scanning to 60Hz.
        • A scan_freq value of 1 synchronizes the input scanning to 50Hz.

        The aout_type parameter sets the analog output type for both optional analog output channels.

        • An aout_type value of 0 sets the output type for 0 to 20mA signals.
        • An aout_type value of 1 sets the output type for 4 to 20mA signals.


        Graph of state sensor in DCE may not show current value after it has been disconnected and reconnected.

        Issue:

        Graph of state sensor in DCE may not show current value after it has been disconnected and reconnected.

        Product Line:

        StruxureWare Data Center Expert (DCE)
        NetBotz

        Environment:

        StruxureWare DCE 7.x graphing
        NetBotz any version, with a state sensor connected

        Cause:

        NetBotz devices only record values for sensors when those values change. This is done to save space. In the case of a door sensor or dry contact sensor for instance, a door closed for a week does not need to record a weeks' worth of data, only the last state. This is done to save space.

        Since there is no new state after the reconnection event however, StruxureWare DCE will not graph the state until it again changes to an open / closed state after the reconnection of the sensor.
        Here you can see a door sensor that shows a space in the graph in NetBotz Advanced View where the sensor was disconnected and reconnected at about 12:27 to 12:28 or so.




        That same report in DCE shows no values after the sensor was reconnected:



        This next image was taken almost immediately after the previous graph but also after the door was closed and re-opened to cause a state change:


        You can see where this graph captured only a minute later shows about 16 minutes more data.


        Resolution:

        APC/Schneider is currently looking into this issue and may have an update in a future revision.
        A table report will show the current state (closed / open) so you will be able to see the value as well as viewing the sensor's current state on the monitoring perspective of DCE.
         

        What is the breakdown of components for 9001KYK117?

        Issue:
        What is the breakdown of components for 9001KYK117?  

        Product Line:
        Harmony Push Buttons

        Environment:
        Harmony Control Stations

        Cause:
        Product Features

        Resolution:
        9001KYK117 components are:
        1-9001KY1S1 (red enclosure)
        1-9001K15 (break glass operator)
        1-9001KA1 (1 open and 1 closed contact)
        1-9001KN799RP (legend plate)

        Replacement glass discs are 9001K57 (package of five)
         

        Common Rack Automatic Transfer Switch Scenarios and Questions


        Issue

        This article discusses common Rack Automatic Transfer Switch (ATS) Scenarios and Questions and provides configuration recommendations.
         
         

        Product Line


        Rack Automatic Transfer Switches including the following models only:
        • AP7721
        • AP7722A
        • AP7723
        • AP7724
        • AP7730
        • AP7731
        • AP7732
        • AP7750A
        • AP7752
        • AP7753


        Environment
         
        • All firmware versions
        • All Rack ATS models listed above


        Cause

        As the Rack Automatic Transfer Switches are complicated and involved products, we have provided some common scenarios and questions along with recommendations and general information on functionality.
        With these models, please ensure that after analyzing the situation, the latest available ATS firmware has been applied and instructions followed - INFORMATION BULLETIN - Upgrading Rack ATS Firmware (AP77XX) - potential to permanently damage ATS during download.



        Resolution

        Please review the scenarios and questions below for additional information.

        When both sources are available and stable, the ATS will switch back to its preferred source after a 30 second wait period. Attempts to continually switch the unit prior to the completion of the 30 second period could result in loss of load or damage to the ATS. Anytime an anomaly is detected within this sampling period, the 30 second timer will be reset.

        The following is a list of potential causes of ATS to source switching when the upstream UPS goes to battery or when power appears to be present at the ATS input:


         
        1. Switching of the ATS when the UPS goes to or from "on battery" mode
        The switching of the ATS occurs as a result of an internal source synchronization when the UPS transfers from mains power to battery power. The UPS creates a frequency shift to speed up or slow down the frequency in order to align the inverter in phase with the sync source chosen. This frequency shift actually creates a deviation in the way the ATS measures the voltage coming from the UPS. This voltage deviation can be large enough for the ATS to interpret this deviation as a voltage drop resulting in the switching from the preferred source to the secondary source. Having two UPS's powered by the same circuit feeding an ATS can also cause output issues. An ATS is designed to supply redundancy, and if both UPS's transfer to battery at the same time due to an input issue, either the transfer time the UPS takes from "online" operation to "on battery", or the frequency shift of two UPS's switching to battery at the same time, can be seen as a complete interruption of power by an ATS. It is not recommended to use 2 UPS's on the same input circuit as the sources of an ATS.
        1. Dropping the load when the ATS switches sources while both appear to have power
        The tripping of the circuit breakers during the switching process has been determined to be the result of switching between two sources that are out of phase with each other producing a voltage potential that exceeds the rating of the internal relays responsible for switching from one power source to the other. ATS firmware v3.5.7 and higher aims to resolve this issue and will help prevent the ATS from tripping the upstream circuit breakers.
         

        Here are some recommended actions that can be put into place to reduce the probability of the ATS switching when the UPS transfers to battery mode:

        1. Revise the voltage transfer range from medium to wide, revise frequency deviation from +/-2 Hz to +/-3 Hz on the ATS:
         
        This will increase the amount of voltage and frequency deviation allowed prior to switching, reducing the probability of switching during this event.
         
        1. Set the sensitivity preference from high to low:
         
        This will allow more time for the frequency synchronization to occur before the ATS takes action and switches.
         
        1. Set the source preference from source A to none on the ATS:
         
        If neither source is preferred, this is the ideal setting. This will avoid switching back to Source A when the two UPSs are most likely to be out of sync with each other.

         

        Using the Rack ATS with a Generator

        APC recommends placing a UPS between the generator and the ATS input. The UPS will condition the input voltage to the ATS to prevent thrashing.  A second UPS should be used between the power utility and the other input of the ATS. This UPS will power the load while the generator starts and stabilizes. The UPS should be sized to allow time for the generator to be started and the time needed for the UPS attached to the generator to operate normally. While the generator is starting, the generator voltage and frequency are not stable. If the ATS is connected directly to the generator, the ATS can switch to the generator input before the generator has stabilized. The load of the ATS will cause the generator voltage to dip. This dip can also shift the frequency of the voltage. Either of these issues can cause the ATS to switch to the other input.

         

        SPM 7.0 / 7.0.1 - Installer fails at step CheckAppModsDatabase

        Issue
        During a 7.0.1 install or upgrade, the installer fails at step CheckAppModsDatabase. It will be considered an incomplete install.
        Re-trying does not resolve the issue.
        In the Setup log, there will be a long stack trace resembling one of the ones listed in the Causes section below.

        Product
        Struxureware Power Monitoring Expert 7.0

        Environment
        Installer

        Cause 1
        The Windows account that SQL Server service is running as, does not have file/folder access to the location stated in the error. It's trying to execute a bulk load from file Unit.xml but fails. This is usually because service has been run under non-standard account. (i.e. something other than LOCAL SYSTEM, which is usually the default.)

        Installer log will indicate an error was found in ApplicationModules.log file. Navigate to the log file as listed in the error message and open it. Error will resemble:
         

          • Starting Synchronization of [CommonDataModel].[Unit]
            Msg 4861, Level 16, State 1, Server STANDALONE\ION, Line 4
            Cannot bulk load because the file "C:\Users\Administrator\Desktop\SPM 7.0.1\setup\SetupSupport\Database\ReferenceData\CommonDataModel\Standard\Unit.xml" could not be opened. Operating system error code 5(Access is denied.).
        Resolution 1
        Either
        a) temporarily grant read/write permissions to the folder listed in the error, to the user account SQL Server is running under.
        or
        b) change SQL Server to run under the LOCAL SYSTEM account.
        Then re-try running the installer to complete.

        Cause 2
        ApplicationModules database files (.mdf and .ldf) have already been created at the target location, but are not attached to SQL Server. The installer tries to re-create the files but fails. This situation can occur when trying to re-configure multiple times (for instance, after encountering the situation described in Cause 1).

        Installer fails with message "The ApplicationModules database could not be found." Installer log contains the following error:
          • executeNonQuery(CREATE DATABASE ApplicationModules ON ( FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.mdf'), ( FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules_log.ldf') FOR ATTACH, master) Failed on exception:
            System.Data.SqlClient.SqlException (0x80131904): Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.mdf". Operating system error 5: "5(Access is denied.)".
            at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
            at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
            at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
            at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
            at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
            at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
            at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
            at SchneiderElectric.Installer.InstallTools.ConfigureSQL.ExecuteNonQuery(SqlCommand command, String dbName)
             
        ApplicationModules.log file contains the following error:
          • Creating ApplicationModules...
            Msg 5170, Level 16, State 1, Server STANDALONE\ION, Line 1
            Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.MDF' because it already exists. Change the file path or the file name, and retry the operation.
            Msg 1802, Level 16, State 4, Server STANDALONE\ION, Line 1
            CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

        Resolution 2
        Delete or rename the existing ApplicationModules database files, the re-run the installer. Let the installer re-create the database and complete the install.

        Cause 3

        The installer fails to create the application modules database successfully.

        Resolution 3

        Checking the diagnostics within the C:\Program Files (x86)\Schneider Electric\ION Enterprise\Applications\Diagnostic shows the following error message: "CREATE DATABASE failed. Primary file must be at least XX MB to accommodate a copy of the model database."

        Instead of "XX" an actual file size will be given. In this situation SQL is attempting to create the Application Modules database, but the Model database is larger in size. All newly created SQL databases must be larger in size than the model system database to succeed. Within SQL Management Studio backup and perform a shrink operation on the model database which should allow the installer to succeed creating the Application Modules database. Right click on the model Database -> tasks -> shrink.

        Parameters for setting up multiple monitors in a SCADA project

        Issue
        Setting up multiple monitors

        Product Line
        PowerSCADA Expert (8.x, 9.0)

        Environment
        Computer Setup Editor
        INI Parameters

        Cause
        Multiple monitors being utilized in the project

        Resolution
        The following parameters are used to control how multiple monitors function in a project.

        PSE 8.0

        [MultiMonitors]DisableAutoStart
        Used to stop the MultiMonitor functionality from being loaded automatically at startup
        False (0)- Enable startup loading of Multimonitor functionality
        True (1)- Disable startup loading of Multimonitor functionality
        Default value: 0

        [MultiMonitors]Monitors
        Indicates the number of monitors the project will be displayed on; the project can be displayed on a maximum of 8 monitors
        Default value: 1

        [MultiMonitors]StartupPage<n>
        Determines the pages that appear when starting up a multi monitor setup. For example, StartupPage1 determines the page that appears on the first monitor at startup, StartupPage2 determines what appears on the second monitor, and so on.
        Default Value: If left blank, the page specified in parameter '[Page] Startup' will be displayed

        PSO 9.0

        1. Common Parameters​

        [MultiMonitors]DisableAutoStart 
        Used to stop the MultiMonitor functionality from being loaded automatically at startup.
        Note: Use the MultiMonitorStart() cicode function to load the MultiMonitor function if required
        Allowable Values: 
        • False (0)- Enable startup loading of Multimonitor functionality
        • True (1)- Disable startup loading of Multimonitor functionality
        Default Value: False (0)

        [MultiMonitors]Monitors 
        Indicates the number of monitors configured for the project. 
        Note: This parameter is ignored if the ScreenProfile parameter is used.
        Allowable Values: 1 to 8. 
        Default Value: 1 

        [MultiMonitors]ScreenProfile
        Sets the arrangement of monitors on a client workstation for a project. 
        Allowable Values: Any valid screen profile name 
        Default: None

        [MultiMonitors]StartupPage<n>
        Determines the pages that appear when starting up a multi monitor setup. For example, StartupPagePrimary determines the page that appears on the first monitor at startup, StartupPage1 (the name you have assigned to the parameter) determines what appears on the second monitor, and so on. 
        Allowable Values: Any valid page name 
        Default Value: If left blank, the page specified in parameter [Page] Startup. 

        [MultiMonitors]StartupPage<Name>
        Determines the page that appears on the monitor that corresponds to the screen named "Screen1" in the screen profile. 
        On start up, Citect SCADA will compare the physical monitors on the workstation to the screens in the screen profile and attempt to map screens to monitors based on the resolution and relative position to the primary monitor/screen. If a physical monitor cannot be found, for example it has failed or been disconnected or the configuration is incorrect, that screen will be mapped to the primary monitor. So, you may have multiple pages displayed on the primary monitor.
        Note: If you don't specify a startup page for a monitor in the Setup wizard, any startup page setting in the Citect.ini file will be replaced by ><. This overrides the configuration of a monitor set up with a page in the Parameters database.
        Allowable Values: Any valid page name 
        Default Value: No default. However, if no value has been specified for any of the screens, the page specified by the [Page] Startup parameter will be shown on the primary screen only. 


        2. CSV Parameters

        [MultiMonitors]LastPageStackSize 
        Determines the maximum number of pages that can be included in the Back button's drop-down list of previously visited pages. 
        Allowable Values: 1 - 10 
        Default Value: 10 

        [MultiMonitors]ScreenWidth 
        Adjusts the displayed page to suit the width of the screen in pixels. If you are not running with the recommended default screen size of 1024 x 768, you should adjust this setting to match the screen width of one monitor. 
        Allowable Values: 640, 800, 1024, 1152, 1280, 1920, etc. 
        Default Value: 1024


        3. Situational Awareness Parameters

        [MultiMonitors]Context<n>
        Allows you to share a single context with one or more screens.
        Note: This parameter is only valid for Situational Awareness projects.
        Allowable Values: Any valid context name.
        Default: None


        [MultiMonitors]Workspaces
        Indicates the number of workspace pages that are shown. This parameter is only relevant when using Situational Awareness workspaces.
        Note: If the number specified is incorrect (value too low), the Workspace functionality may not work as expected, or there may be a delay before workspaces are initialized (value too high).
        Allowable values:Values between 1 to 20
        Default: 1


        Note: For complete list of parameters refer to Setup Editor from PowerSCADA Editor.

        Creating an Aggregate Device within the KVM Access Software


        Issue

        How to create an aggregate device within the KVM Access Management Software and why it may be suggested to do so.


        Product Line

        KVM Switches
        • KVM Access Software (ships with KVMXXXX Digital IP KVMs)
        • KVM1116P
        • KVM2116P
        • KVM2132P


        Environment
        • Users wishing to consolidate nodes within their KVM Access Software
        • All software versions


        Cause

        Aggregate devices can be created when a device (router, server, ethernet switch, etc.,) managed through KVM Access is capable of being accessed through several devices’ ports. By consolidating those ports into a single Aggregate Device, the Aggregate Device counts as a single node, and only requires a single license.

        In the case of utilizing Rack PDU Power Integration, creating an aggregate device allows the end user to tie a PDU port/outlet and a KVM port together, making it easier for the end user to manage power to that specific server without having to guess at what PDU ports are tied to what KVM ports.

        The purpose behind the aggregate device is to allow an end user to tie devices together to make for ease of management through the Access Software.  When a user needs to shut down a specific server remotely they don't have to navigate through different screens to do the necessary power down, they can just access that specific aggregate device, shut down those PDU ports and they are done.

        Example: I have 300 node license but have 300 servers and 600 PDU ports/outlets for a total of 900 total target devices, (servers and PDU ports). Each server has a dual power supply so in full, I would need to purchase a 900 node license to cover all these ports. By creating an aggregate device, I can put in (2) KVM ports and (4) PDU ports/outlets together in each aggregate device effectively creating 150 nodes in total. By doing this, I am decreasing the amount of nodes I need to cover my entire environment.



        Resolution

        Refer to the instructions and steps below in order to successfully create an aggregate device within the KVM Access Software.
         

        How to Create an Aggregate Device
         

        1.) Within KVM Access, navigate to the Device Management section.

        2.) In the Devices menu, select <--Add--> and choose Aggregate Device.



        3.) Fill in the fields on the Add Aggregate Device Page, according to the notes below: 

        Field Explanation
        Auto Detect

        If you are adding one of the specifically mentioned Aggregate Device Model Types and enable Auto Detect, KVM Access will check if the device is online.
        Note: Only a user with administrator privileges can enable this function.

        Detect Interval

        Set the detect interval by entering a value in seconds. This is how often the system automatically checks that the Aggregate Device is online.

        IP

        Key in the Aggregate Device's IP address. Click Test Connection to confirm that the IP has been correctly detected.

        Connect Method

        Select either SSH or Telnet from the drop down menu.

        Port

        Key in the access port used to connect to it (via browser). The default SSH port is 22; Telnet is 23.

        Username/Password

        Key in a username and password that will be required to access the Aggregate Device.

        Login name field/password field

        Key in the information so that the KVM Access knows where to put the login name and password information under certain single sign on situations.

        Timeout

        The amount of time to wait for a connection request to complete before canceling the request.

        Server Select the KVM Access unit that the Aggregate Device server is connected under.


        4.) In the Configure Device Properties page, provide a name to identify the aggregate device in the Name field.



        5.) Optional:
        Provide a further description, department, location and/or type lists and click on the one(s) you want the Aggregate Device to belong to. Provide any additional information in the Contact Information field.

        6.) Set the Power Control Options as outlined below:

        • Click the box to enable confirmation for power operation
        • Click the box to enable delay for power operation, and set the power on/power off delay field in seconds.

          Note: If the device does not support this function, the option will not work.
        7.) When finished with this page, click Next. The Configure Network Connectivity page comes up.



        8.) Fill in the fields according to the information in the table below:
         
        Field Description
        Network Information

        Select network: If the server for the aggregate device only has one network interface, select Primary, then move on to configure the remaining fields. If it has more than one network interface, after you finish configuring the Primary one, come back to choose the additional ones and configure each of them in turn.
        Name: For convenience, each of the network interfaces can be named.
        IP Address: Enter the Aggregate Device's IP address here.
        Access Type: Use the drop down list to select the access type. The choices are Generic, Dell DRAC 5, Dell iDRAC 6, HP iLO2, and IBM RSAII. Only the Generic option supports VNC and RDP connectivity.
        Server: Select the KVM Access unit that the Aggregate Device server is connected under.

        Web Session URL: To access the Aggregate Device server via the web, key in the URL that will bring up its management page.
        Enable SSO: Check this box to enable single sign on functionality, and then select which credentials to use.
        • Select Use login user credentials to use the same account username and password as the KVM Access user account.
        • Select Use following credentials and enter new credentials in the fields below.
        Login name, password: Fill in these fields according to the Aggregate Device server's authentication and authorization procedures.
        Login name field/password field Key in the information so that the KVM Access knows where to put the login name and password information under certain single sign on situations
        SSH/Telnet Session IP Address, Login name, Password, SSH/Telnet port: To access the Aggregate Device server via an SSH/telnet session, key in the appropriate information into these fields according to the Aggregate Device server's authentication and authorization procedures.
        Note: An SSH session also requires entering login string information.
        VNC Session Port: Enter the port number for the VNC session
        Enable SSO: Check this box to enable single sign on functionality, and then enter View only and Full control passwords.
        RDP Session RDP Port: Enter the port number for the VNC session.
        Enable SSO: Check this box to enable single sign on functionality, and then select which credentials to use.
        • Select Use login user credentials to use the same account username and password as the KVM Access user account.
        • Select Use following credentials and enter new credentials in the fields below.
        SPM (Service Processor Management) SPM Method: Select from the drop down menu. Options are IPMI, Dell DRAC 5, Dell iDRAC 6, HP iLO2, or IBM RSA II.
        Port: Enter the port number for the SPM session
        Login name, password: Fill in these fields according to the SPM server's authentication authorization procedures.
        Timeout: Set the amount of time to wait for a connection request to complete before canceling the request.
         

         

        Adding Ports to an Aggregate Device

        1.) Select your Aggregate Device in the Device List or Sidebar. The Port List page comes up.

        2.) Click Add (at the top right of the panel). The Add Ports page appears and lists all the available ports that can be added.
         

        3.) You can combine any of the ports that are listed on the page in the Aggregate Device. Put a check in the checkbox in front of the ports that you want, then click Save.

        4.) If a port is already part of another aggregate or group device, a dialog box appears to notify you that it will be removed from the original device when added to this aggregate device and asks you to confirm that this is what you want to do. Click OK to accept the change or Cancel to abort.

        5.) When you return to the Port List page, the selected ports are automatically unlocked and are listed as being associated with the Aggregate Device. The ports are also nested under the Aggregate Device in the Sidebar.

        Notes:

        1. A port that has been made part of an aggregate device can only be used with that device. It cannot be assigned to any other device without being removed from the aggregate device.

        2. Once a port has been made part of an aggregate device, it is no longer treated as an individual port, and cannot be locked or unlocked manually. If at some point you want to treat this port as a physical port, or add it to a group device you must first delete it from the aggregate device.
         

        Additional Notes and FYIs:
         

        For a blade server: The server itself and every blade in it has to count. For example: Dell M1000e + 16 blades = 17 nodes

        But if the individual blade has connection to KVM Access directly, then the total nodes of KVM Port/Power Port will be reduced as the connection adds, but there are the following rules:

        • KVM port numbers can not be greater than 1.
        • Power port numbers can not be greater than 6.
        • Serial port numbers can not be greater than 1.
        All connection to KVM Access in the Aggregate Only section count as one node. The following rules need to be taken into account:
        • KVM port numbers can not be greater than 2.
        • Power port numbers can not be greater than 8.
        • Serial port numbers can not be greater than 4.
        In the case of the Dell M1000e, you cannot add the whole Blade Server, but you can add individual blades.