White Electric | Flush Plates - Standard Range, Architrave Size, Switch Plate 2 Gang (75 x 32mm)

Issue:
What is the process for ordering a Masterpact NW or NT circuit breaker?

Product Line:
Circuit Breakers

Resolution:
Masterpact circuit breakers cannot be ordered by catalog number.  A Schneider distributor or sales office must enter the order via the online product selector in My Schneider, SE Advantage, or Quote to Cash.
Information they need includes the certification standard (UL, ANSI, IEC), fixed or drawout, ampacity, AIR required, trip unit functions or type, accessories, connectors, and other customer specifications.

The attached decoder will assist in breaking down a catalog number to its component parts.  With knowledge of the breaker's construction it will be possible to use the Q2C or SE Advantage product selector to select, quote, and order the breaker.  DO NOT try to build a catalog number using the decoder.  A number generated using the decoder will be prone to error due to possibly selecting components and features which are mutually exclusive, and the number will have no value for quotation or ordering even if valid.

Required information for placing an order can be found on the attached RFQ (Request for Quote) or RFQ - DC for DC rated Masterpacts.

Issue:
What is Schneider Electric software support policy?

Product Lines:
PowerChute Network Shutdown (PCNS),
PowerChute Business Edition (PCBE),
PowerChute Personal Edition (PCPE),
PowerChute Plus (PC+)

Environment:
All supported OS

Cause:
Informational

Solution:
When new versions of software are released, Schneider Electric will continue to provide full technical support to customers for the previous version for a minimum of 1 year after the new version is released. In practice, Schneider Electric typically goes far beyond this stated commitment, but this 1-year policy is stated here so customers may take it into account for planning purposes.

• The current shipping version of PowerChute Network Shutdown is 4.4.x It was release October 2020
  • NOTE: support is continuing for PCNS 4.2 for 32 bit systems, and PCNS v4.3 for 64-bit systems.
• The current shipping version of PowerChute Business Edition is 10.0.5 It was release February 2022
  • NOTE: support is continuing for PCBE 9.5 for 32 bit systems. 
• The current shipping version of PowerChute personal Edition is 3.1 It was release June 2019 
• PowerChute Plus was discontinued March 2007

Issue

RADIUS set up with APC Network Management Card enabled products.

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 ATS (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 (AP84xx, AP86XX, AP88XX, AP89XX), Rack ATS (AP44xx), Certain SmartUPS online (SRT) Certain Audio/Video Network Management Enabled products.

• ​​​​​​​Network Management Card 3 (NMC3) - AP9640/AP9641/AP9643

Devices with an embedded Network Management Card 3 include (but are not limited to): Certain 2G Metered/Switched RackPDU's manufactured after 2021 (AP84xx, AP86xx, AP88xx, AP89xx), APDU9XXX RackPDU's, RackATS (AP44xxA), Certain SmartUPS online (SRT)

• Network Management Card 4 (NMC4) - AP9644

Environment
 

• All serial numbers
• Firmware versions v2.X.X and higher

Cause

Configuration can vary based on the RADIUS server being used. Below is a successful configuration taken from a FreeRADIUS server. Though this configuration worked through testing, APC by Schneider Electric cannot guarantee that this configuration will work on your RADIUS server. Configuring of your RADIUS server should be provided by your RADIUS server administrator.

Note: Further information on using the specific variety of FreeRADIUS (v2.1.10) included in Zentyal Linux 3.3 is also available in knowledge base article ID FA232648.

Resolution

The three files that need to be edited in order for FreeRADIUS to authenticate properly are:

1) clients.conf
2) dictionary
3) users file

Below are examples of entries that should be entered into each file.

1) clients.conf

client xxx.xxx.xxx.xxx (you would enter the IP address or IP address range of devices authenticating through RADIUS)
secret = radius
shortname = apc

2) dictionary

VENDOR APC 318

BEGIN-VENDOR APC

ATTRIBUTE APC-Service-Type 1 integer APC

VALUE APC-Service-Type Admin 1
VALUE APC-Service-Type Device 2
VALUE APC-Service-Type ReadOnly 3

3) users

# APC local radius authentication (working)
apcradius (username) Auth-Type := Local, User-Password == "apcradius"
     APC-Service-Type = 1

Once these entries are made, you should be able to access your APC product via RADIUS authentication.

In some cases, you do need to specify Vendor Specific Attributes. For example, APC part number AP7900 (Switched Rack PDU) uses the same login accounts as listed in the previous example. However, the AP7900 also allows specific outlets to have their own separate accounts/logins. Therefore, you must create additional entries in the event that a user has a login for specific outlets.

1) clients.conf

client xxx.xxx.xxx.xxx {IP address or IP address range of devices using RADIUS authentication}
secret = radius
shortname = ap7900

2) dictionary

VENDOR APC 318

BEGIN-VENDOR APC

ATTRIBUTE APC-Service-Type 1 integer APC
ATTRIBUTE APC-Outlets 2 string APC

VALUE APC-Service-Type Admin 1
VALUE APC-Service-Type Device 2
VALUE APC-Service-Type ReadOnly 3
VALUE APC-Service-Type Outlet 4

3) users

VSAAdmin Auth-Type = Local, Password = "admin"
     APC-Service-Type = Admin

VSADevice Auth-Type = Local, Password = "device"
     APC-Service-Type = Device

