Building Automation Knowledge Base

Issue The Alarm Priority does not display the correct value (110) in the Alarm View or Event View when the Alarm is in the "Alarm" state and displays 100 Value instead. It displays correctly in the Alarm view when the alarm state is "Acknowledged" or "Reset", and it displays correctly in the Event view when the alarm state is "Reset Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Incorrect configuration Resolution There is an"Alarm decorator override" that seems to override the priority for the alarm If in alarm state and priority is 110, then the priority is overridden to 100 as configured in the alarm decorator object Removing the override in the decoration will resolve this issue

Issue For various reasons it may sometimes be desirable to have the system display the raw bitstream of a card. Here is the configuration needed to accomplish it. Product Line Security Expert Environment Security Expert Controller Security Expert Server Cause Guidance is needed on how to make a Security Expert system display the actual raw bitstream of a Wiegand card. Resolution Configure the reader's format for Custom Credential Make sure the card presented at the reader will not result in valid access granted transaction, e.g. by temporarily removing that user's access to the door.  As seen in the image below, the system will display the format of the card (i.e. 37-Bit), followed by the actual Raw bitstream, for all invalid access transactions.   If the system is able to decode the card, it also appends the decoded info in parentheses right after the raw bitstream, which can also be very useful.

Issue The system will not execute an unlock latched command on a door if the door is in the middle of processing a Request to Exit (REX) transaction.  (Client/Server 4.3.308.52    Controller 2.08.1247) The entry on the Status page below, indicates the system processed the 'unlock latched' command, but left the door in its current state. This can be problematic when attempting to 'unlock latched' a busy high REX traffic door. Product Line Security Expert Environment Security Expert Controller Cause Firmware issue to be addressed in a future release. Resolution The workaround for this issue is to create a Programmable Function to perform the 'unlock latched' when the REX is not active.   1) Make a Virtual Output. 2) Set the Virtual Output's Activation Time to 1 second 3) Create a Programmable Function with the following settings:               Type:                              Door control             Door function mode:    2 - Follow pulse on output             Door control mode:      1 - Latch door unlock             Output to check:           The virtual output created in step 1)             Door to control:            The high REX traffic door you wish to 'unlock latched'   Note: Workaround works for native Security Expert door, do not work for INET transitioned door, a possible solution for INET transitioned door is to convert it to native Security Expert door.

Issue IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue Unable to determine why Users are being denied access at doors. Reviewing events shows that the Users are being denied access due to an Access Level that is not even configured to allow access to that door. User [UN1] Door not allowed [DR2] Using Access Level [AL1] Product Line EcoStruxure Security Expert Environment Security Expert Cause The user has no valid access levels for this door. Resolution The event showing like this is a side product of how access is validated. When a user badges at a reader, the card is first matched to a User record.  Each of that user's access levels is then checked, from top to bottom, until either one is found to have access to the door, or all are checked and none have access to the door. If a valid access level is found then that is the access level shown in the Granted entry/exit event. If the user has only one access level and it is not valid for this door, the event will appear to be correct as that will be the access level name shown in the Door not allowed event. If the user has multiple access levels and none of them allow access to the door then the Door not allowed event shows the name of the last access level checked, which in all cases is the one from the bottom of the user's list of access levels.

Issue Embedded WebStation client licenses were needed when logging directly into a SmartX server as of 3.0.1 but are no longer needed Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation SmartX Server Cause The license requirement is being removed due to market feedback. The quantity of direct web connections to the SmartX server is restricted by the Architectural Guidelines only. Resolution Important for version 4.0 (EBO 2022) and above:  Note that in Building Operation 2022 (v4.0.x) and above, WebStation licenses have now been enforced at the server level and are required.   If there is no embedded server license for example "XWSWXBU0000SD ASP Bundle - Standard" in the SpaceLogic server it will not be possible to login to the server using Webstation. The Webstation license is included in the embedded server license.   For version 3.0.x The change is available via a HotFix to version v3.0.3 and will be incorporated into Maintenance Release v3.0.4. In both the HotFix and the Maintenance Release, license status presentations in the Device Administrator and Control Panel will indicate the availability of 99 client licenses. However, the supported quantity of direct web connections to a single SmartX server is established by the Architectural Guidelines; currently, the maximum is five concurrent connections. In v3.1, the Device Administrator and Control Panel will not list client license availability at the SmartX server level since it is not constrained by licenses.  

Issue When connecting to several OPC servers, is it necessary to have several OPC Client licenses? Product Line TAC Vista Environment Vista OPC Server Cause In some cases, several counts of the same license module is required if several simultaneous sessions are in use. (Example: Workstation) Resolution You can connect to several OPC servers simultaneously while you just have (1) one OPC Client license.  

Issue A message saying "no license available" or starting the license finder popup.  Sometimes Flex license system needs a little extra time to load the licenses. Product Line TAC Vista Environment FLEXnet Licensing Cause The problem is in the Flex license system and not in TAC Vista, the same issue occurs on other Software vendors using the same license system. Resolution Make sure that you are logged in as an admin on the computer. Right-click on This PC > Properties > Advanced system settings Click the button in the lower-left corner labeled "Environment variables" Add a new system variable named FLEXLM_TIMEOUT Give it the value 3000000, press OK Restart TAC Vista Server and Workstation, the Flex license system will now have 3 more seconds before throwing out a message saying "no license available" or starting the license finder popup.

