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 An existing Niagara R2 MicroSmart integration has been operational for several years. Recent changes required reprogramming of some MicroSmart controllers (points added, deleted, or renamed). How should these changes be uploaded to the existing station in the UNC? Product Line TAC IA Series Environment Niagara R2 MicroSmart integrations (all versions) Cause Changes were made to building HVAC equipment, requiring updates to point configurations in MicroSmart controllers. Resolution The MicroSmart driver references the point list stored in the PointListManager of the IbsMsService. To reflect changes in the station: Any modification to point type, order, ID, engineering unit, or status ID requires uploading a new point list. Review the MicroSmart Driver Engineering Guide (F-27327), Chapter 3, Sections 3.3 and 3.3.1 for detailed instructions on: Updating unit displays Updating GX page “displays”

Issue Emails are sent when an alarm is acknowledged in Niagara R2, even though this behavior may not be desired. Product Line TAC IA Series Environment Niagara R2 Cause The MailRecipient object has the routeAcks property set to True, which routes acknowledgment events to email recipients. Resolution To prevent emails from being sent when alarms are acknowledged: Open MailRecipient Configuration Navigate to the MailRecipient object in the Niagara R2 station. Modify routeAcks Property Go to the Config tab. Set the routeAcks property to False. Apply Changes Click Apply to save the configuration. After this change, acknowledgment events will no longer trigger email notifications.

Issue How does a digital command (scheduled or manual override) from a Niagara R2 station get transferred to control a supply fan wired to a Microzone II controller? Product Line TAC IA Series Environment Niagara R2 ASD driver Microzone II Cause Limited familiarity with the Network 8000 product line and its integration with Niagara R2. Resolution Link Niagara Output to Microzone Input Connect the output of the native Niagara object to one of the digital inputs of the MZ2EmsDi object. Verify Microzone EMS Control Ensure the Microzone’s emsControlDefault property is set to On. Check this under Properties > Config for the Microzone’s Shadow object. Confirm EMS Block Status Using PSI serial tunneling, verify that the EMS block’s EMS attribute shows ON. ON indicates the Microzone is under UNC control; OFF means standalone operation. Link to Fan Control The digital command from the UNC station will appear at the corresponding DV output of the EMS block in the Microzone. Link this DV output to the block responsible for fan control.

Issue Users want to display a custom message when an alarm returns to normal in I/A Series R2, but the system only shows the alarm text field. Product Line TAC IA Series Environment I/A Series R2 alarms Cause Alarmable objects in I/A Series R2 do not include a field for “back to normal” text. Only an alarm text field is available. Resolution There is no option to configure custom text for when an alarm returns to normal. When the alarm clears, the alarm message text field will be empty.

Issue After replacing the Niagara R2 Enterprise Server hardware, alarms no longer print because the dot-matrix printer was connected via a USB adapter instead of the original parallel port. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Dot-matrix printer used for alarm printing Cause Niagara R2 does not support USB-connected printers. The original hardware provided a parallel or RS-232 port, which is required for printer communication. Resolution Use a printer connection via: RS-232 serial port, or Standard 25-pin parallel port USB printer connections are not supported by Niagara R2.

Issue Microsmart controllers do not respond to Niagara R2 schedules after a brief power outage. The UNC appears online, but Microsmart shadow objects stop updating. Product Line TAC IA Series Environment Niagara R2 (all versions) Microsmart controllers (all versions) Cause When building power fails for less than 60 seconds: The UNC performs a graceful shutdown using its backup battery but never fully powers down. Microsmart controllers reboot and come back online. The UNC assumes controllers are still online, but the link between Microsmart shadow objects and physical points is lost during the outage and does not automatically recover. Resolution Reboot the UNC to re-establish communication between Microsmart shadow objects and the controllers. Verify all schedule links after reboot to ensure proper operation.

Issue In a Niagara R2 UNC, the standard output window displays the following error repeatedly: Node.set Cast exception: nvi_7238 DsEnum <- DsFloatStatus [/DeltaHotel/lonTrunk/localLonDevice] java.lang.ClassCastException This occurs every few minutes and may impact normal operation. Product Line TAC IA Series Environment Niagara R2 UNC LON network integration Cause The error indicates an incompatible link between DsEnum and DsFloatStatus . Although the system allows the link, the data types are not fully compatible. This results in intermittent failures when property changes occur. Resolution Insert a conversion object between the two points to ensure proper data type translation: If the link direction is float → enum, use a Float-to-Enum converter. If the link direction is enum → float, use an Enum-to-Float converter. Validate the link after adding the conversion object to confirm error resolution.

