Building Automation Knowledge Base

Issue No official internet download available unless you have user name and password access to Schneider Electric websites. Product Line Satchwell MicroNet Environment VisiSat Engineering Guide  Installation and User Guide 1.2 2.1  Cause Not available for download online Resolution Further information regarding this object can be found in the VisiSat help file and engineering guide. VisiSat V1.2 Engineering Guide This document provides details for IAC 400, IAC 420, IAC 600 and IAC Touchscreen configuration. VisiSat V2.1 (185) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 (196) Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 Installation and User's Guide VisiSat V2.1 data sheet VisiSat V2.1 Release note Related Articles: MicroNet 100 series controller MLi's and Data sheets MicroNet 50 series controller MLi's and Data sheets Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue Satchwell MZF 3-Port Flanged Valve Body requires replacement. Product Line Field Devices Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MZF MZF3729 MZF3779 MZF3854 MZF3904 MZF3958 Cause Obsolescence of Satchwell MZF 3-Port Flanged Valve Body Resolution A number of alternative Schneider Electric 3-Port Flanged Valve Bodies are available to replace existing Satchwell MZF 3-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E VG311F 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L9TVG Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the VG311F 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E V321 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the V321 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body Similarly, the centre line to bottom of third port dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body As a result alterations to the pipework connected to the MZF 3-Port Flanged Valve Body will be required. Details of the Satchwell MZF 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric VG311F 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric V321 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric L9TVG Linkage Kit may be viewed here. Details of the Schneider Electric L8TV Linkage Kit may be viewed here. 

Issue Unable to discover BACnet devices from a BACnet interface, discover broadcast address and/or devices are offline after changing IP Address on AS or ES. Bacnet devices are offline after a power cycle or loss of IP connection at the AS or ES. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operations site using devices configured with BACnet Cause Broadcasting on wrong network from either the Automation Server or the Enterprise Server can be a problem. In the example below an AS is broadcasting for a BACnet device (in this case a MNB Controller). In the IP Network for the BACnet Interface, check your settings for Broadcast Address. The key is to ensure your BACnet broadcast address is in the correct range.   In this first screen capture, we have a BACnet network interface using the IP Network with a red failure to communicate indicator on the MNB. In this example, the broadcast is on 192.168.1.255 Resolution The computer being used as well as the BACnet devices we want to discover and use are in the following IP network and settings: Changing the broadcast address to match what the BACnet network is using resolves the issue (BBMD and BBDT from Enterprise Server or Automation Server). Lastly, choose to discover devices For subnet calculations and how to setup your subnet addresses, several recommended calculator are SuperNet Online or SubnetMask a downloadable program from Solar Winds.  When the IP Network broadcast address is set incorrectly, a Wireshark capture may reveal that no WHO-IS message is sent out from the SmartStruxure server when a device discovery is attempted. When in doubt as to whether the 'IP Broadcast Address' is correct, a simple test is to set the IP Broadcast address to 255.255.255.255, doing so will instruct the SmartStruxure server to broadcast on ALL subnets, if the problem was caused by an incorrect broadcast address it will be resolved but care must be taken not to leave the default address set to 255.255.255.255 as this will cause unnecessary traffic on all sub-nets, instead, review your calculations for what the appropriate broadcast address should be and set it appropriately. Key Concept: The AS will retain the Broadcast address, and if moved to a new Subnet, the old Broadcast address must be updated. One can do either of the following:  Edit the IP Broadcast Address Setting  Delete the BACnet Interface and recreate in the new Subnet

Issue Communication of BACnet Protocol across different subnets Can see BCX 4040 on Infinity side but will not learn in on the BACnet side. Product Line Andover Continuum Environment BCX (4000, 4040) B4920 Continuum Workstation Cause BBMD configuration Resolution Typical Multi-Network BBMD Setup 1 In this Scenario, the controllers in Remote Building A cannot send or receive BACnet broadcast data from controllers or the Workstation on the Main Building Network.   Solution 1: Configure Building A BCX1-R as a BBMD, and Cyberstation as a BBMD  Typical Multi-Network BBMD Setup 2 In this Scenario, the controllers in Remote Building A cannot send or receive BACnet broadcast data from controllers or the Workstation on the Main Building Network. Solution 2: Configure Building A BCX1-R as a BBMD, and Main Building BCX1-CR as a BBMD Workstation BBMD configuration BACnetPreferences Located in the lower right hand side of the screen in the icon tray right click on the Continuum icon and select BACnet Preferences NOTE: After Workstation configuration and Bacnet Preferences have changed the Workstation will need to be restarted.    BCX BBMD Configuration Enable the BBMD on the configuration page Save changes and submit to controller After controller restarts select the BBMD link on the left side of the web configuration page. Enter the IP address for the BBMD device on the other side of the router After configuration of BBMD’s on each side of the subnet you will be able to receive and broadcast BACnet messages across an IP router. THE GOLDEN RULE HERE IS ONLY ONE BBMD PER SUBNET. Otherwise you’ll create a broadcast storm that that will not be good for the network performance and could possibly cause controllers to go offline. After successful creation of BBMD’s on each side of the router, go into Continuum explorer and perform a “Find new bacnet devices”from right click on the root.

