Building Automation Knowledge Base

Issue What features are included in Building Operation evaluation (demo) licenses? Product Line EcoStruxure Building Operation Environment Building Operation evaluation license Cause The features included in evaluation licenses are not shown in the documentation. Resolution License Administrator (Software Evaluation License) After adding the evaluation license in License Administrator,   Click on the "Diagnostics" Tab. Click on "Refresh the list". Local licenses list generates. Example of generated list: Local licenses: -------------------------------------------------------------------- Trust Flags: FULLY TRUSTED Fulfillment Type: TRIAL Status: ENABLED Fulfillment ID: LOCAL_TRIAL_FID_498 Activation ID: SC_57LRIHRFBOXC28SGYTPKCH98WIRKMWE Product ID: NAME=EcoStruxure Building Operation Demo License;VERSION=5.0 Suite ID: NONE Expiration date: 01-Feb-2024 Concurrent: 0 Concurrent overdraft: 0 Hybrid: 0 Hybrid overdraft: 0 Activatable: 1 Activatable overdraft: 0 Repairs: 0 Feature line(s): server.mssql (Version 5.0) client.zoning (Version 5.0) client.dashboard (Version 5.0) server.ec.auth.saml (Version 5.0) server.ws.generic.consume (Version 5.0) server.dig.signed.docs (Version 5.0) server.alarms.snmp (Version 5.0) server.ec.es (Version 5.0) server.device.es (Version 5.0) server.ws.ews.history (Version 5.0) Sigma.Server (Version 4) server.mqtt.rw (Version 5.0) graphdb.base (Version 1.0) server.esignature (Version 5.0) server.enterprise.base (Version 5.0) server.ws.ews.consume (Version 5.0) client.cad.import.tool (Version 5.0) smartdriver.license (Version 5.0) server.timescale (Version 5.0) client.script (Version 5.0) server.es.as (Version 5.0) client.graphiceditor (Version 5.0) server.device.as (Version 5.0) server.ws.ews.serve (Version 5.0) server.es.auth.saml (Version 5.0) server.enterprise.central (Version 5.0) client.functionblock.view (Version 5.0) client.station (Version 5.0)   Refer to the Webhelp EcoStruxure Building Operation Software Feature License String Description topic for an explanation of the license feature strings. Device Administrator (Embedded Evaluation License) After adding the evaluation license to the Device Administrator (see the article How to activate a demo license on an Automation Server at EBO 2022) follow the steps to view the available features: Click on the Entitlements. Click on Product Licenses. - The individual features are then shown as column headings The best way to see all the features available is to right-click on the license name under Product Name and choose Add/Remove columns.   A Select columns popup is then shown, and the available features are much easier to read.  

Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue Is it possible when starting Internet Explorer: To log on automatically. To start in Full Screen mode. To show a TGML graphic (without system tree) and without entering a user name and password by a shortcut. Is it possible to hide the 2 toolbars as described below? Product Line EcoStruxure Building Operation Environment Building Operation WebStation Kiosk Mode Cause For some applications such as Kiosk screens, these features are needed Resolution Automatic logon This can be accomplished either by using the "Remember me" checkbox on the logon screen, or by using the guest logon feature. To make WebStation bypass the logon screen, create a user with a username of GUEST and a password of GUEST, give this user limited permissions. For 1.7 and later, the password for the GUEST account when used for WebStation automatic logon, is not compatible with the default password policies. Automatic logon will only happen if the GUEST account password is exactly "GUEST". If policies are not changed the automatic logon will stop working after 90 days. Full Screen mode To make Internet Explorer go directly to full screen mode, you can use the "kiosk mode" switch. Create a shortcut with the command  iexplore.exe -k [insert your URL here] Display TGML Graphic without toolbars Open the graphic you require, using the "Open in a new window" right-click command. Copy the URL and create a shortcut with it. When you open this URL the user is taken directly to the graphic, without toolbars or menus.

