Building Automation Knowledge Base

Issue The COM ports are defined and the communications works great but when the ENC is rebooted it is unable to start up the serial port (COM3), it says “COM3 is not a valid port”.  However, once the station is running COM3 can be typed in the drivers properties and it works fine.  Environment ENC, G3, Niagara Cause The station was loading the "Drivers" before the "Services".  The Services must come first to prepare the ports before the Drivers are loaded. Resolution Open the running station in Workbench, right click on Config and pull down to "Reorder".  Change the order to load the Services first, save the change and reboot the station. 

Issue How many DUIC-5P-12V units can be used simultaneously on a MNL-800? Environment MNL-800 Cause Application-specific requirement for multiple contact status monitoring Resolution According to Smartware Technologies (www.smartwaretech.com), the makers of the device, up to four DUIC-5P-12V units can be connected to a MNL-800 simultaneously. 

Issue Microsoft Hotfix changes the HostId on I/A Series (Niagara) R2 and G3 Enterprise Server or Engineering workstations. See TPA-IA-11-0007.00 for details. Product Line TAC IA Series Environment I/A Series R2 and G3: All 32-bit versions of software installed on 64-bit versions of Windows 7, or Windows Server 2008 R2. Cause Microsoft recently released a hotfix for an issue that affects machines running x64 versions of Windows 7 and Windows Server 2008 R2, described in knowledge base article 2603229. The Windows registry contains entries to designate the organization and owner name that correspond to the computer. Each of these registry entries has a 32-bit and 64-bit version. Prior to applying the hotfix, when the OS was installed and setup for the first time, only the 64-bit version of the registry entries were written, leaving the 32-bit registry entries at the factory default value. I/A Series software HostIds are generated from multiple pieces of information gathered from the registry and hardware components of the host platform. The changes made by this Microsoft hotfix will cause the HostId to change on Windows 7 x64 or Windows Server 2008 R2 x64 machines running 32-bit I/A Series G3 or R2 software. Resolution See TPA-IA-11-0007.00 for recommended solution. NOTE: The TPA indicates that the patch is in the I/A Series G3 "Recovery Files" folder.  The files are version dependent and are located in the Release 3.4.64, Release 3.4.67,  Release 3.5.34, Release 3.5.39 or Release 3.6.31 folder, as appropriate for the specified version.  For other versions, option #1 must be used.

Issue UNC was upgraded to R2 release 529 from an older version and when the station was started, the following error message was displayed in the Standard Output Window: ---------- Station Starting:   THU MAR 26 14:43:09 2009 ---------- Tridium Niagara Station, r2.301.529.v1 [GafbBldg857] ERROR: Reading FlexSnvtTempSetpt [3928] FlexSnvtTempSetpt#link: 60 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException   Environment UNC-520 with release 522 or 529 software installed. Cause Incompatibility in the FlexSnvtTempSetpt object between the release 514 and release 529 versions of the jar file. Resolution The best way to correct this issue is to perform a manual upgrade of the existing version 514 station. Use the release 514 WorkPlace Pro "Admin Tool" DbAdmin function to backup the running station and get the station as a .sns file to the computer. Use the DbAdmin function to convert the station from .sns to .xml. In the release 529 installation folder, use the AdminInstall command to start the release 529 version of the NiagaraD service. Copy the station folder containing the station to be upgraded from the release 514 stations folder to the release 529 stations folder. Start the release 529 AdminTool and open the Localhost. Highlight the station to be converted. Select the DbAdmin tab and use the convert local function to convert the station from .xml to .sns The converted station is now ready to be installed into the UNC that has already been loaded with I/A Series R2 release 529 software. This same procedure can be used to convert a 514 station to 532 by substituting release 532 for the release 529 references. above.

Issue A jobsite of MNL controllers was done with WorkPlace Tech 4.x.  The original databases are no longer available.  Can they be uploaded with WorkPlace Tech 5.x and will the upload convert them from 4.x to 5.x? Environment WorkPlace Tech versions 4.x and 5.x MNL controllers Cause Loss of original controller databases Resolution Uploading a MNL controller's program does not change anything within the controller.  Only downloads do. If a MNL controller was programmed with WorkPlace Tech 4.x and is uploaded with WorkPlace Tech 5.x, the uploaded file can only work with version 5.x.  If the resulting file is then downloaded to the same controller, the program version in the controller will then be at 5.x.  It will no longer work with 4.x.

