Building Automation Knowledge Base

Issue This issue is described in Tridium's internal case NCCB-71360. Users will notice that the default Nrio Device Manager view (Ux/web media) of the NrioNetwork driver in N4.14 looks identical to the previously existing workbench AX view; however, due to this defect, devices discovered and added through the web view will not function as expected.  Product Line TAC IA Series Environment I/A Series N4 Jace 9000 I/A Series N4.14 Framework Version Cause With the release of the Jace 9000, users may notice that the IO-R-16 and IO-R-34 devices will not function properly when discovery and configuration are performed through the web views. Resolution To tell if the device was added through the correct view, there are a few indicators. Malfunctioning devices will not show up with an Installed Version or a Sec version in either view: Working devices will display these values with no issue in either view: The malfunctioning devices' health section will read 'fail' even with a status of ok: Users in N4.14 should only use the Workbench AX Nrio Device Manager view to discover and add devices to a station. This use case is currently not supported in the browser for N4.14. All other use cases function in the UX Web Views, such as viewing devices, adding points, and commanding points.  

Issue Removal of the Mobile Profile in N4.15 Product Line TAC IA Series. Environment I/A Series N4.15 Jace I/A Series N4.15 Enterprise Server Cause The Niagara Mobile Profile has been removed from Niagara 4.15 Resolution Since the Niagara Mobile APIs were deprecated and replacements provided in N4.6,  Niagara Mobile has been removed in N4.15. The standard HTML5 Hx Profile is mobile friendly and users configured with the BDefaultMobileWebProfile will automatically be switched to the HTML5 Hx Profile. When you start up a N4.14 station in a N4.15 environment for the first time and it was configured for using the mobile profile, you should see this warning:   "WARNING [14:06:11 22-May-24 EDT] [web] Support for the "Default Mobile Web Profile" has been removed. Users with this profile have been switched to the "Html5 Hx Profile".

Issue Jace 8000 versus Jace 9000 WiFi specifications Product Line TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Jace 9000 Cause Defining WiFi feature differences Resolution The JACE 9000 includes a WiFi 5 radio supporting Bluetooth 5.2LE that is currently disabled.   Below is a table of the differences between the JACE 8000 and JACE 9000 WiFi:   Feature JACE 8000 WiFi JACE 9000 WiFi WiFi Standard WiFi 4 (802.11n) WiFi 5 (802.11ac) Switch Type Hardware Switch Software Switch Modes Off, Access Point (WAP), or Client Off, Access Point (WAP), or Client Security WPAPSK / WPA2PSK supported WPAPSK / WPA2PSK supported Bluetooth Not Supported Yet Bluetooth 5.2 LE WiFi Disabled at Factory Depending on SKU Depending on SKU   SKU Details: JACE 8000: JACE-8000-CSE-001 US JACE-8000-CSE-002 WW JACE-8000-CSE-003 NON WIFI JACE-8000-CSE-004 China JACE 9000: JACE-9000-CSE-001 US, CA JACE-9000-CSE-002 WW JACE-9000-CSE-003 NON WiFi JACE-9000-CSE-004 China JACE-9000-CSE-005 EU The JACE 9000 includes a button behind the door that can be configured as "Access Point Controlled" mode, enabling the use of an inactivity time limit for access point availability.  Selecting this mode activates a configurable time limit property for inactivity and the use of the Wi-Fi button to toggle on or off the Access Point availability.   This is similar to the hardware switch of the JACE 8000.    Figures Figure 1 shows the front panel of the New JACE 9000 WiFi Figure 1.1 shows the JACE 8000 hardware switch indication Figure 1.2 shows the JACE 9000 software switch indication  Figure 1 - Front of JACE 9000 panel – WiFi LED and button location   Figure 1.1 - JACE 8000 hardware switch indication   Figure 1.2 - JACE 9000 software switch indication   NOTE: WiFi will not be supported in Jace 8000 with N4.15 release. Blackberry QNX chipset support has been dropped in the Jace 8000. Details and Summary 

Issue JACE 8000 WiFi radio Product Line  TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4.15 Software Cause Niagara Framework, Niagara 4.15, includes an update to the QNX operating system that no longer supports the WiFi chipset in the JACE 8000. Resolution Customers who have deployed JACE 8000 devices with the WiFi connectivity option will not be able to activate or configure the WiFi radio under Niagara 4.15.  Blackberry QNX has dropped support for the WiFi chipset used in the JACE 8000. This change was effective with the latest release of its QNX 7.1 Software Development Platform (SDP) in November of 2024. Niagara 4.15 includes this QNX 7.1 SDP update and will install based on the current setting of the JACE 8000 WiFi radio.   What should the Jace 8000 WiFi customer expect When upgrading a JACE 8000-WiFi unit to Niagara 4.15, switch the WiFi radio to the DISABLED setting before attempting to install. In this configuration, 4.15 will install normally. Note that after commissioning, you will no longer see the WiFi Configuration option on the platform menu, and you will not be able to connect via WiFi. Also, note that Niagara 4.15 will not install if the WiFi radio is set to ENABLED.     What to do in situations where WiFi connectivity is needed A factory reset will restore Niagara 4.9, and the JACE will regain its WiFi functionality. You can then commission the JACE 8000-WiFi unit with Niagara 4.14.