Issue Steps for replacing a BACnet B3 controller and things to consider. Product Line Andover Continuum Environment Continuum b3xxx Controller Cause Steps for replacing a BACnet B3 controller and things to consider. Resolution Steps for replacing a B3 controller and things to consider. Use these steps when replacing a B3 controller from brand new stock, it is relatively straight forward. Physically disconnect power and MS/TP data cables from existing B3 Controller. Remove existing B3 Controller. Install replacement B3 Controller. Pull the battery tab on replacement B3. Connect MS/TP data cable to the replacement B3 controller. Connect power to the replacement B3 controller. Edit the B3 controller object in Continuum on the infinity side. On the Runtime tab enter the Serial Number of the new replacement B3 controller and click Apply. Click refresh until B3 controller returns Online. Reload the B3 Controller. Verify existing points and programs are running correctly. Perform a “Backup to Flash” operation on the B3 controller. Perform “Send to Database” operation on B3 controller from BACnet view. One scenario, for example, is the Replacement B3 controller came from a different job that has previously been programmed and has a valid flash backed up onto it. If installed on the new network, when powered up will start trying to communicate with controllers it has routing tables for. Could potentially cause issues on the new network. It is suggested that if you are replacing with a previously used controller from an old site with a valid flash backed up is to flush the controller out before applying to the new network. From a test machine with a test DB bring the controller online, this will require a BCX to do as well. Once the B3 is learned in and online, perform a reload to the controller and then a backup to flash. The only thing that will be reloaded will be the system variables. Another thing to think about is let's say you've already replaced the B3 and sent it off to repair. You've got it back and now want to put it back to its original location. That one is very simple and following the replacement steps above will suffice. Just remember that step 8 above you would make sure the Bacnet Device ID and the serial number match for the original unit integration. But if you wanted to add a new B3 controller to the same site and use the repaired B3 as a newly installed controller, just remember that the previously replaced B3 will have the Bacnet Device ID of the repaired B3 and you'll have to make sure that when manually creating a new B3 with the repaired B3 you'll have to make a new Bacnet Device ID that is unique. Rules to remember: Flush out used B3 controllers before adding to an existing MS/TP network or replacing a defective B3 Bacnet Device ID's must be unique for each given BACnet network  

Issue Microsoft Visual C++ Runtime Library Error After you install I/NET on a computer containing Microsoft Office XP or one of the Office XP programs, you may receive one of the following error messages: Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSDMN.EXE abnormal program termination Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSEARCH.EXE abnormal program termination Environment XP computers containing Microsoft Office or other loaded programs, one of which may be I/NET  Cause This behavior occurs if a program (not necessarily I/NET) conflicts with the Mosdmn.exe and Mosearch.exe files or with video settings, antivirus or 3rd party programs conflicting with your operating system. Resolution The Mosdmn.exe and Mosearch.exe files are part of the "Support for fast searching" feature in Office XP. This feature is similar to the Find Fast feature in Microsoft Office 2000. Fast searching uses the Indexing Service in Office XP to create a catalog of Office files on your computer's hard disk. To resolve this issue, use the following methods, as needed, in the order presented. Method 1: Clean Boot with Only MoSearch The Mosearch.exe (Microsoft Office Search Service) and Mosdmn.exe (Microsoft Office 10 Search Filter Daemon) Startup items may be conflicting with some other program (or programs) running in the background. Therefore, clean boot your computer with only MoSearch selected on the Startup menu to determine whether this program is the source of the conflict. To do this, follow these steps:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the General tab, click Selective startup. 4. On the Startup tab, click to clear all check boxes except for MoSearch. 5. Click OK, and then click Yes when you are prompted to restart the computer. 6. If the error message can be reproduced, repeat the preceding steps. In step 3, also click to clear the Process System.ini file and Process Win.ini file check boxes.   If the error message cannot be reproduced, this indicates that MoSearch is conflicting with some other program or programs running in the background. Follow these steps to locate the conflicting program:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the Startup tab, click to select one of the check boxes. 4. Click OK, and then click Yes when you are prompted to restart the computer. 5. If the preceding steps reproduce the error message, the last item added to the Startup menu is causing the conflict. If the error message is not reproduced, repeat these steps until all Startup menu check boxes are selected. 6. If all the Startup menu check boxes are selected and the error message is still not reproduced, start Msconfig again, and then click to select the Process System.ini file and Process Win.ini file check boxes.   Restart the computer. You may need to install a clean version of I/NET depending on your computer setup.   This is the solution for the Microsoft Visual C++ Runtime Library error with XP Office. Other solutions may entail removal or reconfigure of video drivers, antivirus programs, or other 3rd party programs conflicting with your operating system.

