622T1

Switch Grid Plate and Cover, 1 Gang, Telemecanique

Catalogue Number: 622T1
622T1
Colour: White
Colour: Per UOM Std.
  • White 1 PCE
Added to cart

Specifications

hide show
Range of product
PDL 600 Designer Series
Product brand
Clipsal
Number of gangs
1 gang
Product destination
switch
Material
metal

Frequently Asked Questions

hide show

Do we do a 622T1 with a smaller diameter hole

No, only version available to fit 22mm

Is there a LED version of the PDL 610MN

No but you could use a harmony indicator in a 622T1

What is the PDL plate to fit Push buttons ?

622T1, fits one push button
622T2, fits two push buttons
recommended to use with Harmony Style 5 range

What is a keyed selector switch to fit PDL 600 Series plate, key needs to be removed on / off position

Use PDL 622T + ZB5 key selector switch

Do the HV circuit breakers and contactors work at 60 Hz ?

The HV circuit breakers and contactors work as well as 50 Hz and 60 Hz.
IEC 62271 is applicable to a.c. circuit-breakers designed for indoor or outdoor installation and
for operation at frequencies of 50 Hz and 60 Hz on systems having voltages above 1 000 V.

 

Can you use the 624TM to run halogen and incandescent lighting

Yes 624TM can be used for both halogen and incandescent lighting

Does the PS622T1 come in black ?

No - White only

What is the alternate for 623TM, PDL trailing edge dimmer mechanism?

PDL 624TM is the alternate for 623TM trailing edge dimmer. PDL 624TM is rated to 450VA.
 

Key Features

  • Trailing edge control suitable for controlling incandescent globes, 240 V halogen lighting, and ELV lighting supplied by electronic transformers
  • 0 to 40 deg C
  • Mounting center: 84 mm
  • 1 or 2-way operation
  • Soft start operation
  • User adjustable minimum brightness
  • Ability to multi-gang in 600 series plates
  • Over temperature compensation
For further information, please visit https://updates.clipsal.com/ClipsalOnline/Files/Brochures/W0000844.pdf

 

If a PDL 624TM dimmer is damaged due to a surge caused by a light bulb blowing is this covered under warrantee

No the warranty covers manufacturing faults not surges

What is the min/max load on PDL 624TM?

Maximum Load: 450W, 1.8A resistive. Minimum Load: 20W, 0.1A resistive
https://www.pdl.co.nz/product-details.aspx?rcat=products&catid=0&id=1924

XCSE application questions; using one XCSE7312 + XPSAF510 to achieve Cat.4 according to XCSE instruction sheet

Goals and Symptoms

 

 

XCSE questions, using one XCSE7312 + XPSAF510 to achieve Cat.4 according to XCSE instruction sheet.
Can this combination completely replace 2 safety limit switches +XPSAF5130? Does it indeed achieve Cat.4?
What happen if the only actuator is broken and the main part still remains in the head of XCSE7312?

 library/SCHNEIDER_ELECTRIC/Adobe%20Acrobat%20Document.pdf

Facts and Changes

 

XCSE7312
XPSAF5130
locking function
0 speed detection

 

 

Causes and Fixes

 

 

1) Firstly it is right that the XCSE7312 (locking function without electromagnet power supply) + XPSAF5130 + ... can achieve a PLe or SIL3 solution according to ISO 13949-1 or IEC 62061 standard. Attached some validated solution with XCSE+XPSAK (equivalent to XPSAF)+XPSVNE+... (shown in the Preventa solutions catalogue), certified PLe or SIL3 (so in highest safety level or in cataegory 4)

2) Can this combination completely replace 2 safety limit switches +XPSAF5130? what do you mean by 2 safety limit switches?
I understand it is 2 red limit switches without locking function. Attached some validated solution with 2 XCSM in combined mode+XPSAC+..certified PLd or SIL2 (category 3). If you replace the XPSAC by XPSAF, you can reach PLe or SIL3 after PL or SIL calculation of the complete safety chain solution; so category 4. Attached another equivalent solution with auxiliary contactor monitoring reaching PLe or SIL3 (or category 4).

Can this combination can replace the first one?
Answer : no because in this second case, the locking function, dedicated for high inertia machine, does not exist. So if the XCSE is used in association with 0 speed or a safety timer, your customer needs this locking function.

In this case I suggest the attached XCSLF solution with XPSMC controller, associated to 0 speed for high inertia machine, which proposes a high safety level solution with 2 switches and a locking function. XCSLF lock switch has the same function as the XCSE, not in the same format.

3) What happen if the alone actuator is broken and the main part still remains in the head of XCSE7312? I understand the actuator is the flat-head key XCSZ01 or XCSZ02 or ... In this case, if the main part stays into the head, the switch detects it like a normal key into the head, so machine in operation. We never heard about broken actuator in the XCS metal range (XCSA/B/C/E).

Network Management Card 2 Firmware v6.X.X FAQ/Upgrade Issues


Issue

This knowledge base is intended to summarize and provide information on any FAQ or Upgrade Issues that have been identified with Network Management Card 2 (NMC2) v6.X.X firmware.


