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.

Issue How can the default HTTP port for a Niagara R2 UNC station be changed from port 80 to a custom port? Product Line TAC IA Series Environment Niagara R2 UNC station Cause The station requires a non-standard HTTP port for security or network configuration purposes. By default, Niagara R2 uses port 80. Resolution Follow these steps to change the HTTP port: In WorkPlace Pro Open the station offline. In the tree view, right-click the offline station and select Go → Properties. On the Properties sheet, click the Config tab. Edit the httpPort text box: Remove the default value 80 and enter your chosen port (e.g., 8081 ). Click Apply. Right-click the offline station and select Close. In Admin Tool Log into the UNC. Right-click the station name (not the host name) and select Edit → Properties. In the station.properties file, add the line: httpPort=[newport] Example: httpPort=8081 . From the File menu, choose Close and save changes when prompted. Reinstall the Station In Admin Tool, click the Installation tab. On the Installation Sheet, click Install Station. Select the station from step 1 and click OK. Confirm prompts and select DB format when asked. The system will load the offline database to the UNC and reboot the station. When finished, the message box will display Installation Complete. Common Mistakes Editing the wrong file: Ensure changes are made in station.properties , not host properties. Not saving changes: Always confirm saving before closing the file. Skipping reinstall: The new port will not apply until the station is reinstalled. Firewall not updated: After changing the port, update firewall rules to allow traffic on the new port.

Issue Can the Niagara R2 UNC-410 support an ASD network? Product Line TAC IA Series Environment Niagara R2 UNC-410 ASD network Cause The UNC-410 does not support ASD communications because its RS-485 ports are not electrically isolated, which is required for ASD protocol compatibility. Resolution The Niagara R2 UNC-410 cannot support ASD networks. Here are the available communication ports on the UNC-410: Ethernet: One 10/100 Mbit RJ-45 connector RS-485: One non-isolated bus (up to 76.8 Kbaud) RS-232: One RJ-45 connector LonWorks: One port – 78.8 Kbaud FTT-10A with Weidmuller connector (supports up to 27 devices) Optional Module: UNC-410-MDM Internal Auto-dial/Auto-Answer 56k modem (p/n UNC-410-MDM); RJ-11 connector for North American applications (uses RS-232 port when installed). For further details, refer to document F-27322.

Issue After manually changing all COV increments in a Niagara R2 station, the COV increment values never update. Product Line TAC IA Series Environment Niagara R2 BACnet Integration Cause The COV increment property is not fetched during a standard poll. Therefore, manual changes do not reflect automatically. Resolution To update the COV increment values: Open WorkPlace Pro. Navigate to the workspace containing the BACnet device object. Right-click the device object and select Upload All. This forces the station to refresh and retrieve updated properties, including COV increments. Verify that the new COV increment values are now displayed correctly. For more details, refer to the Niagara R2 BACnet Integration Reference Manual.

Issue No alarms are displayed in the Niagara R2 Alarm Console. Product Line TAC IA Series Environment Niagara R2 Alarm Console Niagara R2 Station Cause The Alarm Console is not properly configured with the Niagara station information. This typically occurs when the station address record is missing or incorrect. Resolution To configure the Alarm Console correctly: Open the Alarm Console From the Address menu, select Enable Edit Enter the password (default is blank). From the Address menu, select Add Address Enter the following details in the input dialog: Station Name: Name of the station node to monitor Host Address: Computer name or IP address running the station User Name: Valid user account for the station (same as WorkPlace Pro login) Password: Password for the user account Confirm Password: Re-enter password Click OK Go to the Stations tab and verify the new station address record in the Address Book. If the record appears red, restart the station to enable alarm routing to the console. Common Mistakes Incorrect IP or Host Address: Ensure the host address matches the station’s actual IP or hostname. User Permissions: The user account must have alarm viewing rights; using a restricted account will prevent alarms from appearing. Firewall Blocking: Network firewalls or security settings may block communication between the console and station. Station Not Restarted: After adding the address, failing to restart the station can prevent alarm routing. Typo in Station Name: The station name must exactly match the configured node name.