Issue A license violation alarm is shown in the alarm viewer even though the system has all licenses necessary. The alarm returns to normal without any action from the operator. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Enterprise Server / Central contacts the License Server installed on the computer to determine what licenses are available. The License Server will then contact the "Trusted Storage" on the computer which is created when activating the licenses and ask how many licenses are available. The issue comes when the "Trusted Storage" creates some metadata once a day.  The metadata is a file created showing which licenses are used at that moment.  This is not currently used but could be by a third-party client who is interested in the license information for the system.  When the "Trusted Storage" creates the metadata it will be busy and not answer the License Server.  This is when the license violation alarm will be activated.  The alarm will return to normal after the "Trusted Storage" has finished creating the metadata. Resolution An investigation is ongoing. This issue has been fixed in EBO 2022. Please refer to License Violation Alarm 

Issue Modbus slaves are programmed according to device documentation, but either the wrong values are returned or error codes complaining about invalid address. Product Line TAC Vista Environment Xenta 913 Xenta 731 Xenta 511:B Cause The XBuilder Device Editor has two ways to address modbus registers. The improper usage of these methods can cause communication problems because the wrong register is polled. 1. Fixed Address Blocks This method combines the function code and register address to produce a single number format that serves multiple function codes. This is sometimes referred to as numerical notation. A poll of a holding register uses function 03 and an address from 00 00 to FF FF. When using Fixed Address Blocks a message of function code 03 and address 00 00 is displayed as 40001. Due to this combination it is limited to 9,999 addresses per function code. Type Function Code  Address  Coil Status  01  00001-9999  Input Status  02  10001-19999  Holding Register  03  40001-49999  Input Register  04  30001-39999 When the device editor is using Fixed Address Blocks then the numerical number is parsed from the Register in the following way. Register Function Code Address 1-9999 01 Register - 1 10001-19999 02 Register - 10001 30001-39999 04 Register - 30001 40001-49999 03 Register - 40001 2. Function Code Tables (Discrete Input, Coil, Input Register, Holding Register) This addressing format is closer to the actual protocol and keeps the function code separate from the register address. It also provides full use of the addresses from 0 to 65535. Table Function Code Discrete Input 02 Coil 01 Input Register 04 Holding Register 03   If the wrong format is used it can result in failure to communicate because the wrong register is used. For example polling register address 40010 on function code 03 when it should have been address 9 on function code 03. Resolution The documentation of the product being interfaced with is the best guide on the register addressing and the format they use. If the documentation does not directly specify the information then use the follow hints to guide your selection: Hints to use Function Code Tables Addresses that fall on zero (0, 10000, 30000, or 40001) Non binary data that is less then 30001 or greater then 40001. Devices states it is J-Bus. Register address is displayed in Hexadecimal format. Hints to use Fixed Address Blocks Any address register above 30000 or 40000, unless it claims to be a JBus device. If it is still unclear which addressing format to use then experiment with read only data and value pages in the Xenta Servers. Pick a point that you can easily confirm the value, add both address formats to a device template, and then confirm the proper format with a values page. Once you know how to read one point the rest of the product documentation is easier to work with.

Issue When using the Modbus RTU X Driver on RS-485 what cable type should be used and what maximum distance would it give? Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RS-485 XDriver. bCX1, NC2 AS Cause Recommended cable type required. Resolution The Modbus RTU is a standard RS-485 network and you can use the same networking rules as per the Infinet network. As long as the baud rates are set the same you can even use an Infilink 200 or a B Link to act as a repeater. Unless the Third Party device manufacturer specifies different requirements the Belden 9182 or a similar cable that matches the Infinet specification would be suitable, again as per Infinet rules this would typically allow a maximum end to end distance of 1200 Meters. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue EcoStruxure Building Operation allows using a period embedded in the name of an object (i.e My.AnalogValue) and  the name of a binding variable in the Script program cannot contain a period.     In the Script program all the periods in the binding variable names have to be changed to a different character such as the underscore (_).   This in turn causes a problem for a programmer that has created many objects using the period in the names as it is now NOT possible to use the default name matching binding template. Product Line EcoStruxure Building Operation Environment Script Programs Enterprise Server Automation Server Cause Script programs do not allow a period '.' in binding variable names because the period has special functionality in the Script compiler. Resolution Create a new path matching binding template or edit an existing one to map the underscore to the period.     Here is a second example:   Name of point/value contains embedded '.' as well as spaces      This is what the binding variable would look like in the Script program   and here is the Path Matching Template

