enclosure adapt pvc clr lid

Adaptable Enclosures, Adaptable Enclosure - L163 x W108 x H142mm

Catalogue Number: 764
enclosure adapt pvc clr lid
Colour: Grey
Colour: Per UOM Std.
  • Grey 1 PCE
Added to cart


hide show
Product brand
Range of product
Cover type
PVC (polyvinyl chloride): housing
108 mm
142 mm
163 mm
Device mounting
EU RoHS Directive
Toxic heavy metal free
Mercury free
RoHS exemption information
China RoHS Regulation
 Pro-active China RoHS declaration (out of China RoHS legal scope)

Frequently Asked Questions

hide show

Can I fit a 50A fuse in to a 63A PDL 760


Is the socket available for the Clipsal appliance plugs 464 & 465?

No, we don't have an offer for the socket

What is the IP rating for the 754HB2/180/60 sensor

IP44 rating, 754 series are suitable for outdoor use only

Is there a 200A version of the Busbar connection/Front wire HRC fuse carriers

 No the largest is the 100A which has a part code is PDL 765

How do I purchase the Hospitality Cards for a PDL626N?

Levco are the suppliers of Hospitality cards +64 9 444 0161

The card is not supplied in the PDL626N pack.

E3 error message on the Symmetra Extended Run Battery Frame (XR frame)


The XR frame of a single phase Symmetra displays E3; The mainframe indicates an XR Frame Fault.

Product Line

Symmetra Power Array
Symmetra RM
Symmetra LX


All serial ranges


The "E3" error message on the Symmetra XR Frame is an indication of lost communication between the Symmetra mainframe and the Symmetra Extended Run (XR) Battery Frame. This error message will cause a fault LED on the PowerView display and will result in the loss of communication between the two frames where the Power Array will not be able to recognize the batteries that are located in the XR Frame.

This condition is a communication issue only, and in no way affects the function of the UPS if it were to go on battery. In that event the UPS goes on battery, the runtime will be recalculated based on the on the additional ampacity provided by the Extended Run Frame.


Resetting the communication card on the Extended Run Frame will alleviate this communication issue. Please following the following steps in resetting the communication card on the Symmetra Extended Run Frame:

1) Disconnect the communication cable(s) in the card located in the back of the Symmetra Extended Run Battery Frame and wait for the green status light to go off.

2) Disconnect the communication cable(s) from the communications card by unscrewing the top right hand thumbscrew on the card so that the micro-latch that is being held by that thumbscrew is unseated.

3) Reseat the micro-latch on the card and screw in the thumbscrew back into the top right-hand corner of the card .

4) Reconnect the communication cable(s) in the back of the card and acknowledge the return of the green status light within 60 seconds the UPS will recognize the additional batteries and adjust the runtime value accordingly to include the batteries located in the Extended Run Frame.

At this point the E3 message should no longer be flashing on the XR Frame and on the PowerView you will see a message indicating "Number of Battery Modules Increase".  If for any reason this error message reoccurs, please contact technical support.

Is there a code for a busbar / back wiring fuse carrier ?

700 Series fuses ranges have been made obsolete early 2017 from the offers and are no longer available

Can I use the 754RFKIT with another range of sensors

754RFKIT is intended to be used in conjunction with the Clipsal 754 Series Infrascan Outdoor Motion Sensors product range only. 

What is the part number for 10mm earth terminal?

What is the screen resolution for the HMIPCCP172CB46T14N00?

The screen resolution for the HMIPCCP172CB46T14N00 is 1024 x 768

Does the Altistart ATS46 unit have kilowatt hour capability?

Issue: Does the Altistart ATS46 unit have kilowatt hour capability?
Product Line: ATS46
Environment: All
Cause: N/A
Resolution: No. Will probably need to use a power meter.


Timeout behavior of 140 DDO 364 00

Goals and Symptoms

The purpose of this resolution is to inform the user about an unexpected Timeout behavior of the Quantum Output module 140 DDO 364 00.

Facts and Changes

Quantum Output modules default in case of Timeout of communication to a PLC in general is Set to Zero.
Due to an incorrect default parameter of the 140 DDO 364 00, the Timeout behavior is Hold Last Value.

Affected Concept versions: Concept 2.2
Concept 2.5SR1
Concept 2.5SR2
Concept 2.6SR1

To change the Timeout behavior, the user has to open the Module Parameter screen and has to leave it by the OK button. To leave it by the Cancel button will not change the Timeout behavior.

Causes and Fixes

The Timeout default will be corrected with Concept 2.6SR2

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

Video: How to model breaker panels within StruxureWare Data Center Operation version 7.4 or newer?

How to model breaker panels within StruxureWare Data Center Operation version 7.4 or newer?

Product Line:
StruxureWare Data Center Operation

7.4.0 or newer


What is the maximum motor cable length for an ATV312?

What is the maximum cable distance from an ATV312 drive to the motor?

Product line:
ATV312, Altivar 312, ATV320, Altivar 320

All models


The ATV312 shows that an output filter or choke is required for any cable distance between the drive and motor exceeding 164 feet (50 meters).  Above 164 feet, there is a change with shielded vs non-shielded.

Shielded cables
From 164 feet to 330 feet (100 meters) you can use the LR filter cell or a motor choke.

Unshielded cables
From 164 feet to 660 feet (200 meters) you can use the LR filter cell or a motor choke.

What is the amperage rating of the power distribution block 9080LBA365212, 9080LBA265212, and 9080LBA165212?

Checking on the power distribution block 9080LBA365212, 9080LBA265212, and 9080LBA165212 amperage rating.

Product Line:

9080LBA365212, 9080LBA265212, and 9080LBA165212

It is 620 amps for aluminum wire and 760 amps for copper wire.


Minimum Polling Time for Advanced Device Crawlers


Minimum Polling Time for Advanced Device Crawlers

Product Line:



NetBotz version 2


Configuration options


The minimum polling time for Advanced Device Crawlers is 5 minutes.

Data Center Operation | Video: How to work with the Visual network management?

How to work with the Visual network management with version 7.4 or newer?

Product Line:
StruxureWare Data Center Operation