VSAReadOnly Auth-Type = Local, Password = "readonly"
     APC-Service-Type = ReadOnly

userA Auth-Type = Local, Password = "apc"
     APC-Service-Type = Outlet, APC-Outlets = "1,3,5"

userB Auth-Type = Local, Password = "apc"
     APC-Service-Type = Outlet, APC-Outlets = "1,2,3,4,5,6,7,8"

UserA will now have access to outlets 1,3,5 and userB will have access to outlets 1,2,3,4,5,6,7,8.

RADIUS and Network Port Sharing with Switched Rack PDU 2G (AP86XX, AP89XX)

Note: See the Security Handbook for APC Network Management Cards for more information on using RADIUS.

For RADIUS users file with VSAs, outlets on guest Rack PDUs can be associated to RADIUS users by using the following method.

# give user access to outlets 1, 2, and 3 on PDU 1,
# outlet 7 on PDU 2, outlets 1 through 6
# on PDU 3, and outlets 1,2,4 through 6, 7 through 10,
# and 20 on PDU 4

newOutletUser Auth-Type = Local, User-Password = "newoutlets"
APC-Service-Type = Outlet,
APC-Outlets = "1[1,2,3];2[7];3[1-6];4[1,2,4-6,7-10,20];"

If you have trouble configuring your RADIUS server, it is advised that you contact your RADIUS server vendor for assistance.

NOTE: To create a "network only" user for supported AOS files, the following line must be added to the dictionary file: VALUE APC-Service-Type NetworkOnly 6
 

Issue:
Manually Uninstalling PowerChute Business Edition Due To Incomplete Removal Or "Maintenance Successful" Error When Reinstalling The Software

Product Line:
PowerChute Business Edition (PCBE)

Environment:
Windows OS

Cause:
Incomplete Removal Or "Maintenance Successful" Error When Reinstalling The Software

Resolution:
Remove PowerChute Business Edition, by deleting the folders and registry keys created by the install.

Warning: Using the Registry Editor incorrectly can cause serious system wide problems that may require you to reinstall Windows to correct them. Schneider Electric and Microsoft can not guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. Schneider Electric is not responsible for any consequence caused by editing of the system registry.

1. Make sure the APC PBE Agent and APC PBE Server services are stopped if they exist.

2. Delete the following folders through Windows Explorer:


Agent:
C:\Program Files\APC\PowerChute Business Edition\agent (or whatever the install path was) 
or C:\Program Files (x86)\PowerChute Business Edition\agent (or whatever the install path was) 

Server:
C:\Program Files\APC\PowerChute Business Edition\server
C:\Program Files\Common Files\APC
or C:\Program Files (x86)\APC\PowerChute Business Edition\server
C:\Program Files (x86)\Common Files\APC

Console:
C:\Program Files\APC\PowerChute Business Edition\console
or C:\Program Files (x86)\APC\PowerChute Business Edition\console

3. Go to the start menu, then run, and type regedit or regedit32.

4. Find and delete the following keys. Note… some keys may require a change of security. Keys such as KEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_APCPBESERVER may error when attempting to delete them.

To change the security, select the key to be deleted and go to the security menu option and choose permissions. Make sure you have full control access. You can set this access to everyone as it will be deleted and permissions will no longer be an issue.

Entries for 32 bit system:

Agent:
HKEY_LOCAL_MACHINE\SOFTWARE\APC\PowerChute Business Edition
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\agent
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{BCE9F441-9027-4911-82E0-5FB28057897D}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_APCPBEAGENT
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_APCPBEAGENT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\APCPBEAgent

 

Server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A6491A4A-AAA0-4892-BFEF-ECD6CECE2FF3}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_APCPBESERVER
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\APCPBEServer
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_APCPBESERVER
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\APCPBEServer

 

Console:
HKEY_LOCAL_MACHINE\SOFTWARE\APC\PowerChute Business Edition\console
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\console.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{0F86FD09-BA63-4E45-A70B-604C1106C2F2}

Entries for 64 bit System:

Agent:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\PowerChute Business Edition\agent
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\agent
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App Paths\agent
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{BCE9F441-9027-4911-82E0-5FB28057897D}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\APCPBEAgent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\APCPBEAgent

Server:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\PowerChute Business Edition\server
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{A6491A4A-AAA0-4892-BFEF-ECD6CECE2FF3}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\APCPBEServer
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\APCPBEServer

 

Console:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\PowerChute Business Edition\console
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App Paths\console.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{0F86FD09-BA63-4E45-A70B-604C1106C2F2}
 

 

5. Exit the registry, reboot the system. 

 

NOTES:

• If you want to go back to the native service see Schneider Electric  FAQ FA159743 Video: What to do if the system is missing native shutdown battery options / How to restore HID UPS device driver.
• In PowerChute Business Edition v9.5+, the server and console registry keys are not applicable. 

No.
There is only AC choke solution provided with voltage drop between 3% and 5% of the nominal line voltage.
On the ATV320 or ATV340 there is no offer for obtain the THDi <5%,
Even with the passive filter of the other range, it is not possible to use it. Unfortunately, we cannot advise such solution for these products.

Since these bits are defined in individual structures with type T_DIS_IN_GEN for each channel, it is not possible to convert them into a DINT directly. However, you can use this work around in your code to convert. i.e use 2x BIT_TO_WORDS, then WORD_AS_DINT.