Building Automation Knowledge Base

Issue Does the entire SBO system need to be upgraded to 1.5.0.171xx, 1.6.2.12xxx or 1.7.2.111xx before upgrading to 1.9.1 if the network includes LON devices? Can SBO be upgraded directly to 1.9.1 from 1.5.X, 1.6.X or 1.7.X? Product Line EcoStruxure Building Operation Environment SBO Workstation 1.5.0/1.6.1/1.7.1 SBO ES 1.5.0/1.6.1/1.7.1 SBO AS 1.5.0/1.6.1/1.7.1 SBO AS-P 1.7.1 Cause In systems that have SBO servers that already are hosting LON devices based on LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to be prepared before an upgrade from versions 1.5/1.6/1.7 to version 1.9.1. Even servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no devices or network variables are created yet, the servers have to be prepared before the upgrade. Resolution Please see section 9.2.3 of SBO 1.9.1 Release Notes. Although it says "Steps to upgrade a 1.6.2/1.7.2 multi-server system" you don't have to upgrade the AS or ES etc, even if they run 1.6.1/1.7.1, it's only SBO Workstation that need to be hotfixed. Links to the different Workstation hotfixes can be found Server with LonWorks devices - TPA-SBO-17-0002.00 - Links to hot fixes. If there are no LON devices in the system, you may upgrade directly to 1.9.1 from 1.5.X/1.6.X/1.7.X

Issue Accessing WebPinpoint graphics from a web browser causes one of the following errors…   Failed CreateDNWACServer. Cause:Object reference not set to an instance of an object. URL:HTTP://eceheatsrvr/DNWACServerFactory DNWACServerFactory /WACServerFactory.soap   Failed creating remote objects. DotNet framework is missing.      Product Line Andover Continuum Environment Continuum webClient Server MicroSoft Windows XP MicroSoft Windows Vista MicroSoft Windows 7 MicroSoft Windows 10 MicroSoft Windows Server 2003 MicroSoft Windows Server 2008 Cause User Account Control redirects files to a different folder than expected by WebClient. User permissions are interfering with the WebClient. A variety of other configuration issues may cause this problem. Resolution User Account Controls Redirection The WebClient installation guide goes into detail about why MicroSoft Windows includes User Account Controls redirection. Follow the procedure outlined below.   Give "Everyone" permissions to the C:\Program Files\Continuum and C:\Program Files\Continuum\DNWACServerFactory folders In Windows Control Panel > User Accounts and Family Safety > User Accounts, select an Administrator user on the PC and select User Account Control Settings. Move the slider all the way to the bottom to Never Notify and select Ok. Follow the instructions in the webClient Installation guide section called "Configuring Graphics for webClient: Windows Server 2008, Windows Vista and Windows 7". Site may be setting User Account Control with group policy and setting it upon reboot of the PC to a setting other than Never notify. A batch file may be used to turn User Account Control off before launching WebClient. A Google search for doing this would be needed and is beyond the scope of this article. Each host that will be running a web browser WebClient session should have also have User Account Control settings set to minimum.       Web.config has not been correctly modified   Using Windows Notepad as an Admin user, modify the web.config file which is located in the c:\program files\continuum\dnwacserverfactory folder. Delete the text and replace with the text below, replacing WORKSTATION1 with the host name of the host computer.  This must be done on all hosts which will run WebClient browser sessions. <configuration> <system.runtime.remoting> <application> <service> <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap" /> </service> <channels> <channel ref="http" machineName="WORKSTATION1"> </channel> </channels> </application> </system.runtime.remoting> <system.webServer> <security> <requestFiltering allowDoubleEscaping="True"/> </security> <directoryBrowse enabled="true" /> </system.webServer> </configuration>     Allow Double Escaping   If for some reason editing this file is still not working. Try the following: In Start >Control Panel > System and Security > Administrative Tools > IIS Manager (Not IIS6) Expand the tree on the left for the webserver name. ie. Webclient1 Expand Sites Expand Default Web Site Click DNWACServerFactory Double Click Request Filtering In the right-hand column select Edit Feature Settings Check Allow Double Escaping and click OK Click on the Default web site and in the far right column click Restart     Test Authentication pass-through for SOAP errors   In IIS Manager; Expand Server> Sites> Default Web Site Left-click on the DNWACServerFactory, on the far right column Select the Basic Settings link Click the Test Settings button. If Authentication pass-through is showing red follow this procedure Click Close Click Connect As> Add a windows user and password that will be used for WebClient Click the Test Settings button Authentication pass through again and it should now show green Perform a local reboot on the WebClient server Test Webclient Graphics     Make sure that the browser PCs are logged in as a Local Administrator for the WebPinpoint and ActiveX installation   Internet Explorer>Tools>Internet Options>Security>(select Zone i.e. TrustedSites)>Custom Level button Make sure that 'Download signed Activex controls' and 'Download unsigned Activex controls is set to prompt or Enable, since the default setting on many web browsers is Disabled.       Add the Webclient PC as a trusted site to the browser PCs   In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. In Internet Explorer: Select Tools > Internet Options > Security > Click Trusted sites > Click Sites Type in http://yourservername/WebClient and click Add (Ex. http://tacweb/WebClient) Deselect the checkbox for Require server verification (https:) for all sites in this zone.  Click OK and then OK again Close Internet Explorer and retry accessing WebPinpoint     Be sure to configure the application pool for 32-bit applications on 64-bit operating systems.   On 64-bit Operating Systems perform the following steps: Open IIS Manager. Expand the computer name in the left-hand pane and click on Application Pools in the system tree view. Select DefaultAppPool and click Advanced Settings. In the Advanced Settings dialog box, change the Enable 32-bit Applications option to True. ** When using 1.94 SP1 and above, check the application pools .net version selected and make sure that the Identity is set to "Network Service" Name                           .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic  4.0 Classic .NET AppPool  2.0 Default AppPool   2.0 WebClient 4.0       DNS issues   Even when you may not be seeing red x’s in Pinpoint View>Options>Web locations and you are able to browse to pin files though IE, WebPinpoint may be giving you a graphic URL error. Try entering using the IP of the WebClient server in place of its DNS name for Pinpoint View>Options>Web locations. Also try using the WebClient Servers IP address in places of the its DNS name and also for accessing WebClient through the browser. For example http://10.159.100.125/WebClient       WebPinpoint fails to register the DNWACClientProxy.dll and tlb files when installed.   On the from the client (web browser) host, perform the steps below:  Close WebClient browser if it is running. Open command line in Administrator mode. Run the batch file C:\Programs Files (x86)\WebClientPinpoint\WPPRegistrationClient.bat     Other items to check:   Disable Windows Defender Turn off all 3 firewalls Shut off SPS software protection service when installing. Run Internet Explorer as an Administrator to make sure the ActiveX controls are being installed