Issue Continuum Graphics (Pinpoint): How do point updates take place and how can I change the update interval and polling speed? Is it different for BACnet points? Product Line Andover Continuum Environment Pinpoint Graphics Bacnet Cause How do point updates take place and how can I change the update interval and polling speed? Resolution In Cyberstation V1.71 and greater, the graphics polling engine was significantly changed. Prior to this change, the Pinpoint application would poll the points within its graphic file directly. If several graphics were open, each graphic would perform its own polling, This engine also applied to Web.client. Each control on the graphic had a separate selection where you could set the polling rate on a per-point basis on the miscellaneous tab of each control. This was the only method to adjust the point polling interval. The main reason for the graphic engine change was for Web.Client graphics. Slow networks, multiple browsers accessing the same graphics, and slow browser machines could make Web.Client graphics unacceptably slow.   The current method to get data into graphics involves a separate graphics polling engine per workstation. When one or more graphics are opened on a workstation or a Web.Client IIS server, the graphics register the points into the polling engine on that workstation. The polling engine then begins updating the values and sends the data to the Pinpoint/web.pinpoint clients. After initially sending all the data values to the graphic, it then only sends the data that has changed since the last update in an XML document format. If several graphics are requesting the same point values, the data is only polled once for all the Pinpoint clients on that workstation or Web.Client. Efficiency was also achieved by registering the points in the polling engine which allowed the polling engine to decrease the number of data requests by 50% to retrieve the same data.   There are now additional settings to adjust the polling rates in a graphic. #11 General preferences "Time interval between requests" This is a global setting and affects all workstations. By default, all polled points which are in the polling queue are sequentially updated at a continuous rate with a default delay between requests of 30 milliseconds. It is often recommended to set this to 100ms (Additional considerations below  under Multiple Cyberstation graphics performance)   General Preferences are accessed by Right Clicking on the Continuum icon in the Windows system tray and selecting General Preferences     There are also a pair of settings in the workstation preferences: #24 Pinpoint active polling rate #25 Pinpoint inactive polling rate These settings are for each workstation individually and do not affect the polling rates of the polling engine, but merely determine how often the graphic requests data updates from the polling engine based on whether a panel is or is not the active window. Typically these settings can be left at their defaults R&D has indicated that #24 is not used as Pinpoint always uses the inactive polling rate whether the window is active or not. Therefore, adjust #25 "Pinpoint inactive polling rate".  It is recommended to set this to keep this at the default of 250ms.   Cyberstation Preferences are accessed by Right Clicking on one of the Cyberstations while logged into Continuum and selecting Edit   Multiple Cyberstation graphics performance Several workstations may be configured to display graphics that are pointing to the same controllers and the controllers being polled may be on a large Infinet or MSTP network. In this case, the controllers could be overwhelmed by simultaneous data requests from the different workstations, slowing down controller scans, the whole field bus and overall system performance. R&D indicates that when multiple Cyberstation Graphics are used there is some randomness as to how the polling requests are accomplished. If graphic or system performance is an issue, it is suggested that another 30 Milliseconds is added to the general preferences "Time interval between requests" (#11) and then measure system performance and add additional time if needed up to 500ms.   When using this setting it is necessary to consider how many Cybersations would be running simultaneous graphics. For example:4 workstations polling graphics simultaneously with "x" number of points in it for 1 Netcontroller could have about 20 requests per second (determined via Wireshark capture at the NC NIC) 30 ms per X 4 Cyber =120ms added In this case, the recommendation was to set the "Time interval between requests" value to 250ms for performance   Note: Individual millisecond settings in each point do not effect polling for the point. They are not used.   BACnet points Bacnet points can be managed differently. Continuum BACnet points can either be polled the same way that Standard continuum points are polled or by using a COV. Standard polling is done by using the point objects from the "Infinity" side of the object tree. If you want to use COV for the point updates which is much more efficient, you should use the "BACnet Points" in the graphic, from the BACnet side of the object tree. The polling engine will then subscribe for COV updates to the respective controllers. When the graphic is closed the polling engine will unsubscribe the COVs. Third-Party BACnet controllers have an additional method to adjust the poll frequency. If the third-party BACnet controller supports COV subscriptions, Cyberstation will subscribe to these points as COV's like the Continuum BACnet controllers however, if the devices do not support COV's their points will be polled. Since many third-party BACnet controllers cannot withstand frequent data requests, there are two additional settings on the BACnet device object editor. The settings are on the Details tab on third-party BACnet controllers only. 1. Max # of Async requests The max # Async requests specify how many requests we should send before we get a reply to the data request, or how many requests can I queue. Typically this should be set to 1. 2. Request interval in ms  The request interval setting will depend on the device. Does it use Ethernet or MSTP network architecture? Are you running "Enhanced MSTP"? How many third-party devices are on the mstp network that cannot run enhanced MSTP? Typically it would be safe to set this in the 1000 to 5000 ms range based on desired data update rates and the controller's capability to handle the polling.

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue Continuum installer throws a Error 1904, dll failed to register error during the installation process. Environment Continuum Error 1904 Failed to Write to Registry. Cause Virus protection is preventing the Continuum install from writing a .dll to the registry. Resolution Uninstall Continuum completely. Reinstall Continuum with all malware protection software disabled and using a Local Administrator user account. Check the compatibility matrix to ensure that the Windows OS you are using is compatible with the Cyberstation version

