Building Automation Knowledge Base

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 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 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 When starting SIGNAL, a pop-up window declares "Sorry this program has not been enabled". But the security plug is installed in the computer’s parallel printer port (LPT1). Environment Windows XP with SP2 Cause The HASP security plug driver that is included with the Signal-XP software is not compatible with Windows XP-sp2. Resolution Follow these steps: Ensure that the serial number on the security plug matches the serial number on the Installation Diskette #1. The first 4 digits of the serial number are a data code and DO NOT need to match. The last 4 digits MUST match. This applies to all versions of SIGNAL. If it’s SIGNAL for Windows XP (version 5.0), the drivers for the security plug need to be updated. See Technical Alert TA06-03 for details in updating the drivers. If it’s SIGNAL for Windows 95/98 (version 4.4.1 or earlier), try the following:      Disconnect any printer.      Modify LPT1, in Windows and/or the computer’s BIOS, and make it bi-directional.      Use the Plug Testing utility program (16Bit Plugtest.zip) available from The Exchange Download Center to validate the security plug. If it’s defective, a new security plug can be ordered.

Issue How to migrate a SIGNAL for Windows 95/98 (version 4.4.1 or earlier) database to a new SIGNAL for Windows XP (version 5.0) installation. Environment SIGNAL for Windows 95/98 version 4.4.1 or earlier SIGNAL for Windows XP version 5.0 Cause Data on the existing database is crucial and don't want to lose any data during the transfer process from SIGNAL for Windows 95/98 to SIGNAL Windows XP. Resolution Perform a backup of the SIGNAL for Windows 95/98 system. When prompted, select to backup only DATA and BITMAP files. DO NOT SELECT executable files. The executable files are specific to the SIGNAL version for Windows 95/98. If this backup is restored to a SIGNAL for Windows XP computer, the executable files will not work on that operating system. If the only backup available contains the executable files, then restore the backup to the SIGNAL for Windows XP computer. Now, perform a new backup containing only the data and bitmap files. Once completed, delete the SIGNAL folder and the signal.ini and bit.ini files from the x:\WINDOWS directory. Re-install SIGNAL for Windows XP from the installation diskettes. Then, restore the backup containing only DATA and BITMAP files.

Issue When starting SIGNAL for Windows XP, an error message appears stating "Can't run 16 bit Windows program, insufficient memory". This occurs when the SIGNAL program "Startup Type" is set for Automatic. Environment SIGNAL for Windows XP Cause Multiple versions of SIGNAL for Windows XP are trying to run simultaneously. The “active” user profile, as well as, the “All Users” profile are both trying to start SIGNAL. Resolution When it is required to have SIGNAL startup automatically for ALL users, either make the entry for each user profile or only make the entry in the “All Users” profile.

Issue SIGNAL (any version) is installed on new computer hardware that has higher video resolutions. Now, the Monitor program's graphics are not aligned. Environment SIGNAL (all version) PC with high resolution graphic card Cause The new PC screen resolution is not set at the recommended resolution. Resolution All versions of SIGNAL support two video resolutions: 640 x 480, and 800 x 600. Shutdown SIGNAL and use Windows to modify the computer's video resolution to one of these two settings.

Issue When starting Niagara R2 Workplace Pro, a window appears stating: "Error occurred during initialization of VM. Could not reserve enough space for object heap" Environment Niagara R2 Workplace Pro Cause The RAM spaces is not enough when it's trying to allocate to it. Resolution If this error occurs on a Windows Server 2003 Service Pack 1 platform, read Technical Bulletin TB06-11. If this error occurs on a Windows XP Professional service pack 2 (32-bit) platform, change the setting in /nre/lib/nre.properties to half of the maximum physical memory installed in the computer.  If the error continues to appear, an increase to 1 Gigabyte of RAM is recommended.

Issue On a MNL-800 controller, are resistors required on the universal inputs when wired for pulse counting? Environment MNL-800 controller Cause Knowing the resistor requirement helps implementing pulse count using universal inputs. Resolution UI1 does not require an external resistor. If using UI2 through UI8 as a pulse input, an external 10K resistor to +5.1 V is required.