Issue A Niagara R2/G3 UNC/JACE controller reboots approximately every 15 minutes. The standard output window shows AC Power status failed, and a Battery test failed message is logged. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed backup battery Faulty battery charging fuse Low battery voltage causing repeated AC power fail shutdowns Resolution Understand Battery Test Behavior The UNC performs an automatic battery load test every 15 minutes. If voltage drops below a predefined threshold, the test logs battery test failed. A station alarm is generated only when the test result changes from the previous state. Troubleshooting Steps Check battery fuse (field-replaceable only in UNC-500/510 models). Inspect battery connections and measure voltage. If battery voltage is <12 VDC, disconnect the battery and monitor for errors or reboots. If reboots stop, replace the battery. Verify Charging Voltage After Replacement Normal charging voltage: 13–14.5 VDC with a good battery. If battery is partially discharged, voltage may read as low as 12.5 VDC initially. Firmware Note In release 2.301.522, battery test logic was improved to coordinate with AC power test, reducing repeated shutdowns caused by weak batteries.

Issue What parameters are used to regulate the speed of the LON trunk in a Niagara R2 integration? Product Line TAC IA Series Environment Niagara R2 Cause Improper configuration of LON device parameters can lead to unnecessary network traffic, especially when values change frequently or remain unchanged for extended periods. Resolution Two key parameters in LocalLonDevice Properties regulate LON traffic: maxSendTime Defines the maximum time the local LON device (UNC station) waits before sending a value that has not changed. Helps reduce redundant transmissions of static values. minSendTime Specifies the minimum time interval between network variable updates for values that change rapidly. Prevents excessive traffic from frequent updates. Reference: Consult the Niagara LonWorks Integration Guide for detailed configuration steps and best practices.