Issue A Niagara G3 ENC is not communicating via the ethernet (RJ-45) jack.  Here is the output from a serial system shell connection: Press to stop autoboot... Autobooting... Loading image from on-board nand flash ppc824x(james) booting Amic29L040A starting /ffs0 filesystem ETFS_FS_2048 starting message queue handler i2c: Using 100Mhz freq divider DINIT Press ESC to restore factory default username and password... mount: Can't mount / (type io-net) mount: Possible reason: No such device or address if_up: retries exhausted ifconfig: SIOCGIFFLAGS en0: No such device or address writing to routing socket: Network is unreachable : Network is unreachable if_up: retries exhausted ----------------------TCP/IP Network Status------------------------------ ifconfig: SIOCGIFFLAGS en0: No such device or address ----------------------------------------------------------------------------------- Environment Niagara G3 Cause The output from the serial system shell connection indicates a on-board failure of the network communications. Resolution Replace the ENC.

Issue Using TimeSync Service in an UNC-520 to directly connect to an internet time sync service, but can not sync time in the UNC.  The following message is displayed in the UNC’s Standard Output Windows when the TimeSyncService debug is turned on: "Error: java.SocketException Message: Timesync aborting: not all servers responded."   Environment Niagara R2 all versions, UNC520, UNC-410, Enterprise Server Cause The port used by R2 TimeSyncService is typically blocked somewhere on the network. Niagara R2 TimeSyncService uses TCP port 37 by default.  Port is block by network domain security policy. Resolution Make sure that all three of the client’s TimeProtocolServer properties are filled in. If only one TimeSync server is being used, enter it for all three TimeSyncServer properties. If the UNC or Enterprise Server still do not sync to the time sync server, then the port may be blocked. The port used by the TImeSyncService must be open. Contacts the site’s IT department and make sure port 37, or whatever port the time sync is configured for, is opened.   NOTE:  I/A Series R2 utilizes TCP port 37 with the standard TIME format (RFC-868).  The official NIST website indicates the TIME protocol using TCP 37 will no longer be supported on March 1, 2013.  R2 does not support other formats (e.g. UDP or NTP).  The recommendation is to configure the Enterprise Server as a time sync server only and configure the UNCs to synchronize to the Enterprise Server's computer time.  The computer running the Enterprise Server will then need to use the standard Windows time sync mechanism and not the R2 time sync mechanism to maintain the time for the computer.

Issue Configured a new UNC / ENC with the proper IP address using a direct  Ethernet connection.  After installing the UNC / ENC on the customer's network, the UNC / ENC cannot be accessed.  It's IP address does respond when pinged. Environment I/A Series (Niagara) R2 -- UNC and  WorkPlace Pro I/A Series (Niagara) G3 -- ENC and Workbench Cause Customer's network (router, smart switch, etc.) is blocking one of the Ethernet ports required for communication with the UNC / ENC. Resolution If the UNC / ENC has been configured with the default ports, verify that those ports are open through the router and/or switch.  The selected ports need to be open for bidirectional TCP and UDP communications. The default ports for a UNC are 80 and 3011.  Additional information is available in the "IT Manager's Frequently Asked Questions" document and in the Niagara Networking & Connectivity Guide".   These documents also lists other ports that might be required depending on the optional features included in the UNC station.  These documents are included with the documentation set optionally installed with the I/A Series R2 software. The default ports for an ENC are 80, 1911 and 3011.  Additional information is available in the "Niagara AX Networking and IT Guide".  This document also lists other ports that might be required depending on the optional features include in the ENC station.  This document is included with documentation set optionally installed with the I/A Series G3 software.

Issue Need to save the application, configuration and COV link data for an MNB-controller so that in the event the controller fails, all the information can be easily reloaded into a new controller. Environment MNB family controllers WorkPlace Commissioning Tool, version 5.7.2 or newer Cause Need to save the application, configuration and COV link data for an MNB-controller so that in the event the controller fails, all the information can be easily reloaded into a new controller. Resolution The Backup and Restore facility of WorkPlace Commissioning Tool allows the user to backup the complete controller application, configuration, flow balance and COV link data for a single or multiple controllers or restore of a single controller on a given network in a simple operation.  The procedures for using the Backup and Restore functions of the WPCT are included in the WorkPlace Tech Tool version 5.7.2 release notes.  The Backup and Restore documentation is available via this WorkPlace Tech Tool release 5.7.3 Release Notes from The Exchange Download Center.

