Building Automation Knowledge Base

Issue Some schedules stop operating correctly after Daylight Savings Time (DST) changeover.  Environment I/A Series G3, all ENS and ENC with builds 3.5.4, 3.4.53.1, 3.3.31.2, 3.2.23.1 or earlier. Cause Any station with a schedule, of any type, with an event set to occur during the "advanced" (missing) hour between 2:00 AM and 3:00 AM on the DST changeover day. The resulting miscalculation of the schedule's "Next Time" or "Next Trigger" time could cause that schedule, or even other schedules in the station, to stop working. This typically affects downstream logic in the station. In some cases it was observed that the CPU usage on an ENC went up to 100% while calculating invalid next event times. Examples A station contains a BooleanSchedule with events at 12:00 AM and then again at 2:05 AM daily. At 12 AM the schedule executes normally and attempts to calculate the next event time. On the second Sunday in March the next event time calculates to a time that does not exist due to the DST change. This causes the Java thread that executes all schedules in the station to become tied up attempting to recalculate the time. A station contains a TriggerSchedule that periodically repeats every 15 minutes, with a range passing through the DST changeover time. On the second Sunday in March the next trigger time calculates to a time that does not exist (say, 2:15 AM). Again, this causes the Java thread that executes all schedules to become tied up attempting to recalculate. Resolution The solution to this issue is to upgrade the schedule.jar file in the platform to one of the versions below, or later. Files are available from The Exchange Extranet.  Release 3.3.31.2 (Download and extract schedule-3.3.34.1) If you are using a build that is higher than the above versions then you will not be affected by this issue.

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue MN-CI revision 4.1 returns an error 511 when sending a “Reset” command to a MicroNet 2000 controller. The controller does reset as commanded. Environment MN-CI rev. 4.1 software, MN-FLO, MN-FLO3T, MN-HPFC Cause The problem is caused because MN-CI rev. 4.1 sends the “Reset” command twice, and temporarily loses communications with the controller. Resolution The error is considered a nuisance and can be ignored.

Issue When accessing the VEO group of an LCM or GCM with XPSI revision 4.1 Terminal Mode, the data is displayed normally for about 90 seconds before it starts to become garbled. The problem begins at the top line of the display and progresses from the top down, one line at a time.   The arrow keys are not operable, cannot move the cursor to select attributes. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Unknown Resolution A work-around is to use a different terminal emulator instead of XPSI revision 4.1; possible alternatives are HyperTerminal or PuTTy.  PuTTY.exe can be downloaded at http://www.putty.org/.  Select putty.exe for Windows on Intel x86.

Issue In XPSI 4.1 Terminal Mode, there is a noticeable delay in the action of the “Escape” key when backing out of a Current Status or VEO group display screen. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Serial communications are slower with the Microsoft port controls used with XPSI version 4.1. Resolution The “Escape” key will work, it just takes a few seconds longer in version 4.1 than it did in earlier versions, such as 3.13.

Issue Between the second Sunday of March and the last Sunday of April, the I/A Series R2 Enterprise Server clock is one hour earlier that the time shown on the host computer. Between the last Sunday of October and the first Sunday of November, the I/A Series R2 Enterprise Server clock is one hour later that the time shown on the host computer. The noted times apply to the North American time zones.  Similar errors may also be seen in other time zones. Environment Any supported Windows operating system. I/A Series R2 (Niagara) software release 522 or newer Cause The Windows operating system has not been updated with the current daylight savings time rules update. The I/A Series R2 (Niagara) software, release 522 and newer includes the updated daylight savings time rules.   Resolution Download and install the appropriate Microsoft Windows operating system software update, per the Microsoft Knowledgebase article 955839 to update the computer's daylight savings time rules. The update can be downloaded from the Microsoft support web site at http://support.microsoft.com/kb/955839.  This Microsoft  Knowledgebase article contains links to the downloadable upgrade file for each of the affected versions of the Windows operating system as well as any related installation prerequisites.