Issue What are the latest supported firmware revisions for MicroSmart controllers when using the Niagara R2 MicroSmart Driver (ibsMs)? Product Line TAC IA Series Environment ibsMs MicroSmart controllers Cause Outdated firmware on MicroSmart controllers can lead to intermittent communication issues or unexpected behavior. Ensuring controllers run validated firmware versions helps maintain compatibility and stability with the ibsMs driver. Resolution Refer to the table below for validated firmware revisions for MicroSmart controllers with the ibsMs driver. These versions were tested and confirmed to work with ibsMS-2.302.514a.v1 or later. Other versions may work but were not validated. ibsMS a Supported Controller Part Number Cntlr Type Cntlr Level Description P/N To Order Firmware P/N Revision CheckSum IC# Yes 1 ENV-III AHF L11 Anemostat Envirotrak III PROM-KIT-10 PROM-48-119 11.1X $8F1E IC12 Yes 1 ENV-III-MPC AHG L11 Anemostat Multi-Purpose Controller PROM-KIT-11 PROM-48-120 11.1X $63F1 IC11 Yes MN-MSI MIM L11 Integrator for MicroSmart Bus PROM-KIT-4 PROM-42-100 11.1T $0B48 IC20 Yes MSC-L1000 ELC L11 Lighting Controller PROM-KIT-16 PROM-48-125 11.2H $31B4 IC3 Yes MSC-MPC-001 HPA L11 Multi - Purpose Controller PROM-KIT-5 PROM-48-104 11.2H $2996 IC11 Yes MSC-P-751/752/753/754 SVA L11 Package Unit Controller PROM-KIT-7 PROM-48-106 11.2H $B762 IC3 Yes MSC-P1501/1502/1503/1504 PCB L11 Package Unit Controller (early version) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-P1501/1502/1503/1504 PCC L11 Package Unit Controller (enhanced AI) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-V-511/512/521/522 VAC L11 VAV Controller PROM-KIT-9 PROM-48-107 11.2H $7D17 IC9 Yes MSC-V-751/752/753/754 SVA L11 VAV Controller PROM-KIT-8 PROM-48-106 11.2H $B762 IC3     ELC-001 SVC L10 SiteManager Controller PROM-KIT-12 PROM-48-121 10.2 $C708 IC4 Yes 1 ENV-III-MPC AHE L10 Anemostat Multi-Purpose Controller N/A       IC11 Yes MSC-MPC EHP L10 Multi - Purpose Controller PROM-KIT-2 PROD-EHP 10.3 $0FEE IC11 Yes MSC-P1000 ELP L10 Enhanced Low PUC PROM-KIT-13 PROM-48-122 10.1 $C25B IC18 Yes MSC-P2000 EMP L10 Enhanced Medium PUC PROM-KIT-14 PROM-48-123 10.1 $AC7A IC24 Yes MSC-U1000 EUC L10 Enhanced Unit Controller PROM-KIT-3 PROD-EUC 10.4C $945F IC21 Yes MSC-V501/502 VAD L10 VAV Terminal Controller PROM-KIT-17 PROM-48-126 10.4D $345C IC9 Yes MSC-V501/502 VAB L10 VAV Terminal Controller PROM-KIT-15 PROM-48-124 10.3 $017C IC12   Yes 1 ENV-IIB (N1-1087) A2B L9 Anamostat (2) Fume Hood Controller N/A PROD-A2B 9.1 $6858 IC23 Yes 1 ENV-II(N1-1058) AHC L9 Anamostat Unit Controller PROM-KIT-1 PROD-AHC 9.1 $320F IC37 Yes MSC-GPC GPC L9 General Purpose Controller PROM-KIT-18 PROM-48-736 9.4C $4E78 IC25 Yes MSC-IOC SIO L9 Input/Output Controller PROM-KIT-21 PROM-48-739 9.4C $64A7 IC43   MSC-L-100 MLC L9 Lighting Controller PROM-KIT-25 PROM-48-743 9.1R $AA35 IC5 Yes MSC-P-100/112/120 LPC L9 Low PUC PROM-KIT-22 PROM-48-740 9.4C $C9FE IC17 Yes MSC-P-200 MPC L9 Medium PUC PROM-KIT-20 PROM-48-738 9.4C $9031 IC23 Yes MSC-T-100 STC L9 Temperature Controller PROM-KIT-23 PROM-48-741 9.4C $558E IC6 Yes MSC-UC UC L9 Unit Controller PROM-KIT-19 PROM-48-737 9.4C $FB25 IC22 Yes MSC-V-100/V110 VAV L9 VAV Terminal Unit Controller PROM-KIT-27 PROM-48-749 9.4C $45AE IC12 Yes MSC-V-200 VSD L9 VAV Terminal Unit Controller PROM-KIT-24 PROM-48-742 9.4C $5CE8 IC13   MSC-V-200E (ETI) VE1 L9 VAV Terminal Unit Controller N/A TEST VE1 9.0C $6A7E IC13 Yes MSC-V-300 VDD L9 VAV (Dual) Terminal Unit Controller N/A PROD-VDD 9.3 $7DC6 IC15 Yes MSC-V-400 MOV L9 Mobil Package Unit Controller PROM-KIT-26 PROM-48-744 9.4C $5148 IC17 a The firmware revisions listed above were validated with this driver. Other versions may function correctly but were not tested. If difficulties are experienced, upgrade firmware. 1 Controller validated with ibsMS-2.302.514a.v1 or greater.

Issue When performing backup or DB Admin operations on a Niagara R2 UNC station, the following errors may occur: java.net.ConnectException: Connection refused: connect (during Save Runtime DB / Backup) DB ADMIN COMMAND ERROR EXCEPTION; CONNECTION REFUSED (during Save Runtime DB) Cannot process DB Admin command; java.net connection refused (during DB Admin Get and other DB Admin commands) Product Line TAC IA Series Environment I/A Series R2 Cause The UNC station’s HTTP port was changed from the default (80), but the station.properties file was not updated to reflect the new port. Backup and DB Admin tools attempt to connect using the old port, resulting in connection refusal. Resolution Open Admin Tool and log into the UNC platform (not the station DB). Right-click the running station → Edit > Properties. Add or update the line in station.properties : httpPort=xxxx Replace xxxx with the station’s configured HTTP port. Save changes and restart the station. Verify by retrying the backup or DB Admin command. If error persists, confirm correct capitalization and port value. (Refer to Niagara Networking and Connectivity Guide for details.) Error Variants & Functions: Error Message Function in Use java.net.ConnectException: Connection refused: connect Save Runtime DB / Backup DB ADMIN COMMAND ERROR EXCEPTION; CONNECTION REFUSED Save Runtime DB Cannot process DB Admin command; java.net connection refused DB Admin Get / other DB Admin commands

