Issue The network interface card (NIC) on a desktop or laptop shows no link LED activity, indicating no network connection. Product Line Andover Continuum, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Devices with built-in or external NICs (Network Interface Cards) Cause The NIC may have power management features enabled. These features can automatically disable the NIC under the following conditions: No network activity is detected Battery power is low Battery connection is intermittent This behavior is designed to conserve power but can result in the NIC appearing inactive or disconnected. Resolution To resolve this issue, disable the NIC's power management settings: Open Device Manager. Expand the Network Adapters section. Right-click your NIC and select Properties. Go to the Power Management tab. Uncheck the box that says “Allow the computer to turn off this device to save power.” Click OK to apply the changes. Additional Notes This issue is commonly observed on laptops running on battery power. Disabling power management may slightly reduce battery life but ensures consistent network connectivity.

Issue What is the difference between XIF and NXE files in LON controllers? Product Line TAC Vista, TAC I/A Environment LNS LON Controllers NL220 LonMaker Cause Users working with LON devices may encounter both XIF and NXE files and be unsure of their respective roles and how to use them effectively. Resolution XIF File (External Interface File) Format: Text-based Purpose: Describes the network interface of a LON device Contents: Device type Network variables (NVs) Configuration properties (CPs) Functional blocks Usage: Used by network management tools during device integration Created by: Device manufacturer or LON development tools Editable: Yes (with caution) Use Case: Used during integration to map and understand the device’s capabilities. NXE File (Neuron Executable File) Format: Binary Purpose: Contains the firmware and application logic for a LON device Usage: Used to download or update the device’s application Created by: Development tools like NodeBuilder or LonBuilder Editable: No (compiled code) Use Case: Used when deploying or updating the logic on a LON controller. Comparison Table Feature XIF File NXE File Format Text-based Binary Purpose Describes device interface Contains executable application Usage Integration and configuration Firmware/application deployment Editable Yes (with caution) No (compiled code) Created By Manufacturer or tools NodeBuilder, LonBuilder Best Practices Ensure the XIF file version matches the corresponding NXE file to avoid integration issues. Avoid manual editing of XIF files unless necessary and fully understood. Maintain version control for both file types to ensure traceability and consistency.

Issue Routers or devices with routing capabilities may not support BACnet Protocol 16 Extended Frames (1474 bytes) and only support BACnet MSTP Frame size (480 bytes), so devices that support the larger size need to receive a request with a smaller APDU defined or they will use the largest APDU they support, which will be dropped at the router. Each BACnet device has a Max APDU Length Accepted property and SpaceLogic/Easylogic, which supports Extended Frames, is 1474 bytes. Product Line TAC IA Series Environment MP-X under Tridium offer SE branded Tridium offer I/A Series MNB 1000 Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic MP-C Building Operation EasyLogic RP IO Expansion Module Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause Routers and devices, acting as routers, that support BACnet Protocol Revision lower than 16 will drop the extended frames (aka large packets). BACnet Protocol 16 introduced Extended Frames (1474 bytes) to BACnet MSTP, which increased the frame size from 480 bytes. BACnet devices have Max APDU Length Accepted, which communicates the largest frame size accepted. SpaceLogic/Easylogic have Max APDU Length Accepted =  1474 bytes. Resolution Add bacnetUtil-rt module to the station, which is included in default Niagara installation, using Platform -> Software Manager. Open Palette -> bacnetUtil Select ApduSizeOverride from DeviceOverrides folder Drag-n-drop it on the BACnet controller The default is 480 for BACnet MSTP. To disable for SpaceLogic/EasyLogic controllers communicating via IP or on MSTP supporting Extended Frames, you can change to 1474 to match the CONFIG -> Device Object -> Max APDU Length Accepted.  NOTE A: This can be added to any device, so changing to 480 will indicate how much slower communication would be if using an MSTP router that does not support Extended Frames. I tried by viewing Device Report in N4.14 while capturing in Wireshark, so I could see packet timing on the wire, and it was about 3 times slower. ApduSizeOverride # of Request Required Period 480 46 17.13 secs 1474 14 6.76 secs

