grid & plate assy arch 2gang

Grid Plate and Cover Switch Saturn - Less mechanism - Architrave - 2-gang - Horizon Silver

Catalogue Number: 4062
grid & plate assy arch 2gang
Colour: Horizon Silver
Colour: Per UOM Std.
  • Espresso Black 1 PCE 1
  • Horizon Black 1 PCE 1
  • Horizon Silver 1 PCE 1
  • Ocean Mist 1 PCE 1
  • Pure White 1 PCE 1

Specifications

hide show
Range of product
Saturn Series 4000
Product brand
Clipsal
Number of gangs
2 gangs
Product destination
switch
Marking
without marking
Mounting position
vertical
Sustainable offer status
Green Premium product
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)
Environmental Disclosure
ENVPEP130201EN
Circularity Profile
N/A

Documents & downloads

hide show
Filter items
  • All

  • CAD Files and Packs

  • Product Brochures

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

Can the 30USBCM charger fir into the Saturn 4062 plate

No, the 30USBCM Chargers are a 30 series mechanism and will only fit into the 403x plates. The 4032VH is the plate to use for a dual USB charger plate.

Do you still do the 406S double adaptor?

No this product has been discontinued and there is no alternative.

What is the part number of Saturn two gang arcitrave switch plate without LED indicators?

Saturn two gang architrave switch plate without LED indicators can be put together using the below individual components:
4062 - Saturn architrave, 2 gang,  grid and cover assembly (less mechanisms)
+
2 off 60PB -  Push-button switch mechanism, Saturn Series, No LED Indication, 250V 16AX/20A - 1 way / 2 way.
For further information, please visit:
https://www.clipsal.com/Trade/Products/ProductDetail?catno=4062
https://www.clipsal.com/Trade/Products/ProductDetail?catno=60PB

Saturn PB Switch DP 2way ?

There is No 4060 series option - use 30MD2-WE + 4031VH

do 60 series mechs into 403X plates

No they are designed to fit into a 406x plate as they need to be activated by the button cap that comes on the 406x plates.

What is the part number for the 4063 cover in OM

Saturn Covers not available on their own but Grid and cover is - 4063VH-OM

Saturn - is there an option for banana mechanisms in this range?

YES - 30BCRM OR 30BCBM OR both in a 4031 or 4032 Communication plate.

What is the 2way push button (latching) for the Saturn Range

 The parts you need is 60PBL if the 406* plates are used and a 30PBL if the 403* plates are used

Can I purchase the cover plates only for Clipsil Saturn Horizon 406x plates?

No, Grid with cover plates available but not cover plates only

What is the code for a 32A mech for Saturn 406* plates?

There is no 32A mech that fits directly into the 406* plates,
The 60R32-** and 60R32COOK-** will only fit into the extra switch position on the 4025XA-**

For a standard plate with a 32A mech you will need to use a 403* plate with a 30 series 35A mech, 30M35

What is part number for Saturn architrave 1 gang plate only?

The part number 4061 grid plate & cover only but no mechs.

What is the difference between 4062ELEDM & 32ELEDM?

The part number 4062ELEDM suits Saturn 4061 plates, however

32ELEDM Ssuits 4031VH plates etc

What is the maximum number of preset speeds for the Altivar ATV18 unit?

Issue:What is the maximum number of preset speeds for the Altivar ATV18 unit?
 
Product Line:ATV18
 
Environment:All
 
Cause:N/A
 
Resolution:The maximum number of preset speeds is 4.


 

What parts are needed to make up a four gang version of the 4063PBL in Horizon Black?

1x 4064VH-HB - 4 gang grid and plate assembly to suit 60PB Series (Note: The 4064VH is also available in Horizon Silver (HS), Ocean Mist (OM), and Pure White (PW))
4x 60PBL - Saturn Push-button with LED to suit 4060 Series (Note: You could also use the 60PB Saturn Push-button without LED to suit 4060 Series)

