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

Electric Orange | Fixing Accessories, PVC, Screwed Lock Rings, 80mm - with 80mm BSP Thread

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

Item Number: 260P80-EO

RRP (Inc. GST)
Colour Electric Orange (EO)
  • Electric Orange 1 PCE



Qty UoM EAN Colour





Product or component type


Sustainable offer status

Green Premium product


Range compatibility

REACh Regulation

Free of Substances of Very High Concern above the threshold

REACh free of SVHC


EU RoHS Directive

Pro-active compliance (Product out of EU RoHS legal scope)

Toxic heavy metal free


Mercury free


RoHS exemption information


China RoHS Regulation

 Pro-active China RoHS declaration (out of China RoHS legal scope)

Environmental Disclosure




PVC (polyvinyl chloride)


Accessory / separate part category

fixing accessory

Package 1 Weight

0.1 kg
Show all specifications

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

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. 

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*
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*
3. XPSMCMDO0004*
4. XPSMCMRO0004*

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•

  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)



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

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

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.