lock ring pvc 80mm bsp

Fixing Accessories, PVC, Screwed Lock Rings, 80mm - With 80mm BSP Thread

Catalogue Number: 260P80
lock ring pvc 80mm bsp
Colour: Electric Orange
Colour: Per UOM Std.
  • Electric Orange 1 PCE
Added to cart

Specifications

hide show
Range
Clipsal
Product or component type
lockring
Accessory / separate part category
fixing accessory
Range compatibility
Material
PVC (polyvinyl chloride)
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

What material are the Iconic Styl plates made from?

The Iconic Styl plates are made from real aluminium material with high quality anodised finishes. Sandblasted surface for a modern ‘satin’ appearance. 

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

Where can I see the Iconic Styl?

You can see the Iconic Styl on display at Clipsal display centres from late October onwards.


For further information on this plate range please visit: https://www.clipsal.com/iconic

What's are the new colours in the Iconic Series?

There are 3 colours available in the new Iconic range:
Silver (-SV)
Crowne (-CE)
Silver Shadow (-SH)
This is in an addition to the colours that are already available (Vivid White (VW), Cool White (CY), Warm White (WY), Extra white (XW) and lastly Anthracite (AN).

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

How is the Iconic Styl plate range manufactured?

The Iconic Style plate range is manufactured by an Extruded piece of aluminium is used to create the basis of the unique oval shape of this design.
The anodising process is used to create the metallic colours.  Anodising increases resistance to corrosion and wear.
The extruded aluminium is machined to create the necessary shapes for the plastic parts.

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

Can I use a wind turbine with my MPPT 60/80 charge controller?

 The MPPT 60/80 charge controllers are not compatible with wind turbines. The MPPT 60/80 charge controllers are designed to work with solar panels only. 

How do i seal up a 50mm hole in the 230DRAVL?

Using parts 220S50-GY and 260/50-GY. Placethe 260/50 on the inside and the 220S50 on the out side place it in the hole and screw them together. This willl then seal the hole.

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

Are magnetic current transformers available for the Sepam 60/80 relays?

Magnetic current transformers are CSP APS_SENSORS, connected on the Sepam 2000 through BNC/BNC cable. This solution was not implemented on the Sepam 60/80 range and is not available.

How to find the modules in the SoSafe software for XPSMCMC0000S1 and S2?

For the expansion modules there is no configuration required or possible
          This means that there is no impact
on the configuration when you split the safety module to different island.
 

When adding an input module or several, the process image will not be extended only into end, but
the process image will be automatically rearranged according to type of modules following the order in next list:

1. XPSMCMCP0802*
2. XPSMCMMX0802*
3. XPSMCMDI1600*
4. XPSMCMDI0800*
5. XPSMCMDI1200MT*
6. XPSMCMEN0200SC* or XPSMCMEN0200HT* or XPSMCMEN0200TT*
7. XPSMCMEN0100SC* or XPSMCMEN0100HT* or XPSMCMEN0100TT*
8. XPSMCMEN0200*

This means, if adding a XPSMCMMX0802 module to rack and configuration behind an existing DI module,
the addressing of inputs of MX module will appear in front of addressing of inputs of DI module.
Change of order in Configuration

 
In addition also order of outputs will be automatically rearranged according to type of modules following the order in next list:
1. XPSMCMCP0802*
2. XPSMCMMX08O2*
3. XPSMCMDO0004*
4. XPSMCMRO0004*
5. XPSMCMRO0004DA*


Also, What does it mean by "The XPSMCMCO0000S1• module has only one channel and must be connected as the first (remote) or last (local) module."???  page 142 of the user manual.

  The XPSMCMCO0000S1• module has only one channel (connector for an RS485 cable) and can only used as the first (remote) or last (local) module in the chain.
  But you can use the XPSMCMCO0000S2• instead of an XPSMCMCO0000S1•
module!!!

  if you have an expansion bus with 3 or more island, each island in the middle need an RS485 connecting (channel) to the previous and a second RS485 connection (channel) to the following island in the chain.
  Only the first and the last island in the chain need only one connection (channel) to another island.
 

The XPSMCMCO0000S• are communication expansion modules which allow the connection of XPSMCMCP0802• Modular Safety Controller with expansion modules placed remotely (≤50 m/≤164 ft). Up to six islands can be created using the communication modules with a total length of 250 meters (820.2 ft) and a maximum of 50 meters (164 ft) between two communication modules.
The system response time does not change with the use of the communication modules.
Using RS-485 shielded cable (see page 175), two XPSMCMCO0000S• modules placed at the desired distance can be linked together thus joining the expansion modules to the controller.
Each XPSMCMCO0000S2• module has two independent connection channels; the connection of two XPSMCMCO0000S2• modules can be accomplished by wiring either channel.


With the setup above, can the EIP module on the local rack have all of the status of the remote IO modules?
   Yes, the communication module get all the data from the CPU module and must therefore be mounted on the local island (together with the CPU module).
   How to find the correct addresses are described in the attached document: ( XPSMCM communication modules description_20150929.pdf)

 

     

How do I troubleshoot a copper Modbus Plus network physical installation?

Goals and Symptoms

How do I troubleshoot a copper Modbus Plus network physical installation?

Causes and Fixes

The following are some basic troubleshooting tips to check a copper MB+ physical network installation. Good cabling practices should always also be employed in routing and installing MB+ cabling:

1 Ensure only Modicon cabling and cabling components are used.
2 Ensure no two adjacent nodes have less than 10 of physical cable between them (except if using Momentum product with cluster mode components).
3 Ensure there are no splices.
4 Ensure the topology is purely linear (branching is not allowed).
5 Ensure taps are properly sided left-to-right, left-to right. (The grounding lug on the standard taps can be utilized to determine proper siding).
6 Ensure all nodes are properly grounded.
7 Ensure no more than 32 nodes exist on the network without a RR85 repeater (usage of a RR-85 repeater allows up to 64 nodes max on the network).
8 Ensure the total network length does not exceed 1500 without usage of a RR-85 repeater (3 RR-85 repeaters can be utilized to connect up to 4 segments to make a total maximum network length of 6000'.
9 Check the resistance of the MB+ network. Disconnect all nodes from the network then measure resistance between the white and blue leads at any point. The resistance should be approx. 60 Ohms (derived from two 120 Ohm resistors in parallel). While spec is 60-80 Ohms, If 68 or more Ohms is read, then check the network for loose connections or damaged ferules on taps. Read resistance directly across a tap to check for resistance. Virtual continuity should be read. If more than negligible resistance is read, reseat connections. If this does not reduce resistance, replace the suspect connector or tap. If 120 Ohms of resistance is read, check cable for a break or loss of end termination at either side of the network.

Legacy KB System (APS) Data: RESL213012 V1.0, Originally authored by MiMe on 11/14/2013, Last Edited by MiMe on 11/14/2013
Related ranges: Modbus Plus

Using the DATA_EXCH block to issue a function code 15 (Write multuiple coils) from a M340 Ethernet interface.

Goals and Symptoms

To use the DATA_EXCH FB in Unity Pro to issue a modbus function code 15 from a Ethernet interface in a M340 PLC system.

Facts and Changes

A minimum version of Unity Pro v4.0 and a M340 CPU or NOE v2.0 must be used for the DATA_EXCH to work properly.

Causes and Fixes

First open the Project Settings form the tools menu in Unity Pro.


Under the Language Extensions tab check off directly represent array variables, Allow dynamic arrays, and disable array size compatibility check.
Then press OK.



Next open the variable editor and create the variables for the DATA_EXCH block

ADDD NEW SCREENSHOT

In this example 4 registers will be read from starting input register %IW1 (30001) of slave device connected via MB TCP/IP. This information is shown above in the bytes of the EMIS_PARA variable.

Explanation of the EMIS_PARA variable

To understand the setup of this array you must take each byte of each word separately.
In the first word (16#000F) the 2 bytes are 00 (high byte) and 0F (low byte). The low byte (0F) is the MB function code 15. The high byte (00) is the first part of the starting address in the slave device.
In the second word (16#0001) the low byte (01) is the rest of the starting address in the slave and the high byte (00) is the start of the number of coils to write.
The next word has the low byte of the number of coils to write (04) is used and next is the Number of bytes to send and the appropriate data.

If you look at the 7 bytes (in Hex) individually you get: 0F 00 01 00 04 01 0A

0F = MB function code 15
00001 = 1 decimal (%M1 or 00001)
0004 = Number of coils to write
01 - one byte to write
0A - 0000 1010 (Data to write)

The last thing to mention here is that the forth word of the management parameter (Manage_PARA) is equal to the size in bytes of the transmitted data. In this case 7.


Now create a new FBD section in Unity Pro and press OK.



Add a ADDM and DATA_EXCH block and link the parameters as follows.



Note: In a M340 the TYP parameter is always a 1
The string input for the ADDM block must be chosen to meet the requirements of your network. An explanation of the syntax of this input can be found in the Unity help files.
In this example %M0 is used to trigger the function code 6 and the slave device is located at 192.168.40.45.

Build and download to the M340.

Open a animation table and trigger %M0. You should see the RECP parameter (RECIEVE_DATA) values. The first register contains the function code used in request in the low byte (04) and in the high byte the number of bytes returned in the responce (08). Then the following four registers contain the data.
Also the first word of the Management parameter should also be changing while the block is enabled. This indicates successful transmissions.