Why is my Conext CL showing an alarm code: 4661 & 4662 ( PV1&PV2 SPD Service Alarm)

Issue: 
Customer is calling to confirm alarm codes: 4661 & 4662 ( PV1&PV2 SPD Service Alarm) 

Product Line: 
Conext CL 18000NA Conext CL 25000NA Conext CL 20000E Conext CL 25000E

Environment:  
On site troubleshooting

Cause:
PV1 or PV2 input SPD reached End of Life
SPD remote control wiring issue

Resolution: 
Check the SPD and replace EOL cartridges if required
Check SPD remote wiring 

What are dimensions of Saturn Z4061 & 4061?

Dimensions for both Z4061 & 4061:

97.5mm (H) x 34mm (W) 31.6mm (D)

 

What is the socket to suit the Clipsal 492 492/32 492/32HD

Socket to suit is 402 series

402  402/32

What is the dimensions of a 4061AL architrave switch?

The overall dimensions for the 4061 Saturn Architrave switch is 34mm(W) X 97.5mm (H) 31.6mm(D)

Some of the key features are:

  • 1 gang
  • LED lighting Indication
  • 4000 series saturn architraive
  • horizontal and vertical mounting
  • 16AX switching current for fluorescent lamps

Please see diagram below:
User-added image
User-added image
For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=4061AL

Can I still purchase an Omegapak 8804 drive?

Issue:
Can I still purchase an Omegapak 8804 drive?

Product Line:
Omegapak 8804 drives

Environment:
All

Cause:
Need to replace an Omegapak drive

Resolution:
The 8804 Omegapack drives were discontinued in the mid-to-late 1980s, depending on the specific model.  These drives are no longer available, and new replacement parts are no longer available.  Repair may be possible though the Schneider Electric Drives Repair center, but this will be handled on a case by case basis.

Are Visio Files of NetShelter cabinets or other APC products available?

Issue:
Customers require Visio stencils of APC products. 
 
Product Line:
NetShelter SX
 
Environment: 
All versions and serial ranges. 
 
 
Cause:
Visio files are being requested.  
 
Resolution :
All Visio stencils are released to the public for free and available on the APC website: https://www.apc.com/prod_docs/results.cfm?DocType=Stencils
If you don't find a Visio of the product you're looking for you can contact Technical Support to ask if there is one, but all available Visio files should be posted to the link provided above.

We do not have Visio files for Smart-UPS or Back-UPS products. 

Other file types are available on the individual product pages of the APC website.
Example: go to the APC website and search AR3100, then go to that product page. Next, click on the Documentation tab. All available drawing files are listed under the Documentation tab.
 

Power loss of our RFI filter VW3A58407 and VW3A58408.

Goals and Symptoms

Power loss of our RFI filter VW3A58407 and VW3A58408.

Facts and Changes

VW3A58407
VW3A58408.

Causes and Fixes

This information is not available for the moment.
401 = 5 w
402 = 11 w
403 = 11 w

No information for 407 and 408.


Legacy KB System (APS) Data: RESL156483 V3.0, Originally authored by on , Last Edited by on
Related ranges: Altivar 58

What are the Commercial and Government Entity (CAGE) codes for Schneider Electric (US only)?