Please note: This article also includes information about an important Information Bulletin. (INFORMATION BULLETIN - Network Management Card 2 upgrade from v5.1.X to v6.0.6 incorrectly maps SMTP server informationknowledge base FA175981.)



Product Line
 
 
  • Network Management Card 2 - AP9630/30CH, AP9631/31CH, AP9635/35CH
  
Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP84XX, AP86XX, AP88XX, AP89XX), Certain Audio/Video Network Management Enabled products.

 
 
Environment
 
  • All serial numbers
  • All users upgrading from v5.X.X firmware to v6.X.X
  • Users new to v6.X.X firmware
 
Cause

This information is provided a supplement to assist users in understanding any FAQ or other recommended references available for NMC2 v6.X.X firmware.



Resolution


Refer to the information and links below for further information.
 
 
 
 
 
  • Knowledge base FA167693 - Things To Consider When Upgrading or Downgrading a Network Management Card 2 (NMC2) Device between v5.X.X and v6.X.X

  •  Knowledge base FA175981 - INFORMATION BULLETIN: Network Management Card 2 upgrade from v5.1.X to v6.0.6 incorrectly maps SMTP server information  

  • Knowledge base FA175980 - v6.X.X Network Management Card 2 "Reset All" or "Reset to Defaults" Command Does Not Work  

  • Knowledge base FA176048 -  Network Management Card 2 config.ini upload for event notification settings does not enable events in v6.X.X

  • Knowledge base FA175982 - v6.X.X Network Management Card 2 config.ini DefaultUserTemeratureScale (misspelled) keyword value displays the opposite of the actual setting

  • Knowledge base FA170552 - Network Management Card 2 (NMC2) v6.X.X User Types and Permissions Definitions
  • Knowledge base FA176542Mass Configuration of Users and User Preferences on Network Management Card 2 (NMC2) v6.X.X
  • Knowledge base FA177701 - Network Management Card 2 (NMC2) v6.X.X potential reboot loop or TCP/IP stack failure experienced when SMTP server MX record is not cached on user's DNS server
  • Knowledge base FA177263 - Symmetra LX Battery Module Information Missing within v6.X.X Network Management Card Firmware Web Interface
  • Knowledge base FA231396 - UPS Network Management Card 2 Firmware Application Compatibility for Smart-UPS Online (SRT) Models
  • Knowledge base FA233873 - About->Support menu option missing from AP8XXX series Rack PDU Web Interface on certain firmware versions
  • Knowledge base FA234740 - "Battery Predicted Replacement Date" missing from AP9630/31 UPS Network Management Card 2 (NMC2) Web Interface on supported UPS models
  • Knowledge base FA235265 - HTTP/HTTPS Web Access does not work in v6.X.X firmware but works on v5.X.X in certain NMC2 configurations/environments   

  • Knowledge base FA235654Network Management Card 2 (NMC2) does not parse .csf files uploaded via Secure Copy (SCP)  

  • Knowledge base FA235716UPS Network Management Card 2 (NMC2) Certain Events do not work properly with the Dry Contact I/O Accessory (AP9810) Control Policy

  • Knowledge base FA238090Using UPS Network Management Card 2 (NMC2) v6.2.0 sumx application to upgrade SMT UPS firmware via Internet Explorer may fail

  • Knowledge base FA241052 - After upgrading firmware on my APC AP8XXX series Rack PDU, the input voltage reads 1V

  • Knowledge base FA242818Chinese language does not work properly with sumx & sy UPS Network Management Card 2 (NMC2) applications v6.2.1

  • Knowledge base FA238115Unable to access my APC Network Management Card (NMC) enabled device via HTTPS (SSL/TLS)

  • Knowledge base FA243736"Ignore PCNS shutdown commands" missing from UPS Network Management Card 2 (NMC2) PowerChute Shutdown Parameters options


 
Knowledge Base Article ID Resolved Network Management Card AOS or APP Module Version Required
FA175981, FA176048 AOS v6.1.1 or higher
FA175980 AOS v6.1.3 or higher
FA175982 AOS v6.1.6 or higher
FA170552 (and related to note in FA176542) AOS v6.1.3 or higher
FA177701 AOS v6.1.3 or higher
FA177263 sy APP v6.2.0 or higher
FA231396 sumx APP v6.2.0 or higher
FA233873 rpdu2g APP v6.3.3 or higher
FA234740 sumx v6.3.3 or higher
FA235265 AOS v6.3.3 or higher
FA235654 AOS v6.3.3 or higher
FA235716 undetermined future version of sumx firmware APP
FA238090 under investigation for future version of sumx firmware APP
FA241052 v6.3.2 rpdu2g firmware APP
FA242818 language pack fix attached in knowledge base ID
FA238115 detailed fix information available in knowledge base ID
FA243736 undetermined version of sumx/sy APP, workaround available in knowledge base ID



Note: Each Network Management Card has an AOS and application file (APP) and they cannot be updated independently. Please check https://www.apc.com/tools/download/index.cfm to verify the latest versions available for your device. Please also consider any suggested workarounds if a firmware upgrade is not yet available.


 

How to Use Local Time in SCADAPack E RTU Logic Applications

