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

Label: "tac ia series"

View in: "Building Automation Knowledge Base" | Community

1684 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue What is the correct method to implement the MsL9Value object in a Niagara R2 / MicroSmart integration using revision 9 controllers? Product Line TAC IA Series Environment Niagara R2 UNC station MicroSmart revision 9 controllers Cause The MsL9Value object requires a specific configuration to function correctly. Incorrect setup can prevent manual setpoint adjustments or operator interaction through graphics. Resolution To implement the MsL9Value object effectively: Create a virtual AI point in the MicroSmart revision 9 controller: Use a standard AI point with no input address assigned to the INPUT field. Learn the virtual AI point into the UNC station. Create an MsL9Value object in the workspace of the virtual AI point’s shadow object: Assign the logpt property (numeric value from 1 to 250). If multiple MsL9Value objects exist under the same L9 controller, each must have a unique logpt value. Refer to ibsMS-2.302.514a Release Notes for additional details. The UNC can now send a value to the virtual AI, which can act as a manual setpoint input for a Loop point or Mode Control point. Optionally, link the MsL9Value object to a GxText object to allow building operators to change the value from a web graphic.

Issue Niagara R2 UNCs using bacnet-2.305.523b.v1 or newer BACnet jar files may fail to operate correctly unless the bacnet.properties file is modified. Product Line TAC IA Series Environment Niagara R2 UNC with bacnet-2.305.523b.v1 or later Cause Upgrading BACnet jar files introduces changes that require enabling specific properties in the bacnet.properties file. Note: New stations created with these versions already include the correct file by default. The modification is only required when upgrading an existing station. Resolution Open the bacnet.properties file on the UNC. Locate the two lines near the end of the file: #pollHeartbeatCheck=true #PollRestartEnabled=true Uncomment both lines by removing the leading # : pollHeartbeatCheck=true PollRestartEnabled=true Save the file and reboot the UNC to apply changes.

Issue Can a master schedule in a Niagara R2 Enterprise Server station trigger slave schedules that reside in a PollOnDemand object within a UNC station? Product Line TAC IA Series Environment Niagara R2 Enterprise Server UNC station Cause The linkage between master and slave schedules requires proper configuration. Misunderstanding the behavior of PollOnDemand folders can lead to incorrect assumptions about schedule triggering. Resolution Schedule objects are unaffected by PollOnDemand folders. Only driver points (shadow objects) are impacted by PollOnDemand behavior. To trigger a slave schedule: Ensure a slave calendar is linked to the slave schedule within the same station. Note: Calendar-to-schedule links do not work across external links.

Issue Can MNB controllers communicate reliably in a peer-to-peer manner (e.g., sharing outside air temperature) on a BACnet/MSTP network without using a Niagara R2 UNC, Enterprise Server, or MNB-1000? Product Line TAC IA Series Environment MNB-300 controllers Cause Some sites want to avoid deploying Niagara R2 UNC, Enterprise Server, or MNB-1000 for cost or design simplicity. Resolution Yes. MNB controllers with firmware 1.4x or higher support Change of Value (COV) subscriptions, enabling each controller to act as both a COV server and client. This functionality allows reliable peer-to-peer communication between all MNB controller models. To configure peer-to-peer links: Use Link Builder in the WorkPlace Commissioning Tool and Flow Balance Users Guide (F-27358). Refer to Chapter 4 for detailed steps.

Issue Device objects in Niagara R2 are not updating as expected. Bundles were used to speed up linking to graphics. Product Line TAC IA Series Environment Niagara R2 Device objects linked to graphics using bundles Cause Bundles execute at their own rate, which interferes with the normal execution of hardware objects such as BACnet, LON, and others. This prevents device objects from updating correctly. Resolution Only native Niagara objects should be placed in bundles (e.g., AO, BO, AI, BI, and logic if desired). Do not include hardware protocol objects in bundles. For detailed guidance, refer to: Standard Reference Manual: Pages 7-14 through 7-21 Web Solutions Guide: Pages 5-1 through 5-6

Issue What colors are used to represent different real-time conditions for Niagara R2 Status Type objects? Product Line TAC IA Series Environment Niagara R2 Cause Status indicators are configured to display different colors for off-normal conditions to help operators quickly identify system states. Resolution Status Type objects contain statusInput (sIn) and statusOutput (sOut) properties. The sOut background color changes based on the condition: Condition Color Fault Orange (Dark Yellow) Down Yellow In Alarm Red Out of Service Cyan (Light Blue) Overridden Magenta (Purple) Normal Clear (Grey) Notes: Real-time text remains black in all cases. These are default colors and can be customized by editing the statusColors.properties file.