StruxureWare Data Center Operation (7.4.0 or newer)

StruxureWare Data Center Operation visual network management with version 7.4 or newer.


Below is a video on how  to work with the Visual network management​:

PSE 7.4 SR1 Web Client Cannot Display Waveform Captures or Alarm Filters Pop-up does not Display

The web client cannot display waveform captures from the server and/or alarm filter pop-up does not display

PowerSCADA Expert 7.4 SR1

PowerSCADA Expert 7.4 SR1

*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).*
Use the steps below to deploy the new PLS_Includes project to correct the issue. If details of the steps are required please refer to the PSE 7.4 User guide located in the documents section of the PSE install location.

1) Download the attached PLS_Include.ctz file
2) Backup the existing PLS_Includes project
3) Restore the PLS_Include project downloaded in step 1
4) Recompile the project and create a new web deployment
5) Verify that the web deployment was created and has the latest date
6) Run the project and verify that the waveform viewer works in a remote client's web browser.

Note: If you do not see the updated project on the remote client's Web Browser you will need to delete the Citect temp folder.  This file can be found by typing '%temp% in the run command section.

Connection limitations and reconnection issues for ION devices when using SER 7.4

Goals and Symptoms

Symptoms: Cannot connect to ION device using SER 7.4 or establishing connection very slow (up to ten minutes)

Keywords: SER 7.4, ION, Serial, ION reconnection, multiple connections

Causes and Fixes

Cause: ION Devices have connection limitations which may cause issues with SER 7.4 while simultaneously connecting from other software.
SER 7.4 supports connections to an ION 7550, ION 7650, and ION 8600. The ION 7550 and ION 7650 with firmware versions V360 or later support 8 direct TCP/IP connections. Earlier firmware versions of the ION 7550 and ION 7650 as well as all firmware versions of the ION 8600 only support 4 direct connections. For instance if ION E 6 Management Console, two ION Setup connections and a Telnet connection were all connected to a device limited to 4 direct connections, there would be a connection error in SER 7.4 when trying to communicate with that device.

ION Devices using the serial connection (Ethergate protocol) have a limitation of one. If any other connection is made to the device (ION E Management Console, ION Setup, Telnet….etc) then SER 7.4 will not be able to connect to the device.

When a connection to an ION device is restored, it may take up to 10 minutes to be established in SER 7.4.ION Devices have connection limitations which may cause issues with SER 7.4 while simultaneously connecting from other software.

Resolution: If a connection to an ION Device cannot be established, you can use Telnet to connect to the device to see how many connections are being used (note that Telnet itself will account for one connection). Telnet can only connect to ION devices directly through TCP/IP.

Legacy KB System (APS) Data: RESL205080 V1.0, Originally authored by MiZe on 04/14/2011, Last Edited by MiZe on 04/14/2011
Related ranges: Sequence of Events Recorder (SER)

How to transfer a Vijeo designer project from a PC with the OS Win 7 (64 bits) to a target type Magelis XBTGT1000 serie using XBTZG925 cable?

Goals and Symptoms

How to transfer a Vijeo designer project from a PC with the OS Win 7 (64 bits) to a target type Magelis XBTGT1000 serie using XBTZG925 cable?

Facts and Changes

When using Vijeo Designer V6.1 installed on a PC with the OS Windows 7 (64 bit) and a XBTGT1100 terminal : the problem is that we cannot install the XBTZG925 cable driver.

Causes and Fixes

This is a limitation. There is only a Win XP XBTZG925 cable driver.

The reason is that Marketing decided that the target type XBTGT1000 serie End Of Commercialization and End Of Service will be in end of 2012.
The solutions are:
1/ either edit the Vijeo designer project on a PC with Win XP Pro,
2/ either replace the XBTGT1000 serie by a terminal type XBTGT1005 serie,
3/ or replace the XBTGT1000 serie by a terminal type XBTGTO
Note that solutions 2/ & 3/ with new terminals are less expansive and higher quality.


Legacy KB System (APS) Data: RESL209008 V1.0, Originally authored by DaBr on 09/05/2012, Last Edited by DaBr on 09/05/2012
Related ranges: Magelis XBT GT

Will the eCatalogue work on my PC?

Your PC will need the following minimum requirements in order to properly run eCatalogue Edition 2:
  • Microsoft Windows XP SP3, Windows Vista or Windows 7
  • Graphics driver capable of displaying 16 Bit colour or higher
  • Microsoft Internet Explorer 8
  • Microsoft® Excel (not included)
  • Microsoft .NET Framework (Included)
  • Adobe® Shockwave® (Included)
  • Adobe® Flash® Player (Included)
  • Adobe® Reader®(Included)
  • 150MB of free hard disk space (for minimum installation)
  • 1024 x 768 display resolution
  • CD-ROM drive
  • Latest Printer Drivers

What are the minimum and maximum cable specifications for Remote I/O ( RIO )?

Maximum drop length is 164 feet.
Minimum drop length is 8.5 feet.
Maximum trunk length is 8400 feet using RG11 and 4600 feet using RG6.
Maximum overall attenuation for the network is 35 db.
Minimum distance between taps is 8.5 feet.
Minimum distance between the RIO head and the self terminating "F" adapter is 18 inches.
Minimum distance between the self terminating "F" adapter and splitter 8.5 feet.

Which Windows operating systems are compatible with the new MBX v8.1 driver suite.

The new MBX v8.1 driver suite is compatible with the following Windows operating systems:
MBX Component MBX Driver Virtual MBX Driver MBX Gateway Driver Ethernet MBX Driver
Windows 8 (32 bits)          x           x              x             x
Windows 8 (64 bits)          x           *              x             x
Windows 7 (32 bits)          x            x              x             x
Windows 7 (64 bits)          x           *              x             x
Windows Vista (32 bits)          x            x              x             x
Windows Vista (64 bits)          x            *              x             x
Windows XP (32 bits)          x            x              x             x
Windows XP (64 bits)          x            *              x             x
Windows Server 2012 (32 bits)          x            x              x             x
Windows Server 2012 (64 bits)          x            *              x             x
Windows Server 2008 (32 bits)          x            x              x             x
Windows Server 2008 (64 bits)          x            *              x             x
Windows Server 2003 (32 bits)          x            x              x             x
Windows Server 2003 (64 bits)          x            *              x             x

