Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue When accessing a Niagara R2 UNC station remotely, the following error occurs: “Invalid status error 503.” Product Line TAC IA Series Environment Remote I/A Series R2 station Cause The error occurs because the UNC web server runs out of available threads. Each station-to-station connection and web browser session consumes a thread. The default thread pool size may be insufficient for sites with many UNCs or heavy traffic. Resolution Open the system.properties file on the UNC. Locate the line: webServer.threadPoolSize=15 Increase the value to 25 or 30 to allow more concurrent connections. Save changes and reboot the UNC. If the issue persists, disable ActiveX activation by changing: ie.activex.activation=true to ie.activex.activation=false

Issue How can a BACnet system be customized to maximize data throughput? The site has a Niagara R2 Enterprise Server and a UNC with multiple MSTP controllers connected. Product Line TAC IA Series Environment Niagara R2 Enterprise UNC MSTP controllers Cause Improper BACnet configuration and default settings can lead to inefficient communication and slow system performance. Resolution Follow these best practices to improve BACnet MSTP performance: Remove Unused BACnet Objects Delete unnecessary BACnet objects learned into the station. Move non-critical objects from Poll-Always to Poll-on-Demand containers. Optimize Controller Addressing Ensure all MSTP controllers are consecutively addressed. Avoid gaps in addressing to reduce communication delays. Benefits of Consecutive Addressing: Faster Token Passing: Token moves quickly without searching for missing addresses. Reduced Token Search Overhead: Minimizes wasted polling cycles caused by gaps. Easier Troubleshooting: Simplifies device identification and network verification. Optimized MaxMaster Setting: Predictable and efficient configuration. Set Correct MaxMaster Value Configure MaxMaster in all controllers and the UNC to two greater than the highest MSTP address. Example: If highest address = 20, set MaxMaster = 22. Leaving MaxMaster at 127 with only 20 controllers causes unnecessary token searches. Adjust MaxInfoFrames Set MaxInfoFrames in the UNC or MNB-1000 to between 5 and 20. Default is 1, which results in sluggish updates. Start at 5 and increase gradually to find the optimal performance point. Reference Documentation See I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360) for detailed recommendations.

Issue How to convert a Trane BCU (models BMTW or BMTX) from BACnet/Ethernet to BACnet/IP for integration with a Niagara R2 UNC. Product Line TAC IA Series Environment Trane BCU (BMTW or BMTX) Niagara R2 UNC Cause The BCU is factory-configured for BACnet/Ethernet. To integrate with Niagara R2 UNC over BACnet/IP, the BCU must be reconfigured using Tracer Summit tools and a special serial cable. Resolution Prepare Required Components Special Trane serial cable (custom pin-out below). Access to Tracer Summit software. Run BCU Configuration Tool Navigate to: C:\Program Files\Tracer Summit\Bin Launch BCUconfig.exe. Enter configuration details and select Download (requires serial cable). Allow the BCU to reset. Update Tracer Summit Connection Settings Open Tracer Summit and select Connect. In the Site Connection Wizard: Choose BACnet/IP. In Ethernet Configuration, check Open on startup. In BACnet/IP settings, enable Use BBMD connection. Specify BBMD BCU IP address and BACnet UDP port. Click Finish.

Issue When attempting to write a setpoint to a holding register in a Modbus controller from an R2 Niagara station, the operation fails with the error: “Illegal Data Address.” Product Line TAC IA Series Environment R2 Niagara integration to a Modbus controller. Cause The Modbus write operation fails because the default configuration does not allow writing multiple registers using the preset function. This results in the controller rejecting the request with an “Illegal Data Address” error. Resolution Navigate to Properties of the Modbus Asynch Service in the Niagara R2 station. Go to the General → Config tab. Set the parameter usePresetMultipleRegister = True. Click Apply to save changes. This procedure has been successfully tested with Siemens PLCs and Thermax chiller controllers.

Issue When using the chart/log servlet in a browser within Niagara R2, the legend size appears truncated and cannot be widened. Product Line TAC IA Series Environment Niagara R2 Cause The legend size is fixed in the servlet design. Log object names selected for charts are truncated because the servlet does not allow manual resizing of the legend area. Resolution The legend size cannot be adjusted manually. To improve readability: Use the Logs Only (Description) or Logs Only (Swid) option when calling /chart/log . Customize the Log Object description field (up to ~26 characters excluding units). If the description field is cleared, the servlet will display the object’s name in the legend instead.