Issue Unable to send out emails using Gmail SMTP server (smtp.gmail.com) with the following error messages in the station's standard output. "javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first." Authentication has been enabled in the system.properties file as per Mail Service in a Niagara R2 UNC station configured correctly but e-mails not being sent to the SMTP server. Product Line TAC IA Series Environment I/A Series R2 Cause As with most public SMTP servers, like Gmail, the outgoing mail SMTP server requires TLS (Transport Layer Security) or SSL (Secure Sockets Layer) which I/A Series R2 does not support. Resolution Use an SMTP server that does not require TLS or SSL.

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

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

Issue There is a need for a single Compatibility Matrix that shows EBO, PME, Energy Expert and relevant software versions all in the same location.   Product Line EcoStruxure Building Operation, Other   Environment EcoStruxure Energy Expert (formerly Power Manager) ETL tool Cause Energy Expert version compatibility information is currently available but is stored in many different places such as release notes and online documentation, rather than one single matrix.   Resolution The full ETL for EBO compatibility matrix is shown in the following table. Energy Expert  PME EBO ETL Integration Utility .NET Framework Power Manager 1.0 7.2.3 1.6.1 3 1.0.14304.2 4.5 Power Manager 1.1 8 1.6.1  1.7.1 4.1 1.0.15306.1 4.5 Power Manager 1.2 8.1 1.6.1  1.7.1  1.8.1 4.3 2.1.16081.1 4.6 Power Manager 1.3 8.2 1.8.1 1.9.x  4.6 2.2.17056.2 4.6 Energy expert 2.0 9 2 5 3.0.18215.3 4.6 Energy expert 3.0 2020 3.0 3.1 6 3.1.19319.1 4.6 Not commercialized  - (n/a) 2021 3.2.3 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2022 4.0.2/2022 6 Integrated - (n/a) 4.8 Not commercialised - (n/a) 2023 5.0/2023 6 Integrated - (n/a) 4.8   Great care must be taken when choosing the correct version of ETL to use when integrating Energy Expert and EBO, as there are actually two families of ETL in production.  One ETL designed and tested for PME use only and ETL for EBO designed and tested with an EBO Extract Task specifically for integrating the two systems.  (For example, a version of ETL 4.7 exists, but this is not ETL for EBO and therefore does NOT contain an EBO Extract Task, even though it is a valid version of ETL for the Power Community) New PME 2023 now offers EWS Client 1.2 which can be used to transfer data from EBO to PME instead of ETL.  The merits for and against using this new EWS Client rather than ETL are discussed at length in the PME 2023 System Guide

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue Controller Error Logs - How to gather Continuum Controller error logs if requested by Product Support for troubleshooting. Product Line Andover Continuum Environment BCX CX  CMX 9680 9900 i2 b3 9702 Controller Error Log Gerry Log Cause Troubleshooting controllers often time requires obtaining an error log from the controller Resolution The controller error logs contain useful diagnostic information when it is necessary to troubleshoot a controller or system problem. Much of what is logged are normal system operations that may assist an engineer in diagnosing a problem in the field. To get the error logs from various controllers follow the procedures below: NetControllers - 99xx  Dumb terminal in using HyperTerminal Sign into the NetController Press V then E and press Enter over the NetController you are attached to Press F2 Hit Alt + Print screen and paste into a Word doc Arrow down to single space or Ctrl+D to page down Hit Alt + Print screen and paste into a Word doc Repeat this process until you are at the end of the errors (up to 200) F4 Exits the error log See the CX Controllers Programmer’s Guide for all terminal keystrokes Email the file to Product Support Services   BCX/i2/B3 Controllers CX9680/ACX5720/ACX5740/9702 Controllers Note: You can not retrieve errors from NetController I (CX9900) using this tool Controller Error Log Tool Navigate to C:\Program Files\Continuum Double click on ControllerErrorLogTool.exe to open (This will do an install the first time) Note: The ErrorLogTool.exe is an older version of this utility and will work, but gives less information and does not contain the error lookup feature. Enter in the BCX or master CX IP Transport type = UDP or TCP depending on controller configuration CX Enode ID = AccNetId from the main CX editor Select Continuum in the Mode area, top right If the controller is a field device then enter the following: CX infinet port = Select the one you want to report on Infinet Node ID = port number of the i2 device you want the error log out of Once all the above required entries have been made: Click Get Log and the page will populate with any errors Once this runs, select SaveAs and name the file Email the file to Product Support Services Suppliment - To gather error logs from Continuum controllers transisioned to StuxureWare please see How to pull the error log from a b3 or Infinet controller in SmartStruxure.

