flange conduit locating 20-25-32mm

SoLid Fittings - PVC, Conduit Locating Flanges, 20mm

Catalogue Number: 221/20
flange conduit locating 20-25-32mm
Colour: Electric Orange
Colour: Per UOM Std.
  • Electric Orange 1 PCE
Added to cart

Specifications

hide show
Product brand
Clipsal
Range of product
Series 221
Material
plastic
External diameter
90 mm
Height
40 mm
Sustainable offer status
Green Premium product
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)
Environmental Disclosure
ENVPEP100802EN
Circularity Profile
N/A

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

Do you have a cap/ flange to for 20mm conduit?

Yes the part number is 221/20

Can I order the 220/20 in white?

Yes, you can order the 220/20 in white but it needs to be done as a special.
For more information, please refer to the link:https://www.clipsal.com/Trade/Products/ProductDetail?catno=220/20

What are the part numbers of slip type expansion couplings?

Slip Type Expansion Couplings are available from 16mm through to 50mm.The part numbers of slip type expansion coupling are as follows:
16mm = 251/16
20mm = 251/20 *
25mm = 251/25 *
32mm = 251/32
40mm = 251/40 *
* = only available in Grey
Where long conduit runs are likely to be exposed to wide variations in temperature, it is recommended that expansion couplings be used at each join. It is not recommended that Slip Type Expansion Couplings be used where the conduit run is exposed to the weather. Standard colour is Grey (GY).
Dimension details are attached.
 

What would be a longer screw to suit Clipsals round j-boxes (Junction Boxes)?

The part number would be 248/20 which is a combination screw head 20MM 3/16 BSW.

Can I get the 251/50 in orange?

No. Unfortunately, the 251/50 is the only one that comes in grey.

For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=251/50



 

What size Clipsal saddles are available?

Size       Ctn Qty     Part Code
16mm    50             261/16
20mm   100            261/20
25mm   100            261/25
32mm    50             261/32
40mm    50             261/40
50mm    20             261/50

Are the Clipsal Conduit Clips available in Electric Orange?

No, they are only available in grey.

This applies to the 280/16 (16mm), 280/20 (20mm), 280/25 (25mm), 280/32 (32mm), 280/40 (40mm) and 280/50 (50mm).

Is there a black version of the 220S20?

Yes, there is.  The 220S20 comes in 3 colors.

For more information, please refer to the link:
https://www.clipsal.com/Trade/Products/ProductDetail?catno=220S20 

What is the part number for a 50mm female and 50mm male bush?

The part number for a 50mm female and 50mm male bush is - 281/50 & 281F50
For further information , visit link below:-
www.clipsal.com/Trade/search-results?q=281/50
https://www.clipsal.com/Trade/search-results?q=281F50
User-added image

 

Is the Clipsal 224/2 floor outlet still available

 Obsolete and deleted. Use a SBIP2P-XX  
The PDL 535F has been obsoleted as well

What are the part numbers for the 25mm PVC saddles and spacers?

The part numbers are 261/25 for the saddles and 261S25 for the spacers. 

Some of the key features are:
  • 63mm Length x 20mm Width x 29mm Overall Height
  • 48mm Mounting Centre
For further information please visit https://www.clipsal.com/Trade/search-results?q=261/25



 

Are the 224/2 floor outlet housing still available?

Yes, the 224/2 floor outlet housing is still available.
Some of the key features are:
  • 249 Length x 110 Width x 107 Depth mm dimension
  • With 4 segregation barriers
  • Suits 4 Standard plates
  • 1 gang
  • 84mm Mounting center
For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=224/2

 

What are the differences between the VAMP 221/321 modules?

What are the differences between the VAMP 221/321 modules:
VAM 3L
- Three supervised fiber loop arc sensor connections
- One heavy duty trip relay
- Portable arc sensor connection

VAM 4C
- 3-phase current measurement or 2-phase and earth-fault current measurement
- Current pick-up setting by potentiometer and led display
- Indication of current channel pick-up
- One heavy duty trip relay

VAM 10L
- 10 point arc sensor connections
- Portable arc sensor connection
- One heavy duty trip relay
- Continuous supervision of APS_SENSORS
- Indication of the sensor channel and trip relay activation

VAM 12L
- 3 selective trip output contacts for dedicated APS_SENSORS
- 10 point arc sensor connections
- Portable arc sensor connection
- One heavy duty trip relay
- Continuous supervision of APS_SENSORS
- Indication of the sensor channel and trip relay activation


Legacy KB System (APS) Data: RESL211597 V1.0, Originally authored by DaFr on 05/29/2013, Last Edited by DaFr on 05/29/2013
Related ranges: Others protection relays

What is the accuracy of the Premium PLC CPU real time clock.

Real time clock accuracy:

Accuracy of the real time clock is one second (%SW50) +/- 200ms.

