socket inlet 63a 500v e range

Metal Clad Appliance Inlets, E Range, Multi Phase, 500V, 63A, 5 Round Pin

Catalogue Number: E563BR
socket inlet 63a 500v e range
Retail
$1415.29*
RRP (Inc. GST)

Specifications

hide show
Range of product
E Range
Product brand
Clipsal
[In] rated current
63 A
[Ue] rated operational voltage
500 V 50/60 Hz conforming to EN 60309-2
Voltage colour
black
Sustainable offer status
Green Premium product
REACh free of SVHC
Yes
EU RoHS Directive
Compliant
Mercury free
Yes
RoHS exemption information
Yes
China RoHS Regulation
Product out of China RoHS scope. Substance declaration for your information
Environmental Disclosure
ENVPEP120809EN

Documents & downloads

hide show

Frequently Asked Questions

hide show

What is the part number for a 5 pin 63A appliance inlet?

The part number is a E563CR.

What is the plug to suit the E532BR?

The plug to suit the E532BR is the E532PR.

What is the part number for an isolation unit to wire , alarm , extra warning lights etc. to the 755PFM?

The part number for an isolation unit to wire , alarm , extra warning lightsetc. to the 755PFM is - 756

For further information , visit link below:-
https://www.clipsal.com/Trade/search-results?q=756
 

What is the plug to suit the 63A, 4 pin socket E463PR?

The plug to suit the 63A, 4 pin socket, E463PR is E463P.
Some of its key features are:
  • Multi phase 500 V Plug
  • E range
  • 4 Round pins
  • 63 Amp
  • E-Range
  • Socket to suit plug is E463PR
For further information on this product please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=E463P
 
 

What is the command word for the ATS22 soft starters for network communication?

Issue:
What is the command word for the ATS22 soft starters?

Product Line:
Altistart ATS22

Environment:
All

Cause:
Modbus address for ATS22

Resolution:
The command word address for the ATS22 soft starter is 752.
The ETA status word address for the ATS22 soft starter is 256

See the attached PDF document for the Command word and the ETA status bit assignments.

Can an ATV56 program be transferred to an ATV61?

Issue:
Can an ATV56 program be transferred to an ATV61? 

Product Line:
ATV56 Altivar 56

Environment:
All

Cause:
Replacement Drive

Resolution:
No, a process to transfer a parameter file from ATV56 to ATV61 is not available.  Manually input parameter settings to the ATV61.

Unable to access PowerChute Business Edition Server from the PowerChute Business Edition Console after upgrading the JRE version with JRE Configuration Tool

Issue:
When upgrading the JRE version, the JRE Configuration Tool runs as expected and both APC PBE Agent (if applicable) and APC PBE Server services are started. When the PowerChute Business Edition Console is launched and username and password is entered, an error window is displayed stating that the server is not accessible.


Product Line: 
PowerChute Business Edition versions 9.0, 9.0.1, 9.1.0, 9.0.2, 9.1.1, 9.0.3, 9.2.0, 9.0.4, 9.2.1

Environment:
OS: Windows x64, x86

Cause:
The latest release of Java JRE 8u60 (and greater) contains a security update which prevents communication between the PowerChute Business Edition Console and the PowerChute Business Edition Server.

Solution:
After upgrading the Java JRE version to 8u60 (or greater), perform the following steps:

1.  Stop the PowerChute Business Edition Agent and Server services.
You can do this from the command line (Run as administrator) with the following command:

Server:                                
net stop apcpbeserver

Agent (if installed):       
net stop apcpbeagent

2.  In the PowerChute JRE folder, open the file lib\security\java.security using a text editor.

Sample JRE locations -
Windows x86:
C:\Program Files\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60
Windows x64:
C:\Program Files (x86)\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60
Linux:
/usr/java/jre1.8.0_60 (Default Java JRE install directory)
Go to the line containing the jdk.tls.disabledAlgorithms setting and carry out the following:
  1. Remove RC4 as a disabledAlgorithm
  2. Change DH keysize restriction from 768 to 256
Original:             
jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768

New:                    
jdk.tls.disabledAlgorithms=SSLv3, DH keySize < 256

3. The following step needs to be carried out for PowerChute Business Edition Agent versions 9.0 and 9.0.1 if it is managed by a PowerChute Business Edition Console/Server.

In the PowerChute JRE folder, open the file lib\security\java.security using a text editor.

