MASTER YOUR CASTLE with your new build or reno project
Enter competition
block mounting pvc 98x45mm

47

Mounting Block, 1 Gang, 103x49x25mm

block mounting pvc 98x45mm
Colour: White Electric
Colour: Per UOM Std.
  • Black 1 PCE
  • White Electric 1 PCE
Added to cart
Successfully added, you can view your cart here

Key Features & Specifications

hide show
  • 1 gang
  • Moulded mounting block to suit cat. no. 16 combinations
  • 98 x 45 mm size
Product brand
Clipsal
REACh Regulation
Free of Substances of Very High Concern above the threshold
REACh free of SVHC
Yes
EU RoHS Directive
Pro-active compliance (Product out of EU RoHS legal scope)
Toxic heavy metal free
Yes
Mercury free
Yes
RoHS exemption information
Yes
China RoHS Regulation
 Pro-active China RoHS declaration (out of China RoHS legal scope)
Circularity Profile
N/A

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • CAD Files and Packs

  • Technical Data Catalogues

  • Installation Instruction

  • Product Environmental

  • Specifications

  • Case Studies

  • Certificates (MSDS)

Frequently Asked Questions

hide show

What is alarm 47 on the Series 2000 Circuit Monitor (CM2000)?

Issue:
A CM2000 series circuit monitor is displaying alarm code 47 on the front display.

Product Line:
CM2000 Series Circuit Monitor

Environment:
Onboard Alarms

Cause:
Alarm code 47 is defined as "Suspended Sag/Swell". The alarm is to identify an excessive number of Sag/Swell events being generated on the meter.

An "excessive number" of Sag/Swell events is defined as:
More than 48 events total from all Sag/Swell Alarms in any 500ms period, or more than 6 events from any single Sag/Swell Alarm in any 500ms period.

Alarm code 47 is active when event 47 is true which occurs when register 2038 on the meter is not equal to zero.  If the user disables alarm 47 without clearing Register 2038, the alarm will immediately be re-enabled and asserted as true.

Resolution:
To clear alarm 47, write a 0 to register 2038.

To learn how to read and write registers using the front panel of the CM2000 series meter, please refer to KB article FA211912
To learn about other CM2000 alarm codes, please refer to the KB article FA218966.

 

Is the ABL8RPS24030 okay for 60 hertz?

Yes they are have a Network Frequency range of 47 - 63 Hz
As shown on attached Data sheet

What are the hole sizes and dimensions of the AR8395 copper bus bar?

Issue:
A customer wants to use 2-hole lugs on the ground bar

Product Line:
NetShelter Bus Bar

Environment: 
AR8395

Cause:
Grounding / bonding is required

Resolution: 
The AR8395 has the following holes available: 
47 holes threaded #10-32, spaced 18 cm center to center. 
25 holes at 5.5 cm and 9 holes at 7.9 cm, spaced at 25 cm center to center. 
 

Is There a lens avaliable for XUY40327350?

XUY40327350 is a high temperature fiber specially manufactured for one of our customer (exclusive sales), so to get this product or informations about it, you have to contact directly the company : we are not authorized to provide any information about this product.

For further information please visit https://www.schneider-electric.com.au

Can TeSys T be used downstream of Altivar range Variable Speed Drive.

The Current Transformers (CTs) of TeSys T are deigned to work under the frequency range between 47 to 63 Hz only. 

However, the output frequency range of Altivar Variable Speed Drive varies from 0 Hz to 400 Hz. So when the TeSys T is placed in the downstream of the Variable Speed Drive, the CTs of TeSys T will not be able to sense the current values correctly, as the frequency of the current is not as per design specifications.
 
This will affect the TeSys T working and the outcome will not be the actual.  So, it is not recommended to use the TeSys T in downstream of the Altivar Range Variable Speed Drives.

Smart-UPS VT-Galaxy 3500; Bypass Not Available Input Freq/Volt Out Of Range, Output: Inverter sync. to bypass alarms

Issue:
Smart-UPS VT-Galaxy 3500; Bypass Not Available Input Freq/Volt Out Of Range alarms
 
