Building Automation Knowledge Base

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 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.

Issue The Niagara G3 platform daemon will not run using an administrator account in Windows. Product Line TAC IA Series Environment Niagara G3 Cause Possible causes: The niagara service is not started IIS is running on the computer Port 3011 is blocked Authentication Resolution There are a number of possible causes: The niagara service is not started. Run Platform Daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) IIS is running on the computer.  Disable IIS in Control Panel > Administrative Tools > Services Port 3011 is blocked. Ensure there are no firewall, antivirus, or remote access software blocking port 3011 There are two types of platform authentication: Basic platform authentication (the default for a Windows-based host) provides integration with existing Windows installations, and provides two levels of platform access, which are determined by a user’s group membership(s). The levels of platform access are: User - Platform access at this level allows full use of most Workbench platform views. This includes the ability to install or delete licenses and stations (including the one running), also to install, reinstall, or upgrade the platform dist file and/or modules, and to start, re-start, or stop a station. Admin - Full access. This includes all user-level platform operations, plus the ability to configure host TCP/IP settings and dial-up configuration, change platform authentication, change platform daemon HTTP port, change host date/time settings, use the File Transfer Client, and reboot the host. Digest platform authentication provides only full level platform login access, using a single platform user account. With Digest platform authentication, there is no linkage between Windows OS user accounts and the platform administrator. If Basic authentication does not work, then Digest authentication must be used. To enable digest authentication, do the following: Using Notepad or WordPad, open the daemon.properties file located in C:\niagara\[release]\daemon folder Add the following lines to the end of the file: installFlag=doc authtype=digest/file user=[username] (where you select the username) password=[password] (where you select the password) stationIsAdmin=true Save, then close the file Restart the platform daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) Launch Workbench AX, then open the platform using the username and password you provided in step 2. Consult the Niagara AX Platform Guide for more information.

Issue Why does the Niagara G3 platform running on a computer have no Station Copier or Distribution File Installer feature? Environment Niagara G3 Cause In release 3.0 and earlier of Niagara G3, various issues arose with these features. Resolution Beginning in release 3.1, the features have been excluded on the local host. However, these features ARE included in the platform on the ENC controllers.

Issue Trying to zoom or control a point on a graphic page and it fails to bring the dialog to the forefront when connected to a controller. Environment Point Editor I/NET Graphic Page Cause A Windows setting causes this problem. Resolution Open Control Panel on the PC. Regional and Language Options. Languages, uncheck the Install files for East Asian Languages. Click on Details, Advanced and check the box for System Configuration where you turn off advanced text services. Reboot the PC. Restart the I/NET application and try clicking on the points again; it should come up front now.

Issue A report has been copied from one PC to another and it is not working. Environment I/NET Seven Reports Cause This occurs because the linking for the report has been lost. Resolution Rename the report with the problem Copy the original report from the I/NET CD Paste it into I/NET Seven, Reports Right Click on the report and verify that it is not set for read only Run the report again  

Issue A door is configured to receive messages and Alarms in AMT but it is not coming in correctly. Environment AMT SCU Cause This occurs mainly because the Resident IO point is not matching the Messages and Alarms in the Door Editor. Resolution Modify the Resident IO and see what type the Messages/Alarm Details and Distribution Masks are set for. Make note of it Connect to the controller, select Access, Doors. Modify the door and set the Transaction and Alarm Distribution to match those of the Messages/Alarm Details. Verify that the AMT configuration have these boxes checked as well. Read a card or generate an Alarm for verification.

Issue Trying to connect to a Xenta 527 over the web and cannot see it in I/NET, but can access it over the Ethernet Environment Xenta 527 Cause This occurs mainly because the reference host of the Xenta 527 and the Host PC are not seeing each other. Resolution Verify that all applicable ports are open, especially #50069, all C-Lan terminations are correct, # 19 and 20 on the Xenta 527. Start I/NET on the Host PC, open I/O Server, verify that TCP/IP is enabled. In the reference host, put in the IP address of the Xenta 527then save the settings. Connect to the Xenta 527 over the Ethernet, select Configuration Profile and put the IP address of the Host in reference #1 then save the settings. Restart both the Host and Xenta 527. Open I/O Server again then click on NP Routers and verify that the Xenta 527 appears in the table. Close this, then go to Edit Host Computer, Network Configuration, penetrate the link, it should be the Xenta 527’s name, save it. Penetrate the controller and its sub-lan devices should be seen as well, save all at this point. Close out of these editors and then connect to the controller, go to Summary and verify that you can control the points.

