clip conduit 25mm with nail

Cable Management Fixing Accessories, 25Mm, Zinc Plated Half Saddle, Fixing Nail

Catalogue Number: 180N25
clip conduit 25mm with nail
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Product brand
Clipsal
Diameter
25 mm
Material
steel
Surface treatment
zinc plated
Length
57.3 mm
Width
26 mm
Height
26 mm
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

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

Is the calibration equipment for PowerLogic and ION meters ISO 17025 certified?

Issue
ISO 17025 certification for calibration equipment used for PowerLogic and ION meters

Product Line
PowerLogic Meters
ION Meters

Environment
ISO 17025 Certification

Cause
Customer is unable to find certification for Schneider Electric’s calibration equipment used for the PowerLogic ION meters

Resolution
PowerLogic and ION meters' calibration equipment is not currently certified per ISO 17025 standards. The reason for this is that the calibration houses (e.g. 3rd party) are required to meet ISO 17025 certification standards as well. Not all the calibration houses used for PowerLogic and ION meters meet these requirements; Schneider Electric, therefore, is not able to attain ISO 17025 certification on PowerLogic and ION meters.

The ION meters are shipped from the factory with a certificate of compliance and calibration. In the event that this certificate was lost or never recieved, a copy can be obtained by providing the meter's serial number and sending the request to technical support.

When installing the PowerChute Business Edition Server, the configuration wizard does not launch on Windows Storage Server 2008 or Windows Small Business Server 2008.

Issue:
When installing the PowerChute Business Edition Server, the configuration wizard does not launch

Product:
PowerChute Business Edition

Environment:
Windows Storage Server 2008 or Windows Small Business Server 2008

Cause:
The 8.3 file name format is not supported by default on these two operating systems but the wizard needs it enabled in order to run correctly.

For information on Windows 8.3 file naming convention please see Windows File and Directory Names

Solution:

To enable this format on Windows Storage Server 2008 and Windows Small Business Server 2008, follow these steps:

1. Type this at the command prompt with administrator privileges.

     C:\>fsutil behavior set disable8dot3 0

2. Reboot Windows

3. Confirm the enabling of the 8.3 file name format by typing this and pressing Enter:

    C:\>fsutil behavior query disable8dot3
    
    The following should then display.     disable8dot3 = 0

(If it states"" = 1"", then 8.3 is still not enabled, please repeat).
 

Updated: Why is my Network Management Card losing SNMPv3 communication?


Issue

My Network Management Card (NMC) is losing SNMPv3 connectivity after a certain amount of time but other communication protocols (web, FTP, SSH, Telnet, SNMPv1, etc) continue to work properly.


Product Line

 

  • Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619
    Devices with an embedded Network Management Card 1 include (but are not limited to): Metered/Switched Rack PDUs (AP78XX, AP79XX), Rack Automatic Transfer Switches (AP77XX, Environmental Monitoring Units (AP9320, AP9340, NetBotz 200)
     
  • Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH
    Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP86XX, AP88XX, AP89XX), Certain Audio/Video Network Management Enabled products.
     
Environment
 
  • All serial numbers
  • Any device listed above utilizing SNMPv3
  • NMC1 AOS v3.7.0 and below; NMC2 AOS v5.0.X and below
  • NMC1 AOS v3.7.3 and higher


Cause

An issue has been identified with the SNMPv3 task on Network Management Card 1 and 2 based devices. SNMPv3 communication will be lost after approximately 49 days and 17 hours. The NMC will continue to run normally, with the exception of the SNMP process, which will not run.


Resolution

Update (July, 2016): Specific to NMC1 products, this issue had previously been fixed for AOS 3.7.3 and higher. The maximum SNMPv3 uptime allowed was modfied from 49.7 days to 497 days. At the 497 uptime day mark, assuming the management uptime had reached this point, the Network Management Card interface would have had to be rebooted though the web, CLI, or SNMPv1 interfaces in order to regain SNMPv3 communication. NMC2 AOS v5.1.X also contained a fix to avoid an SNMPv3 communication loss completely.