* 64-bit Windows operating systems do not support Virtual MBX Driver technology. However, Cyberlogic has provided support for the operation of the Virtual MBX Driver in 64-bit operating systems using 32-bit Windows XP under Virtual PCs, if enabled by the 64-bit operating system.


Comment fonctionne les compteurs d'energie de l'ATS48.

Goals and Symptoms

Comment fonctionne les compteurs d'énergie de l'ATS48.

Causes and Fixes

Il existe 2 compteurs:

- le compteur en kW ( puissance active ) de 0 à 999 kW;
- le compteur en kW/h qui nécessite le fonctionnement du démarreur pendant au moins une heure ( pour la première ). Son échelle est de 0 à 65535, soit 7,4 années ( 7j/7 et 24h/24 ).

Can you put the wireless interconnect base onto the 10 year lithium ion 755 Alarm?

No, you still need to have the 10 Year Lithium Iron unit connected to mains power.
This is to ensure that (A) The battery always remains charged and (B) so the unit is
always receiving power and complying with Regulation 76B under the Development Act, 1993,

"Houses built since 1 January 1995 must be equipped with hard-wired smoke alarms.
When a house with 9 volt battery powered smoke alarms is sold the new owner has
six months to install alarms which are hard-wired to the 240 volt power supply"

What is the MTBF for the M580 SFP socket 490NAC0100?

The MTBF values are in hours for 490NAC0100 as shown below
MTBF 30° Continuous MTBF 30° Intermittent MTBF 60° Continuous MTBF 60° Intermittent
13 386 328 5 767 152 8 620 000 4 783 955

What is the maximum motor lead length you can run the ATV320 drive without a load reactor?

What is the max cable length you can run the ATV320 drive without a load reactor?

Product Line:
Altivar 320


Motor cable length distance without a load reactor. 

The ATV320 drive can run up to 164 feet without load reactor.  
You can go up to 328 feet with shielded cable or up to 656 feet with an unshielded cable.
See the table in the attachment.

My Conext CL-NA shows event 704 AFD selftest fail. What should I do?

This event indicates that the Arc Fault Detector (AFD) in the inverter wiring box was unable to complete it's power on self test.  There are a few probable causes of this message

1) Ensure the inverter is configured for the correct wiring box that is installed with your system.  The AFD only ships in the PVSCL1825NA201 and PVSCL1825NA301 model of wiring box. 
2) Ensure the AFD communications cable is correctly plugged into the communications port of the inverter module. 
3) Upgrade the firmware on your inverter to v 2.04.14 or later. The latest firmware can be found in the downloads section on the product website:

Conext CL
Conext CL-NA 

If the issue persists, please contact your local Schneider Electric customer support office for additional troubleshooting.

NetBotz version 1 and 2 Appliances - MAC Address Ranges


NetBotz version 1 and 2 Appliances - MAC Address Ranges

Product Line:



NetBotz version 1 and 2


Mac address ranges.

  • 300
  • 300B
  • 303
  • 310
  • 320
  • 400
  • 420
  • 500 All NetBotz version 1 and 2 monitoring appliances have MAC addresses starting with: 00:02:D3:xx:xx:xx.

    NOTE: NetBotz Central servers have different MAC addresses and they vary depending on the model of NetBotz Central.

What are the system requirements for SoMachine Basic v1.5?

This software can be installed on a personal computer having the following hardware:
  • Processor                            Core 2 duo or better
  • RAM Memory                       2 GBytes or greater
  • Hard Disk                            600 MBytes
  • Display                                1280 x 768 pixels resolution or better
  • Peripherals                           Mouse or compatible pointing device
  • Peripherals                           USB interface
  • Web access                         Web registration requires Internet access

What operating systems, is SCADAPack RemoteConnect compatible with?

SCADAPack RemoteConnect is compatible with following operating systems.
  • Windows 7 Professional (32-bit or 64-bit), Windows 8.1 Professional (32-bit or 64-bit), or Windows 10 Professional (32-bit or 64-bit) operating system
Additionally, the machine should meet the following minimum requirement.
  • 5 GB available disk space
  • 2 GB RAM
  • 1366 x 768 minimum screen resolution
  • Microsoft .NET 3.5 runtime 
  • Microsoft .NET 4.6.1 runtime 
  • Administrator privileges on the SCADAPack RemoteConnect computer
Please refer to Readme file for system requirement for the latest version. 

Cannot connect to Sepam with SFT2841 V16.4 and I have other Schneider Electric software using the Modbus Driver

Cannot connect to Sepam with the SFT2841 software

Product Line
Sepam series 20
Sepam series 40
Sepam series 80

SFT2841 software
Windows 10
Windows 7

With the SFT2841 software version V16.4, a certain version of the Schneider Electric Modbus Driver is included with the installation package. If it is necessary to troubleshoot the Modbus Driver installation, some additional work may be required.

An issue may arise in some cases because there are other software applications developed by Schneider Electric that use the same Modbus Driver component as the SFT2841 software, and in some cases, they may use different versions of this component compared to SFT2841.

Please refer to FA279049 for initial steps to troubleshoot the connection to the Sepam unit

If your installation of the Sepam SFT2841 software V16.4 has completed without any error messages, but you still have problems connecting to your Sepam relay, you can try the following procedure.
  1. Access Windows Control Panel > Programs and Features > locate the DriverManager X64 and Modbus Driver X64   
  2. Un-install the SFT2841 software
  3. Manually uninstall the DriverManager X64 and Modbus Driver X64 identified in Step 1
  4. Reboot your computer/laptop
  5. Run the SFT2841 V16.4 installer again.  Alternatively, you can also use the BOX link below to download the Schneider Modbus Driver suite, which is current as of December 2018.
    • To reach the BOX link click here.
    • After a successful installation, one should see that the Modbus Driver has been installed again, and this version should be compatible with SFT2841
    • Internet access may be needed for the DriverManager X64 to be updated to the computer/laptop
  6. With your PC connected to the Internet, update the Sepam Serial Port driver through Windows, as shown in the image below.  Be sure that you wait until Windows has finished updating your Sepam Serial Port driver.
  7. One should now be able to connect to your Sepam device.