Product Line:
Smart-UPS VT-Galaxy 3500-AIS3000
 
Environment:
All models, all serial numbers
 
Cause:
The frequency or voltage is out of acceptable range for bypass operation. This message occurs when the UPS is online, and indicates that static Bypass operation may not be available while the alarm is active.
 
If the Bypass frequency is out of range, the UPS should not allow you to command the UPS to bypass. If the UPS allows you to enter Static Bypass operation, it was because the bypass frequency was already within tolerance again, even if the alarm was still present in the display (alarms are displayed for 20> seconds) Correct the input voltage to provide acceptable voltage or frequency.
 
Bypass Sync Error: Input frequency range for the PFC is 40 Hz - 70Hz. As long as the Mains frequency is inside that window, the UPS should be in normal operation.
 
a) Mains distortion will activate as well that alarm (even more frequently than in SYPX)
b) The input frequency range is configurable, as it was in SYPX, so you can have:
 
For 60 Hz systems:
60 HZ +/- 0,1%
57 Hz - 63 Hz
50 Hz - 70 Hz
 
For 50 Hz systems:
50 HZ +/- 0,1%
47 Hz - 53 Hz
40 Hz - 60 Hz
 
Bypass input voltage threshold:
NAM 208V MIN = 187.2 VAC
NAM 208V MAX = 228.8 VAC
 
Output: Inverter sync to bypass error:
The inverter is synchronized to the bypass. The phase difference between the output PLL and the bypass voltage is above a predefined limit and the system will not be able to go to bypass.

 
Resolution:
When AC mains returns you may get a informational event for; Mains no longer prevents UPS from switching to bypass.
 

Network Bandwidth Calculation for ION meters

Goals and Symptoms

There are often questions to evaluate the network activity of the ION Meters. This articles gives a worst case calculation for the bandwidth required by the meters to operate correctly on the network.

Facts and Changes

Bandwidth, network, ION

Causes and Fixes

There are two contributors to data traffic between the Log Inserter and a meter:

1.  Periodic polling by the Log Inserter to check if there are any new records to upload
2.  Uploading data records


1. The periodic polling consists of a request from the server to the meter and a response from the meter. Log inserter polling to meter occurs every 5 seconds.

  • The size of the request (in bytes) will follow the formula:
    54 (TCP/IP overhead) + 46 (ION packet overhead) + 3 * # recorders (data and waveform, whether enabled or disabled) + 3 (for the event log controller)
  • The size of the response (in bytes) will follow the formula:
    54 (TCP/IP overhead) + 47 (ION packet overhead) + 5 * # recorders (data and waveform, whether enabled or disabled) + 5 (for the event log controller)
NOTE: allocating 5 bytes for the log positions of the data recorder and the event log controller assumes that the log position is > 65535.  This is a worst-case assumption.


2. Uploading data records also consists of a request and a response.  Log Inserter sends one request per recorder. 
  • The maximum possible size of this request would be 113 bytes (including TCP/IP overhead).
  • The size of the response depends on the number of values being logged and their data type.  The formula is:

    54 (TCP/IP overhead) + 61 (ION packet overhead) + [logged value data]
    For a 32-bit float the size of the logged data would be 6 bytes (4 bytes for the float, 2 bytes overhead - worst case).

Example in the case of the ION7650:

There are 29 recorders (13 data rec and 16 waveform rec).

1. The default polling period is 5 seconds. The packet sizes would be:
  • Request size = 54 + 46 + 3 * 29 + 3 = 190 bytes
  • Response size = 54 + 47 + 5 * 29 + 5 = 249 bytes
So that's 439 bytes over the link every 5 seconds.


2. If you are logging only 32-bit floats in the 13 data recorders (worst case), the packet sizes would be:
  • Request size = 113 bytes
  • Response size = 54 + 61 + 16 inputs * 13 recorders * 6 bytes = 1363 bytes
So that's another 1476 bytes every 15 minutes.

Maximum network activity over 24h: 7.36 MB