Issue Define I/A Series AX/G3/N4 software compatible with a specific version of Windows Product Line TAC IA Series Environment I/A Series (Niagara) AX/G3/N4 software Windows 32-bit and 64-bit operating systems Cause Only specific releases of the I/A Series AX/G3/N4 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series G3/N4 software and various versions of the Microsoft Windows Operating System software.   Refer to Supported Operating Systems for Niagara 3.7 and earlier (June 2016) Refer to Supported Operating Systems for Niagara 3.8 (July 2020) Refer to Supported Operating Systems for Niagara 4.1, 4.2, and 4.3 (September 2019) Refer to  Supported Operating Systems for Niagara 4.4 and higher (March 2025)   For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Bog File Encryption Changes in 4.15 Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 9000  Cause In Niagara 4.15, to continue to provide the best security practices, the user password hashes are now included in the encryption by the system passphrase. Resolution The system passphrase was introduced in Niagara 4 to provide additional protection to sensitive data from the Niagara system. Prior to Niagara 4.15, this included all reservable passwords (such as Niagara Network, database connection passwords, etc.), excluding the user's passwords as those are protected by being hashed. If you do not have the system passphrase for a station and need to unlock it through Workbench, both the user and encrypted data such as passwords will be removed where prior to Niagara 4.15 the user were left untouched as they are hashed. If you are copying a station from a remote host which you do not have the system passphrase for, you will need to reset the passphrase to successfully copy the station onto a new remote host. You will be required to enter the passphrase to edit or modify users or encrypted properties such as password fields for email, Niagara Network, etc. Prior to Niagara 4.15, you could edit and modify users without the passphrase, in Niagara 4.15 this will require the passphrase to decrypt the users.   Operation Niagara 4.14 Niagara 4.15 Modifying users in offline station bog file Users can be modified without entering the station bog file passphrase Station bog file passphrase is required to modify users Reset station bog file passphrase Removes reversable client passwords such as email, Niagara Network, etc. Hashed user passwords are not impacted Removes both reversable client passwords and hashed user passwords Understanding the System Passphrase in 4.15 Workbench or Supervisor When Niagara is installed on the engineering or supervisor device for the first time, the user will set the passphrase for that device. NOTE: When setting system passphrases, make sure that you take note of what they are. These should be shared with the owner of the building/site as the passphrase is owned by the device. You can change the system passphrase in the Platform Administration screen. You will be required to enter the current passphrase in order to successfully change it to a new passphrase, highlighting the importance of providing it to the owner of the building/site. JACEs & Remote Niagara Devices The passphrase is set during the commissioning process of the remote device. The remote device's passphrase can also be changed through the Platform Administration view with the same requirements as changing the Supervisor/device's passphrase.   Station Bog File Passphrases In 4.15, you will have the option to encrypt the new station with either the local system passphrase or a custom passphrase in the New Station Wizard. This passphrase is required to unlock the bog file in the user home when configuring encrypted properties as well as when copying this station onto a remote host. New Station Wizard: Note: When selecting the "Use the system passphrase" option, this is the passphrase for the local host (Workbench) Unlocking the station in the User Home: Copying the Station to a remote host with a different passphrase: Understanding how the station passphrase changes when using the Station Copier When a station from a remote host to your local host, the passphrase which is encrypting the data will be the system passphrase of the remote host. Copying a station from your local host to a remote host: For a station that originated on your local host with a passphrase encrypting its sensitive data, once you enter the current station bog file passphrase and successfully copy the station onto the remote device, it will utilize the system passphrase of the remote device when copying from the remote device back to your local host. Copying a station from a remote host to your local host: When a station is copied from the remote host, it will automatically be encrypted with the system passphrase of that remote host.   What do I do if I do not know the system passphrase of the remote host I copied the station from? In the user home,  you are able to reset the passphrase of the station, however, you will lose the encrypted sensitive data including system and user passwords. In this workflow, you have the option to remove all users except for one new super user which you provide the new username and password in the Bog File Passphrase dialog:  