Please be aware that other Schneider Electric software that uses this Modbus Driver may not work after following this procedure. The standard practice for Schneider is to ensure the compatibility of the latest Modbus Driver version with all current software platforms.  So, normally a new version of both SFT2841 and your other Schneider program (e.g., PLC programming software) should be released later with a Modbus Driver version that is compatible.

Please contact the Sepam Technical Support if you are still having problems connecting to your relay.
For the latest version of SFT2841 please refer to FA180051.

In the 30072-450-61 manual for the ATS48 on page 76, it shows contacts for ``KM1`` & ``KM2``. What are they?

What is the meaning in the wiring diagram of the contacts labelled KM1 and KM2 feeding into the IC1 forward contactor and IC2 reverse contactor?

Product line:
Altistart 48, ATS48

All enclosed

Typo error in the instruction bulletin

This is an error in the manual.  KM1 should be labelled IC1 and KM2 should be labelled IC2.
These are auxiliary contacts from the forward and reverse isolation contactors, used for electrical interlocking.  This helps prevent closure of both contactors at the same time. 


Serial Terminal Connection Parameters for all NetBotz Appliances


Serial Terminal Connection Parameters for all NetBotz Appliances

Product Line:



Versions as described below
terminal emulation


Terminal emulation (ie. Hyper-Terminal) configuration for communications with NetBotz appliances.


Terminal emulation is often used for initial IP configuration on NetBotz appliances. Hyper-terminal or Putty are often used for this configuration.

Serial Terminal Connection Parameters for all NetBotz Appliances

When connecting to a Netbotz appliance or a NetBotz Central via a serial cable, the terminal settings must be set to:

38400 and 8-N-1

When connecting to a models 300, 303, 310, or 400, you must use a standard serial cable, such as the kind used to connect a modem to a PC.

When connecting to models 320, 420 or 500, you must use a NULL modem cable.

When connecting to models 355, 455, 550, 570 or similar version 3 Netbotz, you must use a USB A-B cable.

The NetBotz 200 uses a Null Modem cable and a baud rate of 9600.

NOTE: When connecting to a NetBotz Central, you must use a NULL modem cable.

PowerChute Network Shutdown version 4.3 fails to power off Hosts in a Stretch Cluster when the Witness host is powered off.

When the PowerChute Appliance is deployed to the same host that is running the vSAN Witness it shuts down this host before the other vSAN hosts if the Witness is powered off. This host should be the last to shut down.

Product Line:
PowerChute Network Shutdown version 4.3

PowerChute Network Shutdown VM installed same ESXi host as the vSAN Witness Appliance.

Witness host is off line when PowerChute initiates shut down process.

1. Download the attached pcns_vsan_ftt.tar file.
2. Copy pcns_vsan_ftt.tar on to the PowerChute VM
3. Log into the PowerChute VM as root
4. Uncompress the file. tar -xvf pcns_vsan_ftt.tar
5. Stop the PowerChute service systemctl stop PowerChute
6. Rename the original pcns.jar mv /opt/APC/PowerChute/group1/comp/pcns.jar  /opt/APC/PowerChute/group1/comp/original_pcns.jar
7. Next copy the uncompress pcns_vsan_fft.jar to the PowerChute directory cp pcns_vsan_ftt.jar /opt/APC/PowerChute/group1/comp/pcns.jar (Note: when the file is copied the name is changed from pcns_vsan_ftt.jar to pcns.jar)
9. Change to permissions of the new pcns.jar file chmod 664 /opt/APC/PowerChute/group1/comp/pcns.jar
8. Re-start the PowerChute service systemctl start PowerChute 


Why is PowerChute not shutting down my Windows system if I leave it at the system logon screen?

Why is PowerChute not shutting down my Windows system if I leave it at the system logon screen?

Product Line:
PowerChute Business Edition
PowerChute Network Shutdown

Windows Server 2003, Windows XP Professional x64 Edition, or Windows 2000 SP3 or late

If you leave the system at the Windows logon screen (user ID & password entry screen), neither PowerChute Business Edition nor PowerChute Network Shutdown can shutdown Windows during power failure or scheduled shutdown. It is a Windows' specification.

Under normal circumstance, you get the logon screen after CTRL+ALT+DEL and do not key in any data for about 30 seconds, the system will bring back the CTRL+ALT+DEL screen.


Do not enable the "Disable CTRL+ALT+DEL requirement for logon" option found in the Security option of Local Security settings tools in Administrative tools. Do not leave your system with the logon screen.
If you are running Windows XP Professional x64 Edition and it is not joined to a domain, follow the steps below to enable the CTRL+ALT+DEL screen.
Start gpedit.msc from the command prompt.
Select Local Computer Policy > Computer Configuration > Administrative Template> Logon
Enable the "Always use classic logon" option

Why is my Conext CL displaying an arc fault alert?

Why is my Conext CL displaying an arc fault alert?

Product Line:
Conext CL 3-phase grid-tie inverters

Conext CL with arc fault detection (wiring box 201 or 301)

The Conext CL is showing an arc fault alert, but none was detected in the PV array

First and foremost, be sure to differentiate between the two types of arc fault alerts:

1. Error code 709 - the unit has detected an arc fault condition
2. Error code 704 - the unit has determined that the arc fault detector is malfunctioning or improperly installed

To check these error codes, navigate to the Event Log menu and check for Active Services.
In either case, be sure that the correct wiring box is selected and the AFD/SPD harness is plugged in. This should solve most cases of error code 704.

If the fault code is 709, it should mean an arc fault was detected, but it can also be the result of other conditions:

1. Nuisance trips have been known to occur in firmware revisions 2.5.10 and below; check the Inverter Info menu for the current firmware on your unit.
2. Intermittent arc fault trips have been traced back to faulty wiring; ensure all DC connections are perfect, including the connection between the wiring box and the inverter. Also check the 1-4 connections on the AFD for proper seating, and check the light on the AFD itself.