Issue Alarms in UNC are not archiving to the Enterprise Server. Environment I/A Series R2 Universal Network Controller (UNC) and Enterprise Server Cause The UNC station and Enterprise Server station has their NotificationService 'archiveMode' property set to 'archive_disabled'. This is the default selection and it prevents notification from happening. Resolution Change the default settings in the UNC station and Enterprise Server:  Set the UNC station's NotificationService 'archiveMode' to 'archive_remote'. Set the Enterprise Server station's NotificationService 'archiveMode' to 'archive_local'. (The “archive_local” selection is valid only if the station is running the DatabaseService) The following have to be also correct in order for alarms archiving to happen: AddressBook entries should be properly setup in the Enterprise Server and UNC stations. Refer to Page 1-15 and 1-16 of the Niagara Standard Programming Reference for further information.  Supervisor checkbox in the UNC's NotificationService 'alarmArchiveAddress' property should be checked. NotificationClass(s) in the NotificationService container in both the UNC station and the Enterprise Server station have to be the same.

Issue Cannot enter a "." (period) into an Object Name of an application drawing using WorkPlace Tech 5.7.4 and newer.  It was possible with previous versions. Has this ability been removed? Environment WorkPlace Tech 5.7.4 and newer Cause The change to not allow a period in an Object Name was to make WorkPlace Tech compatible with StruxureWare. Resolution If a period must be use in an Object Name, do the following:  Open Notepad. Type the desired name (including period). Copy and paste it into the object's name.

Issue What is the procedure to upgrade an existing I/A Series Enterprise Network Server to a newer release of the G3 software? Environment Existing I/A Series G3 ENS installation. Newer release of the G3 software to be installed. Cause Upgrade Resolution Back up existing ENS station. Open the Application Director in the existing version of WorkBench and stop the running station then close Workbench. Install new release of the I/A Series G3 software by running the setup.exe program from the distribution file set (expanded zip file or CD). If the installer prompts to allow copying of settings from previous installation, allow the copy to proceed. At the end of the installation process, allow the installer to start the new Niagara Daemon but not Workbench. Under the Stations folder in the old installation of the G3 software, locate the folder for the station that was being run. Copy the entire folder locate in step 5 from the Stations folder of the old installation to the Stations folder of the new installation. Start the new version of the Workbench, then use the Application Director to start the copied station.

Issue Upgrading / downgrading a jar file in I/A Series G3 Environment Niagara G3 (all version) Cause Not applicable Resolution Do the following: 1. Shut down Workbench 2. In Windows Explorer, navigate to the C:\Niagara\<release>\modules directory 3. Find the original module (e.g. tacAsd.jar), and rename it (e.g. tacAsd.old) 4. Copy the new module in to the modules directory 5. Re-open Workbench, then go to Platform > Software Manager 6. Highlight the module (e.g. tacAsd.jar), then click Install, then click Commit 7. The module will be installed, and the ENC will re-boot

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue Continuum 1.9x and above will not install correctly on a PC / Laptop that is on a domain, One example: When trying to run the Continuum Database Initialization program the following error message may pop up: You must have local NT administrative privileges to run this application. Environment Windows OS 7 8 10 Continuum 1.9x 2.x Inet SQL 2005 SQL 2008 SQL 2012 Cause Microsoft has introduced the use of a higher level of security in the install of their SQL database software SQL 2005 / SQL 2008 / SQL 2012. When you install Continuum you need to make sure you are logged onto the PC / Laptop as a local administrator, in the case of a lot of a corporate networks, you are most likely logged on as ether a restricted user or a domain administrator, these logons do not have the privileges you need to install an SQL database. Resolution Step by step guide to creating a local administrator user on your PC / Laptop Go to "Start" then "Control Panel" in Windows (Windows 7 and above, top right corner change "view by" to "small icons" this will show all icons) Go to "Administrative Tools" Go to "Computer Management" / "Local Users and Groups" In users, right click on the right panel and add new user Fill in the user name and password, un-tick user must change password Tick password never expires then ok it Now go back into control panel and click on "User Accounts" Click on the name you just created, this will open the properties screen (Windows 7 and above click on "Manage user accounts") Click on "Group Membership" then select others, and highlight administrators (Windows 7 and above double click on name you created, click "group membership" click "other" then in the drop down select "Administrator") Apply this and then ok it. Log off your normal account and log back on as the new user you have just created

