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 When integrating LON with Niagara R2, the following error appears in the Standard Output Window: {lon} Wrong Nv direction for nvUpdate from {lon}MNV2_16(1/17) for Selector 132. Product Line TAC IA Series Environment Niagara R2 LON Cause The error occurs due to a mismatch between the Lon network management tables in the Niagara R2 UNC station and the actual configuration in the controllers on the bus. Common reasons include: Controllers offline during network binding changes Rogue controllers with duplicate domain, subnet, and node IDs Resolution Verify Errors Run Lon Utilities Manager (right-click on LonWorks service) Select the local Lon device Use Command Reports → Verify to compare UNC tables with controller values Correct the Issue Re-commission the local Lon device Re-commission all controllers Perform a bind to clear tables, recalculate selectors, and rewrite bindings Confirm Resolution Run Reports → Verify again to ensure no further errors

Issue In a Niagara R2 station, a folder with a very high number of links shows completed link tags as “??” instead of the usual alphabetical letters. Product Line TAC IA Series Environment Niagara R2 Cause Niagara R2 uses alphabetical tags for completed links starting from a to z, then aa through zz. When the number of links exceeds this range, the system displays “??” as a placeholder. This is a display-only limitation and does not affect system performance. Resolution No corrective action is required. The “??” tags indicate that the tag naming sequence has been exhausted. System functionality and performance remain unaffected.

Issue WorkPlace Tech cannot access the LON card when a Niagara R2 / LonWorks integration station is running on the same computer. Product Line TAC IA Series Environment Niagara R2 WorkPlace Tech Cause Niagara R2 station with autorun enabled may run in the background, occupying the LON card and preventing WorkPlace Tech from communicating with it. Resolution If you see symptoms such as: Download attempt shows “loading device driver” followed by a hand icon that does not move Error message: “waiting for service pin” Then: Open Computer Management: Right-click My Computer → Manage Navigate to Services and Applications → Services Stop the following services: Niagara Niagara LON Tunnel Verify these services are not set to start automatically on reboot.

Issue A Niagara R2 BACnet integration station running on a computer can interfere with the WorkPlace Commissioning Tool (WPCT), causing incomplete or incorrect data display. Product Line TAC IA Series Environment WorkPlace Tech Commissioning Tool (WPT CT), any revision I/A series R2 / BACnet integration station running on the same pc as the WPT CT Cause A communications port or driver conflict occurs between the WPCT and the Niagara R2 BACnet integration station, disrupting communication with MNB controllers. Resolution Symptoms of interference include: WPCT finds some or all MNB controllers, but property sheets are not fully populated. Data shown may come from default templates rather than live controller data. Best Practice: Verify the General tab of the device’s Properties sheet is populated before checking other tabs. If Firmware and Application fields are empty, WPCT is not communicating with the controller, and other tabs will show default data. To prevent interference: Open Computer Management: Right-click My Computer → Select Manage. Navigate to Services and Applications → Services. Stop the Niagara service. Note: Niagara service is typically set to start automatically after reboot.

Issue Does the Niagara R2 Modbus driver support a 6-digit address format? Product Line TAC IA Series Environment Niagara R2 Modbus driver Cause The Modbus protocol uses different notations for register addressing. The 6-digit format (e.g., 400001–409999) is a convention that shifts the type digit one position to the left to represent more registers. Niagara R2 does not support this convention when using Modbus-formatted addresses. Resolution The 6-digit Modbus notation is not supported in Niagara R2 when using Modbus format in the driver. However, you can use decimal or hexadecimal notation to specify addresses beyond the 5-digit range. When using Modbus format: The leftmost digit (e.g., '4' for holding registers) indicates the point type. The driver subtracts 1 from the entered address because Modbus uses base-1 indexing, while decimal uses base-0. Example Conversion To read data from register 422202 : Drop the leading digit → 22202 Subtract 1 → Decimal address 22201 Optionally convert to hex → 56B9 Key Notes: First 1,000 holding registers: Modbus notation: 40001–49999 Decimal: 0–9998 Hex: 0–270E There are 64,000 holding registers available, but Modbus format limits notation to 5 digits.

