Building Automation Knowledge Base

Issue Device ID / Device Instance of SE8000 series BACnet controllers Duplicate BACnet Network Address alarms How to have 254 SSL Room Controllers on an Automation Server (AS) as shown in the SBO Automation Server and SE7000 and SE8000 - Architectural Guidelines Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Room Controller BACnet Cause There can be confusion from the difference in naming between SmartStruxure Lite(SSL) Room Controller(RC), SmartStruxure Building Operation and even Niagara(JACE). Bacnet Instance number in SSL = Object ID in SmartStruxure Building Operation COM Address in SSL = MAC Address in SmartStruxure Building Operation Resolution On the AS, considered is the Object ID of the two Comm Ports (as with all object IDs) they need to be unique across the system. A common ID is 1001 for CommA and 1002 for CommB of the first AS, then on the second AS CommA 2001, CommB 2002 etc. The key thing with BACnet is that every object (point, device, program, port etc) must have a unique Object ID. The SE8000 uses the Com Address referred to as the BACnet MAC Address in the AS. This, as detailed in BACnet COM Address of Room Controller SE7000 and SE8000, is the address range on just that one MS/TP bus. 1 – 127 are valid addresses, the AS (or bus master) will be address 0. If a second AS is on the same system this could use 83001 – 83127 for CommA, 84001 – 84127 CommB etc. Also SE8000 uses the BACnet Instance number which is called the BACnet Object ID in the AS. (This is the ID which must be unique across the whole system) So if you have the 2 ports used on one AS all 254 devices must have unique ID’s. When changing the Comm address in the SSL SE8000 to any value between 1 and 127, the Instance number will change as well. For example Comm address 9 would result in an Instance number of 83009. These will cover 127 stats that will go on CommA, and result in Instance numbers between 83001 and 83127. Any value above 127 will keep the Instance number unchanged. For CommB however, a site would need to change the Instance number manually. For example the first RC connected to CommB would be the 128th and would default to address 83127. So it is required to manually change the Instance number to 1083001 (up to 1083127). This defines unique Comm Addresses for ComB on the remaining 127 RC. When using an Automation Server (AS) you can find the Object ID and MAC address for devices on MSTP by using WorkStation and going to AS > System > Hardware > BACnet devices > Network_xxxx. A screen shot is below with the added columns Status, System Status, Object ID, and MAC address. In this first example, b3 controllers use the Object ID or Device ID of their serial numbers so each b3 is unique across the network. B3 controllers with serial numbers greater than 4194302 (the maximum allowed Object ID in BACnet) will be assigned a Device Object ID using a hashing algorithm to ensure it is unique. From an SE8000 series RC, BACnet network set-up screen shows when BACnet is detected in models. Select desired parameter and use up or down arrow to set parameter to desired value. The default BACnet instance number is generated by the model number and COM address of the controller. For example, The instance number of a SE8300A5B00 with a COM address of 57 is generated as "83057." The default instance number appears first. To change the instance number, use number pad and press Accept and Save. Below is a screenshot of the WorkStation logged into an AS, with the BACnet Interface and the MSTP network. The added columns show the Object ID and MAC address. Below is a screen shot of the WorkStation logged into the AS, with the System > Hardware Devices > Network_xxxx. The added columns show the Object ID and MAC address.  The screen shot below is the AS > BACnet Interface > MSTP Network > Configuration Settings.

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.