More Information:
This calculation makes the assumption that you are using an ION meter with a default template, and no power quality events. Downloading waveforms will add some considerable network activity.
Be aware that this calculation is valid only for the communications between Loginserter and the meter. This doesn't take into account the activity generated by Vista, Designer, or anything else that can access the meter over the network.

This is the network activity. This is NOT the amout of data logged in the database.




Last Revised: December 3, 2007
Applies To: ION 7300, 7500 / 7600, 7550 / 7650, 8300 / 8400 / 8500, 8600, 8800
Public
All content © 1992-2007 Schneider Electric

Legacy KB System (APS) Data: RESL190139 V1.0, Originally authored by KBAdPM on 12/04/2007, Last Edited by KBAdPM on 12/04/2007
Related ranges: ION8800, ION8600, ION7550/ION7650, ION7300, ION8500, ION8400, ION8300, ION7500/ION7600

How to read alarm status's via registers on a CM2000 series meter

The alarm status's are stored in registers 5771-5778 with each alarm set to a bit indexed from zero. For example, if one needed to determine if the over current alarm for phase A was active you would read register 5771 and look to bit zero. If the register reading program is not capable of displaying binary (bit level) information, the information may be entered into the Windows calculator and converted from decimal to binary.
Alarm No. Alarm Description
01 Over Current Phase A
02 Over Current Phase B
03 Over Current Phase C
04 Over Current Neutral
05 Over Current Ground
06 Under Current Phase A
07 Under Current Phase B
08 Under Current Phase C
09 Current Unbalance Phase A
10 Current Unbalance Phase B
11 Current Unbalance Phase C
12 Phase Loss, Current
13 Over Voltage Phase A
14 Over Voltage Phase B
15 Over Voltage Phase C
16 Over Voltage Phase A-B
17 Over Voltage Phase B-C
18 Over Voltage Phase C-A
19 Under Voltage Phase A
20 Under Voltage Phase B
21 Under Voltage Phase C
22 Under Voltage Phase A-B
23 Under Voltage Phase B-C
24 Under Voltage Phase C-A
25 Voltage Unbalance A
26 Voltage Unbalance B
27 Voltage Unbalance C
28 Voltage Unbalance A-B
29 Voltage Unbalance B-C
30 Voltage Unbalance C-A
31 Voltage Loss (Loss of A, B, or C, but not all)
32 Over kVA 3-Phase Total
33 Over KW Into the Load 3-Phase Total
34 Over KW Out of the Load 3-Phase Total
35 Over kVAR Into the Load 3-Phase Total
36 Over kVAR Out of the Load 3-Phase Total
37 Over Current Demand Phase A
38 Over Current Demand Phase B
39 Over Current Demand Phase C
40 Over Current Demand 3-phase Total
41 Over Frequency
42 Under Frequency
43 Lagging True Power Factor
44 Leading True Power Factor
45 Lagging Displacement Power Factor
46 Leading Displacement Power Factor
47 Suspended Sag/Swell
49 Over Value THD Current Phase A
50 Over Value THD Current Phase B
51 Over Value THD Current Phase C
52 Over Value THD Voltage Phase A-N
53 Over Value THD Voltage Phase B-N
54 Over Value THD Voltage Phase C-N
55 Over Value THD Voltage Phase A-B
56 Over Value THD Voltage Phase B-C
57 Over Value THD Voltage Phase C-A
58 Over K-Factor Phase A 1071 Tenths % A
59 Over K-Factor Phase B 1072 Tenths % A
60 Over K-Factor Phase C
61 Over Predicted kVA Demand
62 Over Predicted KW Demand
63 Over Predicted kVAR Demand
64 Over kVA Demand Level 1
65 Over kVA Demand Level 2
66 Over kVA Demand Level 3
67 Over kW Demand Level 1
68 Over KW Demand Level 2
69 Over KW Demand Level 3
70 Over kVAR Demand
71 Over Lagging 3-phase Avg. Power Factor
72 Under 3-Phase Total Real Power
73 Over Reverse 3-Phase Power
74 Phase Reversal
75 Status Input 1 Transition from Off to On
76 Status Input 2 Transition from Off to On
77 Status Input 3 Transition from Off to On
78 Status Input 4 Transition from Off to On
79 Status Input 5 Transition from Off to On
80 Status Input 6 Transition from Off to On
81 Status Input 7 Transition from Off to On
82 Status Input 8 Transition from Off to On
83 Status Input 1 Transition from On to Off
84 Status Input 2 Transition from On to Off
85 Status Input 3 Transition from On to Off
86 Status Input 4 Transition from On to Off
87 Status Input 5 Transition from On to Off
88 Status Input 6 Transition from On to Off
89 Status Input 7 Transition from On to Off
90 Status Input 8 Transition from On to Off
99 End of Incremental Energy Interval
100 Power-Up/Reset
101 End of Demand Interval
102 End of Update Cycle
103 Over Analog Input Channel 1
104 Over Analog Input Channel 2
105 Over Analog Input Channel 3
106 Over Analog Input Channel 4
107 Under Analog Input Channel 1
108 Under Analog Input Channel 2
109 Under Analog Input Channel 3
110 Under Analog Input Channel 4
201 Voltage Swell A-N/A-B
202 Voltage Swell B-N
203 Voltage Swell C-N/C-B
204 Current Swell Phase A
205 Current Swell Phase B
206 Current Swell Phase C
207 Current Swell Neutral
208 Voltage Sag A-N/A-B
209 Voltage Sag B-N
210 Voltage Sag C-N/C-B
211 Current Sag Phase A
212 Current Sag Phase B
213 Current Sag Phase C
214 Current Sag Neutral