Issue Extended Jace 9000 Commissioning Time. Product Line TAC IA Series Environment I/A Series Jace 9000 Cause With the release of the Jace 9000 using Ubuntu Core 20 Linux as it’s operating system the commissioning/upgrade times increase as compared to the previous Jace 8000. Initial commissioning times can take longer then 15 minutes to finish. There are scenarios where multiple reboots are needed after the initial commissioning is completed. Once the commissioning has been completed for the Jace 9000, boot times should be significantly lower. Resolution Users will need to reboot their Jace at least twice and will need to set more time aside for commissioning of the new Jace 9000s. Please allow for a minimum of 15 minutes for commissioning. If you continue to experience issues with bootup or commissioning on the Jace 9000,  please contact your country level product support. Please note that the JACE-9000 does not print a lot of output on the debug port when you cycle power so give it time to fully bootup.

Issue Incorrect Default Gateway setting may prevent communication with the JACE-9000 Product Line TAC IA Series Environment I/A Series Jace 8000/9000 Cause The Jace8000 and Jace9000 both have primary and secondary LAN adapters. Previously, Workbench prevented users from some invalid IP configurations, but current versions of Workbench, when connecting to a 9000 will allow invalid configuration in the default gateway. Resolution In the 9000, a user can set different default gateways for the Primary (en0) and Secondary (en1) ports. This should not be allowed on a single network device, and leads to unpredictable behavior when routing. Compare the location of the IPv4 Default Gateway in the TCP/IP Configuration of the Platform on a 9000:      And the same page as seen in the 8000: In future versions, this will be changed, but users should avoid invalid configurations in the affected versions. When configuring both LAN ports for use on a 9000, only enter a value for the default gateway field in one adapter. Leave the other intentionally blank. It does not matter which is given a default gateway and which is left blank. Note: Sometimes, when an Adapter has the Default Gateway, you cannot connect to the other Adapter (despite correctly being on that Adapter's local subnet). These symptoms can be triggered by the Ethernet "link" (active connection) toggling up or down.  The link state can change whenever: the JACE is rebooted or power-cycled; and/or the Ethernet switch ("hub")  is rebooted or power-cycled; and/or the Ethernet cable(s) are un- or re-plugged (at either end). In some cases, the symptoms can alleviated by toggling the Ethernet link state, in the ways listed above.

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you change RSTP settings, the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured correctly per Configuring RSTP on a Managed Switch for SmartX IP Controllers. If asked to review this for a case, please provide PSS screenshots from the switch configuration page(s).  Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Frontline Fridays Episode 02 - Rapid Spanning Tree Protocol (RSTP) Date: 2022-11-11 Mike Botens posted the following in the thread: RSTP Status TGML dated 2022-11-09 PDF of the presentation Fusion Fridays - Session 07 ​​​​ Date: 2020-05-28 The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Offline controllers that are scattered are NOT an RSTP issue. Check to see if there is a possible DHCP issue by verifying controllers are still at their AUTO-IP address (IP 169.254.nnn.nnnn Subnet Mask 255.255.0.0). RSTP communications issues affect the entire RSTP loop or one contiguous group of controllers. Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, Warm Start, re-enable RSTP Mode, Warm Start, and check again. If Firmware 3.02.01 is installed, please upgrade to 3.02.02. SmartX is now SpaceLogic. KNOWN ISSUES with Firmware affecting RSTP: RSTP not performing as expected with Static IP addressing - Schneider Electric Community

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue EcoStruxure Building Operation WorkPlace Tech Editor Supported Microsoft Visio Versions The following error context is encountered when trying to run WorkPlace Tech Editor to edit a program: WorkPlace Tech Editor returned errorClass not registered 0x80040154 REGDB_E_CLASSNOTREG Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation WorkPlace Tech Editor I/A Series MNL, MNB Controllers (MNB - from SBO v1.8.1 and newer) Cause Only the 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. The error is seen when a 64-bit version of Microsoft Visio 2010 is installed. Resolution Currently, only 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. SBO 1.5, 1.6, 1.7 Microsoft Office Visio 2010 SP1, 2007 SP2, 2003 SBO 1.8 Microsoft Office Visio 2010 SP1 (32-bit), 2007 SP2, 2003 SBO 1.9, EBO 2.x, 3.x Microsoft Office Visio 2016 (32-bit), 2013 (32-bit), 2010 SP1 (32-bit) EBO 2022 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2023 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2024 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit)

Issue Can Cyberstation setup and configure 3rd party BACnet devices. Product Line TAC IA Series, Andover Continuum Environment Cyberstation BACnet I/A Series MNB-1000 Cause It is desirable to configure all products from the same software. Resolution Cyberstation and the BACnet protocol do not allow you to do basic setup and configuration of 3rd party devices, most products will have their own configuration software or local display/ keypads for setup. The I/A MNB-1000 BACnet controllers will require I/A Series Software to setup and configure the controllers, this can not be done through Cyberstation. Once setup and communicating Cyberstation will be able to make changes / adjustments depending upon the PIC's statement of the device.

