Building Automation Knowledge Base

Issue What fingerprint or faceprint readers does Security Expert support? Product Line EcoStruxure Security Expert Environment Security Expert Fingerprint Reader Faceprint Reader Biometric Reader Cause Require information on what Biometrics readers are supported with Security Expert. Resolution We officially support Suprema, Princeton Identity and IDEMIA biometric readers (see SX SRVR Security Expert - Compatibility Matrix) however our reader expanders/controllers are able to work with any reader that provides a standard 26-bit Wiegand output.   If there is a biometric reader that does this it should be able to be connected to Security Expert like a standard card reader supplying the controller with Wiegand data that is assigned to a user. The enrolling of biometrics would need to be handled by the third party system, we would essentially be treating it as a normal card reader and card.   For a list of Suprema devices that Security Expert supports refer to the Suprema Biometric Integration in Security Expert Application Note. For a list of Princeton Identity devices that Security Expert supports refer to the Princeton Identity Biometric Integration  Application Note. For a list of IDEMIA devices that Security Expert supports refer to the IDEMIA Biometrics Integration Application Note.

Issue What sensors can be used in Clean Rooms  What sensors can be used outdoors for temperature measurement What sensor can be used in a swimming pool What sensor would be explosive proof What color is the wall sensor and are custom colors available Environment Building Automation System such as I/NET, Vista, or Continuum at a site containing a clean room, swimming pool, or outdoors Cause Questions concerning the uses of Schneider Electric sensors in Clean Room applications Questions concerning temperature sensors for Outdoor installations Questions concerning temperature sensors for swimming pools Questions concerning explosion proof sensors* Questions concerning color and custom colors for sensors Resolution All the Schneider Electric temperature sensors found in the HVAC Sensor Catalogue as well as on iPortal provide high accuracy and can be mounted on the wall, in ducts, or in a J-Box. Appendix A provides the accuracy for each of the temperature sensors. Color: STR series wall sensors are: Front Cover: White NCS S-0500 N Core Plate: White NCS S-0500 N and Gray NCS S-2500 N Base Plate: Gray NCS S 1502-R Manufacturing in custom colors in not available. One option could possibly to have the sensors locally custom finished to meet customer's requirements. While there is not a direct cross reference to RAL colors, our engineering team has found the closest alternates. Please see the attached pdf. Clean Room: Depending on the specified limits of the clean room, the variety of sensors offered by Schneider Electric are possible solutions. Thing you may want to research are the standards required for the site. Clean rooms are a controlled environment where products are manufactured. It is a room in which the concentration of airborne particles is controlled to specified limits. Eliminating sub-micron airborne contamination is really a process of control. These contaminants are generated by people, process, facilities and equipment and must be continually removed from the air. The level to which these particles need to be removed depends upon the standards required. The most frequently used standard is the ISO 14644 Standards, which were first formed from the US Federal Standard 209E Airborne Particulate Cleanliness Classes in Cleanrooms and Clean Zones.  ISO 14644 is a document that establishes standard classes of air cleanliness for airborne particulate levels in cleanrooms and clean zones. Strict rules and procedures are followed to prevent contamination of the manufactured product. The only way to control contamination is to control the total environment. Air flow rates and direction, pressurization, temperature, humidity and specialized filtration all need to be tightly controlled. Outdoor:  Schneider Electrics selection of Outdoor Temperature Sensors are the STO100, 200, 500, & 600. These outdoor sensors are intended for outdoor wall mounting. Variants are available for Vista, I/NET, Continuum and Satchwell systems. The body has a 20mm conduit entry and the product is supplied with a conduit gland. Range -40 to +90 °C Accuracy See Appendix A: Table A, C, F in the attached HVAC Sensor Catalog.pdf Outdoor Temperature Sensor STO100 Order Code 5141100010 Part Number STO100 System Vista, Xenta Outdoor Temperature Sensor STO200 Order Code 5123246000 Part Number STO200 System I/NET Outdoor Temperature Sensor STO500 Order Code 5141104010 Part Number STO500 System Continuum Outdoor Temperature Sensor STO600 Order Code 5126060000 Part Number STO600 System Satchwell Outdoor Temperature Sensor STO600D Order Code 5126000000 Part Number STO600D System Drayton Outdoor Temperature Transmitters STO300 The STO300 transmitter is supplied as a complete unit, comprising a sensing element and an amplifier mounted in a housing which is resistant to ultraviolet light. The transmitter is intended for mounting on an outside wall, on the north side where possible. The transmitter is connected over a 2-wire cable, which serves both as power supply and signal transmission. The reading of the measured signal is made over an external load resistance. Outdoor Temperature Sensor STO300 -50/50 Order Code 006920501 Part Number STO300 -50/50 System All Note for each of these outdoor sensors, find the Description, the Order Code, Part Number, and the System it works with for the iBAS (intelligent Building Automation System) Please note the difference in Weatherproof and Outdoor. I put a lot of these outdoor sensors in at a university in Texas, and always installed in places that were a little protected. I found that under porches, up under the eves and out of the sun, or along a loading dock out of the rain and ice gave me accurate readings. Swimming Pool: In the piping system of a swimming pool is a corrosive environment with steadily harmful and gradually destructive minerals and chlorine in the water which present a challenge finding sensors able to withstand for extended periods of time. Schneider Electric makes several immersion temperature sensors. Beginning on page 12 of the above HVAC Catalogue, there is a variety of immersion sensors for the different iBMS lines.  One example is the STP660 is a Temperature Sensor for the European market, and intended for immersion mounting in pipe or the circulating systems. The stainless steel probe is a good solution but remember,  if the sensor is to be installed in pool water that contains chlorine, the best bet is to use a stainless steel pocket. I suppose it all depends on if sensor is in pipe associated with the secondary pool side of the system or the heating side of the system. If the sensor head is in an area exposed to Chlorine, then there may be an issue.  Chlorine may attack the solder connections of the wired joints inside the sensor. In the old days products from Satchwell used to produce special sensors for such applications where the wire connections were varnished in order to prevent corrosion. I think at the end of the day, our sensor would have a similar life expectancy to other devices in the plant that were no designed for use in such corrosive atmospheres. Explosion proof sensors: Schneider Electric does not manufacture explosion proof sensors. We do not partner with another manufacturer who provides such sensors. The closest is an 3rd party explosion proof enclosure with one of our available sensors. Our sensors are designed for building installations and if in extreme environments, we suggest enclosures.  