Issue Startup programs can slow down system boot time and cause application conflicts if loaded in the wrong order. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows XP, Vista, 7, 8, 8.1, 10, 11 Cause Applications configured to launch at startup may: Increase boot time Cause system instability or delays Load in an incorrect sequence, affecting performance Resolution Windows XP, Vista, 7 Click Start → Run Type msconfig and press Enter Go to the Startup tab Uncheck items you want to disable Click Apply → OK Restart your computer 🔹 Windows 8, 8.1, 10, 11 Press Ctrl + Shift + Esc to open Task Manager Click the Startup tab Right-click any item and choose Disable Restart your computer for changes to take effect 💡 Tip: Only disable items you recognize. Disabling essential services may affect system functionality. Additional Notes Disabling startup items is useful for troubleshooting slow boot times or software conflicts. For persistent issues, consider using tools like Autoruns from Microsoft Sysinternals for deeper analysis.

Issue Understanding whether a building automation product is certified by the BACnet Testing Laboratories (BTL) is crucial for ensuring interoperability, reliability, and compliance with industry standards. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment Schneider Electric Building Management Systems BACnet-compliant devices Cause In the world of building automation, interoperability and reliability are paramount. That’s why many professionals rely on products certified by the BACnet Testing Laboratories (BTL)—a globally recognized authority that ensures BACnet-compliant devices meet rigorous standards for functionality and interoperability. Resolution What Is BTL Certification? BTL Certification is a formal recognition that a product has passed independent testing based on the BACnet standard. Administered by BACnet International, the certification process involves: Testing by a Recognized BACnet Testing Organization (RBTO) Verification against the industry-standard BACnet test package Issuance of a Certificate of Conformance Inclusion in the BTL Listing of Tested Products database Certified products display the BTL Mark, a symbol of quality and assurance that the device will integrate smoothly into BACnet-based systems. How to Verify BTL Certification To determine if a product is BTL certified: Visit the BTL Listing Database Navigate to the BTL Listing of Tested Products and search by: Manufacturer Product name Product category Look for the BTL Mark Certified products typically display the BTL logo on: Packaging Datasheets Product casing Review the Product’s PICS Document The Protocol Implementation Conformance Statement (PICS) outlines supported BACnet features and is available in the BTL listing. Schneider Electric and BTL Certification Schneider Electric is a leading provider of BMS solutions, and many of its products are BTL certified. These include: EcoStruxure Building Operation Servers (AS-B, AS-P, ES) SpaceLogic Controllers (MP-C, MP-V, RP-C series) Smart Field UC Controllers Andover Continuum Controllers These products support native BACnet communication and are designed for seamless integration into smart building environments. For example, the SpaceLogic AS-B server is a BTL-listed BACnet device that supports BACnet/SC, Modbus, MQTT, and other protocols, making it a versatile choice for modern BMS applications. https://ecostruxure-building-help.se.com/bms/topics/show.castle?id=10930&locale=en-US&productversion=7.0&a=1 Why BTL Certification Matters Using BTL-certified products offers several benefits: Reduced Integration Costs: Certified devices are more likely to work together without custom programming. Lower Risk: Independent testing ensures reliability and minimizes project delays. Future-Proofing: Certified products provide a solid foundation for system upgrades and expansions. Conclusion BTL certification is a key indicator of quality and interoperability in BACnet-based building automation systems. Whether you're specifying products for a new project or upgrading an existing system, checking for BTL certification—especially for trusted brands like Schneider Electric—ensures smoother integration, better performance, and long-term reliability.