Issue A Liebert SiteLink panel is not communicating with a Niagara R2 UNC when using BACnet/MSTP protocol. Product Line TAC IA Series Environment Liebert SiteLink panel Niagara R2 UNC BACnet/MSTP communication Cause Termination resistors installed on the EIA-485 trunk negatively affect communication between the Liebert SiteLink module and the Niagara R2 UNC, even at low baud rates. Resolution Remove the 120-ohm termination resistors from the dedicated Liebert SiteLink MSTP segment connected to the UNC. Field testing confirms that removing these resistors resolves communication issues. Technical Note: Why Termination Resistors Affect Communication RS-485 networks typically use 120 Ω termination resistors at both ends of long trunks to prevent signal reflections. However, in short segments with only two devices (SiteLink and UNC), termination is unnecessary and may be harmful because: Extra resistors reduce the effective impedance, loading the line and weakening signal voltage levels. At low baud rates (9600), reflections are negligible, so termination provides no benefit. The added load can cause communication errors and device timeouts.

Issue What is the maximum number of BACnet objects supported by Niagara R2 UNC and Niagara G3 ENC stations? Product Line TAC IA Series Environment Niagara R2 UNC Niagara G3 ENC BACnet Cause Exceeding the recommended BACnet object limits can lead to performance degradation in the station. Resolution The maximum supported limit is 1500 BACnet point shadow objects for UNC and 1500 proxy points for ENC. This limit applies to all BACnet point shadow objects and proxy points, regardless of protocol type (BACnet/MSTP, BACnet/IP, or BACnet/Ethernet). Exceeding this limit will result in degraded system performance. For detailed guidelines, refer to Appendix A of the MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360).

Issue Niagara R2 stations (including Enterprise Server) may experience slow startup, high disk usage, or performance degradation due to excessive historical alarms and trend/archive data. Users need a safe and efficient way to purge old data and restore normal operation. Product Line TAC IA Series Environment I/A Series R2 Niagara Cause Historical alarms and trend/archive data accumulate in the APP folder and station database over time. Large APP folders (>500 MB) or oversized alarm tables increase boot time, consume disk space, and impact station performance. Resolution Two recommended approaches: Option 1: APP Folder Reset (Complete Purge) Removes all archived alarms, trends, and logs. Steps: Stop Niagara Service: Control Panel → Administrative Tools → Services → Stop Niagara Rename or Delete APP Folder: Path: C:\Niagara\stations\[station name]\app Preferred: Rename (e.g., app_backup_YYYYMMDD ) for rollback Restart Niagara Service: Services → Start Niagara Result: Station recreates a fresh APP folder; archiving resumes from zero. Option 2: SQL Query (Selective Purge) Removes specific alarm history while retaining other logged data. Steps: Access query form: http://[ipaddress]/appdb/queryForm Execute SQL: delete from event.eventhistory Repeat for other tables as needed (see SQL_Tutorial\QueryExamples_10_6_04.pdf). Note: May take time for large databases. Best Practices & Warnings Backup first: Zip or copy APP folder before deletion. Maintenance window: Perform during low-impact periods. Data retention compliance: Confirm customer requirements before purging. Verify after restart: Ensure alarms and trends resume logging correctly.

Issue The Niagara R2 Workplace Pro “New Station” wizard lists four vlon services instead of one. Users are unsure which service to select for LonWorks tunneling. Product Line TAC IA Series Environment Niagara R2 Cause The wizard now includes multiple vlon services (vlon0, vlon1, vlon2, vlon3) to support potential multi-service LonWorks configurations. Schneider Electric currently uses only vlon0. Resolution When configuring LonWorks tunneling, select vlon0 in the new station wizard. The additional vlon services (vlon1, vlon2, vlon3) are not used by Schneider Electric and can be ignored. Builds prior to .522 listed only one vlon service; this change does not affect functionality.

Issue When using a Niagara R2 Master Enterprise Server (MES), do all projects need to share the same Project ID? Product Line TAC IA Series Environment Niagara R2 Master Enterprise Server Cause Project IDs are used for license validation. The MES license must include all Project IDs for the Enterprise Servers it supports. Resolution Each Enterprise Server can maintain its own unique Project ID. The MES license must be configured to include all Project IDs for supported sites. Licensing details: IA-MES-1: Supports one Enterprise Server (single site). IA-MES-N: Adds support for additional Enterprise Servers (additional sites). The MES license will list multiple Project IDs and enable the multisite feature.

