Issue How to add Basic Authentication header to SendWebRequest function in Script RESTful Web Services Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause A 3rd party web service requires basic authentication for HTTP requests to ensure that data is requested securely, otherwise, the request will be rejected with an "Authorization Error".   Resolution Basic Authentication is a type of Authorization Request Headers, which transmits credentials as user-id/ password pairs, encoded using Base64, as defined in RFC 7617 - The 'Basic' HTTP Authentication Scheme (ietf.org).  Follow the below steps to create a Basic Authentication header in Script RESTful Web Services: Combine the User ID and the Password with a colon ex. "aladdin:opensesame". Encode the resulting string in base64 using script function to base64 encode a string posted in the Community or using the online encoder as Base64 Encode and Decode - Online, ex.  "aladdin:opensesame" will be "YWxhZGRpbjpvcGVuc2VzYW1l" after Base64 encoding. Construct SendWebRequest header in the following format:  Authorization: Basic <credentials>, as below example:  Headers= "Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l"'User ID=alaadin Password=opensesame Resultstring= SendWebRequest(BaseUrl,Method,ContentType,Headers,Message) Note: Basic Authentication is not a secure method of user authentication unless used in conjunction with HTTPS/TLS, as the user ID and password are transmitted as clear text. User ID and Password are Base64 encoded but Base64 can be easily decoded.  For more information refer to Script RESTful Web Services WebHelp and Authorization - HTTP | MDN (mozilla.org)

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

Issue TAC EM 5 Actuator requires replacement. Product Line Field Devices Environment EM 5 EM5C EM5 Actuator Cause TAC EM 5 Actuator requires replacement Resolution The TAC EM5 Actuator is totally obsolete and no direct replacement is currently available. Details of the TAC EM5 Actuator can be found in EM5 OBSOLETE.tmp.pdf. The TAC EM5 Actuator was capable of use in control systems having alternative electrical wiring connections.   Alternative 1 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA DC positioning signal. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. Details of the S-E MD10A-24 Actuator may be viewed in MD10A S-E.pdf. N.B. The S-E MD10A-24 should be checked for electrical compatibility with other control system devices that it is to be integrated with. It is unlikely that it will be mechanically compatible with the other control system devices such as the Control Valve Body. Arrangements may therefore need to be made for the design and manufacture of a suitable Linkage Kit.   Alternative 2 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA positioning signal with 16 Vdc output. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. It should be noted however that no 16 Vdc output is available from the S-E MD10A-24 and none can be connected. A 16 Vdc power supply should therefore be installed to provide power to any external Controllers or Auxiliary Units.

Issue For EBO Active Directory (Windows Domain) integration, do EBO support usage of "nested groups"?. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause EBO are using Windows API and ask if the user is a member of a certain group.  Resolution Windows API should respond “yes” if the user is part of a group that is part of another group, which is configured in EBO. So this is up to how the Windows AD responds to the Windows API and not on the EBO side.   For more information, please see Integrating Windows Active Directory user accounts with EcoStruxure

Issue ISO 9001 certificate for Schneider Electric Buildings Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices,Other, TAC INET, TAC Vista Environment Management Certification Certificate for the Design and Manufacture of Building Management System Controllers, Devices and Electronic Systems Cause ISO9001 certificates are sometimes requested for different projects. Resolution Download the ISO 9001:2015 certificate here.

Issue How can EcoStruxure BMS server serve data to external devices or software? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Third party devices or software Cause The EcoStruxure Building Operation software supports the major communication protocols in building automation and security management. In many projects, it is required that an EcoStruxure BMS server serve data to external devices or software, E.X. HMI, SCADA or power monitoring. Resolution The following is a summary of the available options to serve EcoStruxure BMS server data to the external world: BACnet:  When you create a BACnet Interface, the system automatically creates the Application and IP network folders within the BACnet Interface folder on the System Tree. If you create a BACnet Interface for a SmartX server, you can optionally create an MS/TP network. You can create BACnet objects in BACnet application folder of EcoStruxure BMS servers and these object will be visible for external BACnet clients. More information about EBO BACnet interface: BACnet Interface   Modbus Slave network:  If you configure the Modbus Slave Network (and associate it with a serial port), you can set up any external Modbus master device to communicate with the internal Modbus Interface. In this example, a Modbus Slave Network is set up on an EcoStruxure BMS Server and the external master device is configured with the same Modbus properties as the Modbus Slave Network object. The Modbus master device can also be an HMI device. More information about Modbus serial interface: Modbus Serial Networks Modbus server network: You can create a Modbus TCP Network on an Ethernet network (TCP/IP).  You can create an internal interface which acts as the server to an external client/clients. More information about Modbus TCP interface: Client and Server Networks   MQTT: MQTT is a lightweight and flexible data transfer protocol for IoT resources. EcoStruxure Building Operation, V3.2 or higher, can be configured to send data to an MQTT broker on interval or event-driven. The below are the tested brokers: Microsoft Azure IoT Hub Amazon IoT Core IBM Watson IoT Mosquitto More information about MQTT interface: MQTT Overview LonWorks Interface: EcoStruxure BMS servers can have a local node on their networks that can act as a LonWorks node. In the local node, you can create your own NVs that can be bound to external LonWorks devices using LonWorks bindings. The NVs in your local node can then be used in EcoStruxure Building Operation bindings for applications and graphics. More information about LonWorks interface: LonWorks Engineering   SNMP: Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. The EcoStruxure BMS servers support SNMP version 3. The SmartX servers support several SNMP traps. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. More information about SNMP: SNMP EcoStruxure Web Service (EWS) server: EcoStruxure Web Services allows seamless sharing of operational data, including alarms and historical information, between software from different Schneider Electric Business Units. When the EcoStruxure BMS server is an EcoStruxure Web Service server, it exposes objects, such as values, to another EcoStruxure system that is an EcoStruxure Web Service client. The EcoStruxure Web Service client can read and change values on the EcoStruxure BMS depending on the configuration of the EcoStruxure BMS server. More information about EBO EWS Server: EcoStruxure Web Service Server Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions which extend and enhance EcoStruxure Building solutions. Ex. SmartConnector can be used to serve EBO data in a RESTful manner, refer to: Configure SmartConnector RESTful EWS Gateway to serve EBO data   For further information watch the Smart Connector explainer video or visit the Smart Connector Developer Community on the Exchange: For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com Smart Connector at Exchange:  EcoStruxure Building Operations SmartConnector 

