Building Automation Knowledge Base

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 How to connect to the Jace 8000 system shell Product Line TAC IA Series Environment I/A Series Jace 8000 Cause Multiple diagnostic and low-level configuration processes need to be performed directly connected to the Jace 8000 in the system shell of the device. Resolution Connect the USB cable between the controller’s Debug port and the USB port you are using on your PC   On your PC, start your terminal emulation software. For example to start PuTTY from the Windows Start menu, this is typically Programs > PuTTY → PuTTY. PuTTy can be downloaded at no cost if you do not already have it on your PC. In the tree in the PuTTY Configuration dialog, expand Connection and click Serial. Set the “Serial line to connect to” for your PC’s (USB) COM port to use. For example, COM3. NOTE: You can examine Ports in Windows Device Manager to determine which serial port is in use on the PC. If you don't see the Jace in the COM ports, you will need to install the driver which can be Downloaded from FTDI.  It is also attached to this document below for Win10. Set the “Configure the serial line” fields as follows: • Speed (baud): 115200 • Data bits: 8 • Stop bits: 1 • Parity: None • Flow control: None In the tree in the PuTTY Configuration dialog, click Session and then click/select the “Connection type” as Serial NOTE: (Optional) You can save this configuration to reuse (load) in future PuTTY to JACE serial sessions. To do this, type in a connection name in the “Saved Sessions” field (for example, “JACE- 8000-S”), and click Save. When you start PuTTY again to serially connect to the JACE, select this name and click Load. At the bottom of the PuTTY Configuration dialog, click Enter. At the login prompt, enter a platform user name, and at the password prompt, the platform password. a. If prompted for system passphrase, enter the platform’s system passphrase. If login is successful, the TITAN System Shell menu appears. When finished making platform changes from the system shell, do the following: • If no changes or reboot is not necessary, simply type L to Logout. • If changes require rebooting, select the Reboot option. Type “y” at the “Are you sure you want to reboot [y/n]” prompt, and press Enter. Shutdown-related text appears in the terminal (PuTTY) window. Click the Close control (upper right corner) in the terminal session (PuTTY) window. Click OK in the “PuTTY Exit Confirmation” popup dialog. Unplug the USB connector from the JACE’s Debug port. This procedure is simply how to connect using USB serial port for system shell.  More information about functions available once connected can be found in other Knowledge Base articles and in the Jace 8000 Install and Startup Guide

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue How to bind BACnet Objects with Priority Levels Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet MPX, RPC, MPC Cause Servers (ES, AS) and other native devices (MPX, RPC) have slightly differing binding options. EcoStruxure Building Operation BACnet binding offers many options and the information below gives an example of how it can be achieved, it is not the only method. Resolution When binding between BACnet objects in EcoStruxure Building Operation (either external or within the device) it is usually better to utilize the BACnet Priority based control, often this facility is not fully exploited. Object Force and Overrides will use set priorities as in the BACnet Interface setting for the site (see System/Interface Manager/BACnet), the defaults are below. The example below shows a simple bind from a BACnet Schedule-value to a BACnet Binary-value Priority 16 (or other priority as required, as binding at Priority 16 can interfere with simple manual overrides). A BACnet datetime_value has no Priority array, so if you bind, for example, from a "BACnet Schedule Next transition" to "BACnet datetime_value Value" the bind to a Priority cannot be achieved, as below. In addition, the MPX & RPC have some constraints that Servers do not have. If you bind "Transfer Value to" an Object Value Property (rather than a Priority) then further bindings "Transfer Value to" binding to a Priority is inhibited. The screenshot below shows the error that is seen. This promotes using Priorities to control BACnet Objects.

Issue How many objects, users, devices, etc. per device with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation Building Operation WebStation Cause How many objects per device and what are the limits of EcoStruxure Building Operation? Resolution The primary source of these details should be the Architectural Guidelines on WebHelp Topic for the version being used

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