Issue How is a subnet defined, and what role does it play in IP networking? Product Line EcoStruxure Access Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, TAC I/NET Environment This explanation is based on principles outlined in TCP/IP Network Administration by Craig Hunt, published by O’Reilly & Associates, Inc Cause Subnetting is a method used to divide a larger IP network into smaller, more manageable segments called subnets. This segmentation helps optimize IP address usage, improve routing efficiency, and enhance network security and organization. Resolution What Is a Subnet? A subnet (short for subnetwork) is a logical subdivision of an IP network. It is defined by applying a subnet mask to an IP address, which determines how the address is split into: Network portion – identifies the specific network. Host portion – identifies individual devices (hosts) within that network. How Subnet Masks Work A subnet mask is a 32-bit binary pattern that accompanies an IP address. It uses binary values to indicate which part of the IP address refers to the network and which part refers to the host: A bit set to 1 in the subnet mask means the corresponding bit in the IP address is part of the network. A bit set to 0 means the corresponding bit is part of the host. Example IP Address: 192.168.1.10 Subnet Mask: 255.255.255.0 (binary: 11111111.11111111.11111111.00000000 ) CIDR Notation: /24 This means: Network Address: 192.168.1.0 Broadcast Address: 192.168.1.255 Usable Host Range: 192.168.1.1 to 192.168.1.254 CIDR Notation Modern networks often use CIDR (Classless Inter-Domain Routing) notation to define subnets. CIDR expresses the subnet mask as a suffix (e.g., /24 ), indicating the number of bits used for the network portion. Common CIDR Blocks CIDR  Subnet Mask Hosts per Subnet /30 255.255.255.252 2 usable hosts /24 255.255.255.0 254 usable hosts /16 255.255.0.0 65,534 usable hosts Additional Notes Subnets are local constructs: They are meaningful within the internal network and typically not visible to external networks unless explicitly routed. Subnetting supports hierarchical addressing, which simplifies routing tables and improves scalability. Proper subnetting is essential for network performance, security segmentation, and efficient IP address management.

Issue The factory uses the number of field failure returns to evaluate product quality.  The analysis of returned product has the potential to produce extensive information about how the product is performing and also reveal areas for improvement. Environment All controllers in following product lines:  MNB, MNL, Niagara, Network 8000, Micronet 2000. Cause Lately, many of the returned controllers, after factory-testing, have resulted in "no fault found", and a high percentage of these controllers have little to no explanation of the failure witnessed in the field. This makes it difficult to investigate the returned product further. Resolution Include the following information with all controller returns: A detailed description of the reason for return The name of the site from where the controller was removed The name and contact information of the field technician who determined the unit was defective The field technician will only be contacted if absolutely necessary. Write the above information on a "returned goods" identification tag (part number F-24802) and attach a tag to each returned controller.  The tags are available via the Publication Zone through iPortal at no charge. For more information on returning product to the factory, review the following technical product advisories: TPA-PSSG-09-0003.00  Return Process Improvement TPA-RKFD-10-0005.00  Return Process Improvements

Issue Where can I find documentation on the JACE-600 or JACE-700 controllers?  Product announcement did not include the documentation or any location references. Environment JACE-600 JACE-700 Cause Product documentation was being finalized at time of announcement. Resolution The documentation for the JAC-600, JACE-700 and all accessories for them are available in the documentation set included with the latest release of the I/A Series G3 software.  This software and included documentation is available by downloading "Release 3.6.31 Files" on The Exchange Download Center. As of the date of writing, both the "TAC_IA_Series_ENC_SW-3.6.31.7.zip" and "TAC_IA_Series_ENS-3.6.31.7.zip" include the documentation in Mounting and Wiring section of index tree.

Issue Upgraded to I/A Series G3 version 3.6.305 and now unable to successfully commission an MNL-800 controller.  Previous versions of G3 commission the same controller without issue. Environment I/A Series G3 LonWorks module version 3.6.305 Cause Issue with how the LonWorks module commissions a host-based controller. Resolution Upgrade the LonWorks module used by the I/A Series G3 station. The LonWorks 3.6.406 module can be downloaded from The Exchange Download Center.

