Building Automation Knowledge Base

Issue When the WorkPlace Commissioning Tool browses a network or internetwork, not all controllers on the network will be found. Environment WorkPlace Commissioning Tool Cause Increase the reply timeout value in WorkPlace Commissioning Tool Resolution If controllers are missing from the list, the recommendation is to Refresh the list after the first attempt  Increase the reply timeout value in the WorkPlace Commissioning Tool to 40,000 milliseconds or greater. With large quantities of controllers (for example 80 or more), wait for the entire reply timeout value to expire for the list to stabilize.

Issue When using Link Builder in the WorkPlace Commissioning Tool, a change to the COV Client Subscription Lifetime to large minute increments (i.e. 60 minutes), is rejected. Environment WorkPlace Commissioning Tool Cause Incrementing the current values in large minute is known to create an issue, implement the below work-around to increase the lifetime value. Resolution The work-around for this issue is to change the COV Client Subscription Lifetime from its current value to the next incremental value (up one minute) and then to the desired value (i.e. 60 minutes).

Issue After converting from .vsd to .vsdx Workplace Tech application, monitor tags sometimes do not work. Product Line TAC IA Series Environment Workplace Tech  Cause The application must be closed and reopened. A new monitor tag from the stencil needs to be added to the drawing Resolution Add the application to a project Monitor the application. If the monitor tags do not function, close the application and re-open it. If the drawing has been converted from .vsd to ,vsdx, add a new monitor tag from the stencil and try the monitor operation again.

Issue Miscellaneous fixes in Workplace Tech 5.5 and 1.4 controller firmware. Environment Workplace Tech 5.5 1.4 controller firmware Cause Require detail on what miscellaneous fixes in Workplace Tech 5.5 and 1.4 controller firmware. Resolution Visio 2003 generates an error and crashes when attempting to save a Visio drawing outside of the WPT environment.  In WPT, the existing application tab in the add application to project dialog area is unable to open and add an existing application drawing. The MNB-1000 will reset in response to a read or write request for the profile_name property or background BACnet object. Cannot read/write background BACnet AO, Floating Actuator or PWM object in MNB-1000. AppLED stops updating in the MNB-1000. Sometimes an unsupported property response when reading BI object name in the MNB-1000. Power up delay object did not work correctly in the MNB-1000. Single and sequence loops incorrectly calculate output.  This issue was found when single and sequence loops were set up with large throttling ranges and had a small positive deviation from setpoint. During these conditions, the output of the loop would intermittently go to 100% output and then return to normal operation. This issue applied to MNB-1000, MNB-300 and MNB-Vx controllers. Interstage delay fails after power cycle causing outputs to come on after controller power cycle of MNB-1000.  Dual delay object may be in incorrect state after controller power cycle of MNB-1000.  There was an issue found where the Dual Delay had a 50/50 chance of coming up in the correct state after a power cycle.  Control object RAM not initialized correctly after a download of an application. Floating Actuator object may oscillate at 22.22 and 66.77% output. This issue was reported in MNB-1000, MNB-300 and MNB-Vx. BACnet flow balance values except BoxFlow can sometimes show error.  COV increment property of the VAV Actuator object does not take effect. Using the MN-Sx sensor to change temperature calibration does not work when temp calibration is set to NA from WPT or a BACnet tool and can lock up S-Link communications for MNB-300 and MNB-Vx controllers Overridden and Out_Of_Service flags for PWM and momentary SS objects not previously supported in MNB-300 and MNB-Vx controllers. COV increment property not previously supported for BI count output of MNB-300 and MNB-Vx controllers.

Issue Email alarming is configured correctly but Continuum keeps crashing when alarms are sent as emails. ACCDataServices is the crashing module.   Windows Application log shows two email errors that point to an issue with Outlook. Email, Failed to send email - SendNote in Send function failed. Result is 80070057. Email, Failed to send email -  SubmitMessage failed in CSession::SendNote, Result is 80070057 Environment Continuum Alarming Outlook Cause Outlook account folder is too large and does not have available space for new entries. In this case the folder was 7GB in size with emails going back eight years. Resolution Archive Outlook account folder and truncate to free up space for new emails.  

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 Having trouble communicating to an NPR or other I/NET hosts over a slow/busy ethernet. Product Line TAC INET Environment Any Version of Windows OS and Any Version of I/NET Seven Cause You can make I/NET more tolerant of communication delays over the IP network by making the following change. Resolution Open regedit. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\CSI - Control Systems International\I/Net 2000\Configurations. Select your active profile. On the right side, right click and modify the DWORD value "EthernetTimeout" and click "Decimal". The default value is 500mS or half of one second. Increasing this value will determine how long I/NET waits for a response over the ethernet before it gives up. Raise it to 1000, 2000, 2500, etc. and see if it helps. For additional information please see NPR's giving you "Host Lost - Host Restore" messages.