Issue Is the I2/B3 865/866/885 UL 916 Listed Environment  I2/B3 865/866/885 Cause  I2/B3 865/866/885 UL 916 Listed Resolution Yes the  I2/B3 865/866/885 are UL 916 Listed Download the complete list of UL916 listed products.

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

Issue The display on the smart sensor module (LCD1/LED1) is blank. Product Line Andover Continuum Environment CyberStation B3 devices/i2 devices with Smart Sensor port. Cause LCDDisplay/LEDDisplay element #2 has a value of 0 which turns off the display The host controller is not sending power to the SPWR port It could be a newer version of the smart sensor, see i28xx-V & i28xx-V-WL Controller v3.501037 - Release Notes Resolution Set LCDDisplay/LEDDisplay[2] to a valid display format value. (see Smart Sensor Installation and User Guide) Measure the voltage between return and SPWR and make sure it is 8.4 volts DC, if the voltage is not correct disconnect the Smart Sensor and measure again, if the second measurement is correct then the Smart Sensor may need to be replaced, otherwise the host controller may have to be replaced.

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue Using access card types not natively supported by Continuum system Product Line Andover Continuum Environment CyberStation CX9900/9940 CX9702 CX9680 ACX5740/5720 ACX701 ACX781 Cause Continuum has built in support for the most widely used Wiegand card types, occasionally a site might be using a card type for which Continuum has not built in support. In such cases the system must be configured using custom card functionality. Resolution Setting Up a Custom Wiegand Format A custom format must be used when the card format is not one of the standard pre-defined formats. Only one custom format can be used in an ACX7xx controller and NC1(CX99xx), NC2(CX968x) using AC1 modules, up to four custom formats can be used with the ACX57xx and NC1/NC2 using AC1Plus modules. In each ACX700 and ACX780/781, NC1, NC2, ACX57xx create an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 22 entries to the point. If using more than one custom card definitions create InfinityNumeric points called AccessFormat2, AccessFormat3 and AccessFormat4 Create the following InfinityProgram in each controller. The program should be type FallThru, and AutoStart. This program basically saves you from having to set each array value individually for each controller. The program, once created, can be copied to all other access controllers that need it. In the following example the AccessFormat array is setup to allow the system to read the HID Corporate 1000, 35 bit card. Program Name: SetCustCrdArray FlowType: FallThru AutoStart: True Code: Set AccessFormat[1] to 35 ‘overall number of bits Set AccessFormat[2] to 0 ‘control mask Set AccessFormat[3] to 0 ‘ manufacturer’s code Set AccessFormat[4] to 0 ‘ start bit of man. Code (first bit is 0, not 1) Set AccessFormat[5] to 0 ‘ end bit of man. code Set AccessFormat[6] to 2 ‘ start bit of site code (NOTE: If the card has no site code set this field to 0) Set AccessFormat[7] to 13 ‘ end bit of site code (NOTE: If the card has no site code set this field to 0) Set AccessFormat[8] to 14 ‘ start bit of card number Set AccessFormat[9] to 33 ‘ end bit of card number Set AccessFormat[10] to 0 ‘ odd parity mask, first 16 bits Set AccessFormat[11] to 0 ‘ odd parity, next 16 Set AccessFormat[12] to 0 ‘ odd parity, next 16 Set AccessFormat[13] to 0 ‘ odd parity, next 16 Set AccessFormat[14] to 0 ‘ even parity, first 16 Set AccessFormat[15] to 0 ‘ even parity, next 16 Set AccessFormat[16] to 0 ‘ even parity, next 16 Set AccessFormat[17] to 0 ‘ even parity, next 16 Set AccessFormat[18] to 0 ‘ card number multiplier Set AccessFormat[19] to 0 ‘ card number divisor Set AccessFormat[20] to 0 ‘ start bit of issue code Set AccessFormat[21] to 0 ‘ end bit of issue code Set AccessFormat[22] to 0 ‘ decimal shift of issue code​   In each Door Configuration, select the Custom Wiegand card type. Other card types may also be selected. For each Personnel, select the Custom Wiegand card type, and enter the correct card number and site code. If the card is not working, check the Event Log and determine the cause. For Invalid Card Parity errors, set all the parity masks to 0 and try again. For proximity cards, the parity check may be eliminated with little consequence. NOTE: In controllers that support the HID Corporate 1000, 35 bit card natively (NC2 – CX968x and ACX2 – ACX57xx) the AccessFormat numeric is internally used by the system, any other custom card definitions must use AccessFormat2 – AccessFormat4 Control mask Some Wiegand cards are encoded with the bits in one or more fields reversed and/or complemented. It is then necessary to operate on the fields when decoding the data in order to obtain the correct data. In the AccessFormat array a control field is provided to configure the system so that the bits in a field in the access card data can be reversed and/or complemented. The control mask is located at AccessFormat[2] Control Mask The bits of the control mask are used by the parsing routine in the controller to reverse or complement selected fields. Setting the appropriate bit to a 1 will enable the special action: Example: To reverse the bits in the site code field set AccessFormat[2] = 8 Parity mask calculation The table below shows the card format information provided by the manufacturer of a 32 bit Wiegand card. From the information provided by the manufacturer we can deduct the flowing about the format of the data on the card: The card data is comprised of the following 3 fields A = Customer Code B = Facility Code C = Card Number Bits 0 through 16 make up the even parity field. (The ‘X’ indicates that the bit is part of the even parity field) Bits 15 through 31 make up the odd parity field. Note the overlap in the fields (bits 15 and 16 are members of both the even and odd parity fields), this is common as the fields are arbitrarily assigned by the card manufacturers. Armed with the information provided by the manufactures we can calculate the parity mask which Continuum will need to use in order to perform the necessary parity check upon receipt of the card data transmitted by the card reader. First, calculate the EVEN parity mask. To better illustrate how the calculation is done we have added a new row to our table, in this row we are going to enter the even parity mask as a binary number. What we do is write a 1 (one) in each bit that is a member of the even parity field and a 0 (zero) for bits that are not part of the even parity field. The second step is to divide the bits that make up the field into groups of 4 which will make it easier to convert the binary number in the previous row to a hexadecimal number. The even parity mask for this card is 0xFFFF8000 It should now be obvious how Continuum uses the mask when checking for even parity. Upon receipt of the card data transmitted from the reader, Continuum applies the mask to the full 32 bit stream of data received, (a logical AND operation is performed) the mask acts like a filer that allows only the set bits in the even parity field to pass through, now all Continuum has to do is count the bits that passed through the filter and make sure the count is an even number, if the count is not an even number Continuum sends a parity error. The Odd parity mask is calculated using the same procedure. Here is an example for the calculation of the parity masks for a 35 bit card A = Company ID Code B = Card Number P= EVEN PARITY Even Parity Mask 0x76DB (30427) 0x6DB6 (28086) 0xC000 (49152) 0x0000 (0) P = ODD PARITY Odd Parity Mask 0x6DB6 (28086) 0xDB6D (56173) 0xA000 (40960) 0x0000 (0) After calculating the parity masks you enter the decimal numbers into the appropriate fields in the AccessFormat array. S = Site Code C = Card Number P= EVEN PARITY Even Parity Mask 0xFFFF (65535) 0XE000 (57344) 0x0000 (0) 0x0000 (0) P = ODD PARITY Odd Parity Mask 0xFFFF (65535) 0xFFFF (65535) 0xF000 (61440) 0x0000 (0) IMPORTANT: If a custom card is configured with a bit count that is the same as the bit count of one of the cards that are supported natively, the parity masks MUST be entered in the AccessFormat array in order for the controller to be able to parse the custom card correctly, if not parity masks information is entered, the controller will generate an 'Invalid attempt, bad parity' event when the custom card is presented at the reader.