Issue When upgrading an I/A Series R2 Enterprise Server station, the database conversion process fails with the error: java.lang.OutOfMemoryError . Product Line TAC IA Series Environment I/A Enterprise Server R2 (all versions) Cause The Java Virtual Machine (JVM) heap size is limited to 1 GB by default. During the upgrade, the conversion process attempts to handle a large station database containing numerous log objects and associated records, exceeding the available heap memory. Resolution Increase Java Heap Size Locate nre.properties in \\niagara\\lib directory. Edit the file and ensure: Java.options=-Xmx1024MB Save changes and restart the Niagara service. Clear Logs if Issue Persists Restart the station in its current version. Archive logs using archiveAll command in WorkPlace Pro. Clear logs manually or use AdminTool to globally reduce buffer sizes: Copy AdminTool from Local Library ( tridium/apps/AdminTool ) to station root. Configure properties: propertyName = bufferSize newValue = 1 objectTypeFilter = *Log recurseChildren = True Execute Search and Replace command. After clearing, return buffer sizes to normal and retry upgrade.

Issue A BACnet Binary Input object cannot be added directly to a Niagara R2 container in Workplace Pro. Product Line TAC IA Series Environment Workplace Pro Cause In Workplace Pro, BACnet objects must reside under a BACnet Device object. Attempting to add a BACnet Binary Input directly to a container without a BACnet Device results in failure. Resolution Copy a BACnet Device from the Local Library: Path: /tridiumx/BACnet/objects/BACnetDevice Add the BACnet Device into the container. Place the BACnet Binary Input object under the BACnet Device. For detailed steps, refer to the BACnet Integration Reference documentation.

Issue A LON SNVT on a shadow object in a Niagara R2 UNC station takes 2–3 minutes to update after an override command is issued from a graphic. Product Line TAC IA Series Environment Niagara R2 UNC LON SNVT on a shadow object Cause The minimum and maximum send times for the LON device are not set correctly. minSendtime controls the minimum delay before updates. maxSendtime controls the maximum interval for sending updates. Incorrect values cause delayed updates. Resolution In Workplace Pro, navigate to Local Lon Device > Config tab. Verify and adjust the following parameters: minSendtime = 5 seconds (default) maxSendtime = 100 seconds (default) Re-upload the affected LON object from the LON controller. Re-bind the LON object in the Lon Link Manager. Confirm that updates occur promptly after override commands.

Issue When logging into a Niagara R2 Enterprise Server station, the default web page displays the error: ERROR: Invalid template: db/Bacnet522/BACnetTemp/Josh_Plant/JoshIndex. The file does not exist on the server. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause The WebUIservice requires a valid background HTML page specified in the default template URL field. If this field is incorrect or missing, the web pages cannot render properly. Resolution In Workplace Pro, navigate to the WebUIservice. Right-click WebUIservice → Properties → Config tab. Verify that the Default Template URL is set to: /tridium/services/defaultTemplate.html Correct the path if necessary and save changes. Restart the station and confirm that the web page displays correctly. For additional details, refer to the Niagara Web Solutions Guide.

Issue How to identify the version of the Cloudscape database running on a Niagara R2 Enterprise Server. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cloudscape database Cause The Cloudscape database version is not immediately visible in the standard interface, requiring navigation to specific properties within Workplace Pro. Resolution Open Workplace Pro and connect to the Niagara R2 Enterprise Server station. Locate the Database Service in the station tree. Right-click the Database Service, select Go, then choose Properties. In the General > Status tab, find the field labeled databaseProductVersion. This field displays the current Cloudscape version running on the Enterprise Server.

Issue The Vykon Alarm Client cannot establish a connection with the Niagara R2 Enterprise Server station. Product Line TAC IA Series Environment Vykon Alarm Client Niagara R2 Enterprise Server station Cause The Vykon Alarm Client communicates with the Enterprise Server using TCP port 4321. Many firewall, antivirus, and remote access applications block this port by default, preventing the connection. Resolution Verify TCP Port Usage Open a command prompt and run: netstat -ano Look for an entry where the Foreign Address includes :4321 and the State is ESTABLISHED . This confirms a successful connection. Adjust Security Settings Create an exception rule in the firewall or antivirus software to allow TCP port 4321. Alternatively, temporarily disable the blocking application to test connectivity. Confirm Connectivity After applying changes, restart the Vykon Alarm Client and check for successful connection.