Issue NRE default configuration and RAM disk removal Product Line TAC IA Series Environment I/A Series N4.11 Jace 8000 Cause In Niagara 4.10u1 and earlier, the RAM disk was used to temporarily store alarm and history data. During station save, this data was copied from the RAM disk and zipped up, and stored on Flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the Flash. Resolution A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. JACE-8000 NRE Memory Default for (older) Niagara 4.10 - sizes in MB: System Reserve Size:          0 Heap Space Size:              360 Meta Space Size:              56 Code Cache Size:              16 RAM Disk Size:                384 Free Memory:                  ~16 JACE-8000 NRE Memory Default for (newer) Niagara 4.11 - sizes in MB: System Reserve Size:          0 Heap Space Size:              384 Meta Space Size:              64 Code Cache Size:              32 RAM Disk Size:                Not present (cannot be created) Free Memory:                  ~352   These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000.

Issue Tridium N4.11 Upgrade Considerations  Product Line TAC IA Series Environment I/A Series N4.11 Enterprise Server I/A Series N4.11 Jace 8000 Cause Detailed information about N4.11 upgrade prerequisites and best practices  Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.11. Please review prior to upgrading to Niagara 4.11. Niagara 4.11 and Default NRE Memory Changes: A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000. Prior to upgrading your JACE-8000, please review NRE default configuration changes and RAM disk removal In 4.11. Niagara 4.11 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.11, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised, or derived from untrustworthy sources. Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules. Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.11, unsigned modules will not execute. For more information, please review the Niagara documentation on Third-Party Module Signing Niagara 4.11 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide. Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.11.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Ubuntu Linux 20.04 LTS – Desktop & Server Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10) As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward. Using Web Launcher with Niagara 4.11 Web Launcher 21.4.1 was recently revamped for Niagara 4.11 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 311 and certificate management has been updated to work with Niagara 4.11 along with any legacy or prospective release. Prior to using Web Launcher with Niagara 4.11, customers should update Web Launcher accordingly (see steps below). How to update Web Launcher? Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version. Niagara 4.11 Release Notes: The release notes for Niagara 4.11 are located here.

Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue It is not possible to change Primary or Secondary Reader Formats as they are greyed out. Product Line EcoStruxure Security Expert Environment Security Expert Client, Security Expert Server Cause When the Reader Expander Port network type is set to Schneider Electric RS485 the Reader format is edit locked and unable to be changed. Resolution The Port network type on the Reader Expanders General tab needs to be temporarily changed to Wiegand.  Under the Reader tab the Reader Format and Reader Secondary Format can now be changed. Repeat this process for Reader 1 and/or Reader 2 as required. On the Reader Expanders General tab change the Port network type back to Schneider Electric RS485. Save your changes, perform a download and update the Reader Expander.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Proper configuration of supervised inputs, Mercury IO modules (i.e MR52) versus Continuum IO modules (AC1/AC1Plus) for transitioned Continuum sites. Product Line EcoStruxure Access Expert Environment Access Expert Controller Access Expert Reader Interface Access Expert Premise Software Access Expert Hosted Software Continuum AC-1 IO Module Cause Guidance is needed on the proper configuration of Access Expert custom EOL resistor tables in order to achieve full supervision of inputs associated with readers/doors. Full supervision in this context means not only being able to detect normal input operation (activation/deactivation) but also detection of attempts to tamper with the input's circuit (short circuit, open circuit, grounding, the introduction of foreign voltages, etc.) Please note that not all resistor configurations can detect all the various circuit issues, for example, a NO Series resistor configuration can't detect a cut in the wire given that the open circuit is the normal state for the Deactivated value of the input. The resistor configuration that provides the most supervision is the Series/Parallel configuration, using 2 resistors is possible to detect both short and open circuits. Resolution Continuum supported a fixed 10K Ohms resistance for supervised inputs, furthermore, Continuum IO modules (AC1/AC1Plus) transitioned to Access Expert under an AX-SSC controller continue to operate with Continuum firmware, this means that they do not support the custom EOL tables in Access Expert, the only configuration that is possible for AC1/AC1Plus modules is the mode of connection of the resistor (parallel, series or both).   Also, when using 2 resistor configuration, the placement of the resistor is different in Continuum compared to Mercury hardware   CONTINUUM When the switch is open only the resistor on the left is seen by the input. When the switch is closed, the two resistors are presented to the input in parallel with each other resulting in the input reading half the sum of the total resistance value.   SECURITY EXPERT       When the switch is open, the two resistors will be presented to the input in series with each other resulting in the input reading the sum of the two resistors value.  When the switch is closed only one resistor is presented to the input   For the above reasons, Continuum transitions sites where the AC1/AC1Plus has been replaced with Mercury hardware like the MR52 for example, need to configure one or more custom EOL table(s) for 10K resistors.   *** The sample tables provided below contain resistance values calculated to take into account wide variations in total supervised loop resistance due to wire distance, gauge etc., supervised loops should be installed in accordance to distance and gauge guidelines for wires as well as recommended resistor tolerance. It may be necessary to make adjustments to the resistance values in the tables on a site by site basis.   See below sample tables for all six possible 10K resistor configurations   Normally Open Parallel (10K-NO-P) Normally Closed Parallel (10K-NC-P) Normally Open Series (10K-NO-S) Normally Closed Series (10K-NC-S) Normally Open Series/Parallel (10K-NO-SP) Normally Closed Series/Parallel (10K-NC-SP)+ 1. Normally Open Parallel (10K-NO-P) 2. Normally Closed Parallel (10K-NC-P) 3. Normally Open Series (10K-NO-S) 4. Normally Closed Series (10K-NC-S) 5. Normally Open Series/Parallel (10K-NO-SP) 6. Normally Closed Series/Parallel (10K-NC-SP)+

