Building Automation Knowledge Base

Issue Time schedules are not switching off according to the workstation time. Time schedules are delayed. Product Line TAC Vista Environment TAC Vista, Xenta Servers and Controllers (280/300/400) Cause The Time in the TAC Xenta 911 and TAC Xenta controller is not the same as in TAC Vista Server. Resolution To check the time in the TAC Xenta controller follow these steps : Browse to the TAC Xenta controller Right Click on the controller and select Properties Select the Information Tab. This will display the time in the TAC Xenta controller To check the time zone of the TAC Xenta controller select the time settings Tab. Once the TAC Xenta controllers have been set in the right time zone TAC Vista server will sync them to the correct time. By default this occurs every 10 minutes The final step is to ensure the time and time zone of TAC Vista server is correct. To do that locate your TAC Vista Server object and right click then select properties.  Select the Information Tab to show the server time. This time is governed by the PC time so to adjust the PC time through Windows.

Issue MP/RP-x device is not pushing firmware down to Room Units (RU) when sensors are attached to the sensor bus. Disconnecting and re-connecting the RU does not help Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause The MP-X controller's file system has been re-initialized and the Room Units firmware files deleted. One case under which this will happen is when the MP/RP-X is factory reset.   The Device Report can be used to confirm whether the files exist in the device or not.   If Room Unit files are not shown in the report then no download to the RU will take place. Resolution Perform an upgrade on the MP/RP-X device, upgrading the device to the same version that is already running will resolve the issue.