Issue In Niagara R2, master-slave schedules are not working. The slave schedule goes into fault and will not clear. The following error appears in the UNC standard output window: ERROR: Could not init node [/OZS_UNC1/IbsAsdNetwork/AHU_9/MZ2_93/Schedule_8] Product Line TAC IA Series Environment Niagara R2 Cause This fault occurs when: The Enterprise Server has a holiday calendar and master schedule. The UNC only has a slave schedule. After a UNC reboot, the slave schedule checks the master schedule on the server to determine if it’s a holiday. If there is a communication issue during this check, the slave schedule object enters fault. Resolution Delete and re-create the slave schedule object in the UNC. Ensure both master/slave schedule and master/slave calendar objects exist in both the Enterprise Server and UNC stations. Verify communication between the UNC and Enterprise Server before rebooting.

Issue Difficulty integrating Eaton Series 2000 Xpert Power Meter with Niagara R2 using Modbus RTU due to unclear documentation on register map differences between IP and RTU protocols. Product Line TAC IA Series Environment I/A Series UNC Eaton Series 2000 Xpert Power Meter Cause The Eaton documentation does not clearly differentiate between Modbus register maps for TCP/IP and RS-485 RTU, leading to confusion during integration. Resolution Locate RS-485 Map: The Modbus RTU RS-485 register map is found under Eaton IQ-250/260 meter documentation, not under Series 2000. Access Embedded Utility: Use the embedded setup and monitoring software on the Eaton Power Meter. Click the Help button to upload the Modbus map as an Excel spreadsheet. Note: This map represents the TCP/IP Modbus register map, not RS-485. Connection Details: Access via a standard internet browser using Ethernet cable. Default IP address: 192.168.1.1. Register Calculation: Convert Eaton’s decimal register number to standard 5-digit Modbus register by adding 40000. Example: Register #1000 → 40000 + 1000 = 41000 (Volts Phase A - Neutral).

Issue When a special event time period overlaps with a public holiday where the calendar day is set to OFF, the system still runs according to the special event. Users need clarity on the priority between: Special events Holiday overrides Weekly time schedules Product Line TAC IA Series Environment I/A Series R2 schedule and calendar objects Cause This behavior is by design. A special event is intended to replace the daily schedule and any holiday action while active. Resolution According to the Niagara Standard Programming Reference, schedule evaluation follows this priority (highest to lowest): overrideIn input (if linked) Special Events – replaces holiday and weekly events holidayOverride input (if linked) – replaces weekly events Weekly schedule – normal time-of-day events Important: When programming special events, include any scheduled and holiday actions applicable for that day within the special event configuration.

Issue Master/slave calendar and schedule operations between an I/A Series R2 Enterprise Server and UNC do not consistently follow or recalculate during holiday override conditions. Product Line TAC IA Series Environment I/A Series R2 Enterprise Server I/A Series R2 UNC Cause The calendar object only links to the local schedule. Holiday override conditions fail when external linking is attempted or when holiday schedules are left blank, causing outputs to remain active. Resolution Schedule Configuration Place master schedule objects in the Enterprise Server and slave schedule objects in UNC controllers. Link masterOut from the Enterprise Server schedule to masterIn of one or more UNC schedule objects. Each UNC retains schedule data locally for resilience during communication failures. Calendar Configuration Place master calendar objects in the Enterprise Server and slave calendar objects in UNC controllers. Link masterOut from the Enterprise Server calendar to masterIn of one or more UNC calendar objects. Each UNC retains calendar data locally for resilience during communication failures. Holiday Override Linking Link the local calendar’s output to the local schedule’s holiday override input (e.g., master calendar → master schedule or slave calendar → slave schedule). Do not link holiday overrides across the network. Ensure holiday schedules are not left blank; otherwise, outputs may remain active.