Issue When attempting to open a Niagara R2 UNC station in Workplace Pro, a pop-up error appears stating: "Not Found (404)". Product Line TAC IA Series Environment Niagara R2 UNC Workplace Pro Cause The error typically indicates that TCP port 80 is blocked on the PC accessing the UNC. Common culprits include: Windows Firewall Remote access software Antivirus software Microsoft IIS Resolution Check if TCP port 80 is blocked: Open Command Prompt as Administrator. Run: netstat -an | find ":80" If you see LISTENING or ESTABLISHED , port 80 is in use. Alternatively, use: telnet <UNC_IP_Address> 80 If the screen goes blank, the port is open. If it fails, the port is blocked. Identify Which Application is Using Port 80 In Command Prompt, run: netstat -ano | find ":80" Note the PID (last column). Find the application linked to that PID: tasklist | find "<PID>" Replace <PID> with the number you noted. Common applications using port 80 include: Microsoft IIS Skype Remote Management Tools Antivirus Web Shield Resolve the Conflict Disable the application blocking the port while accessing the UNC. If disabling is not feasible, create an exception policy in the application to allow port 80 communication for the UNC’s IP address. Procedures vary by application (e.g., firewall, antivirus, IIS)

Issue An "Access Denied" error occurs during the reinstallation of Niagara R2 software. The installer shows a Module Install Error message and repeatedly prompts the user after clicking OK. Product Line TAC IA Series Environment Niagara R2 software Cause Files in the nre\modules folder are marked as read-only after the initial installation, preventing the installer from overwriting them during reinstallation. Resolution Before attempting to reinstall Niagara R2 software: Open Windows Explorer (My Computer). Navigate to the niagara\nre\modules folder. Select all files in this folder. Right-click and choose Properties. In the Properties window, clear the Read-only checkbox. Click OK to apply changes. After removing the read-only attribute, rerun the Niagara R2 installer.

Issue Users need to back up a Niagara R2 UNC or Enterprise Server station but do not have access to Workplace Pro. Is there a way to perform the backup using only a web browser? Product Line TAC IA Series Environment Niagara R2 Cause The station database needs to be saved locally for potential restoration. Workplace Pro is unavailable, requiring an alternative backup method. Resolution Yes, a backup can be performed via a web browser, but note: This method only backs up the station database. The entire database will open in XML format on the webpage. Large stations may take a long time to load. Steps: Log into the station using a web browser. Navigate to: http://[ip-address]/prism/backup Wait for the browser’s loading indicator (bottom-left corner) to finish. Once the page is fully loaded, save the page as an XML file: Use the Save As option in the browser. Store the XML file on your PC for future restoration. Reference: Appendix B of the Niagara Browser Access Guide for additional details.