Issue Some actuators manufactured by Belimo are also available from Schneider Electric Environment Various Belimo Actuators: AF 230 AF 230-S AF 24 AF 24-S AF 24-SR LF 230 LF 24 LM 230 A LM 230 A-S LM 24 A LM 24 A-S LM 24 A-SR NM 230A NM 24A NM 24A-SR SM 230A SM 24A SM 24A-SR Various Schneider electric actuators, part no: 875-0000-010 875-0010-010 874-0000-010 874-0010-010 877-0000-010 875-0003-000 874-0003-000 875-1001-000 875-1003-000 875-1005-000 875-1007-000 875-1009-000 875-1011-000 875-1015-000 875-1019-000 875-1021-000 875-1025-000 875-1029-000   Cause Cross reference between various actuators of Belimo and Schneider Electric Resolution A cross reference table for these actuators can be found here (.xls).

Issue Project specifications call for there to be no default administrator password in the BMS.  Can the ACC user in Andover Continuum be deleted? Product Line Andover Continuum Environment Administrator password Continuum CyberStation Permissions Cause By default Andover Continuum always creates the ACC administrative user on all system but this is deemed unacceptable by some project specifications. Resolution The Andover Continuum default ACC admin user cannot be deleted, however it can be renamed and its permissions can be removed/amended.  

Issue Controller cold starts after power fail Product Line Andover Continuum Environment Continuum 1.x CX BCX Cause ACCRestartMode system variable is set to Cold Start Resolution Change the ACCRestartMode system variable. See the bCX1 Controller Technical Reference Guide Rev F  document page 55 onwards for an explanation of the changes that are required.

Issue How do I time sync my controllers to my workstations? Product Line Andover Continuum Environment Continuum site Cause The workstation will only synchronize its time to the controllers automatically when the controller is reloaded. It is common practice though to have the controller synchronize its time with the workstation on a periodic basis, commonly once a day. Resolution The only way to synchronize time between the Controller and the Workstation is through a Plain English program running the Workstation. This Program only needs to be created in one Workstation. Below is an example of the program as well as how to trigger the program to run. If Minute = 3 then Goto SetTime Else Stop SETTIME: Set NetworkName\LowestNodeCXName\Date to Date Stop E: Stop Note: This program needs to be triggered off the minute system variable. The program is a Fallthru program which resides in the CyberStation. You only need to do the lowest ACCNet Id controller in each Continuum network. Also ensure that the UTC offset has been correctly entered in every Workstation and BACnet device, and that each Network has the correct Time Zone setting.