Resolution of the real time clock is one second (%SW50) +/- 200ms,because 200ms is the refresh rate of the RTC.
 
Accuracy error:
 
The accuracy error of the quartz oscillator is:
 
1. At 0 and 70°C : -101/20 ppm, error in second/day is -8.7/1.7, in minute/year is -53/11.
 
2. At 25°C: -20/20 ppm, error in second/day is -1.7/1.7, in minute/year is -11/11.

What is the part number of the surface mounting box that has a duct entry?

The part number of the surface mounting box that can accept a duct is 900SPMB. The 900SPMB is a standard pattern Surface Mounting Box for single gang accessories. Internal depth - 33mm.
Features: 4 - 25 x 16mm Trunking Entries, including one each end and side.
Supplied with 3 - Cat. No. 900MBC Clip-in/ push out caps, 4 - Cat. No. 220/10 Insulating Caps and 2 - M3.5 x 0.8 x 16mm long pan head screws. Screws thread into brass inserts.
For further information, please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=900SPMB

 

Where are the 1 N/O and 1 N/C auxiliary contacts located on the LC1D Contactors?

They are on the front of the contactor with the coil connections, terminal 13/14 for NO and 21/22 for NC

 

What is the replacement AC coil for CAD32 and CAD50 relay?

Issue:
Are replacement  AC coil available for CAD32 and CAD50 relay?

Product Line:
Tesys Relays

Environment:
All Products

Cause:
Product selection

Resolution:
Volt = coil part number
12 = LXD1J7
21 = LXD1Z7
24 = LXD1B7
32 = LXD1C7
36 = LXD1CC7
42 = LXD1D7
48 = LXD1E7
60 = LXD1EE7
100 = LXD1K7
110 = LXD1F7
115 = LXD1FE7
120 = LXD1G7
127 = LXD1FC7
200 = LXD1L7
208 = LXD1LL7
220/230 = LXD1M7
230 595 21 LXD1P7
230/240 = LXD1U7
277 781 30 LXD1W7
380/400 = LXD1Q7
400 = LXD1V7
415 = LXD1N7
440 = LXD1R7
480 = LXD1T7
600 = LXD1X7
690 = LXD1Y7

 

What are the dimensions for a 261S Saddle Spacer?

The dimensions for a 261S Saddle Spacer are 261S are:
 
Saddle Spacers
Catalogue Number Size Length (L) Width (W) Centres (CRS.) Standoff (T) Height (H)
261S16 16mm 55mm 21mm 32mm 8mm 14mm
261S20 20mm 61mm 22mm 40mm 8mm 14mm
261S25 25mm 74mm 26mm 48mm 8mm 14mm

Saddles Spacers set a conduit run off the wall 8mm to allow easier cleaning and repainting and to facilitate entry into equipment. They are available in sizes 16mm through 25mm.
Standard colour is Grey (GY), with Orange (EO) also available at extra cost.

For further information please visit www.clipsal.com/Trade/search-results?q=261S


 

Using Modbus to trigger a Waveform Capture on a CM2000

Product Line
CM2000 series meter

Environment
Modbus Register Writes

Resolution
In order to trigger a waveform capture, it will be necessary to use Modbus Command Writes to trigger the waveform capture.

Using Modbus Tester (or another Modbus read/write program):

Write the value 4913 to register 7700.
Write the value 1 to register 7701.
Write the value 28120 to register 7702.

VAMP 221/321: What is the difference between using an optical point sensor and a fiber loop sensor?

Issue
The advantages and disadvantages of using an optical point sensor and a fiber loop sensor for arc flash protection.

Product Line
VAMP 221/321 Protection Relays

Environment
Arc Flash Protection Relays

Cause
Optimization of an arc flash protection solution by specifying either optical point or fiber loop sensors.

Resolution


                                                                          Figure 1

                                                                           Figure 2

Fiber loop sensor technology offers the following advantages when compared to the point sensor:
  1. Significantly reduces the cost of installation. A single optical fiber sensor can be as long as 200 feet, typically covering the same protection zone associated with conventional bus-differential protection but at a much lower cost than point sensors as shown in Figure 2.
  2. The loop approach eliminates any concerns about shadows from internal structures that might block the direct exposure to an arc flash.
  3. Optical point sensors are installed in every enclosed compartment and has a wired coverage area as shown in Figure 1.
  4. If the fiber sensor is configured in a loop, it can provide regular self-checking of the sensor’s integrity and continuity, producing an alarm if a problem is detected.