Issue How to modify the setting "initString" to change the number of rings for auto answer for a Niagara R2 UNC-520 internal modem Environment Niagara R2 UNC-520 Cause The Ring to Auto-Answer can't be change. Resolution The UNC-520 is shipped with factory defaults to pick up on the first ring. The internal modem does not answer, a service answers the call.  As a result, the "Ring to Auto-Answer" parameter is NON configurable.

Issue How to get SQL Server 2005 to work with a Niagara G3 Enterprise Network Server. Environment Niagara G3 Enterprise Network Server SQL Server 2005 Cause The SQL Server need to enable TCP/IP and open TCP port number 1433. Resolution "...To get SQL Server 2005 Express (the free edition) configured properly simply follow these steps... Download SQL Server 2005 Express Edition here. Download the SQL Server Management Studio Express from the above URL (note: advanced services are not needed). This is optional but it does provide a useful interface for running SQL queries if desired. Before installing SQL Server 2005 Express Edition, ensure the user is logged on with administrative access to the PC and all older versions of SQL Server are uninstalled. When installing SQL Server 2005, ensure mixed mode is enabled and the give 'sa' user a strong password. Once installed, open the SQL Server Configuration Manager ('Start', 'Programs', 'Microsoft SQL Server 2005', 'Configuration Tools', 'SQL Server Configuration Manager'). Once the Configuration Manager has been opened, enable TCP/IP so G3 can connect to SQL Server (by default this is switched off). Using the tree, navigate to 'SQL Server 2005 Network Configuration' and then 'Protocols for SQLEXPRESS'. Right click TCP/IP and select 'Properties'. The TCP/IP Properties window should now appear. On the first tab labeled 'Protocol', ensure the 'Enabled' property is set to 'Yes'. Go to the second tab labeled 'IP Addresses'. In the section labeled 'IPAll' delete any entry in 'IP Dynamic Ports' and enter the value 1433 in 'TCP Port'. Once completed click ok.  Note that the default port is a 5-digit number that will NOT work.  It must be removed. Restart the SQL Server Express service. If it can't be located easily in Windows, then reboot the computer. Niagara G3 should now be able to connect to SQL Server 2005. Before attempting to connect, ensure all firewalls are properly configured so the connection can be made. If running the Enterprise Network Server on a different computer, then open up a Windows command prompt on the ENS computer and type 'telnet yourIPAddressGoesHere 1433'. If the command prompt window goes blank then connections can be made to this IP address and port number. Open Workbench and run up the desired station. Ensure the station is licensed to use the rdbSqlServer feature. Add the 'RdbmsNetwork' component to the server station. Add the 'SqlServerDatabase' component. Configure the properties for the 'SqlServerDatabase' component. Type in the IP address, port number (1433 in this example), user name and password for the connection. Ping the 'SqlServerDatabase' and ensure its status is 'ok'. Export historical data to the Sql Server database by adding a new 'SqlServerHistoryExport' component and setting up its 'History id' property to point to an existing history already in the station". Ensure Niagara G3 version 3.0.100 and above is used in order for the connection to work.

