end cap conduit 150mm p/pipe

SoLid Fittings - PVC, Conduit Caps, 150mm - Suits 150mm pressure pipe

Catalogue Number: 262P150
end cap conduit 150mm p/pipe
Colour: Electric Orange
Colour: Per UOM Std.
  • Electric Orange 1 PCE
Added to cart

Specifications

hide show
Product brand
Clipsal
Range of product
Series 262
Material
PVC (polyvinyl chloride)
Diameter
  • inner: 160.5 mm
  • outside: 168 mm
    • Length
      53 mm
      Sustainable offer status
      Green Premium product
      REACh free of SVHC
      Yes
      EU RoHS Directive
      Pro-active compliance (Product out of EU RoHS legal scope)
      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)
      Environmental Disclosure
      ENVPEP100802EN
      Circularity Profile
      N/A

      Documents & downloads

      hide show
      Filter items
      • All

      • Product Brochures

      • Technical Data Catalogues

      • Installation Instruction

      • Specifications

      • Certificates (MSDS)

      Frequently Asked Questions

      hide show

      Are there Certificates of Conformity for the 247P100 and 262P100?

      No. Unfortunately, there are not.

      What is a 32A inductive isolator for an induction cook top

      Part number PDL 56SW150

      What is the length of the bell mouth 288/150


       The length is 290mm long.
      please see following website for catalogue information as well as Technical specifications
      https://www.clipsal.com/Trade/Products/ProductDetail?catno=288/150

      What is the standard pack size of the 262/25?

      The standard pack size of the 262/25 is 50

      Some of the key features are:
      • Rigid Tube
      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=262/25
       

      What can cause the InF fault in the Altivar 31 and Altivar 312 drives?

      Issue:
      What can cause the InF fault in the Altivar 31 and ATV312 drives?

      Product Line:
      Altivar 31 and ATV312 drives

      Environment:
      All 

      Cause:
      Internal fault 

      Resolution:
      InF indicates an internal fault.  
      It can occur if there are loose connections inside the drive or if the drive is subjected to electromagnetic interference.  Check the line voltage to the drive.
      Also, check the voltages on the control terminals, +10 to COM and 24V to COM.  It has been observed that improper wiring of the inputs or external potentiometer can overload the internal power supplies of the drive. This may result in InF fault.
      Incorrect connections on the RJ45 ModBus/CANopen port can also cause this.  Verify wiring, particularly to pin 7 (10VDC supply for external keypad).



       

      What material is the XVBC02 & XVBC11 made of?

      Issue:
      What material is the XVBC02 & XVBC11 made of?

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      The XVBC02 is stainless steel (matte black finish). The XVBC11 tulip is a Zinc alloy (black matte finish).


      CTA-ID : 2023180

      What is the part number for the lugs for a NSF250N?

      Product Line:
      Circuit Breakers
      NSF

      Environment:
      Electrical Distribution Equipment

      Resolution:
      Part number is 37488 for 200-250 amps lugs. 3 lugs per kit. Terminal cover included.


       

      What is the timing range for RE7M*, RE7T*, RE7P* and RE7R?

      Issue:
      What is the timing range for RE7M*,  RE7T*,  RE7P*  and RE7R?

      Product Line:
      Relays and Timers

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      The timing is adjustable from 0.05 seconds to 300 hours in 10 ranges.


       

      Are the color inserts available in 30mm 9001KR and 9001SKR pushbuttons?

      Issue:
      What is the part number for the 9001KR1U  color inserts?

      Product Line:
      Harmony Pushbuttons

      Environment:
      9001 K, 9001SK, KR1, KR2, KR3, SKR1, SKR2, SKR3, KR11, KR12, SKR11, SKR12, KRD, T, TRD

      Resolution:
      Universal Color 9001T8U
      Black 9001T8BK
      Blue  9001T8BE
      Gray 9001T8GY
      Green 9001T8GN
      Orange  9001T8OE
      Red  9001T8RD
      White  9001T8WK
      Yellow 9001T8YW

      What is meant by common trip as it relates to a 2 or 3 pole breaker?

      Issue:
      Does a handle switch trip both breakers?
       
      Product Line:
      Miniature Circuit Breaker
       
      Environment:
      QO Circuit Breaker
       
      Resolution:
      This means the 2 or 3 poles are linked internally and if any pole trips, they all open together
      Single pole breakers linked externally with a handle tie are not common trip. One breaker (pole) tripping does not trip the others.

      Where are the EDS files for the ATV58 Devicenet communication card?

      Issue:
      Where are the EDS files for the ATV58 Devicenet option card.

      Product Line:
      Altivar ATV58 with Devicenet option card

      Environment:
      Product versions 5.X and 3.X only

      Cause:
      EDS files for the Devicenet option card for the ATV58 drives.

      Resolution:
      You will need to find the product version of the drive before you install your EDS file.   Remove the keypad from the VFD and you will see a white sticker with a product version on it.
      I have attached ATV58 EDS files for product version 3.X and 5.X

      CTA-ID : 2027180

      Why does an ATS48 soft starter with remote keypad will only allow access to status and SUP menu?

      Issue:
      Why does an ATS48 soft starter with remote keypad will only allow access to status and SUP menu?

      Product Line:
      ATS48 Soft starter with remote HMI

      Environment:
      All

      Cause:
      keypad is locked or stuck on SUP menu

      Resolution:
      On the back of the remote keypad, there is a 3 position switch.  If this switch is in the ``FULLY LOCKED`` position, it will not allow access to any menus other than SUP.  Move this switch to the ``FULLY UNLOCKED`` position to gain access to all menus within the starter.

      How do I assign Reference Switching to a Logic input in the ATV28?

      Issue:   How do I assign Reference Switching to a Logic input in the ATV28?
       
      Product Line:   ATV28
       
      Environment:  All
       
      Cause:   N/A
       
      Resolution:   
      From factory I/O settings it will be necessary to set the LI4 then LI3 inputs to some setting that is compatible with Reference Switching. Preset speeds are incompatible with Reference Switching. LI4 must be changed before LI3. If not using LI3 or LI4 set them to NO.

      In the I-O menu change the desired logic input to rFC. It will be in Auto and use AI2 or AIC for speed reference when the contact is open. The drive will be in Hand mode and use AI1 for speed signal when there is 24 VDC on the rFC input.


       

      Video: Increasing ATV21 & ATV212 High Speed Setting Beyond 60Hz.

      Issue:
      Video: Increasing ATV212 & ATV12 High Speed Setting Beyond 60Hz.

      Product Line:
      ATV21 ATV212 S-Flex

      Environment:
      All serial numbers

      Cause:
      Overspeed operation is desired.

      Resolution:
      First, set the maximum frequency, FH, to at least the desired high speed.
      Second, change the upper limit, UL, to the desired high speed.

      If an analog input is used for speed reference, it will need to be scaled:
      If FMOd=1, VIA analog input, then set F204 to the high speed.
      If FMOd=2, VIB analog input, then set F213 to the high speed.
       

      GV2P disconnect options

      Issue:
      What is the product number for a complete through-the-door disconnect device for a GV2P

      Product Line:
      GV2P Manual Starters and Protectors

      Environment:
      US product

      Cause:
      Digest 176 is unclear as to what is a complete mechanism with shaft and handle

      Resolution:
      There are three devices which include mechanism, shaft and handle:
      GV2APN01 has a NEMA 1, 12 rating and is black
      GV2APN02 has a NEMA 1, 12 rating and is red/yellow
      GV2APN04 has a NEMA 3R, 4, 4X rating and is red/yellow

      What is the difference between the 9001K20 and the 9001K21?

      Issue:
      What single potentiometer operator with single pot should be used with 10 ohms?

      Product Line:
      Harmony Push Buttons

      Environment:
      All products

      Cause:
      Product Features

      Resolution:
      The 9001 K20 is the operator only without the single pot. The 9001 K21 is the operator with the single pot.

      What are the coil voltage codes for the LC1D115 / LC2D115 and LC1D150 / LC2D150 TeSys contactor?

      Product Line:
       
      Tesys D line Contactors
       
      Resolution:
       
      The following list the more common voltage suffix codes for these product lines.  For a more comprehensive list and to determine compatibility with a given product, refer to the catalog below.

      Note 1: LC1D150 contactors are only available with *7 coil codes.
      Note 2: Coil Code ending number represents frequency rating as follows:
      5 = 50 Hertz
      6 = 60 Hertz
      7 = 50/60 Hertz

      AC Volts ___Code                DC Volts ___Code
      24 ___ B5 or B6 or B7          12 ___ Not Avail.        
      42 ___ D5 or D7                   24 ___ BD
      48 ___ E5 or E6 or E7          36 ___ CD
      110 ___ F5 or F6 or F7         48 ___ ED
      115 ___ FE5 or FE7             60 ___ ND
      120 ___ G6 or G7                72 ___ SD
      127 ___ FC5 or FC7            110 ___ FD
      208 ___ L6 or LE7               125 ___ GD
      220 ___ M5 or M6 or M7       220 ___ MD
      230 ___ P5 or P7                 250 ___ UD
      240 ___ U5 or U6 or U7        440 ___ RD
      277 ___ W6 or UE7                
      380 ___ Q5 or Q6 or Q7                
      400 ___ V5 or V7                
      415 ___ N5 or N7                
      440 ___ R5 or R6 or R7                
      480 ___ T6 or T7                
      500 ___ S5 or S7                


       

      What is the part number for the spacer used with the LC*D09 through LC*D32 Contactor and the GV2AF3 combination block when the GV2 Motor Circuit Protector is mounted on din rail and the contactor hangs below it?

      Issue:
      Identifying the spacer part number for use with a LC*D, GV2AF3, and GV2 device combination

      Product Line:
      Digest 177 Section 18 : Contactors and Starters IEC

      Environment:
      Products sold and used in the United States

      Cause:
      Spacer required

      Resolution:
      Compensation plate catalog number GV1F03, requires 2 pieces snap together.
       

      Can the single pole LA1DN and LADN auxiliary contact module be mounted on the TeSys contactors?

      ISSUE
      Can the single pole LA1DN and LADN auxiliary contact module be mounted on the TeSys contactors?
      PRODUCT LINE
      Auxiliary contacts for the Tesys D line
      ENVIRONMENT
      Tesys D-Line and Tesys F
      CAUSE
      Fit
      RESOLUTION
      These contacts will only fit on the following contactors:
      Front mount only for LC1D40 through LC1D115 devices and LC1D40A - LC1D65A.
      Left side mount only to LC1F contactors
      CTA-ID : 2002751

      What is the replacement part number for the Magelis XBTGT2330 HMI?

      Issue
      The Magelis XBTGT2330 HMI is no longer in production. What is the replacement part number for the Magelis XBTGT2330 HMI?

      Product Line
      Magelis XBTGT2000 series HMI, XBTGT2330

      Resolution
      The three options to replace the obsolete XBTGT2330 are:

      1) HMIGTO2310 (5.7" screen)
      https://www.schneider-electric.us/en/product/HMIGTO2310/advanced-touchscreen-panel-320-x-240-pixels-qvga--5.7%22-tft---96-mb/
      This has the same resolution as the XBTGT2330 (320x240) and 65,536 colors, so it will only require a change in HMI ("Target") Type in the configuration software of the project.
      The dimensions for mounting are the same as the XBTGT2330.
      The HMIGTO series requires Vijeo Designer v6.2 (Part Number: VJDSNDTGSV62M)

      2) XBTGT2390 (5.7" screen)
      https://www.schneider-electric.us/en/product/XBTGT2930/advanced-touchscreen-panel---320-x-240-pixels-qvga---5.7%22---tft-lcd---24-v-dc/
      This HMI is almost exactly the same as the XBTGT2330 and is the closest replacement with newer electronics.
      The dimensions are the same as the original XBTGT2330.
      This has the same resolution as the XBTGT2330 (320x240) with 65,536 colors and will require NO change in the configuration project.
      Just call your dealer to ensure that it can be ordered as it may be in short supply.

      3) HMIG3U in combination with HMIDT351 (7" screen)
      https://www.schneider-electric.us/en/product/HMIG3U/premium-box-for-universal-panel/
      https://www.schneider-electric.us/en/product/HMIDT351/7w-touch-advanced-display-wvga/
      The HMIG3U back module holds the CPU and Communication ports, while the HMIDT351 is the 7"  touchscreen that locks into the back module.
      This one is higher resolution at 800x480, 262,144 colors, and has much faster processing power.
      This will require a change in HMI ("Target") Type in the configuration software (Vijeo Designer v6.2) of the project as well as require object resizing in the software configuration.
      This requires a larger cutout for mounting.

      For reference, the XBTGT2330 product page:
      https://www.schneider-electric.us/en/product/XBTGT2330/advanced-touchscreen-panel---320-x-240-pixels-qvga---5.7%22-tft-lcd---24-v-dc/

      Are the D-Line contactors rated to break DC voltages?

      Issue: 
      Can the TeSys D line be used to control DC loads? 

      Product Line:
      Tesys D contactors

      Environment:
      Products sold and used in the United States
       
      Cause:
       DC power circuit
       
      Resolution:
       
      Yes, 75 VDC (125 VDC for D115 & D150) per pole which means that through a four pole device breaking 300 VDC is possible by wiring all four power poles in series. However, be aware that the device current ratings will differ according to the number of poles in series and the type of application.

      Devices are suitable but not UL Listed for DC applications.

      More information on their DC ratings can be found in the current TeSys Motor Control and Protection Compentns catalog: https://www.schneider-electric.us/en/download/document/MKTED210011EN/


       

      What are the stand alone short circuit current ratings on the LC1D** contactors?

      Issue:
      Tesys D SCCR

      Product Line:
      Contactors and Overload Relays

      Environment:
      TeSys™ D Contactors and Overload Relays
       
      Resolution:
      The contactors have a stand alone withstand rating that has been established by UL and is based on the maximum horsepower rating for a given device. However, only combination type starters are supplied with short circuit protective devices having a short circuit current rating.

      They are as follows:
      Horsepower SCCR (A)

      0 thru 1 1,000
      1 thru 50 5,000
      51 thru 200 10,000
      201 thru 400 18,000
      401 thru 600 30,000
      601 thru 900 42,000
      901 thru 1600 85,000
      1601+ 100,000

      What is the breakdown of components for 9001KYK117?

      Issue:
      What is the breakdown of components for 9001KYK117?  

      Product Line:
      Harmony Push Buttons

      Environment:
      Harmony Control Stations

      Cause:
      Product Features

      Resolution:
      9001KYK117 components are:
      1-9001KY1S1 (red enclosure)
      1-9001K15 (break glass operator)
      1-9001KA1 (1 open and 1 closed contact)
      1-9001KN799RP (legend plate)

      Replacement glass discs are 9001K57 (package of five)
       

      Spurious triggers of transient module on ION 7550/7650 and ION8800

      Issue
      ION 7650/7550 and ION 8800 series devices can cause spurious triggering of the transient module when transients do not exist. This issue exists in firmware up to and including V354 for the ION 7650 and V334 for the ION 8800.

      Symptoms
      ION meters displaying this issue will find the transient module on ION 7650 and ION 8800 devices will trigger intermittently or with a fairly regular pattern (i.e. about every 15 minutes) while no corresponding real observable transient event actually occur in the monitored electrical system. The following observations may be describing this issue:

      1. Too many transients events being triggered. Unduly frequent transient events being recorded with associated waveform captures.
      2. Inspection of the waveform captures from transient events show no changes of the waveform.
      3. Transient module triggering regularly with no real corresponding power quality events in the actual physical electrical system being monitored.
      4. Adjustment of the transient module's threshold value doesn't seem to make much difference to the rate of transient triggers.
      5. Re-programming of the meter framework (by pasting the framework from a healthy meter, for example) does not fix the problem.
      6. Newer meters such as the ION 7650 and ION8800 show this problem while older ION meters (ION7600 and ION 8500) with the same or similar framework seem to be immune.​
      Product Lines
      ION7650
      ION8800

      Environment
      Transient Module

      Cause
      The issue is observed when a large nominal voltage (approximately 131,000) is linked to the transient module. The nominal voltage is multiplied internally by the maximum A/D count value, and with the large nominal voltage this calculation overflows a 32-bit integer. The problem will be most noticeable when the nominal voltage is slightly larger than the roll -over value - in this case, the roll-over will result in a very small transient threshold value, and therefore a large number of transients detected. E.g. nominal voltages of 131,000 or 262,000 will be most noticeable, while a nominal voltage of 250,000 would not be as noticeable."

       

      Resolution
      Update the firmware to V355 or newer for the ION 7650 and V340 or newer for the ION 8800.

      If a firmware upgrade is not possible or spurious triggers still persist, scale down the nominal voltage input to the transient module, and increase the threshold setting by a proportionate amount.
      E.g. If the nominal voltage was 140,000, and the threshold was 25%, make the nominal voltage 70,000 and the threshold 50%. This would detect transients with the same sensitivity as the original settings, but the reported values would be different (i.e. the reported magnitude would be twice as large, and the reported nominal would be half of what it should be). The framework would also have to be modified so that a custom value was linked into the transient nominal - otherwise changing this setting would affect other operations on the meter such as sag/swell detection.

      *This issues only affects PRODUCTS with transient capability. This issue affects other product lines with transient capabilities (ie. ION 8500, ION 7600) although only for voltages above 1MV so in practicality it should not appear.

      How to connect ClearSCADA servers using Advanced EWS driver

      DISCLAIMER 

      The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.


      The Advanced EcoStruxure Web Services Client driver (Advanced EWS driver) allows communications with servers that comply with EcoStruxure Web Services version 1.1, which includes ClearSCADA servers.
      This article is a quick start guide showing how to connect two ClearSCADA servers and make the client machine (ClearSCADA machine that will run the Advanced EWS driver) to read both current and historic data from a particular point. For more details on how the driver works, please refer to the manual, at Help > Contents > Driver Reference > EcoStruxure Web Services Client - Advanced Driver.

      First, lets check the configuration that must be done on the ClearSCADA that will act as server.
      Right click on the $Root object, select "Edit Properties, go to the "EcoStruxure Web Services" tab:


      Enable the Web Services and select a ClearSCADA user with rights to access the points that will be read by the other ClearSCADA machine. Save the changes.
      Also, make sure WebX is running on the server machine and take note of the port in use (HTTP or HTTPS).

      On the ClearSCADA machine that will be the client, let's create a few Advanced EWS driver objects, starting with an Schneider Electric EWS - Advanced > Server object:


      Put the object "In Service" and set the appropriate "Server URL". In this example the URL used was:
      https://172.16.159.129:82/webservices/secorp
      The client will communicate using HTTP to IP address 172.16.159.129, port 82, which is where the other machine's WebX server is listening.

      Now let's create a Schneider Electric EWS - Advanced > Group object:

      Put the object "In Service", add the Server object we just created to the "Servers" list and set suitable "Scanning Intervals" for Current Data and Historic Data. Save the changes.

      Now it is time to create the first point, in this case a Schneider Electric EWS - Advanced > Analog Point object:


      On the "Analog Point" tab, put the object "In Service", set "EWS Group" to the Group object we just created and browse for the "Current Data Id" and "Historic Data Id"  of the point we want to read data from the server machine.


      Don't forget to enable historic on the point, then save the changes.

      You can check the connection status looking at the "View Status" dialog box from the Server object:

      If the connection to the server machine was successful, the "State" will be "Healthy" and the driver will poll current and historic data periodically.
      Historic lists for the point on the server side and on the client side should be the same:

      Note: In ClearSCADA 2017 R3, ClearSCADA 2017 R2 and ClearSCADA 2017 from build version 7013 (~15th March 2019) onwards ensures no WebX licence is consumed. Previous versions of ClearSCADA may consume a WebX licence under certain circumstances which may stop users successfully connecting.

       

      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 obtain data at a 5 second poll rate.

      TFS 23262 - Equipment popup alarm table does not acknowledge or disable alarms

      Alarms can now be acknowledged or disabled in the equipment page.

      TFS 23274 - Equipment.profiles cannot be imported into the Profile Editor in cases where the original Device Types and Device Profiles were lost

      The Profile Editor can import the equipment.profiles file to generate device types, device profiles, and tags.

      TFS 23437 - Citect 2016 Updates

       

      Citect 2016 Update (April 10, 2018) is included with this update.

      Project ID management was removed from Citect 2016.  Project IDs are now located in the ProjectInfo.xml file. 

      MinUnitNumber and MaxUnitNumber (previously stored in UnitNumberRange.xml) have also been migrated to ProjectInfo.xml.

       

      TFS 23637 - The Alarm Summary page does not display state information

      The Alarm Summary page now displays the state that caused the alarm.

      TFS 23650 - 8.2 install does not enable ASP feature within IIS

      The installer now enables the ASP feature under IIS. This server role feature is required to run the Citect web control client. (Previously the View-Only web client was the only option for web deployment.)

      TFS 24205 - When Core Services receives a timeout from the Client, alarm processing may halt until the service is restarted

      Core Services properly recovers from a ctApi deadlock condition.

      Files Modified

      Applications\AppServices\bin\Framework.dll
      Applications\AppServices\bin\Framework.ServiceHost.exe
      Applications\AppServices\bin\Modules.CoreServices.dll
      Applications\AppServices\bin\PowerLogic.Cipher.dll
      Applications\AppServices\bin\Modules.ProviderBase.dll
      Applications\AppServices\bin\Modules.ProviderEngine.TestHarness.exe
      Applications\AppServices\bin\ObjectFactoryTools.exe
      Applications\AppServices\bin\ProviderGatewayProviders.dll
      Applications\AppServices\bin\PowerSCADA.Common.dll
      Applications\AppServices\bin\Modules.Platform.Citect.dll
      Applications\EWS\bin\Framework.dll
      Applications\EWS\bin\EWS.dll
      Applications\EWS\Web.config
      Applications\EWS\DataExchange.svc
      bin\de\ProfileEngine.resources.dll
      bin\de\ProfileWizard.resources.dll
      bin\de\WizardLibrary.resources.dll
      bin\es\ProfileEngine.resources.dll
      bin\es\ProfileWizard.resources.dll
      bin\es\WizardLibrary.resources.dll
      bin\fr\ProfileEngine.resources.dll
      bin\fr\ProfileWizard.resources.dll
      bin\fr\WizardLibrary.resources.dll
      bin\it\ProfileEngine.resources.dll
      bin\it\ProfileWizard.resources.dll
      bin\it\WizardLibrary.resources.dll
      bin\ja\ProfileEngine.resources.dll
      bin\ja\ProfileWizard.resources.dll
      bin\ja\WizardLibrary.resources.dll
      bin\ko\ProfileEngine.resources.dll
      bin\ko\ProfileWizard.resources.dll
      bin\ko\WizardLibrary.resources.dll
      bin\ru\ProfileEngine.resources.dll
      bin\ru\ProfileWizard.resources.dll
      bin\ru\WizardLibrary.resources.dll
      bin\zh-chs\ProfileEngine.resources.dll
      bin\zh-chs\ProfileWizard.resources.dll
      bin\zh-chs\WizardLibrary.resources.dll
      bin\zh-cht\ProfileEngine.resources.dll
      bin\zh-cht\ProfileWizard.resources.dll
      bin\zh-cht\WizardLibrary.resources.dll
      bin\ProfileAutomation.dll
      bin\ProfileEngine.dll
      bin\ProfileWizard.exe
      bin\WizardLibrary.dll
      bin\ProfileAutomationUtility.exe
      bin\CommsMethodProperties.xml
      bin\DeviceManagementUserControlLibrary.dll
      Applications\Profile Editor\Tags.xml
      Applications\Profile Editor\ProfileEditor.Business.dll
      Applications\Profile Editor\ProfileEditor.exe
      Applications\Profile Editor\ProfileEditor.UserControls.dll
      Applications\Profile Editor\Resources\ProfileEditor.UserControls.resources
      User\PLS_Include\*
      User\PLS_Example\*
      Starter\Default_Starter.ctz

      Installation

      Unzip "PowerSCADA Expert 8.2 Update 5.zip" and run "PowerSCADA Expert 8.2 Update 5.exe".