If you're sure there is no arc fault in the system, and none of these solutions clear the fault, contact technical support at (866) 519-1470 for further troubleshooting.

PSE 7.4 Event will not Trigger and Cannot be Added to the Computer Setup Wizard

Events added to the Computer Setup Wizard do not save and are not executed during runtime. The name of the event was copied from Excel and pasted in the Project Editor Events Window.

StruxureWare SCADA Expert


When copying from excel there are at least two ways to copy the information:
1) Highlight the cell with the desired name and copy the cell
2) Highlight just the text in the cell.
Method 1 will include hidden characters that are added to the name filed. These additional characters will cause the event to not trigger nor be added to the Computer Setup Wizard.

Rename the event in the Project editor to remove the hidden characters.

How do I clear an overload condition with the Matrix-UPS?

My Matrix UPS shows an overload.  How do I clear this condition?

Product Line:
Matrix UPS

All serial ranges

The Matrix will signal overload if there is too much wattage or volt-amps (VA) being drawn by the connected load. 


The following must be done to clear an overload condition reported by a Matrix UPS:

1. Reduce the load (the connected equipment plugged into the back of the Matrix) on the UPS and follow the procedure below to reset the unit and clear the fault.

2. Reset the Electronics Unit (EU). This is done by loosening the EU separating screw (see section 3.1 of the Matrix User's Manual). The EU separating screw is attached to a slider - it will not fallout. Once the slider has popped out, the EU will power down causing front display to go dark, and the fans to stop spinning. (Note: when this is done, the Matrix-UPS will be in bypass mode. In this state, the load will be powered and surge protected; however, there is no battery backup). To restart the Matrix EU, tighten the separating screw and press any button under the front LCD display. Use the 'menu' button to get to "UPS Control" and the 'scroll' button to select "Out of Bypass". If the condition persists, completely remove all loads and repeat the above steps. If none of these steps resolve the problem, the Matrix Isolation unit may be at fault and may then need to be replaced.

Material Safety Data Sheets (MSDS) or Safety data Sheets (SDS) for Batteries Used in APC UPS Systems


I require the Material Safety Data Sheet (MSDS) or Safety Data Sheet (SDS)  for various APC UPS products.

Product Line:





The majority of batteries used in APC by Schneider Electric Uninterruptible Power Supply (UPS) systems and Replacement Battery Cartridges (RBCs) are contained within cartridges and are sealed, non-spillable, maintenance-free lead acid batteries. The batteries are amanufactured article consisting of a plastic, sealed case, terminals and flame arrestor vent caps. Case color varies. The electrolyte is contained within the case and consists of the electrolyte held captive in an adsorbed glass mat (AGM) or gel matrix. There is no “free” electrolyte to leak out of the case. Under normal use and handling, there is no contact with the internal components of the battery or the chemical hazards. Under normal use and handling, these products do not emit regulated or hazardous substances. The design life of a sealed lead acid battery is 3-5 years depending on environmental factors. Using the batteries past the end of it’s design life can result in electrolyte leakage.  

In a few cases, Replacement Battery Cartridges (RBCs) containing High Power Lithium Ion Cell, Phosphate-Based are also used. These batteries are used stricitly in select models found in the Back-UPS Connect family.



Updated Safety Data Sheets for batteries used in all APC products can be found on our Battery Compliance page.

What is the advantage of the Protected LED light modules in the new XB4 and XB5 22mm push button lines?

What are the characteristics of our XB4/XB5 light module?

Product Line:
Harmony Push Buttons

North American Products

The light module contains electronics to handle surges on the control system.
Specific characteristics and ratings of Protected LED light modules:

Surge withstand Conforming to IEC 61000-4-5 2/1 kV,
Resistance to fast transients Conforming to IEC 61000-4-4 2 kV
Resistance to electromagnetic fields, Conforming to IEC 61000-4-3 10 V/m
Resistance to electrostatic discharges, Specific Characteristics of Protected LED Light Modules Only

Voltage limits
Nominal voltage
24 V: 19.2 to 30 Vdc; 21.6 to 24.6 Vac
120 V: 102 to 132 Vac
240 V: 195 to 264 Vac

Current consumption Applicable to all colors
24 Vac/Vdc supply blocks: 18 mA
120 Vac supply blocks: 14 mA
240 Vac supply blocks: 14 mA

Service life At nominal voltage and at an ambient temperature of 77 F (25C)
100,000 hours

Resistance to electrostatic discharges, Conforming to IEC 61000-4-2 8/6 kV,
Electromagnetic emission Conforming to EN 55011 Class B
Conforming to IEC 61000-4-2 8/6 kV


What are the Twido Compact power supply specifications?

The following table provides power supply information for the Compact controller.

Power supply voltage Rated power voltage; 100 to 240 vac.
Allowable range; 85 to 264 vac.
Failure - depends on quantity of used inputs and output points. Generally, failure is detected when voltage drops below 85 vac, stopping operation to prevent malfunction.
NOTE: Momentary power interruption for 20 ms or less at 100 to 240 vac is not recognized as a failure.
Inrush current flow at power-up TWDLCAA10DRF and TWDLCAA16DRF 35 Amp maximum
TWDLCAA24DRF 40 Amps maximum
Power supply wiring UL1015 AWG22 (0.64 mm) or UL1007 AWG18 (1.02mm) Make the power supply wiring as short as possible.
Ground wiring UL1007 AWG16 (1.30 mm) Do not connect ground wire in common with ground wore of motor EQUIPMENT.

Note: The Twido is obsolete and has been replaced with the M221, for more information on this contact your local distributor or Schneider Electric sales.

Why does my keypad not allow me to change the contrast on the ATV61 and ATV71?

Cannot change contrast

Product Line:
ATV61, ATV71

All models and serial numbers

The menu 7.4 Keypad parameters is accessible if access level is set to Advanced or Expert.  The value of the contrast parameters, standby time are stored in the keypad and not in the drive.  Check the software version of the drive if it's an old version these parameters might not appears.

Purchase current version level keypads.

PowerSCADA Expert (PSE) ION Protocol Help File

Setting up/Troubleshooting an ION protocol device in PowerSCADA Expert (PSE).

Product Line:
PowerSCADA Expert 7.30
PowerSCADA Expert 7.40
PowerSCADA Expert 8.0

PSE projects with ION protocol devices. 

Since the ION protocol is newly supported by PSE, it is useful to have a help document that describes how the ION devices communicate and how their tags are addressed. 

Attached is the help file for the ION Driver. Some of the key topics that this help file covers are: Configuring Variable Tags, Supported Data Types, .ini Parameters, and Ethergate connections.

PowerChute Network Shutdown Fails to Install on RHEL 5.10 and RHEL 5.11

PCNS fails to install on RHEL 5.10 and RHEL 5.11 after running install.sh
The following error message appears:
Error: dl failure on line 863
Error: failed /opt/APC/PowerChute/jre1.7.0_45/lib/i386/client/libjvm.so, because /opt/APC/PowerChute/jre1.7.0_45/lib/i386/client/libjvm.so: cannot restore segment prot after reloc: Permission denied.
Product Line:
PowerChute Network Shutdown
OS: RHEL 5.10 and RHEL 5.11 x86
Build: PCNS 3.1, 3.2, 4.0, 4.1, 4.2

NOTE: Does not occur on x64 systems and on systems with Latest versions of Java. 
This problem is caused by SELinux enforcing an access policy. The policy forbids the installer from changing the attributes for memory protection of a memory segment.
RedHat Enterprise Linux has a SELinux set to “Enforcing” mode by default.
  1. Upgrade JRE to 1.8.0_121 or 1.8.0_131 on RHEL 5.10 and 5.11 x86 systems.
  2. Install PCNS using the above JRE.

Troubleshooting - Usb PLC Service does not start and I cannot connect my PC to my Modicon PLC via USB cable

Troubleshooting - When I try to connect my Modicon PLC to my computer via USB connection, the Windows USB driver cannot detect it and the "Usb PLC" service does not start.

Product Line
EcoStruxure Machine Expert (SoMachine v4.1+, SoMachine Basic): Modicon M238, M241, M251, M258, LMC058, M221 PLCs
EcoStruxure Control Expert (Unity Pro v12+): Modicon M340, M580 PLCs
Schneider Electric PLCUsb Driver x64 Suite

Windows 10, USB Drivers

This FAQ will go through some troubleshooting steps on this topic specifically if the Usb PLC Windows Service does not run.

Before going through the following steps, please contact Schneider Electric Support to obtain the latest 'PLCUsb Driver X64' Suite. This Microsoft signed driver package is compatible with all PLC families from EcoStruxure Machine Expert (SoMachine) and EcoStruxure Control Expert (Unity Pro).

A) Check if the 'Usb PLC' service is running:
  1. Click the Windows Start button.
  2. Run "Services.msc".
  3. Scroll down to the Service names that start with the letter 'U'.
  4. In the row named "Usb PLC", check the  Status column.
  5. If the Status column is blank, right click on the row and choose "Start".
  6. If this is not possible or an error appears, check the Startup Type, is it blank?
  7. If so, Right-click on the row and go to Properties.
  8. Change the Startup Type to Manual, and Start the Service with the Start button.
  9. If an error appears "Windows could not start the Usb PLC service on Local Computer. Error 2: The system cannot find the file specified." go to the next set of steps.