Issue How to configure Custom 37-Bit as well as Infinity 37-Bit Card Format Product Line Access Expert Environment Access Expert Server 2012 and Above Version 2 Version 3 Hosted  Premise Cause When configuring Custom 37-Bit as well as Infinity 37-Bit Card Formats, the settings are different based on the Facility Code, Card Length and Card Formats. The HEX code generated in Live Monitoring can be deciphered to get the correct set of values required to make this work for your application. If you are unable to do so, please contact PSS and open a ticket so that they can help. Resolution The following settings on the screen shots show how to configure Custom, HID Formats and Infinity 37-Bit Formats, please pay attention to the one that will work for your specific application: Open and log on to the respective Access Expert Instance Select the tab Access Configuration to create a new Card Format Name the format accordingly in the description field, this can be used for Infinity 37-Bit if so desired Add the card range by clicking on the page Icon on the Number Range There is a Standard, HID Managed 37-Bit (not Infinity 37) in the drop down in the Card Format Presets This can be used by default but if you have a Custom 37-Bit Format and the Facility Code is known, however the Start Bit and Length will be different. An Infinity 3 Bit Format will use the Parity Bits Create the new format per the screen shots and configure accordingly. Once complete, click on Save or Save and Close, reboot the controller.

Issue How to show raw card data of a badged card in Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Format Cause Need to configure a custom card format and need to see the raw bit string to determine this. Resolution Displaying a cards raw data is a function that can be set in the Reader expander. 1. Confirm that the Display Card Data When Invalid option is enabled on the Reader tab under Misc Options. Misc options Display Card Detail When Invalid: When enabled, the reader expander will display the actual card data received from the reader when the card number is not known. This can be used to interface with custom third party applications that require their own processing of card information. This option is enabled by default and can be used to add card data to a user when operating Security Expert. When disabled the reader will display the card number not found message. 2. Next, set the Reader format on the Reader tab under Configuration to Any bit (raw). any bit raw 3. Now when badging a card at this reader port it should populate two events. One for the Card Number Raw Data and another for the Facility Code Raw Data.   Example: Read Card Number Raw Data: 46160846 Read Facility Code Raw Data: 436207616 Put the facility code into a Programmer Calculator to convert from Decimal to Binary. This is a 32-bit number. 00011010000000000000000000000000 Of the 32 bit number take the first 8 Binary digits (in the example this is 0001 1010) and convert this back to decimal. 00011010 bin = 26 dec What you should see in the decimal field is the bit length the card uses. Now in the Reader Format, it’s an experiment to find out which of the Bit options would correspond to the cards. (In the example above you would need to look through the 26 bit options.)

Issue How to add b3 devices to EcoStruxure. Product Line EcoStruxure Building Operation Environment Building Operation Workstation b3 BACnet Cause List the methods of adding b3 devices to EcoStruxure Building Operation Resolution The following information can be found in the EcoStruxure Building Operation - Technical Reference Guide. Use the guide relevant to the release of EBO installed.   Discovering b3 BACnet Devices with the Device Discovery View Using the Device Discovery view to search deployed Automation Servers for b3 BACnet devices. For more information, see section "b3 BACnet Device Overview". To discover b3 BACnet devices with the Device Discovery view In WorkStation, click the Device Discovery view. In the System Tree pane, click the Automation Server to be searched. In Select device type, click on BACnet devices. Select the b3 BACnet device you want in the Device result pane. Map a device by dragging that device from the Device result area and dropping it in the System Tree pane. When prompted, copy the device only or copy the device and all of its children.   Learning b3 BACnet Devices b3 BACnet devices van be learned and to automatically assign the node IDs and initiate communication with devices on the MS/TP network. Tip: It is possible to learn b3 devices when the b3 devices and the Automation Server functioning as the BACnet interface are connected and online. If the b3 devices are not physically connected to the network, it is also possible to manually create and configure the devices offline in Workstation. For more information, see section  "b3 BACnet Devices. To learn b3 BACnet devices In WorkStation, in the System Tree pane, select the MSTP Network In WorkStation, on the Actions menu, click b3 devices and Learn When the b3 BACnet devices are learned, click Close If necessary, perform a download operation to eliminate any old points and programs stored on the b3 BACnet device.