Issue Unable to connect to a G3 ENC or JACE after attempting to downgrade or install a station. One of several different errors may be displayed in the serial shell console output.  The following are examples: Could not find library libcpp.so.3 Could not find library libcpp.so.4 Error occurred during initialization of VM - Java/Lang/ No Class Def found error: Java/Lang/object Product Line TAC I/A Series Environment I/A Series G3 ENC and JACE (all revisions), ENC-410, ENC-520, TRD-T-645, TRD-T-603, TRD-RB-645, TRD-RB-603, TRD-J-600E, TRD-T-700 Cause The issue is caused by downgrading the ENC / JACE without following the procedure to first install the clean distribution file. In addition, the ENC/JACE will fail if a station is copied into the ENC/JACE without first installing the OS and NRE software using the Workbench Commissioning Wizard. Note: With G3 release 3.3 and newer, the procedure for downgrading an ENC/JACE is included in the Niagara AX Platform Guide - Downgrading a JACE (Clean Dist). Resolution Tools needed: Null Modem Cable Serial Terminal (e.g. HyperTerminal or TeraTerm) Jumper Obtaining the files required to recover the ENC NOTE: If recovery of a Jace-700 is required, please contact Product Support for the recovery file. Download the appropriate OS image and gz file zip file for the ENC/JACE from the Exchange website - https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp ENC-410.zip ENC-410-1 standard memory - etfs512 ENC-410-EM.zip ENC-410-1 extended memory - etfs2048 ENC-520.zip ENC-520-2 standard memory - etfs512 ENC-520-EM.zip ENC-520-2 extended memory - etfs2048 NPM6E.zip JACE603/645, TRD-RB-603/645, JACE600E Note: The files used in the following procedure MUST correctly match the ENC/JACE hardware platform, otherwise permanent damage to the unit may occur. The serial shell can be used to determine the file system requirements (standard or extended memory). To find the exact image needed for an ENC (JACE 2/4/5) execute the following while connected to the unit with serial shell: Log into the unit's menu system using the platform username and password. Type sh to exit the menu system and enter the shell mode. At the # prompt, (type: cat sys/info/fs) and enter This will return the file system type of etfs512 or etfs2048. Extract the OS image and gz files from the downloaded zip to a suitable directory on the local computer (e.g. local hard drive such as: c:\temp). Enable ftp: By default, the ftp port is disabled on every ENC/JACE as shipped from the factory.  Enable the ftp as follows. Set the jumper on the ENC to serial shell mode and connect the null modem cable between the PC and the ENC/JACE. Connect to the ENC using the Serial Terminal program and the following port settings: Baud rate 57600 bps (Note: JACE-603/645 baud rate is 115200) 8 data bits, 1 stop bit, no parity After logging in to the menu system from the serial shell, do the following to enable ftp: Select option 4 from the menu Enter the port number (Normally 21). (type: 21) Press the Enter key to confirm the change Note: Leave the serial shell connection open while performing the next steps. FTP the OS image and gz files On the local system, open a command prompt window and change the directory to the location where the OS image and gz files were extracted (c:\temp). Connect to the ENC via ftp and put the OS image in the /tmp directory entering the following from the command line: Create a ftp connection to the ENC by typing: ftp and enter Type the username and password for the platform when prompted Change directory to /tmp (type: cd tmp) and enter Change to binary mode (type: bin) and enter Download the image to the ENC by using the put command. The image name must exactly match the image extracted from the downloaded zip file. ENC-410-1 standard memory (type: put york-etfs512.image) and enter ENC-410-1 extended memory (type: put york-etfs2048.image) and enter ENC-520-1 standard memory (type: put james-etfs512.image) and enter ENC-520-1 extended memory (type: put james-etfs2048.image) and enter JACE-600E, 603, 645 extended memory (type: put npm6xx-etfs2048.image) and enter Download the gz file to the ENC by using the put command. The name must exactly match the image extracted from the downloaded zip file. Change directory to the root (type: cd ../..) and enter Change directory to /ffs0/zip (type: cd ffs0/zip) and enter Download the gz file (type: put clean.tar.gz) and enter Exit ftp (type: quit) and enter Execute OS image update Return to the serial shell connection Type sh to exit the menu system and enter the shell mode At the # prompt, type: osupdate and enter After a short delay the # prompt will return. Shutdown to reboot the ENC (type: shutdown) and press enter. The ENC/JACE will reboot, install the clean distribution image and perform one additional reboot automatically. The ENC/JACE should now be recovered and allow connection to the platform. Connect and use the Workbench Commissioning Wizard to install the version of G3 required.