Issue How to turn on and release a specific command priority on a BACnet point? Product Line EcoStruxure Building Operation Environment ES AS Bacnet interface Script programming Cause Wants an example script program to turn on/ off specific BACnet command priorities in a BACnet device. Resolution To control a specific Digital or Analog Output in a BACnet device, from a script program you would use a Numeric Output in the program that has its value set as required by the program. This Output from the program is then bound to the specific command priority attribute of the point to be controlled. To release control from that Command Priority the "Relinquish" keyword is used in the program to Null that specific command priority and allow lower commands to take control of the output.   Here is an example AS test program that turns on a Digital Output for 4 seconds and then releases it for 4 seconds. The Numeric Output DOControl should be bound to the required Output Command Priority 2, it is written as a fallthru program. Notice; the Relinquish command is releasing the output from Command Priority 2 as used in this example.   Numeric Output DOControl DOOnLine: DOControl = Active Wait4: If TS > 4 Then goto DOOffline Else goto Wait4 DOOffline: Relinquish(DOControl,2) Wait4More: If TS > 4 Then goto DOOnline Else goto Wait4More   This type of script program can be located in the Application of the BACnet interface and control outputs on 3rd party BACnet products or b3 controllers. Note: For control of b3 outputs it is often better to put an appropriate control program (Not the above code) within the b3 controller itself, making it more robust in case of comms failure and also reducing communications traffic. Also check out the Convert Continuum Plain English into SBO Script 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 During the installation of PCT 2 and 'Starting VM pct' step, one encounters the error: "Error: System.InvalidOperationException: Failed to run: Start-Vm -Name pct". Open Hyper-V Manager and confirm the 'pct' VM was created. Manually trying to start produces this error: Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Hyper-V is not set to start on boot automatically. Resolution DO NOT perform these instructions if PCT 1 is installed on the same OS. Contact Product Support for assistance. Launch Command Prompt as Administrator. Type: bcdedit /enum​  Ensure 'Hypervisorlaunchtype' is not 'Off' and set to 'Auto' by running the following command: bcdedit /set hypervisorlaunchtype auto​ Reboot the PC Rerun PCT 2 installer

Issue "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 Alarm "cannot verify lead object" appears even though AS is online. Product Line EcoStruxure Building Operation Environment StruxureWare Alarm Queue Cause The AS is unable to communicate with the ES. The ES may be able to communicate with the AS allowing the user to view and control the AS, but Value Binds will not work. This type of error can also occur as a result of multiple networks being accessed by the same PC.  It is important that if you are using multiple networks that the ES be configured with the IP address for the correct network. Resolution Ensure that no Firewalls are blocking configured ES and AS ports Ensure all devices are on the same Windows Domain In workstation, select the Enterprise server's Communication Tab and verify that the IP address listed for the ES matches the ES PC IP address. Right click on the ES and select Advanced > Repair Server Communication For more information see Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port

Issue Drayton Theta Autotherm Controller requires replacement. Environment Stand alone discreet Drayton Theta Autotherm Controller applications. Cause Obsolescence of Drayton Theta Autotherm Controller. Resolution A.  Controller - Overview The Drayton Theta Autotherm Controller was manufactured primarily for use in domestic heating applications. The Drayton Theta Autotherm Controller combined the following functions in a single stand alone discreet Controller :- Heating System Compensator HWS Programmer.  There is no simple like for like replacement currently available but the two functions may be replicated as shown below. B.  Controller - Replacement 1.  Suggested replacements for Autotherm Heating System Compensator function and associated Sensors :-  Compensator Controller = CSC5252 or CSC5352, details of which may be viewed here. (The CSC5352 may be programmed to provide automatic Night Set Back) Outside Air Temperature Sensor = STO600, details of which may be viewed here. Clamp-On Temperature Sensor = STC600, details of which may be viewed here. (Use of a Clamp-On Temperature Sensor eliminates the need for any pipework modifications) N.B. The existing Drayton Theta Autotherm Heating System Actuator and Valve Body may be retained should these both be in working order. Alternatively, suggested replacements for the Drayton Theta Autotherm Heating System Actuator and Valve Body are :- Actuator = MD10B-24 or MD10B-230, details of which may be viewed here. Linkage Kit = LMD/AR-MB (914-1071-000), details of which may be viewed here. Valve Body = MB (select size from ½” to 2” size), details of which may be viewed here. 2.  Suggested replacement for Drayton Theta Autotherm HWS (Hot Water Service) Programmer function :- We do not offer an independent Programmer but such a product should be available from the Distributor supplying the S-E Satchwell CSC Compensator Controller and associated Temperature Sensors.  N.B. Any existing Relays that are currently installed may also be retained, in order to complete the replication of the Drayton Theta Autotherm control scheme.