With NMC1 AOS v3.9.2 and higher, this issue has been fully resolved and the 497 uptime limitation has been lifted and SNMPv3 communication through StruxureWare Data Center Expert or any third party SNMPv3 NMS will not be affected after 497 days of uptime. This AOS (or newer) will be released for different firmware applications in the coming months which are available at https://www.apc.com/tt/en/tools/download/. Certain applications are available immediately, such as Rack PDU.
 

SPM 7.0 / 7.0.1 - Installer fails at step CheckAppModsDatabase

Issue
During a 7.0.1 install or upgrade, the installer fails at step CheckAppModsDatabase. It will be considered an incomplete install.
Re-trying does not resolve the issue.
In the Setup log, there will be a long stack trace resembling one of the ones listed in the Causes section below.

Product
Struxureware Power Monitoring Expert 7.0

Environment
Installer

Cause 1
The Windows account that SQL Server service is running as, does not have file/folder access to the location stated in the error. It's trying to execute a bulk load from file Unit.xml but fails. This is usually because service has been run under non-standard account. (i.e. something other than LOCAL SYSTEM, which is usually the default.)

Installer log will indicate an error was found in ApplicationModules.log file. Navigate to the log file as listed in the error message and open it. Error will resemble:
 

    • Starting Synchronization of [CommonDataModel].[Unit]
      Msg 4861, Level 16, State 1, Server STANDALONE\ION, Line 4
      Cannot bulk load because the file "C:\Users\Administrator\Desktop\SPM 7.0.1\setup\SetupSupport\Database\ReferenceData\CommonDataModel\Standard\Unit.xml" could not be opened. Operating system error code 5(Access is denied.).
Resolution 1
Either
a) temporarily grant read/write permissions to the folder listed in the error, to the user account SQL Server is running under.
or
b) change SQL Server to run under the LOCAL SYSTEM account.
Then re-try running the installer to complete.

Cause 2
ApplicationModules database files (.mdf and .ldf) have already been created at the target location, but are not attached to SQL Server. The installer tries to re-create the files but fails. This situation can occur when trying to re-configure multiple times (for instance, after encountering the situation described in Cause 1).

Installer fails with message "The ApplicationModules database could not be found." Installer log contains the following error:
    • executeNonQuery(CREATE DATABASE ApplicationModules ON ( FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.mdf'), ( FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules_log.ldf') FOR ATTACH, master) Failed on exception:
      System.Data.SqlClient.SqlException (0x80131904): Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.mdf". Operating system error 5: "5(Access is denied.)".
      at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
      at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
      at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
      at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
      at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
      at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
      at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
      at SchneiderElectric.Installer.InstallTools.ConfigureSQL.ExecuteNonQuery(SqlCommand command, String dbName)
       
ApplicationModules.log file contains the following error:
    • Creating ApplicationModules...
      Msg 5170, Level 16, State 1, Server STANDALONE\ION, Line 1
      Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION\MSSQL\DATA\ApplicationModules.MDF' because it already exists. Change the file path or the file name, and retry the operation.
      Msg 1802, Level 16, State 4, Server STANDALONE\ION, Line 1
      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

Resolution 2
Delete or rename the existing ApplicationModules database files, the re-run the installer. Let the installer re-create the database and complete the install.

Cause 3

The installer fails to create the application modules database successfully.

Resolution 3

Checking the diagnostics within the C:\Program Files (x86)\Schneider Electric\ION Enterprise\Applications\Diagnostic shows the following error message: "CREATE DATABASE failed. Primary file must be at least XX MB to accommodate a copy of the model database."

Instead of "XX" an actual file size will be given. In this situation SQL is attempting to create the Application Modules database, but the Model database is larger in size. All newly created SQL databases must be larger in size than the model system database to succeed. Within SQL Management Studio backup and perform a shrink operation on the model database which should allow the installer to succeed creating the Application Modules database. Right click on the model Database -> tasks -> shrink.