Issue When integrating a Niagara R2 station with a Niagara G3 station via oBIX, imported R2 alarms appear as “normal” in the G3 Alarm Console even when they are in an active alarm state. Users expect alarms to display in red when active. Product Line TAC IA Series Environment Niagara G3 oBIX integrations (any version) Cause Niagara R2 native alarms are not oBIX “Stateful Alarms.” They lack a defined lifecycle for alarm events, unlike native G3 alarms. Consequently, when imported into G3, these alarms are treated as source state events and appear as “normal” (green bell icon) in the Alarm Console. Resolution To ensure alarms display in red when active: Add native G3 alarming proxies for the imported R2 alarm points. Configure these proxies to reflect the correct alarm state and color coding in the G3 Alarm Console.

Issue The Niagara R2 Enterprise Server station terminates unexpectedly when the user logs off from the virtual machine. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause The station’s App folder exceeds the recommended size of 500 MB, which can cause instability and termination when the user logs off. Resolution top the station database. Navigate to the station folder and locate the App folder. Delete the App folder or rename it with a “.old” suffix. Restart the station. The Cloudscape (App folder structure) will be automatically re-created. Important Notes: Deleting the App folder removes all station archives and logs. If archives need to be preserved, move the App folder to a safe location before deletion. Archived data can be viewed later by placing the saved App folder into a new blank station.

Issue Clarification on whether four Modbus licenses are needed to support all four RS-485 ports on a Niagara R2 UNC-520. Product Line TAC IA Series Environment Niagara R2 UNC-520 Cause Site requires integration with four different vendor products using Modbus RTU over RS-485, leading to confusion about licensing requirements for multiple ports. Resolution A UNC-520 supports up to four separate Modbus Async Networks, each using a distinct ModbusAsyncService. Only one Modbus driver license is required per UNC, regardless of the number of RS-485 ports used.

Issue Clarify the differences between I/A Series R2 time zone settings such as CST vs CST6CDT or PST vs PST8PDT, and how they compare to America/City time zone entries. Product Line TAC IA Series Environment I/A Series R2 UNCs and Enterprise Servers Cause Time zones in I/A Series R2 can be specified in multiple formats: Abbreviations (e.g., CST, PST) Abbreviation with daylight savings offset (e.g., CST6CDT, PST8PDT) Region-based identifiers (e.g., America/New_York, America/Chicago) These variations exist because of different ways to represent location and daylight savings rules. Resolution All three formats represent the same time zone and daylight savings schedule for U.S. regions: Region Abbreviation Abbreviation + DST America/City Format Eastern Time EST EST5EDT America/New_York Central Time CST CST6CDT America/Chicago Mountain Time MST MST7MDT America/Denver Pacific Time PST PST8PDT America/Los_Angeles Daylight Savings: Starts: 2:00 AM, second Sunday in March Ends: 2:00 AM, first Sunday in November For areas without daylight savings or with unique rules: Use America/City (e.g., America/Phoenix for Arizona, America/Indianapolis for parts of Indiana). For fixed offsets without daylight savings, select Etc/GMT±xx (e.g., Etc/GMT-5 for UTC-5).

Issue A Niagara R2 UNC does not keep time accurately. The time does not simply drift by seconds; it jumps by hours. Attempts to change the time using the Admin Tool fail. On startup, the Standard Output Window displays: ERROR: Cannot load /tffs/rel//nre/lib/timezones.txt java.lang.NumberFormatException Product Line TAC IA Series Environment Niagara R2 UNC Cause The timezones.txt file on the UNC is corrupt, preventing proper time synchronization. Resolution Replace the corrupt timezones.txt file with a valid copy from a functional UNC: Access the file via the Admin Tool dropdown menu. Copy the contents of timezones.txt from a working UNC. Paste the contents into the problem UNC. Restart the station to confirm accurate timekeeping.

Issue When attempting to assign a foreign address to the Configurable Analog Input object in I/A Series R2 for BACnet use, the system generates a warning: WARNING: Unable to export object: no BACnet equivalent object type for SpaceTemp [/B12B4_5/services/BACnetService] Product Line TAC IA Series Environment I/A Series R2 Cause The native I/A Series R2 Analog Input object is designed to prevent passing NaN values from input to output, holding the last valid value instead. Although the Configurable Analog Input object can be configured to pass NaN, it is not recognized as a native BACnet object. The BACnet module only supports native object types for foreign address mapping. Resolution Only native I/A Series R2 objects (AI, AO, BI, BO, MSI, MSO, calendar, and schedule) can be exposed as BACnet points using the foreign address property. To resolve the issue: Replace the ConfigurableAnalogInput object with a native AnalogInput object. Adjust the application logic accordingly to maintain functionality.

