5084F-PW fascia image
4 BUTTON GLASS FASCIA. PW
5084F-PW fascia image
4 BUTTON GLASS FASCIA. PW

4 GANG GLASS FACIA CREAM

Catalogue Number: 5084F
5084F-PW fascia image
4 BUTTON GLASS FASCIA. PW
5084F-PW fascia image
4 BUTTON GLASS FASCIA. PW
Colour: Pure White
Colour: Per UOM Std.
  • Pure White 1 PCE 1

Specifications

hide show
Range of product
  • Australian Series
  • C-Bus
  • Saturn Series
    • Range
      C-Bus
      Product brand
      Clipsal
      Number of gangs
      4 gangs
      Product destination
      switch
      Material
      glass
      Control type
      button
      Marking
      without marking
      Mounting position
      vertical
      Fixing center
      84 mm
      Length
      116 mm
      Width
      76 mm
      Depth
      12 mm
      REACh Regulation
      Reference contains Substances of Very High Concern above the threshold
      REACh free of SVHC
      Yes
      EU RoHS Directive
      Compliant
      Mercury free
      Yes
      RoHS exemption information
      Yes
      China RoHS Regulation
      Product out of China RoHS scope. Substance declaration for your information
      Circularity Profile
      ENVEOLI121001EN

      Documents & downloads

      hide show
      Filter items
      • All

      • CAD Files and Packs

      • Product Brochures

      • Installation Instruction

      • Product Environmental

      • End of Life Manual

      • Operating Manuals

      • System User Guide

      • Specifications

      • Software - Released

      Frequently Asked Questions

      hide show

      What is the part number for the Fascia only on a Cbus Saturn 4 gang plate ?

      The part number will be 5084F- and then colour reference eg 5084F-PW for Pure White Fascia

      What is the facia in black to suit 5084NL

       Part code is 5084F-60

      What is the part number for black cover to suit 5084NL?

      The part number for black  cover only to suit 5084NL is 5084F-60.

       

      SSH server running after restored configuration of InfraStruXure Central

      Issue:

      SSH server running after restored configuration of InfraStruXure Central

      Product Line:

      InfraStruxure Central

      Environment:

      InfraStruxure Central
      StruxureWare Central
      StruxureWare Data Center Expert.

      Cause:

      If SSH is turned on, it will be turned off after the configuration is restored as this is the default setting.

      Resolution:

      This issue was found in ISXC 5.1.1 and the only current resolution is to manually reconfigure SSH settings.

      The Replace Battery Date on my new SMT series Smart-UPS is incorrect.

      Issue:

      The Replace Battery Date indicated on the LCD screen of my new SMT series Smart-UPS is incorrect.


      Product Line:

      Smart-UPS

      Environment:

      Models beginning with SMT , All Serial Numbers

      Cause:

      The "Replace Battery by" field indicates an estimated date when the UPS Battery may need to be replaced. This field is dynamic  and changes depending on the operating environment of the UPS. It is not a definitive indicator of a bad battery, but it does give the customer some guidance of when to expect a need for replacement.

      This field defaults to 4.5 years from the time of the last battery replacement. Occasionally you may find that on a new SMT series UPS the "Replace Battery By" date indicated on the LCD is far into the future, and therefore incorrect. 


      Resolution:

      To correct this issue select “Reset to Factory Defaults” from the “Configuration” menu of the LCD screen on the front of the UPS
      You will need to wait approximately 30 seconds until this process complete. The LCD  will indicate "Resetting to Fact Defaults" during this process.
      Upon completion, the UPS will start the new unit install wizard on the LCD screen and prompt you to set "Language", "Local Power Quality", "Menu Type", and "Audible Alarms".
      Once you have made your selections, manually select “Install New Battery” from the configuration menu on the LCD.
      This UPS will now properly calculate the Replace Battery Date (which will initially be  4.5 years in the future).
       

      Power Monitoring Expert 9.0 - upgrade fails at 'Verify Database' on ION_Network database - 'duplicate key was found for the object name 'dbo.Translator'

      Issue
      When upgrading to PME 9.0 from an earlier PME version, the 'Verify Database' step fails on the ION_Network database upgrade due to duplicate entries in the Translator table. You will see an error in the log file something like this:

      Error SQL72014: .Net SqlClient Data Provider: Msg 1505, Level 16, State 1, Line 1 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.Translator' and the index name 'AK_Translator_Name'. The duplicate key value is (BCPM).
      Error SQL72045: Script execution error.  The executed script:
      ALTER TABLE [dbo].[Translator]
          ADD CONSTRAINT [AK_Translator_Name] UNIQUE NONCLUSTERED ([Name] ASC);


      Error SQL72014: .Net SqlClient Data Provider: Msg 1750, Level 16, State 1, Line 1 Could not create constraint or index. See previous errors.
      Error SQL72045: Script execution error.  The executed script:
      ALTER TABLE [dbo].[Translator]
          ADD CONSTRAINT [AK_Translator_Name] UNIQUE NONCLUSTERED ([Name] ASC);


      Product Line
      Power Monitoring Expert 9.0

      Environment
      Upgrading to Power Monitoring Expert 9.0 from PME 8.2 or earlier, whether an in-place upgrade, a CM tool Side by Side upgrade or a manual Side by Side upgrade

      Cause
      As of PME 9.0, a uniqueness constraint was imposed on the Name column in the Translator table in ION_Network. In some older ION_Network databases, it is possible to have duplicate entries in the Name column, usually for the BCPM, CM4000, MICROLOGIC or PM800 device types. During the upgrade to PME 9.0, imposing the uniqueness constraint fails due to the duplicate Name entries.

      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.*​

      Method 1: Requires you to analyze the ION_Network database prior to the upgrade
      Prior to the upgrade, check the Translator table in the ION_Network database for duplicates by running the following query:

      USE ION_Network
      SELECT * FROM Translator
      ORDER BY Name


      If duplicates exist, run the attached .sql called 'clean_up_Translator_table.sql'.
      If this is done prior to upgrading to PME 9.0, you will not encounter this problem.

      Method 2: Assumes you have run the PME 9.0 Installer to upgrade from older PME versions and the Installer stops on 'Verify Database'.
      To correct this problem it is necessary to correct the Translator table. To do this, open SQL Server Management Studio (SSMS) and run the attached .sql called 'clean_up_Translator_table.sql'.
      It is also necessary to drop the WindowsTimeZoneId column in the SRC_Timezone table in the ION_Network database. This can be done within SSMS:
       
      1. Start SSMS
      2. Expand 'Databases', then the ION_Network database
      3. Expand 'Tables' and find the SRC_Timezone table
      4. Expand 'Columns', right click on the WindowsTimeZoneId column and choose 'Delete' from the popup menu

      Once this is done, if the Installer has been left running, click on 'Retry All Steps' to retry the upgrade and it will succeed.

      Important: If you do not delete the WindowsTimeZoneId column as described above, prior to retrying the upgrade, and only clean up the Translator table, you will see this error:

      Warning SQL72013: The following SqlCmd variables are not defined in the target scripts: ReferenceDataFilesPath.
      Error SQL72014: .Net SqlClient Data Provider: Msg 5074, Level 16, State 1, Line 39 The column 'WindowsTimeZoneId' is dependent on column 'RegistryKey'.
      Error SQL72045: Script execution error.
      ...
      Error SQL72014: .Net SqlClient Data Provider: Msg 4922, Level 16, State 9, Line 39 ALTER TABLE ALTER COLUMN RegistryKey failed because one or more objects access this column.
      Error SQL72045: Script execution error.  The executed script:
      DECLARE @CurrentSchemaVersion AS INT;


      To recover, simply use SSMS to delete the column, and then 'Retry All Steps' again.





       
      Show More