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 Is there a way to display the current date and time on a graphic in a Niagara R2 UNC station? Product Line TAC IA Series Environment Niagara R2 UNC station Cause The UNC does not provide a built-in graphic element for date and time display. However, a standard program object exists that can expose the UNC’s time and date components. Resolution Locate the program object in the remote library under tridiumx in the LIB jar file: DateTimeDiscreteComponents.sns Found under muxDemux → programObjects folder. Copy this object into the desired container in the station database. Create links from the object’s exposed elements to graphic text objects (GxText) or other compatible objects. Exposed Elements: As values: dateTime (DateTimeType) date (DateType) time (TimeType) timeAmPmString (String) weekday (WeekdayEnum) month (MonthEnum) SecsToday (FlowtStatusType) As integers: year , day , hour , minute , second Performance Note: Limit custom program objects to 100 or fewer in a UNC station database for optimal performance.

Issue When attempting to add a holiday event to a Niagara R2 calendar, the error message appears: “Cannot add entry” /tridium/props/error.properties#error.E_CALENDAR_FULL Product Line TAC IA Series Environment Niagara R2 Cause The Niagara R2 schedule object has a hard-coded limit of 50 events. Once this limit is reached, additional entries cannot be added. Resolution Use multiple Calendar objects to accommodate additional holiday events beyond the 50-event limit. Review existing calendar entries and remove any unnecessary events to free up space. Consider grouping holidays or using recurring events where possible to minimize the number of entries.

Issue Unable to access a remote BACnet network from a computer over the Internet when using a Niagara R2 UNC. Product Line TAC IA Series Environment Niagara R2 UNC BACnet network Cause The Niagara R2 UNC is not configured as a BACnet Broadcast Management Device (BBMD), which is required for BACnet communication across IP subnets. Resolution Configure the Niagara R2 UNC as a BBMD device. In the Commissioning Tool, set up communications so that the computer accesses the remote BACnet network using the IP address of the UNC configured as BBMD. Ensure proper firewall and routing settings to allow BACnet/IP traffic between the remote computer and the UNC.

Issue What is the maximum number of trended points that can exist in a Niagara R2 Enterprise Server station? Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause There is no fixed limit for trended points in Niagara R2. Each trend sample is stored in the station’s application database. As the database grows, system performance can degrade. Resolution There is no recommended maximum point count or trend interval for Niagara R2 Enterprise Server. Trend samples are stored in the app database located at: C:\niagara\stations\app When this folder becomes too large, the Enterprise Server performance will be affected. Workaround: Periodically move or purge the contents of the app folder to maintain optimal performance. Implement a regular maintenance schedule to prevent excessive database growth. Best Practices for Trend Configuration Set Appropriate Sampling Intervals Avoid very short intervals (e.g., <1 minute) unless absolutely necessary. Use intervals that align with operational needs (e.g., 5–15 minutes for HVAC points). Limit Retention Periods Configure trend logs to purge older data automatically after a defined period (e.g., 30–90 days). Export historical data to external storage if long-term archiving is required. Use Averaging or Summarization For high-frequency data, consider logging averages or summaries instead of raw samples to reduce database size. Monitor Database Growth Regularly check the size of the app folder and set alerts for excessive growth.

Issue When learning an MNB controller into a Niagara R2 UNC station that includes an MN-Sx sensor, a read failure occurs and multiple WARNING messages appear in the Standard Output Window. These errors did not occur with BACnet jar files prior to version 527i. Product Line TAC IA Series Environment MNB controller Niagara R2 UNC station MN-Sx sensor BACnet jar file (527i) Cause A change introduced in BACnet jar file 527i causes these warnings: The read failure occurs because the S_LK_Display1 object has no description property. Subsequent warnings appear because Niagara R2 does not support certain files listed during upload. These conditions existed in previous BACnet jars but were not reported until version 527i. Resolution These messages are legitimate and expected behavior with BACnet jar file 527i and later. No corrective action is required; the warnings do not affect system functionality.

Issue A Niagara R2 / MicroSmart integration is generating IbsMs invalid condition and receive message entries in the Standard Output Window. Example messages: ***IbsMs receive message: 454130433130464631433543 ***IbsMS invalid condition received: 28 Product Line TAC IA Series Environment Niagara R2 MicroSmart Integration Cause The issue occurs when the order of points learned into the UNC station does not match the current order in the MicroSmart controller. If a record number is reused (e.g., a point is deleted and replaced with a different type), the UNC expects the original point type but receives a different one. Example: An Analog Output point is deleted and replaced by a Start/Stop point using the same record number. Resolution Two options to resolve the mismatch: Re-learn the controller in the station. Note: This will break existing links and require re-binding all points. Reload the MicroSmart controller with its original database so it matches the station’s learned database. Additional Tip: Enable debug mode to identify the offending controller(s). Disable debug mode afterward to avoid excessive log entries.