Issue What is the preferred method to find the MAC address of a Niagara R2 UNC? Product Line TAC IA Series Environment Niagara R2 UNC Cause The MAC address is required to configure a reserved IP address or troubleshoot network-related issues. Resolution The quickest and easiest method to find the MAC address of a Niagara R2 UNC: Open a Command Prompt on your PC. Ping the UNC using its IP address: ping <UNC_IP_Address> After receiving the ping statistics, type: arp -a The Physical Address displayed is the MAC address of the UNC. Additional Notes: All Niagara R2 UNCs share the same first four octets: 00-20-96-05 . The last two octets are unique and correspond to the UNC’s serial number.

Issue Which antivirus software is compatible with Niagara R2 and G3? Product Line TAC IA Series Environment Niagara R2 Workplace Pro (all versions) Niagara G3 Workbench (all versions) Cause Antivirus software can block essential ports, services, and files required for Niagara R2 and G3 operation, leading to communication failures or application issues. Resolution Niagara R2 and G3 software will work with any antivirus program that allows unblocked communication to the required ports, services, and files listed below: Niagara R2 Requirements Ports: Port 80 (Station communications & Web access) Port 3011 (Admin Tool) Services: Niagara Service (Control Panel > Administrative Tools > Services) Files: Files in C:\<niagara r2 release number>\nre\bin directory Niagara G3 Requirements Ports: Port 80 (Web access) Port 1911 (Station communications) Port 3011 (Platform access) Services: Niagara Service (Control Panel > Administrative Tools > Services) Files: Files in C:\<niagara g3 release number>\bin directory Important Notes: The specified Ethernet ports must be open bidirectionally for both TCP and UDP traffic. Configure antivirus software to allow or “unblock” these ports, services, and files.