Issue For the Niagara R2 MicroSmart Driver (ibsMs), what are the latest firmware revisions for MicroSmart controllers that are supported? Environment ibsMs MicroSmart controllers Cause Check and upgrade MicroSmart controller firmware to the latest firmware to avoid intermittent problems. Resolution ibsMS a Supported Controller Part Number Cntlr Type Cntlr Level Description P/N To Order Firmware P/N Revision CheckSum IC# Yes 1 ENV-III AHF L11 Anemostat Envirotrak III PROM-KIT-10 PROM-48-119 11.1X $8F1E IC12 Yes 1 ENV-III-MPC AHG L11 Anemostat Multi-Purpose Controller PROM-KIT-11 PROM-48-120 11.1X $63F1 IC11 Yes MN-MSI MIM L11 Integrator for MicroSmart Bus PROM-KIT-4 PROM-42-100 11.1T $0B48 IC20 Yes MSC-L1000 ELC L11 Lighting Controller PROM-KIT-16 PROM-48-125 11.2H $31B4 IC3 Yes MSC-MPC-001 HPA L11 Multi - Purpose Controller PROM-KIT-5 PROM-48-104 11.2H $2996 IC11 Yes MSC-P-751/752/753/754 SVA L11 Package Unit Controller PROM-KIT-7 PROM-48-106 11.2H $B762 IC3 Yes MSC-P1501/1502/1503/1504 PCB L11 Package Unit Controller (early version) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-P1501/1502/1503/1504 PCC L11 Package Unit Controller (enhanced AI) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-V-511/512/521/522 VAC L11 VAV Controller PROM-KIT-9 PROM-48-107 11.2H $7D17 IC9 Yes MSC-V-751/752/753/754 SVA L11 VAV Controller PROM-KIT-8 PROM-48-106 11.2H $B762 IC3     ELC-001 SVC L10 SiteManager Controller PROM-KIT-12 PROM-48-121 10.2 $C708 IC4 Yes 1 ENV-III-MPC AHE L10 Anemostat Multi-Purpose Controller N/A       IC11 Yes MSC-MPC EHP L10 Multi - Purpose Controller PROM-KIT-2 PROD-EHP 10.3 $0FEE IC11 Yes MSC-P1000 ELP L10 Enhanced Low PUC PROM-KIT-13 PROM-48-122 10.1 $C25B IC18 Yes MSC-P2000 EMP L10 Enhanced Medium PUC PROM-KIT-14 PROM-48-123 10.1 $AC7A IC24 Yes MSC-U1000 EUC L10 Enhanced Unit Controller PROM-KIT-3 PROD-EUC 10.4C $945F IC21 Yes MSC-V501/502 VAD L10 VAV Terminal Controller PROM-KIT-17 PROM-48-126 10.4D $345C IC9 Yes MSC-V501/502 VAB L10 VAV Terminal Controller PROM-KIT-15 PROM-48-124 10.3 $017C IC12   Yes 1 ENV-IIB (N1-1087) A2B L9 Anamostat (2) Fume Hood Controller N/A PROD-A2B 9.1 $6858 IC23 Yes 1 ENV-II(N1-1058) AHC L9 Anamostat Unit Controller PROM-KIT-1 PROD-AHC 9.1 $320F IC37 Yes MSC-GPC GPC L9 General Purpose Controller PROM-KIT-18 PROM-48-736 9.4C $4E78 IC25 Yes MSC-IOC SIO L9 Input/Output Controller PROM-KIT-21 PROM-48-739 9.4C $64A7 IC43   MSC-L-100 MLC L9 Lighting Controller PROM-KIT-25 PROM-48-743 9.1R $AA35 IC5 Yes MSC-P-100/112/120 LPC L9 Low PUC PROM-KIT-22 PROM-48-740 9.4C $C9FE IC17 Yes MSC-P-200 MPC L9 Medium PUC PROM-KIT-20 PROM-48-738 9.4C $9031 IC23 Yes MSC-T-100 STC L9 Temperature Controller PROM-KIT-23 PROM-48-741 9.4C $558E IC6 Yes MSC-UC UC L9 Unit Controller PROM-KIT-19 PROM-48-737 9.4C $FB25 IC22 Yes MSC-V-100/V110 VAV L9 VAV Terminal Unit Controller PROM-KIT-27 PROM-48-749 9.4C $45AE IC12 Yes MSC-V-200 VSD L9 VAV Terminal Unit Controller PROM-KIT-24 PROM-48-742 9.4C $5CE8 IC13   MSC-V-200E (ETI) VE1 L9 VAV Terminal Unit Controller N/A TEST VE1 9.0C $6A7E IC13 Yes MSC-V-300 VDD L9 VAV (Dual) Terminal Unit Controller N/A PROD-VDD 9.3 $7DC6 IC15 Yes MSC-V-400 MOV L9 Mobil Package Unit Controller PROM-KIT-26 PROM-48-744 9.4C $5148 IC17 a The firmware revisions listed above were validated with this driver. Other versions may function correctly but were not tested. If difficulties are experienced, upgrade firmware. 1 Controller validated with ibsMS-2.302.514a.v1 or greater.