Issue TimescaleDB Installation Errors - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% - ERROR: could not get 'pg_config --pkglindir' : exit status 1 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.x External Log Storage TimescaleDB (third party)  Cause Missing environment variable paths in Windows is detailed in section 9.4.4 PostgreSQL and TimescaleDB Installation in the EcoStruxure Building Operation 3.0.1 Release Notes. Assistance in how to add these variables is described below. Resolution Using the EBO External Log Storage Installer tool available on the Community, there is no need to make any manual configuration, as the tool executes the installation without the need for e.g. environment variables. Alternatively, you can manually set these as detailed below: You can either view a video showing how it is done:  or follow the instruction below view, add and modify the environment variables from the Control Panel as follows:  In the Control Panel select System and Security Select System Select Advanced system settings Select Environment Variables. In System variables, highlight Path and click Edit. For the error - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% Add the New path 'C:\Program Files\PostgreSQL\11\bin' to the environment variable. For the error -ERROR: could not get 'pg_config --pkglindir' : exit status 1 Add the New path 'C:\Program Files\PostgreSQL\11\lib' to the environment variable. You should see something similar to the following after TimescaleDB has been successfully installed.

Issue What are the IO wiring requirements for the IO Modules? Product Line EcoStruxure Building Operation Environment Analogue, Digital, Input, Output Cables UI-16, DI-16, AO-8-x, AO-8-V-x UI-8, DO b3 Inputs Cause The existing documentation does not specify the exact cable types to be used. Resolution Different types of sensors can be used that come from different legacy systems, so cable types specified for the legacy systems will be appropriate for the same sensor type being connected to an Automation Server I/O module. If you are using Xenta sensors with the 1.8K Ohm thermistors you should use the wiring rules as per the Xenta documentation. Of if you use Continuum 10K Ohm sensors, use the Continuum IO wiring rules etc. Some suitable cables for most Analogue and Digital input, also analogue output applications are: 18 AWG (16 x 30) 0.823 mm2 - single pair screened e.g. Belden 8760 22 AWG (7 x 30) 0.325mm2 - single pair screened e.g. Belden 8761 The maximum distances that these cable can be run are dependent on the input requirements, for Temperature inputs this will depend on the temperature range and accuracy required. For examples of of these cable distances see links below: Continuum 10K Ohm sensors (also applicable for b3 controller inputs). Xenta 1.8K Ohm sensors For digital outputs cable should be used with appropriate size (current rating) to the loads being switched. It is recommended to use screened cables and also ensure correct connections for analogue inputs as detailed in How to wire an Analog input to an IO Module.

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 If the passphrase is incorrect when trying to install a station .bog, the following error message can appear; Transfer failed. com.tridium.platform.daemon.DaemonResponseException: Request to platform daemon at (stationName) failed: bad return code to commit file instance at com.tridium.platform.daemon.DaemonFileUtil.transfer(DaemonFileUtil.java:661) at com.tridium.install.InstallScenario.commit(InstallScenario.java:1444) at com.tridium.platDaemon.ui.stationtransfer.FinalStep.run(FinalStep.java:341) at java.lang.Thread.run(Thread.java:750) Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause The .bog has not been properly placed in the User Home / Stations for copying into the device or the passphrase is not known. Resolution Always use the Station Copier to install the .bog from the User Home / Stations path If the error message appears, open Workbench and navigate to the "Stations" folder under the "User Home" Expand the station you are attempting to install Double-click the .bog (1) and locate the "Bog File Protection" icon at the top of the page (2) Select the (1) "Force the File to start..." radio button and (2) Update.  Note the information regarding existing passwords. If the message "Cannot display page" occurs when you double click the .bog, open the "Details" and look for missing modules "Cannot load module '......=.....'. Any missing modules will need to be available on the Jace or ES before attempting the force start operation.  

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue “IP_ADD_MEMBERSHIP failed” appears in the Application Director output during reboot of the Jace and in the Station Discovery on the Niagara Network after a failed discovery attempt Product Line TAC IA Series Environment ENC 520, 410, Jace 6E, 645, 700, 8000 controllers using G3/AX. The second Ethernet interface only applies to the Jace 6E, 700, 645 and 8000 Cause Incorrect or no default gateway assigned in the TCP/IP Configuration or Interface 2 is enabled and set for DCHP with no DHCP server available to that interface. See the notes on the illustration for possible configuration faults. Resolution Make certain you have a valid IPV4 or IPV6 (schema dependent) Gateway entered for the Interface 1 IP configurations. If set to DHCP, ensure there is a DCHP server available on the interface. Disable all unused interfaces and IPV6 if not applicable. If there are problems accessing or configuring the interfaces, you may need to use the System Shell of the ENC/Jace and correct the configurations there. Need to correct invalid IP address or subnet mask entered into an ENC or JACE

