housing outlet cable divider

Mounting Accessories Housing Outlet Cable Divider, 4 Way, Fits into 50mm ? Hole

Catalogue Number: 224DV
housing outlet cable divider
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Product brand
Clipsal
Length
400 mm
Width
47 mm
EU RoHS Directive
Compliant
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

  • CAD Files and Packs

  • Product Brochures

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

Is the Clipsal 224/2 floor outlet still available

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

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

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

 

Is the 224/1 have outlets either side?

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

What are the dimensions for a Colour CTouch Wallbox 5000CTCWB

The dimensions for the Colour CTouch screen wallbox (5000CTCWB) are as follows:

224mm x 167mm x 68mm 

 

What is the cut out for a 4013/40?

There is no cut out as it is just a lamp (240V SGU10 CFL). Please clarify which down light it is from as this lamp fits multiple fittings.

How to get BIDS(Business Intelligence Development Studio) for SQL Sever 2005 Express Edition?

You can get it from Microsoft website as per below. It's free and around 224.6 MB
https://www.microsoft.com/DownLoads/details.aspx?FamilyID=d434dc36-a24d-44ee-937e-553c382557e3&displaylang=en


Legacy KB System (APS) Data: RESL200965 V1.0, Originally authored by KBAdPM on 01/08/2010, Last Edited by KBAdPM on 01/08/2010
Related ranges: ION Enterprise V6.0

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

 

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

Tenant Metering Software Commercial Edition (TMS CE) 2.5 Patches

Issue:

Tenant Metering Software Commercial Edition 2.5 patches. PLNS Patch.

Product Line:

TMS CE 2.5

Environment:

TMS Commercial Edition

Cause:

This document provides the details and install instructions for all officially released patches for Tenant Metering Software Commercial Edition 2.5

Resolution: 

This document is current through February 22nd, 2011

Instructions and Files


TMS 2.5 Patches (02.22.2011).zipTMS 2.5 Patch Installation Guide (02.22.2011).doc

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
 

 

ADVC Controller Test and Training Set does not show the correct series

Issue  
When the test and training set (TTS) is connected to the ADVC Controller it is showing a U-Series Recloser instead of a N-Series Recloser.

Product Line   
ADVC II, Recloser, U-Series, N-Series, and W-Series

Environment   
Testing the Recloser settings.

Cause  
The old calibration files took the form of the first Recloser series that the TTS connects to.  The series cannot be changed after that.

Resolution  
In order to have the TTS have the ability to switch between series the calibration file needs to be N24-150s (24kV 150kV BIL 1A CT's).
Attached is the calibration file, instructions on how to check the calibration file and how to load the file, and application notes about the calibration file.

Note:  The firmware of the ADVC Controller firmware must be A45-11.01 or above.

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

How many speakers can be linked to a Bluetooth aplifier 5600BTSA50?

The amount of speakers that can connect to the amplifier (5600BTSA50) is dependent on the wiring configuration, an whether it is wired in series or parallel. The speakers impedance also needs to be taken into consideration. The bluetooth for this device is used specifically for transmitting between devices (i.e. Phone, laptop) not speakers.

Basic specifications for the Bluetooth Amplifier 5600BTSA50 are:

• Input frequency: 2.4GHz
• Installed in roof space
• Bluetooth compatibility: A2DP Bluetooth enabled devices
• Bluetooth system: Bluetooth 2.1 + EDR/Class 1
• Range: up to 15m
• Audio output: 50W RMS per channel at 8Ohms impedance
• Power requirement: 24V, 3.75 amp, DC input (240V power source required)
• Amplifier type: Class D
• Frequency response: 200Hz – 15KHz
• Magnet: 20oz
• Sensitivity: < 90dB
• Weight: 1.3kg
• Dimensions: 130mm x 120mm x 45mm
• PIN code for secure pairing
• Zone personalising for easy pairing with Bluetooth device
• Green technology: smart power efficient amplifier with auto-sensing
ON/OFF

For further information please visit https://www.clipsal.com/Trade/search-results?q=5600btsa50

Or see attached PDF