B) Check whether or not UsbConnect.exe and UsbConsole.exe are running:
  1. Right-click on the Windows Taskbar and choose "Task Manager" (or Ctrl+Alt+Delete and choose "Task Manager")
  2. Go to the Details Tab in the Windows Task Manager.
  3. Scroll down to the process names starting with the letter 'U'
  4. Check if 'UsbConnect.exe' and 'UsbConsole' are running.
  5. If they are not running, go to C:\Windows\System32\ to see if UsbConnect.exe and UsbConsole.exe appear at this folder level. If they do not,
C) If these conditions two occur: (A.9) "The system cannot find the file specified" and (B.5): both UsbConnect.exe andUsbConsole.exe do not exist in the C:\Windows\System32\ folder,
we will need to remove the 'Usb PLC' service from Windows:
  1. Unplug the USB cable from your PC
  2. Close the File Explorer open to "C:\Windows\System32\".
  3. Close the Services window (services.msc).
  4. Run CMD in Administrator Mode.
  5. If the location is not already 'C:\WINDOWS\System32\', change the directory with the command: cd C:\windows\system32\
  6. Type: sc delete "Usb PLC"
  7. Hit the Enter key. This will remove the Usb PLC service from your computer's registry.
  8. Run services.msc, once again to confirm it is removed.
D) Next, we will uninstall the Schneider Electric 'PLCUsb Driver X64' suite:
  1. Go to Windows Control Panel-> Programs and Features.
  2. Find "PLCUsb Driver X64".
  3. Right-click on it and Uninstall.
  4. Restart your PC.
E) Install the PLCUsb Driver X64 suite.
  1. Install the new PLCUsb Driver X64 suite.
  2. Restart your PC.
  3. Go to Services.msc and check that the 'Usb PLC' service is Running.
  4. Go to Task Manager and check that 'UsbConnect.exe' and 'UsbConsole.exe" are running.
  5. Plug in the USB cable connecting the PLC to your PC.
  6. Go to Windows Device Manager.
  7. Expand the 'Modem' node.
  8. If there is a yellow triangle by the node of the PLC, right-click on that node and "Uninstall Device".
  9. Once the device disappears from your Device Manager, unplug the PLC's USB cable from your PC.
  10. Wait 30 seconds.
  11. Plug the PLC back into the USB port of the PC.
At this point, you should be able to connect to the PLC using its respective configuration software (EcoStruxure Machine Expert / SoMachine or EcoStruxure Control Expert / Unity Pro).
If the issue persists after these troubleshooting steps, please contact Schneider Electric Customer Care.

“Failed dependency error on terminal” during PowerChute Business Edition 8.0.1, 9.0.x, 9.1.x and 9.2.x installation on Red Hat Enterprise Linux 6.x, 7.x and Oracle Linux 7.3

