label - 2530T-WE
b/holder bc clip cov fxd spigt
label - 2530T-WE
b/holder bc clip cov fxd spigt

Batten Holder BC Clip COV FXD SPIGT

Catalogue Number: 2530T
label - 2530T-WE
b/holder bc clip cov fxd spigt
label - 2530T-WE
b/holder bc clip cov fxd spigt
Colour: White Electric
Colour: Per UOM Std.
  • White Electric 1 PCE
Added to cart

Specifications

hide show
Product brand
Clipsal
Product or component type
BC lamp holder adaptor
Provided equipment
  • lamp holder
  • fixed mounting spigot
  • skirt
    • Colour tint
      white electric
      Device mounting
      surface
      [Ue] rated operational voltage
      250 V
      Connections - terminals
      4 terminals
      EU RoHS Directive
      Compliant
      Circularity Profile
      N/A

      Documents & downloads

      hide show
      Filter items
      • All

      • Product Brochures

      • Technical Leaflet

      • Installation Instruction

      • Operating Manuals

      • Specifications

      • Certificates (MSDS)

      • Corporate Marketing

      Frequently Asked Questions

      hide show

      What is alternative for Schneider part number 25730?

      The part number A9F55320 replaces 25730.

      Is there a specific 2530 that can be mounted on metal?

      No there isn't a specific batten holder as they can all be mounted on any surface surface providing it is earthed in accordance with AS3000.

      Is there a ceiling mounted battern holder available?

      Yes, the part number is 2530.
      Batten Holders, Note: The 2530 Series range of batten holders have been redesigned and are replacing 530 and old 2530 Series products, Batten holder BC straight with Clip-on cover.

      For further information please see https://www.clipsal.com/Trade/Products/ProductDetail?catno=2530
       

      How many watt is the batten lamp holder 530T capable of?

      The batten lamp holder 530T is capable of up 230W.
      Some of its key features are:
      • 250V
      • With built-in fastening Ppugs and screws
      • Easily removable cover by 120 deg rotation and visual indicators
      • Front access to terminal slots allowing easy adjustment of terminals, even after installation
      • Built-in safety feature to ensure removable cover does not fall onto globe
      • Protection against accidental finger access to terminal slots
      • No exposed, unsightly mounting screwheads
      • AS 1939-1991 standard
      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=530T
       

       

      What is the Clipsal lamp holders rated to for a heat lamp

      Most have a rating between 150-200, the 2530 in white has a 250W rating.
      Note this is a Bayonet Cap BC fitting not an Edison screw lamp holder 

      Is a C60N 25801 ok to operate on 24V DC

      Yes it is

      Is backing plate available for part no 530LT

      Unfortunately there is no backing plate available for this part

      What is the part number for a 10A 6kA 1p MCB

       The part code is 25802

      Is there a fixed angle batten holder available?

      Yes, the fixed angle Batten Holder is a  531. There is also an angled adaptor to suit 530 and 2530 series batten holders which is a 530AWP.

      Some of the key features are:
      • 250W
      • With built-in fastening Ppugs and screws
      • Easily removable cover by 120 deg rotation and visual indicators
      • Front access to terminal slots allowing easy adjustment of terminals, even after installation
      For further information please visit https://www.clipsal.com/Trade/search-results?q=batten%20holders&p=1
       

      What is the replacement for 25804 MCB?

      The replacement is A9F44120.

      User-added image
      A9F44120
      Acti9 iC60N 1P 20A C Miniature Circuit breaker

      For further information see:https://eshop.schneider-electric.com/product.aspx?org=21&lang=1&dist=276&prod_id=A9F44120

      What would the breaking capacity be on a 25801 C60N 6A 1p breaker if used with 24V dc

      The breaking capacity is 15kA

      What is the Pin out detail for the Modbus programming cable 110 XCA 20 3000?

      The pin out details of the Modbus programming cable 110 XCA 20300 is as shown in the attached.

       

      How Does Tenant Metering Software Commercial Edition (TMSCE) Calculate 15, 30, or 60 Minute Rolling Demand?

      If the data is collected on a 15 minute interval, there is no difference between rolling demand and present demand. Data that is collected on a 5 minute interval is the average of the current interval and the previous two. For example, if the data is measure at 2:00, 2:05, 2:10, 2:15, 2:20, 2:25, and 2:30, the rolling demand for 2:20 would be the average of the readings taken at 2:10, 2:15, and 2:20.
      With 15 minute interval data, the 30 minute rolling demand is calculated by averaging the previous demand interval with the current one. For example, data is taken at 2:00, 2:15, 2:30, 2:45, and 3:00. The 30 minute rolling demand for 2:45 is the average of the demand readings at 2:30 and 2:45.

      With 15 minute interval data, the 60 minute rolling demand is calculated by averating the current demand interval with the previous three. For example, data is taken at 2:00, 2:15, 2:30, 2:45, 3:00, 3:15, 3:30, and 3:45. The 60 minute rolling demand for 3:15 is the average of the demand readings at 2:30, 2:45, 3:00, and 3:15.


      Legacy KB System (APS) Data: RESL198518 V1.0, Originally authored by AnVa on 05/16/2009, Last Edited by AnVa on 05/16/2009
      Related ranges: Tenant Metering Software

      What is the VA rating of a 9001KM transformer light module?

      Issue:
      What is the VA rating of a 9001KM transformer light module?

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      9001 KM2 110-120 volt 25-30 hertz      2.2 VA
      9001 KM1 110-120 volt 50-60 hertz      2.4 VA
      9001 KM3 208-220 volt 50-60 hertz      2.5 VA
      9001 KM4 220-240 volt 25-30 hertz      2.2 VA
      9001 KM7 220-240 volt 50-60 hertz      2.0 VA
      9001 KM8 277 volt 50-60 hertz             2.4 VA
      9001 KM5 380-480 volt 50-60 hertz      2.8 VA
      9001 KM6 550-600 volt 50-60 hertz      2.5 VA

      What is the part number for surround to suit 2030?

      The surround to suit 2030 architrave is part number 2001.

      Some of the key features are:
      • 1 gang
      • Architrave
      • Curved side

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

       

      Process not running: Please start service" when trying to start the Event Notification Solution (ENS) Service

      Goals and Symptoms

      Symptoms
      When trying to start the ENS service, the error "Process not running: Please start service" is displayed.
      The Windows event log may also show the following error: APMService.exe "An attempt was made to access a socket in a way forbidden by its access permissions"

      Facts and Changes

      PRODUCTS Affected

      APM, ENS, ENM

      Causes and Fixes

      Cause

      Under some circumstances, the TCP port being used by the APMService.exe is already being used by something else in Windows.


      Resolution

      Change the port ENS is using.

      1. Stop all ENS services.
      2. Open the file APMService.exe.config in the Event Notification Solution\EventNotificationSoution\ folder for editing in notepad.
      3. Change the following line:
      <add key="Port" value="63387" />

      to:

      <add key="Port" value="25500" />
      4. Open the file service.xml in the Event Notification Solution\OPC Logger\ folder for editing in notepad.
      5. Change the following line:
      <ESService Machine="127.0.0.1" Name="PLActivePagerModule" URL="tcp://127.0.0.1:63387/apm.tcp"

      to:

      <ESService Machine="127.0.0.1" Name="PLActivePagerModule" URL="tcp://127.0.0.1:25500/apm.tcp"
      6. Restart the ENS services.

      Note: If port 25500 is also being used by Windows, a different port number may be necessary.


      Legacy KB System (APS) Data: RESL208357 V1.0, Originally authored by MaTh on 06/09/2012, Last Edited by MaTh on 06/09/2012
      Related ranges: SMS Add-on, Paging Module

      STBNIP2212 Advantys Ethernet NIM Firmware Upgrade - Exec v.2.30, Kernel 2.03, Web 1.20.04

      Release Notice

      The purpose of this resolution is to inform STBNIP2212 users that the Exec., Kernel, and Web pages have been upgraded to the following:

        • Exec v.2.30
        • Kernel v.2.03
        • Web pagev.1.20.04

      Goals and Symptoms

      A single file named stbnip2212_upgrade_[k]_v.2.03_[fw]_v.2.30_[web]_v.1.20.04.exe, is now available and will automatically run the loader utility program when executed and prompt the user to enter the IP address of the Ethenet NIM. The Exec, Kernel, and web files will load sequentially and then reboot the NIM when completed.

      Facts and Changes

      The new Exec., Kernel and web versions are field upgradable and will work with any STBNIP2212 Ethernet NIM hardware versions. The files for the Ethernet NIM can be found on Planet or as the Attachment to this Resolution.

      Causes and Fixes

      The following issues have been resolved in this upgrade:

      1. Version 2.30 corrects a problem where the Ethernet NIM would sometimes fail to go into Run after a power cycle.
      2. When power is cycled to an ATV31 when it is connected as a prefered module on an STBNIP2212 island, the ATV31 would come back up operational but the Advantys Configuration software would continue to display the ATV31 as failed. With Exec. v.2.30, the Advantys Configuration software will not show the ATV31 as failed after an ATV31 power cycle.
      3. Output values in the 'Data I/O' web page would retain their last value if the client communications was stopped, regardless of the fallback state of the output. In this version, the 'Data I/O' values now show INVALID when this condition occurs.
      4. The STBNIP2212 'I/O Data Values' web page will now display the entire 16 bit field when an Input or Output value is displayed in Binary. The display window on previous versions was too small and would not display the entire 16 bit field.
      5. The 'Save' option in the web page 'Network Interface Module Register' now works properly.
      6. The RS232 serial communications port on the Ethernet NIM would respond to any request, regardless of the address in the request. It now responds to the appropriate address.
      7. The RS232 serial port communications was too slow. Compared to Exec v.2.14, the RS232 serial port communications is now approximately twice as fast as previous installed Exec versions.
      8. Previous firmware versions of the STBNIP2212 had problems reading web page applets using Internet Explorer 7 browsers. These issues have been resolved in v.2.30.
      9. Assigning an IP via DHCP could take a minute and a half or longer. With version 2.30, the time to assign an IP via DHCP has been shortened to approximately 30 seconds.
      10. I/O modules on an island would fail to go into Ready if 15 or more Ethernet connections are made to the NIM during power up.
      11. The 'Process Image area' did not get set to zero if the network cable was removed from the NIM. Outputs would write the last data if the cable was reconnected. In version 2.30, the Process Image area is now cleared if the cable is disconnected and then reconnected. New data from the client is then written to the outputs.
      12. In Ethernet NIM Exec versions 2.27 & 2.28, assigning an IP using DHCP also required a valid Gateway address. If a Gateway address was not provided or was assigned 0.0.0.0, the assigned IP would default to the MAC derived IP address. Exec version 2.30 does not require a Gateway address when assigning an IP via DHCP.
      13. New Faulty Device Replacement (FDR) functionality: (Refer to the FDR User Documentation Attachment below)
        * Multiple FDR servers
        * FDR Functionality
        * Device Parameter file backup/restore
        * FDR Diagnostics
         
      The following Enhancement is included in this upgrade:
      1. A Link failure occurs when there is a disruption in communications between the Advantys Ethernet NIM and the device (ex: PLC) communicating to it. However, the outputs of an island can behave differently depending on where a link failure occurs within a network. Therefore, to allow the outputs to behave the same regardless of where the link failure occurs, an option called Link Failure Mode was added to the web pages for Exec. v2.30 in the Ethernet NIM. Further explanation is provided in the attachment Link Failure Mode Option.
         
      The following is an open issue with 2.30 that will be resolved in the next Exec release.
      1. A behavior has been indentified with version 2.30, which differs from version 2.14. After being on for approximately 15 minutes to 1 hour, the STBNIP2212 will reboot if the Rotary switches are set to "Device/Rolename" (DHCP mode) and no DHCP server is available to assign an IP address. The STBNIP2212 will not reboot if the Rotary switches are set to "Bootp" (default position) or any other position. If a bootp server is available and an IP address is assigned via DHCP, the NIM will not experience a reboot.

        A reboot causes the outputs to go to zero, which is the fallback condition.

      Attachments

      FDR User Documentation

      • (Removed File URL: 191005_4CE2/FDR_User_Documentation.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cc39d5d1fe079fe1c125760900108a76/fl_block_5/0.5C6?OpenElement&FieldElemFormat=gif)


      Link Failure Mode Option
      • (Removed File URL: 191005_4CE2/Link_Failure_Mode_Option.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cc39d5d1fe079fe1c125760900108a76/fl_block_5/0.14A8?OpenElement&FieldElemFormat=gif)

      Legacy KB System (APS) Data: RESL191005 V2.0, Originally authored by DaDz on 02/06/2008, Last Edited by DaDz on 08/05/2009
      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".