Issue Unable to commission an I/A Series JACE-6 or JACE-7. The commissioning wizard cannot locate the sun-jre-qnx-ppc distribution file required for the installation process. Environment I/A Series G3, JACE-6, JACE-7 Cause The sun-jre-qnx-ppc distribution file was not included in the initial TAC release of build 3.6.31.6.  in addition, the Sun Hotspot Virtual Machine (JVM) for the QNX operating system included with the 3.6.31.6 build was found to have timing issues. Review TPA-IA-11-0005.00 for more details. Resolution The initial TAC release of build 3.6.31.6 was removed for download within a few days of original release.  The software was replaced by TAC build 3.6.31.7 (dated 09/29/2011). For those using I/A Series G3 Release 3.6 you must take the following actions: Discontinue using G3 release build 3.6.31.6.   Download and install the latest build, G3 release 3.6.31.7 from The Exchange Download Center.   For those instances where deployment has already occurred in the following JACE platforms JACE-6 or JACE-7, an upgrade to G3 3.6.31.7 is required. Note: The version of the Sun Hotspot JVM can be verified using the Workbench Platform tool – Platform Administration. The Java Virtual Machine (sun-jre-qnx-ppc) should indicate Sun Microsystems Inc 1.5.0.16.21 or higher.   The Enterprise Network Server, ENC-410, ENC-520, and JACE-2 platforms do not utilize the Sun Hotspot Java Virtual Machine (JVM) for QNX.  These platforms are not affected by the issue. However, it is strongly recommended to upgrade to G3 3.6.31.7 to maintain compatibility with the same version of Workbench and associated files.

Issue Need the UL Listings for Xenta Product Line Product Line TAC IA Series, TAC INET, TAC Vista Environment Xenta Cause UL Listings for Xenta Product Line Resolution Go to Exchange Online and log in Search for "TAC Vista UL Listings" (Example, Click Here) You can find more information in Xenta Hardware UL 864 Listing.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue SmartStruxure with I/A Series Micronet BACnet (MNB) controllers Environment SmartStruxure version 1.4 and earlier I/A Series Micronet BACnet (MNB) controllers Cause Need to know if it is possible to use MNB controllers with SmartStruxure.  Resolution I/A Series MNB controllers can be integrated into SmartStruxure as 3rd party BACnet devices. For more information on SmartStruxure with MNB controllers, download document MNB BACnet Support within a StruxureWare Building Operation System Solution Guide.

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue A Network 8000 LNC-100 cannot communicate to LON devices under it even though all the devices can be accessed with WorkPlace Tech or a LON commissioning tool. Product Line TAC IA Series Environment NETWORK 8000 LNC-100 LON devices WorkPlace Tech Cause If the LON network is known to be good and otherwise functioning, this issue indicates a problem with the LON interface in the LNC-100. This is typically caused by accidentally attempting to commission the LNC-100 using LonMaker or other LON commissioning tool. Attempting to commission the LNC-100 will result in its LON interface being set into a network state called HARD - OFFLINE. Resolution The condition can be corrected using the Echelon NODEUTIL program to set the interface network to the required CONFIGURED - ONLINE state. NodeUtil can be downloaded from The Exchange Download Center. After downloading NodeUtil to your computer, open a command prompt window and launch NodeUtil in that window.  After launching NodeUtil, perform the following steps to correct the problem. Press the F key to execute the Find function.  This will browse the connected LON network for all attached LON devices.  In the list of found devices, the LNC-100 will be identified with the program id "C 1 11.0A". Press the G key to execute the Go To Device function.  Enter the device number of the LNC-100 (program ID "C 1 11.0A") as displayed in the list of discovered devices.  The device menu will then be displayed. Press the S key to display the status of the device.  Typically 17 lines of status information are displayed followed by the "Device Status" menu.  Press Y to clear the error status.  The "Device State" line will usually show a state of either Configured, Off-line or Hard, Off-line. Press the  M key to change the device mode and state. After selecting the M command, the list of mode options is displayed.   Press the S key to select the State menu. The list of State options will be displayed.  Press the C key to set the device to the Configured state. A status message will be displayed followed by the DEVICE prompt. Press the M key again to display the Mode options then press N to set the device into the OnLine mode. A status message will be displayed followed by the DEVICE prompt. Press the S key again and verify that the Device State is now Configured, On-line. Press the D key to display the domain address table of the LNC-100.  One or two lines of device domain address information will display.  If two domain addresses were defined in the SYS: SIM block of the device, two lines of information will display, otherwise only one line will display.  Verify that the address information (Subnet, Node and Domain ID) are as set in the SYS: SIM block. The data entered for Domain0, Subnet0 and Node0 will be displayed on the Index 0 line. The data entered for Domain1, Subnet1 and Node1 will be displayed on the Index 1 line. Press the E key to exit the Device level and press the E key a second time to exit the program.

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue I/A Series G3 version 3.8 and N4 version 4.2 Weather Service not following redirects Product Line TAC IA Series Environment I/A Series G3 3.8.x I/A Series N4 version 4.2 or older  Cause The National Weather Service (NWS) started recently redirecting from an HTTPS to an HTTP connection. Current conditions are not updated in Weather Service. The following messages appear in station output:  TRACE [15:05:30 27-Feb-18 EST][weather] Redirect to https://www.weather.gov/xml/current_obs/KBIV.xml WARNING [15:05:30 27-Feb-18 EST] [weather] Updating current conditions failed for WeatherReport javax.baja.sys.BajaException: Unable to get NWS Current Conditions feed at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:71) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) ... 12 more java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Note: The issue does not occur in I/A Series N4 version 4.3 or higher. Resolution For I/A Series G3 version 3.8 and newer, patched weather.jar modules resolve this issue. The weather module patches are available for download from the Schneider Electric Exchange as:  weather 3.8.311.1 - G3 Firmware weather 3.8.213.3 - G3 Firmware weather 3.8.112.1 - G3 Firmware weather 3.8.41.3 - G3 Firmware    To resolve the issue in Niagara 4.2 and/or versions of G3 not covered by the patches, Clear the hidden flag on the conditionsServer slot of the weather provider and change the value to w1.weather.gov.  After making this change, the current conditions will update.  The conditionsServer slot for each weather report will need to be modified if more than one is being used.  The following is a screenshot of the provider slot sheet. The Conditions Server slot is highlighted. Select Config Flags.   Config Flags dialog. Uncheck the Hidden flag and save.   View the Property Sheet for the provider and modify the Conditions Server to be w1.weather.gov

