Building Automation Knowledge Base

Issue After upgrading to Niagara G3 3.8 (from 3.7), nested PxIncludes now only partially load and very slowly.  They are not all entirely missing.  After a screen refresh, most will load except for a random few.  Also, they may load all at one moment but not the next.  The same Px file in version 3.7 loads faster with nothing missing. Environment Niagara G3 / AX version 3.8 Cause PxInclude caching is disabled by default in 3.8. Resolution This issue was addressed with the release of an updated bajaui module - version 3.8.38.3.  This version re-enables PxInclude caching.  Download it here.

Issue The TGML page is dynamic but looks static. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista StruxureWare Interface Cause In the Release Note, page 30 says: It is possible to navigate to a TAC Vista Webstation TGML Graphic through a link in a SmartStruxure TGML Graphic. To achieve this connection a link object is created in the SmartStruxure TGML Graphic which is linked to a SmartStruxure hyperlink object that holds the TAC Vista Webstation TGML Graphic page address. Example of a hyperlink objects address in SmartStruxure that is linked to a TGML Graphic in TAC Vista: HTTP://ip_address/webstation/LoginPage.aspx?page=TgmlGraphicsPage.aspx?objectId=3074949137 Note: This will always require a login by a valid TAC Vista user, even if the TAC Vista Webstation auto login feature has been activated. Resolution The example link above is referring to a static page. For example, if the TGML page is dynamic, you will see the following in the copied link (see bold). HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 You can also read the following in the release note: In order to determine the TAC Vista Webstation URL for a TAC Vista Webstation TGML Graphic the following TAC Vista Web Setting configuration must be in place: Optimized TGML Loading is deactivated Folders pane is set to Standard HTML With these settings it is possible to right-click a TGML object in the folders pane and select "Copy Shortcut." This will copy the TAC Vista Webstation URL to the clipboard and it can then be pasted into a SmartStruxure hyperlink object address field. After the shortcut has been pasted, it will have to be modified in order for the TAC Vista TGML Graphic to be displayed properly in SmartStruxure. The modification is marked with bold in the example below: Copied: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 Modified: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 If the link you copied was a dynamic TGML the link will look like: HTTP://ip_address/webstation/TgmldynamicGraphicsPage.aspx?objectId=3074949137 and should be modified as this HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 Also reference the TAC Vista Webstation Graphics Links and SmartStruxure Integration tool on the Community.

Issue ACCDataService.exe in ITP.DLL crashes when any function is calling another function. Product Line Andover Continuum Environment Continuum 2.0 Plain English Cause A PE Function is called from within another PE Function. Resolution To resolve this issue the following steps need to be followed: Do not call up a PE function from within another PE function. Copy the script code function from the second function and put it directly into the first function.

Issue Webstation shows 12 hour AM/PM time and U.S date format even when the PC is setup to 24 hour and UK date formats   Environment Webstation Localization Cause Webstation does not get its time and date format from the Windows PC, but from the installed and selected language pack. To change the format, you need to install the language pack for your country or language. There might not be language packs for all languages and countries, and unfortunately there is currently no option to UK/ European English in Webstation. Resolution The workaround is to install a modified English language pack. Download and save and install one of the following two zip files, and install as described below. DO NOT UNZIP THE FILE! UK English 24 hours format with time zone indication UK English 24 hours format without time zone indication    While you are logged into Webstation, Select Settings, then Add or remove language Select "Choose file" and browse to the location you downloaded the language pack .zip file to and select ok Then under settings, select "Change regional settings" You should now have the option to select "English (UK) (en-UK)"  you should now see that the date and time have now changed to UK format.