Issue Need to use Mobile Apps to access EBO. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation Commission mobile application Building Operation Engage mobile application Cause What are the mobile apps available to use with EcoStruxure Building Operation sites? Resolution WebStation: WebStation is a web-based user interface for day-to-day operation in an EcoStruxure BMS. WebStation, V2.0 or higer, improves user experience by automatically adapting the user interface to the resolution of the device being used: desktop, laptop, tablet or smartphone, using Windows, Linux, Android or iOS, out-of-the-box using standard web browsers, without the need to install additional applications.  WebStation replaces the obselete Technician Tool app. Refer to: WebStation Overview Building Commision: EcoStruxure Building Commission mobile application (requires EBO V2 or higher, formerly eCommission) is designed to help airflow balancers, electricians, and technicians carefully and quickly pre-commission and commission SpaceLogic BACnet/IP devices and RP controller expansion modules. The Commission mobile application does not require a license for activation and is available at no cost to the user. It is designed for use with Android, iOS (Apple), and Microsoft Windows 10 and Windows 11 devices, and is available for download from Google Play, Apple App Store, and Microsoft Store. Refer to: Commission Mobile Application Engage: The Engage mobile application (requires EBO V3.1.2 or higer) enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. The Engage mobile application connects easily via BLE (Bluetooth Low Energy) to the RP-C controller. The application is compatible with RP-C (HVAC) and RP controller expansion modules (lights and blinds). The Engage mobile application is free and available for download from Google Play and Apple App Store.  

Issue Configuring a Xenta 527/NPR - Combo Product Line TAC INET Environment I/NET site with a Xenta 527 End of Commercialization of TAC INET Building Management System Products Cause How to configure a Xenta 527/NPR - Combo Resolution When setting up a Xenta 527 NPR or Combo Unit for the first time, there are six basic steps to commissioning the Xenta 527/NPR-Combo. These steps are described below. Connect the Xenta 527/NPR-Combo to 24 VAC power. Refer to the TAC Xenta 527 Installation Instructions (0FL-3956). Connect a PC to the Xenta 527/NPR-Combo. Attach a serial cable from the computer’s COM port to the RS-232 B port on the front of the Xenta 527/NPR-Combo. Refer to TAC Xenta 511/527/911/913 Handbook (0-004-7870) for complete instructions. Set the Xenta 527/NPR-Combo's communication parameters. Start a Hyper Terminal Session on your PC. Once the cable is connected, it will display the 527's default information. Note: The factory default login/password is root/root, at the dsh> prompt, type inethost then enter. Now add your I/NET information for reference host, etc. Restart the unit, when the "dsh>" prompt appears, type setip then enter this command will let you set its IP address and other basic parameters. Note: Refer to TAC Xenta Server Manual - TAC Xenta 527/NPR-Combo Supplement (0-004-7682-1) Chapters 3 & 5 for instructions. Once completed restart the unit again. Connect the Xenta 527/NPR-Combo to the Ethernet. Attach the Xenta 527/NPR-Combo to the network at the necessary location. Refer to Chapter 4, “Connecting the Xenta 527/NPR-Combo to your Network. Now ping the unit through the cmd prompt on your PC to verify that communications is taking place on the Network. If necessary, load the Xenta 527/NPR-Combo’s software. Note: The Xenta 527/NPR-Combo is delivered from the factory with preloaded software. If you need to reload this software, you can download it from the EcoXpert website. Before installing downloaded software, review its release information to verify compatibility with your hardware. Configure the Xenta 527/NPR-Combo to communicate with I/NET. In order for the Xenta 527/NPR-Combo to communicate with I/NET devices from across an Ethernet, you must first define basic communication parameters. Tip: You can now access the I/O configuration editor by opening NP Routers. From the Netplus Router Summary, select the router, modify it, and print the configuration for your records or the customers. Once these steps are followed, your unit should be online, communicating to the Network, and seeing all your controllers at this site.