Issue [Invalid Address] Product Line TAC Vista Environment Vista Workstation Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Invalidate Resolved Addresses Cause If you view a controller in Vista Workstation and point values read [Invalid Address] instead of showing values, there are a number of troubleshooting techniques to rectify this. Unfortunately, [Invalid Address] is a bit of a "catch-all" error code. Since it can be difficult to determine the cause of the error, these troubleshooting suggestions will have varying degrees of success. The best course of action is to try each of these methods in the order of least to most disruptive. As new techniques and procedures are discovered, they will be documented here. Resolution Check the label for N/P Designation If a programmable controller has read [Invalid Address] on every point since it was installed (it has never worked properly) then there is a chance that this is not a Network Presentation controller. These are referred to as stand-alone controllers and each of the 280 and 300 series have a non-network presentation variety. Check the label on the controller to make sure it says "302/N/P" or "282/N/P." If it just says "302" or "282" then this controller cannot communicate on a network and will never report values to a front end. Also see Xenta 280 or 300 Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. In the Vista Workstation Right-click on the controller and choose Advanced Operations > Invalidate Resolved Addresses Proceed? Select Yes. Right-click on the controller and choose Advanced Operations > Read Address Proceed? Select Yes. Wait up to about 30 seconds for the values to populate. Download the Controller In the System Plug-in, Download Applications and Parameters to the controller Recommission the controller In the System Plug-in, TAC Network > Commence Communication (skip to this step for LON controllers) You may want to follow this action with another attempt at the steps outlined in the section above "In the Vista Workstation" Repair or recommission the Routers in the NL220 or Lonmaker database repair or recommission the Routers. Re-Do Group Bindings & Commence Communication: In the System Plug-in, LNS network > Create Group Bindings In the System Pug-In right click on the TAC Network and commence communication Re-doing group bindings ensures that the LNS network interface, and LON to IP routers receive message can 0 for the main xenta address broadcast in the network. Monitor Sets If your monitor sets have become corrupted, then every controller you download from that point on will say [Invalid Address] on every point. Monitor sets are actually stored on the hard drive of the PC, not in the LNS database. If you have made backups and passed them back and forth between PCs, as you often do during the commissioning phase, this invites corruption of monitor sets. There were some known issues with monitor sets in LNS version 3.24 that have since been corrected in LNS version 3.26. This can be downloaded from Echelon's website in LNS Server/Turbo Edition Service Pack 7. Go to http://www.echelon.com Navigate to Support > Support Resources > Downloads Log in with a user name and password. If this is the first time logging in, register for a free user name and password. Search for software in the Recommended Downloads category Find LNS Server/Turbo Edition Service Pack 7 (this is the latest at the time of this article, a newer one may exist and should be downloaded) Prior to restoring a backup, you may want to resynchronize the drawing making sure to check the option for "Sync monitor sets between drawing and database." Usually restoring the last good backup will fix up the monitor sets. If you do not have a recent backup, there are a couple of procedures that may help resolve the corrupted monitor sets issue.   Note: Viewing and altering monitor sets is only available in Echelon LonMaker. There is no analogous menu item in Newron's NL220. Do not download any more controllers. Check your monitor sets in LonMaker by navigating to LonMaker > Network Service Devices Click on the NSS which should have the same name as the network Select the Monitor Sets button If you get "Monitor set cannot be found. (Subsystem: NS, #160)" then your monitor sets are corrupt. Close down Vista Server & LonMaker (if you don't you will get an error when you try to validate that says "The Network Interface, database directory, or NSS type, conflicts with the already active network. (Subsystem: NS, #149)") Navigate to Start > Programs > Echelon LNS Utilities > LNS Database Validator Navigate to the LNS Network to Validate Check the Repair Database checkbox Hit the Validate button If that does not find and repair the monitor sets, the following steps may help. Make backup of the LNS database. Start LonMaker. Do not start Vista Server. Go to the monitor sets (LonMaker > Network Service Devices > NSS > Monitor Sets) and right-click and delete the monitor sets Run the System Plug-in and create a brand new Vista database in a different location than your current database. Stop the Vista Server and start it again Check the monitor sets again, they should be right now Stop the server again and change back to your original Vista database Non-Latin Characters If you use a signal name or description in the XBuilder Device Editor with non-Latin characters (like Swedish åäöÅÄÖ) you will get [Invalid Address] when you view the signal in Vista. Value pages are displayed correctly. Do not use non-Latin characters for signal name or description. This issue has been confirmed in versions 5.1.2 - 5.1.4, and will be fixed in a future release. Classic Networks View the Address Tab under the controller's properties in Vista Workstation Check Address Table slots 0 and 1. If the "Domain Index" and "Member or Node" have been manually altered, set them back to 0. An applicationless controller will display [Invalid Address] in a classic network, whereas in an LNS network, it would simply fail to commission due to its applicationless state.  Direct download the controller through the Menta serial cable to see if it resolves the error. Xenta 700 Menta values See Xenta 700 Menta Object Values report [Invalid Address] in Workstation, Read operation failed. Delete, Destroy, Redo This is your last resort. If you have tried everything else possible, it is time to remove this controller from the database and start from scratch. The exact steps and methodologies may change based on your network and controllers, but basically you need to remove any mention of this controller and add it back in as though it were a brand new device. Decommission the controller Delete the device Delete the device template In the System Plug-in, remove the device from the TAC Network Update the Vista Database Create a new controller Browse in a Menta file Update Vista and download

Issue How to Set Up BACnet Enabled ABB Variable Frequency Drives for Use With Continuum Product Line Andover Continuum, Other Environment ABB Variable Frequency Drives Continuum Cause ABB VFDs must wired and configured properly to be used with a BACnet Continuum network. Resolution When wiring an ABB drive up to the Continuum BACnet MSTP network make the following connections: Terminal X2 Type (+) (-) Reference Drive Only 29 30 31 Bypass 27 28 29  ABB recommends that when using a two conductor cable with shield that the shields not be connected  to any pin (Note that pin 29 would be unused) but simply connected together with a wire nut. However, they do say that the shields can be connected to pin 29 if the drive communication is intermittent.  If the ABB drive does not have an E-Clipse bypass (E-Clipse is the ABB brand name for the bypass portion of the VFD) use the following settings:  Parameter  Setting Notes 9802  BACNET  Sets the communications protocol of the VFD. 5302  MAC ID Create a unique ID. A good practice is to set this to the Infinet ID + 1000. For example, if the Infinet ID is 5 then set this to 1005. 5303  Baud Rate  Set the baud rate being used on your BACnet network. 5311  Device Instance ID                   This is the Infinet ID and should be set to an available number between 1-127. This will display as a hexadecimal value in the BACnet side of Cyberstation. 1001  COMM  Set this if you want to start & stop the VFD over BACnet. 1103  COMM  Set this if you want to control the drive speed over BACnet. 1604  COMM  Set this if you want to reset VFD faults over BACnet. If the ABB drive does include a bypass the following settings must all be entered (notice that 5302 and 5311 are now specific to the VFD portion of the unit whereas the 5002 and 5011 are specific to the bypass portion) All of these parameters as well as the parameters listed above must be entered at the bypass. Parameter Setting Notes 5302  Drive MAC ID  Create a unique ID specific to the VFD. 5311  Drive Device Instance ID  This is the Infinet ID specific to the VFD. 5002  Bypass MAC ID  Create a unique ID specific to the bypass. 5011  Bypass Instance ID  This is the Infinet ID specific to the bypass. NOTE If the ABB drive is ACH550. Then the parameter below need to be set as a minimum. Other points will also need to be set depending on your site requirements, but the ones below will get communications up and running    Parameter  Setting Notes 5301   x5xx -This parameter indicates the active protocol and its revision. It should read x50xx if BACnet is properly loaded. If this is not the case, confirm that drive parameter 9802 = BACNET (5). 5302  MAC ID -This parameter sets the drive’s BACnet MS/TP MAC ID. A temporary value of 0 places the protocol channel in reset. 5303  Baud Rate -Set the baud rate being used on your BACnet network. 5304 Set to 0 -This parameter sets the BACnet MS/TP character format as follows: 0 = 8N1 1 = 8N2 2 = 8E1 3 = 8O1. 5311 EFB PAR 11  - Instance ID part1 This parameter, together with parameter 5317, EFB PAR 17, sets BACnet instance IDs: • For the range 1 to 65,535: This parameter sets the ID directly (5317 must be 0). For example, the following values set the ID to 49134: 5311 = 49134 and 5317 = 0. • For IDs > 65,535: The ID equals 5311’s value plus 10,000 times 5317’s value. For example, the following values set the ID to 71234: 5311 = 1234 and 5317 =7 5317 EFB PAR 17  - Instance ID part2 This parameter works with parameter 5311 to set BACnet instance IDs. See parameter 5311. 1001  COMM -Set this if you want to start & stop the VFD over BACnet. 1103  COMM -Set this if you want to control the drive speed over BACnet. 1604  COMM -Set this if you want to reset VFD faults over BACnet.

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue When starting SigmaX, an error is reported, the error is: - This application failed to start because side-by-side-configuration is incorrect. Reinstalling SigmaX does not help. Product Line Satchwell Sigma Software Environment SigmaX Windows 7 Windows 10 Cause SigmaX error when trying to run on a Windows 7 or Windows 10 machine. Resolution Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: Open an elevated command prompt. Click Start > All Programs > Accessories Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. More Information about SFC scan can be found in this document: http://support.microsoft.com/kb/929833 At the command prompt, type the following command, and then press ENTER: sfc /scannow The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows. Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished. However Microsoft Visual C++ Redistributable may not be installed sfc /scannow will not detect this, the Visual C++ Redistributable will need installing. Please see Error when trying to run SigmaX.exe and RegSigmaX.exe for further information regarding this.

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

Issue Should automatic updates be turned on for Continuum workstation? Are there certain known issues of updates that have caused problems with Continuum or Webclient? Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows 10 Windows XP  Windows Vista Windows Server 2003 Windows Server 2008 Cause Microsoft Windows has an automatic update feature and frequently releases updates which can potentially affect Cyberstation and Webclient Server. Resolution Automatic updates should not be turned on for a Continuum or Webclient workstation. The Continuum compatibility matrix indicates Windows Operating Systems, Windows Service packs, SQL Server, .Net and Internet Explorer versions that were tested by Quality Assurance at the time of product release. Continuum Quality Assurance does not perform regression testing where new Microsoft updates are tested with Continuum products released in the past. Product Support recommends setting Windows updates to one of the other two options to allow for testing of Microsoft updates: Additional details can be found at: http://support.microsoft.com/kb/306525 Download updates for me, but let me choose when to install them Notify me but don't automatically download or install them   There are several specific updates that have caused issues with Cyberstation or Webclient. This is not a comprehensive list. Occasionally updates will break certain features and we discover this from our internal testing or from reports from partners or branches. Here is a list of some updates that have caused issues. KB835732-  Pinpoint 1.52 crashes when installed on a machine and you are accessing graphics from a network share. If you remove the hotfix the problem goes away.  This is the same hotfix that caused the SmartHeap out of Memory errors that was fixed with SP5 for 1.6.  KB828741- IIS (Webclient) machines without this patch may receive “Unable to establish a link to the remote Infinity services” Webclient 1.73 - Any patches that will install .Net Framework 2.0 will cause problems with webclient 1.73 since we don’t start using .Net 2.0 until webclient 1.74. KB911280 - this update blocks the acc.scp script from setting controller to PPP mode. This will a cause a Cyberstation using RAS controllers to not allow a connection. It will authenticate, but not connect. KB928366 – Webclient machines that use .Net 1.1(Listed on the compatibility matrix) will receive the error "Could not connect to server cause; type missing for member of type object _context id'. Could not create acwppserverproxy."  when opening web pinpoint graphics.  Remove this hotfix or upgrade to webclient 1.74 or greater. KB929969 – this hotfix does not require a reboot by Microsoft, but can cause the Cyberstation install to fail, if the install is performed before rebooting after the installation of the hotfix. See the Technical bulletin. KB968749 - SQL Express install fails on XML6 SP2 See SQL Express install fails on MSXML 6.

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution Note: The Excel method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the ActiveX snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the ActiveX control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.    Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC. This feature does not work with newer versions of Windows 10

Issue Sometimes just looking at the error message you get from e.g. TAC Vista or SmartStruxure when you try to send an email and it fails can lack information. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure WireShark Cause It is not necessarily all SMTP error messages and their explanation that are implemented in the software. Resolution For general information on WireShark usage read Using WireShark to analyse communications on an Ethernet network. If McAfee antivirus with HIPS is installed on the PC, use RawCap to capture the communication, as you will not see traffic originating from your PC online in WireShark. Additional reference for this article: Enhanced SMTP status codes   First of all when working with WireShark logs, it's a good idea to filter and focus the communication type you want to look at. In this case it's SMTP, so simply type smtp in the display filter and hit enter.   The easiest way to isolate a single smtp "conversation" between client and server, is to find one of the packets in the conversation, and in the "Analyze" menu click on "Follow TCP Stream".   This will give you the complete conversation in a separate window.   When you have used "Follow TCP Stream" be sure to set the display filter to "smtp" again when closing the window.   This is what happens if authentication is needed by the SMTP server but the client is not using authentication.   Here is the same attempt to send an email, but this time the client has enabled authentication   A little trick when using authentication is that WireShark can actually decrypt the Base64 encoded username and password. Simply right click on any SMTP packet, click "Protocol Preferences" and click "Decrypt AUTH parameters".   He are the packets decrypted   An error not easily detected by e.g. TAC Vista is error 535 "Incorrect authentication data". As stated in the enhanced status code table linked above, it simply means that either username, password or both is incorrect.   Though the product used may not have support for SSL and TLS, you can encounter SMTP server requiring it. Here is an example of a SMTP requesting SSL     For further info on troubleshooting sending emails from TAC Vista, please read Troubleshooting Sending Emails from a Vista Server.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue Power cycling the SE8000 room controller will cause the settings to revert to default. This requires reconfiguring each of the parameters once again. Product Line EcoStruxure Building Expert Environment Multi Purpose Manager Automation Server SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause This has to do with BACnet priority; if the configuration was not written with the appropriate priority, the Room controller will overwrite the parameters upon a power cycle and set them to default. Resolution There are a few ways to prevent the SE8000 from reverting to its default settings after a power cycle: Configuring each Room Controller locally by navigating to the configuration menu. (Centralized and Standalone system) Using a LUA4RC script (Centralized and Standalone system) Writing to points with a specific priority via the BACnet front-end (Centralized system) NOTE: Since Zigbee does not have any command prioritization mechanisms, setting the parameters from an MPM via Zigbee will not be retained after a power cycle and is strongly not recommended. All three methods can be used to configure a Room Controller prior to or after its installation. Configuration prior to installation can save a lot of time for the technician on site.     1 - Configuration on SE8000 (Local) Changing the parameters on the SE8000 locally will permanently save the settings and will also allow the user to change the parameters settings locally (e.g. Occupied cooling setpoint). This however can be time consuming.   2 - Configuration via LUA4RC This method is especially useful in standalone applications with no BACnet front end. If there are many parameters that need to be adjusted, it will be quicker to upload the script to each of the Room controllers rather than navigate to each parameter manually. By default, when you assign a value to a BACnet point, the write priority will be priority 16 Example: ME.MV6 = 2 --Set "Network Units" to Imperial (blocked by using priority 16, not user-adjustable) To write to another priority, an array is used Example: ME.MV4_PV[3] = 1            --Language will be blocked by user, room controller and bacnet front-end. Will be saved to memory and will stay after a power cycle NOTE: To release this priority, you can set it to nil (example: ME.AV25_PV[8] = nil). To access the relinquish default, priority 17 can be used Example: ME.MV10_PV[17] = 1    --Set "Occupancy Command" to "Local Occupancy"; here it is mandatory to have (_PV[17]) because thermostat must be able to toggle between "Occupied" and "Unoccupied" temperature Use the script below as a template for your LUA4RC script (remove comments to use less memory) if not init then ME.MV6 = 2           --"Network Units" ME.MV10_PV[17] = 1  --"Occupancy Command"  ME.AV46_PV[17] = 3   --"Standby Temperature Differential" ME.MV5 = 2           -- "Time Format" ME.AV67_PV[17] = 4   --Standby Time ME.AV68_PV[17] = 12  --Unoccupied Time ME.MV46_PV[17] = 3   --UI 16 Configuration ME.MV4_PV[3] = 1     --Language --Add all required configuration parameters init = true end   3 - Configuration Via BACnet: SE8000 parameters can be configured via the BACnet front end by using the following priorities: Priority 2 or 3: Using these priorities will permanently save the setting on the SE8000 and will not allow the user to change the settings locally. Relinquish default: This will allow the user to change the value locally on the SE8000. This is typically used with setpoints NOTE: using Priority 16 will not allow the user to change the value locally on the SE8000, however, the SE8000 will revert to value to default upon a power cycle. Another effective method is to push the configuration to multiple SE8000s across the network using a lua script. See Bulk Lua4RC upload via BACnet (Mass upload).