Issue When using XPSI and serial tunneling on Windows 2003 Server, this error occurs:  "NTVDM encountered a hard error" Environment XPSI Windows 2003 Server Cause Environment settings for TEMP and TMP is not 8.3 namespace compatible. Resolution "Most ntvdm errors can be fixed by modifying the TEMP and TMP environment settings to make them 8.3 namespace compatible. The default path for the TEMP directories is:  %USERPROFILE%\Local Settings\Temp This will (typically) expand to something like: C:\Documents and Settings\Administrator\Local Settings\Temp 16-bit applications cannot  manage the spaces or long file names, and will generate ntvdm errors, even if not explicitly referencing the TEMP directory. Either use a common temp location (i.e C:\Temp) or use the short version of the path.  For the Administrator ID, the short filename path is C:\DOCUME~1\ADMINI~1\LOCALS~1\TEMP Check these names by using ‘dir /x’ The variable settings can then be changed for each user by going into My Computer -> Properties -> Advanced -> Environment Variables -> Set TEMP and TMP to c:\temp or the short filename version Also, consider the PATH environment variable, and any INI files that may be used. The short filename for the "c:\Program Files" directory is "c:\progra~1" Here is how to disable 8.3 naming in the registry. Note - "Edit the registry by using Registry Editor (Regedit.exe or Regedt32.exe). If Registry Editor is used incorrectly, serious problems can occur requiring a reinstallation of the operating system. Use Registry Editor at your own risk." http://support.microsoft.com/kb/121007/en-us

Issue In the process of upgrading a Niagara G3 ENC from version 3.0  to version 3.1, the station fails to start due to an invalid license. Environment Niagara G3 ENC Cause In order to complete an upgrade to version 3.1, it is necessary to obtain a 3.1 license. Resolution Ensure that a new license is available to install in the ENC before upgrading. Once the ENC has been upgraded it cannot be downgraded back to 3.0 unless it is done by the factory.  If a new 3.1 license has not been installed, the ENC will be inoperable until it is installed.

Issue Getting error 'Failed to access IIS' when starting webstation. Environment TAC Vista Webstation Cause This happens if IIS is installed before .NET Framework. Resolution It is necessary to register ASP.NET with IIS. From the Windows Start Menu>Run In the Run window type "cmd" to open the command prompt window To register ASP .NET 2.0, In the command prompt window, type  "%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" To register ASP .NET 4.0,  In the command prompt window, type "%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i" This command will re-register ASP.NET as if it were installed after IIS.

Issue When using COV with BACnet and Niagara R2, what object types should be used with it? Environment BACnet Niagara R2 COV Cause To get the most benefit from implementing COV and make certain it performs well. Resolution Per the Niagara R2 BACnet Integration Manual follow these COV Strategies: Best Candidates for COV:  In general, the best usage of COV is for objects that have values that change infrequently - typically binary and multistate input objects or binary and multistate value objects. These are represented by BACnet shadow object types BI, BV, MSI, and MSV. You can also use COV for analog input and value objects (AI and AV). However, to reduce notifications you would have to increase each object’s covIncrement value, which would also reduce sensitivity to changes - consider that only changes larger than the covIncrement value will be reported. Poor Candidates for COV:  Starting in release r2.3.4, the priorityArray property of output-type objects (AO, BO, MSO) and value-priority objects (AVP, BVP, MSVP) is polled, in addition to presentValue and statusFlags properties. This is done as part of a “rewrite mechanism” (see “Rewrite Mechanism,” page 3-25). Although you can configure any of these BACnet objects to useCOV, the object remains in the poll queue to receive priorityArray - as this property cannot be received using SubscribeCOV logic. Therefore, configuring these objects to useCOV will not significantly reduce message traffic. The poll message for each will request only one value instead of three, but this typically makes little difference. Therefore, it is recommended that you do not configure any output-type and value-priority objects for COV usage, unless the device can support plenty of COV subscriptions, and you have already subscribed all of the input and “non-priority” value type objects.

