cover pvc 3/4gang arch surr

Flush SurRound, 3/4 Gang, Curve Sided, Architrave

Catalogue Number: 2003/4
cover pvc 3/4gang arch surr
Colour: White Electric
Colour: Per UOM Std.
  • White Electric 1 PCE
Added to cart

Specifications

hide show
Range of product
Series 2000
Product brand
Clipsal
Number of gangs
  • 3 gangs
  • 4 gangs
    • Product destination
      switch
      Material
      plastic
      Marking
      without marking
      Mounting position
      vertical
      Length
      141 mm
      Width
      35 mm
      Depth
      11 mm
      Sustainable offer status
      Green Premium product
      REACh Regulation
      Reference contains Substances of Very High Concern above the threshold
      EU RoHS Directive
      Pro-active compliance (Product out of EU RoHS legal scope)
      Mercury free
      Yes
      RoHS exemption information
      Yes
      China RoHS Regulation
      Product out of China RoHS scope. Substance declaration for your information
      Environmental Disclosure
      ENVPEP120506EN
      Circularity Profile
      N/A

      Documents & downloads

      hide show
      Filter items
      • All

      • Product Brochures

      • CAD Files and Packs

      • Technical Data Catalogues

      • Product Environmental

      • Installation Instruction

      • Operating Manuals

      • Specifications

      • Certificates (MSDS)

      Frequently Asked Questions

      hide show

      Is there any bracket available for a 2000/4?

      There is no stud bracket, you could use the 2154/4 mounting clip.

      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=2154/4

      Are there any plaster clips or other accessories for 2000/3 ?

      We only make wall boxes for this 2000/3
      The Part number is 2157/3  or 2157/3SB1 or 2157/3SB2

      What is part number for 4 gang 2000 series surround?

      The part number for 4 gang 2000 series surround 2000/4.

      Is Silver color on part 2000/2 same as Brushed Aluminium?

      The Silver color is shinier than Brushed Aluminium and is distinctly different

      for information on this part please refer to https://www.clipsal.com/Trade/Products/ProductDetail?catno=2000/2

      User-added image

      Can you get a plate larger than 6 gang in the 2000 series?

      Not directly, but using the 2000/2 or 2000h2 series you can fit 2 plates under one surround.

      What is the plaster bracket to suit the 2000/2?

      The part number for the plaster bracket to suit the 2000/2 is 2155PRM/2.

      What material is used in QO breaker contacts?

      Issue:
      What is the QO breaker contacts made out of? 

      Product Line:
      Circuit Breakers

      Environment: 
      QO Circuit Breakers

      Resolution:
      The contacts are made of a silver & tungsten alloy.

      What is the part number for the Heatsink thermal switch for ATS46 softstarter?

      Issue: Heatsink thermal switch part number
      Environment: Replacement parts
      Cause: Thermal switch  failure.
      Resolution: See attached document for HS Thermal switch part numbers. Note: All are obsolete with no replacement. Replace starter with new ATS48.

      Can you get a 2000/2 in chrome.

      This part  only comes in standard 'bakelite' colours. Please visit the below link to our website for more information and colour options.
      Today, the 2000 series is clipsal’s most popular product range and its surrounds are available in a wide choice from single gang standard size versions to multigang surrounds for situations where you want to house up to four gridplates in a single surround. 2000 series flush surrounds feature a design that neatly conceals all mounting holes, a durable high gloss finish for easy cleaning and a clever clip on/clip off design that enables surrounds to be easily removed when redecorating to conceal overpainting or untidy cut marks when wallpapering.
      Please see following link for more details and colour choices of multi gang range.
      https://www.clipsal.com/Trade/Products/ProductDetail?catno=2000/2

      What is the part number of Mounting bracket for a 2000/2?

      The part number for a for a mounting bracket for a 2000/2 is 2154/2.

      Some of the key features are:
      • Mounting brackets
      • 2 gang
      • For plaster board or hardboard mounting for wall boards up to 12 mm thick

      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=2154/2
       

      What is the mounting hole size required for a 9001O pilot light?

      Issue:
      Need to know the mounting diameter of the 9001O pilot lights.

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      0.68`` ; 17.5mm

       

      My meter is measuring 0A and 0kW but correctly reads the Voltage, what is the issue?

      Product Line
      ION Meters

      Environment
      Installation/Setup

      Resolution
      If the meter is being provided a very small current (0.005A/5mA or less) on the secondary side, the meter will read 0 for the phase current.
      Since kW is dependent on the current reading this value will also be zero.

      To find out what the minimum Primary starting current is you can calculate as follows:
      Primary_Min_Current = 0.005 * CT_Ratio
      Where CT_Ratio = CT_Primary/CT_Secondary

      Example:
      CT Ratio = 2000:5 (Primary:Secondary)
      Starting Current = 0.005A (Secondary)

      CT_Ratio = 2000/5 = 400
      Primary_Min_Current > 0.005 * 400 = 2A (primary side load).

       

      Is ProWORX 32 supported on Windows Server 2003, 2008 or 2012 operating systems?

      ProWORX 32 is not qualified to run on Microsoft Windows Server 2003, 2008 or 2012 operating systems.
       


      Legacy KB System (APS) Data: RESL177093 V1.0, Originally authored by on , Last Edited by on
      Related ranges: ProWORX

      FCL Current Transformers

      Issue
      Customer needs split-core CT with an amperage rating greater than 2400 A

      Product Line
      Model FCL Current Transformers

      Environment
      Current Transformers

      Resolution
      Model FCL Current Transformers have current ratios from 200/5 to 6000/5 A. They are a split-core type current transformer.

      Please find cutsheet for Model FCL Current Transformers attached. 

       For quotes for FCL CTs please contact sales.

      How to change the display settings of energy units from MWh to kWh in ME Meter.

      Depending on the ME meter version, meter will automatically select the appropriate units and therefore it is not possible to modify the energy units. From 40/5 to 150/5 CT ratio, the energy unit display is KWh and from 200/5 to 6000/5 CT ratio, the energy unit display is MWh.

      CT Setting:
      To change the CT settings hold down the button on the Front Face of the ME Meter for more than 5 sec when on the CT Rating display. After approximately 5 sec the display will start blinking, now enter the CT setting. Once again hold the button till the display stop flashing, to ensure that the entry is saved.

      With Power Suite V1.5, I understand that the PS for Pocket PC can be installed for iPAQ 3800/3900. What about the newer series of iPAQs (eg 2200 and 5...

      Goals and Symptoms

      With Power Suite V1.5, I understand that the PS for Pocket PC can be installed for iPAQ 3800/3900. What about the newer series of iPAQs (eg 2200 and 5500)? Does the PS support this product series? Does it also work with Pocket PC 2003? Thank you.

      Causes and Fixes

      Powersuite v1.5 doesn't work under PC2003, for that you need to wait the V2 of Powersuite ( forecast end 2003 ) with Ipaq22xx in qualification.


      Legacy KB System (APS) Data: RESL157567 V1.0, Originally authored by on , Last Edited by on
      Related ranges: Other VVD PRODUCTS

      After a graceful shutdown by PowerChute, Windows 2003, 2008, or 2012 system fails to turn on when utility power is restored.

      Issue:
      After a graceful shutdown by PowerChute,  Windows 2003, 2008, or 2012 system fails to turn on when utility power is restored.

      Product:
      PowerChute Network Shutdown
      PowerChute Business Edition

      Environment:
      Windows 2003, 2008, 2012

      Cause:
      After a graceful shutdown by PowerChute Network Shutdown or PowerChute Business Edition, the server fails to turn on when utility power is restored. Due to changes in the power management feature in Microsoft® Windows Server 2003, 2008, 2012, some servers with an ACPI (Advanced Configuration and Power Interface) BIOS will not turn on when utility power is restored after an outage. The following is an example of what may occur:

      1. A server is attached to an APC UPS and running PowerChute Network Shutdown or PowerChute Business Edition. PowerChute Network Shutdown or PowerChute Business Edition is configured to shut down the operating system when the UPS has been on battery for a specific time.

      2. When the utility power fails, causing the on-battery event, PowerChute Network Shutdown or PowerChute Business Edition commands the operating system to shut down gracefully.

      3. Because ACPI power management is controlled by the operating system rather than by the BIOS, when the operating system completes its graceful shutdown, it commands the server to turn off.

      4. The UPS remains on battery until its shutdown delay time has expired. When utility power is restored, the UPS provides power; the server does not turn on.

      Solution:

      Upgrade the OS to include the latest Microsoft service pack.
       

      Power Monitoring Expert 7.2 - After upgrade to PME 7.2 I can't run or edit my saved RepGen reports

      Issue
      When editing or saving a report in Repgen you will see a “Connection failed” screen like the following:
       


      Manually entering the "Report" login with password "rep0rter!" allows you to edit the report.  However, the next time you edit the same report, Reporter will prompt you for the same connection information.
       
      Also, you will see an “*ERROR* Error 3704” message in Reporter when you try to run a report that had been previously saved.
       
      You will see this issue if you upgraded to PME 7.2 from older versions of the software (e.g. SPM 7.0, SPM 7.0.1) and kept the same SQL Server instance and ION databases in place.

      Product Line
      Power Monitoring Expert 7.2.x

      Environment
      Repgen, Reporter

      Cause
      The password for the “Report” login that is used to connect to SQL Server in order to retrieve data for Reporter reports has changed.  As a result, when upgrading to PME 7.2 from a previous version of the software, you will see errors when trying to edit or generate previously-saved reports

      Resolution
      Change the “Report” login password in SQL Server to “rep0rter!”  This will allow all new reports generated in PME 7.2 to run properly.  You will be able to edit reports without the Connection Info dialog popping up.

      If you are using reports from your previous version of the software in PME 7.2, you will also have to edit them manually to change the stored login information to “Report”/ “rep0rter!”

      • Open the report in Excel.
      • Unhide the |PRIVATE|Datasheets worksheet.
        • Excel 2003:
          • From the menu, choose Format -> Sheet -> Unhide.
        • Excel 2007 / 2010:
          • Right-click on any sheet and choose “Unhide” from the popup menu that appears.
          • Choose the |PRIVATE|Datasheets sheet and click OK.
      • Ensure the USERID and PASSWORD columns contain "Report" and "rep0rter!"
      • After making the changes, hide the sheet |PRIVATE|Datasheets again.
        • Excel 2003:
          • Select the sheet.
          • From the menu, choose Format -> Sheet -> Hide.
        • Excel 2007 / 2010:
          • Right-click on the sheet and choose “Hide” from the popup menu that appears.
      • Save and close the file.


      The report can now be edited and generated without issues.

      How many simultaneous Webreach Connections can access the Server?

      For non-server operating systems (IE: WinXP) 10 Webreach connections can be gathering data.
      For Server Class operating systems (IE: Windows Server 2003) the number of connections is only limited to BandWidth. So effectively unlimited connections can be made.

       

       

      Original article#16715

      Last Revised: May 29 2007

      Public

      All content © 1992-2007 Schneider Electric


      Legacy KB System (APS) Data: RESL186620 V1.0, Originally authored by KBAdPM on 07/06/2007, Last Edited by KBAdPM on 07/06/2007
      Related ranges: ION Enterprise V5.6, ION Enterprise V5.5, ION Enterprise V5.0, ION Enterprise V4.5

      What is the standard of PoE (Power over Ethernet) adopted on EGX devices?

      Product Line
      EGX100
      EGX300

      Resolution
      The Power over Ethernet (PoE), IEEE802.3af, is deployed on the EGX100 and EGX300 devices.

      The IEEE 802.3af PoE standard (ratified June, 2003) provides up to 15.4 W of DC power at 44~57 V DC (though the nominal voltage is 48 V) and 10~350 mA to each device.
      Only 12.95 W is assured to be available at the powered device as some power is dissipated in the cable.

      There is another new version for PoE, IEEE802.3at-2009, sometimes called "POE+", (ratified September 11, 2009), provides up to 25 W of power. Except the Power Output, the voltage and current output are the same as IEE 802.3af. As of 7/1/2015 the EGX only supports IEEE802.3af.

      I can’t find the Project DBF Add-In tool of PowerLogic SCADA in my MS Excel 2003.

      First, you need to check whether the tool has been installed well or not.

           1. Find the tool from Add or Remove Programs of Control Panel as below.

             

               If you cant, you need to install that component from your PowerLogic SCADA CD.

       

           2. If you can find the tool there, you need to go to MS Excel to check other property.

               Go to Help à About Microsoft Office Excel

           

               And then Click Disabled Items below.

            

       If you can find the DBF Add-In item at the Disabled Items window below, you need to enable it.

       

      ---

      Last Revised: 22-July-2009

      Applies To: PowerLogic SCADA 7.1

      Original Author: YJ

      Published By: DRM

      Public

      All content © 1992-2009 Schneider Electric


      Legacy KB System (APS) Data: RESL199485 V2.0, Originally authored by KBAdPM on 07/28/2009, Last Edited by DaMi on 07/31/2009
      Related ranges: PowerLogic SCADA 7.1

      Is ION Enterprise 5.6 supported on Windows Vista?

      For an ION Enterprise 5.6 server installation, the only supported operating systems are Windows XP or 2003, as stated in the Commissioning Guide. Our ION software has not yet been formally tested with Windows Vista, thus full support can not be provided for Windows Vista installations.

      Last Revised: March 4, 2008
      Applies To: ION Enterprise 5.6
      Original Author: KG
      Public
      All content © 1992-2008 Schneider Electric


      Legacy KB System (APS) Data: RESL191337 V1.0, Originally authored by KBAdPM on 03/04/2008, Last Edited by KBAdPM on 03/04/2008
      Related ranges: ION Enterprise V5.6

      OFS / Windows Operating System Compatibility

      OFS V3.50 is compatible with the following Windows platforms (2000, XP, Vista, Server 2003, 7, Server 2008, Server 2008 R2, 8, Server 2012).

      Up to OFS V3.34, OFS is compatible with Windows 32 bits only.
      From OFS V3.35, OFS is compatible with Windows 64 bits including Windows 7.
      From OFS V3.40, OFS is compatible with Windows Server 2008 and Windows Server 2008 R2.
      From OFS V3.50, OFS is compatible with Windows 8 and Windows Server 2012.

       
      See attached an extract of the OFS V3.50 documentation regarding the minimum Drivers version (chapter 'Driver installation' , p.42).

      Note : OFS is supposed to follow the evolution of the Operating System.
      So, except a big technical issue, e.g. OFS V3.60 is planned to be compatible with Windows Server 2012 R2.

      Configuring the Windows SNMP Agent for use with PowerChute Business Edition versions 9.2.1 and below

      Issue:
      How to configure Windows SNMP Agent for use with PowerChute Business Edition

      Product:
      PowerChute Business Edition versions 9.2.1 and below.
      NOTE: PowerChute Business Edition version 9.5 and above include SNMP therefore SNMP Windows service is no longer used. 

      Environment:
      Supported Windows

      Cause:
      Informational

      Solution:
       
      1. In Windows XP and Windows 2003 click Start button, then go to Control Panel and run Add or Remove Programs. In the Add or Remove Programs window, click Add/Remove Windows Components to open Windows Components wizard.

        In Windows  Vista and above, click Start button, then go to Control Panel. Click on Programs And Features link and then click on Turn Windows features on or off. If you're prompted with User Account Control dialog, click "Continue".

      2. In Components of Windows XP and 2003, click on the Management and Monitoring Tools (make sure that you do not select or clear, tick or untick its check box to change the existing selection), and then click Details.

        In Windows Vista and above, locate Simple Network Management Protocol (SNMP).

      3. Select and tick the check box of Simple Network Management Protocol or SNMP feature.
      4. Click OK. Also click Next if you're in Windows XP or 2003. SNMP service will be installed on the system. You may require to insert the Windows setup CD/DVD disc into optical drive.
      5. SNMP will start automatically after installation. But it's recommended to verify the service status from Services in Control Panel, and if it's stopped, you can start the SNMP service from there.

        Two new services will be created:

        1. SNMP Service which is the main engine with agents that monitor the activity in the network devices and report the information to the monitoring console workstation.
        2. SNMP Trap Service which receives trap messages generated by local or remote SNMP agents and forwards the messages to SNMP management programs running on this computer.

      Windows doesn't assign any community string to the SNMP service by default, and also only allow access from localhost or local devices. Further configuration is needed to add in desired community string, which act as the password to grant reply to any SNMP request from remote system.

      Configuring the Windows SNMP Agent for use with PowerChute Business Edition or PowerChute Plus with the PowerNet Agent:

      1. Go to Control Panel->Administration Tools->Services->SNMP service. The following screen will appear. The startup type should be set to automatic.

       



      2. Click on the Agent tab, make sure all service boxes are checked, enter any relevant contact information and location information here:

       



      3. Click on the security tab, enter the appropriate read, and read-write community names to the accepted community names list. In the lower box, click "Accept SNMP packets from these hosts" and click the add button. The IP Address or Host Name of the ISX Central(or other NMS) should be entered. This will enhance security allowing only ISX Central or another NMS to access information via SNMP.

       



      4. Click the Traps tab, and you can create your own trap community name and manually enter the IP Address of ISX Central(or other NMS) as a trap destination.

       



      5.) Click "Apply". Following these configuration changes, it is best practice to verify the functionality of the software SNMP agent using a SNMP utility or network management system. Using an NMS or SNMP utility, query the OID .iso.org.dod.internet.mgmt.mib-2.system.sysDescr (.1.3.6.1.2.1.1.1) to verify the system description (note: this is a standard MIB-2 OID, no other MIB is required). The return string for a Intel/Microsoft SNMP agent should be something similar to: ""Hardware: x86 Family 6 Model 7 Stepping 3 AT/AT COMPATIBLE - Software: Windows 2000 Version 5.0 (Build 2195 Uniprocessor Free)"".

      6.) Install PowerChute Business Edition. If PowerChute Business Edition was installed prior to this configuration, it is necessary to uninstall PowerChute Business Edition, reboot the machine, and then install the software. The SNMP agent MUST be properly installed and configured PRIOR to the installation of PowerChute Business Edition.

      7.) Once PowerChute Business Edition has been install log into the Console - Double Click on the Agent (to view device properties)- Select Show Advanced Items - Communications - SNMP Communications - Enable SNMP Communications:

       

       

       

      When access is enabled, use the Minimum SNMP Trap Severity setting to select what events will cause an SNMP trap to be sent. The default is Informational which will send traps for all levels.

      ReadIDN_S command for IDN 100 using a Quantum/Premium SERCOS Controller and a Lexium Drive

      Goals and Symptoms

      The purpose of this resolution is to inform the user on the behavior of IDN 100 ( Ascii equivalent GV) when using the command ReadIDN_S (opcode 1556) from a Quantum (or) a Premium SERCOS Controller.

      Facts and Changes

      The data length of IDN 100, as described in the IDN user manual (version 2.0, June 2003) is 2 bytes. The PLC register can hence accommodate values from -32767 to + 32767 in signed format. Although the IDN document lists the maximum value for IDN 100 as 200, GV can have values higher and calls for data length greater than 2 bytes in the PLC register, due to its scaling ( GV*100). However the 2 byte limitation is in compliance with the SERCOS standard for this IDN.
      Due to the above reason, values for IDN 100 set higher than 32767 (GV = 327) when read, will be returned as follows:

      (i) 32768 -> -32768
      (ii) 32769-> -32767
      (iii) 35000 -> -30536 in signed format. Unsigned format will result in a huge number.

      Causes and Fixes

      When ReadIDN_S returns a negative value, it may be converted to its positive equivalent by adding 65536.
      For example, -30536 + 65536 = 35000 and so on. There is no implication on using the WriteIDN_S command for the same IDN which is Unsigned decimal format.

      How to Run an Elevated Command Prompt

      Issue:
      While trouble shooting an issue, it may be necessary that commands be run in an MS-DOS command prompt under elevated mode.

      Product:
      Struxureware Power Monitoring
      Power Monitoring Expert
      ION Enterprise
      ION EEM

      Environment:
      Windows 8, Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP

      Cause:
      The privileges of the members of the Administrators group are not equivalent nor sufficient to the Administrator User privileges and 
      therefore even for the members of this group, commands require to be elevated to gain necessary privilege.

      Resolution:
      Elevated mode was a restriction introduced by Windows Vista User Access Control.

      Windows 8
      To run an elevated command prompt in Windows 8:  (if displaying START screen in Windows 8, start at step 2.)

      1. Press keyboard 'Windows key'
      2. Type word 'command'
      3. Then right-click on 'Command Prompt'
      4. From menu click 'Run as administrator' (menu is at bottom of screen in Windows 8)
      5. If you are not an administrator of the computer a dialog box will be shown prompting for the administrator password

      Windows Vista, Windows 7 and Windows Server 2008 and later Servers
      To run an elevated command prompt under Windows Vista, Windows 7 and the Windows Server 2008 and later family of operating systems:

      1. Click Start
      2. In the search box type in command
      3. Right-click 'Command Prompt' in the search results list
      4. Click 'Run as administrator' from the popup menu
      5. If you are not an administrator of the computer a dialog box will be shown prompting for the administrator password

      (Note: the Windows 8 procedure will also with Windows Vista, 7 and Servers 2008 and later if you start at step 1.)

      Windows XP and Windows Server 2003
      There is no concept of elevated command prompts for Windows XP and Windows Server 2003, on these platforms running a command
      prompt with Administrator privileges will achieve the same effect.

       

      The menu 8-Communication doesn' t appear on the display and so it is not possible assign an IP address to the ATV. The display shows a menu 8 called A...

      Goals and Symptoms

      The menu 8-Communication doesn' t appear on the display and so it is not possible assign an IP address to the ATV. The display shows a menu 8 called Application but I don' t know how to use it. Using an ethernet card VW3A58310 v1.1 IE 12 all works fine. Is it possible update the firmware of ethernet card in some way ?

      Facts and Changes

      ATV58 V5.1 IE 32 Display keypad VW3A58101 V4.1 IE 13 VW3A58310 V1.0 IE 11

      Causes and Fixes

      Try to replace the keypad by a new one V5.2 ie32, an incompatibility with your control board is possible.
      A new version of Ethernet card is forecast for September 2003, waiting that it's possible to update the firmware ( v2.1 ) here for firld test.


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

      What is the definition of the shutdown types in PowerChute Business Edition?

      Issue:
      Need to know the different shutdown types in PowerChute Business Edition.

      Product Line:
      PowerChute Business Edition

      Environment:
      All supported Windows OS

      Cause:
      Informational

      Solution:
      Depending on the UPS model and the version of PowerChute the options are

      Shutdown
      Shutdown and off
      Hibernate

       
      Both the Shut Down options shut down your operating system. Shut Down and Off also turns off your computer. If your computer BIOS power management setting is set to [Last State], the computer does not turn on again automatically when the UPS resumes the supply of power. If your computer BIOS power management setting is set to [Always On], the computer does turn on again. For assistance with the system BIOS see Kbase FA159550. 
      If the OS is Windows 2003, 2008, or 2012 see Kbase FA159604 for restart issues. 
       
      NOTE: Hibernation must be enabled before it can be selected and it is not available in PowerChute Business Edition Agent versions 9.1, 9.1.1, 9.2, 9.2.1, 9.5, 10
      Warning: With hibernation as your shutdown type, PowerChute scheduled shutdown operations do not perform normally. You should not schedule shutdowns when hibernation is in use.

       

      ProWORX 32 could return Runtime error - 'skcl.dll not correctly registered' during the installation on Windows XP. Service Pack 2.

      Goals and Symptoms

      ProWORX 32 could return Runtime error - 'skcl.dll not correctly registered' during the installation on a PC that
      has the Windows XP. Service Pack 2.

      Causes and Fixes

      The error is due to the 'Windows XP Service Pack 2' support for DEP (Data Execution Prevention). On the
      latest hardware from both Intel and AMD, they have started putting hardware data execution prevention (Intel's
      Execute Disable(XD) flag and AMD's 'Virus Protection'). This is preventing the .dl from executing.

      To resolve the problem,

      • Download the new version (4.2.1.12) of the 'skcl.dll' file
      • Click on Start\Run and type in the following command to unregister it.

      regsvr32 -u C:\WINNT\system32\SKCL.dll
      • Locate the file in the Windows\System 32 folder and backup the existing file named 'SKCL.dll'
      • Replace the current file with the new file that was downloaded.
      • Click on Start\Run and type in the following command to register it.

      regsvr32 C:\WINNT\system32\SKCL.dll

      If this does not resolve the problem, you can try turning off the 'Data Execution Prevention'
      To turn off the Data Execution Prevention, refer to the article (A detailed description of the Data Execution
      Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows
      Server 2003) on Microsoft's web site at

      https://support.microsoft.com/kb/875352#5

      The following workaround is quoted from the Microsoft article.

      "For the purposes of program compatibility, you can selectively disable DEP for individual 32-bit programs
      when DEP is set to the OptOut policy level. To do this, use the Data Execution Prevention tab in System
      Properties to selectively disable DEP for a program."

      Attachments

      (Removed File URL: 177163_B46E/Microsoft_article__875352.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cf3bad122ebb29d8c12571640047338b/fl_block_5/0.642?OpenElement&FieldElemFormat=gif)(Removed File URL: 177163_B46E/SKCL.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cf3bad122ebb29d8c12571640047338b/fl_block_5/0.20A6?OpenElement&FieldElemFormat=gif)


      Legacy KB System (APS) Data: RESL177163 V2.0, Originally authored by on , Last Edited by on
      Related ranges: ProWORX

      Active Pager Module (APM) and Sequence of Events Recorder (SER) Webpage Does Not Load; Internet Explorer Error “Server Error in ‘/’ Application. The resource cannot be found.”

      Goals and Symptoms

      When the user tries to access the PowerLogic eSolutions Web Site (usually from a remote workstation), the page does not load. Instead, the user sees the following error.
      Server Error in '/' Application.

      The resource cannot be found.

      Requested Url: /PLDefaultWeb/Default.aspx

      Causes and Fixes

      This issue is NOT related to Internet Explorer security settings or the Windows account used to log in to the web page.

      Instead, this issue is caused by an attempt to access the PowerLogic eSolutions page on an invalid TCP port. In Internet Information Services (IIS) Version 6.0 (Windows Server 2003) and later, multiple web sites can be hosted on one server. Because the PowerLogic SMS Web Client uses different IIS settings than the PowerLogic eSolutions software suite (APM, SER), these software packages may be installed on separate web sites. A caveat to hosting multiple web sites on one server is that no two sites can answer on the same IP/port combination. In this case, the SMS Web Client and eSolutions web page exist on different ports.

      To determine the port that the eSolutions web site answers on, open IIS by going to Start > Run, typing inetmgr and clicking OK. Right-click the PLeSolutionsWeb site and open Properties. On the Web Site tab, note the TCP Port that is configured. This port number will be appended to the web address used to open the PowerLogic eSolutions page.



      For example, in the above screen capture, Port 81 has been configured for the PLeSolutionsWeb site. In this case, the address used to access the page should be:
      https://###.###.###.###:81/PLDefaultWeb/Default.aspx (where ###.###.###.### is the IP address of the server)


      Legacy KB System (APS) Data: RESL203617 V1.0, Originally authored by AnVa on 10/01/2010, Last Edited by AnVa on 10/01/2010
      Related ranges: SMS Add-on

      Why can’t I access the PowerChute Business Edition Agent from the Console on Windows Server 2003?

      Issue: Accessing the PowerChute Business Edition Agent web pages from the Console might not work properly due to the network configuration of the Windows Server 2003 machine.

      Product: PowerChute Business Edition

      Environment: Windows 2003 Enterprise Server

      Cause: The network configuration of the Windows Server 2003 machine.

      How to identify if you are encountering this problem

      If you are unable to get a ping response from the fully qualified domain name of the Windows Server 2003 machine. You can check this as follows:

      Open a command prompt and type in

      ping <machine name.domain-name>

      e.g. ping WIN2003ABCDE.acme.com

      If you do not receive a response for the ping then you may be experiencing this problem.

      Solution:

      Modify the DNS dynamic update behaviour of the Windows 2003 Server to register the IP addresses and the connection-specific domain names.

      1.   Click Start - Control Panel - Network and Internet Connections, and Network Connections.

      2.   Right-click the network connection that you want to configure, and then click Properties.

      3.   On the General tab (for a local area connection), or the Networking tab (for all other connections), click Internet Protocol (TCP/IP), and then click Properties.

      4.   In the next window click on Advanced.

      5.   In the next window click on the DNS tab.

      6.   Select the Use this connection's DNS suffix in DNS registration check box.

      7.   Click on OK to close all open windows.

       

      By default, the Use this connection's DNS suffix in DNS registration check box is not selected. The connection-specific domain name of this connection is the DNS suffix for this connection appended to the computer name.

      For more information see https://technet.microsoft.com/en-us/library/cc779282(v=ws.10).aspx

      Why is PowerChute not shutting down my Windows system if I leave it at the system logon screen?

      Issue:
      Why is PowerChute not shutting down my Windows system if I leave it at the system logon screen?

      Product Line:
      PowerChute Business Edition
      PowerChute Network Shutdown

      Environment:
      Windows Server 2003, Windows XP Professional x64 Edition, or Windows 2000 SP3 or late

      Cause:
      If you leave the system at the Windows logon screen (user ID & password entry screen), neither PowerChute Business Edition nor PowerChute Network Shutdown can shutdown Windows during power failure or scheduled shutdown. It is a Windows' specification.

      Under normal circumstance, you get the logon screen after CTRL+ALT+DEL and do not key in any data for about 30 seconds, the system will bring back the CTRL+ALT+DEL screen.

      Solution:

      Do not enable the "Disable CTRL+ALT+DEL requirement for logon" option found in the Security option of Local Security settings tools in Administrative tools. Do not leave your system with the logon screen.
      If you are running Windows XP Professional x64 Edition and it is not joined to a domain, follow the steps below to enable the CTRL+ALT+DEL screen.
      Start gpedit.msc from the command prompt.
      Select Local Computer Policy > Computer Configuration > Administrative Template> Logon
      Enable the "Always use classic logon" option

      Can I set the Magelis date using scripting in Vijeo Designer?

      Yes, you can set the Magelis date using scripting in Vijeo Designer. By using the Sys.setDate command.
      Function

      Changes the date on the target machine.

      You can also change the date from the Configuration menu, but using scripts makes it possible to change the date while still running Vijeo-Designer Runtime.

      Format

        • public static boolean Sys.setDate(int year4, int month, int day);
      Parameters
            • Parameter
            • Description
            • int year4
            • First parameter defines a four-digit year. Acceptable values are 1980 to 2037.
            • int month
            • Second parameter defines the one- or two-digit month. Acceptable values are 1 to 12.
            • int day
            • Third parameter defines the one- or two-digit day. Acceptable values are 1 to 31.

      Use  1 as any of the parameters to ignore that parameter.

      Example:

        • Sys.setDate(2003, 12, -1);

          // set the year to 2003, month to 12, and do not change the day

        • For the month and day parameters, use only single digits for the numbers 1 to 9. Using two digits, such as "08" or "09", may produce unexpected results.
      Return Value
            • Value
            • Description
            • false
            • Failed to set the date on the target machine. Usually indicates invalid parameters, but may also indicate a communication error.
            • true
            • Successfully set the date on the target machine.

      PowerLogic PM800 Recommended Replacement

      Product Line
      PowerLogic PM800 Series Power Meters

      Environment
      End of commercialization and recommended replacement

      Resolution
      The PowerLogic PM800 series was originally launched in 2003. The PM810s and PM820s are replaced by the PM5500 and the PM850s and PM870s are replaced by the PM8000.

      Repair Service will continue through December 30, 2021, or until components are no longer available
      ●The meter will continue to be supported in the power monitoring software offers as a legacy device 
      ●Technical support will continue indefinitely, though by 2021 support will be limited to basic support (User manual information) 

      Suggested Replacement Offers for the PM800 series meters:

      PM810, PM820 = PM5500
       
      Reference Number System Recognized Part Number Part Number Description
      PM5560 METSEPM5560 Basic metering with class 0.2S accuracy + 4DI/2DO + data logging + multi tariff + dual Ethernet and serial comms + 4th CT input for neutral & ground measurement + internal web server.   (Gateway + Cyber Security Added)
      PM5563 METSEPM5563 Basic metering with class 0.2S accuracy + 4DI/2DO + data logging + multi tariff + dual Ethernet and serial comms + 4th CT input for neutral & ground measurement + internal web server - DIN Rail meter with no display.
      PM5563RD METSEPM5563RD Basic metering with class 0.2S accuracy + 4DI/2DO + data logging + multi tariff + dual Ethernet and serial comms + 4th CT input for neutral & ground measurement + internal web server - Remote Display and DIN Rail meter.

      PM850, PM870 = PM8000
       
      Reference Number System Recognized Part Number Part Number Description
      PM8240 METSEPM8240 Intermediate metering with class 0.2S accuracy + 3 digital status/counter inputs + 1 KY(form A) energy pulse output & dual port ethernet + serial communications. PM8000 power meter panel mount with display.
      PM8243 METSEPM8243 Intermediate metering with class 0.2S accuracy + 3 digital status/counter inputs + 1 KY(form A) energy pulse output & dual port ethernet + serial communications. PM8000 power meter din rail no display.
      PM8244 METSEPM8244 Intermediate metering with class 0.2S accuracy + 3 digital status/counter inputs + 1 KY(form A) energy pulse output & dual port ethernet + serial communications. PM8000 power meter din rail with remote display.





      More information on the PM5500 series is available here: 
      FA234023.



      More information on the PM8000 series is available here: 
      FA244498.

      Computer will not automatically reboot after UPS has shutdown and restarted

      Issue:
      Computer will not automatically reboot after UPS has shutdown and restarted

      Product Line:
      PowerChute Personal Edition
      PowerChute Business Edition
      PowerChute Network Shutdown

      Environment:
      All devices that include BIOS
      All APC UPS

      Cause:
      This problem is independent of the type of UPS connected. It is a function of the BIOS implementation supporting the soft-switch on computers. It is not a problem with APC UPS's or with PowerChute.

      Solution:

      To resolve this, change this BIOS setting, if possible, to Always On. If you cannot modify this setting, then the UPS will not be able to automatically reboot the computer under any circumstances - with APC or any other UPS.

      Please contact your computer or BIOS manufacturer to find out if it is possible to change this BIOS setting on your particular computer and for exact instructions on how to do so.

      NOTE: If the system OS is Windows 2003, 2008 or 2012 please review Kbase FA159604

      Background:

      Most new computers available in the market today use the ATX motherboard which supports the use of a soft switch to turn the Computer On and Off. The implementation of this soft switch includes a BIOS parameter which defines the state the computer will enter when the power supply senses input power when plugged into the wall. This BIOS parameter can have any one of three values :

      ALWAYS ON: When power is cycled on, the computer will automatically turn on and boot up.

      ALWAYS OFF: When power is cycled on, the computer will stay off until the user manually hits the On/Off soft switch.

      LAST STATE: When power is cycled on, the computer will either come on or stay off depending on whether it was On or Off when the power was lost.

      Most computer manufacturers set this parameter to Last State and some computer manufacturers set this parameter to Always Off. It is highly unlikely to find the Always On parameter setting. In many cases, the computer manufacturer permits the user to change the value of this parameter by using the system setup menu which can accessed prior to the operating system loading when the computer is turned on.

      If this parameter is set to Always Off then an APC UPS cannot reboot this computer as it will not turn on when the power is cycled independent of the state of the PC prior to power being turned off.



       

      How to end Excel and repgen tasks from the command line

      Issue:
      The system has a large number of process running Excel.exe and possibly repgen.exe


      Product:
      ION Enterprise 6.0.x
      StruxureWare Power Monitoring (SPM) 7.0.x
      Power monitoring Expert (PME) 7.2.x, 8.0

      Environment:
      Windows Server 2003, 2008, 2008 R2, 2012, 2012 R2, Windows 7

      Cause:
      At times when "repgen/Reporter" is launched from a scheduled task, the process does not end properly and the task continues to run.

      Resolution:
      1) Create a text file with the following commands

      taskkill /f /im "reportgen.exe"
      taskkill /f /im "excel.exe"
      pause


      2) Save this file as batch file 'Filename'.bat

      3) Right click on the file and select Run as Administrator

      Note:
      The above commands will stop all instances of excel and repgen without any prompts. More information about taskkill is included below

      TASKKILL [/S system [/U username [/P [password]]]] { [/FI filter] [/PID processid | /IM imagename] } [/T] [/F]

      Description:
          This tool is used to terminate tasks by process id (PID) or image name.

      Parameter List:
          /S    system           Specifies the remote system to connect to.

          /U    [domain\]user    Specifies the user context under which the command should execute.

          /P    [password]       Specifies the password for the given user context. Prompts for input if omitted.

          /FI   filter           Applies a filter to select a set of tasks. Allows "*" to be used. ex. imagename eq acme*

          /PID  processid        Specifies the PID of the process to be terminated. Use TaskList to get the PID.

          /IM   imagename        Specifies the image name of the process to be terminated. Wildcard '*' can be used to specify all tasks or image names.

          /T                     Terminates the specified process and any child processes which were started by it.

          /F                     Specifies to forcefully terminate the process(es).

          /?                     Displays this help message.

      Examples:
          TASKKILL /IM notepad.exe
          TASKKILL /PID 1230 /PID 1241 /PID 1253 /T
          TASKKILL /F /IM cmd.exe /T
          TASKKILL /F /FI "PID ge 1000" /FI "WINDOWTITLE ne untitle*"
          TASKKILL /F /FI "USERNAME eq NT AUTHORITY\SYSTEM" /IM notepad.exe
          TASKKILL /S system /U domain\username /FI "USERNAME ne NT*" /IM *
          TASKKILL /S system /U username /P password /FI "IMAGENAME eq note*"

      Video: How do I use Modbus Scanner tool in Series E Configurator software to poll a Modbus slave device with the SCADAPack RTU?



      Issue: Need to configure Modbus communications between SCADAPack RTU and a Modbus slave device. Then need to poll a Modbus slave device with the SCADAPack RTU
      Product Lines:
      Series E Configurator
      SCADAPack RTU
      Environment:
      Microsoft Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, or Windows 10, on 32-bit or 64-bit Operating System
      Cause: N/A
      Solution:
      1. Open Series E Configurator and create a new 535E project.
      2. Open the ‘Master’ folder and select the Modbus Scanner page than click on the ‘add device’ button.
      3. Give your Modbus slave a name, select the device type you want to use, type in the Modbus unit identifier and the IP address of your device, the listen port is 502.
      4. If you did want to communicate via serial you would select Modbus serial RTU then type in the Modbus device address same as for TCP and select the serial port on the RTU that you want to communicate with. Before doing this though you need to configure the port as the Modbus master port. To do this go to the ‘ports’ page and change the desired port to Modbus master, then change the communication parameters to whatever you need them to be for communication
      5. Add the points you want to read and write from. To do this click on the ‘add points’ button under ‘Modbus points scanner’. I’m going to select the operation as a read/write parameter as the holding registers I’m targeting are read-writable. I’m going to change Modbus data type from UINT to INT and make the Modbus register start address 48502 I’m targeting the command and frequency reference register of a VSD and their registers are 8501 and 8502 but there is an offset of one so the starting address is 48502. I’m going to leave it as an analog output and change the dnp out point to 8501 because it is easy to remember as this is the holding register of the command. I’ll change the point quantity to 2 as I’m targeting two points.
      6. Open the analog points page and see that some of the points have been created automatically.
      7. Write configuration to the RTU
      8. Read of the RTU and see that the dnp points have been automatically created at 8501 and 8501 as specified.
      9. If using TCP, Open the TCP page and give the Ethernet 1 port an IP address that puts your RTU on the same subnet as your Modbus slave device. Also, enable your ‘Modbus client’ checkbox.
      10. Write your communication parameters to your RTU.
      11. Open point browser and create the DNP points that you are targeting. Mine are 8501 and 8502. Perform a read of the holding registers. yours might still be zero so you won’t see a change. Change the values of the holding registers and perform a write to the slave device. Do a read to see if the value values you attempted to write stayed in the holding registers.

      Video: How do I configure IO boards and points on a SCADAPack RTU and then test them with Series E Configurator software?


      Issue: Need to use Series E Configurator software to configure the IO boards to communicate correctly with your SCADAPack RTU processor board. Need to use Series E Configurator software to configure system points, derived points and physical points on the IO boards correctly. Need to use Point Browser tool in Series E Configurator software to test reading from and writing to configured points.
      Product Lines:
      Series E Configurator
      SCADAPack RTU
      Environment:
      Microsoft Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, or Windows 10, on 32-bit or 64-bit Operating System
      Cause: N/A
      Solution:
      1. Factory reset your RTU
      2. Start Series E Configurator,
      3. Use USB communication setting
      4. Read the RTU Configuration
      5. Open IO-> SCADAPack IO on the left-hand side of Series E Configurator window
      6. When you read the configuration of a factory reset rtu, the modules will not be automatically created
      7. Add a 6601 composite IO module if you are using a 535e RTU.
      8. If we’re using remote IO you’re going to need to change the address so that each address is unique so that you can target each IO board correctly.
      9. Now add another module. You’re going to add the 6201 IO board these are the IO on the actual processor of the 535e on the top rack. Now you can see that your physical IO has been created and it correlates to the physical points on the SCADAPack.
      10. Map the physical points to the dnp points for all physical IO. So just type in 1, 2, 3, 4, 5, 6, 7, 8 for DIs 1, 2, 3, 4, 5, 6, 7, 8 etc. so it’s easy to keep track of their point numbers.
      11. Write the configuration to the SCADAPack. Once the configuration is written open the Points pages and you can see that your physical points have been mapped to dnp points here.
      12. Double click a point to observe the properties.
      13. Create a point from the Points page. To do this you can either create a range or a single point. You must select your point type. For this point we're going to select system and point number 50005. This point correlates to the point the which represents the 6601 IO firmware version.
      14. Open your point browser and start creating some points to test: DIs 1 and 2 and the Dos and AIs from the 6601 module; the last DO from the 6201 module; and the system point you created.
      15. Select the read button and all your values will update.
      16. Make a comment. This is just a point description and this will come straight through to the point browser.
      17. Observe that point 50005 matches your IO firmware.
      18. Test your binary values by writing a 1 to some of them and checking if the corresponding led comes on. If it doesn’t, go to controller setting as and check the led power always on the box and write the configuration. Once it's written and you’ve confirmed the binary points were written to the SCADAPack you should see the led come on.

      Video: How do I communicate between Series E Configurator software and my SCADAPack RTU?



      Issue: Need to use Series E Configurator software to configure SCADAPack RTU. But first, need to know how to set up communications between Series E Configurator software and my SCADAPack RTU
      Product Lines:
      Series E Configurator
      SCADAPack RTU
      Environment:
      Microsoft Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, or Windows 10, on 32-bit or 64-bit Operating System
      Cause: N/A
      Solution:
      1. Factory Reset the RTU
      2. Open Series E Configurator and create a new project. I am using a 535e SCADAPack RTU today.
      3. Communicate via USB by going to the communication drop-down menu and select USB.
      4. Read the RTU configuration.
      5. Once the RTU configuration has been read into your RTU click on the general status page. In here you can see many properties of the RTU. If you press refresh it will update your up time and you can also see your input voltage and whether it is normal or out of range.
      6. Set the RTU up for Serial communication
      7. Open the ports folder on the left-hand side.
      8. The DNP address of a factory reset RTU is zero. Change this to a unique number. This needs to be unique because if we have two RTUs at DNP address 12 on the network and you try to communicate with slave device 12, the master will get confused and not know where to send that information.
      9. Set the port 2 functions for serial communication.
      10. Write your new DNP address to your RTU. Once the write is complete go to the communication drop down box and select serial.
      11. Click on your communications setting icon.  Make sure your parameters are the same as your port 2 functions and that your communication with the correct com port.
      12. Try to refresh your page. It will fail because you haven’t updated your target DNP address. So, update this, then go into controller status and refresh your page again and see the traffic light come back to green
      13. Set the RTU up for Ethernet communication
      14. Open TCP/IP page then add your IP address to Ethernet 1. The IP address must be on the same subnet as the rest of your network and the final number must be unique. Enter a subnet mask of 255.255.255.0
      15. Change the IP Address of your computer to be on the same subnet as your RTU
      16. Write the IP address to the RTU.
      17. Now go to the communication drop down box select TCP click on the communication box and enter your IP address and the TCP port number of the RTU is 20000. Refresh your page again and you’ll see the traffic light come back to green if the communication has been set up correctly.

      Video: How do I use Workbench 6 software to program a SCADAPack RTU to poll and control a Modbus slave device?



      Issue: Need to use Workbench 6 software to configure a connection between SCADAPack RTU and a Modbus slave device. Example device used in this video is an Altivar 900. Need to address correct holding registers of the slave device. Need to test reading from and writing to holding registers of a slave device by going Online in Workbench 6 software and using the Point Browser tool in Series E Configurator software.
      Product Lines:
      Series E Configurator
      SCADAPack RTU
       
      Environment:
      Microsoft Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, or Windows 10, on 32-bit or 64-bit Operating System
       
      Cause: N/A
      Solution:
      1. Open Series E Configurator and create or open a project
      2. If using TCP make sure TCP/IP is enabled in the RTU. If using serial set up a port on the SCADAPack to communicate to a PLC Device with
      3. In Configurator: Open Logic-> IEC 61131-3
      4. Set the correct target type
      5. Select “launch workbench”
      6. In Workbench, Right click your 1st resource, open IO devices
      7. Create your I/O device to read RTU value: RTU_{DATA_TYPE}_READ
      8. Choose the amount of inputs you wish to read in the “Number of” parameter. Fill in device parameters according to your slave device and targeted points.
      9. Create a VarInput variable of the appropriate Data Type for each channel and attach it to the corresponding channel by double-clicking the channel, then select the variable. The values of the selected points from the RTU will now be read into your Workbench program when it is online.
      10. Create a VarOutput variable of the appropriate Data Type for each holding register you wish to write to.
      11. Create a program that transfers the values of the input variables to the corresponding output variables.
      12. Create your I/O device to write the readings from the RTU to the Modbus Slave Registers: MBUS_WRITE_{DATA_TYPE} for serial communication, MTCP_WRITE_{DATA_TYPE} for Ethernet communication.
      13. Choose the amount of outputs you wish to read in the “Number of” parameter. Fill in device parameters according to your slave device and targeted holding registers.
      14. Attach the output variables to their corresponding channels. When the program is online the points being read from the RTU will automatically be written to the chosen holding register in the slave device.
      15. Make the RTU I/O Device a ‘WRITE’ device and make the MBUS/MTCP I/O Device a ‘READ’ device.​
      16. Make a simple program to control slave device

      APC by Schneider Electric - APC Surge Product Recall

      Issue:

      This recall involves APC 7 and 8 series SurgeArrest surge protectors manufactured before 2003. The model and serial numbers are located on a label on the bottom of the surge protector. The two numbers that follow the first letter or letters in the serial number sequence indicate the year of manufacture.

      APC and the words Personal, Professional, Performance or Network are printed on the surge protectors. 

      The unit is included in the recall ONLY if the numbers are 93, 94, 95, 96, 97, 98, 99, 00, 01 or 02.


      Product Line:

      APC SurgeArrest; The following model numbers are included in this recall.
       

      7 Series model numbers

      8 Series model numbers

      NET7   

      NET8   

      NET7T

      NET8N

      NET7T-C

      PER8T           

      PER7  

      PER8TR

      PER7C

      PER8TR-CN

      PER7T

      PER8TVR

      PER7T-CO

      PER8XTV

      PER7T-U

      PRF8T2

      PER7TX137

      PRF8TT

      PER7-U

      PRO8 

      PER7X148

      PRO8T2

      PRF7  

      PRO8T2C

      PRF7T

      PRO8T2MP12

      PRO7

      PRO8T2MP12B        

      PRO7C

      PRO8TV

      PRO7T

       

      PRO7TX183

       

       

      Resolution:

      Contact Schneider Electric for Replacement

      Schneider Electric IT Corp., toll-free at (888) 437-4007 from 8 a.m. to 5 p.m. ET Monday through Friday, or online at https://recall.apc.com, or www.apc.com and click on the Recall link to submit a claim and obtain more information.

      Further Details: CPSC

      Video: How do I configure Trio J Series radios to communicate with each other using the Trio Web User Interface?



      Issue: Need to Access the WUI. Need to configure Trio J Series radios to communicate with each other using the WUI. Need to test and diagnose connection using Tview+ Management Suite.
      Product Lines:
      Trio Radio
      Environment:
      Microsoft Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, or Windows 10, on 32-bit or 64-bit Operating System
      Cause: N/A
      Solution:
      1. Factory reset your radio
      2. Change your computer’s IP address to 192.168.2.xxx (not 192.168.2.15 though)
      3. Connect the computer to only the “Remote” radio via Ethernet.
      4. Open your web browser, go to address “https://192.168.2.15/”
      5. Click on “setup” tab in top toolbar then click on Wizards in left-hand toolbar
      6. Configure radio to be point to point remote radio
      7. Record the serial number
      8. Change IP Address to be unique
      9. Change the “Subnet ID” from “default” to your network name and click “active configuration” in top right corner
      10. Wait about 60 seconds then in the web search bar type the new IP Adress of the radio. You may need to change your computer’s IP address to remain on the same subnet as your radio.
      11. Once connected, click “setup” again, then click “network” (under “configuration”) in left-hand toolbar
      12. Observe that there are many more parameters that can be set for diagnostics, security and identification purposes
      13. Go to eDiags and enable them, make the “Controller 1 IP Address” your computer’s IP Address
      14. Scroll to the top of the page and click “active configuration” in top right corner. An error will pop up prompting you to setup up security because security is automatically enabled by default. The remote radio is now configured for communicating and diagnostics
      15. Now connect to your Access point radio via Ethernet. It is ok to be connected to both radios at the same time now because they both have different IP Addresses. If needed, change your computer’s IP address to 192.168.2.xxx (not 192.168.2.15 though)
      16. Open a new tab in your web browser, go to address “https://192.168.2.15/”
      17. Following the previous procedure, configure the radio to be a point to point access point radio
      18. Change IP Address to be unique but place it on the same subnet as your remote radio
      19. Change the “Subnet ID” from “default” to your network name (same as for the remote)
      20. Type your remote radio’s serial number in the trusted serial number box
      21. Scroll to top of page and click “active configuration” in top right corner
      22. Wait about 60 seconds then in the web search bar type your new IP Address. Remember if you change the subnet of your ip address you will need to change your computer’s ip address to remain on the same subnet as your radio.
      23. Once connected, click “setup” again, then click “network” (under “configuration”) in left-hand toolbar
      24. Go to eDiags and enable them, make the “Controller 1 IP Address” your computer’s IP Address
      25. Scroll to top of page and click “active configuration” in top right corner
      26. Both radios should be synchronized now. So, the sync LEDs on each radio should now blink yellow/green instead of red. To prove they are synchronized we can view the connected radios on the network in the diagnostics, browse network section. We can also do a packet transmission test.
      27. Click on diagnostics, packet transmission test. Type in the serial number of the remote radio you are communicating with and click “start test”. Once the test is finished view the results and see the number of packets received should be very close to those sent. 
      28. Now we can do eDiags, open Tview management suite, create a new file
      29. Fill in the known details for your access point radio, i.e. unit name, unit serial number, model, communication port, and remote IP address remote
      30. Click “apply changes to database” then “add new” and do the same for your remote radio
      31. Create your eDiags port, type in  the IP address of your computer
      32. Start group poll

      Why does my local mouse (the mouse on the server I am connecting from) not synchronize with my remote mouse (the mouse on the server I'm connecting to) when connected through the APC IP KVM product?



      Issue

      When using an IP KVM Switch, the local mouse does not sync up with the remote mouse on the target device. The mouse is 'laggy.'


      Product Line

      • Rack Accessories - IP KVM Switches
        • KVM1116P
        • KVM2116P
        • KVM2132P
        • AP5610
        • AP5615
        • AP5616
        • AP5405


      Environment

      • IP KVM Switch
      • Mouse lag/sync problems
      • All firmware versions
      • All serial numbers

      Cause

      When connecting to a server via a Digital IP KVM, you may notice that the local mouse (your desktop) is not synchronizing with the remote mouse (the workstation/server that you are attaching to). There are a couple of steps that you can take to resolve this, depending on the KVM you are using.



      Resolution


      Recommended options and tweaks for KVM1116P, KVM2116P, and KVM2132P
      • Try enabling mouse sync mode which is an icon option available from the Remote Viewer Toolbar.
      • From the same toolbar, it is recommended to try and set the Network Type to 512K ADSL under Video Settings
      • Consider changing the mouse mode between single, dot, dual, crosshair options along with enabling/disabling mouse sync between each of the mouse modes. (This is also accessible from the Remote Viewer Toolbar.)
      • Make sure "Cable Length" is set accurately for your configuration. The available options are short, medium, and long. (This is also accessible from the Remote Viewer Toolbar.)
      Recommended options and tweaks for AP5610, AP5615, AP5616

      • Connect to a server via the Digital IP KVM. Once connected to the target server via the IP KVM's Java viewer, select Tools, then Single Cursor mode to sync your mouse with the target server's.
      Recommended options and tweaks for AP5405

      • If using an AP5405, connect to a server via the IP KVM. Once connected, scroll to the top of the server window. You should see the following menu options: Shortcuts, Options, Connection, Host OS, About.... Choose Options, then Auto Sync Mouse.

      You can also try adjusting mouse settings direct from the attached servers (i.e. mouse acceleration) if the mouse is not working correctly (meaning the servers attached to the KVM, not the server you're connecting from).


      Windows NT Platforms :

      Connect to the server via the IP KVM. Perform the following steps:
      1. Start/Settings/Control Panel to open the Control Panel window.
      2. Double-click the Mouse icon to open the Mouse Properties dialog box.
      3. Click the Motion tab.
      4. Move the pointer speed slider to slow, which is the tick mark furthest to the left).
      5. Make sure the Snap to default checkbox is unchecked.
      6. Click OK to close the Mouse Properties dialog box and to save your settings.

      Windows 2000 Platforms:

      Connect to the server via the IP KVM. Perform the following steps:
      1. Start/Settings/Control Panel to open the Control Panel window.
      2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
      3. Click the Motion tab.
      4. Move the speed slider to the default of 50% (the middle of the slider or the sixth tick from the left).
      5. Set the Acceleration option to None.
      6. Make sure the Snap to default checkbox is unchecked.
      7. Click OK to close the Mouse Properties dialog box and to save your settings.

      Windows XP, 2003, Vista, 7, or 2008:


      Connect to the server via the IP KVM. Perform the following steps:
      1. Start/Control Panel to open the Control Panel window. (Accessing the Control Panel can differ depending on the version of Windows is being used)
      2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
      3. Click the Pointer Options tab.
      4. Set the Select a pointer speed slider to the default of midpoint (the middle of the slider or the sixth tick mark from the left).
      5. Uncheck the Enhance pointer precision checkbox.
      6. Make sure the Snap To and the Visibility checkboxes are unchecked.
      7. Click OK to close the Mouse Properties dialog box and to save your settings.


      Systems with Intellipoint Drivers:


      Connect to the server via the IP KVM. Perform the following steps:
      1. Start/Control Panel to open the Control Panel window.
      2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
      3. Click the Pointer Options tab.
      4. Set the Select a pointer speed slider to the default of midpoint (the sixth tick mark from the left).
      5. Uncheck the Enhance pointer precision checkbox.
      6. Make sure the Snap To and the Visibility checkboxes are unchecked.
      7. Click the Wheel tab.
      8. Uncheck the Enable accelerated scrolling ... checkbox.
      9. Click OK to close the Mouse Properties dialog box and to save your settings.

      Linux (pre 8.0)


      Connect to the server via the IP KVM. Perform the following steps:
      1. From the Workspace Menu, click the Desktop Manager icon and select Application Manager -Desktop_Controls to open the Control Center dialog box.
      2. From the tree view, select Peripherals - Mouse to list the mouse settings.
      3. Set the Acceleration slider to the center position.
      4. Optional) Select the desired Mouse buttons option and set the Threshold slider to the desired position.
      5. Click OK to close the Control Center dialog box and to save your settings.

      Linux (post 8.0)


      Connect to the server via the IP KVM. Perform the following steps:
      1. Click the Red Hat icon.
      2. Select Preferences - Mouse to open the Mouse Preferences dialog box.
      3. Click the Motion tab.
      4. Set the Acceleration slider slightly left of the center position.
      5. (Optional) Set the Sensitivity and Threshold sliders to the desired positions.
      6. Click Close to close the Mouse Preferences dialog box and to save your settings.

      Red Had Enterprise Edition


      Connect to the server via the IP KVM. Perform the following steps:
      1. Click the Main Menu icon.
      2. Select Programs - Settings - Peripherals - Mouse to open the Mouse dialog box.
      3. Click the Start Here icon to open the Start Here dialog box.
      4. Click the Preferences icon to open the Control Center dialog box.
      5. Click the Peripherals icon to open the Peripherals dialog box.
      6. Set the Acceleration slider to the middle position.
      7. (Optional) Select the desired Mouse buttons option and set the Threshold slider to the desired position.
      8. Click OK to close the Mouse dialog box and to save your settings.

      SUSE Linux


      Connect to the server via the IP KVM. Perform the following steps:
      1. Click the SUSE icon and select Control Center. (By default, SUSE uses a modified version of the KDE graphical user interface.)
      2. Click anywhere in the screen area to open the Behavior (first time use default) - Control Center window where you clicked.
      3. If the Index side navigation bar is shown in tree view, click the plus symbol (+) next to Peripherals to display the submenu items.
      4. Select the Mouse option to display the Mouse - Control Center dialog box.
      5. Click the Advanced tab.
      6. Set the Pointer acceleration slider to the leftmost position (1.0x).
      7. (Optional) Set the Pointer threshold, Double click interval, Drag start time, Drag start distance and Mouse wheel scrolls by sliders to the desired positions.
      8. If necessary, click Defaults to restore the default settings.
      9. Click Apply to save your settings.
      10. Click the X button in the upper-right corner to close the Mouse - Control Center dialog box.

      Solaris 9


      Connect to the server via the IP KVM. Perform the following steps:
      1. From the Workspace Menu, select Desktop Manager and go to step 3 - or -
      2. Click on the tab above the Text Note control and select Applications to open the Application Manager window.
      3. Click the Desktop_Controls icon to open the Application Manager - Desktop_Controls window.
      4. Double-click the Mouse Style Manager icon to open the Style Manager toolbar and Style Manager - Mouse dialog box.
      5. In the Style Manager - Mouse dialog box, set the Acceleration slider to 1.0.
      6. (Optional) Select the desired Handedness and Button 2 options and set the Double-Click and the Threshold sliders to the desired positions. Test the double-click speed by double-clicking on the mouse icon.
      7. Click OK to close the dialog box and to save your settings.

      Solaris 10


      Connect to the server via the IP KVM. Perform the following steps:
      1. In the Front Panel dashboard, click the Style Manager icon to open the Style Manager toolbar.
      2. Double-click the Mouse icon to open the Style Manager - Mouse dialog box.
      3. In the Style Manager - Mouse dialog box, set the Acceleration slider to 1.0.
      4. (Optional) Select the desired Handedness and Button 2 options and set the Double-Click and the Threshold sliders to the desired positions. Test the double-click speed by double-clicking on the mouse icon.
      5. Click OK to close the dialog box and to save your settings.

      Certain Sun/Linux Varieties adjustment via Terminal Session

      Open a terminal session and issue the following command:

      Sun: xset m 1
      Linux: xset m 0 or xset m 1 (if one doesn't help, try the other.)
      Linux using the Redhat AS3.0 mouse mode: xset m 1


      Mac OS


      Connect to the server via the IP KVM. Perform the following steps:
      1. Click the Apple icon.
      2. Select System Prefs to open the System Prefs window.
      3. Select View - Mouse to open the Mouse dialog box.
      4. Set the Tracking Speed slider to the default of the fifth tick mark from the left.
      5. (Optional) Set the Double-Click Speed slider to the desired position. Test the double-click speed by double-clicking a word in the text field below the slider.
      6. Close the Mouse dialog box to save your settings.

      If your mouse is still not synchronizing, please contact APC technical support. Please be sure to provide the following to your technical support representative to expedite resolution.
      • How far apart is the local and remote mouse pointer?
      • Does this problem occur on all remote servers?
      • What type of browser is local and remote?
      • What operating system platform is on the local and remote server/workstation?
      • What is the firmware revision of your IP KVM?
      • Server module part number (Server modules are the components that connect the from the RJ-45 port on the KVM to your remote server).
      • Length and type of Ethernet cable being used between the KVM and the server.

      Where can I get support for APC and MGE Products?

      For support on APC and MGE products please visit:  https://www.apc.com/support/

      AC Power
      Additional Management Cards and Options
      Air Cooled Chillers
      Air Distribution Accessories
      Airflow Management
      AIS 3000
      AIS 5000
      AIS Accessories
      AIS Battery Systems
      APC CS
      APC Enterprise Manager
      APC ES
      APC RS
      Application Shutdown Utilities
      Assessment Services
      Auto and Air Inverters
      AV Accessories
      AV Power Conditioners & Battery Backups
      AV Power Filters
      AV Pro Interconnects
      AV Surge Protectors
      Backpacks and Messenger Bags
      Back-UPS
      Back-UPS Accessories
      Back-UPS BI
      Back-UPS CS
      Back-UPS ES
      Back-UPS HI
      Back-UPS HT
      Back-UPS LS
      Back-UPS Office
      Back-UPS Pro
      Back-UPS RS
      Back-UPS XS
      Basic Rack PDU
      Battery Management
      Battery Replacement Services
      Biometric Security
      Bulk Cable
      Cabinet Power Distribution
      Cable Management
      Charge-UPS EX
      Commercial/Industrial Surge Suppression
      Condensers
      Configurable Power Accessories
      Configurable Power Distribution
      Console Port Servers
      CyberFort
      Data Center Facility Cooling - Andover Continuum or TAC Vista
      Data Center Facility Power - PowerLogic ION Enterprise
      Data Center Software Integration Kits
      Data Center University
      Data Distribution Cable
      DC Battery
      DC Components
      DC Distribution Components
      DC600
      Desktop KVM
      Desktop Notebook Stands
      EcoBreeze Air Economizers
      Environmental Management System
      Environmental Monitoring Unit
      Ethernet Switches
      Extended Warranties
      Fiber Optics
      Firmware Upgrades
      FLM Series
      Fluid Coolers
      FRP/Ferroresonant Power Supply
      Game Console Surge Protection
      Gender Changers
      Global Deployment
      Hardwire Surge Suppression Accessories
      High-Density Cooling Enclosures
      IDE Cables
      IEEE1394
      Industrial
      InfraStruxure for Large Data Centers
      InfraStruxure for Medium Data Centers
      InfraStruxure for Server Rooms
      InfraStruxure for Small Data Centers
      InfraStruxure for Wiring Closets
      InfraStruxure Manager
      InfraStruxure Type A
      InRoom Direct Expansion
      InRow Chilled Water
      InRow Direct Expansion
      InRow Pumped Refrigerant
      Installation Services
      Interface Cables
      International Plug Adapters
      Keyboard
      KVM Switches
      Laptop Power Adapters
      Line-R
      Magnum VS
      Magnum XS
      Magnum XS Rectifier
      Maintenance Bypass Panels
      Management Platform Integration
      Matrix Battery Systems
      Matrix-UPS
      Matrix-UPS Accessories
      Metered Rack PDU
      Metered-by-Outlet Rack PDU
      MGE Accessories
      MGE Alpes
      MGE Battery Systems
      MGE Comet
      MGE EPS
      MGE EPS 6000
      MGE EPS 7000
      MGE EPS 8000
      MGE Galaxy
      MGE Galaxy 300
      MGE Galaxy 3000
      MGE Galaxy 3500
      MGE Galaxy 4000
      MGE Galaxy 5000
      MGE Galaxy 5500
      MGE Galaxy 6000
      MGE Galaxy 7000
      MGE Galaxy 9000
      MGE Galaxy PW
      MGE Legacy
      MGE Service Bypass
      MGE Sinewave
      MGE Static Transfer Switches
      MGE UPS 4000
      Microsol Estabilizadores
      Microsol Modules Isoladores
      Mobile Notebook Stands
      Modular Components
      Modular Power Accessories
      Modular Power Distribution
      Monitor
      Mounting Hardware
      Mouse
      MRC1800
      MRE2400
      Multimedia
      MWF1700
      NetBotz 200
      NetBotz 300
      NetBotz 400
      NetBotz 500
      NetBotz Access Control
      NetBotz Accessories and Cables
      NetBotz Central
      NetBotz Rack Access
      NetBotz Sensors
      NetShelter CX
      NetShelter EP Enclosures
      NetShelter ES Enclosures
      NetShelter Open Frame Rack Accessories
      NetShelter SX
      NetShelter VL
      NetShelter VS Enclosures
      NetShelter VX Enclosures
      Network Integration Services
      Network Patch Cables
      NetworkAIR Accessories
      NetworkAIR AFX
      NetworkAIR CM
      NetworkAIR CW
      NetworkAIR FM
      NetworkAIR IR
      NetworkAIR TC
      Notebook Security
      On Site Service
      Open Frame Racks
      Operations Capacity
      Operations Change
      Operations Energy Cost
      Operations Energy Efficiency
      Operations Insight
      Operations Mobile
      Operations VIZOR
      Outdoor Enclosures
      Panelmount Environmental Monitoring
      Parallel
      Patch Panels
      PC1200
      Planning Tools and Publications
      Portable Cooling
      Power Cords
      Power Distribution Units
      Power Generation Systems
      Power Ready Notebook Cases
      PowerChute Business Edition
      PowerChute Inventory Manager
      PowerChute Network Shutdown
      PowerChute Personal Edition
      PowerChute plus
      PowerManager
      PowerShield
      Preventive Maintenance
      Project Management Services
      ProtectNet
      Rack Air Distribution
      Rack Components
      Rack LCD Consoles
      Rack PDU Accessories
      Rack-mount Transfer Switches
      Refrigerant Distribution
      Remote Monitoring Services
      Replacement Batteries
      Replacement Notebook Batteries
      Residential Hardwire Surge Suppression
      Retail
      Retractable Cables
      Room Air Distribution
      Room Cooling Accessories
      Router Cables
      Row Cooling Accessories
      SCSI
      Security Cameras
      Sensors
      Serial
      Service Bypass Panel
      Service Plans
      Silcon
      Silcon Accessories
      Silcon Battery Systems
      SLM/FLM Series
      SmartSlot Expansion Chassis
      Smart-UPS
      Smart-UPS Accessories
      Smart-UPS Battery Systems
      Smart-UPS DP
      Smart-UPS On-Line
      Smart-UPS RT
      Smart-UPS VT
      Software Configuration
      Software Education
      Software for NetBotz Appliances
      Software Installation
      Software Integration
      Spare Part Kits
      Specialty Enclosures
      Start-Up Service
      Stationary Power Distribution Units
      Step-Down Transformer
      StruxureWare Central
      StruxureWare Operations Suite
      SurgeArrest Essential
      SurgeArrest Home/Office
      SurgeArrest Notebook
      SurgeArrest Performance
      Switch Boxes
      Switched Rack PDU
      Symmetra
      Symmetra Accessories
      Symmetra Battery Systems
      Symmetra MW
      Symmetra MW Accessories
      Symmetra Power Module
      Symmetra PX
      Symmetra PX Accessories
      Sync and Charge Cables
      Thermal Containment
      Thick and Thin Ethernet
      Token Ring
      Toploading Cases
      Traditional Cases
      Training Services
      Transceivers
      Transportation
      Travel Mice
      TSP Accessories
      TSP Battery
      TSP/Generator
      TSP/Total System Power
      Tune-UPS for Symmetra
      Uniflair Chilled Water
      Universal Mobile Device Batteries
      Universal Notebook Batteries
      Universal Notebook Power Adapter
      Universal Power Accessories
      Universal Power Adapters
      UPS Network Hub Card
      UPS Network Management Cards
      USB Adapters & Converters
      USB Cables
      USB Charging Cables
      USB Hubs
      Wall-mount Transfer Switches
      Wheeled Cases
      Wireless
      Wizards and Configurators
      WS200

      Where can I find the Compatibility Support Matrix for PowerLogic/PowerSCADA Expert/ION products?

      Issue
      Where can I find the Hardware and Software Support Matrix for PowerLogic, Power Scada Expert, and ION products?

      Product Line
      Power Monitoring Expert
      Power Scada Expert 
      ION Enterprise
      Struxureware Power Monitoring
      Summary Report Packs
      Event Notification Module
      Active Pager Module
      SMS
      Sequence of Events Recorder

      Environment
      For New Installations

      Cause

      Need to know what Hardware and Software Matrix support is needed to install software packages. 

      Resolution

      Power Monitoring Expert 8.2 Support

      Operating Systems
      Windows 7 Professional/Enterprise, SP1 32/64
      Windows 8.1 Professional/Enterprise 64
      Windows 10 Professional/Enterprise 64
      Windows Server 2008 R2 Standard/Enterprise, SP1 32/64
      Windows Server 2012 Standard 64
      Windows Server 2012 R2 Standard 64
      Windows Server 2016 Standard 64
       
      SQL Server Editions StandAlone Server Distributed Database Server
      SQL Server 2008 R2 Express, SP3 Yes  
      SQL Server 2012 Express, SP3 Yes  
      SQL Server 2014 Express, SP1, SP2 Yes  
      SQL Server 2016 Express, SP1 Yes  
      SQL Server 2008 R2 Standard/Enterprise, SP3 Yes Yes
      SQL Server 2012 Standard/Enterprise/Business Intelligence, SP3 Yes Yes
      SQL Server 2014 Standard/Enterprise/Business Intelligence, SP1 SP2 Yes Yes
      SQL Server 2016 Standard/Enterprise/Business Intelligence, SP1 Yes Yes
       
      Note that supported 32-bit and 64-bit SQL Server editions can only be installed on supported 32-bit and 64-bit Windows operating systems, respectively. For example, a 32-bit SQL Server edition is not supported on a 64-bit Windows operating system.
       

      Power Monitoring Expert 8.1 Support

       
      Operating Systems
      Windows 7 Professional/Enterprise, SP1 32/64
      Windows 8.1 Professional/Enterprise 64
      Windows 10 Professional/Enterprise 64
      Windows Server 2008 R2 Standard/Enterprise, SP1 32/64
      Windows Server 2012 Standard, 64
      Windows Server 2012 R2 Standard 64
       
      SQL Server Editions StandAlone Server Distributed Database Server
      SQL Server 2008 R2 Express, SP3 Yes  
      SQL Server 2012 Express, SP2 Yes  
      SQL Server 2014 Express, SP1 Yes  
      SQL Server 2008 R2 Standard/Enterprise, SP3 Yes Yes *1
      SQL Server 2012 Standard/Enterprise/Business Intelligence, SP3 Yes Yes *2
      SQL Server 2014 Standard/Enterprise/Business Intelligence, SP2 Yes Yes *2
       
      1. Supported for a distributed database server configuration on WindowsServer 2008 R2 Standard/Enterprise SP1.
      2. Supported for a distributed database server configuration on WindowsServer 2012 Standard SP1, and on WindowsServer 2012 R2 Standard.
       Note that supported 32-bit and 64-bit SQL Server editions can only be installed on supported 32-bit and 64-bit Windows operating systems, respectively. For example, a 32-bit SQL Server edition is not supported on a 64-bit Windows operating system.



      Power Monitoring Expert 8.1 DCE Support

      Operating Systems
      Windows 7 Professional/Enterprise, SP1 32/64
      Windows 8.1 Professional/Enterprise 64
      Windows 10 Professional/Enterprise 64
      Windows Server 2008 R2 Standard/Enterprise, SP1 32/64
      Windows Server 2012 Standard, 64
      Windows Server 2012 R2 Standard 64
       
      SQL Server Editions
      SQL Server 2008 R2 Standard/Enterprise, SP3
      SQL Server 2012 Standard/Enterprise/Business Intelligence, SP2
      SQL Server 2014 Standard/Enterprise/Business Intelligence, SP1

       Note: 32-bit and 64-bit versions are supported. Bites must match between SQL Server and Windows OS (32-bit SQL on 32-bit Windows, 64-bit SQL on 64-bit Windows).

       

      Power Monitoring Expert 8.0 Support

      Operating Systems
      Windows 7 Professional/Enterprise, SP1 32/64
      Windows 8.1 Professional/Enterprise 64
      Windows Server 2008 R2 Standard/Enterprise, SP1 32/64
      Windows Server 2012 Standard, 64
      Windows Server 2012 R2 Standard 64
       
      SQL Server Editions StandAloneServer  Distributed Server
      SQL Server 2008 R2 Express, SP3 Yes No
      SQL Server 2012 Express, SP2 Yes No
      SQL Server 2014 Express, SP1 Yes No
      SQL Server 2008 R2 Standard/Enterprise, SP3 Yes Yes *1
      SQL Server 2012 Standard/Enterprise/Business Intelligence, SP3 Yes Yes *2
      SQL Server 2014 Standard/Enterprise/Business Intelligence, SP2 Yes Yes *2
       
      1. Supported for a distributed database server configuration on WindowsServer 2008 R2 Standard/Enterprise SP1.
      2. Supported for a distributed database server configuration on WindowsServer 2012 Standard SP1, and on WindowsServer 2012 R2 Standard.
       Note that supported 32-bit and 64-bit SQL Server editions can only be installed on supported 32-bit and 64-bit Windows operating systems, respectively. For example, a 32-bit SQL Server edition is not supported on a 64-bit Windows operating system.
       

      Power Monitoring Expert 7.2.2 Support

      Operating Systems and Respective SQL installations
      32-bit Windows Operating Systems 32-bit Microsoft SQL Server Editions Standalone Server Distributed Database Server
      Windows 7 Professional/Enterprise, SP1 SQL Server 2008 R2 Express, SP2 Yes No
      SQL Server 2008 R2 Standard/Enterprise, SP2 Yes No
      SQL Server 2012 Express, SP1 Yes No
      SQL Server 2012 Standard/Enterprise, SP1 Yes No
      Windows Server 2008 Standard/Enterprise, SP2 SQL Server 2008 R2 Express, SP2 Yes No
      SQL Server 2008 Standard/Enterprise, SP3 Yes Yes
       
      64-bit Windows Operating Systems 64-bit Microsoft SQL Server Editions Standalone Server Distributed Database Server
      Windows 7 Professional/Enterprise, SP1 SQL Server 2008 R2 Express, SP2 Yes No
      SQL Server 2008 R2 Standard/Enterprise, SP2 Yes No
      SQL Server 2012 Express, SP1 Yes No
      SQL Server 2012 Standard/Enterprise, SP1 Yes No
      Windows Server 2008 Standard/Enterprise SP2, and R2 SP1 SQL Server 2008 R2 Express, SP2 Yes No
      SQL Server 2008 R2 Standard/Enterprise, SP2 Yes Yes
      Windows Server 2012 / R2 Standard/Enterprise SQL Server 2012 Express, SP1 Yes No
      SQL Server 2012 Standard/Enterprise, SP1 Yes Yes
       

      Struxureware Power Monitoring 7.0.1 Support

      Operating Systems and Respective SQL installations
      32-bit Windows Operating Systems 32-bit Microsoft SQL Server Editions Standalone Server Distributed Database Server
      Windows 7 Professional Enterprise Editions, SP1 SQL Server 2008 R2 Express Edition x
      SQL Server 2008 R2 Standard Edition, SP1 x
      Windows Server 2008 Standard/Enterprise Editions, SP2 SQL Server 2008 R2 Express Edition x
      SQL Server 2008 Standard/Enterprise Editions, SP2
      SQL Server 2008 R2 Standard/Enterprise Editions, SP1
       
      64-bit Windows Operating Systems 64-bit Microsoft SQL Server Editions Standalone Server Distributed Database Server
      Windows 7 Professional Enterprise Editions, SP1 SQL Server 2008 R2 Express Edition x
      SQL Server 2008 R2 Standard Edition, SP1 x
      Windows Server 2008 Standard/Enterprise Editions, SP2 SQL Server 2008 R2 Express Edition x
      SQL Server 2008 Standard/Enterprise Editions, SP2
      SQL Server 2008 R2 Standard/Enterprise Editions, SP1
      Windows Server 2008 R2 Standard/Enterprise Editions, SP1 SQL Server 2008 R2 Express Edition x
      SQL Server 2008 Standard/Enterprise Editions, SP2
      SQL Server 2008 R2 Standard/Enterprise Editions, SP1
       

      ION Enterprise 6.0 SP1 Support

      Operating Systems and Respective SQL installations  
      32-bit Microsoft Windows Operating Systems 32 bit Microsoft SQL Server Versions StandAlone Distributed DB Server  
      Windows XP (32-bit) Professional Edition, SP3 SQL Server 2005 (32-bit) Express Edition from the ION:E DVD x  
      Windows Vista (32-1,4) Business/Ultimate/Enterprise Editions, SP2 SQL Server 2005 (32 bit) Express Edition from the ION:E DVC x  
      Windows 7 (32-bit) Professional/Enterprise Editions SQL Server 2005 (32-bit) Express Edition from the ION:E DVD 1 x  
      SQL Server 2005 (32 bit) Standard/Enterprise Editions 2 x  
      SQL Server 2008 R2 (32 bit) Standard/Enterprise Editions 3 x  
      Windows Server 2003 (32-bit) Standard/Enterprise Editions, SP2 SQL Server 2005 (32-bit) Express Edition from the ION:E DVD x  
      SQL Server 2005 (32-bit) Standard/Enterprise Editions  
      Windows Server 2003 R2 (32-bit) Standard/Enterprise Editions SQL Server 2005 (32-bit) Express Edition from the ION:E DVD x  
      SQL Server 2005 (32-bit) Standard/Enterprise Editions  
      Windows Server 2008 (32-bit) Standard/Enterprise Editions, SP2 SQL Server 2005 (32-bit) Express Edition from the ION:E DVD x  
      SQL Server 2005(32-big Standard/Enterprise Editions  
      SQL Server 2008 R2 (32-big Standard/Enterprise Editions 7 11  
         
      64 bit Microsoft Windows Operating Systems Microsoft SQL Server Versions  StandAlone Distributed Minimalist
      Windows 7 (64-bit) Professional/Enterprise Editions SQL Server 2005 (32-bit) Express Edition from the ION:E DVD 4 x x
      SQL Server 2005 (64-bit) Standard/Enterprise Editions 5 x x
      SQL Server 2008 R2 (64-bit) Standard/Enterprise Editions 6 x x
      Windows Server 2008 64 bit Standard/Enterprise Editions, SP2 SQL Server 2005 (32-bit) Express Edition from the ION:E DVD 8 x x
      SQL Server 2005 (64-bit) Standard/Enterprise Editions 9 12 x
      SQL Server 2008 R2 (64-bit) Standard/Enterprise Editions 10 13 14
      Windows Server 2008 R2 64 bit Standard/Enterprise Editions SQL Server 2005 (32-bit) Express Edition from the ION:E DVD 8 x x
      SQL Server 2005 (64-bit) Standard/Enterprise Editions 9 12 x
      SQL Server 2008 R2 (64-bit) Standard/Enterprise Editions 10 13 x
       

      Browser Support for ION E, Struxureware Power Monitoring, and Power Monitoring Expert Support

      Browser Support for ION/SPM/PME
      Browser Support  ION E 6.0 SPM 7.0.1 PME 7.2.2 PME 8.0 PME 8.1 PME 8.2
      IE 11      
      IE 10    
      IE 9        
      IE 8        
      IE 7          
      IE 6          
      Chrome 16+            
      Chrome 20 or later          
      Chrome 42 and later*      
      Firefox 14+            
      Firefox 35 and later*      
      Microsoft Edge*        
      Safari 5 and later          
      Safari 7 and after      

      * The browsers support the web application framework, and Dashboards, Diagrams, and Trends
      applications. Alarms and Tables are dependent on browser support of the Silverlight plugin.

      Power Scada Expert Support

      Operating Systems PLS 7.10 PLS 7.20 PSE 7.30 PSE 7.40 PSE 8.0 PSE 8.1 PSE 8.2
      Windows XP, SP3 Professional Yes Yes Yes No No No No
      Windows Server 2003, SP2 Standard/Enterprise Yes Yes Yes No No No No
      Windows Server 2003 R2, SP1 Yes Yes No No No No No
      Windows Vista, SP2 Yes Yes Yes No No No No
      Windows 7, SP1 Professional/Enterprise No Yes Yes Yes Yes Yes *4 Yes *4
      Windows Server 2008, SP2 Standard/Enterprise No Yes Yes Yes No No No
      Windows Server 2008 R2, SP1 No Yes Yes Yes Yes Yes Yes
      Windows 8 No No Yes *1/2 Yes Yes Yes *4 Yes *3/4
      Windows 8.1 No No No No Yes *2 Yes *4 Yes *4
      Windows Server 2012 No No Yes *1/2 Yes Yes Yes Yes
      Windows Server 2012 R2 No No No No Yes *2 Yes Yes
      Windows 10 No No No No No No Yes *4
      Windows Server 2016 No No No No No No Yes
       
      1. Service Pack 1 for the operating system is required
      2. Available with PowerSCADA Expert Service Release 1
      3. Not supported by Advanced Reporting and Dashboards (PME)
      4. Not supported by PowerSCADA Anywhere
       

      Summary Report Pack Support

      Platform Compatibility
      ✓=Supported SRP 2.1 SRP 3.0  SRP 3.0.1 SRP 3.2 SRP 4.0  SRP 4.2 SRP 4.3
      ION Enterprise 6.0 SP1 x x x x x x
      SPM 7.0 x x x x
      SPM 7.0.1 x x x x x
      PME 7.2 x x x x x
      PME 7.2.1 x x x x x
      PME 7.2.2 x x x x x x
       
      SQL Server              
      Microsoft SQL Server 2005 (32-bit) x x x x x x
      Microsoft SQL Server 2008 (32-bit & 64-bit) x x
      Microsoft SQL Server 2008 R2 (64-bit)
      Microsoft SQL Server 2008 R2 Express x x x x
      Microsoft SQL Server 2012 AI x x x x
       

      Sequence of Events Recorder (SER) Support

      Devices SER 8.0 SER 7.5/7.5.1 SER 7.3
      CM4000 (SER and Standard Alarms)
      Multilin (489, 745, 750,760)
      Sepam (20 40 80)
      Sepam (1000 2000) x x
      Moghnahan Protime
      Moghnahan PLC
      Cyber Sciences 3200
      Cyber Sciences 2408    
      Power Meter 870
      Schweitzer Devices (300G,351A,700G,710,75 A) x x
      Historian SER 8.0 SER 7.5/7.5.1 SER 7.3
      Event Logging
      "Live" Current Events view
      "Historical" Events View
      Event Sorting and Filtering for analysis
      System Health x x x
      "Live Current Events view
      Historical" Events View
      Event Sorting and Filtering for analysis
      Operating System SER 8.0 SER 7.5/7.5.1 SER 7.3
      Windows Server 2012/2012 R2 x x
      Windows 8/8.1 x x
      Windows Server 2008 R2 (64bit)
      Windows Server 2008 (64bit)
      Windows Server 2008 (32bit)
      Windows 7 (64bit)
      Windows 7 (32bit)
      Windows Server 2003 x x
      Windows Vista (32bit) x x
      Windows XP x x
      SQL Server SER 8.0 SER 7.5/7.5.1 SER 7.3
      Microsoft SQL Server 2012 x x
      Microsoft SQL Server 2008 R2 (64bit) x
      Microsoft SQL Server 2008 R2 (32bit) x
      Microsoft SQL Server 2008 x
      Microsoft SQL Server 2005 (32bit) x x
      Browser Support SER 8.0 SER 7.5/7.5.1 SER 7.3
      lE 11 x x
      IE 10 x x
      IE 9 x x
      IE 8 x x x
      IE 8 (Compatibility Mode) x
      Chrome 16+ x x
      Firefox 14+ x x
      Languages SER 8.0 SER 7.5/7.5.1 SER 7.3
      English
       
      *SER 7.5.1 contains the same feature set at SER 7.5, but includes a hotfix related to installs on distributed systems.              
       
       

      Event Notification Module Support

      Platform ENM 8.3 ENM 8.2 ENM 8.0 ENM 7.1 ENM 7.0 ENS 6.4
      PME 8.0 x x x x x
      PSE 8.0 x x x x x
      PSE v7.40 SR1 x x x x
      PSE v7.40 x x x x
      PLSCADA v7.20 x x
      PLS v7.20 SR1 x x x
      PSE 7.30/SR1 x x x
      PLSCADA v7.10 x x x x x x
      CitectSCADA v7.20 x x x x x x
      CitectSCADA v7.10 x x x x x x
      Vijeo Citect v7.20 x  
      Vijeo Citect v7.10 x x x x x x
      SPM 7.0/7.0.1 x x
      PME 7.20 x x x
      ION Enterprise 6.0/6.0 SP1 x x x x
      SMS 4.3 x x x x x
       
      Operating System ENM 8.3 ENM 8.2 ENM 8.0 ENM 7.1 ENM 7.0 ENS 6.4
      Windows Server 2012 R2 (64bit) x x x x
      Windows Server 2012 (64bit) x x x x
      Windows Server 2008 R2 (64bit) x
      Windows Server 2008 (64bit) x
      Windows Server 2008 (32bit)
      Windows 8.1 (64bit) x x x x
      Windows 8 (64(bit) x x x x
      Windows 7 (64bit) x
      Windows 7 (32bit)
      Windows Server 2003 x x x x x
      Windows Vista (32bit) x x x x x
      Windows XP x x x x x
       
      Operating Systems Support for Event Notification Module
      SQL Server ENM 8.3 ENM 8.2 ENM 8.0 ENM 7.1 ENM 7.0 ENS 6.4
      SQL Server 2014 Standard/Enterprise x x x x x
      SQL Server 2014 Express x x x x x
      SQL Server 2012 Standard/Enterprise x x
      SQL Server 2012 Express x x x x x
      SQL Server 2008 R2 (64bit) x
      SQL Server 2008 R2 (32bit)
      SQL Server 2008  x x x x
      SQL Server 2008 SP2 x x x x x
      SQL Server 2005 (32bit) x x x x x
       
      Browser Support for Event Notification Module
      Browser Support ENM 8.3 ENM 8.2 ENM 8.0 ENM 7.1 ENM 7.0 ENS 6.4
      IE 11 x x x
      IE 10 x x x
      IE 9 x x x
      IE 8 x x x x x x
      IE 8 (Compatibility Mode) x x x
      Chrome 20+ x x x x
      Chrome 16+ x x x x
      Firefox 14+ x x x
       

      System Manager Software (SMS) 4.3 Support

      32-bit Microsoft Windows Operating Systems 32-bit Microsoft SQL Server Versions Supported?
      Windows XP (32-bit) Professional Edition, SP3 SQL Server 2005 (32-bit) Standard/Enterprise Yes
      Windows Vista (32-bit) None No
      Windows 7 (32-bit) - Professional/Enterprise  None No
      Windows Server 2003 (32-bit) - Standard/Enterprise Editions, SP2 SQL Server 2005 (32-bit) Standard/Enterprise Yes
      Windows Server 2003 R2 (32-bit) - Standard/Enterprise Editions SQL Server 2005 (32-bit) Standard/Enterprise Yes
      Windows Server 2008 (32-bit) - Standard/Enterprise Editions, SP2 SQL Server 2005 (32-bit) Standard/Enterprise Yes
       
      64-bit Microsoft Windows Operating Systems Microsoft SQL Server Versions Supported?
      Windows Vista (64-bit) None No
      Windows 7 (64-bit) - Professional/Enterprise Editions None No
      Windows Server 2008 (64-bit) - Standard/Enterprise Editions, SP2 None No
      Windows Server 2008 R2 (64-bit) - Standard/Enterprise Editions None No
       
      1. Supported for a distributed database server configuration on WindowsServer 2008 R2 Standard/Enterprise SP1.
      2. Supported for a distributed database server configuration on WindowsServer 2012 Standard SP1, and on WindowsServer 2012 R2 Standard.
      Note that supported 32-bit and 64-bit SQL Server editions can only be installed on supported 32-bit and 64-bit Windows operating systems, respectively. For example, a 32-bit SQL Server edition is not supported on a 64-bit Windows operating system.