Issue Declaration of Conformity on I/A Devices Environment MicroNet 2000 Family of Products (MN Controllers & MN Sensors) MicroNet BACnet Family of Products (MNB Controllers & MNB-ROAM-IA) MicroNet LON Family of Products (MNL Controllers & MN Sensors) UNC/ENC Family of Products (UNC-410 & ENC-410 Controllers) UNC/ENC Family of Products (UNC-520 & ENC-520 Controllers) Cause Help locate information regarding Declaration of Conformity for I/A Series hardware. Resolution Information on Declaration of Conformity for I/A Series are available on The Exchange Download Center.

Issue Controllers that will operate in a  Master / Slave configuration, where values such as the setpoint, temperature etc can be shared. Environment MNL controllers LonMaker WorkPlace Tech Cause Configuration issue. Resolution The MNL 20RF controllers will not directly act in a Master / Slave configuration. If there is a requirement to share values between controllers, such as the setpoint, temperature etc. then these values need to be assigned to SNVT's in each controller, and the controllers bound together using LonMaker or similar.

Issue After using the I/A Series (Niagara) R2 Admin Tool Installation Wizard "Upgrade" process to install an earlier version of the R2 OS and NRE, the UNC will no longer reboot properly. The heartbeat LED remains turns on and stays on. The software was downgraded to a release earlier than R2.301.527. While watching the bootup process on a serial console connection, the bootup log shows the following message just before the UNC reboots: old clock frequency detected, modifying and rebooting -> Since the BOOT Flash chip does not allow its clock frequency to be changed, this "change, reboot, start, clock change, reboot" process will continue as long as the UNC is powered. Product Line TAC IA Series Environment UNC-410 with serial number 36218b and newer UNC-520 with serial number 36184b and newer Cause The UNC features a new bootflash chip that is incompatible with the older releases of the R2 software. When the affected UNCs are shipped by the factory the following yellow warning label is attached to the transformer cover: WARNING! This Universal Network Controller (UNC) features a new bootflash chip. To properly configure or install the software you MUST use one of the following releases. Release R2.301.527 or newer Failure to follow these instructions will cause the UNC to become inoperative. Refer to Product Announcement PA-00123 on The Exchange Download Center for more details. Resolution Contact Product Support to obtain a return authorization number. The UNC returned with this issue will be repaired by the factory for a nominal fee of $250.

Issue A version of the WorkPlace Tech Tool software prior to version 5.7 had previously been installed on the computer and licensed with an expiring license.  The WPT software was updated to version 5.7.x.  When the previous expiring license was about to expire, the next expiring license renewal was requested.  However, when the previous expiring license did expire, the new one also expired. Environment Initial WIBS/WPT license on computer created by installation of any version Wonderware for Intelligent Buildings Software (WIBs) or any version prior to 5.7 of the WorkPlace Tech Tool software (WPT). New version (5.7.x or later) of the WorkPlace Tech Tool software installed on same computer. Cause New license request was incorrectly generated using the WIBSPurchase ("Purchase WIB Software" icon) program instead of using the "Purchase WorkPlace Tech Software" icon on the computer desktop. Resolution Use the "Purchase WorkPlace Tech Software" icon on the computer desktop to request any license updates for version 5.7.x and newer of the WorkPlace Tech Tool software.