Issue Common Outlook errors with emailing of Reports in Continuum using the ReportCmdLine.exe Environment Continuum CyberStation WebClient Outlook Report ReportCmdLine Cause Outlooks default installation will block a lot of file extensions, especially in later versions. These are Microsoft Outlooks security features and has nothing to do with Continuum sending email attachments. Resolution The Continuum online help system describes how to setup scheduling of automatic reports The first thing to check would be to use the Outlook editor to send an email with a .htm attachment. If that is successful, then you'll know that you're not filtered at the exchange level. If you are filtered at that level then contact the system admin. The second check would be to make sure that your email from the ReportCmdLine.exe (with your report configured send htm or pdf attachments) is sending and receiving. If this is successful, but you cannot view the attachment then you're Outlooks local settings are most likely filtering the attachment. There are lots of articles on how to unblock certain file extensions. By searching on Google you can find more information than one would want to possibly know. In specific search for “Level1Remove”, you’ll find lots of information on how outlook blocks these file extensions and how to enable certain file extensions. In these articles you’ll see that in order to enable some of these extensions, you’ll need to add a registry key and in particular allow the .htm and .pdf file extension. There are third party tools available that you can do this with and not have to edit the registry directly. It is advised that you are very familiar with registry settings before ever editing them, as one mistake could corrupt the registry. Also on the Email accounts Microsoft Exchange Settings, deselect “Use Cached Exchange Mode” this will allow your settings to take place on the restart of Outlook.

Issue What properties are updated in a MNB Controller COV Client objects? Environment MNB Controller Cause Information about the properties sent to the COV client when a value of the point changes. Resolution COV Client objects can only update Present Value & Status properties.

Issue In Niagara R2 Workplace Pro, a Save Runtime DB command on a UNC does not work.  This error message appears: "DB ADMIN COMMAND ERROR EXCEPTION; CONNECTION REFUSED". Environment Niagara R2 Workplace Pro UNC Cause The UNC has its http port configured for a port number other than the default port of 80. A line must be added to the station.properties file to specify the new port number. Resolution Open the admin tool and log into the UNC (not the station database). Right-click on the station name that indicates "running" and select Edit > Properties. The station.properties window will open (typically indicates autoStart=true and autoRestart=true). Add a line to this file that specifies the new port number.  For example, if the station database was configured to use port 8080, the line would read:  httpPort=8080 Choose File - Close and Save when prompted. NOTE: To enable this change, the UNC must be rebooted.

Issue Restored backup of a TAC Vista Database is running really slow or is not responding at all. Environment TAC Vista Workstation Cause This will happen when the LNS database for this Vista database is not on the computer.  Vista is trying to communicate on that LNS port, but cannot find the LNS database. Resolution There are two options to fix this: The preferred solution is to restore a backup of the LNS database to the PC you are working on. If you do not have an LNS backup or are merely making some Vista-only change (like to graphics) it is possible to shut off that port. Right-click on the LNS port in Vista Workstation and select Properties Under General > Device address, delete the LNS path Click OK Vista will no longer attempt to communicate on this port.  ** You will not want to restore this version of the Vista database back to the original PC without restoring this value. **

Issue How to display the true position of a return air damper on a Vista OGC graphic when using a common outside air/return air damper signal. Product Line TAC Vista Environment TAC Vista IV OGC Graphics Editor Cause If an outside air damper is interlocked with the return air damper, then there will only be one 0-100% value in the Vista database. Some math is required to calculate the inverse position of the opposite damper. Resolution Entering the following formula in the Formula Section of the Attributes of a Digital Presentation: C-100.00+C-1.00* Note: the format for formulas in the OGC editor is Reverse Polish Notation.

Issue How to calculate the polling time at the netcontroller / OPC server? How many nodes/ controllers can be put on each netcontroller to get to specific polling time. Environment Netcontroller OPC Server Cause The OPC server was designed to be performance tuned. Resolution It is hard to determine just how many controllers / polling time. It would be determined better by looking at the programming of the controllers, for example, Inputs / Outputs how many points in each group and the interval of the data that is required to be received. The "OPC Server Guide" has performance options and guidelines on setting up an optimal system. You can also add another OPC server if you need to do load balancing.

Issue TAC Menta, using a dot in the application file name causes the MTA file to grow. Environment Menta Cause Using a dot, or period, in the application file name. Resolution Make sure to not have any dot in the application file name, except for the extension .MTA