Issue Can DDC lines in ASCs be displayed on I/NET Graphic Pages? Product Line TAC INET Environment I/NET .gpg graphics DDC Lines Cause DDC Lines are represented different from Resident I/O points. Resolution Yes. The following Lines are the most common to view: Line 1 = Active Cooling setpoint Line 4 = Active Heating setpoint Line 5 = Active setpoint (*see below) Line 10 = Cool CFM setpoint (only on VAV-X2) Line 12 = Airflow setpoint (only on VAV-AX and X1) Line 14 = Mix Air (only on AHU w/ mixed air econ. control) Line 15 = Warm CFM setpoint (only on VAV-X2) Line 26 = Cool Air Flow (only on VAV-X2) Line 27 = Hot Air Flow (only on VAV-X2) * Line 5 should be the same as the value displayed on the STR-250, I/STAT, M/STAT. It will display either line 1 or line 4's value, whichever one is closer to the current space temperature. If average is selected for SPD, then line 5 will show that averaged value even though the controller is operating on the actual heating or cooling setpoint. For a complete listing of all ASC points and lines, see ASCLines.pdf.

Issue How can I get audible alarms with I/NET 2000? Environment I/NET 2000 site Cause How can I get audible alarms with I/NET 2000? Resolution First, in Control Panel, sounds, ensure that a sound is selected for default sound. That is the sound I/NET will use. Second, if you cannot hear anything, and you have the amt configuration set for either timed or constant, it does work with the small speaker inside your pc. The trouble is, it may be barely audible or your pc may not have a little speaker inside. If so, you may want to purchase a sound card and speakers.

Issue The documentation on The Exchange differs from the documentation included in the packaging. Neither document shows the full capabilities or wiring options of the transmitter. Environment STO300 Cause The supplier recently changed the PCB and as a result, all of the 300 model plantroom type sensors now offer dual outputs (current and voltage). Since the part number designation is for current only the documentation included in the packaging only shows this configuration. To further complicate matters the specification and installation materials on The Exchange have not been updated to reflect the changes at this time Resolution The installation instructions included in the product packaging should always be referred to when installing these transmitters. The latest installation instructions can be downloaded here. If the new 0-10VDC output feature is required please follow the diagram below for wiring and DIP switch configuration.

Issue How do I create a Multi-Columned report for an A-Sample Trend? Using I/NET Seven and Sub Reports (Seven Reports) Product Line TAC INET Environment I/NET Seven 2.21 and below Cause In most BMS systems the most common report was a tabular (or column report) of data. Seven Reports (Crystal Reports) did not provide this facility easily.  Although it can be achieved using the subreport feature within Seven Reports.   Resolution The Steps to create this report are discussed in the following link. Subreports process w screen captures.doc

Issue When I/NET is installed for the first time and MSDE begins to install, it fails on the "renaming of the SQL folder" partly due to "Read Only" rights to the folder SQL is installed in. "The error message has this reference; SQL: MSSQL$MICROSOFTBCM cannot be renamed". The install of I/NET stops at this point. You do not have the option to use "Add Remove Programs" to uninstall the previous install of SQL.   Product Line TAC INET Environment DELL PC computers I/NET Seven Cause Loading I/NET on a new Dell PC with XP Pro as its OS that already has an instance of MSSQL installed.   Resolution The solution is to go to Manage\Services\Applications\Services... to Stop and or Disable (3) current instances of SQL running. Right click on "MSSQLSERVER" and click on Properties Click on the Startup type, then select "Disabled" Click Apply and then repeat for MSSQLSERVERAD Helper and SQLSERVERAGENT. Close the Manage window Begin the I/NET Seven install again. MSDE will install correctly as well as the rest of the I/NET Seven. This problem has only been seen on DELL PC computers.

Issue Can a 7798C be used in an I/NET 2000 System? Product Line TAC INET Environment I/NET 2000 I/NET Seven rev 1.16 and above 7798C SLI Cause AMT is different in I/NET 2000 than it is in I/NET Seven and any message and transaction from this SLI will not report correctly. Resolution This SLI cannot be used in I/NET 2000.  Even if 7798C Bin files are loaded into I/NET 2000, the SLI will not work. This SLI is designed to ONLY operate correctly in I/NET Seven Rev 1.16 and above.