The CAGE codes for Schneider Electric/SQUARE D are listed below:
CAGE Code Company Address
04429 SQUARE D CO LEEDS MFG PLANT 940 MOORE ST NE LEEDS, AL 35094
05684 SQUARE D CO MIDDLETOWN MFG PLANT 1500 S UNIVERSITY BLVD MIDDLETOWN, OH 45044
07442 SQUARE D CO DALLAS ASSEMBLY PLANT 1111 REGAL ROW DALLAS, TX 7524
12670 SQUARE D COELECTROMAGNETIC INDUSTRIES DIV 1410 DONALDSON PIKE B-5 NASHVILLE, TN 37217
14280 SQUARE D CO LEXINGTON MFG PLANT 1601 MERCER RD LEXINGTON, KY 40511
14799 SQUARE D CO CHICAGO ASSEMBLY PLANT 9522 W WINONA SCHILLER PARK, IL 60176
19804 SQUARE D CO GRAND BAY OF BRECKSVILLE 6995 S EDGERTON RD SUITE 100 BRECKSVILLE, OH 44141
2E203 SQUARE D CO 810 GLEN EAGLE CT SUITE 100 BALTIMORE, MD 21286
4T466 SQUARE D CO 1010 AIRPARK CENTER DR NASHVILLE, TN 37217
51917 SQUARE D CO ASHEVILLE MFG PLANT 128 BINGHAM RD ASHEVILLE, NC 28806
51918 SQUARE D CO AUTOMATION AND CONTROL BUSINESS RALEIGH, NC 27611
51920 SQUARE D CO COLUMBIA MFG PLANT SUMTER HWY 76 AND 378 COLUMBIA, SC 29209
55947 SQUARE D CO SORGEL MFG PLANT 4065 N RICHARDS ST MILWAUKEE, WI 53212
56158 SQUARE D CO OSHKOSH MFG PLANT 3300 MEDALIST DR OSHKOSH, WI 54901
56302 SQUARE D CO CEDAR RAPIDS MFG PLANT 3700 6TH ST SW CEDAR RAPIDS, IA 52406
56303 SQUARE D CO 1717 CENTER PARK RD LINCOLN, NE 68512
56304 SQUARE D CO OXFORD MFG PLANT 5735 COLLEGE CORNER RD OXFORD, OH 45056
56365 SQUARE D CO CORPORATE OFFICES 1415 S ROSELLE RD PALATINE, IL 60067
63637 SQUARE D CO MISSOURI MFG PLANT 4800 PARIS RD COLUMBIA, MO 65202
63831 SQUARE D CO HUNTINGTON PLANT 6 COMMERCIAL RD HUNTINGTON, IN 46750
70745 SQUARE D CO SENECA PLANT 1990 SANDIFER BLVD SENECA, SC 29678
88434 SQUARE D CO 13191 CROSSROADS PKY N SUITE 205 LA PUENTE, CA 91746
88753 SQUARE D CO 3516 CONCORD RD YORK, PA 17402


Legacy KB System (APS) Data: RESL206488 V1.0, Originally authored by MaTh on 10/26/2011, Last Edited by MaTh on 10/26/2011
Related ranges: Standards Applied to Power Management PRODUCTS

PowerSCADA Expert - Maximum number of IODevices of MODNET type

Customer request:
To integrate in the PowerSCADA Expert (PSE) project 400 sets of Ethernet devices which support Modbus TCP protocol.
The question was if all the devices can be integrated to one PSE Server, and the SCADA system is redundant.
In the legacy software version, one IOServer could only have one TCP/IP Board and 255 Ports can be created on that type of Board.
Can we integrate all the devices into one PSE Server? If yes, then how to configure the communication including IO Server, Board, Port and IODevice?

Resolution:
The maximum limit in PowerSCADA software is of 16383 IODevices per project and 4095 simultaneous multiple protocols.
BOARD types have to be unique per IOServer.
You may find reference of the word "Channel" in various documentation resources.
To be clear, PORT = Channel.
PORT number limits are hardcoded into each communication driver.
The TCPIP driver (TCPIP.DLL) supports 512 PORTS per board since DLL version 2.4.4.0, thus MODNET driver (MODNET.DLL) supports 512 PORTS (channels) since driver version 2.6.21.0.