Issue Customer wants UNC to calculate times to turn outdoor lights on and off. Environment I/A Series (Niagara) R2 (any version) Cause Customer request for Scheduling functions based on SunRise and / or SunSet. Resolution There is a program called "SunClock" that be used for that purpose. Here is a brief overview of using program modules, if you are not familiar with their use. Create a folder, such as MyProgLib, for holding your program modules under the Niagara release folder: Extract the SunClock.sns file from the attached zip file and place it in the folder you created. Open WorkPlace Pro and open the UNC station into which the program module is to be placed. Open the Local Library and navigate to the folder you created in step 1 above. Copy the SunClock.sns module. Paste the module into the desired container within the UNC station. The SunClock program module has the following outputs: sLights        BooleanStatusType     Status Output On between LtsOn and LtsOff times     pLtsOn         BooleanPriorityType   Priority Output to turn lights on pLtsOff        BooleanPriorityType   Priority Output to turn lights off SunRiseTime    DateTimeType          Calculated Sunrise Time SunSetTime     DateTimeType          Calculated Sunset Time LtsOn          DateTimeType          Calculated Lights On Time LtsOff         DateTimeType          Calculated Lights Off Time The program uses the following properties to control its operation: LtsOnPriority          Priority level for turning lights on LtsOffPriority         Priority level for turning lights off Latitude               Geographic Latitude of location Longitude              Geographic Longitude of location SunRiseOffset          Minutes before sunrise to turn lights off SunSetOffset           Minutes after sunset to turn lights on DSTEnable              Enable Daylight Savings Time calculation DSTBeginWeekOfMonth    Week of month that DST starts, 1=first DSTBeginDayOfWeek      Day of week that DST starts DSTBeginMonth          Month of year that DST starts       DSTEndWeekOfMonth      Week of month that DST ends, 5=last DSTEndDayOfWeek        Day of week that DST ends DSTEndMonth            Month of year that DST ends Notes:  Enter Latitude as a positive number for locations in northern hemisphere Enter Longitude as positive number for locations west of prime meridian  Enter negative offsets to set control times after sunrise / before sunset      

Issue In a Niagara G3 station, attempts to send email fail with message:  invalid address error. Environment Niagara G3 Cause If spam filter is enabled the SMTP server will not route email, as long as the Reply to parameter is empty.  It will treat the message as spam. Resolution The Outgoing account under the email service should have an email address listed under the Reply to parameter. If an account is required in the Outgoing Account parameter, for example:  joe.jones@acme.com, the same email address can be entered in Reply to parameter. If no Account is required for the SMTP server to route email but the spam filter is enabled, enter a fictitious account.

Issue A seven day schedule has been setup in the MNB-1000 using WorkPlace Tech but I don't see any way to set the controller time? Environment WorkPlace Tech 5.X, Commissioning tool Cause The time and date in the MNB-1000 cannot be defined using WorkPlace Tech. Resolution Open the WorkPlace Tech Commissioning tool, locate the desired controller in the Device list and open the Device Properties for that device.  On the Device Properties - General tab there is a "Device Clock>>" button used to synchronize the MNB-1000 to the PC's time and date.  This is also where the Time Zone is defined for the MNB-1000.

Issue Need to write a setpoint value from one controller to the setpoint of a different controller but the receiving controller does not show up in the Link Builder Client list. Environment I/A Series Workplace Tech Commissioning Tool - Link Builder Cause Only controllers that contain AVCOV or BVCOV objects will show up on the Link Builder "Client" side.  Resolution Link Builder "Server" objects can only link to AVCOV or BVCOV objects in a "Client" controller.  Once an AVCOV or BVCOV object is created in a controller that controller will show up in the "Client" list.  A setpoint value from a "Server" controller can then be linked to a AVCOV object of a client controller and used as desired in the client controller.