Issue Distinguishing whether an xDriver-enabled commport on a controller is set for Modbus RTU or Modbus TCP/IP. Environment CX9900, CX9940 CX9680 bCX4040 Cause How does one know if the xDriver-enabled commport on a controller is for Modbus RTU or Modbus TCP/IP? Resolution Open the controller editor and go to the Options tab. At a minimum the Modbus RTU XDriver, like all Xdrivers, requires Bit 0 for the commport be Xdriver enabled. The most common example would look like this: Xdrvr Commx: 00000001(####). In the above example x = commport number. The four digit number in parentheses indicates whether an Xdriver file is loaded into the port. If it is 0000 then no Xdriver file is loaded into the port. A number such as 4767 corresponds to "Xdriver Valid" line at the end xdriver XDR file. You can edit the XDR file with a text editor and go to the bottom to see this.   In addition to Bit 0 being enabled for the commport, the Modbus TCP/IP Xdriver requires Bit 3 to be Xdriver enabled.  A common example of this would look like this: Xdrvr Commx: 00000009(####). The 00000009 is in hexadecimal format -  converting this to an 8-bit binary number you get 00001001. The furthest right bit is Bit 0 and the 4th from the right is Bit 3. Both are set to 1 which means they are Xdriver enabled. For a further explanation see page 15 of the linked Modbus TCP/IP Xdriver User Guide.   Note: Since Bit 0 is enabled in both of the above examples, the Modbus RTU Xdriver will work on either. But only the second example will load the Modbus TCP/IP Xdriver.      

Issue Need Menta programming that can be used to monitor a pulse signal coming from a water meter, electric meter, or gas meter. Environment Menta Vista Cause A Menta program that can be used to monitor water, electric, or gas metering. Resolution The program below is set up to receive a pulse signal for three different meters. Click the picture of the Menta macro below to download the source file.

Issue Is there a way to populate an array in the declaration line as in other programming languages i.e. Numeric numbers[4] = {1, 2, 4, 8}? Environment StruxureWare for Building Operation Script Editor Cause When defining an array in Script Editor the user may wish to populate the array with initial values. Resolution The way to populate an array in Script Editor is to initialise each element individually.

Issue Is it possible to create a switch, in TGML, which has a popup dialog to confirm the action taken (Yes/No)? Environment TGML editor 5.1.X Vista workstation 5.1.X Webstation 5.1.X Cause A customer wishes to confirm changes before applying them, to avoid setting variables by mistake. Resolution In the components library in TGML editor, there is a check box component which has a confirm function. Drag & drop the component onto the workspace and study the code. This can be used as a basis for a switch component.

Issue Is it possible to prevent a 3rd party BACnet Operator Workstation (BOWS) from deleting the BACnet objects in an Enterprise/Automation server? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Current version of EBO/SBO puts the responsibility of creating & deleting BACnet objects to the site administrator.  The enhanced security on this issue will be added in the later version. Resolution The following video demonstrates how to protect the BACnet objects in ES/AS by utilizing shortcut objects.    

Warning   Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Issues upgrading Automation Servers (AS, AS-B, AS-P) connected to an Enterprise Server (ES) from versions prior to 2.0.x to a version that is 2.0.x. ES and one Automation Server will upgrade but no others connected to that same ES will upgrade and will show an error while attempting to download the new software.  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v1.9.x Building Operation Enterprise Server v1.9.x   Cause If the Automation Servers within the ES environment are not uniquely named, and/or are the same name as the ES, an error will be received if upgrade is attempted stating "Deploy upgraded database failed". Resolution As found within the Enterprise Central section of the 2.0 Release Notes, "All servers must have unique names".   *NOTE* Renaming the Automation Server will break any paths to that Automation Server, as such they will need to be corrected.   Follow these steps to address this issue: Prior to upgrading any devices within the environment, check for and find any servers with non-unique names Detach the Automation Server (with the naming identical to the ES or any other server) from the ES Rename the Automation Server with a unique name Correct any binding path issues Reconnect Automation Server to the ES Upgrade the environment to 2.0.x

Issue 3rd party BACnet Gateway can be seen  and points found when performing "send to database" but the Life Safety points do not show up. Product Line Continuum BACnet Environment Andover Continuum, EcoStruxure Building Operation Cause We do not currently support the BACnet Life Safety objects with the Andover Continuum or EcoStruxure Building Operation product lines Resolution Use an object that we do support, either an AV (Analog Variable) or MV (Multistate Variable) would probably suffice as long as the 3rd party Gateway can provide this instead of the Life Safety objects. See our BACnet PICS statements at the link below that show what BACnet objects each of our products support. https://www.bacnetinternational.net/btl/index.php?m=20

Issue Cannot find third party bacnet IP devices Environment BACnet Third party device Find bacnet devices Cause Default router address was incorrectly configured in the third party device. Resolution Corrected the default router address configuration in the third party device.

Issue Bind to more than 13 unique LON devices without running out of address table entries Product Line TAC Vista Environment LonMaker NL220 LNS Cause Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. Resolution Open the Network Variable Connection tool by right clicking on a function block in LonMaker and selecting Connect. Set the Connection Attribute to Repeated to use this as a starting point. Hit the Properties button.    On the Connection Details window, select New. Give the New Connection Description a name. "Broadcast" is a good description.    Hit the Advanced button for this connection type.    Set the Use Broadcast setting to Yes.   Try binding some outputs with this new connection type and it will reduce the number of address table slots consumed.

Issue Procedure to activate the Add-on reports module. Environment Continuum Add-on reports module. Cause Received an Activation Code from the COE Team, need to know the procedure to activate the Add-on reports module. Resolution You will receive an Email from the COE Team with the Activation Code along with Instructions on how to activate it. For your Convenience the instructions are below. ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files\Continuum_Reports" Enter in lower case: reports key writer Enter the activation code. (Note: Case sensitive)   -(OR)-   ACTIVATION INSTRUCTIONS - CONTINUUM REPORTS INSTALLED IN C:\PROGRAM FILES (X86) Make sure Continuum is not running Make sure Continuum Reports is not running Launch a DOS Command Window CD "Program Files (x86)\Continuum_Reports" Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)Activation Instructions - Continuum Reports installed in C:\Program Files 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files\Continuum_Reports" 5. Enter in lower case: reports key writer 6. Enter the activation code. (Note: Case sensitive) -or- Activation Instructions - Continuum Reports installed in C:\Program Files (x86) 1. Make sure Continuum is not running 2. Make sure Continuum Reports is not running 3. Launch a DOS Command Window 4. CD "Program Files (x86)\Continuum_Reports" 5. Enter in lower case: reports key writer c:\progra~2\continuum_reports 6. Enter the activation code. (Note: Case sensitive)

Issue What amount of memory is used for DPU Resident Individuals in the DPU\SCU controller? Product Line TAC I/NET Environment I/NET Seven - Access control DPU7910A, DPU7920, DPU7920 w/DPU48K, and SCU1284 Cause Need to understand the memory allocation and implications of using DPU Resident settings with both the DPU or SCU hardware devices. Resolution To set the Individual as DPU Resident the DPU Res. checkbox needs to be checked in the Individuals editor as shown below (red box) shown below.     In the table below from TCON300 05/17 Chapter 9-14 shows the memory allocation for a 7910A DPU or DPU7920   If you have a selection of between 6000 to 12000 Resident User Individuals (i.e. set as DPU Resident) in the system you can ONLY have between 3262 to 2887 Cached users respectively stored within a properly communicating system.  If the DPU is offline to the Sub LAN Interface (SLI) these cached users will be reduced as the requirement for the DPU storage capacity will need to store 'offline' messages as shown under the "Messages" column.     In the table below from TCON300 05/17 Chapter 9-15  shows the memory allocation for a SCU1284 DPU or DPU7920 w/DPU48K   If you have a selection of between 6000 to 12000 Resident Users Individuals (i.e. set as DPU Resident) in the system you can have the full quota of 48,000 Cache Users respectively stored within a properly communicating system.  Unlike the DPU7910 or 7920 if the DPU is offline to the Sub LAN Interface (SLI) there is no change to these cached users and there is more 'offline' message storage as shown under the "Messages" column. For further information on DPU Caching and memory management read from Chapter 9-11 in TCON300-05/17

Issue Some links in graphics are unresponsive on Advanced Display when running EBO 1.9.4. Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V2 Building Operation Advanced Display V3 EcoStruxure Building Operation v. 1.9.4 Cause The links that are unresponsive are trying to open the target in a floating window. This is not supported on Advanced Display with WebStation when using EBO v. 1.9.4. More specifically the graphics script function is not supported under the conditions mentioned above. invoke("Link", "OpenInFloatingWindow"); Resolution Use alternative arguments other than "OpenInFloatingWindow" such as "OpenInNewWindow". See the WebHelp Section Invoke Function for more information about the Invoke function.

Issue LonWorks Device is Offline in Vista, but Online in LonMaker. For Xenta Programmable devices refer to Xenta Programmable Device is Offline in Vista but Online in LonMaker. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation LonWorks Device Cause If the Vista database has some LonWorks devices that are not communicating, one cause could be due to changes in the system such as moving controllers to a new channel for example. Updating the Vista database with the system plug-in might not fully overwrite all the node properties causing the device not to communicate in Vista Workstation even though it is communicating in the LNS database. Resolution Delete the LonWorks device from the TAC Network in the System plug-in. "Update Vista Database" in the System plug-in to remove the device or devices from Vista Workstation. "Update TAC Network" to add the devices back to the TAC Network. "Update Vista Database" again to add the devices back to the Vista database.

Issue Site Access Control lockdown for the entire complex. But, also allow certain cards to override certain doors during an emergency situation. Environment I/NET site with access control Cause There is a requirement to lockdown an entire complex with a single toggle switch, but allow First Responders access to certain locked doors in the building. Resolution  There are two different Demo programs for this process One Link program (Download One Link Zip file): MCI -- 7798 DPU – SCU1284 (2 addresses) A maintained switch SPDT   Two or more Links program (Download Two Link  Zip file) MCI – 7798 Link1 MCI – 7793 Link2 – Channel “B” SCU1284 (2address) Link1 SCU1284 (2address) Link2 – On second channel A maintained switch SPDT Each of the above zip files have the following inside: Note: This would be restored to your test bench, and then configuration implemented into a production site.

Issue Advice on the configuration of a Sigma DNN (Distributed Network Node) when connecting it to a "Flat" Ethernet network. The DNN provides a communications route to Sigma controllers connected to an Ethernet or ARCnet sublan. Product Line Satchwell Sigma Environment Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice. Resolution A "Flat" Ethernet network is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. On this type of network the DNN will only require an IP address and Subnet Mask to be entered. This information and details of the DNN's "Default Server" are added to the device using the SDCU (Sigma Device Configuration Utility). If the DNN has RIP (Routing Information Protocol) enabled then it will broadcast the route to the sublan onto the network, if RIP is not enabled, then a persistent route must be added to the Sigma server. Please refer to Persistent routing on the Sigma server for more information.  To modify the DNN RIP settings, use the Pocket Terminal programme. RIP is enabled by default. To disable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPD 5 and select send. To enable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPE 5 and select send. To review the status of RIP Enter RIPS and select send

Issue Is it possible to rebuild a  Continuum Database from the BACnet controllers in the field? Environment Continuum BACnet Cause The SQL server has failed and there are no acceptable backups of the ContinuumDB to restore once the server has been repaired. The controllers in the field are still functioning and have valid application programming. Resolution Although it is possible to recover the database from the field controllers, the best method of recovery is to have a recent backup of the ContinuumDB and to restore this once the Server gets fixed up. You can load the data from your field controllers into a new Database. Note that all objects will have their name now set the same as the alias, as this is what is stored in the controller. To load the bCX and attached b3's, do the following with a blank database. 1. Create and configure a network folder. 2. Create and configure you bCX1 device object to bring it online in the Infinet view. 3. Right-click on the bCX1 object in the Infinet view and select "Send to -> Database". 4. This will save the controllers database to a temporary dump file on the Workstation then load from this dump file, creating the objects and populating the database. 5. When done, this should have also found all b3's that were defined in the bCX1 and loaded their contents as well. 6. This will load the BACnet objects as well as the Infinet objects. Note: Recreating the Network from the field does not recreate any objects that were stored in Workstations or in folders off the root. These objects; such as listviews, programs, reports, etc...; are not stored in the controllers and will need to be recreated. 

Issue BACnet Schedule does not change the Digital Value when the Value attribute of the DV is bound to the Schedule Environment StruxureWare Building Operation BACnet controller B3xxx series. Cause When a user creates the BACnet Schedule object in the b3 controller, if the Default_Value attribute of the BACnet Schedule in the b3 is not configured, the schedule's default value is left as "NULL".   And later on, when the Schedule turns to True, it sets the bound DV value to Active. But when the Schedule turns to False, it tries to change the bound DV value to NULL (as it is the default value of the schedule),  which fails as it is not allowed to set the DV value to NULL.  As a result, the bound DV value cannot be changed and it keeps its previous value "Active" without being able to change it any longer. Resolution Set the Default Value attribute of the BACnet Schedule object from NULL to False as below: - Right click the BACnet Schedule object in the b3 controller and select the Properties. - In the Basic tab of the Properties window, scroll down all the way to the bottom and locate the Default Value attribute. - Click the setup icon on the right side of the attribute, it pops the Default Value window. - Uncheck the Null checkbox and confirm the Value now shows False. - Click OK from the attribute window, verify the Default value is False now, click OK from the Properties window.

Issue Reset Instructions for 1200 Series SCU Product Line TAC INET Environment SCU 1200 series controllers I/NET Cause Need to restart SCU, perhaps after a reload of firmware or dip switch settings Resolution Follow the written instruction carefully.   Reset Instructions: Locate the 3-pin connector labeled P610 and the reset push button switch. Refer to the above diagram. Momentarily short P610 pins 1 and 2 while simultaneously pressing the reset push button switch. (Note: P610 pins 1 and 2 are the pins located nearest the dip switch.) Re-download the proper BIN file to the SCU.