Building Automation Knowledge Base

Issue A network of GCM-86000s with EtherNet NIMs does not have bi-directional communications between all GCM/ NIMs. It is a shared network with routers. Some symptoms reported include: A GCM/ NIM may be able to send to some GCM/ NIMs, but not to others. A GCM/ NIM may be able to receive data from some GCM/NIMs, but not from others. A GCM/ NIM may be able to send to a GCM/NIM, but not receive data from that GCM/NIM. You might be able to "ping" all GCM/NIMs on the network, and ACCESS all of them from the GCM menu, but still have issues as in 1-3 above. Product Line TAC IA Series Environment GCM-86000 series (including LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK) EtherNet NIM (GCM-ETH-001) Shared (customer's) EtherNet LAN with routers Cause In the NIM block of one or more of the affected GCM/ NIMs, the IP Multicast address (IPMLT) is set incorrectly. In the following example, the NIM block parameters were taken from a network of four GCM/NIMs, experiencing all four of the issues noted above.     GCM#1 GCM#2 GCM#3 GCM#4   5.4A 5.3A 5.4A 5.4A   11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.019 010.020.000.019 010.020.000.019 010.120.000.019 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 Resolution On a shared network with routers, the IP Multicast address (IPMLT) should be the same as the Panel IP address (PNLIP); IPMLT = PNLIP. Using the appropriate FLASH clear procedure, and set the NIM block parameters so that IPMLT = PNLIP. In the example below, make the changes to the IPMLT as high-lighted in yellow.   GCM#1 GCM#2 GCM#3 GCM#4 GCM Rev. 5.4A 5.3A 5.4A 5.4A NIM Rev. 11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 See the Nim Networking and Configuration Guide, F-25955-4, Chapter 2, "GCM Shared Network Address Guidelines (Routed Network)" for details. For EtherNet NIMs with firmware revisions 11.2P or 11.2T, see "Special NIM Address Switch Functions" for the REVISED FLASH clear procedure. For EtherNet NIMs with firmware revisions 11.1F or earlier, see "Flash clear" procedure for GCM Ethernet NIMs (GCM-ETH-001) with firmware prior to revision 11.2P.

Issue A red exclamation mark is seen with a discovered MNB controller icon in WorkPlace Commissioning Tool Product Line TAC IA Series Environment I/A Series WorkPlace Commissioning Tool I/A Series Micronet BACnet controller (MNB) Cause The WorkPlace Commissioning Tool has lost communications with the BACnet device Resolution Resolve the BACnet communications issue. Refer to BACnet MS/TP Bus Communication Troubleshooting Checklist. Refer to the table below which is extracted from the IA Series MicroNet BACnet WorkPlace Commissioning Tool and Flow Balance Tool Users Guide. Icon and Type Applicable Devices Meaning Remote I/O Warning MNB-1000 A remote I/O module connected to the MNB-1000 controller is in a state other than "online and configured" (status code 0x03). Lost Communication All Devices The Tool is no longer able to communicate with the device. Operation in Progress All MNB-xxxx Devices Device is in the midst of an operation. For example, the device may be undergoing a firmware upgrade, or an MNB-Vx VAV Controller may be performing a Check Rotation.

Issue Error "Software Releases are incompatible, Local 2.301.532v1, Remote:Null" is displayed when accessing a UNC with the I/A Series WorkPlace Pro software. Product Line TAC IA Series Environment I/A Series (Niagara) R2 UNC Cause A Firewall is blocking part of communications between the UNC and the computer running the WorkPlace Pro software. Resolution For proper communications operation, the I/A Series (Niagara) R2 software requires specific Ethernet ports to be open through any Ethernet firewall that is between the WorkPlace Pro computer and the UNC. The default settings of a UNC specify the use of ethernet port 80 and 3011 for communications between UNCs, the Enterprise Server and WorkPlace Pro.  These two ports must be open for bidirectional communications for both UDP and TCP communications. See Procedure for configuring the Windows Firewall for use with the I/A Series R2 (Niagara) software.

Issue When printing a graphic page with Internet Explorer the printed page or print preview is blank. Product Line TAC IA Series Environment Internet Explorer 11 Java version 7 update 55 R2 gx graphic Cause Enable the next-generation Java Plug-in option is disabled in the Java control panel advanced tab. Resolution Enable the next-generation Java Plugin Restart the browser. If the next-generation plugin was disabled for security reasons please consult I/A Series R2 / G3 graphics are not displayed when using web browser after the Java version is updated to Java 7 Update 51 or later on how to add the site to the exception list so the graphics will load without having to disable the next-generation plugin.

Issue Every time you compile a program object you get a message saying the "Program is not signed"   Product Line TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Enterprise Server Cause Tridium's Niagara N4 product will at some point in the future require code signing Resolution Create the main certificate in our Workbench to be used for signing our Program Objects. Go to the top drop-down menu on the Workbench and select "Tools - Certificate Management". Note: do not open the Certificate Management of your Platform. That is different and will be used for our running stations, not for this purpose. On the "User Key Store" tab, press "New" to create a new certificate. Fill in all the required fields. Make sure you change the "Not After" date so the certificate does not expire in just 1 year. Select the specific "Certificate Usage" as "Code Signing"   Press "OK" and set a password for your certificate. Remember: this password will be asked by the workbench at the point of compiling your code. Now select the new certificate, then press the "Export" button below   Export the certificate without the private key. You will be prompted then to give your certificate file a name and store it in your computer. We would also recommend exporting the certificate again, this time with the private key included, and storing it with an indicative name, in case you want to transfer it to a different machine. Change tab and move to the "User Trust Store". From there, press the button "Import" at the bottom and select the certificate without the private key. It should appear in green as accepted in the windows above. Go to the top drop-down menu, and select "Tools - Options" Find the "Code Signing Options" on the left-hand side, and on the "Signing Cert" section select the certificate we have just created and accepted on our Workbench. Then press OK to confirm. Open the local host Platform, and double-click the platform Certificate Management. Select the tab "User Trust Store", then press the button "Import" and select again the certificate without the private key. On the station running locally, you can now compile your code. Note that the first time the Workbench will ask for your password (the one you assigned when creating the certificate). Add the password and see that the code now compiles with no certificate error If you try compiling code on a Jace, it will return the "Certificate not trusted" until you add the certificate to the Jace Certificate Management too. On the Jace Platform, double click the "Certificate Management", then select the tab "User Trust Store". In there, press "Import" and select your certificate without the private key. Your program objects will now compile correctly.  

Issue Factors to consider using oBIX vs. BACnet IP to exchange data between Niagara R2 and G3 systems Product Line TAC IA Series Environment Niagara R2 version 522 and later Niagara G3 version 3.4 and later Cause Planning factors to consider as to which method is better suited for the customer Resolution Either solution has pros and cons regarding implementation. One needs to think about what fits and how much engineering is required.  If the R2 UNCs (Jaces) are nearly full (CPU and/or memory or less than 40% idle time), then oBIX probably can't be used. It requires some resources to drop in the oBIX service. But if their CPU usage is good (> 40% idle time) and the resource count isn't near the limit, the oBIX service should fit into the UNC. With oBIX, one has access to much more information in the R2 station than with BACnet. BACnet just gives access to its standard objects (BV, BO, AV, AO, etc). oBIX would provide access to just about anything in the station, though some things might be in a string format. One could get trend logs and such using oBIX.  Please also note that R2 oBIX is server only - no R2 "shadow objects" exist to obtain remote oBIX data (e.g. from a G3 station). For additional details, refer to the following documents: Niagara AX-3.x oBIX Guide Niagara R2 to Niagara AX via oBIX Engineering Notes   With BACnet IP, one would need to set all the R2 points 'Foreign Address' field for any point to be available to the G3 station.  Then, configure the G3 BACnet network, and discover the R2 devices and points (Note that if the G3 station is a supervisor, or Enterprise Server, a BACnet license feature with the appropriate number of BACnet points must be purchased).   A G3 supervisor PC should handle 5000 oBIX or BACnet points, provided the station is properly licensed.  

Issue When commissioning I/A MNL800 controller in LonMaker LNS network management tool, an error will happen: One or more devices failed to update successfully, due to the following problem: "A device encountered an operational or messaging error while its configuration was being updated. (Subsystem: NS, #4031)" Product Line TAC IA Series, TAC Vista Environment Vista I/A MNL800 LonMaker Cause The issue is possibly due to more than one MNL800 controllers in the LonWorks network have the same Program ID defined in the WPT that causes the commissioning failed. Resolution Open the program of the MNL800 in WPT, right click in the blank place and choose Hardware Wizard. Click Next and modify the Program ID so that each MNL800 has unique program ID. Then it will be fine to commission them in LonMaker. There is also another method to deal with this issue. Please refer to Error: NS #4031 lcaErrNsUpdateFuncError A device encountered an operational or messaging error while its configuration was being updated (Subsystem: NS, #4031).

Issue An UltiVist client workstation failed to re-start and generated the following pop-up error: SYS3175 - A program generated an access violation at 1e1b1300. FIAHAPI.DLL 0001:00001300   Product Line TAC IA Series Environment UltiVist Cause Large file sizes cannot be handled by UltiVist. Resolution On the UltiVist client: Look for the almhist.d$$ file and delete it if it's greater than 10 megabytes in size.  The file is located in the \FI directory.  On a restart of UltiVist, this file will be re-created. On the UltiVist server: Look for the WSQxx.D$$ file in the \FI\ALARMS folder (where xx = workstation number) Follow instructions in The UltiVist server is not operating properly

Issue Can an internal modem be installed in the field on a Niagara G3 ENC. If so, what is the part number? Product Line TAC IA Series Environment Niagara G3, ENC-410, ENC-520 Cause Can an internal modem be installed in the field on a Niagara G3 ENC? Resolution An internal modem can be field installed on an ENC after purchase. No license changes are required. Both the ENC-410 and the ENC-520 uses the same part number, UNC-410-MDM. Reference the Replacing the Modem section of the TAC I/A ENC-xxx Installation Instructions documents for details on installing the internal modem. ENC-410 (document #F-27415) ENC-520 (document #F-27416) Reference Configure a Niagara G3 ENC serial port for dialup modem on setting up the port for dialup modem.   

Issue Obix is being used import logs from the R2, UNC-520 station into a Niagara G3, ENS. The problem is that some logs are being split into multiple histories in the ENS. A single log in the UNC is split into multiple histories when imported into the ENS. Product Line TAC IA Series Environment Niagara G3, ENS Niagara R2, UNC-520 Cause The problem is on the R2 side. The R2 web server uses multiple threads, each servicing a single HTTP request. The R2 oBIX server has a method to resolve the requested URI to an object in the station - usually a Node of some kind. If multiple requests are coming into the oBIX server at the same time, the URI resolution can be invoked by multiple threads. So if one thread resolved a URI to a particular Node, then a second thread came in and resolved a second URI to a second Node, sometimes the second Node could be used to fulfill the first request (as well as the second request). This resulted in multiple copies of the same history when brought in to the G3 ENS.    Resolution Once this problem was clearly identified, the solution was simply to synchronize access to the URI.  The new obix-2.301.535i.beta.jar synchronized this process to eliminate the splitting logs. Download and install the new R2 obix-2.301.535i.beta.jar file in all UNCs which archives their logs to the ENS. Reference How to install an I/A Series R2 JAR File for more information.

Issue MN-S# sensor connected to MNB-1000 showing all segments lit up Product Line TAC IA Series Environment I/A Series MNB-1000 Cause Connecting a UI to a Binary Input set as a binary type "pulse" in the MNB-1000's database will cause this. Resolution Per UI inputs of the MNB-1000 do not support pulse inputs, pulse inputs connected to an MNB-1000 must use a DI input.  Correct the database so the pulse input uses one of the DI inputs. Connect that DI to a Binary Input object set to binary type "pulse." Compile and download and the issue will clear. 

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