Issue What is pneumatic actuator spring range shift and how can it be eliminated? Product Line Field Devices Environment Pneumatic Actuator Cause Spring range shift is an inherent feature of all spring return pneumatic actuators without positive positioners. The nominal published spring range of a pneumatic actuator without a positive positioner is the air pressure required to fully stroke the actuator WITH NO EXTERNAL LOAD. In the extend direction against an opposing load as provided by a damper or a valve, the supply air pressure must be increased above the spring range of the actuator to overcome the spring and the opposing force. In the retract direction against an opposing load as provided by a damper or a valve, the supply air pressure must be decreased below the spring range of the actuator so that the spring can overcome the air pressure and the opposing force. Under constant load conditions, the range of the actuator is offset by the amount of air pressure required to provide close-off of the damper or the valve. Resolution When is "Spring Range Shift" a concern? It is a concern when two or more pneumatic controlled devices should be sequenced from one pneumatic signal without an overlap. An example would be a normally open heating valve and a normally closed cooling valve being sequenced from a direct acting thermostat, In this example the spring range of the normally open valve will shift upward and the normally closed valve will shift downward which means the two valves may overlap. Another area of concern is that pneumatic control signal provides proper pressure span to operate the control device and provide "tight" close-off of damper or valve. Examples of limited pressure change would be: pneumatic controllers maximum output which is limited by main air pressure; the low pressure output capability of a pneumatic controller; and electronic to pressure transducer which can have a limited output such as 3 to 15 psig.   What can be done to overcome "Spring Range Shift" when sequencing devices? Sequencing can be accomplished in a pneumatic system by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment (2378-501) or controllers with separate outputs for each actuator. Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning. This is the ideal way to provide precision sequencing, since variable loading on the actuator will not effect the sequencing. Biased start ratio relays may be used to provide a method of sequencing by amplifying or shifting the pneumatic signal. For applications involving sequencing a pressure to electric (P.E.) switch with a pneumatic actuator, the P.E. can often be adjusted to operate outside the operating range of the actuator. Sometimes larger actuators will help the sequencing problem. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper and therefore reduces control signal change required to control the actuator. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, adjusting the start points can help prevent sequencing problems. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Sequencing problems can be eliminated by providing controllers with separate outputs for each actuator and do the sequencing in the controller. What can be done to increase the close-off of a damper or valve actuator due to limited or insufficient pneumatic control pressure to the control device? Proper control and close-off of the control device can be accomplished by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment ( 2378-501). Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning (0 to main air pressure to the actuator). Biased start ratio relay provide a method of amplifying or shifting the pneumatic signal. Selecting larger actuators will increase close-off pressure. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, proper adjustment of the start points will increase close-off. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Provide electronic to pneumatic transducers with sufficient input span to obtain maximum or sufficient pneumatic output.

Issue How to log on to CX9900 controller for commissioning or configuring IP settings. Product Line Andover Continuum Environment HyperTerminal CX9900 CX9940 CX9200 CX9400 Cause First generation Continuum controllers do not support web page configuration and must be configured using a terminal emulation program such as HyperTerminal. Resolution Configure HyperTerminal for 9600 baud (or baud that matches default baud configuration for the comm port), 8 data bits, no parity, no flow control. Connect cable to comm3 (or another port configured for autoset) on controller (for information on cable pinout please see PinOuts for the RS-232 Connection of the older 1st Generation CX controllers) On the NetController make sure RS232 is selected, use the MODEM/RS232 override switch to de-select the modem if necessary. Run HyperTerminal and type "window" to have the controller display the log on window Default user/password is acc/acc