Issue When using Change of Value (COV) with BACnet and Niagara R2, which object types should be configured for optimal performance? Product Line TAC IA Series Environment BACnet Niagara R2 Cause Incorrect selection of BACnet object types for COV can lead to unnecessary polling, increased network traffic, and reduced efficiency. Resolution Follow these guidelines from the Niagara R2 BACnet Integration Manual: Best Candidates for COV: Objects that change infrequently: Binary Input (BI) Binary Value (BV) Multistate Input (MSI) Multistate Value (MSV) Analog objects can also use COV: Analog Input (AI) Analog Value (AV) Tip: Increase covIncrement to reduce notifications (only changes larger than this value will trigger updates). Poor Candidates for COV: Output-type objects and priority-based value objects: Analog Output (AO) Binary Output (BO) Multistate Output (MSO) AVP, BVP, MSVP These remain in the poll queue because priorityArray cannot be updated via SubscribeCOV. Configuring them for COV will not significantly reduce traffic. Recommendation: Use COV primarily for input and non-priority value objects. Avoid configuring output-type objects unless the device supports many COV subscriptions and all suitable input objects are already subscribed.

Issue How can an override of the nciMinFlow SNVT be performed directly from a container in Niagara R2 WorkPlace Pro? Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro Cause A direct override of a network configuration input (nci) is not possible in Niagara R2. Resolution To change the nciMinFlow value: Copy and paste the DynamicCmd object from: Local Library\tridiumx\lonworks\conversion into the Workspace. Link the nciMinFlow property on the VAV shadow object to the Link property on the DynamicCmd object. In the Config tab of DynamicCmd properties, set floatConversion as: 1st dropdown: Volumetric Flow 2nd dropdown: liters_per_second 3rd dropdown: cubic_feet_per_minute In the Visual tab, type MinFlow in the float box and apply changes. Switch to Monitor mode, right-click the DynamicCmd object, select MinFlow, and enter the desired value in CFM. The nciMinFlow SNVT in the VAV controller will update accordingly.

Issue Creating a link from an Enterprise Server station to a UNC station in Niagara R2 WorkPlace Pro takes approximately three minutes. Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro Enterprise Server UNC station Cause When creating a link, the Enterprise Server attempts to connect to all devices listed in its address book. If the address book contains offline or non-existent UNC devices, this results in significant latency. Resolution Before creating links: Remove all offline or unused address book entries from the Enterprise Server station. Ensure only active UNC devices are listed in the address book. This minimizes connection attempts to unreachable devices and reduces link creation time.

Issue When BACnet devices are learned as lite objects in I/A Series R2, properties such as covIncrement are not available at the UNC. This limits the ability to configure or adjust Change of Value (COV) notifications without editing the controller application. Product Line TAC IA Series Environment I/A Series R2 (Niagara)  Cause The “Use lite objects” option in BACnet Utilities creates simplified BACnet objects without certain properties (e.g., covIncrement ). These properties are essential for fine-tuning COV behavior. If lite objects are used, changes must be made in WorkPlace Tech and downloaded to the controller. Resolution To learn BACnet devices as full objects and enable access to covIncrement : Navigate to BACnet Service → BACnet Utilities. When performing LearnDevice or LearnNetwork, click Execute. In the pop-up window, uncheck Use lite objects. Click OK to proceed. The system will learn full BACnet objects, exposing properties like covIncrement for configuration at the UNC. Additional Notes Full objects provide complete BACnet property sets, improving flexibility for diagnostics and tuning. Lite objects are suitable for simple integrations but restrict advanced property access.

