Building Automation Knowledge Base

Issue An error occurred while installing DSS: MSDTC The content of the dialog box or windows event entry starts with: System.EnterpriseServices.RegistrationException: Unable to open COM+ 1.0 catalog to configure components. ----> System.Runtime.InteropServices.COMException (0x8004E00F): COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator Product Line TAC Vista Environment Vista Installation DSS Cause This happens when there is a problem with Microsoft Distributed Transaction Coordinator (MDTC) Resolution Go to Control Panel Administrative Tools – Services Check if MSDTC in running as a Service. The name that you should see in the service list is 'Distributed Transaction Coordinator' Make sure that this is Started, Automatic, Network Service (for XP and Win2003) Here is how to install it if it is not already running: Open cmd prompt Navigate to C:\Windows\%windir% Type "msdtc -install" which installs Msdtc. The service now appears under the 'Services' area. After installing follow the steps in Microsoft Technical Bulletin.

Issue How to recover I2 controller with auto started corrupt/bad PE program and flash backed up with this corrupt/bad program. Environment I2 Controller Cause If the program is in flash, and the ACCRestartMode is set to ACCWarmToCool and the ACCStatusFlash is set to AccValidFlash, you’ll find yourself in an endless loop when trying to power down and restart. What needs to be performed at this point is to get the corrupted/bad auto start program out of the backed up flash. The corrupted program can be one that has just been created/edited or imported and then saved to flash. Resolution Get the corrupt/bad program out of the controller and its flash: With the WS in offline edit, dump the corrupted program/s to file and then delete it/them from the controller. Now send the I2 controller to text file. Edit the controller and write down the parameters i.e.….Name, model #, commport, serial # and infinet ID. Then delete the controller. Bring WS online, manually create a new I2 with a temporary name, same serial #, same model #, same comport and an infinet ID that is not used… ie (if you have for example less than 100 infinet controllers use infinet id of 101) select apply. The temporary I2 just created should come online. Once online, delete it. (The reason for creating with a new temp name and Infinet ID, is that a newly created controller will create an empty controller and empty out the flash.) Now create a new I2 with the original name, commport, serial # and original infinet ID. Once online import the controller dump file we saved, reload and back up to flash if needed.

Issue What is the Vista Server LNS license? Environment Vista Licensing Cause Vista will automatically detect the presence of binding tools (LonMaker, Alex, Lonwatcher, and NL220) and properly communicate with the LNS server without the need of a specific license. However, if you have an LNS database but no binding tool then the LNS license will need to be ordered and installed. Resolution The Vista Server LNS license is used by Vista to enable LNS communication when there is not a binding tool installed on the computer. Note: Vista 5.0 had a bug and was incorrectly checking for the binding tool. This was corrected in Hotfix 14 and 17.  

Issue It is desired to configure a minimum off time, so when the compressor stops in e.g. heating mode, it will not start again before a minimum time has elapsed in the same mode. This setting is not available in the device. Environment TAC Xenta 121-HP Cause There is no setting for minimum stop time when in the same mode, there is only a minimum stop time between modes. Resolution As a workaround, set the "Activate at" value to something other than zero (say 10%), so that you can use the "Hysteresis" at 10%, and this way get a delay. This way you will get a delay in the most cases, a little time before the controller reacts.

Issue Error message "Exception from HRESULT: 0x80041038 Code: -2147217352" when logging into TAC Vista Webstation 5.0.0 Environment Webstation 5.0.0 Internet Explorer Cause This error results from an attempt to log in with an invalid user/password Resolution Check that the username and password are valid and try to log in again.

Issue Alarms cease to display and Continuum Workstation reports offline in the Workstation editor but appears as online to the CX controllers. Environment Continuum Workstation Cause On sites where this has been detected, there were alarms setup, the eventnotification settings were set for multiple entry, there was no recipient configured, and the deactivate settings required acknowledgement. This type of configuration will allow the active alarm count in the system to increase with each alarm. The active alarm buffer in the workstation by default is 3000 and when exceeded can cause the WS to appear as offline. Resolution NOTE: Before any query or access of a database make sure that you have a recent known good backup. To test for this situation, run the following query from the database: Select count(*) from alarmevent where active = 1 To fix this situation, correct the incorrectly configured event notifications to avoid the same problem. Shutdown all CyberStations. Run the following query on the database: Update alarmevent set active = 0 where active = 1 Restart Continuum.  