Issue Xenta OP menu items: Status, Sub menu, Week chart, Holiday chart, Alarm, Access Code, Edit Access Code, Date and Time, Daylight Saving have defined Access Levels: Low Level Medium Level High Level Accessing the medium or high-level menu items requires a password. What is the default password and how can they be changed? What if the passwords have been lost? Product Line TAC Vista Environment Menta Xenta Controllers Xenta OP Cause Accessing the medium or high-level menu items requires a password. Resolution The default password for accessing medium level menu items is: 1111 The default password for accessing high-level menu items is: 2222 These can be changed via the Xenta OP only provided the "Edit Access Code" menu item is present in the OP Tree. Downloading the controller may reset the access level passwords back to the default.

Issue The following error can occur when logging into Security Expert using a Remote Client:   Could not log on to Server. Please check your remote connection setup. The server has rejected the client credentials. Product Line EcoStruxure Security Expert Environment Security Expert Server / Client Cause The security policy settings are different between the Server and Client.   When installing the Security Expert Server and Clients, the default security policy is used. This requires that the Windows username and password that the operator has used to log in on a client machine is also a valid user on the computer that is running the Security Expert Server. These security requirements are very favourable for corporate networks and setups where the users and policies are easy to manipulate. For that purpose alone, the Security Expert Server and Client are installed with these settings by default.   All installations are not created equal however and sometimes the Security Expert Server is not located within a domain. In another scenario, the server may be in a domain but the operators need to connect to it from a machine that is not in the domain. In these cases, it has been requested that the security policy in place on a domain or the physical machine is disabled and although this is not recommended practice the security of the system can be maintained using a suitable VPN structure.   This solution should be used with full knowledge that the security of the system will rely on the operator user login name and password as well as the security measures put in place for a client to be able to hit the server with a login request. Protection of the infrastructure to the connection is beyond the scope of this document. Resolution The easiest solution would be to put the Client machine(s) in the same Domain as the Server.  However if this is not possible or if no Domain is used then you can still manually update the security policy instead. The following process is a manual edit of the XML configuration files  SecurityExpert.exe.config  SecurityExpertSV.exe.config  Both of these files are located in the .\Program Files\Schneider Electric\Security Expert directory on the Client and Server. It is recommended then to backup these two files prior to performing this task. Close all Security Expert clients and stop the Security Expert Data Service. We are first going to update the Security Expert Client configuration file SecurityExpert.exe.config on the client machine.  If using more than one Client, the change must be done for ALL clients Open Notepad as the administrator, browse to the specified location making sure the 'all files option' is selected.  Then open SecurityExpert.exe.config (Be aware that it may not have the file extension showing and will be called an XML Configuration file by default) Locate the netTcpBinding tag . Nested within this tag is the binding tag Ensure that you insert the below text after the opening binding tag and before the closing \binding tag . If you insert the text outside this tag, the application will fail to run.   "<security mode ="None"></security>" IMPORTANT You must ensure you enter "None" with a capital "N" (not lower case). Ensure you copy input text exactly as shown. Now save the file. If you get a write error then you need to open notepad as the administrator. Repeat the process for the Security Expert Server configuration file SecurityExpertSV.exe.config which is located in the same directory on the server machine.      Again, make sure the line is inserted after the opening tag and before the closing tag or the application will fail to run when you save the changes. Restart the Security Expert Data Service and test the connection settings.