Issue Why does it take three minutes to create a link in Niagara R2 WorkPlace Pro from an Enterprise Server station to a UNC station? Environment Niagara R2 WorkPlace Pro Enterprise Server UNC station Cause Enterprise Server station attempts to connect to all devices in the address book. There will be latency if there are offline or no longer exist UNC devices in the address book. Resolution When engineering a job it is common practice to load the Enterprise Server station into an engineering laptop and create links to UNCs one at a time. This is not a problem as long as the address book entries are removed from the Enterprise Server station that are not online. Upon creating a link, the Enterprise Server station attempts to connect to all devices listed in its address book. This creates a large latency in completing a link if there are multiple devices in the address book that are not able to respond. To create links in this fashion remove all address book entries from the Enterprise server station's address book that are not online.

Issue When upgrading the MNB-1000 firmware from v1.32 to v1.4, the value of property APDU Retries changes to 0. This will cause problems with any MNB-1000 that make BACnet requests. Environment MNB-1000 v1.32 Cause Firmware v1.4 change APDU Retries to 0, which the value needs to be to 2 or 3. Resolution Set the value of APDU Retries to 2 or 3 using WorkPlace Commissioning Tool or any other tool capable of changing that property. To change the APDU retries follow these steps: Open WorkPlace Commissioning Tool Discover MNB-1000 and select its properties Select the Advance Tab Change the APDU retries to 3 Select OK then restart the MNB-1000 Note: If there problems with COV, make sure this property is set to a value of 2 or 3.

Issue How can an override of a nciMinFlow SNVT be done directly from a container in Niagara R2 WorkPlace Pro? Environment Niagara R2 WorkPlace Pro nciMinFlow SNVT Cause A direct override of a nci is not possible. Resolution However, a change to a nci can be done by doing the following in WorkPlace Pro: Copy and paste the DynamicCmd object from the Local Library\tridiumx\lonworks\conversion folder into the Workspace Link the nciMinFlow property on the VAV shadow object to the Link property on the DynamicCmd object In the Config tab of the DynamicCmd properties, configure the floatConversion properties as follows: 1st dropdown: Volumetric Flow, 2nd dropdown: liters_per_second, 3rd dropdown: cubic_feet_per_minute In the Visual tab, type "MinFlow" in the float box Apply the changes In Monitor mode, right-click on the DynamicCmd object, and select MinFlow Enter the desired value in CFM.  The nciMinFlow SNVT in the VAV controller will update the value

Issue If power is removed from a UNC, how long before the UNC shuts down? Environment UNC Cause A UNC will not immediately shut down after power is removed. Resolution By default, the number of seconds to elapse after detecting an AC power failure and beginning the shutdown of the UNC or ENC is 60 seconds. This can be adjusted by opening the drivers.properties file and changing the value referenced in the power.shutDownDelay entry. For more information refer to the NiagaraSysmonEngNotes.pdf

Issue When creating links between an Enterprise Server and a UNC, the process takes 2 to 3 minutes per link. Why? Environment Enterprise Server UNC (Universal Network Controller) Cause The Enterprise Server station's address book may contain a UNC (or more than one) that does not exist or is offline. Resolution If a UNC no longer exist or is offline, it will slows down the link creation process. Remove the entry from the address book and restart the station, or, enable the UNC so that it is online.

Issue A UNC-5x0 fails to start its station and reports the error "Driver failed to load license". How can this be corrected? Environment UNC-5x0 Cause The error indicates a failure in the flash memory. Resolution Field repair of the UNC-5x0 is not possible. Contact Product Support Services to obtain a return authorization (RA) number.

Issue In a Niagara R2 / MicroSmart integration, what's the optimal method to transfer data from a UNC station to all the MicroSmart controllers connected to its RS-485 port? Environment Niagara R2, Niagara G3 MicroSmart controllers (versions 10 & 11) Cause Sharing data between controllers Resolution The MSGlobalDataOut object will transmit data, from a UNC station, onto the MicroSmart (RS-485) bus using a MicroSmart global broadcast channel. Then, within each controller, a point can be programmed to access the data from that specific channel number. Only controllers with firmware revision 10 & 11 support MicroSmart global broadcast channels. MicroSmart controllers with a capacity of 64 points, like the MSC-MPC, can receive information on all 122 global channels. MicroSmart controllers with a capacity of 48 points, like the MSC-P1500 series, can only receive information on global channels 1 – 24. See the MicroSmart Driver Engineering Guide (F-27327) for more details on the MSGlobalDataOut object. See the DMS Operator Interface User’s Guide (F-25467) for more details on MicroSmart Global Broadcasting.