Issue Can a Niagara R2 UNC be integrated with Microsoft's Active Directory (LDAP protocol) so IT departments can change the UNC password every 60 days? Environment Niagara R2 UNC Microsoft Active Directory Cause LDAP protocol is not supported on the Niagara R2 Resolution Unfortunately, Niagara R2 cannot integrate with Microsoft's Active Directory or the LDAP protocol. It is available with Niagara G3.

Issue On a NiagaraR2/ASD integration, the shadow objects from all the Microzone II controllers display dynamic data in purple. Typically, purple means the object is in override but no overrides have been applied. Environment Niagara R2 Cause Outdated firmware Resolution The firmware in the Microzone II controllers requires updating in order to clear the purple color. The current firmware revision is 2.0 and can be ordered using part number MZ2A-119-200. Review the installation instructions for details and diagrams (document number is F-26538-1).

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment WorkPlace Commissioning Tool Cause There could be a Niagara R2 station running on the computer configured for BACnet/IP. Since the Niagara station also uses UDP port 47808 by default, the Niagara service prevented WorkPlace Commissioning Tool from "binding" to the UDP port. Resolution There are two ways to resolve this issue: Disable the Niagara service when using the WorkPlace Commissioning Tool In Workplace Pro, stop the station that has the BACnet/IP service enabled, and configure it so that it does not auto-start. NOTE: If this procedure does not correct the issue and the WorkPlace Tech Tool software is being run on the Windows 7 operating system, refer to WorkPlace Commissioning Tool Windows 7: "A critical error occurred in the communication server rtmonitor.exe" for information on how to correct what may be a program security settings issue.

Issue What parameters are used to regulate the speed of the LON trunk in a Niagara R2 integration? Environment Niagara R2 Cause Configuration of LON devices create unnecessary network traffic from changing values. Resolution There are two settings that can regulate LON traffic: 1. In the LocalLonDevice properties, the maxSendTime parameter specifies the maximum amount of time the local lon device (which is the UNC station) waits to send out a value that has not changed. 2. Also in the LocalLonDevice Properties, the minSendTime parameter specifies the minimum amount of time that must elapse between network variable updates for values that are changing rapidly. Consult the Niagara LonWorks Integration Guide for more information.

Issue Finding a new BACNet device causes a BCX controller to show in the Continuum Explorer with the icon of a Workstation Environment BCX Continuum Explorer CyberStation Cause There are incompatible revisions between the controller and the CyberStation. Resolution Delete the BCX from the BACNet view Choose one of the following options: Upgrade the CyberStation to version 1.73 and higher Downgrade the BCX below revision 4.4. Review the Compatibility matrix posted on the Buildings Business Extranet for compatible revisions of products.

Issue While trying to connect to a BACnet/Ethernet network with Workplace Commissioning Tool, the following error appears:   "An error occurred while open communications. Please verify communications settings and try again." Environment Workplace Commissioning Tool BACnet/Ethernet network Cause Workplace Tech and WorkPlace Commissioning Tool use the NDIS BACnet Ethernet Packet driver to connect to BACnet/Ethernet networks. This driver's file name is KPF.sys and is known as a Kernel driver. If this file is not installed correctly or is halted by another program, BACnet/Ethernet will not function. Resolution To identify if Kernel driver is the issue, follow the steps below:   Open system information from Windows - Accessories - System Tools - System Information Navigate to Software Environment - System Driver Look for KPF in the name column. If it is not there, re-install WorkPlace Tech as an administrator.   Make sure there is no software running that might not allow this file to be loaded.  Some virus software may also block the installation. If this file is there, check the state column to verify that it says running. Note:  this driver will only say running if BACnet/Ethernet is being used. If the file is there but it is not running, ensure that the actual location of the file in Windows Explorer is the same as the file column location in System Info. If they are not, then copy the file to the location listed in System Info. To verify that this driver is working correctly, use the net start command at a command prompt (type "net start kpf"). If the driver is working, it will indicate that it is already running. As this is a Kernel level driver, if the above steps do not resolve the  issue, un-install WorkPlace Tech and re-install ensuring a local administrator account is used.