Issue Includes PSI Error Messages and Device Error Messages Environment PSI Microzone II Network 8000 Cause Quick reference Resolution The error codes are listed in the PSI MicroZone II Operator's Manual.  The full document is available here:  F-23058. Just the error codes are available here:  Pages 59-61.

Issue Active sensors that have a 0-10V output can not be directly connected to a controller with a 0-5V input, what resistors and settings are required? Product Line Andover Continuum Environment All i2 and b3 controllers with 5V inputs, not applicable to the controllers with a 10V input i.e. the i2/b3920 & 810 which directly support the 0-10V sensors I/O Module UI8-10 XP Modules xPUI4, xPBD4, xPBA4.   Cause There is a requirement to calculate the appropriate potential divider resistor values and the settings for the upper and lower voltage in the input point configuration Resolution Download the Voltage Inputs LSM document, this document details the value of the 2 resistors to use in the circuit and the upper and lower voltage settings to enter in the Auto Conversion box in the input point, these will correspond to the sensor reading at 0V & 10V. For controllers that allow the pull up resistor to be switched out, ensure that it is in circuit for these setting to work correctly.

Issue Doing a Niagara G3 integration with a Modbus controller from ASCO Power Technologies.  What type of Niagara object is required to read register 40158?  Click here to view Modbus Register Map Environment Niagara G3 ENC-520 ASCO Power Technologies controller Cause Cannot identify what type of object is needed. Resolution The number appears to be an enumerated value (1-22) and is a read-only integer. Use a Numeric Point.

Issue Daylight Savings time changed in the U.S. and methods are needed to synchronize time Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Methods for synchronizing controller time Resolution The following document was email out when Daylight Savings changed in the U.S. and contains 2 methods for synchronizing time Click Here to download the pdf document.

Issue String comparison in TGML script is not working. Product Line TAC Vista Environment TGML graphics editor 1.1.X Cause Javascript has a string class and a string literal. String literals are denoted by double or single quotation marks ("" or '') and it is important to compare "like" with "like". String literal: string1 = "Apples" String class: string1 = target.getAttribute("Name"); Resolution A deeper comparison is required in the example below. Instead of: name = target.getAttribute("Name"); tmp = target.getParentNode().getElementsByTagName("Ellipse").item(i).getAttribute("Name"); if (tmp==name) Use: if (tmp.equals(name)) An example is shown in the TGML graphic attached. Download graphic Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Configuring a Smart Sensor in SBO. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operations b3xxx Controllers Smart Sensor (LCD or LED) Cause Unsure how to program for a Smart Sensor in SBO. Resolution Some considerations to be aware of first; Object naming differences Programming of the Smart Sensor is very similar to the old Plain English programming used in Continuum. One of the main differences is that each input must be specifically defined at the start of the program. Depending on the version of SBO, there may be some other considerations with setting up/reading the LcdDisplay array by renaming of the BACnet AnalogValue's to remove the "_AV" from the BACnet name. This naming issue affects SBO v1.4. Specific variables for Smart Sensor to be used in Plain English programming. Here is an old Smart Sensor Installation manual that will help explain which objects need to be created and how they work in the controller to enable the LCD display. Create the LCDDisplay and SpaceTempSP as numerics and any other objects that are not already created as InfinitySystemVariables. See "Configuration and Programming" section in the manual starting on page 14. Also note that the sensor will not light up until values are written to it. Sample Plain English code. LCDDisplay (or LEDDisplay) is not automatically created. Create this numeric and assign it as an array with 8-elements.  If it is an LCD Smart Sensor, then create a numeric and name it "LCDDisplay" and set its logsize to 7 (this configures it as an array with 8 elements from 0 to 7). If it is an LED Smart Sensor, then create a numeric called "LEDDisplay" instead. After creating this numeric you should be able to create the PE Program successfully. The simple program below will show the current spacetemp (LcdDisplay[1]) in two decimal place format (LcdDisplay[2]) when the Display key (LcdDisplay[0]) is pressed. The degrees symbol (LcdDisplay[7]) is also shown. Consult the Smart Sensor Installation and User Guide starting on page 16 for more details on how these values are configured. Numeric Input SpaceTemp Numeric Output LcdDisplay Initialise: LcdDisplay[2] = 0 If LcdDisplay[0] = 4 then Goto ShowTemperature ShowTemperature: LcdDisplay[1] = SpaceTemp LcdDisplay[2] = 12 LcdDisplay[7] = 1024 If TS > 30 then Goto Initialise In SBO, do the following under the Application section of the b3 controller: Create a BACnet Analog Value object in the b3 called "LCDDisplay". Go to the Advanced tab and under the Log Settings section change Log Records to be 7. Save the changes. Create the program and add the above PE Script. Add the binds to the LCDDisplay object created in step 1, RoomTemp input, and any other objects used in the program.