Issue Not able access a new MNB-1000 via its default IP address. It will not respond to when pinged. Product Line TAC IA Series Environment WorkPlace Tech all versions, WPT Version 1.50E and later Cause The ability to ping the MNB-1000 controller was removed starting in Firmware version 1.50E. All MNB-1000s are shipped with IP port disabled. Resolution Starting with firmware revision 1.50E, the ability to ping a MNB-1000 controller was removed; so any MNB-1000 controller at or above firmware Revision 1.50E will not respond to a ping. Reference Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E or higher for further details. All new MNB-1000 controllers are shipped from the factory with their IP and MS/TP ports disabled. The Ethernet port is the only port enabled. The MNB-1000 controller must first be accessed via its Ethernet port. Once gaining access, its BACnet/IP port can then be enabled.  Note: Both BACnet/Ethernet and BACnet/IP ports should not be enabled at the same time. So if BACnet/IP is being used and once the BACnet/IP port is configured and enabled, then disable the Ethernet port. NOTE:  Firmware 1.537 made the MNB-1000 visible via the ping command again.

Issue Can a MNB-1000 be configured to get an IP address via DHCP? Product Line TAC IA Series Environment MNB-1000 Cause End user does not want to use fixed IP addresses on their network. Resolution The MNB-1000 does not support the use of DHCP for setting the IP address.

Issue How can the MNB-1000 be set back to factory defaults? Product Line TAC IA Series Environment I/A Series MNB-1000 Cause Reconfigure the MNB-1000 Resolution Do the following: Set all of the dip switches on the MNB-1000 to the ON position (all ones)  and cycle power.  Wait until the controller completely boots up (solid green status light), then change dip switches from all ones back to the desired address. Cycle power again. Note - Setting the MNB-1000 back to factory defaults will delete the installed application.

Issue In WorkPlace Tech 5.7.2, some selections in the menu bar at the top of the screen are missing (i.e Project and Application selections) Product Line TAC IA Series Environment WorkPlace Tech 5.7.2 Cause Disable COM add-ins on the Security tab. Resolution Click on "Tools" in the menu bar Click on "Visio Options." The Options screen appears. Click on the Security tab and un-check "Enable COM add-ins".

Issue After converting from .vsd to .vsdx Workplace Tech application, monitor tags sometimes do not work. Product Line TAC IA Series Environment Workplace Tech  Cause The application must be closed and reopened. A new monitor tag from the stencil needs to be added to the drawing Resolution Add the application to a project Monitor the application. If the monitor tags do not function, close the application and re-open it. If the drawing has been converted from .vsd to ,vsdx, add a new monitor tag from the stencil and try the monitor operation again.

Issue After uploading a Workplace Tech application from an MNL controller, Workplace Tech attempted to generate the application drawing, but aborted with an error message. Product Line TAC IA Series Environment Workplace Tech Cause The issue is related to the drawing information portion of the hex file. One or more object names, entered by the user, are longer than 31 characters in length. Although the WorkPlace Tech Tool 4.0 Engineering Guide states that long object names (over 32 characters) are permitted, it seems that 31 characters is the limit with all MNL controllers. Resolution When performing the above task with Workplace Tech 4.0.4 (running on Visio 2002 sp2), the error message is: "Error code -2032465748 Code meaning: Unknown error 0x86db98acs". When performing the above task with Workplace Tech 5.6 (running on Visio 2003 sp2), the error message is: "An unknown error was encountered while the application was generating the drawing." Workplace Tech 5.7.2 works around the naming error by truncating the first long-named object to 31 characters followed by naming the remaining objects as obj1, obj2, etc. It completes the conversion without error. Use Workplace Tech 5.7.2 to generate the application and compile it. Then take the complied hex file and use it with Workplace Tech 4.0.4 to generate an application drawing.

Issue At the completion of the download of a WorkPlace Tech application into an LON controller, the following error window is displayed: Product Line TAC IA Series Environment WorkPlace Tech Tool release 5.x.x I/A Series MNL Controller application file Cause A default nci constant is out of range for its variable type. Resolution Verify that all nci values are valid for the SNVT type, re-compile and re-download the application. The most frequent issue that causes this error is an invalid text string value for a nciLocation SNVT.

Issue Does the part number, ENS-MOD license the Enterprise Network Server for both Modbus TCP master and slave functions? Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server Cause The Enterprise Network Server needs to function as a Modbus master or slave device.  ENS-MOD only licenses the Enterprise Network Server to function as a Modbus master device. It does not license it to operate as a Modbus slave device. Resolution ENS-MOD only licenses the Enterprise Network Server to function as a Modbus TCP master (client) device. As of 2013, the ENS can also be licensed as a Modbus TCP Server (slave) using the part number ENS-MOD-SL.