Issue An R2 station is unable to communicate with any BACnet MSTP controllers. The Standard Output Window displays the following error: ERROR: Cannot open BACnet MSTP Driver tridium.nre.DriverException: Cannot open Com5 [mstp] Product Line TAC IA Series Environment R2 station with BACnet/ MSTP trunk Cause The MSTP port specification is case-sensitive. The configuration uses Com5 (lowercase letters), which is incorrect. Resolution Update the MSTP port specification to use uppercase letters: COM5 This ensures the BACnet MSTP driver can open the correct port and establish communication.

Issue Can the I/A Series R2 ModbusAsync driver be configured to control the minimum send time between Modbus messages on the bus? Product Line TAC IA Series Environment I/A Series R2 Modbus Cause Some Modbus devices cannot process messages at normal transmission rates and require a delay between consecutive messages to avoid communication errors. Resolution Yes, the minimum send time between Modbus messages can be controlled by adding a parameter in the drivers.properties file: Ensure you have modbusAsync-2.302.514.v1 or higher installed. Open the UNC using the Admin Tool and navigate to the Installation tab. Edit the drivers.properties file. Add the following property on its own line: modbusAsync.minSendInterval=1000 (Value is in milliseconds; adjust as needed, e.g., 1000 = 1 second delay) Save the file and reboot the station. Important: Backup the station when prompted during the process.

Issue The Dynamic DEMUX object in the R2 LonWorks jar (Conversions folder) appears to incorrectly set output bits for certain SNVT_State values, causing confusion when interpreting state information. Product Line TAC IA Series Environment Niagara R2(all versions) Cause The discrepancy occurs because some third-party manufacturers define SNVT_State bits starting from bit15 on the left, counting down left to right. In contrast, the Dynamic DEMUX object assigns bits from bit0 to bit15, with bit0 on the left and counting left to right. Resolution Understand the bit assignment logic used by the Dynamic DEMUX object: For example, a SNVT_State value of 1000 hex equals 1000000000000000 in binary. The DEMUX object interprets this as bit0 ON. If third-party documentation indicates bit15 ON for the same value, this is due to their reversed bit numbering convention. Once this difference is understood, interpret DEMUX output bits accordingly.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Niagara R2 MicroSmart Integration – Updating Station After Controller Reprogramming

Prevent Email Notifications When Alarm Is Acknowledged in Niagara R2

Niagara R2 Digital Command Integration with Microzone II

I/A Series R2: No Custom Text for “Alarm Back to Normal”

Niagara R2 Enterprise Server Does Not Support USB-Connected Dot-Matrix Printers

Microsmart Controllers Not Following Niagara R2 Schedule After Power Failure

Niagara R2 UNC Error: Node.set Cast Exception Between DsEnum and DsFloatStatus

Niagara R2 Master-Slave Schedule Fault After UNC Reboot

Niagara R2 Modbus RTU Integration with Eaton Series 2000 Xpert Power Meter

Priority Between Special Events and Holiday Overrides in Niagara R2 Schedules

Intermittent Master/Slave Calendar and Schedule Issues Between I/A Series R2 Enterprise Server and UNC

Niagara R2 Alarms Display as Normal in G3 Alarm Console During oBIX Integration

Niagara R2 Enterprise Server Station Stops When User Logs Off in Virtual Environment

Does Niagara R2 UNC-520 Require Multiple Modbus Licenses for Four RS-485 Ports?

Understanding I/A Series R2 Time Zone Settings: CST vs CST6CDT and America/City Formats

Niagara R2 UNC Time Inaccuracy – Error Loading timezones.txt

Unable to Assign Foreign Address to I/A Series R2 Configurable Analog Input for BACnet Exposure

Niagara R2 BACnet MSTP Communication Failure – Driver Cannot Open COM Port

Configure Minimum Send Interval for ModbusAsync Driver in I/A Series R2

Dynamic DEMUX Object in R2 LonWorks Jar Displays Incorrect Bit Mapping for SNVT_State

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!