Building Automation Knowledge Base

Issue WorkPlace Commissioning Tool configured for BACnet IP is unable to discover MNB MS/TP devices connected to an ENC Environment I/A Series G3 Enterprise Network Controller BACnet Integration Cause The ENC station's BACnet routing is not enabled. Resolution In the G3 station, navigate to BacnetNetwork > Bacnet Comm > Network. Check and ensue that 'Routing Enabled' is set to true. 

Issue Windows installer fails to install an application Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows Server 2012 editions Windows Server 2012 R2 Cause Errors with the Windows Operating system are preventing the installation from completing. Resolution Run the file at the link below on the affected PC:   https://support.microsoft.com/en-us/mats/program_install_and_uninstall

Issue One folder, on a jobsite computer, contains all the DMS backups done over the past several years.  Since each backup contains multiple files, how can the files be identified and then grouped together for easy retrieval in the future? Environment DMS35, DMS350A, and DMS3500 (revisions 9, 10, and 11) Cause Multiple DMS backups were performed from the same jobsite computer. They were not grouped by name or date. All the backup files exist in one folder in a disorganized state. Resolution The files created from a database 'save' for a DMS35 or DMS3500 are: filename.IOC (stores DMS point IDs, records, alarm parameters) filename.UC (stores DMS point configuration elements) filename.PG (stores DMS tables and schedules) filename.UDP (stores UDPs in the DMS panel) The files created from a database 'save' for a DMS350A include the four listed above as well as: filename.Dxx (stores DCM tables, schedules, and other elements) filename.Uxx (stores DCM UDPs) where xx = DCM address 01-32

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue I/A Series G3 version 3.8 and N4 version 4.2 Weather Service not following redirects Product Line TAC IA Series Environment I/A Series G3 3.8.x I/A Series N4 version 4.2 or older  Cause The National Weather Service (NWS) started recently redirecting from an HTTPS to an HTTP connection. Current conditions are not updated in Weather Service. The following messages appear in station output:  TRACE [15:05:30 27-Feb-18 EST][weather] Redirect to https://www.weather.gov/xml/current_obs/KBIV.xml WARNING [15:05:30 27-Feb-18 EST] [weather] Updating current conditions failed for WeatherReport javax.baja.sys.BajaException: Unable to get NWS Current Conditions feed at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:71) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) ... 12 more java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Note: The issue does not occur in I/A Series N4 version 4.3 or higher. Resolution For I/A Series G3 version 3.8 and newer, patched weather.jar modules resolve this issue. The weather module patches are available for download from the Schneider Electric Exchange as:  weather 3.8.311.1 - G3 Firmware weather 3.8.213.3 - G3 Firmware weather 3.8.112.1 - G3 Firmware weather 3.8.41.3 - G3 Firmware    To resolve the issue in Niagara 4.2 and/or versions of G3 not covered by the patches, Clear the hidden flag on the conditionsServer slot of the weather provider and change the value to w1.weather.gov.  After making this change, the current conditions will update.  The conditionsServer slot for each weather report will need to be modified if more than one is being used.  The following is a screenshot of the provider slot sheet. The Conditions Server slot is highlighted. Select Config Flags.   Config Flags dialog. Uncheck the Hidden flag and save.   View the Property Sheet for the provider and modify the Conditions Server to be w1.weather.gov

Issue The Lonworks Trunk Connector Plug (Orange) for ENC's and UNC's, can they be purchased separately? Environment UNC-410 UNC-520 ENC-410 ENC-520 Cause Part Number description Resolution LON connector ( p/n E24-1555-2) is available though the iPortal. For other Standard Replacement Parts see the Installation Instruction sheet of the UNC or ENC model.

Issue Using the TAC I/A BACnet WorkPlace Balance Tool to balance a VAV, when requesting the box drive to Maximum flow, get error "Controller was temporarily busy. Please restart this balancing step” message. What does this mean and how to solve it? Environment BACnet  WorkPlace Flow Balance Tool MNB-V1 MNB-V2 Cause Multiple tools connected to the same VAV controller.  Resolution "Controller was temporarily busy. Please restart this balancing step” message means one of two things – One tool has control of the VAV while another is attempting to connect or the VAV is in the process of completing a balancing step while another balancing function is attempted. Flow balancing should be  accomplished with a single tool connected to a VAV controller.  