Issue Emails fail to send from a Niagara R2 UNC station using MailService. Issues may include: “relay access denied” error messages Test email fails despite correct SMTP configuration. Product Line TAC IA Series Environment Niagara R2 station Cause SMTP servers often require authentication. By default, Niagara R2 does not enable SMTP authentication in its configuration, causing email delivery to fail. Resolution Enable SMTP authentication in the Niagara host configuration: Edit the system.properties file on the UNC or Enterprise Server. Add or confirm the following lines: mail.smtp.auth=true mail.useUTF=false If mail.smtp.auth is commented out (e.g., #mail.smtp.auth=true ), remove the # . Save changes and reboot the UNC or Enterprise Server. Retest email sending to confirm successful delivery.

Issue Clarification is needed on whether the IP address must be included in the SSL certificate for a SmartX server using self-signed certificates managed with Device Administrator, and what happens if the server’s IP address changes after certificate issuance. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation server Building Operation Device Administrator Cause When using self-signed SSL/TLS certificates managed with Device Administrator, client validation checks the Subject Alternative Name (SAN) entries in the server certificate. If clients connect by IP address, the SAN must include that IP. If clients connect by DNS hostname, the SAN must include the hostname. Certificates missing the identifier used by clients will fail validation. Additionally, self-signed certificates require clients to trust the issuing root certificate. Resolution Is the IP address mandatory in the SSL Certificate? No. It is not strictly required. Recommended: Include the DNS hostname (e.g., My_Server ) in the SAN. SSL Certificate dialog box Optional: Include the IP address if clients are known to connect using IP rather than hostname. Certificates with (left) and without (right)DNS set Why hostname is preferred: Hostname-based SAN entries are resilient to IP changes. As long as DNS resolves the hostname to the current IP, the certificate remains valid. What happens if the SmartX server’s IP address changes? If SAN only contains the old IP and clients connect via IP, TLS validation fails, and clients cannot connect. If SAN contains the DNS hostname and clients connect via hostname, the certificate remains valid after IP changes, provided DNS is updated. Self-signed consideration: Ensure all clients trust the self-signed root certificate. This requirement is independent of SAN content.

Issue Customer wants to configure external log storage using Microsoft SQL Server and use an alias instead of an IP address for the connection. Is alias supported? Product Line EcoStruxure Building Operation (EBO) Environment EcoStruxure Building Operation External Log Storage Cause The customer prefers using an alias for the SQL Server connection instead of an IP address or hostname. Alias configuration is typically managed in SQL Server Client Network Utility or SQL Server Configuration Manager. However, EBO does not have built-in support for SQL Server alias resolution. Resolution SQL Alias What it is: An alias is a client-side configuration in SQL Server Configuration Manager that maps a custom name to a specific SQL Server instance and port. How it works: Applications that support SQL Native Client can use the alias instead of the actual server name. EBO limitation: EBO does not use SQL Native Client for alias resolution. It expects a direct hostname or IP. Using an alias to connect to the MSSQL server is not supported in EcoStruxure Building Operation. To ensure proper connectivity: Use the server hostname or IP address in the external log storage configuration. Verify that the SQL Server instance is accessible via the chosen hostname/IP. Ensure firewall and network settings allow communication on the required SQL ports (default: TCP 1433).

Issue The UNC is not communicating at 100 Mbps as expected. Product Line TAC IA Series Environment Niagara R2 UNC Cause The Ethernet port on a UNC is auto-sensing, meaning it negotiates speed and duplex settings with the connected device. The UNC supports 10 Mbps or 100 Mbps, full or half duplex. Gigabit (1000 Mbps) speed is not supported. If the UNC fails to communicate at 100 Mbps/full duplex, common causes include: Hub or switch does not support 100 Mbps/full duplex Wiring issues between UNC and hub/switch Resolution Verify that the hub or switch supports 100 Mbps/full duplex. Check and correct any wiring issues between the UNC and the hub/switch. Ensure the UNC is connected to a compatible Ethernet device (10/100 Mbps).

Issue Stations do not open when multiple versions of Niagara R2 software (e.g., 4.31, 5.14, 5.22, 5.29) are installed on the same computer. Product Line TAC IA Series Environment Niagara R2 Cause By default, the Niagara service for the most recent version starts automatically when the computer boots. Only one Niagara service instance can run at a time, preventing older versions from opening stations. Resolution To open stations with an older version: Open the Console for the desired Niagara version: Start > Programs > Niagara <version> > Console In the Console window, type: admininstall install /start If successful, you will see: Niagara service successfully installed. Niagara service successfully started. The stations will now open using the selected older version.

Issue When Niagara R2 UNCs use BACnet routers, the router function stops working if other BACnet routers are present on the same network. Product Line TAC IA Series Environment Niagara R2 UNC BACnet routers Cause Niagara R2 stations detect a routing conflict when multiple routers exist on the same BACnet network. To prevent packet flooding caused by repeated circulation of requests, the station disables its routing functionality. Resolution By default, routing cannot be re-enabled without restarting the station, which may cause remote access issues. Starting with release 2.305.516, you can configure the BACnet service to maintain routing even during network misconfigurations: Edit the bacnet.properties file on the host and add: maintainRoutingEnabled=true From the BACnet service, run the menu command: readBACnetPropertiesFile This applies the changes without requiring a restart.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Niagara R2 UNC Remote Access Error 503 – How to Resolve

Optimize BACnet MSTP Data Throughput in Niagara R2 Systems

Convert Trane BCU (BMTW/BMTX) from BACnet/Ethernet to BACnet/IP for Niagara R2 Integration

Modbus Write Error “Illegal Data Address” in Niagara R2 Station

Niagara R2 Chart/Log Servlet – Legend Size Cannot Be Extended

Enterprise Server Upgrade Fails with java.lang.OutOfMemoryError During Database Conversion

BACnet Binary Input Cannot Be Added to Niagara R2 Container in Workplace Pro

LON SNVT Shadow Object in Niagara R2 UNC Updates Slowly After Override

Niagara R2 Enterprise Server Error: Invalid Template File Missing

Determine Cloudscape Database Version on Niagara R2 Enterprise Server

Vykon Alarm Client Fails to Connect to Niagara R2 Enterprise Server

Niagara R2 UNC Station Not Found (404) Error in Workplace Pro

Access Denied Error During Niagara R2 Software Reinstallation

Backup Niagara R2 UNC or Enterprise Server Station via Web Browser

SMTP Authentication Required for MailService in Niagara R2 UNC – Emails Not Sent

SSL Certificate Requirements for SmartX Server: IP Address and Impact of IP Changes

Is SQL Server Alias Supported for External Log Storage in EBO?

Niagara R2 UNC Ethernet Port Supported Speeds

Niagara R2: Stations Fail to Open When Multiple Versions Are Installed

Niagara R2 BACnet Router Stops Routing When Multiple Routers Exist on Network

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!