Issue Workplace Commissioning Tool is showing a yellow triangle with red exclamation point on an MNB-1000 controller icon. Environment WorkPlace Commissioning Tool version 5.x.x MNB-1000 controller Cause The yellow triangle icon indicates that there is a firmware or Remote I/O Status issue on the RIO bus of that MNB-1000 controller. Resolution There are three ICON overlay symbols that can be displayed over the device icon in the WorkPlace Commissioning Tool.  These symbols are defined in the Device Icons table of Chapter 1 of the I/A Series MicroNet Commissioning Tool manual, F-27358.  Further information regarding the reason for the display of the Remote I/O Warning (yellow triangle with exclamation point) is found in Table 6.1 of that manual.  This document is installed along with the WorkPlace Tech Tool software package and can be accessed from the Help menu of the Commissioning Tool. Any R-I/O module status except Communicating OnLine is reported with the warning symbol being displayed overlaying the MNB-1000 device icon.

Issue No link LED on a Desktop's and Laptop's Network Interface Card (NIC). Environment Windows OS Cause Network interface card has power management feature enabled.  This will shutdown the network interface card if no activity is present, battery is low on power, or battery is intermittent. Resolution Disable power management features under Device Manager Network Adapters. 

Issue Can an internal modem be installed in the field on a Niagara R2 UNC, if so, what is the part number? Environment Niagara R2, UNC-410, UNC-520 Cause NA Resolution An internal modem can be field installed on an UNC after purchase. No license changes are required. Both the UNC-410 and the UNC-520 uses the same part number, UNC-410-MDM. Reference the Replacing the Modem section of the TAC I/A UNC-xxx Installation Instructions documents for details on installing the internal modem. UNC-410 (document #F-27321) UNC-520 (document #F-27391)  

Issue Hardware wizard has been run in the WorkPlace Tech Tool for this application and it shows that the application is configured for English units (Degrees F, etc.), not metric units (Degrees C, etc.) but some of the points still read in metric values. Environment LON Controllers WorkPlace Tech Tool software, version 5.x (or newer). Cause When a WorkPlace Tech Tool application file is upgraded from WPT release 4.0.x to WPT  5.x.x, it is possible that some information defined by the use of the Hardware Wizard may not migrate properly.  This problem has only been noted occasionally in applications migrated forward from WPT 4.0.x. Resolution A two step process is required to insure that the Hardware Wizard data inconsistencies are corrected in the application file. Run the Hardware Wizard and change the engineering units to Metric. Click [Finish] to save the changes.  Compile the application but do not download it. Run the Hardware Wizard again and change the engineering units to English. Click [Finish] to save the changes. Run the "Rebuild Application" function from the Application menu to reconstruct (and clean) the application database. Save the application file then compile and download the application to the controller. 

Issue When air temperature falls to 30 degrees F, the output values calculated by the Enthalpy object are incorrect as compared to performing manual calculation verification or humidity measurement Environment IA Series MNL-800 controller WorkPlace Tech Tool (any version) Cause The Enthalpy object limits the allowed range of its input values so as to maintain the resolution of the values it calculates.  These range limits are set based on the temperatures typically encountered when calculating enthalpy for mixed air, return air and supply air needs in air handlers. Resolution The following limits are used when processing the Enthalpy object inputs: Dry Bulb Temperature:  32 to 120 Degrees F (0 to 48.9 Degrees C) Dewpoint Temperature: 32 to 120 Degrees F (0 to 48.9 Degrees C) Relative Humidity: 1 to 100% Barometric Pressure: 19.94 to 39.79 in-Hg (506.5 to 1010.7 mm-Hg) Input values outside the ranges listed will be processed as if they were clamped to the listed limit.  For example if the air temperature (dry bulb) was 26 degrees F, it will be processed as if the temperature were 32 degrees F.

Issue When attempting to start the Niagara G3 AX Lon Tunnel Service, the following pop-up error appears: Could not start the Niagara AX Lon Tunnel service on local computer Error 1075: The dependency service does not exist or has been marked for deletion Environment Windows XP Niagara G3 Cause Two possible causes: Uninstalling WorkPlace Tech 5.7 and installing WorkPlace Tech 5.8. Installing a newer version (3.6.x) of the I/A Series G3 Software. Resolution Remove and re-install AX Lon tunnel software.

Issue The Echelon U10 USB LON adapter (part number ECH-75010R) does not include an interface cable.  Is a cable available with the proper connector for the MNL series controllers? Environment Echelon U10 LON network adapter Cause The Echelon U10 USB LON adapter (part number ECH-75010R) does not include an interface cable.  Is a cable available with the proper connector for the MNL series controllers? Resolution WPIA-CBL-1 This cable is available via iPortal.