Building Automation Knowledge Base

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

Issue The alarms in the UNCs stop archiving to the Enterprise Server database. The process was working before and nothing was changed. Product Line TAC IA Series Environment I/A Series R2 using the Cloudscape database Cause The size of the Cloudscape database has grown too large. This may cause issues with the system. Resolution Reduce the size of the Cloudscape database by deleting older alarms and logs. Refer to this document for details on how you can delete old alarms and logs. For details on the CloudscapeAdmin utility mentioned in the document, refer to How to remove data for all logs prior to a specific date in a Niagara R2 Enterprise Server.   Switch to using a SQL database instead of the default Cloudscape database if there is a requirement to keep old alarms and logs for a longer period.   There isn't a known limit where the size of the Cloudscape database can grow before the possibility of problems starting to occur. It is different for each site. As a guideline, it is recommended that SQL database be used if the size of the Cloudscape database has to be greater than 2GB.

Issue Require LonWorks shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11 Product Line TAC IA Series Environment I/A Series R2 Cause The lonDanfoss module prior to version r2.301.529 does not have the shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11. Some NCIs cannot be read if a DynamicDevice is used. Resolution The shadow device object for Danfoss device with program ID 80:0:8:3c:a:84:4:11 (VltFc100V121) is available in lonDanfoss JAR file version 2.301.529a. You can download the JAR file here. This is also available in I/A Series R2 version r2.301.532. Refer to How to install an I/A Series R2 JAR File for the procedure to install an updated JAR file to an I/A Series installation.

Issue When using the LOYTEC NIC709-USB100 LON Interface every time an attempt is made to connect to an MNL controller via WorkPlace Tech 5.X it gives an error "installing device driver" and causes the PC to lock up. Product Line TAC IA Series Environment WorkPlace Tech 5.x Loytec NIC709-USB LON interface Cause WorkPlace Tech 5.x is not compatible with Loytec LON interfaces. Resolution Only Echelon LON interfaces are supported in WorkPlace Tech 5.x due to it utilizing the Echelon Open LDV driver. The WorkPlace Tech installation instructions notes the following as part of the hardware requirements:- Echelon™ LonTalk™ adapter card, WPA-LON-x. Since many newer notebook computers do not have a PCMCIA card slot and therefore must use a USB LON interface an Echelon U10 USB interface (75010R) can be utilized. Also see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for an adaptor that can be used to convert PCMCIA to Express card.

Issue Will the TE200AD24 sensor from Greystone Energy work with a MNB controller? See the datasheet. Product Line TAC IA Series Environment MNB controllers Cause Retrofitting an existing 3rd party control system with a MNB controller Resolution Any 10k thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the MNL/MNB controllers. An 11k shunt resistor wired in parallel with the sensor (1/8 watt, +/- 0.1% tolerance) is also required. See What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? The inputs only take a 10k resistive load. So, for the setpoint slider, use a 10k linear pot. The datasheet says the AP model comes with a 20-30k pot and that you’ll have to call for other values. The 5 Vdc source required is not available on the MNB-300. It is available on the MNB-1000

Issue Master / Slave schedules not working Product Line TAC IA Series Environment I/A series R2 Niagara Cause When Master / Slave schedules not functioning properly the most common cause is an issue with the Address books. Another issue that can cause this is the firewall application on the Enterprise Server computer. Resolution To confirm it is an Address book issue conduct the following test: Create an AO object in the Master device (typically the Enterprise Server) and the Slave device (typically the UNC).  Link the output of the AO in the Master device to the input of the AO in the Slave device.  Link the output of the AO in the Slave device to the input of the AO in the Master device.  When viewing the AO's at each station in the WorkspaceEditor there should be little boxes on both sides of each AO indicating both devices can send and receive data.  If an Address book issue exists there will be a box missing at one device or the other.  To correct this issue: Reboot which ever station only shows one box by its AO.  If the issue persists go to step 2. Clear the address book entries in the device that has the AO with both boxes (this is usually the UNC) and reboot the device.  When the station comes back up carefully re-enter the Address book data and then check each AO to make sure both have two boxes.  Typically this will resolve the issue, but until both AO's have boxes on both sides the issue is not resolved.  It may be necessary to clear and redefine the address book a second time or clear and redefine the address books in both devices to pass this test.  Once the AO test is successful the Master / Slave scheduling will link and function as expected. Ensure that ports 80 and 3011 are added as exceptions in the firewall application. Refer to Which antivirus software is compatible with Niagara R2 and G3? for details.

Issue To communicate directly with a laptop to a DMS Microsmart controller requires an interface adapter. The model number of the adapter is MSC-LIM. It is obsolete. Does it have a replacement? Product Line TAC IA Series Environment DMS Microsmart revision 10 and 11 Cause Obsolete part Resolution There is no replacement for the MSC-LIM, but there is a repair option. See Repair or replace an obsolete part from the Network 8000 and DMS product lines.