Issue Can an alarm be generated if a Niagara R2 Enterprise Server loses connectivity to the Vykon Alarm Service (VAS)? Product Line TAC IA Series Environment Niagara R2 VAS client Cause The system does not automatically generate an alarm when the VAS connection changes state. A custom logic is required to monitor the VAS client activity. Resolution To alarm on VAS connectivity status: Create a Program Object in WorkPlace Pro and use the following logic: //////////////////////////////////////////////////////////////// // VAS Active clients // This object monitors the number of active VAS clients. // Revision History: // 07 August, 2007 ////////////////////////////////////////////////////////////////// // Inputs // flex input int ActiveClients // // Outputs // output FloatStatusType Clients // Processing Clients.value = ActiveClients Link the clientActive property of the VykonAlarmService to the ActiveClients property of the program object Create a comparison object, and link the output of the program object to Input A of the comparison object In the comparison object, configure the function so that A < B, and set defaultB to 1 Create a BI object, and link the status out of the comparison object to the status in of the BI Configure the alarm properties of the BI

Issue What is the best way to transfer data from a Niagara UNC/ENC station to all MicroSmart controllers connected via RS-485? Product Line TAC IA Series Environment Niagara R2 Niagara G3 MicroSmart controllers (versions 10 & 11) Cause Need to share data efficiently between a UNC station and multiple MicroSmart controllers on the RS-485 bus. Resolution Use the MSGlobalDataOut object in the Niagara station to transmit data onto the MicroSmart RS-485 bus using a global broadcast channel. In each MicroSmart controller, program a point to access data from the specific global channel number. Firmware requirements: Only controllers with firmware revision 10 & 11 support global broadcast channels. Controller capacity: MSC-MPC (64 points): Can receive data on all 122 global channels. MSC-P1500 series (48 points): Limited to global channels 1–24. Refer to: MicroSmart Driver Engineering Guide (F-27327) for MSGlobalDataOut details. DMS Operator Interface User’s Guide (F-25467) for MicroSmart Global Broadcasting.

Issue How to start a Niagara R2 station using the Windows command prompt instead of the Admin Tool. Product Line TAC IA Series Environment Niagara R2 Cause Users may need an alternative method to start a Niagara R2 station, especially when the Admin Tool is unavailable or not preferred. Resolution Add the Niagara bin folder to the system PATH or navigate to the folder manually. Example folder: C:\Niagara\r2.xxxx\nre\bin Run the following command in the command prompt: station <StationName> Example: station Lon522 Notes: The command window can be minimized, but closing it will stop the station. When started this way, the station will not display as “running” in the Admin Tool. Optional: Create a batch file for convenience: cd C:\Niagara\r2.xxxx\nre\bin station Lon522    

Issue When configuring a Niagara R2 UNC with a DNS server, users need to identify the correct node name or computer name for the UNC on a Microsoft network. Product Line TAC IA Series Environment Niagara R2 Cause The end customer requires the UNC to be identifiable on the Microsoft network using a specific node name for DNS resolution. Resolution The Computer Name displayed on the Network Settings tab in the Niagara Admin Tool is used as the node name on the Microsoft network. This name is modifiable within the Admin Tool. Ensure the chosen name complies with Microsoft naming conventions for DNS and network identification.

Issue WorkPlace Pro fails to run or connect to a station due to local security restrictions on the computer. Product Line TAC IA Series Environment Niagara R2 Workplace Pro Cause Firewall or security software may block port 3011, and Local Security Policy settings can prevent network access to the local computer (localhost). Key problematic settings: Access this computer from the network missing the Administrators group. Deny access to this computer from the network includes the user or their security groups. Resolution Confirm port 3011 is open in the internal firewall. If WorkPlace Pro still fails: Open Local Security Policy under Administrative Tools in Windows Control Panel. Navigate to Local Policies → User Rights Assignment. Configure these policies: Access this computer from the network → Ensure Administrators group is listed. Deny access to this computer from the network → Ensure the user and their security groups are not listed. After changes, log off and log back in to apply the updated policies.