Legacy KB System (APS) Data: RESL209554 V1.0, Originally authored by MaTh on 11/02/2012, Last Edited by MaTh on 11/02/2012
Related ranges: CM2000 series

INFORMATION BULLETIN - Using Global Outlet Groups simultaneously between AP79XX and AP8XXX series Rack PDUs with the same multicast IP range causes AP79XX PDU not to boot properly


Issue

An issue has been identified with AP79XX series Switched Rack PDU users who enable the global outlet group functionality. If the user has AP79XX series units on the same subnet with AP89XX or AP86XX series Switched Rack PDUs that also have the global outlet group functionality enabled and both are using the same multicast IP range value, the AP79XX series will fall into a reboot loop and after six tries, stop booting. This results in both of the following symptoms, depending on how you normally access the PDU.

Web Interface: User will receive the following message or similar after the reboot loop has stopped
 

Error: The application was not able to load.

You are attempting to access an APC device.

There was a problem loading the application. Please login to the device via telnet for more details.

 

Telnet/SSH/Local Console: User will notice Stat section indicates A! or A-. 
 

American Power Conversion               Network Management Card AOS      v3.7.4
(c) Copyright 2009 All Rights Reserved  Rack PDU APP                     v3.7.4
-------------------------------------------------------------------------------
Name      : RackPDU                                   Date : 06/26/2014
Contact   : Unknown                                   Time : 15:34:50
Location  : Unknown                                   User : Administrator
Up Time   : 8 Days 1 Hour 47 Minutes                  Stat : P+ N+ A-



Product Line

  • Rack Power Distribution
    • AP79XX Switched Rack PDU
    • AP89XX Switched Rack PDU 2G
    • AP86XX Switched with Metering By Outlet

Environment

  • Users utilizing global outlet group/global outlet groups via network
  • Users with both AP79XX and AP89XX and/or AP86XX PDUs in their environment
  • AP79XX series v3.X.X firmware
  • AP89XX and AP86XX firmware - all versions

Cause



This is a firmware bug on the AP79XX series Switched Rack PDUs. The following criteria must be met in order for the issue to occur:

  1. Global outlet group configuration on both generations of Switched Rack PDU are enabled.
  2. Both generations/groups of Switched Rack PDUs are utilizing the same Multicast IP range.
  3. Both generations/groups of Switched Rack PDUs are on the same subnet/network.