Issue The appropriate jar files have been installed in the host computer and in the UNC-520's remote library.  For more information see Lon jar files required to integrate a Proview display into a Niagara R2 UNC. The shadow object for ProView successfully pasted to the Workspace.  Right-clicking on the shadow object and selecting the wizard generates a pop-up error indicating a missing resource file. Product Line TAC IA Series Environment Niagara R2 ProView Cause The host computer has never been used previously to configure ProView and the installer program was not performed. The lonworks bin directory is missing the executable named DRFupdate.exe.  Also, there are other support files that should exist in this directory. Resolution Run the installer executable file which comes with the ProView zip package on the host computer.  The ProView zip package can be downloaded from The Exchange Download Center.

Issue WorkPlace Tech menu disappears when an application is opened. WorkPlace Tech Tool "Application Menu" and some "Tools Menu" entries missing or grayed out and WorkPlace Tech "Application Menu" and some "Tools Menu" entries are missing or grayed out did not help. Repairing and re-installing WorkPlace Tech and re-installing Visio 2007 did not help correct the issue. Host pc was Windows 7 Pro 32-bit. Product Line TAC IA Series Environment WorkPlace Tech 5.8.6 and earlier Cause An update to Adobe Acrobat Pro (done between May 12 and May 21, 2014) broke WorkPlace Tech 5.8.6 / Visio 2007. The exact update number is not known at this time. Resolution Remove the update from Adobe or uninstall Acrobat Pro.

Issue Enable or disable I/A Series R2 alarms via a graphic page Product Line TAC IA Series Environment I/A Series R2 Cause Alarming for an I/A Series R2 alarmable object can be disabled or enabled by accessing the object's properties, 'Alarm Setup' tab using WorkPlace Pro. In most cases, the end user is not going to use WorkPlace Pro to access the system. They will normally access the system via the graphic pages in a web browser. Resolution Create program logic in WorkPlace Pro and use Binary Output objects to link to the alarmable objects via 'Flex' objects. The BO objects can be linked to a GxPage. Below are 2 examples with an Analogue Input object and a Binary Input object. Enable / disable alarm for an AI object The FlexLimitEnableBits object can be found in tridiumx > programlib > control. Link the AI 'limitEnable' to the FlexLimitEnableBits 'link'. The BO to enable / disable the high limit alarm is to be linked to the FlexLimitEnableBits 'highLimitEnable'. The BO to enable / disable the low limit alarm is to be linked to the FlexLimitEnableBits 'lowLimitEnable'. Create suitable command texts for the BO objects.   Enable / disable alarm for a BI object The FlexBoolean object can be found in tridiumx > programlib > control. Link the BI 'alarmValueEnabled' to the FlexBoolean 'link'. The BO to enable / disable to alarm to be linked to the FlexBoolean 'propertyInput'. Create suitable command texts for the BO object. Note: The FlexLimitEnableBits object can only be found in programlib module version 2.301.532d.v1. Install this to the Enterprise Server or UNC to use it. Refer to How to install an I/A Series R2 JAR File for an example of the procedure to install an I/A Series R2 JAR file.

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue The Following error is displayed when attempting to use webUI: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecptionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro 532 Cause Some servlets which the browser uses were left out of the webUser-2.301.532.jar files. Resolution The plan is to correct this issue in the next maintenance build release. The workaround is to replace the current webUser-2.301.532.jars with the webUser-2.301.530a jars. Reference How to install an I/A Series R2 JAR File.

Issue How can a Viconics BACnet thermostat instance number be changed with Niagara G3? Product Line TAC IA Series Environment Niagara G3, ENS, ENC-520 Cause The device Default Device ID is set to: 7x000+MAC address. The MAC address being the current Mac address of the BACnet device. Example, when a VT7300C5018B thermostat with a MAC address of 7 is connected to a network, its default Device ID will be 73007. There will be Device ID conflicts when the same Viconics model is used on multiple MS/TP networks and uses the same identical MAC address. Resolution How can the instance number be changed in a Viconics BACnet thermostat? lists how to change the Device ID (instance number) via the Viconics thermostat. However, it only allows for change of the MAC address portion of the Device ID. When changing the MAC address portion of the instance number is not enough, Niagara G3 can be used to change the entire instance number. The steps to change the Viconics thermostat instance number are as follows: Open (double-click) the BACnetNetwork Under the Database window, highlight the Viconics stat you want to change the instance number Click on the DeviceID button at bottom of screen and click yes Highlight the DeviceID number and change it to the desired number and click OK This screen show the device number it is being changed from to the device number it is being changed to – click OK If the change was successful, you should get a pop up stating: "Successfully changed remote device ObjectID!"

