End cover comb busbar

Acti 9 Busbar Side Covers, 2 Set of 40 Comb, 3P+N for Clario, Librio, Prodis

Catalogue Number: 21095
End cover comb busbar
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range of product
  • ProDis
  • Clario
  • Librio
    • Range
      Acti 9
      Product name
      Linergy FH
      Product or component type
      comb busbar side cover
      Accessory / separate part category
      insulation accessory
      Poles description
      3P + N
      Quantity per set
      set of 40
      Range compatibility
    • Multi 9 N40 N40N comb busbar
    • Multi 9 N40 Vigi N40 Vigi comb busbar
      • Product compatibility
      • DT60
      • C40
      • DT40
      • iDPN
        • Device presentation
          cuttable
          Distribution type
        • 3 L
        • N + 3 L
          • Market segment
            small commercial
            REACh Regulation
            Free of Substances of Very High Concern above the threshold
            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)
            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

            • Technical Data Catalogues

            • Catalog Page

            • Technical Leaflet

            • Product Environmental

            • Handout

            • Installation Instruction

            • End of Life Manual

            • Data Bulletin

            • Specification for Tender

            • Application Solutions

            • Certificates (MSDS)

            • Declaration of Conformity

            • Marine Certificate

            • Software - Released

            Frequently Asked Questions

            hide show

            What is the replacement for the mistral fan 6109?

            The replacement is the 7106A you will also need the wall plate 7100WP.

            Is the 81295 MG plug and socket available in NZ

             Not supported in NZ

            What is the extended rotary handle for a 31146

            The part code is 31055

            Can you get the Magelis XBTGT range with Conformal Coating?

            Yes, the product offering for Conformal Coating on the XBTGT line will be available in 6 Steps:


            Conformal Coating Service for XBTGT 5.7, Sell stage gate in 10th July 2009: XBTGT2110, XBTGT2120, XBTGT2130, XBTGT2220, XBTGT2330

            Conformal Coating Service for XBTGT 12.1, Sell stage gate in 1st August 2009: XBTGT6330, XBTGT6340

            Conformal Coating Service for XBTGT 10.4, Sell stage gate in 1st September 2009: XBTGT5230, XBTGT5330, XBTGT5340

            Conformal Coating Service for XBTGT 3.8, Sell stage gate in 1st October 2009: XBTGT1105, XBTGT1135, XBTGT1335

            Conformal Coating Service for XBTGT 15, Sell stage gate in 1st November 2009: XBTGT7340

            Conformal Coating Service for XBTGT 7.5, Sell stage gate in 1st December 2009: XBTGT4230, XBTGT4330, XBTGT4340

            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).
             

            What are the Commercial and Government Entity (CAGE) codes for Schneider Electric (Canada only)?


            Issue
            What are the Commercial and Government Entity (CAGE) codes for Schneider Electric (Canada only)?

            Product Line
            CAGE codes

            Environment
            CAGE code is a unique identifier

            Cause
            CAGE codes provide a standardized method of identifying a given facility at a specific location.

            Resolution
            The CAGE codes for Schneider Electric/Square D are listed below:

            CAGE Code Company Address
            L0154 POWER MEASUREMENT LTD 2195 KEATING CROSS RD SAANICHTON, BC V8M 2A5

            What are the markings for the Extended rotary handle on a single handle transfer switch?

            They are labelled: I ON 1, O OFF, I ON 2
             

            Can Power Supply ABL7RM 24025 be din rail mounted?

            Yes, ABL7RM24025 can be din rail mounted, it also has 2 x 4mm panel mount holes.

             

            Netbotz user information changes require a reboot if user info is also used for SNMP version 3 credentials.

            "

            User names and passwords are also used when configuring version 3 SNMP credentials. If the credentials are changed, they will not take effect until the Netbotz appliance is rebooted.

            This is a known issue and for version 3 Netbotz devices and is fixed in Botzware 3.2.

            Version 2 Netbotz must be rebooted and there is no fix scheduled.

            "

            What is the Clipsal 5470

            This is a keyless entry system that Clipsal used to sell until approximately 2009. The key cards used for this are no longer available but work off of 134.2KHz frequency.

            This was a product which Clipsal rebadged from Axeze. Please see the below links for datasheets

            https://axeze.com.au/wp-content/uploads/2015/06/Datasheet-AT-C-01.pdf

            https://axeze.com.au/wp-content/uploads/2015/06/Datasheet-KES-I.pdf

            What is the alternative for a Main switch (surface) 3 phase T300-BK?

            The original T300-BK was unfortunately discontinued. As an alternative the T300FA is very similar. The Majority of its components are the same but some specifications may vary.
            Some of the key features are:
            • Panel mount
            • 300 Amp rated
            • Triple pole
            • Front wiring cover
            • Has dimensions of 210mm (L) x 158mm (W) x 112mm (D)
            For Further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=T300FA

            Or see PDF attached below.
             

            FCL Current Transformers

            Issue
            Customer needs split-core CT with an amperage rating greater than 2400 A

            Product Line
            Model FCL Current Transformers

            Environment
            Current Transformers

            Resolution
            Model FCL Current Transformers have current ratios from 200/5 to 6000/5 A. They are a split-core type current transformer.

            Please find cutsheet for Model FCL Current Transformers attached. 

             For quotes for FCL CTs please contact sales.

            Data Center Expert | Performing an SNMPwalk

            Issue:
            Instructions for performing a walk file for StruxureWare Data Center Expert DDF files or if requested by technical support.

            Product Line:
            InfraStruXure Central (ISXC)
            StruxureWare Central (SWC)
            StruxureWare Data Center Expert (DCE)

            Environment:
            ISXC, SWC, & DCE (all versions)
            Device Definition File (DDF) creation

            Resolution:

            If your Data Center Expert (DCE) appliance is running version 7.6.0 or greater, an SNMPwalk can be done from the web interface.  Instructions can be found in the following Help Center article:
            https://sxwhelpcenter.ecostruxureit.com/x/oY4SC​

            Instructions for performing an SNMP walk (outside of DCE 7.6+) can now be found here:
            https://sxwhelpcenter.ecostruxureit.com/x/4JpUBg


             

            What does Warning 2107 means in Vijeo Designer?

             Title

             What does Warning 2107 means in Vijeo Designer

            Issue

             

            Product Line

             Vijeo Designer

            Environment

             

            Cause

            Resolution

            Warning 2107: Target Security is enabled, and Web Gate security is disabled. You cannot write to variables from Web Gate.

            This message displays when you have set Target Security to Use Security, and Web Gate Security is disabled. You need to enable Web Gate security so you can properly log in and  write to variables from Web Gate.

             

            To resolve the warning message:

            In the security properties for the target, enable the Web Gate/Web Server Security property by setting it to Use Security.

             

            Com'X 200 Gateway (EBX 200) firmware upgrade fails when upgrading to version 2.0.5 or later

            Issue
            Com'X 200 firmware upgrade fails when upgrading from a version prior to 1.46 to firmware version 2.0.5 or later.

            Product Line
            Com'X 200 Gateway

            Environment
            Firmware upgrade

            Cause
            "Signed Firmware" was introduced in version 1.1.20. 

            Resolution
            If the current version of firmware is prior to 1.1.20, you must first be upgrade to version 1.1.20 then to 1.4.6. Afterwards, the Com'X 200 firmware can be upgraded to 2.05 or later.

            The firmware can be upgraded through the Com'X web page.
            1. Once logged in to the Com'X web page, select the 'Maintenance' tab.
            2. Click on the 'System Settings' tab on the left-hand side of the screen.
            3. Click on 'No file chosen' and select the firmware upgrade file.
            4. Finally, click on the 'Upgrade firmware' button.
            Kindly refer to the FAQ below for the steps on upgrading the com'x firmware and the latest firmware:
            Latest firmware version: FA270260
            How to upgrade: FA270261


            All mentioned firmware versions are attached below and available here.
             

            How to change the display settings of energy units from MWh to kWh in ME Meter.

            Depending on the ME meter version, meter will automatically select the appropriate units and therefore it is not possible to modify the energy units. From 40/5 to 150/5 CT ratio, the energy unit display is KWh and from 200/5 to 6000/5 CT ratio, the energy unit display is MWh.

            CT Setting:
            To change the CT settings hold down the button on the Front Face of the ME Meter for more than 5 sec when on the CT Rating display. After approximately 5 sec the display will start blinking, now enter the CT setting. Once again hold the button till the display stop flashing, to ensure that the entry is saved.

            RAE Systems Sensor Compatability with Version 3 NetBotz Appliances

            Issue:

            RAE Systems Sensor Compatability with Version 3 NetBotz Appliances

            Product Line:

            NetBotz

            Environment:

            NetBotz version 3 appliances
            RAE systems sensors

            Cause:

            Compatibility with 3rd party sensors.

            Resolution:

            As of the release of our Next Generation (v3) NetBotz appliances in April 2009, RAE Systems sensors are no longer supported for direct integration on NetBotz appliances with Botzware 3.x or higher

            Configuring the Windows SNMP Agent for use with PowerChute Business Edition versions 9.2.1 and below

            Issue:
            How to configure Windows SNMP Agent for use with PowerChute Business Edition

            Product:
            PowerChute Business Edition versions 9.2.1 and below.
            NOTE: PowerChute Business Edition version 9.5 and above include SNMP therefore SNMP Windows service is no longer used. 

            Environment:
            Supported Windows

            Cause:
            Informational

            Solution:
             
            1. In Windows XP and Windows 2003 click Start button, then go to Control Panel and run Add or Remove Programs. In the Add or Remove Programs window, click Add/Remove Windows Components to open Windows Components wizard.

              In Windows  Vista and above, click Start button, then go to Control Panel. Click on Programs And Features link and then click on Turn Windows features on or off. If you're prompted with User Account Control dialog, click "Continue".

            2. In Components of Windows XP and 2003, click on the Management and Monitoring Tools (make sure that you do not select or clear, tick or untick its check box to change the existing selection), and then click Details.

              In Windows Vista and above, locate Simple Network Management Protocol (SNMP).

            3. Select and tick the check box of Simple Network Management Protocol or SNMP feature.
            4. Click OK. Also click Next if you're in Windows XP or 2003. SNMP service will be installed on the system. You may require to insert the Windows setup CD/DVD disc into optical drive.
            5. SNMP will start automatically after installation. But it's recommended to verify the service status from Services in Control Panel, and if it's stopped, you can start the SNMP service from there.

              Two new services will be created:

              1. SNMP Service which is the main engine with agents that monitor the activity in the network devices and report the information to the monitoring console workstation.
              2. SNMP Trap Service which receives trap messages generated by local or remote SNMP agents and forwards the messages to SNMP management programs running on this computer.

            Windows doesn't assign any community string to the SNMP service by default, and also only allow access from localhost or local devices. Further configuration is needed to add in desired community string, which act as the password to grant reply to any SNMP request from remote system.

            Configuring the Windows SNMP Agent for use with PowerChute Business Edition or PowerChute Plus with the PowerNet Agent:

            1. Go to Control Panel->Administration Tools->Services->SNMP service. The following screen will appear. The startup type should be set to automatic.

             



            2. Click on the Agent tab, make sure all service boxes are checked, enter any relevant contact information and location information here:

             



            3. Click on the security tab, enter the appropriate read, and read-write community names to the accepted community names list. In the lower box, click "Accept SNMP packets from these hosts" and click the add button. The IP Address or Host Name of the ISX Central(or other NMS) should be entered. This will enhance security allowing only ISX Central or another NMS to access information via SNMP.

             



            4. Click the Traps tab, and you can create your own trap community name and manually enter the IP Address of ISX Central(or other NMS) as a trap destination.

             



            5.) Click "Apply". Following these configuration changes, it is best practice to verify the functionality of the software SNMP agent using a SNMP utility or network management system. Using an NMS or SNMP utility, query the OID .iso.org.dod.internet.mgmt.mib-2.system.sysDescr (.1.3.6.1.2.1.1.1) to verify the system description (note: this is a standard MIB-2 OID, no other MIB is required). The return string for a Intel/Microsoft SNMP agent should be something similar to: ""Hardware: x86 Family 6 Model 7 Stepping 3 AT/AT COMPATIBLE - Software: Windows 2000 Version 5.0 (Build 2195 Uniprocessor Free)"".

            6.) Install PowerChute Business Edition. If PowerChute Business Edition was installed prior to this configuration, it is necessary to uninstall PowerChute Business Edition, reboot the machine, and then install the software. The SNMP agent MUST be properly installed and configured PRIOR to the installation of PowerChute Business Edition.

            7.) Once PowerChute Business Edition has been install log into the Console - Double Click on the Agent (to view device properties)- Select Show Advanced Items - Communications - SNMP Communications - Enable SNMP Communications:

             

             

             

            When access is enabled, use the Minimum SNMP Trap Severity setting to select what events will cause an SNMP trap to be sent. The default is Informational which will send traps for all levels.

            PowerSCADA Expert 8.2 Update 5 - Release Notes

            Issue
            What is new in PSE8.2 and a detailed listing of resolved problems and minor enhancements.

            Product Line
            PowerSCADA Expert 8.2 (PSE8.2)

            Environment
            Installer
             
            Cause
            A new PSE8.2 cumulative update release.

            Resolution
            PowerSCADA Expert 8.2 Update 5 - Release Notes
            Release Notification (Updated 25 April 2018)

            This is a detailed listing of resolved issues and minor enhancements in this release.

             


             

            Prerequisite

            You must have PowerSCADA 8.2 installed prior to installing this update. No previous updates are required.

            Cybersecurity Announcement

            Floating License Manager v2.1 addresses vulnerabilities in the Flexera FlexNet Publisher component detailed in CVE-2016-10395, CVE-2017-5571 and CVE-2016-2177. Uninstall the current version of the Floating License Manager, and then install version 2.1.
            NOTE: The Floating License Manager v2.1 installer is included with this hotfix release but is not a part of the hotfix installer. Unzip "Floating License Manager v2.1.zip" and run "setup.exe".

            Important Notice: There is a known issue with the Floating License Manager v2.1.0.0 installer. When installing with a logged-in Windows User name containing a space, the install will not succeed. The workaround is to install the Floating License Manager with a user that does not include a space character in their name.

            Bug Fixes and Enhancements

            TFS 21482 - AlarmEvents with a state of normal returned in GetAlarmEvents response for EWS

            GetAlarmEvents was changed to not return alarms in the normal state.

            TFS 21483 - Incorrect timestamp information provided for AlarmEvents not in the Active state

            Alarm timestamps are now updated to reflect the true timestamp of occurrence for all state changes (active, drop out, acknowledge).

            TFS 21484 - Unable to filter AlarmEvents by Type using EWS

            Alarms are now filtered based on type. 

            TFS 21485 - Unable to successfully acknowledge alarms using EWS

            In some situations, EWS would not acknowledge alarms correctly.  This behavior has been fixed.

            TFS 21486 - Unable to filter alarms using the PriorityTo and PriorityFrom fields

            EWS did not observe the priority field correctly. This has been addressed and the minimum allowable priority has been set to 1 (to exclude non-alarm objects in the PowerSCADA alarm database).

            TFS 21557 - PowerSCADA projects - including the starter project, PLS_Include, and PLS_Example - need to be upgraded to support the new DBF schemas

            PowerSCADA projects have been upgraded to the latest DBF schemas.  If there are existing projects created from the starter project, set [CtEdit] Upgrade = 1 in the Citect.ini file using the Setup Editor, and then restart PowerSCADA Studio.

            TFS 21564 - Alarm Proxy does not show the analog alarm states

            Alarm Proxy now reports the analog alarm states (HIGH HIGH, HIGH, LOW, LOW LOW) instead of ON / OFF.

            TFS 21566 - If a CSV file that does not exist is selected in the I/O Device Manager, the application throws a runtime exception

             

            A message is displayed indicating that the file does not exist.

             

            TFS 21569 - On large systems with 200k configured alarms, the GetAlarmDefinitions call in Alarm Proxy is slow and causes ENM to timeout

            Performance issue in alarm proxy has been resolved.

            TFS 21649 - When CoreServiceHost adds and removes devices, it may lose the original IDs

            CoreServiceHost now keeps a device chronicle.  When the device is removed and then later added, the ID will remain the same.

            TFS 21913 - If the equipment name is changed in the system, but the I/O Device name is unchanged, CoreServiceHost will not refresh the equipment name

            CoreServiceHost now properly updates the equipment on name change.

            TFS 21935 - Logs that are too large for the Windows Event Log do not get logged properly

            Large logs are now broken down into smaller log entries.

            TFS 21970 - Profile Wizard and Automation does not support IPv6

            Profile Wizard and Automation now supports IPv6 for TCP/IP Board level drivers.  This requires the TCP/IP Driver version 4.0.0.0 or later.

            TFS 21975 - Open and Close buttons are disabled at runtime on equipment popup when separate digital tags are used for commands

            The form now enables the command buttons if the Pos_On or Pos_Off tags are defined.

            TFS 21979 - Alarm Proxy cannot return alarms that transition to inactive

            This setting is now configurable in the Application Configuration Utility.

            TFS 22043 - Single sign-on calls from a remote thick client do not work

            Single sign-on now detects remote clients.

            TFS 22060 - The I/O Device Manager cannot bulk import devices with device names greater than 16 characters

            The I/O Device Manager now reads the device name length from the equipment.profiles file for proper validation.

            TFS 22066 - Wonderware ArchestrA Logger Security Patch

            Wonderware ArchestrA Logger Patch 2017.517.2328.1 is applied.

            TFS 22150 - Alarm filters do not work on some resolutions

            Alarm filter AN numbers are fixed for all alarm page resolutions.

            TFS 22155 - Alarm filters perform exact matching

            The alarm filter screen allows the user to select the filtering mode. The default setting is read from the INI file [Alarm] FilterMode.  0 (default) = Exact Match, 1 = Starts With, 2 = Ends With, 3 = Contains.

            TFS 22306 - The equipment tree used on alarm pages is slow to render over the web client

            Any page using the equipment tree should set the default library and symbol on the equipment tree genie, or set 'Hide Symbol Icons' to 'TRUE' if a default icon is not available.

            TFS 22401 - Alarm filter and equipment tree filter operate independently

            The alarm filter and equipment tree filter operate together to filter the alarm tables.

            TFS 22896 - Core service host logs two warnings during shutdown - exception thrown during disposal.

             

            Cleanup methods were reworked to prevent the exception.

             

            TFS 22898 - EWS cannot obtain tag updates at a 5 second rate

            EWS and core services were updated to obtain data at a 5 second poll rate.

            TFS 23262 - Equipment popup alarm table does not acknowledge or disable alarms

            Alarms can now be acknowledged or disabled in the equipment page.

            TFS 23274 - Equipment.profiles cannot be imported into the Profile Editor in cases where the original Device Types and Device Profiles were lost

            The Profile Editor can import the equipment.profiles file to generate device types, device profiles, and tags.

            TFS 23437 - Citect 2016 Updates

             

            Citect 2016 Update (April 10, 2018) is included with this update.

            Project ID management was removed from Citect 2016.  Project IDs are now located in the ProjectInfo.xml file. 

            MinUnitNumber and MaxUnitNumber (previously stored in UnitNumberRange.xml) have also been migrated to ProjectInfo.xml.

             

            TFS 23637 - The Alarm Summary page does not display state information

            The Alarm Summary page now displays the state that caused the alarm.

            TFS 23650 - 8.2 install does not enable ASP feature within IIS

            The installer now enables the ASP feature under IIS. This server role feature is required to run the Citect web control client. (Previously the View-Only web client was the only option for web deployment.)

            TFS 24205 - When Core Services receives a timeout from the Client, alarm processing may halt until the service is restarted

            Core Services properly recovers from a ctApi deadlock condition.

            Files Modified

            Applications\AppServices\bin\Framework.dll
            Applications\AppServices\bin\Framework.ServiceHost.exe
            Applications\AppServices\bin\Modules.CoreServices.dll
            Applications\AppServices\bin\PowerLogic.Cipher.dll
            Applications\AppServices\bin\Modules.ProviderBase.dll
            Applications\AppServices\bin\Modules.ProviderEngine.TestHarness.exe
            Applications\AppServices\bin\ObjectFactoryTools.exe
            Applications\AppServices\bin\ProviderGatewayProviders.dll
            Applications\AppServices\bin\PowerSCADA.Common.dll
            Applications\AppServices\bin\Modules.Platform.Citect.dll
            Applications\EWS\bin\Framework.dll
            Applications\EWS\bin\EWS.dll
            Applications\EWS\Web.config
            Applications\EWS\DataExchange.svc
            bin\de\ProfileEngine.resources.dll
            bin\de\ProfileWizard.resources.dll
            bin\de\WizardLibrary.resources.dll
            bin\es\ProfileEngine.resources.dll
            bin\es\ProfileWizard.resources.dll
            bin\es\WizardLibrary.resources.dll
            bin\fr\ProfileEngine.resources.dll
            bin\fr\ProfileWizard.resources.dll
            bin\fr\WizardLibrary.resources.dll
            bin\it\ProfileEngine.resources.dll
            bin\it\ProfileWizard.resources.dll
            bin\it\WizardLibrary.resources.dll
            bin\ja\ProfileEngine.resources.dll
            bin\ja\ProfileWizard.resources.dll
            bin\ja\WizardLibrary.resources.dll
            bin\ko\ProfileEngine.resources.dll
            bin\ko\ProfileWizard.resources.dll
            bin\ko\WizardLibrary.resources.dll
            bin\ru\ProfileEngine.resources.dll
            bin\ru\ProfileWizard.resources.dll
            bin\ru\WizardLibrary.resources.dll
            bin\zh-chs\ProfileEngine.resources.dll
            bin\zh-chs\ProfileWizard.resources.dll
            bin\zh-chs\WizardLibrary.resources.dll
            bin\zh-cht\ProfileEngine.resources.dll
            bin\zh-cht\ProfileWizard.resources.dll
            bin\zh-cht\WizardLibrary.resources.dll
            bin\ProfileAutomation.dll
            bin\ProfileEngine.dll
            bin\ProfileWizard.exe
            bin\WizardLibrary.dll
            bin\ProfileAutomationUtility.exe
            bin\CommsMethodProperties.xml
            bin\DeviceManagementUserControlLibrary.dll
            Applications\Profile Editor\Tags.xml
            Applications\Profile Editor\ProfileEditor.Business.dll
            Applications\Profile Editor\ProfileEditor.exe
            Applications\Profile Editor\ProfileEditor.UserControls.dll
            Applications\Profile Editor\Resources\ProfileEditor.UserControls.resources
            User\PLS_Include\*
            User\PLS_Example\*
            Starter\Default_Starter.ctz

            Installation

            Unzip "PowerSCADA Expert 8.2 Update 5.zip" and run "PowerSCADA Expert 8.2 Update 5.exe".

            List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

            Issue:

            List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

            Product Line:

            NetBotz

            Environment:

            NetBotz version 2

            Cause:

            Supported configurations

            Resolution:

            The following is the list of available device definition files (DDF) as of March 2009. Available DDF files:

            APC
            Alcatel
            Avaya
            Best Power
            Cisco Systems
            Compaq
            DMTF
            Dell
            Extreme Networks
            Foundry Networks
            IBM
            Juniper Networks
            Kohler
            Liebert
            MGE
            MIB2-UPS
            Mitsubishi
            NetBotz
            Powerware
            Server Technology
            Sun Microsystems


            Erroneous Switch Gear Messages from a Network Management Card 2 & Galaxy 3500 UPS


            Issue

            Upon closing the mechanical bypass switch on a Galaxy 3500 UPS, the Network Management Card 2 (AP9630/30CH & AP9631/31CH) will report an "Internal Mechnical Bypass" alarm, which is expected. A user may also see "The External Switch Gear Q003 has closed" in the event log.



            Product Line
            • UPS Network Management Card 2
              • AP9630/30CH, AP9631/31CH

            • MGE Galaxy 3500 3ph UPS
              • All models


                 
            Environment

            • All serial numbers
            • All sumx application firmware versions for NMC2


            Cause

            This is an erroneous alarm and will be fixed in a future firmware release.



            Resolution

            If you're experiencing these erroneous messages, upgrade your Network Management Card 2 firmware, when available. A release that fixes this issue is still to be determined.

            PTZ or motion detection functions on an existing Pelco camera no longer work through NetBotz appliance after upgrade to 3.3

            Issue:

            PTZ or motion detection functions on an existing Pelco camera no longer work through NetBotz appliance after upgrade to 3.3

            Product Line:

            NetBotz

            Environment:

            NetBotz 3.3. upgrade

            Cause / Resolution:

            If after upgrading from 3.2.x to 3.3.x, the PTZ or motion detection functions on an existing Pelco camera no longer work the camera has to be removed and re-added and shared. Possible cause is that the user upgraded to 3.3.x Advanced View but did not upgrade to 3.3.x on the appliance and then added the camera. The user should upgrade both Advanced View and the appliance before adding the Pelco camera. An existing camera added with matching software and firmware will not have this issue.

            StruxureWare Central reports NetBotz sensor values when the device is actually offline

            Issue:

            StruxureWare Central reports NetBotz sensor values when the device is actually offline

            Product Line:

            StruxureWare Central / Data Center Expert

            Environment:

            StruxureWare Central / Data Center Expert any version 7.x

            Cause:
            Data collection.

            Resolution:

            Based upon the manner that we collect historical data from NetBotz appliances at a configurable scheduled interval, the appliance will report it's last known value until a further data collect takes place. In the event that the device is offline for a period of time, last known values are still reported and just the link status is listed as unplugged. When the NetBotz appliance comes back online, a subsequent data collection will occur, updating the sensor values and returning the link status sensors to online. Unlike with an SNMP device and polling the current value, StruxureWare pulls all data on a NetBotz appliance since the last poll.

            In the case of a Virtual Sensor on StruxureWare Central 7.x, if all contributing sensors are NetBotz appliances in an offline state, the value will not be recalculated until at least one appliance returns to an online state. This is reflected by the 'Retrieved At' time stamp for the Virtual Sensor.
             

            User can not successfully log into PowerChute Network Shutdown client via a web browser.

            Issue:
            Browser reports "Page cannot be displays" or the user is repeatedly asked to re-enter their login information when attempting to log into PowerChute Network Shutdown (PCNS) client via a web browser, though a correct user name and password has been entered. Upon login, the username and password form fields are cleared, and the user is not logged in.

            Product Line:
            PowerChute Network Shutdown

            Environment:
            Web browser

            Cause:
            This will occur if cookies are blocked in the browser settings.

            Solution:
            To resolve the issue in the browser:
             
            Internet Explorer - go to Tools > Internet Options > Privacy > Sites Button. Enter the IP address of the system running the PCNS client that is being blocked and click "Allow".
             
            Chrome - Settings > Show Advanced Settings > Privacy > Content Settings> Cookies > Manage Exceptions. Enter the IP address of the system running the PCNS client that is being blocked and click "Allow".
             
            Firefox - cookies are not blocked by default in Firefox.
             
            Safari - cookies are not blocked by default in Safari.
             
             
            You should now be able to successfully log in to PowerChute via the web browser.
             

            When installing the PowerChute Business Edition Server, the configuration wizard does not launch on Windows Storage Server 2008 or Windows Small Business Server 2008.

            Issue:
            When installing the PowerChute Business Edition Server, the configuration wizard does not launch

            Product:
            PowerChute Business Edition

            Environment:
            Windows Storage Server 2008 or Windows Small Business Server 2008

            Cause:
            The 8.3 file name format is not supported by default on these two operating systems but the wizard needs it enabled in order to run correctly.

            For information on Windows 8.3 file naming convention please see Windows File and Directory Names

            Solution:

            To enable this format on Windows Storage Server 2008 and Windows Small Business Server 2008, follow these steps:

            1. Type this at the command prompt with administrator privileges.

                 C:\>fsutil behavior set disable8dot3 0

            2. Reboot Windows

            3. Confirm the enabling of the 8.3 file name format by typing this and pressing Enter:

                C:\>fsutil behavior query disable8dot3
                
                The following should then display.     disable8dot3 = 0

            (If it states"" = 1"", then 8.3 is still not enabled, please repeat).
             

            Can I reset the ATV600 or ATV900 Process Drive without cycling power to it?

            Issue:
            Customer would like to restart (reboot) the drive without having to cycle power.

            Product Line:
            ATV630
            ATV660
            ATV930
            ATV960

            Environment:
            All Models, All serial numbers

            Cause:
            Restart to clear errors or load new communication parameter settings usually requires a power cycle.

            Resolution:
             
            If connected via a network; you can write a value of 21072 to address 1500 it will reboot the drive as if it had been power cycled.

            If connected to the drive via SoMove you can go to the Device menu and select Restart Device.
            You can also use the HMI to do this by going to Complete Settings - Error/Warning Handling - and change the Product Restart (rP) to YES and press and hold the OK button for 2 seconds.
            Also, a digital input can be assigned to perform this by setting the Prod Restart Assign (rPA) to one of the DI's in the same menu as above.

            NOTE:  The Product Restart and Prod Restart Assign parameters are only available if the Access Level has been set to Expert.

            171CCC9x0x0 M1E Processor 984LL Exec. Upgrade to v.1.30 - Enhancement: Manual TCP/IP retransmission timer for MSTR

            Goals and Symptoms

            The purpose of this resolution is to inform Momentum M1E users that the 984LL Exec. has been upgraded (Aug. 2009) to version 1.30.

            Facts and Changes

            984LL Exec version 1.30 contains the following enhancement:
            1) A configurable TCP/IP retransmission timer for the MSTR function block.

            • The following units affected by this firmware are:
              • 171CCC96020 Processor
                171CCC98020 Processor
                171CCC96030 Processor
                171CCC98030 Processor
            • This enhancement is not supported in the Concept MSTR DX Zoom screens at this time.
            • Resource file MSTR.URF for ProWORX NxT and resource file MSTR.UCS for ProWORX32 are included.

            Causes and Fixes

            A description of the new MSTR function is explained in the attachment Resolution document.

            The attached zip file contains the following files:
            m1ev130.bin M1E firmware
            m1 v130 Resolution.doc Resolution
            MSTR.ucs ProWORX32 resource file
            MSTR urf ProWORX NxT resource file

            Attachments



            (Removed File URL: 199568_C68E/M1ev130.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/6b02aed0302b04aec125760b00528fdc/fl_block_5/0.574?OpenElement&FieldElemFormat=gif)

             


            Legacy KB System (APS) Data: RESL199568 V1.0, Originally authored by DaDz on 08/07/2009, Last Edited by DaDz on 08/07/2009
            Related ranges: Modicon Momentum

            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).
             

            PowerChute Network Shutdown & "Security Information Mismatch" error message


            Issue

            PowerChute Network Shutdown & "Security Information Mismatch" error message between PowerChute and UPS Network Management Card 2.



            Product Line

            • UPS Network Management Card 2
              • AP9630/30CH
              • AP9631/31CH
              • AP9635/35CH

            • PowerChute Network Shutdown
              • All versions


            Environment

            • All serial numbers
            • NMC2 application firmware < v5.1.5

            Cause


            Update: This specific issue was resolved in application version v5.1.5 and higher. Please upgrade your Network Management Card 2 firmware to avoid it.

            In regards to a UPS Network Management Card's (AP9630/AP9631/AP9635) PowerChute Configuration screen (UPS Tab->Powerchute->Configuration), if a user clicks or selects the "Apply" button, whether or not you actually change any data on the menu, it will result in corrupting the Network Management Card's Authentication Phrase which will cause a "Security Information Mismatch"" error message if a user decides to install Powerchute Network Shutdown.

            Furthermore, if a PowerChute Network Shutdown client is already set up and installed, clicking this "Apply" button will result in a lost communication message in the Powerchute Network Shutdown client's event log - "PowerChute cannot communicate with the Management Card."


            Resolution

            In order to fix this, the Authentication Phrase will need to be re-entered in the Network Management Card interface.

             

            Can I poll 6 Digit Modbus registers with Telepace Studio?

            The MSTR and MSIP use a block of registers to store their configurations.

            If the MSTR block uses register 41001 in the SCADAPack as it's configuration start register, then :

            41001 = Comm port number

            41002 = function code

            41003 = slave controller address

            41004 = slave register address

            41005 = master register address

            41006 = length

            41007 = time out in 0.1s increments

            Trying to configure the MSTR block in Telepace prevents you from putting in a slave register address greater than 49999.

            Using a PUTU block, you can put an unsigned integer in the range 40001-65535 into register 41004 to indicate the slave register address. It appears as though the program will take the value in register 40004 and subtract 40001 to determine the holding register offset that gets sent in the actual modbus message.

            For example, using PUTU to put a value of 50010 into register 40004 would then cause the MSTR block to poll for a holding register with an offset of 10009 in the message which would correspond with a 6 digit address of register 410010.

            The largest unsigned integer you could put into register 40004 would be 65535, which would correspond with a 6-digit modbus holding register of 425535.



             

            Updated: Why is my Network Management Card losing SNMPv3 communication?


            Issue

            My Network Management Card (NMC) is losing SNMPv3 connectivity after a certain amount of time but other communication protocols (web, FTP, SSH, Telnet, SNMPv1, etc) continue to work properly.


            Product Line

             

            • Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619
              Devices with an embedded Network Management Card 1 include (but are not limited to): Metered/Switched Rack PDUs (AP78XX, AP79XX), Rack Automatic Transfer Switches (AP77XX, Environmental Monitoring Units (AP9320, AP9340, NetBotz 200)
               
            • Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH
              Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP86XX, AP88XX, AP89XX), Certain Audio/Video Network Management Enabled products.
               
            Environment
             
            • All serial numbers
            • Any device listed above utilizing SNMPv3
            • NMC1 AOS v3.7.0 and below; NMC2 AOS v5.0.X and below
            • NMC1 AOS v3.7.3 and higher


            Cause

            An issue has been identified with the SNMPv3 task on Network Management Card 1 and 2 based devices. SNMPv3 communication will be lost after approximately 49 days and 17 hours. The NMC will continue to run normally, with the exception of the SNMP process, which will not run.


            Resolution

            Update (July, 2016): Specific to NMC1 products, this issue had previously been fixed for AOS 3.7.3 and higher. The maximum SNMPv3 uptime allowed was modfied from 49.7 days to 497 days. At the 497 uptime day mark, assuming the management uptime had reached this point, the Network Management Card interface would have had to be rebooted though the web, CLI, or SNMPv1 interfaces in order to regain SNMPv3 communication. NMC2 AOS v5.1.X also contained a fix to avoid an SNMPv3 communication loss completely.

            With NMC1 AOS v3.9.2 and higher, this issue has been fully resolved and the 497 uptime limitation has been lifted and SNMPv3 communication through StruxureWare Data Center Expert or any third party SNMPv3 NMS will not be affected after 497 days of uptime. This AOS (or newer) will be released for different firmware applications in the coming months which are available at https://www.apc.com/tt/en/tools/download/. Certain applications are available immediately, such as Rack PDU.
             

            Video: Battery Installation of APC AV Power Conditioners with Battery Back-Up

            Issue:
            How to install and connect the battery in a APC Power Conditioner with Battery Back-Up at first time start-up or following routine battery replacement.

            Product Line:
            APC AV Power Conditioners with Battery Back-UP
            S20BLK
            S15BLK
            S10BLK
            J15BLK
            J10BLK

            Environment:
            All models and serial number ranges.

            Cause:
            Battery must be installed and connected for proper device protection during power outages and interruptions. This is most common upon initial set-up or following a routine replacement of an end-of-life battery.

            Resolution:
            In accordance with APC’s interpretation of U.S. Department of Transportation regulations, APC ships this device with the internal battery pack disconnected. The front bezel of the unit is also not attached to the unit when shipped. This procedure provides for connection of the battery when the front bezel has been prematurely installed onto the chassis. Connect the internal battery pack as follows:



            1. Grasp the front panel at the sides (Figure 4), and pull the front bezel from the unit.



            2. Push the Battery Wire Connec