Building Automation Knowledge Base

Issue Will Niagara applications run on Dual Core / Duo Core / multiprocessor computers? Environment Niagara Computer with (Dual Core / Duo Core / multiprocessor) Cause Knowing the processor spec requirement helps assess existing computer for installing Niagara applications. Resolution Currently, Workplace Pro / Enterprise Server and Workbench / Enterprise Network Server will run on Dual Core / Duo Core  / multiprocessor computers. These programs were designed to use only one of the processors, leaving the other processor(s) available for other applications. Other software (i.e. WorkPlace Tech) has not been validated on these types of computer systems. Therefore, these systems should be avoided since there would be no way to confirm proper functionality for each application. It is recommended that dual-processor and multi-processor computers as well as computers utilizing Intel Pentium 4 processors supporting Hyper-Threading Technology (when this processor feature has been enabled in the computer BIOS) be avoided for all company software for both server and client workstation applications. For more information read Technical Bulletin TB04-07-01

Issue The MNB-1000 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-BASE-1000 UL 864 Cause Information on MNB-1000 compliant with the UL 864 standard. Resolution The MNB-BASE-1000 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue UI-4 Expansion module will not work with i2 controller. Points cannot be controlled. Environment UI-4 Expansion modules i2 Controller Cause The firmware of the controller is less than what is required. The compatibility matrix indicates that to use the ui-4 expansion module that the firmware must be at version 3.3x. Resolution Uprev the firmware to version 3.3x. Read through Technical Bulletin #1361 to ensure that the bootloader flash is at the correct version. 

Issue Using an Analogue Input card to display Digital Inputs when no Digital Input channels are available. Environment Sigma Analogue Input cards. Cause There are no Digital Input channels available. Resolution An Analogue Input card cannot be used directly as a Digital Input card. A work around for this is to configure an Analogue Input to act as a Digital Input. Programme an Analogue Input object in Sigma. In Sigma System Manager create a lookup table, using an appropriate free number. Input Output 0 1 15 0 20 0 Add the above Lookup table to the Analogue Input object. In Sigma System Manager create a Short Text such as On/Off =%2.f Add the new short text number to the Analogue Input object. Across the Analogue Input channel fit a 1000 ohm resistor, this will be in parallel with the Digital Input connections. When the Digital Input changes state, Sigma will display either 1 or 0.

Issue The following error is showing up in the Application Director of the ENS: ERROR (09:45:06 26-Jul-11 EDT)(alarm) Cannot write alarm. java.lang.NullPointerException… Environment G3 (Niagara) ENS Cause The number of alarms in the system have exceeded the capacity defined in the AlarmService. Resolution By default the “capacity” for the AlarmService is set to 500.  Increasing this to a value greater than the number of alarms in the system will correct the error, however consider doing periodic Alarm Db Maintenance to keep the number of alarms at a manageable level.

Issue Is it possible to use 24VDC as power supply to the OP7? Environment OP7 power supply adapter included in package. Cause The documentation only recommends using 24VAC as power supply. Resolution Usage of 24VDC is not tested, and therefore not recommended or supported.

Issue Needs to add two MNB-300 controllers under an ENC-410.  How do I order the license? Environment ENC-410 Cause Needs to add some MNB-300 controllers under an existing ENC-410. Resolution According to our published literature, the ENC-410 does not support BACnet MS/TP because the RS-485 port is not isolated. If it becomes absolutely necessary to license an ENC-410 for BACnet MS/TP, you must submit a written or emailed request to the I/A Series G3 product marketing manager.  The product marketing manager may approve or deny the request based on the information contained in your request.  If approved, he will provide ordering and pricing information.

Issue Attempting to link from one I/A Series G3 station to another using a pop-up link and getting an error when using the browser.  The error indicates - javax.baja.license.FeatureNotLicensedException: tridium:brand. Environment I/A Series G3 (all versions) Cause Created a PxFile with a bound label pop-up binding to open another link outside the station environment (e.g. history).  The link works properly when using and viewing in Workbench but does not work with IE browser. Resolution The pop-up link through the browser currently does not support links to another station (supports only links within the same station).  Recommend the graphic be located with the associated history in the same station if pop-up link required.