Issue The majority of the Satchwell MicroNet and Satchnet product ranges is now re-branded to Schneider Electric. Product Line Satchwell MicroNet Environment IAC-420-F IAC-420-P IAC-440-F IAC-440-P MN350-LON MN450-LON MN550-LON MN650-LON MN50-TS-LON MN50-TSP-LON MNN-COM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM MNN_RTC M50_RTC MN-TK MN-VWIO-NCP MN-VWIO-SNP MN-VW100-UK MN-VW500-UK MN-VWP500-UK MN-VWP2K-UK MN-VWP10K-UK MN-VWP60K-UK Monitor Tool MicroNet View Cause The branding exercise provided some insightful information regarding sales volume. As a result, a number of products that were low or zero sales have been discontinued. Resolution Updated June 2019   The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- For more information on the re-branding of the Satchwell MicroNet product range, see PA-00145A - Satchwell MicroNet Range Rationalisation and Schneider Electric Re-branding. Old Part Number New Part Number IAC420-F IAC420-P MN350-LON MN350-NCP + MNL-C (LON card) MN450-LON MN450-NCP + MNL-C (LON card) MN550-LON MN550-XCOM + MNL-C (LON card) MN650-LON MN650-XCOM + MNL-C (LON card) MN50-TS-LON MN50-TSP-LON (Panel Mounted Only) MNN-COM MN550-XCOM or MN650-XCOM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM  