Issue Can an existing UNC-600 serve graphics for a new UNC-520, without adding an Enterprise Server? Environment I/A Series (Niagara) UNC-600 I/A Series (Niagara) UNC-520 Cause Application for serving graphics without adding Enterprise Server. Resolution Yes you can without adding a Enterprise Server. It is recommended that native Niagara objects in the UNC-600 be liked to data points in the UNC-520. This will optimize communication speed and database modifications if need. Remember to set-up the address book and select PEER to PEER. And to watch the resource count of the UNC-600

Issue USB-serial adapter recommended for use with DMS Operator interface (OPRIF)  version 11.6.  Environment DMS OPRIF 11.6, DMS-350A and DMS-3500 Cause Lack of serial port on PC. Resolution We recommend the IOGEAR model GU232A. (This is the same adapter we recommend for use with other devices, such as the MSC-LIM, MN-CIM and CBL-002 (DB-9S>DB-9S). NOTE: When using the converter with the MSC-LIM, launch the OPRIF from the LINKERGL.EXE in the DMS folder.

Issue How to select a platinum sensor compatible with the Analog Input (AI) object in WorkPlace Tech. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Sensor manufacturers provide platinum sensors with different Temperature Coefficient of Resistance (TCR). Resolution The Analog Input (AI) object supports 1Kohm platinum sensor with Temperature Coefficient of Resistance (TCR) equal to 0.00385 OHM/OHM @ °C. Check manufacturer's datasheet and select sensor with TCR of  0.00385 OHM/OHM @ °C

Issue Can I/A ENC-520 interface to a Honeywell Q7700 Network Interface for boiler/burner monitoring? Environment I/A Series G3 (Niagara) ENC-520 Cause Driver for Interface Resolution Tridium reports that there is no G3 driver to support an interface with this product.

Issue How to identify the DMS (MicroSmart) MSC-P1502 Enhanced from the non- Enhanced version. Environment DMS MicroSmart MSC-P1500 series Cause Controller version identification Resolution The MSC-P1502 controller came in two versions, non-Enhanced and Enhanced. The Enhanced version had the feature for AI 5 & 6 to be configured (jumpers J1 & J2) for a Voltage/mA input or resistance input.  Non-Enhanced version: Using OPRIF to communicate to the controller, the controller greeting screen would display PCB as the Controller Type. Visual identification would be that the circuit board has a label with the p/n MSCA-6160.  Enhanced version: : Using OPRIF to communicate to the controller, the controller greeting screen would display PCB as the Controller Type.  Visual identification would be that the circuit board has a label with the p/n MSCA-6161.  If there is no p/n label on the board, another way to identify an enhanced version is by looking at the circuit board. Above the inputs AI5 & AI6 there would be a white box with the wording ENHANCED AI.

Issue Is MNL-V2RV3-APP the actual controller hardware or is it an application for the actual physical controller? Environment I/A MicroNet LonMark series controllers. MNL-5RF3-APP, MNL-5RH3-APP, MNL-5RR3-APP, MNL-5RS3-APP, MNL-5RS4-APP MNL-10RF3-APP, MNL-10RH3-APP, MNL-10RR3-APP, MNL-10RS3-APP, MNL-10RS4-APP MNL-11-RF3-APP MNL-13-RF3-APP MNL-20RF3-APP, MNL-20RH3-APP, MNL-20RR3-APP, MNL-20RS3-APP, MNL-20RS4-APP MNL-V1RV3-APP, MNL-V2RV3-APP, MNL-V3RV3-APP Cause Part Number description Resolution The MNL-V2RV3 is the actual controller; the extension -APP is an option for factory to install customer's in-house engineered application. Contact Customer Service for details.

Issue DMS MicroSmart, Global point passing (broadcast) not working. Environment MSC-L1000 MSC- MPC-001 MSC-P-751, MSC-P-752, MSC-P-753, MSC-P-754 MSC-P-1501, MSC-P-1502, MSC-P-1503, MSC-P-1504 MSC-V-510, MSC-V-511, MSC-V-521, MSC-V-522 MSC-V-751, MSC-V-752, MSC-V-753, MSC-V-754 Cause The number of TXD and RXD broadcast channels are limited per controller type. Resolution The Level 11. controllers' MicroSmart Global Data Broadcasting capabilities are as follows: MSC-L1000: TXD and RXD on 1-122 channels MSC- MPC: TXD and RXD on 1-122 channels MSC-P-75x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-P-150x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-51x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-52x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-75x: TXD on 1-122 channels. RXD on 1-24 channels.  

Issue In WorkPlace Tech can a SNVT exist in a Custom Object? Environment I/A Series WorkPlace Tech 4.0 and higher. Cause Custom Object Rules Resolution Nearly all types of WP Tech shapes may be included on the Definition page of a Custom object, There are several exception and  "SNVT objects"  is one of them. This object must be on the top page of any control logic drawing instead. For  additional  exceptions see WorkPlace Tech Tool 4.0 Engineering Guide (F-27254-3), Chapter 3 "Custom Object Rules"

Issue When using DCT version 11.6, modifying the MSC-NCM schedule start-stop times do not save. The time reverts to the setting before the change was attempted. Environment MSC-NCM Cause Version 11.6 of DCT has an error in the compiled code. Resolution Instead of starting DCT from the desktop shortcut, launch it from the DCT folder (double-click DCTGL.EXE).

Issue Modify occupied cooling and heating (nciSetPts) variables on Viconics VT7652 LON stat, but changes are not transmitting to  thermostat. Have a DynamicCmd object linked up and can write the values in the DynamicCmd but they don’t ever change in the thermostat and they don’t show up in the nvoEffectSetPt variable. Environment VT7200 LonWork series VT7300 LonWork series VT7600 LonWork series Cause Setup of limits Resolution Check the HeatMaxSetpoint and CoolMinSetpoint limits found in the nciCfgRtuHP ( Vt76Pir properties). When a change that is outside of the limits, it will take the request but will not transmit change down to the thermostat.

Issue In WorkPlace Tech Tool, the Definition tab of a Custom Object, right click on any object to request Properties info. The response is an error "Exception happened finding Visio shape". What does this mean? Environment WorkPlace Tech Tool 5.7.x Cause There was an error in Visio. The custom object may have been copied from a newer version of Visio to an older version. There may have been an error when creating the custom object. Shapes may have been added to the custom object when opened directly in Visio instead of being opened in WPTech. Some other corruption to the drawing took place. Resolution Do a “Rebuild Application”, and then try opening the shape properties again.  If this does not work, try creating a new custom object, and then try copying the contents of the old custom object definition page into the new custom object definition page (while in WPTech).  Then delete the old custom object, and then try the shape properties in the newly created custom object.

Issue Unable to connect with DCT to log in MicroSmart MSC-NC Environment MSC-NC MSC-NCM MSC-DCT Cause Flash Memory got corrupted. Resolution Reloading Flash Memory on an MSC-NC (M) Power down; jump J1 (near processor); power up. Can DCT connect? If so, remove J1 jumper Do Alt-L to start Load Flash ROM installation If unable to connect with DCT, will need to consider replacing/repairing unit.

Issue Micronet BACnet (MNB) AV and BV objects in G3 are purple indicating they are overridden. The AV and BV objects are read only, how can they be overridden? Product Line TAC IA Series Environment Niagara G3 Micronet BACnet MNB-300 MNB-VAV MNB-1000 Cause Purple BACnet values (I/A Series R2 and G3 graphic override color) are internal BACnet points that can not be modified (display only). This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher. Per the BACnet specification, read-only type points must be set to indicate an override condition. The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification. The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device. In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services.In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user).When the ENC learns the device it reads what "Protocol Services" it supports. If it supports COV then the "use COV" flag is set to true in the device object and when the proxy points are brought in they are defined as COV and once subscribed they will send their present value and status flag values to the ENC. In this case the AVM & BVM (being read only) objects will show overridden along with their value and be purple by default. Resolution All MNB devices support COV so the use COV property is set to true when they are discovered in the ENC.If the use COV property of the Device object is changed to false the ENC will use readPropertyMultiple (if supported in the device) to poll for data. If readPropertyMultiple is not supported in the device the ENC will read one property at a time. Now when the points are learned they will be defined as polled and when polled only the present value (PV) is requested (by default). Hence the AVM & BVM objects will show their value but not show overridden because their status flags are not known at the ENC. If the use COV device property is set to true after the AVM and BVM proxy points are defined in the ENC they will show overridden and purple after they are successfully subscribed. Turning the use COV property in the device to false at this point will cause these objects to be polled but their status is already known so they will continue to show overridden along with their present value. The only way to change that is to delete and re-learn them while the device use COV property is sent to false.