Issue Can Niagara R2 WebUI be configured to automatically log off web users? Product Line TAC IA Series Environment Niagara R2 Cause Niagara R2 WebUI uses HTTP Basic Authentication, which does not support de-authentication or automatic logoff. This limitation is inherent to the protocol. Resolution Automatic logoff is not available for WebUI sessions in Niagara R2. The only logoff feature applies to JDE sessions in WorkPlace Pro. For automatic logoff functionality, consider upgrading to Niagara G3, which uses cookie-based authentication and supports browser session timeout. Comparison: R2 vs G3 Authentication Feature Niagara R2 Niagara G3 Authentication Method HTTP Basic Authentication Cookie-Based Authentication Auto-Logoff Support No Yes (Session Timeout) Security Level Lower (credentials sent in header) Higher (session tokens) Recommended for Modern Security No Yes

Issue Is Niagara R2 compatible with Windows Server 2003? Product Line TAC IA Series Environment Niagara R2 Windows Server 2003 Cause Windows Server 2003 uses IIS services, which conflict with TCP port 80 required by Niagara. Microsoft update KB921883 introduced memory allocation issues for applications requiring large contiguous memory blocks. These issues occur primarily when accessing the system via Remote Desktop. Resolution Compatibility: Niagara version 514 and higher is officially certified for Windows NT, Windows XP, and Windows Server 2003. Port Conflict: Address IIS service conflicts with TCP port 80 during station database engineering. Memory Issue: If fui.exe fails with “Could not reserve enough space for object heap,” apply Microsoft Hotfix KB924054. This resolves problems caused by update KB921883 on Windows Server 2003 SP1. Remote Desktop Consideration: The memory issue is limited to Remote Desktop sessions.

Issue The Niagara R2 UNC Standard Output Window displays a ReassertDaemon error, often accompanied by java.lang.NullPointerException messages. Product Line TAC IA Series Environment Niagara R2 Cause The UNC station cannot log into the Enterprise Server as a client to update slave schedule information. This typically occurs because: Firewalls or antivirus software block inbound connections to the Enterprise Server. The Enterprise Server Address Book does not include the UNC’s IP address, username, and password. Resolution Verify that the Enterprise Server can accept inbound connections from the UNC: Check Windows Firewall and antivirus settings. Allow required ports for Niagara R2 communication. Update the Enterprise Server Address Book: Add all UNC IP addresses, usernames, and passwords. Restart the UNC and Enterprise Server after changes. Confirm that subscriptions are re-established without errors.

Issue How to properly configure a LON Router (LPR-10) within a Niagara R2 system to ensure correct communication and network stability. Product Line TAC IA Series Environment Niagara R2 system LPR-10 Cause The configuration process requires defining the router and associated channels before initiating automated processes in LonDeviceManager. Incorrect setup or missing steps can lead to communication failures. Resolution Follow these steps to configure the LON Router: Prepare the Network: Cut the existing LonRouter and Channel1 from the station. Set the status of all Lon devices to Unknown. Define Router and Channels: Refer to the procedure starting on page A-9 of the Niagara LonWorks Integration Guide. Define the LonWorks network, router, and associated channels before running any automated processes. Install Termination Devices: Ensure four LON-TERM-2 devices (LON BUS Topology Terminators) are installed: One at each end of the trunk. One at the near end of the router. One at the far end of the router. Verify Configuration: After defining the router and channels, proceed with LonDeviceManager operations. Confirm device statuses and communication integrity.

Issue How can two Niagara R2 stations run simultaneously on a single computer without causing port conflicts? Product Line TAC IA Series Environment Niagara R2 Cause By default, Niagara R2 stations use HTTP port 80. When a second station attempts to start, it fails because the port is already in use by the first station. Resolution To run two stations concurrently: Open the second station offline in Workbench. Right-click the station root and select Properties. Navigate to the Configuration tab and set the httpPort to a different value (e.g., 8080). Save and close the station database. Start the station. It should now run without conflict. When accessing the station, use the IP address followed by the port number: http://<IP_Address>:8080 Update address books for external links to include the new port number.