These limits are theoretical limits, in reality there are Kernel Queues that introduce another limitation.
[Kernel]Queue has a max of 5000 (which is also default value), but some drivers like Modnet consume more queues per channel than others.
Modnet consumes 13 Kernel Queues per PORT.
As a result, a 512 hardcoded limit for Modnet PORTs will be downgraded to 300-350 because of these queues.
So, consider the limit at 350 MODNET PORTS per BOARD (per IOServer).
If you use ModbusTCP/RTU Gateways, then you can have thousands of IODevices on the same IOServer, just because for each of the 350 PORTS you could have several different IODevices, with different Addresses (UnitID).
For example: 1 Gateway to collect 5 SEPAMs means: 5 IODevices (5 different IODevice Addresses), 1 PORT (the same PORT that uses Special Options for Gateway's IP address), 1 BOARD (TCPIP).

To overcome the 350 PORTS limit, more IOServers are needed.

Further, another reduction should be made, imposed by the recommended number of IODevices per IOServer.
In the same project, the same Cluster, the same Network Address, the PowerSCADA team recommendation (rule) is: either 50000 tags or 250 IODevices per IOServer. Whichever comes first.
To create another IOServer in the same Cluster and the same Network Address, simply add another IOServer but specify a different Port (this is the Port from the IO Server dialog window).
Doing so, you will need to define different Ports for the extra IOServers: default is 2082, so you may add any unused TCP port: 3082 for second IOServer, 4082 for third IOServer and so on.

Here are some configuration screenshots (using Excel and DBF Add-in) to illustrate the IODevices distribution per IOServers:

IOServers:


Boards:


Ports:


IODevices:



                                            
Created on 8th JUL 2015 by
Adrian Dicea
Global Expert Technical Support Engineer - Support Prime PSE / EGX

How do I Distinguish Different Versions of 4000 Series Display Modules?

Problem

My transmitter comes with a label that states "Do not interchange display with other sensors", or "Do not install display on a different unit. This display is for 4012 and 4032s only" or "This display is for 4102 and 4203s only" How come I can no longer swap displays on my transmitters?
 

Environment

4000 Series Transmitters, SCADASense Transmitters
 

Solution

The original Invensys displays used by the 4000 Series product line have been discontinued. Investigation into the new displays found that modifications to the new Invensys displays were necessary when the displays were used with a 4299 SI (Sensor Interface) board. The displays must be unmodified to function with an Invensys SI board.

Problems will arise if you try to connect an incorrect display to a 4000 Series Transmitter which is why we discourage swapping displays among transmitters.

  • Original Invensys displays with TRSS part number TBUM298016 will continue to work on all 4000 Series Transmitters
  • New Invensys Displays with TRSS part number TBUM298020 will work on all transmitters that contain an Invensys SI board (4012, 4032, 4202 and older 4102s built before October 2006)
  • New Invensys Displays with TRSS part number TBUM298021 or TBUM298022 will work on all transmitters that contain a 4299 SI board (4203 and 4102s built after October 2006)

To determine if you have a 4299 SI board or an Inversys SI board, open the 4000 Series Configuration Software, find the transmitter then check Status/Information.

Transmitters with a 4299 SI board will have a Sensor Software Version greater than 5.
 

Transmitters with an Invensys SI board will have a Sensor Software Version less than 5.

 

What can I expect if I have the wrong display on my transmitter?

If you have a 4299 display connected to an Invensys SI board, the display will go blank shortly after power up. Cycling power to the transmiter will bring back the display, but only for a short while. With the display out, the transmitter will continue to read valid data that will be accesible via polling.

If you have an Invensys display connected to a 4299 SI board, it will create invalid sensor readings (e.g. static pressure readings of 250,000 PSI. These invalid readings will also be reported to the flow computer or any other device polling the transmitter. Removing the display from the transmitter should allow the transmitter to read normal values again.
 

How can I tell the displays apart?

You can visually differentiate between the old and new style displays by looking at the back of the display (see attached pictures below). The PCB fills the display casing with the old style displays, and is more rectangular with the new style displays. The old style displays will work with any 4000 series product. The new style displays will flash a version string at power up like *LCDAT* .

During the transition, a small number of new boards were modified with one of the connector pins cut for transmitters with the 4299 SI Board.

Original Style Display
 


 

Short Term Display (removed pin circled in red)


 

New Style Display

Transmitters with the Invensys SI board can work with:

  • Original style display
  • New style display with version string *LCDAT* , *LCDAU* or *LCDAV*

Transmitters with the 4299 SI board can work with:

  • Original style display
  • New style display with version string *LCDAW*
  • New style display with cut pin and version string *LCDAT* , *LCDAU* or *LCDAV*

 

How do I setup the Altivar Process Drive to communicate over CanOpen?

Issue:
How do I setup the Altivar Process Drive to communicate over CanOpen?

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

Environment:
All serial numbers for Altivar Process Drive

Cause:
N/A

Resolution:
This FAQ will go over some basic settings to check. For a more detailed list of procedures on setting up the drive for CanOpen please reference the manuals attached.

EDS Files Basic Settings
Programming with the Drive
  • Program Communication Settings:
    • [Communication] COM, [CANopen] CnO
      • [CANopen Address] AdCo
        • This is a read/write parameter. The parameter number is 6051 via Modbus access
      • [CANopen Baudrate] bdCO
        • This is a read/write parameter. The parameter number is 6053 via Modbus access.
      • [CANopen Error] ErCO
        • This is a read-only Parameter. The parameter number is 6056 via Modbus access..
  • Program Command Settings:
    • [Complete settings] [Command and Reference]
      • ​For command speed from Network, program:
        • [Ref Freq 1 Config] Fr1 - Set to [CANopen] CAn 
        • [Ref 1B switching] rCb - Set to [Ref Freq Channel 1] Fr1
        • [Control Mode] CHCF - Set to [Not separ.] SIM
      • ​Video: Setting an Auto/Manual or Reference Switching on the Altivar Process Drives
  • Powercycle the drive
Programming with SoMove
  • [Parameters List] [Fieldbus] [Slot A - CanOpen]
    • Configure
      • CanOpen Address, Baud Rate & Error
Communicate with the Drive
  • Sending a command to the drive
  • Configuration of the Drive for Operation in I/O Profile
    • [Complete Settings] [Command and Reference] [Control Mode] - Set to IO
    • Command Word - CanOpen Register 2037/2
      Speed Reference Word - CanOpen Registers 2037/3 (Hz) or 2038/3 (rpm)
    • 16 bit word (Bit 0, 1, 2..... 15)
    • Start/Stop for FWD command must turn on bit 0
      • Write a 1 to start
      • Write a 0 to stop
    • Bit 1 to 15 are assignable like logic inputs
      • Example: To assign a fault reset to bit 7 - [Fault reset] - Set to Cd07 (Reference Programming manual for more details)
  • Configuration of the Drive for Operation with CiA 402 Profile (DriveCom Profile)
    • Works with other assemblies
    • [Complete Settings] [Command and Reference] [Control Mode] to [Not separ.] or [Separate]
    • Command Word - CanOpen Register 2037/2
      Speed Reference Word - CanOpen Registers 2037/3 (Hz) or 2038/3 (rpm)
    • No 16 bit word
    • Start/Stop
      • Sequence of values must be written to the drive
      • 6, 7 and 15
      • Toggle between 7 and 15 to start and stop or "RDY" to "RUN"
Troubleshooting

How to control an Altivar312 (ATV312) drive with a Twido PLC via Modbus RTU?

Goals and Symptoms

How to control an Altivar312 (ATV312) drive with a Twido PLC via Modbus RTU?

Causes and Fixes

Below is a step by step procedure describing a small application using a Twido Compact PLC controlling an ATV312 drive connected via Modbus RTU. A program example can be found at the end of this procedure.
Hardware and software used:

- TWDLCAE40DRF Twido PLC
- TWDNAC485T (RS485 serial interface adaptor with 3 pin screw terminal type connector)
- TwidoSuite 2.30.007 (free to download from www.schneider-electric.com)
- ATV312H075M2 variable speed drive


WIRING CONSIDERATIONS FOR THE MODBUS NETWORK

Connection:
ATV312 RJ45 connector pin 4 - A terminal of the Twido TWDNAC485T
ATV312 RJ45 connector pin 5 - B terminal of the Twido TWDNAC485T
ATV312 RJ45 connector pin 8 SG terminal of the Twido TWDNAC485T





ATV312 SETUP

The Altivar 312 control process using the communication bus is based on the CANopen CiA 402 profile status chart compatible with the IEC61800-7 standard. Each state represents an aspect of the internal behavior of the drive.

In practical terms, before you can start the motor you will have to write to the CMD command word, Modbus address 8501, a value of 16#0006 (drive goes to a Ready to switch on state that can be checked with ETA status word, Modbus address 3201), then a 16#0007 (drive goes to a Switched on state) and finally a 16#000F (drive goes into an Operation enabled state, drive running).

Please refer to the chart and description of the states at the end of this document.

Relevant parameters:

  • 1. Drive Modbus Address (ADD) - 4 in our example (default: 1)
    2. Modbus baud rate (TBR) - 19200 in our example (default)
    3. Modbus com format (TFO) - 8-E-1 in our example (default)
    4. Level of access control (LAC) - change to Level3 (default: Level1)
    Note: When the drive is controlled via a communication bus, it is advisable to configure the access level "LAC" = "L3":
    5. Configuration reference 1 (FR1) - change to Modbus (default: AI1).
    6. Control channel 1 config (CD1) - change to Modbus (default: Terminal)
    Note: Change CHCF Channel mode config to Separate to be able to change this parameter. You can change it back to Not separate after that.


TWIDOSUITE CONFIGURATION
Note: the program example is attached to this resolution.

1. Your Twido controller must be configured as a Master:



2. You have to add a Generic Modbus element with a Modbus address, 4 in our example


3. Configuration of the Comm Macro
Set the Modbus address of the drive in the Network address field.
Comm Macro zero is used in this example to read N words and write N words.

C_RDNW
We will read one word, ETA status word, Modbus address 3201. C_RDNW will use 8 registers (1+7), from %MW0 to %MW7.
C_RDNW _ADDR1_0 sets the address of the register to be read from the drive (%MW3:=3201).
C_WRNW 0 1 sends the Modbus message to the drive. (0-comm macro instance, 1 number of words to be read)
The result will be read in C_RDNW _VAL1_0 or %MW7 in our example.

C_WRNW
We will write two words, CMD control word, Modbus address 8501 and LFr frequency reference, Modbus address 8502. C_WRNW will use 11 register (2+9) from %MW20 to %MW30.
C_WRNW_ADDR1_0 sets the address of the starting register to be written in the drive (MW23:=8501).
C_WRNW_VAL1_0 sets the value of the first register be to written (%MW26, the CMD control word value)
The second value to be written is set with %MW27 and this will be the LFr speed reference.
C_WRNW 0 2 sends the Modbus message to the drive.(0-comm macro instance, 2 number of words to be written)





ADDITIONAL INFORMATION


IEC 61800-7 status chart




Description of the status chart states




CMD control word (W8501)


ETA status word (W3201)


ATV312 Communication Menu Structure



This completes the step by step procedure on how to control an Altivar312 (ATV312) drive with a Twido PLC via Modbus RTU.

Attachments

(Removed File URL: 207065_2002/Twido_ATV312_Comm_Macro.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/17453b735252b685c125797d005801cc/fl_block_5/0.EA?OpenElement&FieldElemFormat=gif)


Legacy KB System (APS) Data: RESL207065 V1.0, Originally authored by TVe on 01/06/2012, Last Edited by TVe on 01/06/2012
Related ranges: Twido, Altivar 312