Issue How can the default HTTP port for a Niagara R2 UNC station be changed? Environment Niagara R2 UNC station Cause The station need to change the default port 80 to a non-standard HTTP port in the httpPort text box. Resolution Do the following:  In WorkPlace Pro, open the station offline In the tree view, right-click on the offline station and select Go - Properties On the Properties sheet, click the Config tab Edit the httpPort text box, removing the default port of 80 and replacing it with your chosen port number (e.g. 8081) Click Apply In the tree view, right-click on the offline station and select Close Open the Admin Tool, and log into the UNC Right-click the station name (not the host name or address) and select Edit - Properties. This opens the station.properties file Add the following line to the station.properties file:  httpPort=[newport] (newport = port number from step 4), example httpPort=8081 From the file menu, choose File - Close. The system will prompt you to save any changes. Choose Yes. In the Admin Tool, click the Installation tab On the Installation Sheet, click Install Station Select the station from step 4, then click OK In the Confirm dialog box, click Yes In the Select Database Format dialog box, select the DB radio button, then click OK The system will load the offline database to the UNC, then re-boot the station. When finished, the message box will display "Installation Complete"

Issue With Niagara R2 UNCs using BACnet routers, router function quits when other routers are on the network. Environment Niagara R2 UNC BACnet routers Cause Niagara R2 station detected a routing issue and has disabled its routing functionality. Resolution When Niagara R2 stations encounter a network mis-configuration, such as multiple routers on the same BACnet network, it disables its routing functionality, to avoid a packet flood when multiple routers repeatedly circulate the same request. This routing functionality cannot be re-enabled without restarting the station. In some installations, this could be bad, as the installing engineer may not be able access the station remotely, or it may be difficult to reboot the UNC. Beginning with release 2.305.516, the BACnet service can be programmed to maintain its routing functionality even with such network problems. Do this by editing the bacnet.properties file in the host with the following line:  maintainRoutingEnabled=true. Note that after editing this file, from the BACnet service, issue the menu bar command "readBACnetPropertiesFile" to make changes effective.

Issue No alarms are displayed in the Niagara R2 Alarm Console. Environment Niagara R2 Cause Generally, this condition indicates that the Alarm Console is not properly configured with the Niagara station information. Resolution To configure the Alarm Console: Open the Alarm Console From the Address menu, select Enable Edit Type the appropriate password to enable editing (by default, this password is blank) From the Address menu, select Add Address. An input dialog is displayed that allows entry of the new station address record information In the Station Name box, type the name given to the station node that will be monitored In the Host Address box, type the computer name running the station. Use either the station host name or the actual IP address of the computer In the User Name box, type the user name for a user account that exists in the station. Typically, this is the same name (user account) used to access the station in WorkPlace Pro In the Password box, type the password for the station’s user account In the Confirm Password box, type the user’s password again to confirm it Click OK Click the Stations tab to verify that the new station address record was added to the Address Book. Note that if the new station address record appears red, a restart of the station is required for alarms to be routed to the console

Issue Can the Niagara R2 UNC-410 support an ASD network? Environment Niagara R2 UNC-410 ASD network Cause The UNC-410 does not support ASD communications because the RS-485 ports are not electrically isolated. Resolution Here is a list of all the Communication ports available on the UNC-410: Communications - all Versions One 10/100 Mbit Ethernet RJ-45 connector. One non-isolated RS-485 bus (up to 76.8 Kbaud). One RS-232 port, RJ-45 connector. One LonWorks port – 78.8 Kbaud FTT-10A with Weidmuller connector (maximum of 27 devices). Options Optional UNC-410-MDM Internal Auto-dial /Auto-Answer 56k modem (p/n UNC-410-MDM); RJ-11 connector for North American applications (uses RS-232 port when installed). For further information consult F-27322

Issue There are multiple versions of Niagara R2 software installed on a computer (i.e. 4.31, 5.14, 5.22, 5.29).   Stations will not open with the older versions. Environment Niagara R2 Cause By default, the Niagara service for the most recent version (e.g. 5.14) will run when a computer is started. And only one instance of the Niagara service can run at a time. Resolution In order to open stations with the older versions, the Niagara service for the appropriate version must be installed and running. To install the service for an older version (i.e. 4.31): Open the Console for the desired Niagara version (Start > Programs > Niagara 2.301.431.v1 > Console In the Console window, type the following: admininstall install /start If successful, you will see the following responses: Niagara service successfully installed. Niagara service successfully started. Now, stations will open using the older releases.

Issue If there is a routing problem with a MNB-1000, how can the routing table be cleared? Environment MNB-1000 Cause The MNB-1000 controller need to relearn the network information. Resolution Anytime there is a routing loop or a network mis-configuration on a BACnet internetwork containing MNB-1000 controllers, it is possible to get a network mismatch displayed in the status column of the WorkPlace Commissioning tool. Because the MNB-1000 controller has learned the mis-configured network information, its routing tables will have incorrect information. Currently, the only way to remove this information and fix the problem is to correct the network mis-configuration and reboot the MNB-1000. Upon restarting the MNB-1000 controller, if the problem still exists the network mismatch will still appear in the status column, indicating that the problem is not resolved. If the problem is resolved this message will not display.

Issue What are the default heartbeat values for the MNL controllers? Environment MNL controllers. Cause Reset heartbeat values to default values. Resolution The default values are: nciSndHrtBt=120sec nciRvHrtBt=300sec nciMinOutTm=5sec For further information on these values consult the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254)

Issue What are the supported speeds for the Ethernet port on a Niagara R2 UNC? The UNC is not communicating at 100Mbps Environment UNC Cause The Ethernet port on a UNC is auto sensing - meaning it gets its speed and duplex settings from the device (hub or switch) into which it is plugged. The UNC is capable of supporting 10 or 100 Mbps, full or half duplex communication over the Ethernet port. Presently, gigabyte speed is NOT available on the UNC. Resolution If the UNC is not communicating at 100Mbps and full duplex, the most likely causes are: The hub or switch does not support 100Mbps / full duplex communications There is a problem with the wiring between the UNC and the hub / switch.

Issue What components make up the LON-TERM1 and LON-TERM2 terminators? Environment LON-TERM1 terminator LON-TERM2 terminator Cause LON-TERM1 and LON-TERM2 terminators are required for MicroNet LonWorks network topologies. Resolution The LON-TERM1 uses a capacitor in series with a resistor with each part having the following specs: Resistor E19-607 52.3 ohms, +\- 1%, 1W, MF Capacitor E13-468 47 uF, +\- 20%, 50WVDC, Elec The LON-TERM2 uses a capacitor in series with a resistor with each part having the following specs: Resistor E19-608 105 ohms, +\- 1%, 1W, MF Capacitor E13-468 47 uF, +\- 20%, 50WVDC, Elec

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