Issue Satchwell CD2201 Compensator Controller–Actuator requires replacement. Environment Stand alone discreet Satchwell CD2201 Compensator Controller–Actuator Cause Obsolescence of Satchwell CD2201 Compensator Controller–Actuator Resolution Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller, compatible Temperature Sensors and MD Series Actuator and Linkage Kit. Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller. N.B. Two models of the Schneider Electric Satchwell CSC Compensator Controller are available :- CSC 5252 Compensator Controller without Time Clock CSC 5352 Compensator Controller with integral Time Clock  Details of the Schneider Electric Satchwell CSC Compensator Controllers may be viewed here. It should be noted however that the CD2201 Compensator Controller–Actuator had no integral Time Clock. Replacement of Air Temperature Sensors It should be noted that the existing Satchwell Outside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Similarly, it should be noted that the existing Satchwell Inside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Details of replacement Schneider Electric STO600 Outside Air Temperature Sensor may be viewed here. Details of replacement Schneider Electric STR600 series Inside Air Temperature Sensor may be viewed here. N.B. It should be noted that the CSC Compensator Controller will perform entirely satisfactorily without the connection of an Inside Air Temperature Sensor. Replacement of Water Temperature Sensor. It should be noted that the existing integral Satchwell Water Temperature Sensor associated with the CD2201 Compensator Controller – Actuator cannot be re-used and should therefore be replaced. In order to minimise mechanical work it is suggested that a Surface Mounting Temperature Sensor is installed on the pipework, rather than an Immersion Temperature Sensor installed in a Pocket in the pipework. Details of replacement Schneider Electric STC600 Surface Temperature Sensor may be viewed here. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CSC Compensator Controller. Details of the Schneider Electric MD10B Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here. Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue Changing the default port numbers for the Fox, Platform Daemon and HTTP ports in I/A Series G3 Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Enterprise Network Controller Cause There is a need to change the default port numbers of the Fox, Platform and HTTP ports used in I/A Series G3. Below are the descriptions of the ports usage and their default port numbers: TCP port 1911 (Fox port) Default port for a station's Fox Service used for Workbench to station and station to station communications TCP port 80 (HTTP port) Default port for a station's Web Service used in browser access (Hx, Wb) TCP port 80, 3011 (HTTP and Platform Daemon ports) Default ports for Workbench Platform connection Resolution The default ports for the Fox and HTTP ports can be changed during the process of creating a new station. Follow the following procedures if the ports need to be changed after the station has been created. To change the Fox port: In Workbench, open the station. Expand 'Config' > 'Drivers'. Open the Property Sheet of the NiagaraNetwork. Expand the 'Fox Service' and you can change the port number from the default of 1911. To change the HTTP: In Workbench, open the station. Expand 'Config' > 'Services'. Open the Property Sheet of the WebService and you can change the Http Port number from the default of 80. To change the Platform Daemon port: In Workbench, open the host's Platform. In the Platform view, go to the Platform Administration. In the Platform Administration view, click on the 'Change HTTP Port' button to change the default port.

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue Is JSON supported in a web service environment? Product Line EcoStruxure Building Operation Environment Web Services JSON StruxureWare Building Operation Cause Many third party application only communicate JSON. Resolution JSON is not a supported format in StruxureWare Building Operation as an HTTP response in Generic Consume. Only Simple XML Web Service and SOAP Web Service are supported. It must be an XML document. There is a tool developed on the Community to automatically convert the JSON response from a Web Service to XML, and though it is not officially supported by PSS, it has proven to be a valid work around. Refer to SBO - Web Service through a Proxy, JSON and Image conversion.

Issue SER8000 series room controllers communications options Environment SER8000 series room controllers Cause Integration to SER8000 room controllers via Modbus is required.  Resolution Currently, the SER8000 series room controllers communications options are Zigbee Pro or BACnet MS/TP. Refer to the SER8300 datasheet.  To communicate on Modbus RS-485, an option would be to use the multi purpose manager (MPM-UN) as a gateway device.    * Updated July 2015 As per Product Annoucement PA-00428, the SE8000 with firmware 1.3 can now act as a Modbus slave using the RS-485 port.