Issue What operation modes should be used in zone control then the area is not being used? Environment Xenta 121 FC Xenta 121 HP Cause The TAC Xenta 120 device does not have any internal clock. The actual operation modes has to be sent from another device such as a Xenta 401. The following values could be sent to the nviManOccCmd SNVT: 0=OC_OCCUPIED 1=OC_UNOCCUPIED 2=OC_BYPASS 3=OC_STANDBY other values=OC_NUL 255=OC_NUL Resolution Normally, OCCUPIED mode is used when there are people in the zone. During night time, or short periods without people in the zone STANDBY may be used. If someone enters the area and triggers a motion detector or presses the Bypass button, the mode changes to BYPASS. UNOCCUPIED mode is most appropriate if the area is no longer rented or during some other long period without anyone in the area.

Issue Creating an email notification within Access Expert can be challenging if the correct steps are not followed.  Product Line EcoStruxure Access Expert Environment Access Expert Premise Software Cause If you don't follow specific steps, email notifications can be very difficult to write. Following the steps below, you can use pre-canned expressions which help to automate your notifications based on specific parameters. Resolution *Note* though you can add the Expressions tab by customizing the ribbon, no expressions can be found or used without following the process below. If you need to edit the notification to add more parameters then you will need to create a new template as editing an existing one will not expose the expressions. Trigger an event or alarm for what you would like a notification on. Right-click on the event or alarm in Event Viewer or Live Monitoring and select Add Email Template This will open up the template editor for you where you then will be able to select the necessary expressions based on your needs  Type the email message you would like to receive when the alarm triggers, click save    Type in the name you would like to use for the template and what you would like in the subject line of the notification you receive        Click on Alarm Actions, Add Alarm Action, and then Notification  Within the next dialogue box: Create a label for the notification Check the box next to "Send Email" Select the appropriate template Select Add Recipient Type in the name of the recipients you would like to receive the notification Click Save

Issue Does the oBIX service in I/A Series R2 require the web services license feature to operate? Environment I/A Series R2, UNC, oBIX Cause Licensing requirements for I/A Series oBIX Resolution The web services and associated license feature (webUi) is not required to run the oBIX service in an I/A Series R2 station.  The feature line in the R2 license must include obix. UNC example ... features=coreRuntime;bacnet;lonworks;obix If the license does not include the obix feature, purchase part number IA-DRV-OBIX for each Enterprise Server / UNC that needs to function as an oBIX server.

Issue Can the expansion board P8UI8DO be used on a 7716 or a 7718? Environment 7716 7718 P8UI8DO Cause Expansion Module for controllers Resolution The expansion board P8UI8DO can be used on a 7716 and the 7718

Issue The Analog inputs are reading too high or too low on a 7780. Product Line TAC INET Environment 7780 Cause Resistor configuration errors, damaged power supply, or the circuit may have been shorted. Resolution Several things could be contributing to this. Check the resistor configuration installed for the input and make sure it is correct. Check is the analog power supply (+15 VDC) has been damaged. Make sure a sensor does not have an open circuit in it (sensor is shorted).

Issue The Output relays will not control on a 7780, how can I fix this? Environment I/NET site Cause Output relays will not control on a 7780 Resolution First, check the matrix relay interface cable and make sure it is correctly connected. Secondly, make sure the matrix straps are not set incorrectly. Finally, Fuse F2 maybe blown. Fuse F2 is located near the top edge of the base card, directly above the LEDs. Fuse F2 is plugged into positions A and B of receptacle J20. This is a 0.5 amp pico fuse.