Issue Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK  Product Line Field Devices Environment Pop Top Valves Pop Top Actuators Cause Actuator Part no's available in the UK Valve Part No's and connection types available in the UK ZY valve and actuator replacement Resolution   Actuators AH13U230 - High Close Off - Spring Closed 230Vac Actuator c/w 36" Lead AH13U23A - High Close Off - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG13A230 - Spring Closed - 24Vac Actuator c/w 36" Lead AG13A23A - Spring Closed - 24Vac Actuator c/w 36" Lead + Aux Switch AG13U230 - Spring Closed - 230Vac Actuator c/w 36" Lead AG13U23A - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG23U230 - Spring Open - 230Vac c/w 36" Lead AG23U23A - Spring Open - 230Vac c/w 36" Lead + Aux Switch AG23A230 - Spring Open - 24Vac c/w 36" Lead AG23A23A - Spring Open - 24Vac c/w 36" Lead + Aux Switch Valves (Note:NPT is American connection) VT2222 - 2way - 1/2" NPT 2.5Cv VT2223 - 2way - 1/2" NPT 3.5Cv VT2231 - 2way - 1/2" BSP 1.0Cv VT2232 - 2way - 1/2" BSP 2.5Cv VT2233 - 2way - 1/2" BSP 3.5Cv VT2325 - 2way - 3/4" NPT 5.0Cv VT2327 - 2way - 3/4" NPT 7.0Cv VT2332 - 2way - 3/4" BSP 2.5Cv VT2333 - 2way - 3/4" BSP 3.5Cv VT2335 - 2way - 3/4" BSP 5.0Cv VT2337 - 2way - 3/4" BSP 7.0Cv VT2437 - 2way - 1" BSP 8.0Cv VT3231 - 3way - 1/2" BSP 1.5Cv VT3232 - 3way - 1/2" BSP 3.0Cv VT3233 - 3way - 1/2" BSP 4.0Cv VT3332 - 3way - 3/4" BSP 3.0Cv VT3333 - 3way - 3/4" BSP 4.0Cv VT3335 - 3way - 3/4" BSP 5.0Cv VT3337 - 3way - 3/4" BSP 7.0Cv VT3437 - 3way - 1" BSP 8.0Cv Erie™ PopTop™ Series Valve Bodies and Actuators - Installation Instructions.pdf for the VT and VS valve, AG and AH actuator. Note: Only those listed above are available in the UK.

Issue How to create a proper XLSX/Excel template under Alarm Triggered Notification of EcoStruxure Building Workstation, in order to receive the Multi trend logs report in the XLSX/Excel format. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation Cause Additional information is needed to create a template for presenting multi-trend log information in Excel XLSX format.    Resolution Below screenshot shows where users can select the Report format and XLSX template.   The multi trend log containing four Interval Trend Logs 1 to 4 with their time stamp is shown as below as an example   In order to get the XLSX multi trend log report in XLSX/Excel format upon receiving a trigger, the following XLSX template needs to be used containing two rows: The first header row contains the column headers from the trend log. The second row include the <Multi Log List> command   Here is final report in Excel/XLSX format:  

Issue Where can information on programming and configuring the AC256 line of controllers be found.  Environment AC256 AC8 AC4+4 Cause Although the AC256 line of controllers has been discontinued, there are many live systems still in existence which need to be supported. Resolution The AC256/AC8 Configuration and Programming Student Guide can be found here.

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

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 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 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 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 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 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 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.