End cover comb busbar

Acti 9 Busbar Side Covers, 2 Set of 40 Comb, 1P+N for Clario, Librio, Prodis

Catalogue Number: 21094
End cover comb busbar
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range of product
  • Librio
  • ProDis
  • Clario
    • Range
      Acti 9
      Product name
      Linergy FH
      Product or component type
      comb busbar side cover
      Accessory / separate part category
      insulation accessory
      Poles description
      1P + N
      Quantity per set
      set of 40
      Range compatibility
    • Multi 9 N40 N40N comb busbar
    • Multi 9 N40 Vigi N40 Vigi comb busbar
      • Product compatibility
      • DT60
      • DT40
      • C40
      • iDPN
        • Device presentation
          cuttable
          Distribution type
          N + L1
          Market segment
          small commercial
          REACh Regulation
          Free of Substances of Very High Concern above the threshold
          REACh free of SVHC
          Yes
          EU RoHS Directive
          Compliant
          Toxic heavy metal free
          Yes
          Mercury free
          Yes
          RoHS exemption information
          Yes
          China RoHS Regulation
           Pro-active China RoHS declaration (out of China RoHS legal scope)
          WEEE
          The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
          Warranty
          18 months

          Documents & downloads

          hide show
          Filter items
          • All

          • Product Brochures

          • CAD Files and Packs

          • Technical Data Catalogues

          • Catalog Page

          • Technical Leaflet

          • Product Environmental

          • End of Life Manual

          • Handout

          • Installation Instruction

          • Data Bulletin

          • Specification for Tender

          • Application Solutions

          • Certificates (MSDS)

          • Declaration of Conformity

          • Marine Certificate

          • Software - Released

          Frequently Asked Questions

          hide show

          What is the replacement for the mistral fan 6109?

          The replacement is the 7106A you will also need the wall plate 7100WP.

          Can you get the Magelis XBTGT range with Conformal Coating?

          Yes, the product offering for Conformal Coating on the XBTGT line will be available in 6 Steps:


          Conformal Coating Service for XBTGT 5.7, Sell stage gate in 10th July 2009: XBTGT2110, XBTGT2120, XBTGT2130, XBTGT2220, XBTGT2330

          Conformal Coating Service for XBTGT 12.1, Sell stage gate in 1st August 2009: XBTGT6330, XBTGT6340

          Conformal Coating Service for XBTGT 10.4, Sell stage gate in 1st September 2009: XBTGT5230, XBTGT5330, XBTGT5340

          Conformal Coating Service for XBTGT 3.8, Sell stage gate in 1st October 2009: XBTGT1105, XBTGT1135, XBTGT1335

          Conformal Coating Service for XBTGT 15, Sell stage gate in 1st November 2009: XBTGT7340

          Conformal Coating Service for XBTGT 7.5, Sell stage gate in 1st December 2009: XBTGT4230, XBTGT4330, XBTGT4340

          What is the difference between an alarm contact and an auxiliary contact when used in a circuit breaker?

          Product Line:
          Circuit Breakers

          Environment:
          Electrical Distribution Equipment

          Resolution:
          The auxiliary contact changes state when the circuit breaker contacts change state (breaker opens or closes). The alarm contact changes state only when the circuit breaker goes to the tripped position (or is reset).
           

          What is replacement for part number 25014?

          The replacement for part number is a 9f54420.

          How to determine the firmware version of CM2000 series meters via Front Panel or remotely by software

          Issue
          The customer needs to determine the current firmware version of a Circuit Monitor 2000 either via front panel or over comms remotely by software.

          Product line
          CM2000 Series meters:
          CM2050
          CM2150
          CM2250
          CM2350
          CM2450

          Environment
          Firmware version verification

          Cause
          The meter may not have the latest firmware version 17.011 (fix for rapid energy accumulation on pervious versions of firmware)

          Resolution

          Via Software:
          If CM2000 software is connected to an Ethernet Gateway unit such as EGX or ECC, a Modbus TCP/IP program (like Modscan) or Modbus "Tester" could be used to determine the firmware version over comms.

          1- Read register 2094. This register has a 4 digit number. The two digits on the right in the 4-digit decimal value represent the circuit monitor firmware version (e.g. the decimal value of register 2094 is "1617", the firmware version is 17.XXX).  
          2- Then read register 2093. This decimal value represents the circuit monitor firmware sub-revision level (e.g. the decimal value of register 2093 is "9", the firmware version and sub-revision is 17.009).

          To download "Tester" software, you may refer to article FA180037

          Via front panel:
          The version of firmware in the CM2 can be determined by using the Configuration option of the Setup Mode. The Configuration option allows the user to view configuration data in Protected Mode. No changes to CM2 configuration can be saved when in Protected Mode. When entering the Configuration option in Protected Mode, the CM2 will cycle through four screens of device information. This information will contain the firmware version currently resident in the CM2. It also contains the device model number and the last four digits of the device serial number. 

          PROCEDURE: To view configuration data, complete the following steps:
          1. Press the MODE button until the red LED next to [Setup] is lit. The circuit monitor displays ConFig.
          2. Press the PHASE [Enter] button. The circuit monitor displays the password prompt P - - - -.
          3. Enter 9999 for the password. To enter 9999, use the SELECT METER [Value] buttons to decrease the displayed value until it reaches 9999. Then press the PHASE [Enter] button. The circuit monitor enters the protected viewing mode and scrolls through the following device information:

          • d=2450 (the number after d= represents the device model number)
          • s=0345 (the numbers following s= represent the last four digits of the device serial number)
          • r=1617 (the first two digits after r= represent the reset code revision and the last two digits represent the circuit monitor firmware revision level
          • L=0009 (the digits following 1= represent the circuit monitor firmware sub-revision level, as in firmware version 17.0009)

          After this scrolling sequence, the display shows the present CT ratio.

          The instructions are also in the attached POWERLOGIC/POWERLINK TECH SUPPORT Application Tip document.

          What is the Clipsal 5470

          This is a keyless entry system that Clipsal used to sell until approximately 2009. The key cards used for this are no longer available but work off of 134.2KHz frequency.

          This was a product which Clipsal rebadged from Axeze. Please see the below links for datasheets

          https://axeze.com.au/wp-content/uploads/2015/06/Datasheet-AT-C-01.pdf

          https://axeze.com.au/wp-content/uploads/2015/06/Datasheet-KES-I.pdf

          What is the alternative for a Main switch (surface) 3 phase T300-BK?

          The original T300-BK was unfortunately discontinued. As an alternative the T300FA is very similar. The Majority of its components are the same but some specifications may vary.
          Some of the key features are:
          • Panel mount
          • 300 Amp rated
          • Triple pole
          • Front wiring cover
          • Has dimensions of 210mm (L) x 158mm (W) x 112mm (D)
          For Further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=T300FA

          Or see PDF attached below.
           

          Why does the Zelio Logic Relays turn automatically off.

          One of the main reasons for the Zelio Logic Relays turning off automatically is input supply voltage fluctuation.
           
          The voltage limit for Zelio Logic Relays like SR2 B121JD, SR2 B201JD and SR3 B261JD, with standard input voltage 12V DC, is  10.4 VDC to 14.4 VDC.
           
          The Zelio Logic Relays work properly within the band 10.4 VDC to 14.4 VDC. The moment the input voltage either falls below the lower limit (10.4 VDC) or goes above upper limit (14.4 VDC), the Zelio Logic Relay does not behave properly and turns off.
           
          Recommendation:
          If problem of voltage fluctuation is present suggestion is to use Constant Voltage Transformer (CVT) or Automatic Voltage Stabilizer along with Regulated Power Supply module.

          What does Warning 2107 means in Vijeo Designer?

           Title

           What does Warning 2107 means in Vijeo Designer

          Issue

           

          Product Line

           Vijeo Designer

          Environment

           

          Cause

          Resolution

          Warning 2107: Target Security is enabled, and Web Gate security is disabled. You cannot write to variables from Web Gate.

          This message displays when you have set Target Security to Use Security, and Web Gate Security is disabled. You need to enable Web Gate security so you can properly log in and  write to variables from Web Gate.

           

          To resolve the warning message:

          In the security properties for the target, enable the Web Gate/Web Server Security property by setting it to Use Security.

           

          What is the power terminal lug data for the LC1D40, LC1D50, LC1D65, LP1D40, LP1D50, and LP1D65 contactor?

          Issue:
          Identifying power terminal lug data for the D2 style contactors

          Product Line:
          Tesys D line contactors

          Environment:
          Products sold and used in the United States

          Cause:
          Power terminal lug data required

          Resolution:
          For contactors with screw clamp terminals:
          stranded cable w/o cable end : One #10-3 AWG or Two #10-4 AWG per terminal.
          stranded cable w/cable end: One #10-4 AWG or Two #12-2 AWG per terminal.
          solid cable: One #10-3 AWG or Two #10-6 AWG per terminal.

          Can I poll 6 Digit Modbus registers with Telepace Studio?

          The MSTR and MSIP use a block of registers to store their configurations.

          If the MSTR block uses register 41001 in the SCADAPack as it's configuration start register, then :

          41001 = Comm port number

          41002 = function code

          41003 = slave controller address

          41004 = slave register address

          41005 = master register address

          41006 = length

          41007 = time out in 0.1s increments

          Trying to configure the MSTR block in Telepace prevents you from putting in a slave register address greater than 49999.

          Using a PUTU block, you can put an unsigned integer in the range 40001-65535 into register 41004 to indicate the slave register address. It appears as though the program will take the value in register 40004 and subtract 40001 to determine the holding register offset that gets sent in the actual modbus message.

          For example, using PUTU to put a value of 50010 into register 40004 would then cause the MSTR block to poll for a holding register with an offset of 10009 in the message which would correspond with a 6 digit address of register 410010.

          The largest unsigned integer you could put into register 40004 would be 65535, which would correspond with a 6-digit modbus holding register of 425535.



           

          RAE Systems Sensor Compatability with Version 3 NetBotz Appliances

          Issue:

          RAE Systems Sensor Compatability with Version 3 NetBotz Appliances

          Product Line:

          NetBotz

          Environment:

          NetBotz version 3 appliances
          RAE systems sensors

          Cause:

          Compatibility with 3rd party sensors.

          Resolution:

          As of the release of our Next Generation (v3) NetBotz appliances in April 2009, RAE Systems sensors are no longer supported for direct integration on NetBotz appliances with Botzware 3.x or higher

          List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

          Issue:

          List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

          Product Line:

          NetBotz

          Environment:

          NetBotz version 2

          Cause:

          Supported configurations

          Resolution:

          The following is the list of available device definition files (DDF) as of March 2009. Available DDF files:

          APC
          Alcatel
          Avaya
          Best Power
          Cisco Systems
          Compaq
          DMTF
          Dell
          Extreme Networks
          Foundry Networks
          IBM
          Juniper Networks
          Kohler
          Liebert
          MGE
          MIB2-UPS
          Mitsubishi
          NetBotz
          Powerware
          Server Technology
          Sun Microsystems


          Video: Clear Event Counter on Back-UPS XS/RS "G" & "M" Series

          Issue:
          Tutorial for clearing the on-battery event counter on APC Back-UPS Pro RS/XS/NS G & M models via the front display.

          Product Line:
          Back-UPS Pro XS/RS/NS

          Environment: 
          BR700G/BR1000G/BR1500G
          BX850M/BX1000G/BX1300G/BX1350M/BX1500M/BN1080G/BN1350G

          Cause:
          It may be desired to clear the event counter to track power disturbances following a relocation of the UPS or a change to its electrical environment.

          Resolution: 
          Process to reset the device's on-battery event counter using the method below:
          1. Press the MENU button until Event Counter Screen is displayed.
          2. Press and hold the MENU button for six seconds.
          3. While holding down the MENU button, briefly press the POWER button to set Counter to zero.

          Video: Power-Saving Display Mode on Back-UPS XS/RS "G" & "M" Series

          Issue:
          Tutorial for toggling the power saving display mode on APC Back-UPS Pro RS/XS/NS G & M models to automatically disable the front display or configure the display for always-on operation.

          Product Line:
          Back-UPS Pro XS/RS/NS

          Environment: 
          BR700G/BR1000G/BR1500G
          BX850M/BX1000G/BX1300G/BX1350M/BX1500M/BN1080G/BN1350G

          Cause:
          It may be desired to disable the display when the UPS is in normal operation to avoid visual distraction. Alternately, one may wish to configure the UPS to always illuminate the display for status at-a-glance.

          Resolution: 
          To toggle the power saver display mode, press and hold the MENU button for 2 seconds until a beep is heard. The default behavior to keep the display active at all times.

          Single Phase Symmetra Extended Run (XR) Frame Cable Lengths

          Issue:
          What are the lengths of the DC cables that are attached to single phase Symmetra extended run (XR) frames?

          Product Line:
          Single Phase Symmetra XR Frames

          Environment:
          All serial ranges

          Cause:
          These products are designed to be able to reach each other if position in the same area.  This information can be relevant if a user is planning on installing the products in slightly different areas - different racks, for example.

          Resolution:
          The following table outlines the cable lengths of the DC cable provided with each of the single-phase Symmetra Extended Run cabinets.
           

          XR Type

          Cable Type and Length

          SYXR4

          Fixed or Detachable 5ft (1.5m)
          SYXR12

          Fixed or Detachable 5ft (1.5m)

          SYRMXR4

          Fixed 2ft (0.6m)

          SYARMXR3

          Fixed 3.5ft (1.0m)

          SYARMXR9

          Fixed 5ft (1.5m)

          SYAXR9

          Fixed 5ft (1.5m)




          When polling dual registers in InfraStruXure Central 6.0, both registers must be polled together.

          Issue:

          When polling dual registers in InfraStruXure Central / StruxureWare Data Center Expert, both registers must be polled together.

          Product Line:

          InfraStruXure Central / StruxureWare Data Center Expert

          Environment:

          Modbus communications

          Cause:

          Modbus registers are limited in size, which limits the values they can store and return to a BMS. Unsigned values can not exceed 65535. Because some values returned by ISXC may be greater than this maximum value, we have created the ability to use 2 registers together as a pair to allow for this larger output. If you choose to configure 31001 as a dual register, it will encompass 31001 and 31002.

          Resolution:

          When polling these registers, poll both 31001 and 31002 (or whatever register pair you have set up this way) during the same poll. Failure to do so will return invalid results.

          Pelco Sarix cameras do not get full frame rate with Botzware 3.3

          Issue:

          Pelco Sarix cameras do not get full frame rate with Botzware 3.3

          Product Line:

          NetBotz

          Environment:

          NetBotz version 3 with 3.3 firmware.

          Cause:

          With the release of Botzware 3.3, NetBotz supports a new line of Pelco Cameras. We have tested 3 Sarix cameras and support the entire line by design.

          Due to the large size of JPG images coming from the Sarix cameras, we are unable to pull the images from the camera and then show them or save them in an alert at the full 15 fps rate. We have tested 3 different cameras and have seen the following frame rates when set at 15 frames per second:

          IXS0C-AAWLL39 - 10 fps
          IXE20DN-ABAWU52 - 5 fps
          IX30DN-AAWL040 - 3 fps

          Resolution:

          With the release of BotzWare 4.0, this should no longer be an issue.

          PowerChute Business Edition not recording lost comms in a serial-to-USB configuration

          Issue:
          PowerChute Business Edition not recording lost comms in a serial-to-USB configuration

          Product:
          PowerChute Business Edition

          Environment:
          All supported Windows OS

          Cause:
          When you have the following configuration:
          * the 940-0272A cable ,
          * connecting a serial port on the Smart-UPS SC 1500 to a USB port on a server ,
          * and running with the PL2303 driver from the Prolific company,
          and the cable is disconnected, accidentally or otherwise, then PCBE is unable to report it as a lost communications event.
          (This happens because when the cable is disconnected, the Prolific driver is disabled).

          Solution:

          If this happens you must reconnect the USB plug to the CORRECT USB port on your server and restart the APC UPS Windows service: "APC PBE Agent".

          We strongly recommend, if possible , that you use a serial-to-serial connection to avoid this situation from arising.

          NOTE: If issue is connecting Smart-UPS SC to Windows OS using the 940-0272A cable PowerChute Business Edition does not discover the UPS please see Kbase FA283834
           

          I connected a DVI-D to HDMI converter to display the HMIG5U onto a TV monitor but there is no signal on the TV. Why?

          Issue:
          I connected a DVI-D to HDMI converter to display the HMIG5U onto a TV monitor but there is no signal on the TV.  Why?

          Product Line:
          HMIG5U

          Environment:


          Cause:


          Resolution:
          DVI-D output on the HMIG5U does not support Hot Plug Detect (HPD). Even when the main unit power is on while connected to an external display, this product outputs the display signal as XGA. If the external display does not support XGA Input, the screen will not display.  

          In other words, both the DVI-D to HDMI converter and the TV has to support the XGA (1024 x 768) resolution.  If it does not support the XGA resolution, it will not see the signal properly.  We recommend getting a DVI-D to HDMI converter and TV that will support the XGA resolution.

          Can I reset the ATV600 or ATV900 Process Drive without cycling power to it?

          Issue:
          Customer would like to restart (reboot) the drive without having to cycle power.

          Product Line:
          ATV630
          ATV660
          ATV930
          ATV960

          Environment:
          All Models, All serial numbers

          Cause:
          Restart to clear errors or load new communication parameter settings usually requires a power cycle.

          Resolution:
           
          If connected via a network; you can write a value of 21072 to address 1500 it will reboot the drive as if it had been power cycled.

          If connected to the drive via SoMove you can go to the Device menu and select Restart Device.
          You can also use the HMI to do this by going to Complete Settings - Error/Warning Handling - and change the Product Restart (rP) to YES and press and hold the OK button for 2 seconds.
          Also, a digital input can be assigned to perform this by setting the Prod Restart Assign (rPA) to one of the DI's in the same menu as above.

          NOTE:  The Product Restart and Prod Restart Assign parameters are only available if the Access Level has been set to Expert.

          171CCC9x0x0 M1E Processor 984LL Exec. Upgrade to v.1.30 - Enhancement: Manual TCP/IP retransmission timer for MSTR

          Goals and Symptoms

          The purpose of this resolution is to inform Momentum M1E users that the 984LL Exec. has been upgraded (Aug. 2009) to version 1.30.

          Facts and Changes

          984LL Exec version 1.30 contains the following enhancement:
          1) A configurable TCP/IP retransmission timer for the MSTR function block.

          • The following units affected by this firmware are:
            • 171CCC96020 Processor
              171CCC98020 Processor
              171CCC96030 Processor
              171CCC98030 Processor
          • This enhancement is not supported in the Concept MSTR DX Zoom screens at this time.
          • Resource file MSTR.URF for ProWORX NxT and resource file MSTR.UCS for ProWORX32 are included.

          Causes and Fixes

          A description of the new MSTR function is explained in the attachment Resolution document.

          The attached zip file contains the following files:
          m1ev130.bin M1E firmware
          m1 v130 Resolution.doc Resolution
          MSTR.ucs ProWORX32 resource file
          MSTR urf ProWORX NxT resource file

          Attachments



          (Removed File URL: 199568_C68E/M1ev130.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/6b02aed0302b04aec125760b00528fdc/fl_block_5/0.574?OpenElement&FieldElemFormat=gif)

           


          Legacy KB System (APS) Data: RESL199568 V1.0, Originally authored by DaDz on 08/07/2009, Last Edited by DaDz on 08/07/2009
          Related ranges: Modicon Momentum

          What is one way to tell if a drive is still under warranty?

          Issue:
          Warranty verification
           
          Product Line:
          Altivar variable frequency drives

          Environment:
          Open style
           
          Cause:
          None
           
          Resolution:
          The date of purchase indicated on the distributors invoice or receipt can be used to determine if the drive is in warranty.   The standard warranty is 18 months (see FAQ FA117023) .  If no receipt or invoice is available the date code of the drive can be used to determine if the drive is in warranty.  This date code is imbedded into the number that is located on the right side label of the drive below the bar code.  The first 2 digits indicate the manufacturing plant.  The next two digits indicate the last two numbers of the year it was manufactured and the next two digits indicate the week of that year.  The following numbers indicate the sequence of drive. 
           example:  8B 092124041 (8B = manufacturing location, 09 = year 2009, 21 = week).  The warranty ends November of 2010 (18 months from May 2009).
           

          Symmetra Power Array Input Voltage Selector Theory of Operation

          Issue:
          This document describes how the input voltage selector block of the Symmetra Power Array (NAM) works.

          Product Line:
          Symmetra Power Array

          Environment:
          NAM models only

          Cause:
          This document describes how the input voltage selector block of the Symmetra Power Array (NAM) works.  This is useful for understanding the theory of operation or for troubleshooting.

          Resolution:
          The input voltage selector switch is primarily responsible for two things:  routing power through the appropriate taps of the isolation transformer and notifying the intelligence modules of the expected input voltage. 

          The reason that the IMs need to know the expected input voltage is so that the automatic bypass functionality can operate properly.  If the input differs drastically from the jumper setting, a bypass out of range message will be displayed and the UPS will not be capable of transferring to command or temporary bypass.

          When the jumper is set to the up position, it makes contact with the microswitch at the top of the block.  This will notify the IMs to expect 240 VAC and will also jump the bypass source to the 240 VAC tap. 

          When the jumper is not set (down position), the microswitch is open and the IM assumes 208 VAC input.  This also jumps the bypass to source to the 208 VAC tap. 

          When on inverter, the power modules will output 240 VAC all the time and therefore the inverter output only needs to connect to the 240 VAC tap of the transformer.  The setting of the jumper is only necessary to obtain correct voltages while in bypass. If the jumper is not set correctly, the user will only realize it when in temporary, command, or manual bypass.


            

           

          ClearSCADA: convert group to instance and retain history

          Is there a way to convert a group to an instance of a template and retain the historic data of the points from the group object?

          It is possible to do this but it requires a few a few steps.  Here is how historic files work:

          When you create an object in the CleraSCADA database (i.e. an analog point) an object ID is created for that point.  With 'historic' enabled on that point a corresponding folder is created in the Database\History\Historic folder.  The folder name is derived from the object ID number of the point divided by 256.  For example, if you have an analog point with an object ID of 22004 then you would see a folder created with the name HdI00085.  This is because 22004 / 256 = 85.95.

          Inside folder HdI00085 will be a folder with the name of the object ID (for the example above you would see a folder named 22004).  Inside the 22004 folder will be the historic files which pertain to this point.

          In order to retain history for objects in a group (that is converted to a template) you would need to do the following:

          1) Note the object IDs for each of the objects in the group you wish to retain history for.  Here I've created an analog point and selected 'view status' from the database tree in order to determine that its object ID is 3882.




          2) Open Windows Explorer (File Explorer) and browse to the ClearSCADA\Database\History\Historic folder.  Since the object ID is 3882, the folder we want to look for is 3882 / 256 = 15.164.  Therefore we want folder HdI00015.





          3) Once the folder name(s) have been found, locate the sub folders named with the object IDs.  In this case we are looking for a folder named 3882.

          Inside this folder will be files named with a .hrd extension.  The name of the file corresponds to the number of weeks that have passed since Jan 1, 1601.  One file per object (point) per week is created to store historic data.




          4) Shut down the ClearSCADA server and copy the sub folders (i.e. 003882) to another location.  Shutting down the CS server ensures that the files will not be written to as you are copying them.

          5) Convert the group to a template and then create an instance of the template.

          6) Locate the corresponding objects (points) in the instance (from the Database tree) and note the object IDs for each of these.

          7) Use the method mentioned above to find the folder names where the historic files for the instance objects reside.

          8) Once the new folder names have been found, locate the sub folders named with the new object IDs.

          9) Rename the saved 'original' folders (from step 4) with the new object ID names (from step 7).  In this example you would rename folder 3882 with the corresponding object ID number from the instance.

          10) Shut down the ClearSCADA server and delete the sub folder from step 8).

          11) Copy the folders from step 9) into the locations where you deleted the folders in step 10).

          12) Restart the ClearSCADA server.  (Note: the ClearSCADA server must be shut down prior to moving the folders (in step 11) as the server requires a restart in order to recognize the newly added historic files).

          The instance should now contain the historic values that were previously seen in the original group.

          Video: Back-UPS XS/RS "G" & "M" Manual Adjustment for Sensitivity

          Issue:
          Demonstration of the adjustment for the internal input AC Sensitivity and Transfer Voltages of the Back-UPS XS/RS 'G' & 'M' families.
          Symptom may be seen as frequent transfers to battery power or constant "clicking" being heard from the unit.

          Product Line:
          Back-UPS Pro XS/RS/NS

          Environment: 
          BR700G/BR1000G/BR1500G
          BX850M/BX1000G/BX1300G/BX1350M/BX1500M/BN1080G/BN1350G

          Cause:
          The Back-UPS detects and reacts to line voltage distortions by transferring to battery backup power to protect connected equipment. In situations where either the Back-UPS or the connected equipment is too sensitive for the input voltage level it is necessary to adjust the transfer voltage.

          Resolution: 
          Process is to adjust for frequent line issues such as Line Noise (Total Harmonic Distortion), Brownout or Over Voltage conditions using the method below.
          1. Connect the Back-UPS to an AC power source. Be sure the Back-UPS is turned off.
          2. Press and hold the POWER button for six seconds. The load capacity bar will flash on and off, to indicate the Back-UPS is in Program mode.
          3. Press the POWER button again to scroll through the menu options. The Back-UPS will beep to confirm the selection. Refer to the table for an explanation of the transfer voltage sensitivity levels.
          Sensitivity Indicators

           

          Video: Connect Battery on Back-UPS RS/NS M2 & MS Series

          Issue:
          Tutorial for connecting or replacing the internal battery on Back-UPS Pro RS/NS M2 & MS series. The UPS will indicate a disconnected battery by flashing an empty battery icon on its front display.

          Product Line:
          Back-UPS Pro RS/NS

          Environment: 
          BR1000MS/BR1350MS/BR1500MS
          BN1100M2/BN1350M2/BN1375M2/BN1500M2

          Cause:
          All APC UPS systems are shipped with batteries disconnected to comply with US DOT regulations. The UPS will flash the battery icon to indicate a disconnected battery state.
          A severly discharged/damaged battery will also generate the flashing battery alert. The Back-UPS will not be able to recharge or otherwise use a severely discharged battery.

          Resolution: 
          To connect, disconnect or replace the internal battery, please follow the steps indicated in the video and images below.



          Phase Sources on Symmetra LX PDU Panel SYAPD1

          Issue

          I need to balance my load; how do I identify which receptacle maps to which phase on my SYAPD1 PDU panel so that I do not overload any one phase?


          Product Line

          Symmetra LX


          Environment

          Split phase UPS systems only (SKU ends in P)


          Cause

          Being a split phase UPS system, the load attached to a Symmetra LX UPS must be well balanced across both output phases.  Failure to do so could cause one of the phases to become overloaded and enter a bypass state even if the load is less than the total frame rating.  Each phase should supply roughly the same amount of current so 120 volt loads must be distributed properly by the user to ensure this.


          Resolution

          The SYAPD1 is the standard PDU Panel provided on rack-mount split-phase Symmetra LX UPSs (100/200v, 110/220v, 120/208v, or 120/240v AC output).  SYAPD1 provides the following standard NEMA outlets:

          (2)  L5-20R (3-pin twist-lock)

          (1)  L14-30R (4-pin twist-lock)

          The L5-20R outlets provide single-phase 100, 110, or 120v AC (Phase-Neutral) service. These outlets are sourced consistently from specific phases (legs) on the Symmetra LX.

          The L5-20R located on the left of the SYAPD1 PDU Panel sources from Phase 1.

          The L5-20R located on the right of the SYAPD1 PDU Panel sources from Phase 2.


           


          The UPS is capable of displaying the load on each phase; this information can be accessed either via the front LCD display or via the included network management card.  The information in this document, in addition to the load percentages given by the UPS display, should be enough to balance the load properly across the output phases.


           

          STB Module Logic Bus Current Requirements

          Goals and Symptoms

          The purpose of this resolution is to provide information sources for STB module logic bus current consumption values used by Advantys Configuration Software v4.0.

          Facts and Changes

          This information can be found:
          1. On line in v4.0 configuration software under Hardware Help in the Advantys STB Planning and Installation folder section highlighted below.



          2. On line in v4.0 configuration software under Hardware Help. The four folders shown have logic bus current consumption values in individual modules Specification sections.



          3. On Pl@net in the Advantys STB Technical publications listing.



          The Advantys STB System Planning and Installation Guide, p/n 31002947 has information in the same location as the online version, ie: under STB Module Operating Temperature Ranges.

          4. On Pl@net in the Advantys STB Technical publications listing. STB module manuals have logic bus current consumption values in the individual modules Specification sections.

          Pl@net manuals are:

          Analog I/O Modules Reference Guide 31007715
          Digital I/O Modules 31007720
          Special Modules Reference Guide 31007730
          Counter Modules 31007725

          There are errors in the System Planning and Installation Guides, Special Modules Reference Guides and Analog Module Reference Guides.

          Online and Pl@net versions of the System Planning and Installation Guide incorrectly lists:
          - STBXBE2100 current as 1mA (should be 100mA).

          Online and Pl@net versions of the Special Modules Reference Guide:
          - do not have bus current listed for the STBXBE1100 (25mA).

          Online and Pl@net versions of the Analog Module Reference Guide incorrectly lists
          - STBACO0120 current as 210mA (should be 155mA)

          Attached is a quick reference listing of STB module logic bus current requirements.

          reso_current.zip

          Causes and Fixes

          See Facts and Changes


          Legacy KB System (APS) Data: RESL192962 V3.0, Originally authored by WeDa on 10/11/2008, Last Edited by WeDa on 11/25/2008
          Related ranges: Advantys STB

          How to configure a FDR function in BMXNOC0401 to communicate with a TesysT?

          Applicable to Product Range(s): Web Designer


          Goals and Symptoms
          How to configure a FDR function in BMXNOC0401 to communicate with a TesysT?

          Facts and Change
          BMXNOC0401 firmware version 2.09, BMXP342020 firmware version 2.8, TesysT LTMR27EFM firmware version 2.7

          Causes and Fixes
          The BMX NOC0401 module can be a DHCP and FDR (Faulty Device Replacement) server.

          HTTP, FTP and TFTP are disabled by default in DTM instances created using BMX NOC0401 module firmware version 2.04 or later and Unity Pro 8.1 or later, so the first step is enable these in DTM Browser (Tools -> DTM Browser -> Open -> Security).
          The second step is add the TesysT to DTM  Browser and configure the DHCP and FDR Server (see pictures below).


          Finally, you need to configure the FDR client to receive the data from the server,  in this case the client is a TesysT.




          How FDR works:
          Once the new replacement device is assigned its Role_Name and installed in the network, it issues a DHCP request to obtain its IP address. If its Role_Name is configured in the DHCP server, it will receive an answer with the same IP address as the failed device along with the sub-net mask, the gateway address and the parameter file location. The parameter file location specifies where the device parameter file is stored, the IP address of the FTP server, the directory path in this server and the FTP password.
          When the new device - the FDR client - receives this information bundle from the FDR server, it issues a command to obtain the configuration parameters from the FDR server. Once proper configuration is verified, the FDR server sends the file requested by the replacement device which then takes the file and configures itself to start running on the network.


           

          PowerSCADA Expert 8.2 Update 5 - Release Notes

          Issue
          What is new in PSE8.2 and a detailed listing of resolved problems and minor enhancements.

          Product Line
          PowerSCADA Expert 8.2 (PSE8.2)

          Environment
          Installer
           
          Cause
          A new PSE8.2 cumulative update release.

          Resolution
          PowerSCADA Expert 8.2 Update 5 - Release Notes
          Release Notification (Updated 25 April 2018)

          This is a detailed listing of resolved issues and minor enhancements in this release.

           


           

          Prerequisite

          You must have PowerSCADA 8.2 installed prior to installing this update. No previous updates are required.

          Cybersecurity Announcement

          Floating License Manager v2.1 addresses vulnerabilities in the Flexera FlexNet Publisher component detailed in CVE-2016-10395, CVE-2017-5571 and CVE-2016-2177. Uninstall the current version of the Floating License Manager, and then install version 2.1.
          NOTE: The Floating License Manager v2.1 installer is included with this hotfix release but is not a part of the hotfix installer. Unzip "Floating License Manager v2.1.zip" and run "setup.exe".

          Important Notice: There is a known issue with the Floating License Manager v2.1.0.0 installer. When installing with a logged-in Windows User name containing a space, the install will not succeed. The workaround is to install the Floating License Manager with a user that does not include a space character in their name.

          Bug Fixes and Enhancements

          TFS 21482 - AlarmEvents with a state of normal returned in GetAlarmEvents response for EWS

          GetAlarmEvents was changed to not return alarms in the normal state.

          TFS 21483 - Incorrect timestamp information provided for AlarmEvents not in the Active state

          Alarm timestamps are now updated to reflect the true timestamp of occurrence for all state changes (active, drop out, acknowledge).

          TFS 21484 - Unable to filter AlarmEvents by Type using EWS

          Alarms are now filtered based on type. 

          TFS 21485 - Unable to successfully acknowledge alarms using EWS

          In some situations, EWS would not acknowledge alarms correctly.  This behavior has been fixed.

          TFS 21486 - Unable to filter alarms using the PriorityTo and PriorityFrom fields

          EWS did not observe the priority field correctly. This has been addressed and the minimum allowable priority has been set to 1 (to exclude non-alarm objects in the PowerSCADA alarm database).

          TFS 21557 - PowerSCADA projects - including the starter project, PLS_Include, and PLS_Example - need to be upgraded to support the new DBF schemas

          PowerSCADA projects have been upgraded to the latest DBF schemas.  If there are existing projects created from the starter project, set [CtEdit] Upgrade = 1 in the Citect.ini file using the Setup Editor, and then restart PowerSCADA Studio.

          TFS 21564 - Alarm Proxy does not show the analog alarm states

          Alarm Proxy now reports the analog alarm states (HIGH HIGH, HIGH, LOW, LOW LOW) instead of ON / OFF.

          TFS 21566 - If a CSV file that does not exist is selected in the I/O Device Manager, the application throws a runtime exception

           

          A message is displayed indicating that the file does not exist.

           

          TFS 21569 - On large systems with 200k configured alarms, the GetAlarmDefinitions call in Alarm Proxy is slow and causes ENM to timeout

          Performance issue in alarm proxy has been resolved.

          TFS 21649 - When CoreServiceHost adds and removes devices, it may lose the original IDs

          CoreServiceHost now keeps a device chronicle.  When the device is removed and then later added, the ID will remain the same.

          TFS 21913 - If the equipment name is changed in the system, but the I/O Device name is unchanged, CoreServiceHost will not refresh the equipment name

          CoreServiceHost now properly updates the equipment on name change.

          TFS 21935 - Logs that are too large for the Windows Event Log do not get logged properly

          Large logs are now broken down into smaller log entries.

          TFS 21970 - Profile Wizard and Automation does not support IPv6

          Profile Wizard and Automation now supports IPv6 for TCP/IP Board level drivers.  This requires the TCP/IP Driver version 4.0.0.0 or later.

          TFS 21975 - Open and Close buttons are disabled at runtime on equipment popup when separate digital tags are used for commands

          The form now enables the command buttons if the Pos_On or Pos_Off tags are defined.

          TFS 21979 - Alarm Proxy cannot return alarms that transition to inactive

          This setting is now configurable in the Application Configuration Utility.

          TFS 22043 - Single sign-on calls from a remote thick client do not work

          Single sign-on now detects remote clients.

          TFS 22060 - The I/O Device Manager cannot bulk import devices with device names greater than 16 characters

          The I/O Device Manager now reads the device name length from the equipment.profiles file for proper validation.

          TFS 22066 - Wonderware ArchestrA Logger Security Patch

          Wonderware ArchestrA Logger Patch 2017.517.2328.1 is applied.

          TFS 22150 - Alarm filters do not work on some resolutions

          Alarm filter AN numbers are fixed for all alarm page resolutions.

          TFS 22155 - Alarm filters perform exact matching

          The alarm filter screen allows the user to select the filtering mode. The default setting is read from the INI file [Alarm] FilterMode.  0 (default) = Exact Match, 1 = Starts With, 2 = Ends With, 3 = Contains.

          TFS 22306 - The equipment tree used on alarm pages is slow to render over the web client

          Any page using the equipment tree should set the default library and symbol on the equipment tree genie, or set 'Hide Symbol Icons' to 'TRUE' if a default icon is not available.

          TFS 22401 - Alarm filter and equipment tree filter operate independently

          The alarm filter and equipment tree filter operate together to filter the alarm tables.

          TFS 22896 - Core service host logs two warnings during shutdown - exception thrown during disposal.

           

          Cleanup methods were reworked to prevent the exception.

           

          TFS 22898 - EWS cannot obtain tag updates at a 5 second rate

          EWS and core services were updated to