Issue Proper handling and preparation of existing .vsd files help eliminate the crashing and lockup of the Visio application. Product Line EcoStruxure Building Operation, TAC IA Series Environment Workplace Tech Editor EcoStruxure 1.9.x - 3.2.3 Workplace Tech 5.9.1 - 5.9.4 Visio 2013, Visio 2016 Note: This does not apply to Workplace Tech Editor EBO 2022 (and newer) and Workplace Tech 5.10.x Cause The product is affected by the version of Visio in use as well as the file size and unused objects in the drawing. Resolution When using Workplace Tech 5.9.x with Visio 2013 or 2016, the file has to be opened in "Compatibility Mode." DO NOT CONVERT. Illustration 1 While the .vsd file is open in Visio, not in Workplace Tech, use the "Reduce File Size" option and select the boxes in Illustrations 1&2. Illustration 2 In Visio 2016, after opening the "Inspect Diagram," (Illustration 3), select the first 3 boxes in the "Reduce File Size" option (Illustration 4). Illustration 3 Illustration 4 Save the file for use in the Workplace Tech Project or to be imported into your AS-P as a .vsd. Add the "cleaned" file to your project or import it to Workplace Tech Editor. Make sure the Visio 2013 or 2016 is at the most recent version and build. You can find this under the file/account/About Visio. If Version 1802 is available in your Microsoft Office update Channel, use it. Version 1801 was used in testing. For Visio 2013 Build 15.0.4971.1000 MSO 15.0.5007.1000 was tested (Illustration 5) Illustration 5

Issue Converting the Velocity Pressure measured by the pressure sensor to Flow velocity (CFM) Product Line Andover Continuum,TAC INET,TAC Vista Environment Air flow measurement / balancing Cause Requirement for converting the velocity pressure to flow velocity (CFM) Resolution To calculate Air Flow in Cubic Feet per Minute (CFM), determine the Flow Velocity in feet per minute, then multiply this figure by the Duct Cross Sectional Area. Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A)   Determining Flow Velocity The easiest way to determine Flow Velocity is to measure the Velocity Pressure in the duct with a Pitot Tube Assembly connected to a differential pressure sensor. The Pitot Tube Assembly includes a Static Pressure Probe and a Total Pressure Probe. A Total Pressure Probe, aligned into the airflow, senses the duct velocity pressure and the static pressure, which equals the total pressure. A Static Pressure Probe aligned at a right angle to the airflow senses only the static pressure. The difference between the total pressure reading and the static pressure reading is the Velocity Pressure. If you connect the Total Pressure Probe to the HIGH port on a differential pressure sensor and the Static Pressure Probe to the LOW port on the differential pressure sensor, then the sensor’s output will be the Velocity Pressure, as shown in the figures below. The Flow Velocity is then determined with the following equation: V = 4005 x Sqrt(ΔP) V = Flow Velocity in feet per minute. Sqrt() = Square root of the number in the parenthesis. ΔP = The Velocity Pressure measured by the pressure sensor Example: Measuring a Velocity Pressure of .75” W.C. equals a Flow Velocity of 3,468 Ft/Min. V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min   Determining Duct Cross Sectional Area After obtaining the Flow Velocity from the previous procedure, that figure is now multiplied by the Duct Cross Sectional Area to determine the Air Flow in CFM. There are two different equations for determining the Duct Cross Sectional Area, one for round ducts and one for square or rectangular ducts. The equation for a round duct is: A = π x r 2 A = Duct Cross Sectional Area π = 3.14159 r = radius of duct in feet The equation for square or rectangular ducts is: A = X x Y A = Duct Cross Sectional Area X = Duct height in feet Y = Duct width in feet. Example: An 18” diameter round duct has a Duct Cross Sectional Area of 1.77 Ft 2 A = π x r 2 or A = 3.14158 x .5625 18” diameter is 1.5 feet, therefore the radius is .75 feet • r 2 = 0.752 = 0.5265 • π = 3.14159 A = 3.14159 x 0.5625 = 1.77 Ft 2   Determining Air Flow in CFM After obtaining the Flow Velocity and the Duct Cross Sectional Area from the previous two procedures, the Air Flow in CFM is determined by multiplying the two: Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Example An 18” diameter round duct with a Velocity Pressure of .75” W.C. has an Air Flow of 6,128 CFM The Flow Velocity is 3,468 Ft/Min. V = 4005 x Sqrt(ΔP) V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min The Duct Cross Sectional Area is 1.65 Ft 2 A = π x r 2 π = 3.14159 • r 2 = 0.752 = 0.5625 Duct Cross Sectional Area (A) = 3.14159 x 0.5625 = 1.77 Ft 2 The Air Flow in CFM is 6,128 Ft 3 /Min Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Air Flow in CFM (Q) = 3,468 Ft/Min x 1.77 Ft2 = 6,128 CFM

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