Issu Niagara R2 GCM driver may generate errors during the upload of View/Edit/Override (VEO) information. Product Line TAC IA Series Environment Niagara R2 GCM driver Cause Missing LABEL blocks: If VEO## attributes exist without an associated LABEL block, the upload process can fail and trigger a NullPointerException . Unsupported attribute types: The GCM driver only supports AV and DV types. Any other attribute types in the VEO list will cause a ClassNotFoundException . Resolution Use the CreateVeoGxPages button on the Block List Manager screen to upload VEO information and generate display screens. Ensure each VEO has a corresponding LABEL block in the GCM. Name LABEL blocks starting with VEO and ending with 01 to 10. Remove all non-AV or DV attributes from the VEO attribute lists before uploading. After these corrections, retry the upload process.

Issue Is it possible to configure a single computer to perform both Niagara R2 and Niagara G3 serial tunneling? Product Line TAC IA Series Environment Niagara R2 Serial Tunnel Client Niagara G3 Serial Tunnel Client Cause Running Niagara R2 and G3 simultaneously on the same COM port causes conflicts and prevents proper operation. Resolution Yes, a single computer can run both Niagara R2 and G3 serial tunneling services. Each version installs its own Windows service, allowing them to operate concurrently. Important: They must use different COM ports. If separate COM ports are not available, only one service can be active at a time. Stop the other before starting the desired service.

Issue When attempting to run Workplace Pro on a Niagara R2 computer, the following error appears in the Niagara Console: *** Unjar: c:\niagara\r2.301.522\nre\modules\demo.unjar java.util.zip.ZipException Product Line TAC IA Series Environment Niagara R2 Workplace Pro Cause .unjar files, which are normally used by the Niagara installer during installation, have been incorrectly copied into the modules directory on the computer. Resolution Stop the Niagara Service on the computer. Navigate to the directory: c:\niagara\r2.301.522\nre\modules\ Delete all .unjar files in this directory. Restart the Niagara Service. Launch Workplace Pro – it should now function correctly.

Issue Understanding how a Niagara R2 Master Enterprise Server operates and its role in archiving data from subordinate Enterprise Servers. Product Line TAC IA Series Environment Niagara R2 Master Enterprise Server Cause The installation uses a Master Enterprise Server and requires details on its functionality, especially for log archiving and multisite polling. Resolution Key features and configuration steps for Niagara R2 Master Enterprise Server: License Requirement Must include the “multisite” feature to enable Poll Archive Service. Poll Archive Service Located in tridiumx / Multisite.jar . Collects data from the Application Database (App folder) of subordinate servers. Appends new polled data to existing archives. Address Book Setup Include all subordinate stations as clients in the Master Enterprise Server’s Address Book. Poll Groups Enable Poll Archive Groups individually. Configure poll frequency (hours) in Poll Archive Service properties. Optional: Use Date-Time Trigger for scheduled polling via “Link From, Link To”. Manual Polling Navigate to Services Container → Go → Service Manager → Poll Archive Service. Select Poll Group and click Invoke. Log Data Sources Direct polling from log objects in UNC 5x0/6x0: Enable “polled” in archiveSetup. If polling archived data: Client station log service = Archive Local. If polling live log objects: Client station log service = Archive Remote. Viewing Archived Data Use WorkPlace Pro Database Browser or web servlets: appdb , archive/index , or chart/log .