Issue What is the BACnet attribute COV Increment and how to use it Product Line Andover Continuum Environment BACnet Cause The COV Increment attribute on a BACnet point is equivalent to the Threshold attribute of standard Continuum Infinity inputs. When a Continuum BACnet point is subscribed to by other BACnet devices using COV (Change of Value), its value must change by at least that COV Increment value before a new Value Notification will be sent out. Using this attribute will decrease network traffic especially on the MSTP network when subscribing to frequently changing values.  Resolution This CovIncrement attribute can be set in the BACnet point's Editor on the Basic Alarms Tab.   If you have a CyberStation prior to Version 1.8, setting this value from the point editor will not stay persistent in the controller after the controller is reloaded, it will default to 0. In order to keep the value after a reload, you will need to write a PE program to set the desired value after a reload. The program should be Autostart and Fallthru. A sample of the program is below: Line SetCov Writeproperty("Full Bacnet Path to Point", CovIncrement, "Desired Value") Stop If you have several points that need the CovIncrement set, you would just add the additional lines into this program.   In 1.8 or greater, this program is not needed as these attributes get sent to controller on a reload. Suitable initial CovIncrements still need to be added to each BACnet point however as they default to 0.

Issue Replacement of ARE, ARX and ARM rotary actuators Product Line Field Devices Environment Satchwell ARE1xxx Satchwell ARE2xxx Satchwell ARE7xxx Satchwell ARX1xxx Satchwell ARX2xxx Satchwell ARX7xxx Satchwell ARM1xxx Satchwell ARM2xxx Satchwell ARM7xxx Cause Obsolescence of Satchwell ARE, ARX and ARM actuators. Resolution ARE actuator                                                               Replaced by ARE1301                                                                          MD20A-24 (p/n 875 1029 000) ARE1302                                                                          MD20A-24 (p/n 875 1029 000) ARE2301                                                                          MD20A-24 (p/n 875 1029 000) ARE2302                                                                          MD20A-24 (p/n 875 1029 000) ARE2303                                                                          MD20A-24 (p/n 875 1029 000) ARE2304                                                                          MD20A-24 (p/n 875 1029 000) ARE2351                                                                          MD20A-24 (p/n 875 1029 000) ARE2352                                                                          MD10A-24 (p/n 875 1019 000) ARE2354                                                                          MD10A-24 (p/n 875 1019 000) ARE2355                                                                          MD10A-24 (p/n 875 1019 000) ARE7301                                                                          MD20A-24 (p/n 875 1029 000) ARE7303                                                                          MD20A-24 (p/n 875 1029 000)   ARX actuator                                                               Replaced by ARX1201                                                                          MD20B-24 (p/n 875 1025 000) ARX1202                                                                          MD20B-24 (p/n 875 1025 000) ARX2201                                                                          MD20B-24 (p/n 875 1025 000) ARX2202                                                                          MD20B-24 (p/n 875 1025 000) ARX2203                                                                          MD20B-24 (p/n 875 1025 000) ARX2251                                                                          MD10B-24 (p/n 875 1015 000) ARX2252                                                                          MD10B-24 (p/n 875 1015 000) ARX2253                                                                          MD10B-24 (p/n 875 1015 000) ARX7201                                                                          MD20B-24 (p/n 875 1025 000)   ARM actuator                                                             Replaced by ARM1601                                                                        MD20B-230 (p/n 875 1021 000) ARM1602                                                                        MD20B-230 (p/n 875 1021 000) ARM2601                                                                        MD20B-230 (p/n 875 1021 000) ARM2605                                                                        MD20B-230 (p/n 875 1021 000) ARM2606                                                                        MD20B-230 (p/n 875 1021 000) ARM2607                                                                        MD20B-230 (p/n 875 1021 000) ARM2651                                                                        MD20B-230 (p/n 875 1021 000) ARM2656                                                                        MD20B-230 (p/n 875 1021 000) ARM2657                                                                        MD20B-230 (p/n 875 1021 000) ARM7601                                                                        MD20B-230 (p/n 875 1021 000)   Options To fit replacement actuator to an existing MB screwed valve use linkage kit - LMD/MB (p/n 914 1071 000) To fit replacement actuator to an existing MBF flanged valve use linkage kit - LMD/MBF (p/n 914 1070 000)   If 1 end switches are required, the reference is MD-S1 (p/n 914 1060 000)  If 2 end switches are required, the reference is MD-S2 (p/n 914 1061 000)