plug conduit pvc plain 16mm

SoLid Fittings - PVC, Conduit Plugs - Plain, 16mm

Catalogue Number: 220/16
plug conduit pvc plain 16mm
Colour: Grey
Colour: Per UOM Std.
  • Electric Orange 1 PCE
  • Grey 1 PCE
Added to cart

Specifications

hide show
Product brand
Clipsal
Range of product
Series 220
Material
PVC (polyvinyl chloride)
Product destination
diameter: 16-16 mm tube
Stub stiffness
rigid
Length
12 mm
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)

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

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).

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

How many plates fit on the 224/1?

The 224/1 fits 2 standard size plates. This can include GPO's, Multigang data plates, Light switches.

For further information, please visit www.clipsal.com/Trade/Products/ProductDetail?catno=224/1

User-added image

 

How many 261/16 Clipsal saddles are there in a carton?

There are 50 16mm saddles in a carton.

Note: This information can be found in your Clipsal pocketbook right next to the part code.

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

 

What is the part code for a RCBO 4P 32Amp C-curve

 Combine a mccb 25016 32Amp C-curve with a 23382 rccb = RCBO

Is part no 224/1 avaialble in Black

Part no 224/1 is not available in Black

for more information on this part please refer to https://www.clipsal.com/Trade/Products/ProductDetail?catno=224/1

User-added image

Is there a surface mount floor box available?

We can offer a 224/1

Is the 224/1 have outlets either side?

Yes it houses 2 standard size plates, one either side.

What is the C clip bracket for double gyprock roughly 25mm thick? Do you also do long screws to suit?

The part number for the C clip is 154/1.
The Part number for the screws is 355A.

For further information please visit https://www.clipsal.com/Trade

Does Clipsal offer something similar to the 224/1 floor outlet housing in metal?

No, Unfortunately this product is unavailable.
Some of the key features of the 224/1 floor outlet housing are:
  • 134 Length x 111 Width x 113 Depth mm dimension
  • With 2 segregation barriers
  • Suits 2 Standard plates
  • 1 gang
  • 84 mm Mounting centre
For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=224/1
 

 

What are the processes associated with PowerSCADA Expert?

Issue
The processes associated with PowerSCADA Expert.

Product Line
PowerSCADA Operations, PSO
PowerSCADA Expert, PSE
PowerLogic SCADA, PLS

Environment
Runtime Manager
Task Manager

Cause
In cases that a project does not start or shut down properly, it is advised to check the processes.  In the case the project did not shut down properly, the process can be killed manually using Windows Task Manager.  This way upon a restart of Runtime Manager, the project starts without any problem.

As such it is important to know the associated processes.

Resolution
The example below shows a project with six I/O Servers (numbered 2, 4, 6, 8, 10 and 12), a Trend Server, one Alarm Server and a Client (represents the main project); a total of 9 processes as shown in Runtime Manager.

NOTE: While the screenshot below applies to older version of SCADA, the same analogy applies to newer versions.

          

The processes above can be verified in Windows Task Manager as shown below.  There is an entry for each of the above 9 processes, each labeled Citect32.exe *32.  Note the one-to-one correspondence among the Process IDs in Task Manager and Process IDs in Runtime Manager.  For example PID 22716 in Task Manager corresponds to IOServer6 as show in the above picture.

          


NOTE: The last three processes in the above screenshot applies to PSE 8.1 and older; more explanation below.

In case SCADA application is open for editing a project, there will be additional processes.  Process names and their corresponding application are shown below.  Depending on the version, different applications open.

1. SCADA version 8.1 and older:

CtDraw32.exe *32     Citect Graphics Builder
CtEdit32.exe *32       Citect Project Editor
CtExplor.exe *32       Citect Explorer

2. SCADA version 8.2:

PowerSCADA Studio (32 bit)     PowerSCADA Studio

          



Example of a PowerSCADA 8.2 project with 5 process and PowerSCADA Studio open for editing:

1. Runtime Manager:

          

2. Task Manager (Details tab):

           

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".