Issue When attempting to use Serial Tunneling through an I/A Series (Niagara) G3 system ENC, the following error message is displayed in the Application Director window: ERROR [....][Serial Helper] Denied Opening comm port 'COM1' javax.baja.serial.PortDeniedException: COM1 is already owned by dbgjmpr Environment I/A Series (Niagara) G3 ENC-520, ENC-410. Cause This error is reported when the operating system console enable jumper is installed on the front two pins of the MODE connector in the upper right corner of the ENC circuit board.  NOTE: This jumper is installed only when using a serial terminal running at 57600 baud and connected to serial port COM1 to troubleshoot ENC operating system startup / IP address issues. Resolution Remove the jumper and reboot the ENC.

Issue The station’s database indicates a “successful” start, however, the error message “Service Unavailable – Service disabled in remote station” is seen when attempting to tunnel with XPSI.  See I/A Series Enhanced ASD Driver - Release Notes for more information on this issue. Environment I/A Series (Niagara) R2 station, with VSerial service and ibsAsd service installed. XPSI 4.1 or newer. Cause The vserial and IbsAsd services use common tunnel software components, and having both services enabled at the same time causes conflicts in registering the services. Resolution The resolution to this issue requires that the I/A Series (Niagara) R2 station be running the ibsAsd 2.302.516b.v1 jar file, or later. In a station where communications with ASD controllers, and the ability to tunnel into the ASD bus with XPSI are both required, delete the vserial service and reboot the UNC.   In stations where both the ibsAsd service and the vserial service are required (not simultaneously), see the TAC I/A Series Enhanced ASD Driver Engineering Guide, F-27429-3, Appendix B, “Tunneling Example”, pp 123 – 130 for an application that will allow only one or the other service to run at a time, and prevent the conflict between them. This document and the I/A Series Enhanced ASD Driver - Release Notes are included with the I/A Series (Niagara) R2 software release R2.301.522 and newer documentation.

Issue When a Binary Input object is configured as a pulse counter, what happens when the time between pulses is longer than the interval specified in the “Pulse Input, Minimum Rate”? For example, the MNB-1000’s Fast Pulse Input, Minimum Rate  = 1 pulse per 4 minutes; what if 20 minutes pass between pulses? Environment MNL- controllers (MNL-5Rxxx, MNL-10Rxxx, MNL-15Rxxx, MNL-20Rxxx, MNL-800) MNB - controllers (MNB-70, MNB-300, MNB-1000, MNB-V1, MNB-V2) Cause Some meters transmit output pulses at a rate slower than the specified Minimum Rate of the controller. Resolution In the Binary Input object, the input is integrated over the time period, and the resulting calculated value is the object’s Output. If there is no pulse to count, the Output = 0 (no pulses, no measured output calculated over that time period), but the Count output will still be correct. Refer to the current Specifications Data Sheet for the controller for details on the Minimum Pulse Rate.

Issue Unable to override points in a MicroZone II from an I/A Series (Niagara) G3 station. Get error " javax.baja.sys.ActionInvokeException   at com.tridium.fox.sys.broker.BFoxComponentSpace$FoxTrapCallbacks.invoke(BFoxComponentSpace.java:355)...  ... at java.awt.Component.dispatchEventImpl(Unknown Source)  com.tridium.fox.session.ServerException: java.lang.RuntimeException: Invalid response during override.  Check username and password" Environment I/A Series (Niagara) G3 station with the tacAsd driver I/A Series Network 8000 ASD controller (MicroZone II, PEM-1, LIM) Cause The "User Name" and "User Password"  in the Property Sheet of the ASD device object (under the AsdNetwork object) in the ENC's station, and the USRn and PASn stored in the MicroZone II, PEM or LIM database do not match exactly. The USRn and PASn are case sensitive, accepting ONLY capitalized characters. The AsdZone2 device property sheet in the G3 station allows entry of lower case characters, which can cause a mismatch in the User Name or User Password, or both. Resolution Be sure to enter the correct User Name and User Password in the Property Sheet of the AsdZone2 device, and remember to use ONLY capital letters.