Issue How can the resource count be found for a Niagara R2 station? Environment Niagara R2 station Cause User can't locate the Resource counts using Workplace Pro or a web browser. Resolution There are two methods. Using Workplace Pro, Open a station (Note:  the station must be running)  Highlight the station name Select Search > Resource Count in the drop-down menu bar (alt-R shortcut) Using a web browser, In the address bar, type http://[stationHost]/prism/resources. Sign into the station using an Admin user account. This will display a summary at any level of the database. For each level there is a "Total objects" listing at the top of the page. This is where the resource count is displayed for that level.

Issue Move TGML graphics from one Vista 5 database to another and keep the links/bindings intact. Environment Vista 5 TGML Graphics Cause Linking and binding information is not stored in the TGML source file, but in the Vista database. Therefore if only the TGML graphic is saved and transferred to the new database, all of the binding and linking information would be lost. To preserve this information, a Database Export must be performed for graphics transfers between databases. Resolution In Workstation, open the database you would like to export from and select File-Database-Export. Under the Site PC tab, use the default selection of "Get a customized copy of the database" and click OK. In the Database Export window, Right click on the root object and select Add. In the Select widow, navigate to the object(s) you would like to export and click Select. Use multiselect commands (hold ctrl or shift) to select multiple objects. When you are finished selecting objects, click on the green arrow of the Database Export window to name the export file and save. In the new database, select File-Database-Import. Browse to the Exported file and click OK. (You can also click View to see the contents of the selected File before importing if you have multiple Export files). Refresh the Folder pane of Workstation and the object should now be imported.

Issue "Access Denied" errors are reported during the re-installation of the Niagara R2 software. Environment Niagara R2 software Cause The files installed in the nre\modules folder are write protected. Resolution If an attempt is made to reinstall Niagara R2 software on a computer, an installation error frequently occurs. The Niagara installer (second installation program) progresses one tick on the progress bar then displays a "Module Install Error" window containing the message "Access is Denied". Clicking the OK button to acknowledge the error results in the message window reappearing multiple times. This occurs because the files installed in the nre\modules folder are write protected when installed. To prevent this problem before attempting to reinstall any release of the Niagara R2 software, Open Windows Explorer ("My Computer") Select all files in the niagara\nre\modules folder Right-click on the selected files Select "properties" from the displayed menu. The Properties window appears.  Clear the mark in the "Read-only" box Click the OK button.

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.

Issue Is there a way to backup a Niagara R2 UNC or Enterprise Server station from a web browser? Environment Niagara R2 UNC Enterprise Server XML-capable browser (IE 4.x or higher) Cause Need to save the station's database on the PC for possible restoration. Resolution Yes but note that this method will only backup the station database.  It will open the entire station database in XML format on the webpage.  Depending on the size of the station it may take a long time.  It is best to use this method if Workplace Pro is not available. Follow the steps below to create a station backup of a UNC or Enterprise Server via a web browser: Log into the station via a web browser Navigate to the following URL:  http://[ip-address]/prism/backup. Watch the lower left hand corner of the web browser.  The web pager loader indicator must finish. Once the web page indicates that it is done, save the page as a XML file to your PC.  Use the “Save As” choice to do this step. For more information review Appendix B of the Niagara Browser Access Guide.

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue Settings for the USRobotics 5686 series for use with a DMS panel. Environment USRobotics 5686 series DMS panel Cause For the modems to communicate, V.92 protocol needs to be disabled. Resolution The V.92 protocol must be disabled when using these modems with older modems. To disable the V.92 protocol on a USRobotics 5686 series modems, enter the following setup string (without the quotation marks), in addition to any string specified in the referenced bulletin, before saving the settings: " AT +PIG=1 +PMH=1 +PQC=3 ". Refer to Bulletin 00-19

Issue Is WorkPlace Tech 5.x compatible with Microsoft Windows 2000 Professional and Visio 2002? Environment WorkPlace Tech 5.x Microsoft Windows 2000 Professional Visio 2002 Cause WorkPlace Tech 5.x system specify Visio 2003. Resolution WorkPlace Tech 5.x is designed to function with Visio 2003. However, considerable development testing was done on Windows 2000 Professional with Visio 2002 platforms to verify functionality and compatibility. WorkPlace Tech 5.x appears to be fully functional with Windows 2000 Professional with Visio 2002.