Issue How to integrate the nciSetpts SNVT from a Viconics Thermostat (Model VT7200C1018E) into Niagara R2. Product Line TAC IA Series Environment Niagara R2 Viconics Thermostat (Model# VT7200C1018E) Cause Configuration details are required to correctly link the thermostat’s SNVT setpoint object ( nciSetpts ) with Niagara R2 for proper integration. Resolution Use the shadow object: T7XFCr . Link the thermostat’s nciSetpts SNVT to Niagara R2 using the SnvtTempSetptCmd object. Important Note: If a setpoint is changed locally at the thermostat display, that value will override the SNVT-provided setpoint and become the controlling setpoint.

Issue Enabling Authentication in a Niagara R2 station’s LonWorks service when MNL controllers are on the LON trunk under a UNC can disable LON communications to the controllers, possibly permanently. Product Line TAC IA Series Environment Niagara R2 MNL Controllers Cause When Authentication is enabled in the LonWorks service without proper commissioning, MNL controllers can enter one of two states: Recoverable Mode – Authentication enabled but controllers not commissioned with Authentication. Permanent Hard Offline Mode – Authentication cleared via service pin, then recommissioned incorrectly, making the controller unrecoverable. Resolution Do NOT enable Authentication when MNL controllers are present on the LON trunk. If Authentication was enabled: Use the service pin method to clear controller authentication (refer to WorkPlace Tech Tool 4.0 Engineering Guide, p. 602). Attempt recovery using NodeUtil to access and modify memory. Contact Product Support for detailed instructions. If the controller was recommissioned after clearing authentication, it will be permanently offline and cannot be recovered.

Issue A Niagara R2 Enterprise Server station fails to start. The Standard Output Window displays the following error: ERROR: Cannot add key entry: 8390 java.lang.IllegalStateException: Missing class for: 24 Product Line TAC IA Series Environment Niagara R2 Enterprise Server station Cause Conflicting or missing jar files. This typically occurs when non-standard jar files (e.g., Smartware or Distech) are present, which are not part of the official released version of WorkPlace Pro. Resolution Verify that all jar files in the station are part of the official Niagara R2 release. Remove any third-party or custom jar files that are not included in the standard installation package. Restart the Enterprise Server station after correcting the jar file set.

Issue Cannot connect to a Niagara R2 UNC-520 because the IP address was incorrectly set. No access is available via the Ethernet port. Product Line TAC IA Series Environment UNC-520 or UNC-410 Cause Incorrect entry of the IP address or subnet mask can cause the UNC to appear unresponsive to WorkPlace Pro, preventing normal network access. Resolution Two methods are available to determine and correct the IP address and subnet mask: Check the Configuration File If you have access to the computer used to change the IP address, locate the file: \Niagara\r2.301.522\nre\user\ipchanges.txt This file contains the date, time, username, original IP, new IP, and controller name. Example entry: 9:54 16-Dec-2008 CST: tac 10.159.34.123 -> 10.1.146.128 on J404-29764 Direct Serial Connection Using HyperTerminal Required components: UNCC-405 adapter, CBL-RJ45 cable, and HyperTerminal. Connect to the UNC-520 via RS232 using the adapter and cable. Follow steps in Chapter 2 of the Niagara Networking & Connectivity Guide for HyperTerminal setup. Use the procedure “Determining an IP address of a JACE-4/5” in Chapter 3 to display or change the IP address and subnet mask. Ensure the subnet mask is entered correctly; failure to do so will prevent the UNC from being recognized by WorkPlace Pro.

Issue In a Niagara R2 UNC or Niagara G3 ENC station running the ASD service, the block output override feature does not get range-checked if the override is initiated from a linked gxText or graphic. Product Line TAC IA Series Environment Niagara R2 Niagara G3 Cause A defect in the graphic feature allows overrides from gxText or graphics to bypass range validation. When the override value exceeds 255, it is truncated to a one-byte value (equal to four minutes). Resolution Overrides performed directly on the Block Output object are range-checked (valid range: 0–255). If using gxText or graphics: Add descriptive text or a warning near the override control indicating the valid range (0–255). Avoid entering values greater than 255 to prevent truncation.

Issue When commissioning a ProView for LON Display in a Niagara R2 station, the wizard initializes with the error message “Nv Type Lookup Error.” Product Line TAC IA Series Environment Niagara R2 station ProView for LON Display Cause The error occurs during the initial commissioning of the display. The Workplace Pro DOS window may also show a Java exception: OnInit_WeekSchedStep called. Disposal was interrupted: java.lang.InterruptedException Resolution This is a nuisance error that only appears during the first commissioning attempt. To resolve: Clear the program from the display. Exit the wizard completely. Re-enter the wizard and restart programming. Subsequent commissioning attempts will complete successfully without the error.

Issue In Niagara R2, manual commands cannot be issued directly to Network 8000 GCM/LCM analog and binary points through a web browser. The manualCmd field exists in objects such as LcmAnalogCmd , LcmBinaryCmd , GcmAnalogCmd , and GcmBinaryCmd , but the option does not appear. Product Line TAC IA Series Environment Niagara R2 system with Network 8000 GCM/LCM integration Cause An anomaly in these command objects prevents the manualCmd option from being available until the object is linked to an appropriate output object. Resolution To enable manual commands: Connect the command object ( AnalogCmd or BinaryCmd ) to an Analog Output or Binary Object. Issue a change using the connected output object. After this step, the option to issue a manual command to the AnalogCmd or BinaryCmd object will become available.

Issue In Niagara R2, some GxPages and control objects need to be duplicated many times, each with multiple links. Manually linking each property individually is time-consuming. Product Line TAC IA Series Environment Niagara R2 Cause Graphics programming in Niagara R2 requires linking properties between GxPages and control objects. Without an efficient method, this process becomes labor-intensive when dealing with large numbers of objects. Resolution Use Bundles and Composites to streamline linking: Create a Bundle Container Bundles group related objects for easier linking. Only native Niagara objects should be placed in bundles (avoid shadow objects). Apply Composites Assign the same name to both the GxPage property and the control object property that need linking. Use the Match Function In the Link Properties screen, click Match. Objects with identical names will automatically link. Reference Documentation Detailed steps are in the Niagara Standard Programming Reference document.

Issue Users need to access a Niagara R2 station through a browser or Java Desktop Environment (JDE) without being prompted for a username and password. Product Line TAC IA Series Environment Niagara R2 Cause By default, Niagara R2 requires user authentication before granting access to station pages. This behavior can be bypassed using the Public Access feature introduced in Niagara R2 version 2.3. Resolution Starting with Niagara release 2.3, a Public Access feature was added that allows configuration of a station to permit GxPage access without sign-on. To enable: Open the station configuration in Niagara R2. Enable the Public Access option for the desired GxPages. Save and restart the station if required. Verify that the Sign On dialog box is skipped and the GxPage displays as if the user is already signed on. For detailed setup instructions, refer to the Niagara Web Solutions Guide. Security Considerations Risk of Unauthorized Access: Enabling public access removes authentication, allowing anyone with network access to view station pages. Sensitive Data Exposure: Ensure that no critical control points or configuration settings are exposed on public pages. Network Segmentation: Consider isolating the Niagara station on a secure VLAN or behind a firewall to limit exposure. Audit and Monitoring: Implement logging and monitoring to detect unauthorized or unexpected access. Alternative Approach: If possible, use role-based access with limited permissions instead of full public access.

Issue Alarm notifications are generated and forwarded when plant or equipment is intentionally offline for maintenance or other downtime, causing nuisance alarms. Product Line TAC IA Series Environment Niagara R2 Cause The system lacks logic to inhibit alarms when plant or equipment is intentionally offline. By default, the StatusInhibit property of the AI object is not linked, and the inhibitTime property remains at zero, preventing proper alarm suppression. Resolution Add a Binary Output (BO) Object Link the StatusOutput of the BO to the StatusInhibit of the AI object (the alarm to be inhibited). Set inhibitTime Property Ensure the inhibitTime property of the AI object is set to a non-zero value (any value other than zero). Configure Input Signal The BO object should represent the plant or equipment’s offline status: From an object indicating equipment down/offline Or from a manually activated GxPage object Verify Functionality When the plant or equipment is offline and the BO signal feeds into StatusInhibit, the AI object will not produce alarms even if alarm conditions exist. Test thoroughly before deploying in a live system.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Niagara R2 UNC – Display Current Date and Time on a Graphic

Niagara R2 – Error “Cannot add entry” When Adding Holiday Event to Calendar

Niagara R2 UNC – Accessing Remote BACnet Network via BBMD Configuration

Niagara R2 Enterprise Server – Maximum Trended Points and Performance Impact

Niagara R2 MNB Controller Learn Failure with MN-Sx Sensor and BACnet Jar 527i

Niagara R2 MicroSmart Integration – Invalid Condition and Receive Message Errors

Niagara R2 GCM Driver Errors When Uploading VEO Information

Can One Computer Run Both Niagara R2 and G3 Serial Tunneling?

Niagara R2 Workplace Pro Fails to Start – ZipException Error During Unjar Process

Niagara R2 Master Enterprise Server – Features and Poll Archive Configuration

Integrating nciSetpts SNVT with Niagara R2 for Viconics VT7200C1018E Thermostat

Do Not Enable Authentication in Niagara R2 LonWorks Service with MNL Controllers on LON Trunk

Niagara R2 Enterprise Server Station Fails to Start – Missing Class Error

Unable to Connect to Niagara R2 UNC-520 Due to Incorrect IP Address Configuration

Niagara R2/G3 ASD Service: Block Output Override Range Check Issue

ProView for LON Display Wizard Shows “Nv Type Lookup Error” in Niagara R2

Manual Commands for Network 8000 GCM/LCM Points in Niagara R2

Quick Linking of Multiple GxPages and Control Objects in Niagara R2

Enable Public Access for Niagara R2 Station Without User Sign-On

Prevent Nuisance Alarms in Niagara R2 During Plant or Equipment Downtime

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!