Issue Cannot find manual service pin location Environment Schneider Electric SE76xx, SE73xx and SE72xx Viconics VT76xx, VT73xx, VT72xx Ready7 Commissioning Neuron ID Lonworks ID Service Pin message Cause The Service PIN is used to identify the device at commissioning. There is not a visible service pin button located on the Viconics device. Resolution A Service Pin will transmit the program ID and the Neuron ID (LonWorks Unique ID) contained in the device to the commissioning or service tool. The Status LED will blink when the device accepts the Service PIN command. VT7600 device - Press simultaneously the “Yes” button and the “No” button located on the keypad interface VT7300 and 7200 device - Pressing simultaneously the “Up” button and the “Down” button located on the keypad interface.       Additional Information on Viconics VT7600 series can me found in this Viconics Lon Integration Manual. Additional Information on Viconics VT7300 and VT7200 series can me found in this Viconics Lon Integration Manual.

Issue When running VisiSat 2.1 build 196 (200 or 201) a message is displayed - “Unable to Load the Schneider Electric CET Style DLL” and VisiSat fails to launch. Product Line Satchwell MicroNet Environment Windows (Windows, XP Professional, Windows 7, Windows Vista Ultimate) Microsoft Visio Cause .NET Framework 2.0 is not installed. Resolution Check that the version of VisiSat installed is either v2.1 196 or for SP1 build 200 or for SP2 build 201 on a computer running with a supported operating system and Microsoft’s Visio version.   MicroNet Software Datasheet   The suggested procedure to correct the “Unable to Load the Schneider Electric CET Style DLL” issue as follows: - Uninstall VisiSat Install .NET Framework 2.0 Install VisiSat 2.1 196, add service packs 1 and 2 files as required. Re-boot computer Run VisiSat. Links to VisiSat software and information:   The VisiSat main software can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=c93346a7-9d82-48e7-9b54-a866ac75bb71&title=VisiSat%202.1%20Build%20196%20-%20Software   VisiSat service pack 1 can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=fd2e9849-1ffe-4c10-b3a6-5f27bac91870&title=VisiSat%20Release%202.1.196%20Service%20Pack%201%20(2.1.200)%20-%20Software   VisiSat service pack 2 can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=839c09d2-400d-4434-8b1e-97f339545034&title=VisiSat%20Release%202.1.196%20Service%20Pack%202%20(2.1.201)%20-%20Software   VisiSat documentation can be downloaded from the link below: https://community.se.com/t5/Building-Automation-Knowledge/Download-latest-VisiSat-Data-Sheets-Engineering-Guides/ta-p/6110

Issue Need information on securing a building automation system. Environment Best practices Cause End user has requested assistance for their IT department to secure the building automation system. Resolution Click here to get a copy of Best_Practices_for_Securing_an+IBMS_WP.pdf,  a white paper written by Schneider' Electric's Buildings BU IT Security Group. This also located on the Download Center here