Issue How to add Web Service and create Simple XML Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add XML files and how to add to a project or site How to create values from the XML Files added How to make a graphic that uses the values from XML Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: Are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Weather for a particular location data using Simple XML: Select New > Interface > Web Service > Simple XML Specify the URL for this data (to find the weather for your area, Google XML data Make changes to polling, alarm, retry interval Choose Create Now you can Create a value from that Simple XML Web Service by highlighting and select New > Value > and type of value. Select Analog for temperature, String Value for wind direction and so forth. One can add as many of the values as desired. The Simple XML List View would look like the below screen capture. Lastly for Simple XML Web Service a graphic is created and the values which come from the XML Web Service are place on the page. Also check out the SmartStruxure - Web Services - Simple XML Interface Quick-Help video on the Exchange.

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 Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

Issue Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

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 PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue How and when are Modbus points polled? Product Line EcoStruxure Building Operation Environment Building Operations Enterprise Server Building Operation Automation Server Cause Need to understand the Modbus poll mechanism Resolution Consult the 'Modbus Deep Technical Reference' chapter of EcoStruxure Technical Reference Guide Or use WebHelp to find information on the Modbus Poll Manager, which manages all polling of the points/data and devices, and the Poll List which contains all the current subscriptions (eg. data being referenced within Programs, Listviews, Graphics, Logging, etc) These mechanisms isolate the Modbus Polling from programs and graphics. Note: For each network, the poll manager operates with a poll list and a poll task. If a Modbus Object value is only required for logging purposes, then the  "Requested poll interval" is set to a high number (typically 2,147,483,647 ms) This means the object values are not currently being polled. When the time arrives for the log value to be collected, the "Requested poll interval" is set to 1000ms, until the value is collected, at which point it reverts to this higher number.