Issue No alarms are displayed in the Niagara R2 Alarm Console. Environment Niagara R2 Cause Generally, this condition indicates that the Alarm Console is not properly configured with the Niagara station information. Resolution To configure the Alarm Console: Open the Alarm Console From the Address menu, select Enable Edit Type the appropriate password to enable editing (by default, this password is blank) From the Address menu, select Add Address. An input dialog is displayed that allows entry of the new station address record information In the Station Name box, type the name given to the station node that will be monitored In the Host Address box, type the computer name running the station. Use either the station host name or the actual IP address of the computer In the User Name box, type the user name for a user account that exists in the station. Typically, this is the same name (user account) used to access the station in WorkPlace Pro In the Password box, type the password for the station’s user account In the Confirm Password box, type the user’s password again to confirm it Click OK Click the Stations tab to verify that the new station address record was added to the Address Book. Note that if the new station address record appears red, a restart of the station is required for alarms to be routed to the console

Issue When WebReports is installed, two users called "appuser" are created. One is a local Windows user, and one is a SQL user. Product Line EcoStruxure Building Operation Environment WebReports User accounts Cause These users are or have been needed by WebReports Resolution EBO version 2.0 and above: the Windows user account "appuser" is no longer required to operate WebReports.  It is only a requirement during installation. SBO/EBO version 1.8 and above:  In SQL, the "appuser" user account has been removed as it's not essential for the Web Reports to operate correctly. In these versions, if an upgrade from an earlier version is performed and this user account is still present, it can be safely deleted /disabled.     In all other versions: The local Windows user account ([PC_NAME]\appuser) is used for importing report packs (RDL files) and synchronizing between WebReports and Microsoft Reporting Services.   For more information about this account, refer to SmartStruxure WebReports Installation Errors (1001 while importing report pack). To change the password for this Windows user, refer to Changing Report Server "appuser" password.    

Issue What options are NOT supported by Signal XP? Product Line TAC IA Series Environment SIGNAL software installed in PC Windows XP Professional. Cause Knowing the product features helps sum-up what SIGNAL can manage day-to-day operations. Resolution Below are features not supported with Signal XP: Networking BAS third party support (Andover, Metasys, Trane, …) DataTalk for Windows CTI port expansion card Foreign language capability

Issue I/NET Message Masking Product Line TAC INET Environment I/NET site pre 2.13 Cause Message Masking with Rev. 2.13 and prior Resolution In Rev 2.13 a new configuration option was introduced, Server/Remote Client. The Server should be set to mask for all Links’ messages and AMT similarly set. If this configuration is chosen, it will be necessary to use filters in AMT if it is desired to display only selected link messages on a host. In Rev 2.12 and earlier versions, the message masking for the links could be set so a host would receive messages from only selected links. AMT on those hosts with masking similarly set would therefore display messages from only those links. An example of using masks to route messages for File master//Equalized Clients is shown on link below. There are three links and three hosts. It is desired that Host 1 see messages and interact with controllers only on Link 1. Host 2 will handle Link 2 and Host 3 will handle Link 3. Link 1 controllers can use Group 1 bits 1 and 8, Link 2 controllers use Group 2 bits 1 and 8, and Link controllers use Group 3 bits 1 and 8. Host 1 will then set Group 1 bits 1 and 8 for link 1. Host 2 will set Group 2 bits 1 and 8. Host 3 will set Group 3 bits 1 and 8 (these masks are arbitrary and were chosen for illustration only). AMT masking is set the same for these hosts. File master/Equalized Client Server/Remote Client In the Server/Remote Client configuration all messages are routed to the Server (Host 1). AMT can then be configured on a host to show messages from only selected links using the filter option in AMT. To display messages from only Link 1 on the Server (Host 1) set up a filter to select messages from just Link 1 as shown in the linked document below: The Start address has to be an address before the start of the link desired in order to show all messages for the link. In this example it is assumed there are no devices on the link 00. If there were, set the Start to the highest possible address that is not used, e.g. 00633109. Message Masking

