block mounting 3gang arch

Mounting Block, 3 Gang

Catalogue Number: 70/3
block mounting 3gang arch
RRP (Inc. GST)
Colour White Electric (WE)
  • White Electric 1 PCE
  • Black 1 PCE


hide show
Product brand
Product or component type
mounting block
Fixing center
97 mm
25 mm
116 mm
36 mm
PVC (polyvinyl chloride)
Number of gangs
3 gangs
Sustainable offer status
Green Premium product
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

Frequently Asked Questions

hide show

Is part number 70/3 available in black?

Yes part no 70/3 is available in Black.

What are dimensions of part number 70/3?

The part number 70/3 has dimensions 116mm x 36mm x 25mm.


What is the part number for a 3 gang architrave switch that will fit to mounting block 70/3?

The part number for a 3 gang architrave switch that will fit to mounting block 70/3 is - 33A

For further information , visit link below:-
User-added image

mounting block for C2000 series arcitrave 2 gang

 Part number - 70/2

What is the part number of the mounting block to suit C2030, Classic C2000 series 1 gang architrave switch?

70/1 is the part number of the mounting block to suit C2030.

Key Features

  • Moulded surface mounting blocks
  • With metal inserts
  • impact resistant
  • Mounting direction: Horizontal and vertical
  • Cable entry: Straight
  • To suits 1 gang architrave switches
For further information, please visit

How to restore the RS-485 communications on a 'Tesys U' connected to a Tesysport..

Goals and Symptoms

How to restore the RS-485 communications on a 'Tesys U' connected to a Tesysport.

Facts and Changes


Causes and Fixes

If '140NOE77111 'communications to the Tesysport is recovered after a lockup, the RS-485 connection to
the 'Tesys U' does not get restored. When this happens, the ERR led on the 'Tesys U' will be flashing.

In order to re-establish the RS-485 Modbus communications to the 'Tesys U', the recovery bit (bit 3 of
word 703) must be reset.

The following is from page 58 of the 'TeSys® U LULC032-033 Modbus Communication Module
Users Manual'.

Recovery After Loss of Communication
After acknowledgment by setting bit 703.3 to 1, recovery occurs according to the states of control

bits 704.0 and 704.1.

To resolve the issue the application needs to be modified to

  • Detect a 'Loss of communications with a master warning' using word 109 bit 15 as described on page
58 of the user manual.
  • Set bit 3 of word 703 upon detection of the communications loss.
  • Reset bit 3 of 703 after the 'Loss of communications with a master warning' is cleared.

Legacy KB System (APS) Data: RESL201897 V1.0, Originally authored by AlCh on 12/16/2010, Last Edited by AlCh on 12/16/2010
Related ranges: Modicon Quantum

How to troubleshoot an Altivar Process Drive with an Input Phase Fault

Troubleshoot an Altivar Process Drive with an Input Phase Fault (PHF)

Product Line:
Altivar Process Drive (ATV630, ATV930, ATV650, ATV950, ATV660, ATV960, ATV680, ATV980)

All serial numbers for Altivar Process Drive


  • Loss of one phase on the input side of the drive

Probable cause:
  • Drive incorrectly supplied or a tripped fused.
  • One phase missing.
  • 3-phase drive used on a single-phase supply mains.
  • Unbalanced load.
  • Check the power connection and the fuses.
  • Use a 3-phase supply mains.
  • Disable the detected error by [Input phase loss] IPL = [No] nO if single phase supply mains or DC
    bus supply is used for programming only
The Process drives are not currently available to work with 1 phase input 3 phase output. 

How to connect ClearSCADA servers using Advanced EWS driver


The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.

The Advanced EcoStruxure Web Services Client driver (Advanced EWS driver) allows communications with servers that comply with EcoStruxure Web Services version 1.1, which includes ClearSCADA servers.
This article is a quick start guide showing how to connect two ClearSCADA servers and make the client machine (ClearSCADA machine that will run the Advanced EWS driver) to read both current and historic data from a particular point. For more details on how the driver works, please refer to the manual, at Help > Contents > Driver Reference > EcoStruxure Web Services Client - Advanced Driver.

First, lets check the configuration that must be done on the ClearSCADA that will act as server.
Right click on the $Root object, select "Edit Properties, go to the "EcoStruxure Web Services" tab:

Enable the Web Services and select a ClearSCADA user with rights to access the points that will be read by the other ClearSCADA machine. Save the changes.
Also, make sure WebX is running on the server machine and take note of the port in use (HTTP or HTTPS).

On the ClearSCADA machine that will be the client, let's create a few Advanced EWS driver objects, starting with an Schneider Electric EWS - Advanced > Server object:

Put the object "In Service" and set the appropriate "Server URL". In this example the URL used was:
The client will communicate using HTTP to IP address, port 82, which is where the other machine's WebX server is listening.

Now let's create a Schneider Electric EWS - Advanced > Group object:

Put the object "In Service", add the Server object we just created to the "Servers" list and set suitable "Scanning Intervals" for Current Data and Historic Data. Save the changes.

Now it is time to create the first point, in this case a Schneider Electric EWS - Advanced > Analog Point object:

On the "Analog Point" tab, put the object "In Service", set "EWS Group" to the Group object we just created and browse for the "Current Data Id" and "Historic Data Id"  of the point we want to read data from the server machine.

Don't forget to enable historic on the point, then save the changes.

You can check the connection status looking at the "View Status" dialog box from the Server object:

If the connection to the server machine was successful, the "State" will be "Healthy" and the driver will poll current and historic data periodically.
Historic lists for the point on the server side and on the client side should be the same:

Note: In ClearSCADA 2017 R3, ClearSCADA 2017 R2 and ClearSCADA 2017 from build version 7013 (~15th March 2019) onwards ensures no WebX licence is consumed. Previous versions of ClearSCADA may consume a WebX licence under certain circumstances which may stop users successfully connecting.