Overview

The SCADAPack E RTU can operate using UTC or Standard Time in the RTU Real Time Clock. When using the DNP3 protocol, UTC time is the recommended industry practice. When using UTC time, some logic applications may require local time and/or daylight savings time. The SCADAPack E RTU has the ability to display local time and control if daylight savings time needs to be applied

SCADAPack E Configuration

UTC & Standard Time

When UTC Time is set in the SCADAPack E RTU real time clock, the Time Offset from UTC system point (float system point 63201) should be set appropriately (as per the installation of the RTU). Where Standard Time is set in the RTU real time clock, the Time Offset from UTC should be set to zero.

The Time Offsett from UTC system point 63201 can be found on the General -> Controller Settings property page of SCADAPack E Configurator.

Summer Time

If summer time activities are required, it is not necessary to adjust the RTU Real Time Clock. Rather, the Time Zone Modifier system point (binary system point 50302) can be activated. This system point is also known as Apply Daylight Savings point. Setting this point is the responsibility of the SCADA Master or a combination of information from the SCADA Master and a user-created logic program.

The Time Zone Modifier selects summer time on the RTU when the binary system point is active. The RTU immediately adjusts for summer time upon receiving a control message from the SCADA Master to set the point.

When Summer Time is selected, certain RTU facilities receive local information from the RTU based on Standard Time + 1.0 Hours. When summer time is not selected, these facilities receive standard time.

Example


In the example below the RTU is located in Ottawa, Canada. The date is September 30th, 2015 UTC time is 8:14pm. Daylight Savings time is enforced, thus binary point 50302 is enabled from the SCADA Host. The Configuration is set to have a UTC time offset of -5. The TIMEDATE block in SCADAPack Workbench CAM5 will return the local time values. DNP3 events are still generated using UTC time, the SCADA host is configured for UTC time, yet logic can execute using local time. The adjustment of daylight savings time is facilitated using binary output point 50302 twice a year.


Time Presentation


Except where noted below, RTU facilities use UTC or Standard time (e.g. RTU Real Time Clock, Trends, and DNP3 Time-stamps).

Summer Time (Daylight Savings) corrected time only affects RTU sub-systems that use Local Time. The following table indicates which SCADAPack E RTU facilities use Local times (UTC offset and Daylight Savings / Summer time adjusted) or UTC / Standard (Summer time independent) times.

RTU Facilities Using UTC or STANDARD Time
(Independent of Summer Time
RTU Facilities Using LOCAL Time
(Adjusted for UTC offset and Daylight Savings Time)
RTU Real Time Clock Profiler Task
Trend sample time-stamps ISaGRAF TIMEDATE Function Block
DNP3, IEC60870-5 protocol event time-stamps ISaGRAF LOC_TIME Function Block
ISaGRAF OS_TIME Function ISaGRAF DAY_TIME Function
Times shown in RTU diagnostics  

More Examples

Example 1 – SCADAPack E RTU clock set to UTC time, Daylight Savings not applied
UTC Time = 11:15:10.5
Time Offset to UTC = 10.0 hours
Apply Daylight Savings = NO
· Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
· ISaGRAF OS_TIME returns seconds since Jan 1, 1970 UTC
· Profiler control time = 21:15:10.5
· ISaGRAF LOC_TIME & TIMEDATE function block indicates 21:15:10
· ISaGRAF DAY_TIME function indicates 21:15:10
Example 2 – SCADAPack E RTU clock set to UTC time, Daylight Savings applied
UTC Time = 11:15:10.5
Time Offset to UTC = 10.0 hours
Apply Daylight Savings = YES
· Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
· ISaGRAF OS_TIME function returns seconds since Jan 1, 1970 UTC
· Profiler control time = 22:15:10.5
· ISaGRAF LOC_TIME & TIMEDATE function block indicates 22:15:10
· ISaGRAF DAY_TIME function indicates 22:15:10
Example 3 – SCADAPack E RTU clock set to Standard time, Daylight Savings not applied
RTU Time = 11:15:10.5
Time Offset to UTC = 0.0 hours
Apply Daylight Savings = NO
· Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
· ISaGRAF OS_TIME returns seconds to 11:15:10 since Jan 1, 1970 standard time
· Profiler control time = 11:15:10.5
· ISaGRAF LOC_TIME & TIMEDATE function block indicates 11:15:10
· ISaGRAF DAY_TIME function indicates 11:15:10
Example 4 – SCADAPack E RTU clock set to Standard time, Daylight Savings applied
RTU Time = 11:15:10.5
Time Offset to UTC = 0.0 hours
Apply Daylight Savings = YES
· Trend samples, DNP3 events, RTU diagnostics indicate 11:15:10.5
· ISaGRAF OS_TIME returns seconds to 11:15:10 since Jan 1, 1970 standard time
· Profiler control time = 12:15:10.5
· ISaGRAF LOC_TIME & TIMEDATE function block indicates 12:15:10
· ISaGRAF DAY_TIME function indicates 12:15:10

More Details

To read more about UTC Time vs. Standard time in SCADAPack E, please consult the Reference Manual which may be selected from the Help menu of the E Configurator.