What are the pinouts for current inputs on the AMI0810 when using the FTW308 cable with pigtail leads ?

 

 

 
  : Here are the pin assignments for current inputs I0 - I7 when using the FTW308 cable and the BMXAMI0810 .
 
      
    Current input 0  +                   pins 1/3 blue/white & white/blue are jumped together
    Current input 0  common        pin 2 white/orange
 
    Current input 1  +                   pins 4/6  green/ white & white/green are jumped together
    Current input 1  common        pin 5 orange/white
 
    Current input 2  +                   pins 7/9 white/brown  & brown/white are jumped together
    Current input 2  common        pin 8   white/gray 
 
    Current input 3  +                   pins 10/12 blue/red & red/blue are jumped together
    Current input 3  common        pin 11 gray/white
 
    Current input 4  +                   pins 15 /17 red/ orange & orange/ red are jumped together
    Current input 4  common        pin 16 red/green
 
    Current input 5  +                   pins 18/20 brown/red & red/brown are jumped together
    Current input 5  common        pin 19 green/red  
 
   Current input 6  +                 pins 21/23 red/gray & gray/ red are jumped together
   Current input 6  common        pin 22 black/blue
 
   Current input 7  +                   pins 24/26 black/orange & orange/ black are jumped together
   Current input 7  common        pin 25 blue/black 


R-6-30-17

Legacy KB System (APS) Data: RESL211859 V1.0, Originally authored by DaSo on 06/21/2013, Last Edited by DaSo on 06/21/2013
Related ranges: Modicon M340

STBNIP2212 Ethernet Communication Adapter Exec. Upgrade to v.1.16.0 Web Upgrade to v.1.12.0

Release Notice

The purpose of this resolution is to inform users of Advantys Ethernet Network Interface Modules (STB NIP 2212) that the following files have been upgraded:

  • Executive firmware has been upgraded to version 1.16.0. The previous Exec. version was 1.12.0.
  • The Web pages have been upgraded to version 1.12.0. The previous Web version was 1.10.0.
  • The Kernel had been previously upgraded to version 1.07.0.

Goals and Symptoms

The Exec. was updated to fix the following issues:
1. Outputs could come on for 500ms under certain conditions.
2. The LAN ST LED would blink 4 times (duplicate address detected) if a hub or switch is powered up after 2 or more Ethernet NIMs on a network are powered up.
3. During initialization, the LAN ST LED blink pattern appeared as valid LAN Status codes and could be misinterpreted as an error or status.
4. LAN ST LED blinks 4 times (duplicate address detected) if a link was broken and then re-established between the NIM and a hub/switch
5. Inconsistent Ethernet NIM response times.
6. Unable to accurately count an error code blink pattern with the ERRor LED.
7. A failure loading the Exec. may randomly occur when using the Loader Utility (dated 12/8/03).

The Web pages, updated to version 1.12.0, were changed with the following:
1. Adds CAN Extension modules to the Web pages.
2. Increased the size of some text boxes that would not properly display all of the characters in that field.

Facts and Changes

This affects STBNIP2212's with:
Exec. version 1.12.0 or lower.
Web pages at 1.10.0 or lower.

Causes and Fixes

Updating the Exec. to v.1.16.0 and the Web pages to v.1.12.0 resolves the above mentioned issues.

Attachments

The attached document contains the following:

  1. Description of the Problems
  2. File Information
  3. Accessing the Files
  4. An updated Field Upgrade Procedure

(Removed File URL: 163673_59B6/stbnip2212exec116_v1.doc)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/0378d13b210ea1b685256ecc00678e8b/fl_block_5/0.14D4?OpenElement&FieldElemFormat=gif)

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

PowerSCADA Expert 8.2 Update 5 - Release Notes

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

Product Line
PowerSCADA Expert 8.2 (PSE8.2)

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

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

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

 


 

Prerequisite

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

Cybersecurity Announcement

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

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

Bug Fixes and Enhancements

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

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

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

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

TFS 21484 - Unable to filter AlarmEvents by Type using EWS

Alarms are now filtered based on type. 

TFS 21485 - Unable to successfully acknowledge alarms using EWS

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

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

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

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

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

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

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

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

 

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

 

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

Performance issue in alarm proxy has been resolved.

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

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

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

CoreServiceHost now properly updates the equipment on name change.

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

Large logs are now broken down into smaller log entries.

TFS 21970 - Profile Wizard and Automation does not support IPv6

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

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

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

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

This setting is now configurable in the Application Configuration Utility.

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

Single sign-on now detects remote clients.

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

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

TFS 22066 - Wonderware ArchestrA Logger Security Patch

Wonderware ArchestrA Logger Patch 2017.517.2328.1 is applied.

TFS 22150 - Alarm filters do not work on some resolutions

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

TFS 22155 - Alarm filters perform exact matching

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

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

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

TFS 22401 - Alarm filter and equipment tree filter operate independently

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

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

 

Cleanup methods were reworked to prevent the exception.

 

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

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

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

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

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

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

TFS 23437 - Citect 2016 Updates

 

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

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

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

 

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

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

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

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

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

Core Services properly recovers from a ctApi deadlock condition.

Files Modified

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

Installation

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