The installation requires 32-bit libraries (glibc) to be available on an x64 system.

Product Line: 
PowerChute Business Edition  versions 8.0.1, 9.0, 9.0.1, 9.0.2, 9.0.3, 9.1.x, 9.2.0, 9.2.1, 9.0.4

Red Hat Enterprise Linux (RHEL) versions 6.x and 7.x
Oracle Linux 7.3

32 bit libraries used by PowerChute missing in the x64 Operating System installation.

Please follow the steps below to ensure that 32-bit libraries are available on your x64 system: 
For RHEL 6.0, 6.1, 6.2, 6.3
1.     Registered Red Hat Network (RHN) users:
Download the Red Hat Package Manager (RPM). For more information see:https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/compilers.html
Download the following packages from RHN:
  •         "glibc-x.xx-x.xx.xxx.xxxx.rpm"
  •         "nss-softokn-freebl-x.xx.x-x.xxx.xxxx.rpm"
Non-registered users, copy the packages listed above to your desktop from the Packages folder on the CD of one of the following, depending on your RHEL version:
  • RHEL_6.0 X86_64
  •  RHEL_6.1 X86_64
  • RHEL_6.2 X86_64
  • RHEL_6.3 X86_64
2.     Navigate to the files’ location and type the command:

yum localinstall --disablerepo=* glibc-x.xx-x.xx.xxx.xxxx.rpm  nss-softokn-freebl-x.xx.x-x.xxx.xxxx.rpm

(Replace x with the relevant package numbering for your RHEL version). 
If you see the following message on the command line:
“Public key for nss-softokn-freebl-x.xx.x-x.x.xxx.xxxx.rpm is not installed”
then, add --nogpgcheck to the command line to disable public key verification (see below):

yum localinstall --nogpgcheck --disablerepo=* glibc-x.xx-x.xx.xxx.xxxx.rpm  nss-softokn-freebl-x.xx.x-x.xxx.xxxx.rpm
3.     When prompted, type “y”.
4.     Install PowerChute versions prior to 9.1 using:
rpm -i pbeagent<version>.rpm
            Install PowerChute versions 9.1 and higher using
 Red Hat Version glibc nss-softokn
 RHEL 6.0  glibc-2.12-1.7.el6.i686.rpm  nss-softokn-freebl-3.12.7-1.1.el6.i686.rpm
 RHEL 6.1  glibc-2.12-1.25.el6.i686.rpm   nss-softokn-freebl-3.12.9-3.el6.i686.rpm
 RHEL 6.2  glibc-2.12-1.47.el6.i686.rpm      nss-softokn-freebl-3.12.9-11.el6.i686.rpm
 RHEL 6.3  glibc-2.12-1.80.el6.i686.rpm      nss-softokn-freebl-3.12.9-11.el6.i686.rpm
Table 1: Red Hat versions 6.0, 6.1, 6.2, 6.3 and associated packages.
For RHEL 6.4, 6.5, 6.6, 6.7, 6.8, and 7.x
1. Registered Red Hat Network (RHN) users, download the following packages from RHN:
  • "glibc-x.xx-x.xx.xxx.xxxx.rpm"
  •  "nss-softokn-freebl-x.xx.x-x.xxx.xxxx.rpm"
  •  “libstdc++-x.x.x-x.xxx.xxx.rpm”
  •  “libgcc-x.x.x-x.xxx.xxxx.rpm”
Non-registered users, copy the packages listed above to your desktop from the Packages folder on the CD of RHEL_6.4 X86_64
3.     Navigate to the files’ location and type the following commands:
yum localinstall --disablerepo=* glibc-x.xx-x.xx.xxx.xxxx.rpm nss-softokn-freebl-x.xx.x-x.xxx.xxxx.rpm
yum localinstall --disablerepo=* libstdc++-x.x.x-x.xxx.xxx.rpm libgcc-x.x.x-x.xxx.xxxx.rpm
(Replace x with the relevant package numbering for your RHEL version).
5.     When prompted, type “y”.
6.     Install PowerChute versions prior to 9.1 using
        rpm -i pbeagent<version>.rpm
            Install PowerChute versions 9.1 and higher using
 RHEL 6.4 Packages  
 glibc glibc-2.12-1.7.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.12.7-1.1.el6.i686.rpm
 libstdc++ libstdc++-4.4.7-3.el6.i686.rpm
 Libgcc libgcc-4.4.7-3.el6.i686.rpm
Table 2: Red Hat versions 6.4 and associated packages.

 RHEL 6.5 Packages  
 glibc glibc-2.12-1.132.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-9.el6.i686.rpm
 libstdc++ libstdc++-4.4.7-4.el6.i686.rpm
 Libgcc libgcc-4.4.7-4.el6.i686.rpm
 Table 3: Red Hat versions 6.5 and associated packages.

 RHEL 6.6 Packages  
 glibc glibc-2.12-1.149.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-17.el6.i686.rpm
 libstdc++ libstdc++-4.4.7-11.el6.i686.rpm
 libgcc libgcc-4.4.7-11.el6.i686.rpm
 Table 4: Red Hat versions 6.6 and associated packages.
 RHEL 6.7 Packages  
 glibc glibc-2.12-1.166.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-22.el6_6.i686.rpm 
 libstdc++ libstdc++-4.4.7-16.el6.i686.rpm
 libgcc libgcc-4.4.7-16.el6.i686.rpm
 Table 5: Red Hat versions 6.7 and associated packages.
 RHEL 6.8 Packages  
 glibc glibc-2.12-1.192.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-23.el6_6.i686.rpm 
 libstdc++ libstdc++-4.4.7-17.el6.i686.rpm
 libgcc libgcc-4.4.7-17.el6.i686.rpm
 Table 6: Red Hat versions 6.8 and associated packages.