Issue Getting "Commport is not XDriver enable" error when attaching the driver file to the comm port. Comm port has been flashed to enable XDriver operation. Controller Options shows Xdvr Comm2:00000009 (0000) Product Line Andover Continuum Environment BCX NCI NCII B4920 XDriver Comm Port Cause Bad controller XDriver support flash file. Resolution 1. Take the Workstation offline, edit the comm port, and set the default mode to "XDriver". 2. Go back online and send the comm port to the Controller. 3. Attempt to attach the Driver file to the comm port, if the same error occurs then contact Schneider repair department for a new XDriver option flash file. See article Determine if a controller comm port is XDriver enabled - Communities (se.com) 

Issue WorkPlace Tech Tool reports Database Error when attempting to link to the output of a copied custom object. The displayed error message shows the name and attribute of the object being connected along with the error "Exception error occurred during WriteProperty [0xE0330020]". Product Line TAC IA Series Environment WorkPlace Tech Tool Software Version 5.7.x or newer Workplace Tech application file containing a custom object copied from another WPT application. Cause Unknown, believed to be an internal Visio error. Resolution Open the application file in the WorkPlace Tech Tool software and select the page for the Custom Object that is reporting the error. Break the connection (disconnect the link) between the Custom Object output tag and the corresponding source object. When breaking the link, it is suggested that the wire link be dropped onto the drawing page before being re-linked. Select the link and reconnect it to the proper object. It may be necessary to perform this unlink and relink operation for all output tags within the Custom Object that had been copied from another WPT application file.

Issue The following Popup window is displayed when attempting to open WorkPlace Tech. WPTech Unable to load WorkPlace Tech Ribbon for Visio. There was a problem loading the WorkPlace Tech Fluent Ribbon for Visio, therefore, it will be unavailable. Product Line TAC IA Series Environment Visio 2010, 2013, 2016, and 2019 WorkPlace Tech Tool release 5.8 or later Cause If Visio crashes when a third-party ribbon bar function is in use, Visio may lockout that ribbon bar, believing that something on that ribbon bar caused Visio to crash.  In this case, a menu function, selected from the WorkPlace Tech (WPT) ribbon bar was being processed at the time Visio crashed, therefore Visio locked out the WorkPlace Tech ribbon bar. This is a system protection mechanism built into the ribbon bar handler in all Microsoft Office applications including Visio.   Resolution To re-enable the WorkPlace Tech ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech. Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'WorkPlaceTech.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech ribbon bar will be available in WorkPlace Tech.  

Issue After editing an MNL-800 application with the WorkPlace Tech Tool Editor, an error is displayed indicating that the application file could not be saved. Product Line EcoStruxure Building Operation Environment Building Operation Workstation >1.4 Building Operation WorkPlace Tech Editor Cause The name of a LON Network Variable (nvi or nvo SNVT) or a LON controller configuration constant (nci SNVT) contains a space. Echelon standards do not allow spaces in network variables or configuration constant names. Resolution Edit the application file removing any spaces or other non-supported characters from network variable and configuration constant names. More information is contained in the SBO WebHelp topic "WorkPlace Tech Editor"

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue Detailing configuration and starting DWiz on a computer running EcoStruxure for Buildings Operation. Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Xenta 281 Xenta 301 Xenta 401 Cause DWiz (Download Wizard) was a part of the TAC Vista installation, but not so commonly used in EcoStruxure Buildings Operation, and therefore no longer included in the Start menu. It is however still installed and could be started from Windows File Explorer. Resolution   Verify the Com port used. If your computer does have a serial port, this is normally Com1 or Com2. If you are using a USB to RS232 adapter (like Aten), you could get a much higher number. The program requires a port number between 1 and 9. You may need to change the port number. This could be done via Windows Device Manager. In Windows File Manager, go to the directory where EcoStruxure Buildings Operation Workstation is installed. Here you will find DWiz.exe as well as MentaSetup.exe. Start MentaSetup.exe, adjust Com Port, select Apply and Close. MentaSetup        5.  Now it should be possible to start DWiz.exe located in the same directory.