Resolution

  1. Verify this is your issue by understanding if you have both generations of Switched Rack PDU active in your environment.
  2. Next, confirm what you did previously before the condition on the AP79XX occurred. (For example, similar error messages can be provided by AP79XX when a firmware upgrade has failed.) Verify it is feasible global outlet groups were recently enabled or you added a different generation of Rack PDU to your subnet with this feature enabled - it is disabled by default. 
  3. Access to the current configuration on the AP79XX via config.ini file or Telnet/SSH/Local console menu will be unavailable. There are few options.
    • Check AP89XX and AP86XX Outlet Group configuration to verify if outlet groups are enabled.
      • If so, consider disabling them temporarily, which requires the PDU to reboot.
      • After completing the previous step, reboot the AP79XX series Rack PDU which will restart the PDU's attempts to boot properly.
      • As long as there is no traffic from the AP89XX or AP86XX series units, the AP79XX should boot properly.
      • If the AP79XX series boots properly, you should change the Multicast IP range to be different from the AP89XX and AP86XX series.
    • Alternatively, the user can reset the AP79XX series PDU to default (excluding TCP/IP is OK) which will disable global outlet groups.
      • Then, reconfigure the PDU and make arrangements to select a different, unique Multicast IP range for each series of Rack PDU, and also each individual PDU group who share outlets.
In order to check global outlet group configuration, here is where the information is located.


AP79XX series

Note: These methods will be unavailable or missing if your PDU is already experiencing this issue. Depending on your environment, you'll need to either work around the issue with the AP79XX series as noted above or verify on the AP89XX or AP86XX series and modify there to temporarily disable. Then, reboot the AP79XX series after the AP89XX or AP86XX traffic is no longer present or is configured on a different Multicast IP range.

  • Web Interface - Navigate to Device Manager tab, Outlet Groups->Group Configuration. There is a drop down list here that says Device Level Group: Enabled or disabled. If enabled, you may be experiencing this issue.
  • Config.ini configuration file  - Under the [OutletGroup] section, look for the following values below. OutletGroupMembership=Enabled indicates the feature is enabled.
[OutletGroup]
; Configure an Outlet Group on the RackPDU.
; Format: OutletGroup# = Outlets[], Name
;   Outlets:        Outlet numbers to be grouped: Outlets[1,2,3...]
;                   Note: Global outlets are indicated by an '*' after the
;                         outlet number (e.g. Outlets[1*,2,3])
;   Name:           Outlet Group text description
OutletGroupMembership=Enabled
OutletGroupMulticastName=McastName
OutletGroupMulticastIPAddr=224.0.0.100

AP89XX

  • Web Interface
    • v5.X.X firmware - Navigate to Device Manager tab, Outlet Groups->Group Configuration. There is a drop down list here that says Device Level Group and it has a few different options. Earlier versions say Enabled or Disabled. Enabled or Enabled via Network means that the feature is enabled.
    • v6.X.X firmware - Navigate to Configuration->RPDU->Switched Outlet->Outlet Group Settings. There is a drop down list here that says Device Level Group and it has a few different options. Enabled via Network means that the feature is enabled.
  • Config.ini configuration file
    • v5.1.0, 5.1.1, 5.1.2 firmware - Under the [OutletGroup] section, look for the following values below. OutletGroupMembership=Enabled indicates the feature is enabled.
[OutletGroup]
; Configure an Outlet Group on the RackPDU.
; Format: OutletGroup# = Outlets[], Name
; Outlets: Outlet numbers to be grouped: Outlets[1,2,3...]
; Note: Global outlets are indicated by an '*' after the
; outlet number (e.g. Outlets[1*,2,3])
; Name: Outlet Group text description
OutletGroupMembership=Enabled
OutletGroupMulticastName=McastName
OutletGroupMulticastIPAddr=224.0.0.100
  • v5.1.6, v6.X.X firmware - Under the [Outlet] section, look for the following value below.
[Outlet]
OUTLET_GROUPS_ENABLE_A=Enabled
 
Under the [Multicast] section, look for the following values below.
 
[Multicast]
MULTICAST_NAME_A=McastName
MULTICAST_IP_A=224.0.0.100