Issue Sigma remote client software has been added to new PC and the client will not connect to the Sigma server properly.  On some occasions the connection occurs but the Sigma Client Menu options are not available. Environment Sigma remote client (up to version 4.04), Windows XP, Windows 2000. Cause Sigma Software up to version 4.04 uses the Windows Share to allow the Sigma Remote Client to connect to the Sigma server.  The Windows share is not working correctly. Resolution 1.  Upgrade to Sigma 4.05 or above as this no longer uses the Windows Share to connect remote clients to the server. 2.1  If the software can't be upgraded then enable file Sigma file sharing between the PC’s by using a common Windows username and password on all the Sigma server/client PC’s. 2.2  Check the firewall/network will allow TCP port 3614 to be passed, unblock if necessary. 2.3 If the PC’s are on a client network then you may have to discuss this with the sites IT people to allow TCP port 3614 to pass through their routers/firewalls. 2.4 If the Sigma communications needs to pass through a firewall then port UPD 49152 will need to be unblocked.

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 Services for assistance. Issue When upgrading to 1.8.1 a Xenta Central Schedule that resides outside the LonWorks network it is not upgraded to the current version. If the upgrade is attempted it breaks all the Xenta time schedule bindings with the Xenta Cental Schedule. Product Line EcoStruxure Building Operation   Environment StruxureWare Building Operation 1.8.1   Cause During the LonWorks Pre-upgrade only the objects under the LonWorks networks are upgraded. If the Xenta Cental Schedule is located outside the LonWorks network this is not included in the upgrade process. Resolution Options to resolve this issue. Before upgrading to 1.8.1 If the site uses Xenta Central Schedules, then use the server Hotfix 1.8.1.5101 to upgrade all the servers. Please contact Product Support and request Hotfix 1.8.1.5101. After upgrade to 1.8.1 There are two options in this case: You can delete the Xenta Central Schedule and add a new Xenta Central Schedule. You are then able to bind the Xenta Schedules to the new Xenta Central Schedule.   If there are many Xenta Schedules that refer to a Xenta Central Schedule you can use the export function to resolve the problem as shown here Export the  Xenta Central Schedule as shown here Once you have exported the Xenta Central Schedule you need to edit the exported XML file with Notepad++ and change the Xenta Central Schedule attributes from "lon" to "lon2".  This is what the change should look like Once this change has been made the XML File can be saved ready for an import to the Server. Delete the existing Xenta Central Schedule from the database, making sure you check the box keep references. Then import the edited XML to the server and this will re-establish the Xenta Central Schedule binding with the Xenta Schedules.

Issue S-E Forta M700 Actuator unable to be mounted on S-E VGS211F Valve Body . Environment S-E Forta M700 Actuator mounted on S-E VGS211F Valve Body  Cause S-E Forta M700 Actuator unable to be mounted on S-E VGS211F Valve Body due to absence of S-E VGS211F Valve Body Spindle Adaptor. Resolution 1.  Install S-E VGS211F Valve Body Spindle Adaptor prior to installation of S-E Forta M700 Actuator. The S-E VGS211F Valve Body is supplied with a Valve Spindle Adaptor. The Adaptor is illustrated in the S-E Forta M700 Installation Instruction (OFL – 4340 – 001). It is particularly important to ensure that this Adaptor is fitted to the Valve Spindle, as its absence will prevent the M700 Actuator from being mechanically connected to the Valve Body Spindle.