RHEL 6.9 Packages  
 glibc glibc-2.12-1.209.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-23.el6_8.i686.rpm 
 libstdc++ libstdc++-4.4.7-18.el6.i686.rpm
 libgcc libgcc-4.4.7-18.el6.i686.rpm
 Table 7: Red Hat versions 6.9 and associated packages.
 RHEL 6.10 Packages  
 glibc glibc-2.12-1.212.el6.i686.rpm
 nss-softokn nss-softokn-freebl-3.14.3-23.3.el6_8.i686.rpm 
 libstdc++ libstdc++-4.4.7-23.el6.i686.rpm
 libgcc libgcc-4.4.7-23.el6.i686.rpm
 Table 8: Red Hat versions 6.10 and associated packages.
 RHEL 7.0 Packages  
 glibc glibc-2.17-55.el7.i686.rpm
 nss-softokn nss-softokn-freebl-3.15.4-2.el7.i686.rpm
 libstdc++ libstdc++-4.8.2-16.el7.i686.rpm
 Libgcc libgcc-4.8.2-16.el7.i686.rpm
 Table 9: Red Hat versions 7.0 and associated packages.

 RHEL 7.1 Packages  
 glibc glibc-2.17-78.el7.i686.rpm
 nss-softokn nss-softokn-freebl-
 libstdc++ libstdc++4.8.3-9.el7.i686.rpm
 Libgcc libgcc-4.8.3-9.el7.i686.rpm
 Table 10: Red Hat versions 7.1 and associated packages.
 RHEL 7.2 Packages  
 glibc glibc-2.17-105.el7.i686.rpm
 nss-softokn nss-softokn-freebl-
 libstdc++ libstdc++4.8.5-4.el7.i686.rpm
 Libgcc libgcc-4.8.5-4.el7.i686.rpm
 Table 11: Red Hat versions 7.2 and associated packages.
 RHEL 7.3 & Oracle 7.3
 glibc glibc-2.17-157.el7.i686.rpm
 nss-softokn nss-softokn-freebl-
 libstdc++ libstdc++4.8.5-11.el7.i686.rpm
 Libgcc libgcc-4.8.5-11.el7.i686.rpm
 Table 12: Red Hat versions 7.3, & Oracle Linux 7.3 and associated packages.
 RHEL 7.4 Packages  
 glibc glibc-2.17-196.el7.i686.rpm
 nss-softokn nss-softokn-freebl-3.28.3-6.el7.i686.rpm
 libstdc++ libstdc++4.8.5-16.el7.i686.rpm
 Libgcc libgcc-4.8.5-16.el7.i686.rpm
 Table 13: Red Hat versions 7.4 and associated packages.
 RHEL 7.5 Packages  
 glibc glibc-2.17-222.el7.i686.rpm
 nss-softokn nss-softokn-freebl-3.34.0-2.el7.i686.rpm
 libstdc++ libstdc++4.8.5-28.el7.i686.rpm
 Libgcc libgcc-4.8.5-28.el7.i686.rpm
 Table 14: Red Hat versions 7.5 and associated packages.
 RHEL 7.6 Packages  
 glibc glibc-2.17-260.el7.i686.rpm
 nss-softokn nss-softokn-freebl-3.36.0-5.el7_5.i686.rpm
 libstdc++ libstdc++-4.8.5-36.el7.i686.rpm
 Libgcc libgcc-4.8.5-36.el7.i686.rpm
 Table 15: Red Hat versions 7.6 and associated packages.
 RHEL 7.7 Packages  
 glibc glibc-2.17-292.el7.i686.rpm
 nss-softokn nss-softokn-freebl-3.44.0-5.el7.i686.rpm
 libstdc++ libstdc++-4.8.5-39.el7.i686.rpm
 Libgcc libgcc-4.8.5-39.el7.i686.rpm
 Table 16: Red Hat versions 7.7 and associated packages.

PowerChute Network Shutdown unable to communicate with the NMC if the username is greater than 10 characters.

PowerChute Network Shutdown unable to communicate with the NMC if the username is greater than 10 characters.

PowerChute Network Shutdown (PCNS)

Network Management Card 2 (NMC2) firmware AOS 5.1.1 and above. SKUs AP9630, AP9631, AP9635

With the latest release of Network Management Card 2 (NMC2) firmware AOS 5.1.1, with APPs SUMX/SY/SY3P 5.1.0, the NMC2 username can now be up to 64 bytes in length. (64 byte maximum supports up to 64 ASCII characters; Less for multi-byte languages OS). This was previously restricted to 10 characters and PowerChute Network Shutdown (PCNS)  will still only be able to communicate with the NMC if the username is 10 characters or less. The PowerChute installers do not restrict the number of characters that a user can enter for the username nor do they provide any warnings about the max length.

If the user configures the NMC2 username to be greater than 10 characters and does the same in PowerChute side, they will receive an error when trying to register with the NMC - "Security information did not match information at <IP Address>".


What is the replacement for the Modicon Premium TSXDSY64T2K 64 discrete output module?

What is the replacement for the Modicon Premium TSXDSY64T2K 64 discrete output module?

Product Line
Modicon Premium I/O Modules

The TSXDSY64T2K (64 output discrete output module) for Modicon Premium PLCs does not have a direct replacement in the same product line.
It's replacement is th BMXDDO6402K (Discrete output module M340 - 64 outputs - solid state - 24 V DC positive) for the Modicon M340 line of PLCs (for Unity Pro configuration software):

A new PLC in the Modicon M340 line would need to be purchased and configured to use this BMXDDO6402K.
See the following for information on the M340 line of PLCs:

What is the power rating differences between the 8660 Alphapak and the 8660 SSRVS style starters?

Issue: What is the power rating differences between the 8660 Alphapak and the 8660 SSRVS style starters?
Product Line: 8660 AlphaPak starters
Environment: All
The currect rating abbreviations were:
Alphapak`s SSRVS`s
MD (16 amps) MG (120 amps)
ME (32 amps) MH (200 amps)
MF (64 amps) MJ (320 amps)
MG (128 amps) MK (500 amps)
MM (750 amps).

They voltage codes were:
Alphapak`s SSRVS`s
23 (208 / 230 volts) 11 (200 volts)
46 (380 / 460 volts) 22 (230 /460 volts)
57 (500 / 575 volts) 33 (500 / 575 volts).  NOTE The 8660 AlphaPak SSRVS are obsolete.  Parts, Service, or Support are no longer available.

Show More