Issue XIF and Device Resource files for the Schneider Electric SE7000 Series Room Controllers Product Line EcoStruxure Building Expert, Field Devices, TAC IA Series Environment SE7000 Series Room Controller Cause In order to commission Schneider Electric SE7000 Series Room Controllers into an LNS system, the XIF is required. Resolution LonWorks External Interface Files (XIF) SE72_73_PIR.XIF (80:00:10:55:00:04:04:20) SE76_PIR.XIF (80:00:10:55:00:04:04:21) SE76RH_PIR.XIF (80:00:10:55:00:04:04:22) Device Resource File for XIFs listed above. For Datasheets for the SE7000 Series Controllers, see Where to find datasheets and information on the SE7000/SE8000 series room controllers.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue Various issues have been observed regarding the use of the I/A Series R2 WorkPlace Pro or I/A Series G3 Graphics access.  The following is a partial list of known issues caused by the Ethernet firewall built into the Trend Micro Internet Security Suite software: When attempting to install an R2 UNC license using the Admin Tool, the error "Unable to install license" is displayed. When attempting to connect to a UNC from the WorkPlace Pro tree, a "Cannot connect" error occurs. When attempting to access G3 graphics using the web browser, the user is unable to log into the station serving the graphics. When attempting to access R2 graphics using the web browser, the user is unable to display the graphics pages. When attempting to paste a .gif file to a UNC's remote library, WorkPlace Pro stops responding and must be closed with Windows Task Manager. When attempting to open a local station on the computer, using WorkPlace Pro, the Windows hourglass is displayed and the station never opens. This list will be updated as additional issues are encountered. Environment Computer running "Trend Micro Internet Security Suite" I/A Series R2 (Niagara) WorkPlace Pro software or attempting to use the computer to view I/A Series G3 (Niagara) graphics. Cause The I/A Series R2 software requires bi-directional communications over Ethernet port 80 unless the software has been user-configured to use a different Ethernet port. The Trend Micro Internet Security Software Suite has a built-in firewall that blocks incoming access to Ethernet port 80.  The Trend Micro software does not allow this port to be unblocked because it considers web access to a "workstation class" computer as a security risk. Resolution The best solution to this issue is to use a different Internet Security software package on the computer that does not block the use of Ethernet port 80.  One approach is to use the "Server" version of Trend Micro Internet Security instead of the "Workstation" version.  Since port 80 is typically used on server systems as the IIS (Internet Information Services) access port, the Server version of the software does not block that port. The alternate solution is to configure the I/A Series R2/G3 (Niagara) software to use a different Ethernet port for HTTP communications and Web services.  This change would need to be made in the R2 or G3 software installed on the computer as well as in every UNC or ENC being accessed from this computer. See New installation of the I/A Series (Niagara) R2 WorkPlace Pro software cannot connect to existing UNC for more information.

Issue Downgrading an UNC to an earlier Niagara build Product Line TAC IA Series Environment I/A Series R2 Universal Network Controller (UNC) Cause Station is unable to run in an UNC with newer version of Niagara R2 because a 3rd party module does not have an updated JAR file Resolution The procedure to downgrade an UNC would be to use the version of WorkPlace Pro that you want the UNC to be and commission the UNC as per what you would do for a new UNC or to upgrade an UNC. The modules installed in the station should also match the Niagara version of the UNC. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330?. Refer to Procedure 4 on pages 9 and 10 of the UNC-520 Installation Instructions for details on installing the software to an UNC-520. It is important to note that newer UNCs with the newer boot flash chip requires I/A Series R2 version r2.301.527 or newer. Installing the UNC with newer boot flash chip with an I/A Series R2 version lower than r2.301.527 will make the UNC inoperable. Refer to Cannot get my I/A Series (Niagara) R2 UNC to boot after downgrading the system software to a version earlier than release 529 for details.

Issue BACnet Service does not start after enabling BACnet IP on a UNC station. The following error messages are seen in the UNC standard output. ERROR: Error initializing IP link layer. [IpLinkLayer.updateLocalAddress] java.lang.NoSuchMethodError: tridium/nre/Platform.getLocalHost()Ljava/net/InetAddress; ERROR: Cannot startService [Sys: BACnetService [12] BACnetService] java.lang.NullPointerException ERROR: Run error [BTrprt] java.lang.NullPointerException Product Line TAC IA Series Environment I/A Series UNC running at version r2.301.5xx prior to version r2.301.535 with BACnet 2.305.535a. Cause Most I/A Series R2 Niagara JAR files are backward compatible. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330? for details.  There were some changes to the BACnet service IP to support the new JACE-603/645 platforms. Because of these changes to the R2 core, the BACnet 2.305.535a JAR file is not backward compatible.  Resolution Upgrade the UNC to version r2.301.535. Refer to the Installation Instructions for upgrade procedure. 

Issue What is the Part Number for the optional battery for the JACE-NXT (TRD-NXT-R2)? Product Line TAC IA Series Environment I/A Series R2 JACE-NXT (TRD-NXT-R2) Cause An optional battery is required for the JACE-NXT (TRD-NXT-R2). Resolution The part number for the optional battery is TRD-NPB-BATT, per the Spec Data sheet for the JACE-NXT, F-27769. There is also an optional UPS that includes a battery, TRD-NXT-UPS, per Hardware platforms to replace the I/A Series R2 UNC-600 or UNC-610. See Product Announcement PA-00223 for further information on the JACE-NXT.   *Update - The NXT platform has been withdrawn. Refer to PA-00373 for details. 

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.