Sample JRE locations -
Windows x86:
C:\Program Files\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60
Windows x64:
C:\Program Files (x86)\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60
Linux:
/usr/java/jre1.8.0_60 (Default Java JRE install directory)
Go to the line (should be at the end of the file) containing the jdk.tls.legacyAlgorithms setting and remove 'RC4_128,' from it:

Original:
jdk.tls.legacyAlgorithms= \
                K_NULL, C_NULL, M_NULL, \
                DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
                DH_RSA_EXPORT, RSA_EXPORT, \
                DH_anon, ECDH_anon, \
                RC4_128, RC4_40, DES_CBC, DES40_CBC
 
New:    
jdk.tls.legacyAlgorithms= \
                K_NULL, C_NULL, M_NULL, \
                DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
                DH_RSA_EXPORT, RSA_EXPORT, \
                DH_anon, ECDH_anon, \
                RC4_40, DES_CBC, DES40_CBC

4.  Start the PowerChute Business Edition Agent and Server services
You can do this from the command line (Run as administrator) with the following command:

Server:                                
net start apcpbeserver

Agent (if installed):
net start apcpbeagent
 

Unable to add PowerChute Business Edition Agent to PowerChute Business Edition Console/Server after upgrading the JRE version with JRE Configuration Tool

Issue:
Upgrading the JRE version of the PowerChute Business Edition Agent via the JRE Configuration Tool runs as expected and the service/daemon is restarted successfully. The following error messages appear:  “Could not login to <device>” or “Failed to add <device>” when trying to add the PowerChute Business Edition Agent via the Console or Server.

Product Line: 
PowerChute Business Edition versions 9.0, 9.0.1, 9.1.0, 9.0.2, 9.1.1, 9.0.3, 9.2.0, 9.0.4, 9.2.1

Environment:
OS: Linux, Solaris, Windows x64, x86

Cause:
The latest release of Java JRE 8u60 (and greater) contains a security update which prevents communication between the PowerChute Business Edition Server and the PowerChute Business Edition Agent.

Solution:

After upgrading the Java JRE version to 8u60 but lest than 8u162, perform the following steps:

1.  Stop the PowerChute Business Edition Agent service/daemon.

Windows:          
net stop apcpbeagent

Linux:   
/etc/init.d/PBEAgent stop

2.  In the Powerchute JRE folder, open the file lib\security\java.security using a text editor.

Sample JRE locations –

Windows x86:
C:\Program Files\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60

Windows x64:
C:\Program Files (x86)\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60

Linux:
/usr/java/jre1.8.0_60 (Default Java JRE install directory)

Go to the line containing the jdk.tls.disabledAlgorithms setting and carry out the following:
  1. Remove RC4 as a disabledAlgorithm
  2. Change DH keysize restriction from 768 to 256
Original:             
jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768

New:                    
jdk.tls.disabledAlgorithms=SSLv3, DH keySize < 256

After upgrading the Java JRE version to 8u162 or greater, perform the following steps:


Windows x86:
C:\Program Files\APC\PowerChute Business Edition\JreConfigTool\1.8.0_162\lib\security\
 
Program Files (x86)
C:\Program Files (x86)\APC\PowerChute Business Edition\JreConfigTool\1.8.0_162\lib\security
 
Linux:
Navigate to /usr/java/jre1.8.0_162\lib\security(Default Java JRE install directory)
 
Steps:
1.Open the java.security file
2.Go to the line containing the jdk.tls.disabledAlgorithms setting and carry out the following:
3.Remove RC4, RC4_40 as a disabledAlgorithm
4.Change DH keysize restriction from 1024to 256
 
Original:            
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40
 
New:                   
jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize <256, \
EC keySize < 224, DES40_CBC


3. The following step needs to be carried out for PowerChute Business Edition Agent versions 9.0 and 9.0.1 if it is managed by a Powerchute Business Edition Console/Server.

In the Powerchute JRE folder, open the file lib\security\java.security using a text editor.

Sample JRE locations –

Windows x86:
C:\Program Files\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60

Windows x64:
C:\Program Files (x86)\APC\PowerChute Business Edition\JreConfigTool\1.8.0_60

Linux:
/usr/java/jre1.8.0_60 (Default Java JRE install directory)
Go to the line (should be at the end of the file) containing the jdk.tls.legacyAlgorithms setting and remove ‘RC4_128,’ from it:

Original:
jdk.tls.legacyAlgorithms= \
                K_NULL, C_NULL, M_NULL, \
                DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
                DH_RSA_EXPORT, RSA_EXPORT, \
                DH_anon, ECDH_anon, \
                RC4_128, RC4_40, DES_CBC, DES40_CBC
 
New:    
jdk.tls.legacyAlgorithms= \
                K_NULL, C_NULL, M_NULL, \
                DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
                DH_RSA_EXPORT, RSA_EXPORT, \
                DH_anon, ECDH_anon, \
                RC4_40, DES_CBC, DES40_CBC

4.  Start the PowerChute Business Edition Agent service/daemon

Windows:          
net start apcpbeagent

Linux:   
/etc/init.d/PBEAgent start
 

What needs to be done to run a autodiagnostics or self test on an ATV66 or the ATV56 AC drive?

Issue:
What needs to be done to run a autodiagnostics or self test on an ATV66 or the ATV56 AC drive?

Product Line:
Altivar 66 and Altivar 56

Environment:
All

Cause:
Need to run autodiagnostics

Resolution:
In the de-energized state the supply power connections must be removed from the L1, L2 & L3 drive power terminals.
If there is a jumper from the drive's CL1 control power terminal to the drive's L1 power terminal, it must be removed.
If there is a jumper from the drive's CL2 control power terminal to the drives L2 power terminal, it must be removed.
The L1 power supply must then be connected to CL1 and the L2 power supply must then be connected to CL2.
With power applied to CL1 and CL2 only, you can run the autodiagnostic test in Menu 8 of the AC drive.
If a DC Bus Too High message is seen on the keypad display when trying to run the autodiagnostics, this could indicate that there is still power applied to the L1, L2 or L3 terminals of the drive causing the DC bus voltage to be greater than 22VDC.




CTA-ID : 7691

What are some features I need to be aware of while manipulating the config.ini file of a APC Network Management Card?


Issue

What are some features I need to be aware of while manipulating the config.ini file of a APC Network Management Card?
 


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 (AP84XX, AP86XX, AP88XX, AP89XX), Certain Audio/Video Network Management Enabled products.
 


Environment
 
  • All serial numbers
  • Firmware versions v3.X.X and higher

Cause

The config.ini file on every network management card can be downloaded using command line FTP or SCP. It is a current snapshot of what is running in the Network Management Card's flash memory.

You can make minor changes to the config file and put the file back on the card to make changes to the options on the network card or unit it is installed in. This is useful for configuring multiple units with similar settings.


Resolution

The purpose of the override keyword is to prevent a user from accidentally setting many cards to the same IP settings, thus causing IP conflicts on the network. The override keyword is located in the NetworkTCP/IP section, for example:
[NetworkTCP/IP]
Override=00 C0 B7 6A 33 56
SystemIP=159.215.xxx.xxx
SubnetMask=255.255.255.0
DefaultGateway=159.215.xxx.xxx
BootMode=Manual

When putting the config.ini file back on a network card, the override keyword MUST match the MAC address of the card for the four settings listed above to apply. They will be ignored if the override and MAC do not match.

On certain types of devices such as UPSs, there is a similar override mechanism to protect certain values. In this instance, you'll find a keyword called UPSOverride under the UPS device settings section (ex. [SmartUPS/Matrix]) and it will look similar to this at the top of the specific section with UPS values and UPSOverride:
 
[SmartUPS/Matrix]
UPSName=APC_UPS
UPSOverride="IS1314000000"
RatedOutputVoltage=230
OutputUpperVoltage=253
OutputLowerVoltage=207
Sensitivity=Normal

UPSOverride must equal or have a value of the serial number of the UPS in which the Network Management Card in this example, which is where this setting would be applied.

On newer generation Micro-link UPS devices, such as SMX, SMT, SRT, and SURTD the following keywords in config.ini are protected by UPSOverride:
  • RatedOutputVoltage
  • OutputFrequencyRange

On older generation devices, the following are protected by UPSOverride:
  • RatedOutputVoltage

These values are protected to avoid accidently setting the same potentially "site specific" settings to multiple UPSs without extra care, just as with the TCP/IP settings.

For more details on UPS "generations," refer to knowledge base FA230533.

For more information on mass configuration, please see knowledge base FA156117.