Issue Removing Trend Log before Upgrading to Vista 4.3 Environment Vista upgrade Cause During the addition of digital signatures to the log values, as required when upgrading to Vista 4.3, the PC may experience excessive demand of the processor and take a significant amount of time. Resolution If you do not require these trend log values you can follow these steps to avoid this potentially lengthy process. In the version of Vista that you are upgrading from create a full Vista backup by accessing the $Backup_FVB object found in you Operator Unit. Make sure that the "Include trend log files" selection is not checked before you start the backup. Upgrade to Vista 4.3 and specify a different database path then the one your old Vista database resides in. Start Vista Server and manually log in. Select "Restore Database" from the File menu in Vista Server. Browse to the backup file and specify the path you want to restore this database to. (The path to restored database must be different from the current Vista database path being used by Vista Server) Shutdown Vista Server and using Vista Server Setup change the database path to the directory you restored the backup into. Start Vista Server and the database will be upgraded without having to wait for the trend logs to get digital signatures. Once you have verified the upgrade completed made another backup of your database.  

Issue Using TOAD with Vista 4.3 Environment Vista 4.3 TOAD Cause The release notice for Vista 4.3 recommended the use of TOAD which is a free program that allows users to view and query SQL databases. This can be a very powerful tool to assist in database verification, exploration of the database for creating Crystal Reports, and running scripts. Resolution Warning: Care should be taken before making any changes to the SQL database since damage could break Vista To setup TOAD to work with the Vista database: Run Vista Server Setup and check the "SQL Server" tab and write down what is filled into the Instance and Database fields. Run TOAD_SS.exe. At the Server Login screen select "Add". Give your connection a name. Select "Use Connection String" and click "Build". Select "Microsoft OLE DB for SQL Server". Click "Next". In section "1" use the dropdown menu to select the Instance name found in Vista Server Setup. Typically the PC name or PC Name\TACVISTA. Select "Use Windows NT Integrated Security". In section "3" verify that "Select the database on the server" is selected and with the drop down menu choose the database name found in Vista Server Setup. Typically "taclogdata". Click "Test Connection" to verify it is working and click "Ok". Click "Ok" in the Data Link Properties window. Click "Ok" in the Add Registration window. Select the line your server was added to and click "Connect". You should now be connected to the server and you can use the Data Browser window to view the tables, views, procedures, and users of the database among other things. The SQL Editor window will allow you to run queries as well as other administrative tasks. Remember that all changes should be carefully considered before made to avoid breaking the database.  

Issue Running Equalization on a PC that has SP4 (Service Pack 4) and the clients are unable to connect to the File Master Environment PC that has SP4 Cause There is a protocol setting that needs to be enabled for this to occur. Resolution The following steps show the path to MSQL Server where the protocol resides and how to get it enabled. Open Windows Explorer and go to C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNTCN.exe. Double click on this file and enable the following files, Named Pipes and TCP/IP. Apply the changes and then close the editor SQL Server Network Utility.  

Issue Entering values less than 1 in Zbuilder results in red error indication. If you enter ".05" or ".2" into a field in Zbuilder it won't accept it. Environment Zbuilder Xenta 121 Cause A period cannot be the leading digit in a numerical input. Resolution The first digit must be a number,  so you must enter fractional values with a leading zero. Example: "0.05" or "0.2"

Issue Vista receives an I/NET transaction from a Xenta 527 as an alarm but not as a transaction Environment TAC Vista Workstation Alarm Queue Event Log I/NET Transactions Xenta 527 Cause If your time stamp is in the future, the events window (transactions window is really a filtered events window) will not display them but for some reason alarms come through. Resolution Open the Xenta 527 from Internet Explorer. Open the Events folder under I/NET. Look for the transactions. Note the date and time. Make sure the date and time in your 527 are set correctly and that the time zone is right in regional settings. Even though the SCU time stamps the transaction, the 527 shifts the stamp according to it's own settings.

Issue Displaying “??781”, “??782”, ”??787” or similar values. Environment Vista Workstation Cause The "??781," "??782," "??787" are in fact a Vista error codes, however, these codes are not documented. We have used the following approaches to get the device talking. Resolution In Vista right-click and upload parameters to the devices. Right-click > Properties > XIF File, browse in the XIF file to the Vista database.  In LonMaker Recommission the devices and Update the Vista Database. Try to delete the device from LonMaker, update the Database then reinstall the device. There is not a known proven method; these are things to try. Observe the results of the steps and please call if you are unsuccessful at seeing a change