Issue Using the SIM-MTECH manual (F-26133-2) for reference, the Read/Write range of "Space Static Pressure Setpoint' on page A-45 displays as 0 to 5.0 "WC.  But the displayed setpoint does not match the value in the McQuay controller.  And, in general terms, any space static is never as high as 5.0 "WC. Environment SIM-MTECH Cause The manual contains a typo. Resolution The above-mentioned space static pressure setpoint range is actually -0.25 to +0.25 "WC. Keep this in mind as calculations are done to convert the unitless range of 0-250 to a value in "WC.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue "An unexpected error occurred" shown while downloading a LonWorks device through a Xenta Server Product Line TAC Vista Environment TAC Xenta Server (511, 527, 555, 701, 711, 721, 731, 913) TAC XBuilder TAC Vista Server Cause There are a couple of reasons that you can get this error message. One is that SSL 3.0 is not enabled in Internet Options for the Windows user running TAC Vista Server. This will keep Vista Server from being able to download a Xenta controller using a Xenta Server.  It will also not let you download and XBuilder project to the Xenta Server, and you can not connect to the browser of the Xenta Server using Internet Explorer. The other reason could be, that while running Vista Server as a service, the Windows account running the service is Local System and that this account does not have SSL 3.0 enabled. This could also occur if you have enabled "System cryptology: Use FIPS compliant algorithms for encrypting, hashing and signing" in the local policy setting. Resolution Enabling SSL 3.0 Go to Control Panel and open Internet Options. Choose the Advanced tab and scroll to the bottom of the Settings list. Near the bottom you will see Use SSL 3.0.  Make sure the Use SSL 3.0 box is checked. Configuring the Windows account running TAC Vista Server Download the TAC Vista Run Mode tool and run it. Under the Service Logon section choose Local User for the Logon Type, select or write the Windows user name and password. It has to be the account you are currently logged in with, or another user having enabled SSL 3.0 and has administration rights. Restart the service.   Check the local security policy for FIPS Open Control Panel - Administrative Tools -Local Security Policy (or type secpol.msc in Start-->run) Go to Local Policies-Security Options Find System cryptology: Use FIPS compliant algorithms for encrypting, hashing and signing Change to disable, apply-OK Restart XBuilder

Issue How to control an output with one or more inputs. Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure how to program one or more inputs to directly control an output. Input Control Output Resolution The below guide details how to use an Input to activate an Output on Security Expert and SP-C-WEB systems. An output can be assigned to the Input Type and to the Input allowing many to one and one to many configurations.   In order for an Input to activate an Output it needs two things: To be inside an always armed area - This can be an Automation/Dummy area with its only purpose being to activate the output. To have an Input Type that tells it to activate an Output   Single/Multiple Input Activating the same Output If one or more inputs are required to activate the same output, this output can be defined by the input type. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Set the Control Output to the required output Under Options 2 enable the required control options for your scenario e.g. to have the output follow the input exactly enable Activate Control Output on Alarm and Deactivate Control Output on Restore. To have the output activate for a time simply enable Activate Control Output on Alarm and set the Activation Time under the General tab of the Input Type Menu (Control Output Time) For more details on the option see The difference between using "Control Output" and "Input Control Output" Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following: Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Check for any related health status messages that need to be resolved Arm both portions of the Area Activate the Input to confirm Output Activates   Multiple Inputs Activating Different Outputs When multiple inputs are required to activate different outputs, one input type can be used and the outputs can be defined at each input. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Under 'Options 3' enable the required control options for your scenario. e.g. to have the output follow the input exactly enable Activate Input Control Output on Alarm and Deactivate Input Control Output on Restore. To have the output activate for a time simply enable Activate Input Control Output on Alarm and set the Activation Time at the Output itself For more details on the option see The difference between using "Control Output" and "Input Control Output" Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following Set the Control Output to the appropriate Output Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Arm both portions of the Area Activate the Input to confirm Output Activates

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need to replace an AVUE, AVUX or AVUM Mark 5 Actuator Product Line Field Devices Environment AVUE5305 AVUE5355 AVUE5304 AVUE5354 AVUX5202 AVUM5601 Cause Need to find a replacement for the obsolete AVUE, AVUX or AVUM Mark 5 actuator, that will allow the valve to be retained. Resolution The AVU* Mark 5 range of actuators can be replaced from the MZ300S range. AVUE5305 replace with MZ300S-24M AVUE5355 replace with MZ300S-24M AVUE5304 replace with MZ300S-24M AVUE5354 replace with MZ300S-24M AVUX5202 replace with MZ300S-24F AVUM5601 replace with MZ300S-230F The AVUE, AVUX, AVUM Mk 5 Datasheet is attached   MZ300S Specification sheet   MZ300S-24M Installation Instructions MZ300S-24F Installation Instructions   MZ300S-230F Installation Instructions

