controller dim pot mech

CONTROLLER DIM POT MECH

Catalogue Number: 30POTDM
controller dim pot mech
Colour: White Electric
Colour: Per UOM Std.
  • White Electric 1 PCE 1

Specifications

hide show
Range of product
Series 30
Product brand
Clipsal
Device presentation
basic element
Control type
rotary knob
REACh Regulation
Free of Substances of Very High Concern above the threshold
EU RoHS Directive
Compliant
Mercury free
Yes
RoHS exemption information
Yes
Environmental Disclosure
ENVPEP111278EN_V0

Documents & downloads

hide show
Filter items
  • All

  • CAD Files and Packs

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

What is the Ohm value of the 30POTDM?

The resistance of the 30POTDM is 500k Ohms. It also has a trim pot to adjust the minimum brightness level.

Some of the key features are:
  • For use with 32/1000 and 32/2400 high power remote dimmers only
For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=30POTDM

Can I stop triggering my SAE_UE_MS_CDBWE sensor when I walk past my room in the hallway?

Yes. the sensor head can be pulled down 30º and rotate in range of 350 º to orient at desired angle for better detection, or avoid from unwanted direction

How does the sensitivity adjustment work on the SAE_UE_MS_CDBWE 360° PIR sensor ?

Sensitivity can be adjust for different requirement by adjust the knob setting or use remote control to set Lux value (10Lux to 1000Lux), time 1 (5sec to 20min), time 2 (10sec to 60min),
the sensor head can be pulled down 30º and rotated in range of 350 º to orient at desired angle for better detection

How to Check Index Fragmentation on Indexes in a Database

Issue
SQL Queries taking longer than normal to complete.

Product
Struxureware Power Monitoring
Power Monitoring Expert
ION Enterprise
ION EEM

Environment
SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

Cause
When a database is frequently updated via INSERT, UPDATE, or DELETE statements we can expect it to become fragmented over the time.
If database indexes are fragmented, the SQL Server query optimizer may chose a non-optimal execution plan when using an index to resolve a query.
This will affect the overall query performance and you may notice a query behaving slower than normal.

Resolution
*Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

The following is a simple query that will list every index on every table in your database, ordered by percentage of index fragmentation.
 
SELECT dbschemas.[name] as 'Schema',
dbtables.[name] as 'Table',
dbindexes.[name] as 'Index',
indexstats.avg_fragmentation_in_percent,
indexstats.page_count
FROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL, NULL, NULL) AS indexstats
INNER JOIN sys.tables dbtables on dbtables.[object_id] = indexstats.[object_id]
INNER JOIN sys.schemas dbschemas on dbtables.[schema_id] = dbschemas.[schema_id]
INNER JOIN sys.indexes AS dbindexes ON dbindexes.[object_id] = indexstats.[object_id]
AND indexstats.index_id = dbindexes.index_id
WHERE indexstats.database_id = DB_ID()
ORDER BY indexstats.avg_fragmentation_in_percent desc

This query can be modified to focus on specific tables by append the table name to the 'where' clause:

WHERE indexstats.database_id = DB_ID() AND dbtables.[name] like '%%'

In order to reduce fragmentation we will have to reorganize or rebuild the indexes. Choosing between reorganizing or rebuilding depends on the query results.
For heavily fragmented indexes a rebuild process is needed, otherwise index reorganization should be sufficient.

The following table summarizes when to use each one:
Reference Values (in %) Action  SQL statement
avg_fragmentation_in_percent > 5 AND < 30  Reorganize Index  ALTER INDEX REORGANIZE
avg_fragmentation_in_percent > 30  Rebuild Index  ALTER INDEX REBUILD

What are the supported controllers based on the Unity Pro v11 license size?

Unity Pro v11 is available in 3 different sizes :  S, L, XL
The only difference between sizes S, L, XL  is the supported controller  references.
Supported PLCs by size :
In bold, new controllers available in Unity Pro v11
 
Controllers family Small
(S)
Large
(L)
X Large
(XL)
MC80 (*) All models All models All models
Momentum All models All models All models
Modicon M 340 All models All models All models
Atrium   TSX PCI 57 204 TSX PCI 57 204
  TSX PCI 57 354 TSX PCI 57 354
Premium   TSX P 57 00 TSX P 57 00
  TSX P 57 10 TSX P 57 10
  TSX P 57 20 TSX P 57 20
  TSX H 57 20 TSX H 57 20
  TSX P 57 30 TSX P 57 30
  TSX P 57 40 TSX P 57 40
  TSX H 57 40 TSX H 57 40
    TSX P 57 50
    TSX P 57 60
M580 Standalone   BMEP 58 10••
BMEP 58 20••
BMEP 58 30••
 
BMEP 58 10••
BMEP 58 20••
BMEP 58 30••
BMEP 58 40••
BMEP 58 5040
BMEP 58 6040
M580 Hot-Standby   BMEH 58 2040
 
BMEH 58 2040
BMEH 58 4040
BMEH 58 6040
Quantum   CPU 311 10 CPU 311 10
  CPU 434 12 U CPU 434 12 U
  CPU 534 14 U CPU 534 14 U
    CPU 651 50
    CPU 651 60
    CPU 652 60
    CPU 670 60
        CPU 671 60
        CPU 672 60
        CPU 672 61
CPU 658 60
CPU 678 61
 
Note : Unity Pro 7.0 is also available in model XLS (XL Safety).
No update of XLS version is available with Unity Pro V11, nor V8.1
 
(*) MC80 controller family is delivered in project mode only.
It requires Update UnityPro_V11_HF_MC80 to be installed in addition to Unity Pro V11