Issue I/A Series G3 schedule times can only be adjusted in half hour increments? Environment I/A Series G3 versions 3.3.22, 3.4.51, and 3.5.25 Cause Schedule module and associated user interface is not correctly processing the time setting causing the time to round to the nearest half hour increment. Resolution Note: It is recommended to upgrade to the latest maintenance build for the I/A Series G3 version being used. If this is not possible, updated schedule modules are available for download from https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp website.  

Issue Some schedules stop operating correctly after Daylight Savings Time (DST) changeover.  Environment I/A Series G3, all ENS and ENC with builds 3.5.4, 3.4.53.1, 3.3.31.2, 3.2.23.1 or earlier. Cause Any station with a schedule, of any type, with an event set to occur during the "advanced" (missing) hour between 2:00 AM and 3:00 AM on the DST changeover day. The resulting miscalculation of the schedule's "Next Time" or "Next Trigger" time could cause that schedule, or even other schedules in the station, to stop working. This typically affects downstream logic in the station. In some cases it was observed that the CPU usage on an ENC went up to 100% while calculating invalid next event times. Examples A station contains a BooleanSchedule with events at 12:00 AM and then again at 2:05 AM daily. At 12 AM the schedule executes normally and attempts to calculate the next event time. On the second Sunday in March the next event time calculates to a time that does not exist due to the DST change. This causes the Java thread that executes all schedules in the station to become tied up attempting to recalculate the time. A station contains a TriggerSchedule that periodically repeats every 15 minutes, with a range passing through the DST changeover time. On the second Sunday in March the next trigger time calculates to a time that does not exist (say, 2:15 AM). Again, this causes the Java thread that executes all schedules to become tied up attempting to recalculate. Resolution The solution to this issue is to upgrade the schedule.jar file in the platform to one of the versions below, or later. Files are available from The Exchange Extranet.  Release 3.3.31.2 (Download and extract schedule-3.3.34.1) If you are using a build that is higher than the above versions then you will not be affected by this issue.