Issue When accessing I/A Series R2 station graphics via a web browser, the graphic area appears blank (gray/white) or shows a placeholder box. Graphics do not render or respond to interaction. In some cases, repeated Java security warnings appear when loading graphics. Product Line TAC IA Series Environment I/A Series R2 software releases: 522.v2, 529, 532 Enterprise Server (ES) or UNC-based stations Access via Microsoft Internet Explorer (IE 7/8 or later with security updates) Cause Microsoft Internet Explorer security updates changed how ActiveX and third-party Java applets are initialized. IE now requires explicit user activation (click-to-activate) for embedded applets. This behavior blocks Niagara R2’s Java-based graphic components, preventing proper rendering. Java security prompts may also appear due to stricter applet execution policies. Resolution Apply the workaround introduced in R2 522.v2 to disable IE’s ActiveX activation fix: Backup station database before changes. Open Admin Tool → Host → Edit File → System Properties. Append the following lines at the end of system.properties (do not remove # comments): # This is used to disable the IE ActiveX activation fix. If set to # false, then the user will be required to click on the# false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false Save the file and restart the station (or reboot the UNC/ES). Repeat steps for Enterprise Server and UNCs as needed. Additional Notes / Best Practice This workaround only applies to Internet Explorer; modern browsers do not support R2’s ActiveX/Java graphics. Persistent issues may indicate Java security settings or outdated station versions—verify compatibility.

Issue No published instructions are available for installing an updated JAR file in an I/A Series (Niagara) R2 system. Product Line TAC IA Series Environment I/A Series Niagara R2 software Cause An updated version of a JAR file has been released and downloaded, but there are no clear instructions on how to replace the existing file in the system. Resolution Follow these steps to install the updated JAR file: Prepare Windows Explorer Ensure file extensions are visible: Open Windows Explorer → Tools → Folder Options → View tab. Uncheck Hide extensions for known file types. Update JAR Files on the PC Extract the downloaded ZIP file containing the updated JAR files. Copy the new .emb file to the \\niagara\\r2.<version>\\emb folder. Rename the existing file by adding .old to its name. Remove .emb from the new file name. Repeat the same process for the .nt file in the \\niagara\\r2.<version>\\nt folder. Copy the .nt file to the \\niagara\\r2.<version>\\nre\\modules folder and rename as above. Install JAR File into the UNC Launch the Niagara Admin Tool for the correct version. Connect to the UNC and open the Installation tab. Click Installation Wizard → Select the emb folder → Click Install. In the Niagara Remote Installation window: Choose Configure Modules Only → Click Next. Verify the updated JAR file is marked for upgrade. Perform a database backup when prompted. Complete the wizard and allow the station to restart.

Issue When polling BACnet points with an I/A Series R2 (Niagara) UNC, the Standard Output Window displays the warning: “BACnet Read Property Multiple Error” followed by a property name and device or object name. Product Line TAC IA Series Environment I/A Series R2 (Niagara) UNC or BACnet Server Cause The warning occurs because the BACnet device being polled does not support the Read Property Multiple function. The station attempts to use this function for efficiency, but when unsupported, the device responds with an error. Resolution This is normal operation and does not indicate a failure. All requested data will still be retrieved because the station automatically falls back to polling each property individually. To suppress the warning messages: Set the device’s Read Property Multiple property to false in the configuration. Note: Disabling Read Property Multiple will slow down polling for that device.

Issue A Niagara R2 UNC station fails to start and displays the following error messages in the standard output window: FATAL: cannot boot station from sns java.lang.JavaClassNotFoundException: tridiumx.londevices.siebe.MNLRV3 Product Line TAC IA Series Environment IA Series R2 UNC-520-2-N Cause The UNC was replaced, and the existing station database was installed on the new UNC. The station uses objects from the lonSiebe module, but this module is not installed on the replacement UNC. Resolution Install the lonSiebe module into the UNC and restart the station: Open Admin Tool and connect to the UNC. Navigate to the Installation tab and click Installation Wizard. In the Select Distribution Directory dialog, highlight emb and click Install. In the Niagara Remote Installation dialog, select Configure Modules Only and click Next. In the Configure Modules dialog, select the required modules in the Upgrade/Add column. Click Next and proceed through the Database Backup dialog (leave the red check mark next to the station database name). Enter the station username and password when prompted. Complete the process in the Niagara License dialog by clicking Finish. Restart the UNC to apply changes.

Issue Is the I/A Series (Niagara) R2 WorkPlace Pro and Enterprise Server software compatible with Microsoft Windows 7? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software, any version Microsoft Windows 7, all editions, 32-bit or 64-bit Cause PCs have been upgraded to Windows 7, and compatibility with I/A Series R2 software needs to be confirmed. Resolution The I/A Series (Niagara) R2 software is not officially certified for use with Windows 7. Informal testing was performed on the following environments: Windows 7 Professional (32-bit) Windows 7 Professional (32-bit) XP-Mode Windows 7 Professional (64-bit) XP-Mode No major issues were reported except for R2 Niagara Application Tunneling, which must be configured to run in Silent Mode in any Windows 7 environment. Tested releases: R2.529 and R2.532.

Issue How to quickly determine the IP address of an MNB-1000 integrated into a Niagara R2 station when only WorkPlace Pro is available (WorkPlace Commissioning Tool is not accessible). Product Line TAC IA Series Environment MNB-1000 Niagara R2 UNC-410 and UNC-520 Cause The IP address is stored in hexadecimal format within the controller’s shadow object properties. It must be converted to decimal format to obtain the actual IP address. Resolution Open WorkPlace Pro and navigate to the shadow object of the MNB-1000. Go to Properties → Config tab. Locate the parameter address – MAC Address. Record the first 8 digits of the hexadecimal number displayed. These represent the IP address. The last four digits are the UDP port number and should be ignored. Convert each pair of hexadecimal digits to decimal using a unit conversion tool (Windows Calculator can be used): Example: C0 = 192 A8 = 168 01 = 1 96 = 150 Resulting IP address: 192.168.1.150 Ignore the UDP port number (e.g., BA:C0 = 47808 ).

Issue How to adjust the LonWorks send and receive heartbeat settings for the localLonDevice in an I/A Series R2 UNC station to control update frequency. Product Line TAC IA Series Environment I/A Series R2 UNC LonWorks Integration Cause There may be a need to change heartbeat settings to achieve faster or slower updates for LonWorks network variables. This ensures proper synchronization without overloading the network. Resolution To Change Send Heartbeat (localLonDevice): Open the UNC station in WorkPlace Pro. Navigate to localLonDevice → Properties → Config tab. Adjust the following parameters: maxSendTime: Maximum time (in seconds) before sending an output value even if unchanged. Ensures periodic updates within the receiver’s heartbeat limit. minSendTime: Minimum time between updates to prevent network congestion from rapidly changing values. To Change Receive Heartbeat: In the same Config tab, expand nvoStatusProps. Set Receive Heartbeat: If set to 0, the device does not expect periodic updates and only reacts to value changes. Use a non-zero value to enforce periodic updates for linked inputs. Refer to Niagara LonWorks Integration Reference (pages 9-4 to 9-6) for detailed parameter definitions.

Issue After restarting a Niagara R2 UNC station, communication to LON controllers is lost. The station fails to open the LonWorks driver and cannot start LON communications. Errors such as the following appear in the standard output window: Error opening driver LON1 java.lang.Exception: Unable to open lonworks driver Cannot startService [Sys: LonWorksService] java.lang.IllegalStateException: Unable to open lonworks driver Additional LonException codes like ldvWrite() failed - rc = 6 may follow. Product Line TAC IA Series Environment Niagara R2 UNC-520-2 Niagara R2 UNC-410-1 Also applies to obsolete models: UNC-500, UNC-510, UNC-600, UNC-610 Cause The Niagara operating system is unable to communicate with the onboard Echelon MIP chip. Resolution To confirm the issue: Open the running station in Tree View. Navigate to localLonDevice → Properties → Engineering tab. Blank out the neuronId and click Apply. Reboot the UNC. If the neuronId field shows all zeros after reboot, the MIP chip has failed. This issue is not field-repairable.

Issue A Vykon Alarm Service (VAS) Client configured with limited access can view and acknowledge alarms but cannot delete acknowledged alarms from the Alarm History. The VAS Client has been configured with low-level access for use at a security desk in a building. Only certain alarms are routed to this client and the user account assigned allows for the ability to view and acknowledge alarms. The Security Mask settings are illustrated below: However, these settings do not allow for acknowledged alarms to be deleted from the VAS Client's Alarm History: Product Line TAC IA Series Environment Niagara R2 Enterprise Server Niagara R2 Vykon Alarm Service (VAS) Cause The VAS Client requires access to the entire alarm history database to delete acknowledged alarms. Limited Security Mask settings prevent this access. Resolution Modify the Security Mask settings to grant access to the entire alarm history database. This change will route all alarms to the VAS Client, enabling the user to view, acknowledge, and delete any alarms. Important: There is no way to allow deletions without granting full alarm history access. If alarm deletions should be restricted to administrative users, restore the original Security Mask settings after performing necessary deletions.

Issue When launching I/A Series R2 WorkPlace Pro or Enterprise Server, the following error appears: “This product requires a valid license. Missing license file: /nre/lib/license.properties.” Product Line TAC IA Series Environment I/A Series R2 (all versions), Enterprise Server, WorkPlace Pro Cause Windows is configured to hide file extensions for known file types. As a result, the license file is incorrectly named license.properties.properties instead of license.properties. Resolution Open Windows Explorer and navigate to the directory containing the license file (typically \niagara\r2.301.xxx\nre\lib ). If using Windows 7: Select Organize → Layout → Menu Bar to enable the classic menu bar. Go to Tools → Folder Options → View tab. Locate and uncheck the option Hide extensions for known file types. Click OK to apply changes. Rename the file from license.properties.properties to license.properties. Save the changes and restart the application.

Issue Interstation links between UNC and Enterprise Server are not functioning in Niagara R2 due to blocked unsolicited messages. Product Line TAC IA Series Environment Niagara R2 Windows XP, Windows Vista, Windows 7 UNC and Enterprise Server communication Cause Windows Firewall is enabled by default on desktop operating systems after Windows XP SP1. By default, Windows Firewall blocks unsolicited TCP packets, including alarms and interstation links from UNC to Enterprise Server, unless exceptions are configured. Resolution Overview: Windows Firewall is a stateful packet filter. To allow Niagara R2 interstation communication, create exceptions for required ports or programs. Option 1: Program Exception (Preferred) Open Windows Firewall from Control Panel. Add program exception for nre.exe located in: C:\Niagara\<Version>\Nre\Bin\nre.exe Configure scope: Any computer (least secure) My network (subnet) only (recommended) Custom list (most secure) Option 2: Port Exceptions Add TCP ports: 80, 3011 Repeat for UDP ports if required. Configure scope as above. Windows 7 Advanced Settings: Create Inbound Rules for nre.exe or custom TCP/UDP ports. Apply to appropriate profiles: Domain, Private, Public. Name rules clearly (e.g., “Niagara 80, 3011 TCP”).

Issue The UNC-520-2 in an R2 system displays an “Authentication mismatch” error for an MNL-800 controller. How can this error be corrected? Product Line TAC IA Series Environment I/A Series R2 MNL-800 Controllers Cause The Authenticate property in the LonWorksService does not match the setting in the MNL-800 shadow object. One is set to True, and the other is set to False. Authentication is rarely used due to high overhead, so it is generally recommended to disable it. Resolution Verify Authentication Settings In LonWorksService properties → Netmgmt tab In DynamicDevice shadow object → Engineering tab In MNL shadow object → General and Engineering tabs Disable Authentication In WorkPlace Pro: Open the station LonWorksService Highlight affected shadow objects From the menu, select Commands → disAuth → Yes Note: An error may appear even if the action succeeds Recommission and Rebind Recommission each Lon device (reset if commissioning fails) Rebind all affected bindings Recommendation: Set Authenticate = False in both LonWorksService and MNL-800 shadow object properties.

Issue Can Niagara R2 Enterprise Server and Niagara G3 Enterprise Network Server be installed on the same computer? Product Line TAC IA Series Environment Niagara R2 all versions Niagara G3 all versions Cause Both Niagara platforms use their own service, and only one service can run at a time. Running both simultaneously is not supported. Resolution Niagara R2 ES and Niagara G3 ENS software can be installed on the same computer if: The Windows OS is supported by both platforms. Only one Niagara service runs at any given time. Important: Both platforms cannot operate simultaneously. You must stop one service before starting the other.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Niagara R2 LON Integration Error: Wrong NV Direction for nvUpdate

Niagara R2 Folder Displays “??” Tags When Link Count Exceeds Limit

Niagara R2 LonWorks Station Interferes with WorkPlace Tech Access to LON Card

Niagara R2 BACnet Station Interferes with WorkPlace Commissioning Tool

Niagara R2 Modbus Driver Support for 6-Digit Address Format

Finding the MAC Address of a Niagara R2 UNC

Antivirus Compatibility with Niagara R2 and G3

I/A Series R2 Graphics Fail to Display in Internet Explorer Due to ActiveX and Java Applet Restrictions

How to Install an Updated JAR File in I/A Series R2 (Niagara)

BACnet Read Property Multiple Error Warning in I/A Series R2

Niagara R2 UNC Station Fails to Start – Missing LonSiebe Module

Windows 7 Compatibility for I/A Series (Niagara) R2 WorkPlace Pro and Enterprise Server

Locate IP Address of MNB-1000 Controller in Niagara R2 Station Using WorkPlace Pro

Configure LonWorks Send and Receive Heartbeats for localLonDevice in I/A Series R2 UNC Station

Niagara R2 UNC Station Fails to Start LonWorks Driver – Communication Lost to LON Controllers

VAS Client Cannot Delete Acknowledged Alarms in Niagara R2 Alarm History

I/A Series R2 Enterprise Server or WorkPlace Pro Fails to Start: Missing License File Error

Configuring Windows Firewall for Niagara R2 Interstation Communication

Authentication Mismatch Error on MNL-800 Controller in R2 UNC-520

Niagara R2 and Niagara G3 Enterprise Servers on the Same Computer

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!