Issue ADI FSCO Panel Integration Product Line TAC Vista Environment ADI FSCO Panel Xenta 913 Cause Integration to an ADI Fire/Smoke Control Panel. Resolution This document details the process for integrating an ADI FSCO Panel (www.adipanel.com) with a TAC Xenta 913 through the ModBus serial interface. Comm Settings In XBuilder, right click the "RS232-485 A" Serial Port, add a ModBus Slave interface. The comm settings necessary are shown below:   The ADI FSCO Panels speak RS232. The 913's baud rate is adjustable in XBuilder from 300 to 19200. The panel's baud rate is adjustable via DIP switches from 2400 to 19200. There is no right or wrong speed, they just need to match. Parity is even, 7 data bits, 1 stop bit, and ASCII framing mode. On the ModBus serial line slave, right click and add a device. If it has not been created yet, you will need to create a device template first. The device requires a ModBus address. With an ADI FSCO Panel, this address is always 1. Physical Connections The RS232 port is an RJ45 port on the left front of the 913 labeled “A.” If you are creating your own patch cable to tie into the ADI FSCO Panel, the pin-out is as follows:   1 - White Orange 2 - Orange 3 - White Green – TXD 4 - Blue – RXD 5 - White Blue – GROUND 6 - Green 7 - White Brown 8 - Brown     TXD ties to the ADI FSCO Panel on the terminal block labeled "IN." RXD ties to "OUT" and GROUND ties to "GND." Signal Connections When populating connection objects between an ADI FSCO Panel and a Vista database, the best option is to use a Multi-Connection Object. Right click on the root folder in the System pane of XBuilder and select New > Object > Multi-Connection Object. The Multi-Connection Object can be populated by dragging and dropping points from the ADI Device Template and Menta. The Send Option in the Connection Manager lets you select either Periodically, Write on change, or Write initially and on change. Choose to write initially and on change. Each point also has a designated Period. Just because a point is not set to update periodically does not mean the period ceases to have any effect. If too many points are on the same period, it can overwhelm the 913. So regardless of the Send Option, the Period (s) should be staggered. Set the first 20 points to 10 seconds, the next 20 points to 11 seconds (for example – in reality, just avoid having hundreds of points at the same period.) When finished populating all data fields of the Connection Manager, hit the Validate button on the bottom left corner and make sure there are no errors. Menta Programming Menta files that accept data from an ADI FSCO Panel do so through PVBs and PVRs. These come default with the "Backup" option selected. This is used to store the value in non-volatile memory on power loss. When using a PVR for a setpoint, this is a good thing. However, when something is constantly writing a value to this public variable, and it in turn is constantly writing values to flash memory, it can cause the controller to lock up and stop working. You must de-select the "Backup" option from any PVBs or PVRs in a Menta file that are accepting data from a connection object in a 913. Disclaimer This document is intended to address some of the most common (and most commonly overlooked) settings when integrating with an ADI FSCO Panel through a serial ModBus connection. Contact ADI for product information and to ensure that the correct FSCO Panel is ordered to facilitate this type of integration. No guarantee can be made that changes to the physical configuration, communication settings, or software format have not been made, so always check with your ADI sales representative first.

Issue How can I convert my BACnet B4920 to a BCX 4040 Using Cyberstation Environment Cyberstation BACnet B4920 bCX 4040 Cause Change model number from b4920 to bCX 4040 using Cyberstation. Resolution In Cyberstation V1.90 Service pack 1 the capability to convert a b4920 to a BCX 4040 has been added. In order to change the model you open the controller editor on the b4920 and from the model pulldown, select bcx 4040. This is a non reversible change so make sure you have a database backup before doing this. Once the model is changed, you will need to edit comm2 and verify that it has the same settings for the MSTP as comm1 did on the b4920. If you have not already done so you will also have to reassign any I/O points that were on the b4920 to different hardware such as XP modules or another b3 Controller. The conversion will leave the I/O points in the database but all the channels will be set to "0" so that any programs that reference them will stay in tact. Make sure to set the Bcx up with the same ACC Net ID and do not change the Bacnet Device ID or the comm2 and UDP Net ID's. They will stay the same as the b4920 had them. Once you have connected the BCX to the network and the MSTP controllers to comm2, you simply reload the Bcx, but you do not have to reload the b3 controllers. They should come online after the Bcx is reloaded. Prior to this version a deletion of the b4920 and all b3 controllers was required, and edited dump files needed to be imported into the Cyberstation to recreate the BCX and b3's, followed by a reload of all controllers.

Issue Xenta 555/731 resets when an alarm is blocked or unblocked. Environment Xenta 555, 731 XBuilder Cause If you set an alarm object to email you when the alarm is blocked or unblocked, the Xenta will send the email, and change the alarm state to blocked or unblocked, but then performs a reset. Resolution Work around for now is to not check the blocked and unblocked condition to send emails in XBuilder