Issue How to connect a 4 wire PT100 or PT1000 sensor to a 3-wire RTD input. Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch RTD Cause Some PT100/PT1000 sensors have only 3 terminals to connect to. Resolution The wires to the sensor are often color marked in pair, like two red cables and two white cables. As we only have 3 terminals to connect to, the solution is to only connect 3 of the cables, and not connect the 4th cable.   As the RTD device also measure the resistance of the cables, to make a correct temperature reading, it is important that all three wires used do have the same length and resistance. Therefore, the fourth wire should NOT be connected in parallel, it has to be un-connected.

Issue Procedures and processes to secure I/A Series G3 (AX) Systems Environment I/A Series Niagara G3 (AX) Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara G3 system. While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara G3 system more secure by carefully configuring and using.  Passwords Accounts and Permissions Authentication TLS and Certificate Management JACE-8000 Settings Additional Settings Please note that while all of these steps should be taken to protect your I/A Series Niagara G3 system, they do not constitute a magic formula.  Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn't mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it.  Note: Schneider Electric strongly recommends upgrading to the latest I/A Series G3 version 3.8 maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build included documentation to understand the behavioral impacts of the security enhancements. Download the Niagara AX Hardening Guide for more details.

Issue General questions and best practices for RS-485 protocol including cable length and terminating resistors Product Line Andover Continuum, EcoStruxure Building Operation Environment MSTP Cause Understanding best practices for installing, cabling, and terminating RS-485 networks can avoid a lot of problems with communication and hours of troubleshooting communication problems. Resolution MS/TP MS/TP stands for Master Slave Token Passing. Each device on the link is considered the master when it has the token. If it does not have immediate need to use the token, it is required to pass the token along to the next device. This is the token passing part. All devices on the link which do not currently have the token are regarded as slaves, and are expected to listen to any messages the current master may have for it. Because all devices take turns being master, the link is effectively peer to peer. Electrically, MS/TP adheres to standard RS-485, physically wired using two-conductor shielded twisted pair cable. RS-485 Cable Specifications Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and <22 pF/ft between the conductor connected to ground and the next conductor. Topology Daisy chain bus topology. Star topology can be achieved using Infilink/B-Link repeaters. Maximum Cable Length Cable lengths of up to 4000 ft (1220m) daisy chained from controller to controller on one arm of a star are supported. After 4000 ft (1220m), a signal repeater (b-Link) is required to add more nodes to the network or further extend the cabling. Using a b-Link fiber repeater allows you to extend the length of RS-485 with fiber optic cable, recommended for running cable between buildings and through noisy environments. Maximum Number of Devices TAC's MS/TP RS-485 supports a maximum of 127 nodes overall. Each controller represents a single node on the network. RS-485 Termination The MS/TP field bus requires a 120 ohm terminator resistor at both ends of a daisy chain segment. The following diagram illustrates the connection of the terminator: Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.