Issue  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope. Environment Infinet Field Bus MSTP Field Bus Cause Documentation Resolution See  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope.pdf

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

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 In the Workstation, old alarms are showing in the alarm pane. Recheck does not remove, and the only option left is to "Hide". The same goes for disabled alarms. Is there a way to erase or scrub these 8-month-old alarms? When checking disabled alarms, there are a lot of alarms that have been disabled, but no one has disabled any alarms. When right-clicking on the alarms to get the context menu, most of the alternatives are greyed out. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.2 or higher Cause First, check the disabled cause to see what disabled the alarms. If it is "user," a person has disabled them. If it is "system," the system has automatically disabled them because the alarm object has lost its monitored value. Resolution Alarms in the alarm view "Recheck" command does not help then try the "Alarms Integrity Check" commend, please see LL Removing invalid alarms  Check the source path on the alarms, do they point to actual alarm objects? If the alarm objects that triggered the alarm in the first place still exist, you should be able to disable them then just enable them again. If you cannot, use the disable button in the alarm viewer then you can use the Disable alarm property in the editor (assuming version 1.2 or higher). If you can’t disable them then try to trigger them back and forth once. If the alarm objects don’t exist anymore, create alarms that would fit the source path, then just trigger those. After that, it should be safe to delete the alarm objects again. Basically, the alarms you create will take ownership of the old alarms in the viewer. Also, add the column Type in the alarm viewer and see what type they are. It would be helpful to know what the Source path and System alarm id (if there is one) are. Remove old Alarms in Alarm Pane Disabled alarms If the monitored values are not used anymore delete the alarm object that monitors the value If this is not enough make sure the path exists in the system, it can be needed to recreate the alarm in the correct path meaning the folder structure needs to be recreated. There is also the choice of right-clicking on the Alarm which gives the following menu: From this menu, one can Disable the alarm or alternatively, Hide the alarm. To view Hidden or Disabled alarms once they are not shown in the Alarms window, select one of the two Icons from the Alarms window icons as shown below:

Issue TAC Vista Error Codes in Plain Text Product Line TAC Vista Environment Vista Server Vista Workstation Cause Vista will sometimes give an error code. This list decodes the TAC Vista Family Error Codes. Resolution For a list of TAC Vista Error Codes in plain text click here.

Issue When trying to embed a website in an N4 Px view, the site renders in Workbench but not in most browsers displaying this error in the browser's developer console; Product Line TAC IA Series Environment I/A Series N4 Workbench Web Browsers, Chrome, Firefox, Edge, Internet Explorer Cause Most major browsers no longer support NPAPI/Java plugins.  Oracle has stated they would remove it in JDK 9  and from Java entirely.  The N4 WebBrowser object under the workbench pallet requires Java to work correctly.  That is why it only works in the Workbench environment, Internet Explorer, and older Oracle Java platforms. Resolution When using the WebBrowser object in Niagara N4. Viewing in the Browser Preview Mode or in an actual browser that doesn't support the Java plugin, the embedded site will not render. The only solution is to use Internet Explorer or the Web Launcher application detailed in the attached document to view the Px. For more information, refer to the Niagara Web Launcher - Niagara Java-based Web Clients Guide PDF

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.

Issue What is the replacement actuator for the EM42? Environment EM42 Actuator Cause The EM42 is obsolete. Resolution The EM42 actuator is generally associated with the V280/290, and the V380/390 series valves. The replacement actuator for the EM42 is the Schneider Electric Forta M310 Actuator. Please note that an adaptor kit (880-0252-000) is required for DN15 valves. For a copy of the EM42 data sheet please click HERE. For a copy of the M310 data sheet please click HERE.