Issue Copy or paste operations in Niagara R2 fail when the selected objects exceed the maximum allowed size. Users often see this when working with large sections of the station database. Product Line TAC IA Series Environment Niagara R2 stations (UNC-410, UNC-510, UNC-520, TRD-NXT) WorkPlace Pro JDE tree operations (cut, copy, paste) Cause The Lifecycle margin defines the maximum size (in resource count) for any cut or copy operation in a running station. If the combined resource count of the selected objects exceeds this margin, the operation is blocked. For example, if the lifecycle margin is 20,000 and the selected objects total 43,000 resources, the operation will fail. Resolution Understand Resource Limits: UNC-410, UNC-510, UNC-520: 600,000 resources TRD-NXT: 2,500,000 resources Lifecycle margin: 20,000 resources for cut/copy operations. Check Current Resource Usage: In WorkPlace Pro, go to Search > Resource Count. Select the station root in the JDE tree to view the total resource count and lifecycle margin. Adjust Your Operation: If the cut/copy exceeds the lifecycle margin, break the operation into smaller portions. Perform multiple smaller cut/paste actions instead of one large operation. Additional Notes: Lifecycle margin exists to support the Undo feature in JDE. This mechanism temporarily creates a new tree of objects in memory, which is why limits apply.

Issue Niagara R2 UNC station sends multiple messages when emailing an alarm to a cell phone. Product Line TAC IA Series Environment I/A Series R2 station Cause When an alarm message exceeds the character limit for SMS (typically 160 characters), the cell phone carrier splits the message into multiple segments. These segments may arrive out of order, causing confusion. Resolution Limit the number of fields included in the alarm message: Configure the MailRecipient object properties to reduce message length. Each selected field appears on a separate line, increasing message size. Include only essential fields in the alarm email. Additional Notes: SMS-based delivery splits messages into 160-byte chunks. MMS delivery may send the message as a single item, but requires WAP access to view full content. Some carriers (e.g., US Cellular) now support HTML-based email without the 160-character limit in certain areas.

Issue Niagara R2 Workplace Pro cannot open localhost in the Admin Tool, preventing login. Product Line TAC IA Series Environment Niagara R2 Workplace Pro Cause The issue is typically related to Windows domain policies and administrative privileges. The username and password are tied to the domain. Domain policy restricts local administrative rights on the computer. Resolution To resolve the issue: Option 1: Modify the domain policy to allow local administrative rights (requires IT approval). Option 2: Create a new local user account with the same username and password as the domain account. Ensure this local account has administrative privileges. Note: IT departments often prefer creating a local user rather than changing domain policies.

Issue Can Network 8000 Microflo or CVV-80000 series controllers be integrated using the Niagara R2 GCM driver? Product Line TAC IA Series Environment Niagara R2 Network 8000 controllers connected via GCM-84000 GCS bus communication Cause Clarification needed on architectural compatibility and integration method between Network 8000 controllers and Niagara R2 using the GCM driver. Resolution Yes, integration is supported. The Network 8000 controllers connect to the GCS bus of a GCM-84000 controller. The GCM database contains VVBOX blocks, which interact with Microflo controllers. These VVBOX blocks can be read and written using GcmGeneric objects within a Niagara R2 UNC station. Key Notes: Ensure proper configuration of VVBOX blocks in the GCM database. Use GcmGeneric objects for data exchange between Niagara R2 and Network 8000 controllers.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Niagara R2: Best Practice for Implementing MsL9Value Object with MicroSmart Revision 9 Controllers

Niagara R2: Required bacnet.properties File Changes After BACnet Jar Upgrade

Niagara R2: Triggering Slave Schedules in PollOnDemand Objects from a Master Schedule

Peer-to-Peer Communication Between MNB Controllers on BACnet/MSTP Without Niagara R2 UNC or Enterprise Server

Niagara R2 Device Objects Not Updating When Using Bundles

Niagara R2 Status Type Object Colors for Real-Time Conditions

Liebert SiteLink Panel Fails to Communicate with Niagara R2 UNC via BACnet/MSTP

BACnet Object Limits for Niagara R2 UNC and Niagara G3 ENC Stations

Niagara R2 / Enterprise Server: Clearing Alarm & Trend History to Improve Performance

Niagara R2 vlon Services Listed in New Station Wizard

Niagara R2 Master Enterprise Server – Project ID Requirements for Multiple Sites

Niagara R2 WebUI Auto-Logoff Capability

Niagara R2 Compatibility with Windows Server 2003

ReassertDaemon Error in Niagara R2 UNC Standard Output Window

Configuring LON Router (LPR-10) in Niagara R2 System

Run Two Niagara R2 Stations Concurrently on the Same Computer

Niagara R2 – Lifecycle Margin vs Station Database Resource Count

Prevent Multiple Alarm Messages from Niagara R2 UNC When Emailing to Cell Phones

Cannot Log into Localhost Using Niagara R2 Admin Tool on Windows

Integrating Network 8000 Microflo or CVV-80000 Controllers with Niagara R2 GCM Driver

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!