Issue Can the existing communication wiring from a NETWORK 8000 (ASD) or DMS (Microsmart) project be re-used for a BACnet MS/TP trunk? Environment NETWORK 8000 (ASD) cable DMS (MicroSmart) cable BACnet MS/TP Cause Using ASD cable become an issue as baud rates increases pass the range of 9600 or 19.2 k. Resolution Testing has shown that existing communication wiring of a NETWORK 8000 (ASD)or DMS (MicroSmart) system is compatible at a speed setting of 9600 baud.  It is unlikely that this wire will work at higher baud rates or at extended distances.  Communications will be limited to the slower baud rates (9600 or 19200 baud) on these systems.

Issue How can a BACnet system be customized to maximize data throughput?  The site has a Niagara R2 Enterprise Server and a UNC with a variety of MSTP controllers connected to the UNC. Environment Niagara R2 Enterprise UNC MSTP controllers Cause Improper configurations won't achieve optimum performance. Resolution This can be a relatively complicated question, however, there are a number of basic steps that can be taken in terms of best practices to enhance performance. Within the UNC station, any BACnet objects that are not needed are to be deleted. During the learn of a BACnet controller, many objects are learned that are not used. All BACnet objects when learned into a station are placed in Poll-Always containers. All but the most critical objects, schedules and trended objects are to be moved to Poll-on-Demand containers. All controllers on the MSTP bus should be consecutively addressed.  Gaps in addressing add delay in communications. The MaxMaster setting in all controllers, including the UNC, is to be set to a numeric value two greater than the highest MSTP controller address on the network. To leave MaxMaster at 127 but only have 20 controllers on the network will also add delays in communications looking for the other non-existent 107 controllers. The MaxInfoFrames setting in the UNC or MNB-1000 is to be set to a number higher than 5 but no more than 20. This setting determines how many pieces of information can be requested each time the UNC or MNB-1000 receives the token on the MSTP bus. The default value is 1 and if left at this value the system will be sluggish with updating values on graphic screens. The range of 5 to 20 is given as a starting point for experimenting and each system will be different depending on the number of controllers and what data is being requested.  Lab tests have shown there is a performance curve with an optimum point.  Starting at a value of 5, performance increases as the value increases.  Performance will then peak and any further increase to the setting will result in a performance reduction.  As a result, stay above 5 but less than 20. Refer to the document titled "I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide" (F-27360) for additional information.

Issue Can third party BACnet/MSTP devices be placed on the same MSTP bus with MNB controllers? Environment MNB controllers MSTP communication bus Third-party BACnet/MSTP devices Cause Have not test MNB controllers and third-party BACnet/MSTP devices on the same BACnet MSTP communication Bus. Resolution There has not been thorough evaluation to know if third party devices can co-exist with MNB controllers. It is not currently recommended by the factory. The best solution is to create a separate BACnet network under a UNC/ENC to support the third party devices.

Issue A LON SNVT on a shadow object in a Niagara R2 UNC station takes 2-3 minutes to update after an override command is issued from a graphic. Environment Niagara R2 UNC LON SNVT on a shadow object Cause Minimum and maximum send times are not set correctly. Resolution Verify the maxSendtime and minSendtime parameters in the Local Lon Device > Config tab have the appropriate values (default values are 100 and 5 seconds respectively).   The minSendtime parameter specifies the minimum amount of time that the controller will wait before updating values. Re-upload the affected LON object from the LON controller. Re-bind the Lon object in the Lon Link Manager.

Issue The Mail Service in a Niagara R2 UNC station is configured correctly.  However, e-mails do not get sent to the SMTP server. Product Line TAC IA Series Environment Niagara R2 UNC station Cause The Niagara station needs to enable mail.smtp.auth in system.properties. Resolution In the station, the following lines need to be added to the system.properties file if authentication is required: mail.smtp.auth=true mail.useUTF=false Once these lines are added and the UNC is re-booted, the UNC will successfully send emails to the SMTP server.

Issue A Binary Output object has just been created in a Niagara R2 UNC station.  The Prioritized Output of the object defaults to a state of "Active" at a priority 10. Environment Niagara R2 UNC Cause It can be a corruption issue with the station database. Resolution Re-load the UNC station database from Workplace Pro (convert the .db file to .sns in the Admin Tool) to resolve the issue.