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.

Issue ENC is licensed for GCM but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacgcm" when attempting to access the GCM Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses   Tridium.license (Tridium 3.5 - never expires)   TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates   Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)  TAC.license (Tridium 3.6 - never expires)Certificates Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.  If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center website.  Navigate to the I/A Series G3 (ENS, ENC, etc.) Conference > SE Proprietary Drivers.  Use Workbench to import the downloaded file.

Issue Unable to key in a 'plus' sign (+) in the SMS recipient's Phone Numbers field Environment I/A Series G3 Cause The SMS recipient's phone numbers is required to be entered in international format. The international phone numbers format for sending an SMS is different for different countries. Example (using United Kingdom country code '44'): 00441403740290 or +441403740290 The following I/A Series G3 versions do not allow the 'plus' sign (+) to be entered in the SMS recipient's Phone Numbers field. I/A Series G3 version 3.4 and below I/A Series G3 3.5 versions lower than 3.5.36 I/A Series G3 3.6 versions lower than 3.6.36 Resolution Starting in build 3.5.36, 3.6.36, and 3.7 or later, a phone number may contain a ‘plus’ sign, for example: +441403740290. If you are running I/A Series G3 version 3.4 or below, you can download the updated SMS module here. If you are running a version of I/A Series G3 version 3.5 that is below version 3.5.36, upgrade to the latest version of 3.5 which is 3.5.39. If you are running a version of I/A Series G3 version 3.6 that is below version 3.6.36, upgrade to the latest version of 3.6 which is 3.6.31. These can be downloaded from https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp.

Issue Where can I find the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets? Product Line TAC IA Series Environment WorkPlace Tech Tool software I/A Series MNB BACnet family of controllers I/A Series MNL LON family of controllers Cause There is no single online source for the all the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets. Resolution All documentation related to the WorkPlace Tech Tool (WPT, WPCT & WPFB) and related controller documents are installed to your computer when you install the WorkPlace Tech Tool software. At the time of release, the current version of each software manual, hardware installation manual (LON & BACnet), specification data sheet (LON, BACnet & Software) and the software release notes document is built into the software installation program. These documents are all accessible under the \WorkPlace Tech\Help folder on any computer where the WorkPlace Tech Tool software is installed. All documentation can be displayed from the list displayed by the WorkPlace Tech Help menu. This was done to insure that all WorkPlace Tech Tool users would have access to the version of all documents related to that specific release of the software. Since these documents are included in the installation package for any version of the WorkPlace Tech Tool software, you can download the latest WorkPlace Tech Tool installation file from The Exchange Download Center to get the complete set of documents. These documents are also available individually from the 'Publication Zone', accessible from the 'Links' menu on iPortal (https://iportal2.schneider-electric.com).

Issue Where are the DUI expander objects for the MNB-300 and MNB-1000 controllers in Workplace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech version 5.1 through 5.9.4 I/A Series WorkPlace Tech version 5.10.0 till current Cause The standard stencils do not include an object for Momentary SS or a DUI multiplexer.  Resolution The I/A Series BACnet controllers do not currently support the DUI object directly within the MNB-300 or MNB-1000. An application performing the same basic function was created and factory tested. This application was created as a custom object named "DUI_App". For support of these objects in Workplace Tech 5.1 until 5.9.4, log into The Exchange Download Center and download the file Application Objects_rev1.zip. There is also a detailed DUI_Application_Documentation_rev1.pdf that describes the operation of the "DUI_App". For support of these objects in Workplace Tech 5.10.0 until further notice, log into The Exchange Download Center and download the file Application Objects_rev2.zip. There is also a detailed DUI_Application_Documentation_rev2.pdf that describes the operation of the "DUI_App". Note: VAV box controllers do not have DUI expander objects available. See TB06-02 for additional details.

Issue Cannot interface to the GE Lighting Control Panel PSLP Object nviPattern and nvoPatternFb with G3 lonGe-3.8.37.  Network variables nviPattern, nvoPatternFb, and nciChannelCfg are missing from the proxy points within the object definition. Environment I/A Series G3 - 3.8.37 Cause Network variables nviPattern, nvoPatternFb, and nciChannelCfg are based upon manufacturer types (GEPatternType and GEChType) and are not properly defined in the lonGe 3.8.37 module. The pslp object within the lonGe module generates warnings when added. WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nviPattern WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nvoPatternFb WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_0 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_1 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_2 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_3 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_4 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_5 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_6 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_7 Resolution Upgrade to lonGe-3.8.38.1.   The updated module is available for download from the Schneider Electric Download Center. https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp

Issue Can I install the Java7u25 patches in 3.5.25? Environment I/A Series G3 with multiple browsers Cause JAVA 7u25 prevents the Java applet from loading Resolution You must be at a level specified in the TPA before applying these patches.  See TPA-IA-13-0007.01 Java 7 Update 25 May Cause I/A Series G3 Niagara Applet to Fail.

Issue COV subscription links are being lost between MNB controllers Product Line TAC IA Series Environment MNB Controller Cause This is caused specifically by changing certain required link properties or by removing the objects that contain the link data. Resolution See TPA-RKFD-08-0001.00 "Avoid accidentally removing COV subscriptions (links) between MNB controllers" on The Exchange Download Center.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

Issue Alarm DB View Filter only works for timestamp. Other filter properties do not work. Below is an example of filtering the Source to find any alarms with the '1' in the source name. However, the results still include alarm with source names that do not contain '1'.  Environment I/A Series G3 version 3.5 and 3.6 Cause This is a known issue in the above versions of I/A Series G3. Resolution This issue is fixed in I/A Series G3 version 3.7.10 and above. Schneider Electric has released I/A Series 3.7.46 and 3.7.106 and they are available for download from The Exchange Download Center. It is recommended that you use the latest release version which is 3.7.106 as it includes many fixes for other issues. 

Issue A newly installed program may fail to launch because it attempts to use a network port that is already in use by another application or service. How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum Environment Microsoft Windows Cause The program is trying to bind to a port that is already occupied by another process. Resolution   Open Command Prompt as Administrator Press Win + X → Select Command Prompt (Admin) or Windows Terminal (Admin). Run the following commands: View all active TCP connections with associated executables: netstat -a -n -p tcp -b​ Displays protocol, local/remote addresses, connection state, and the executable using the port. View active TCP connections with Process IDs (PID): netstat -a -n -p tcp -o  Use Task Manager to match the PID to the corresponding application. Check a specific port (e.g., port 80): netstat -a -n -p tcp -o | findstr :80 Filters output to show only entries using port 80.   Additional Tips Use Resource Monitor ( resmon ) for a graphical view of network activity. Consider using third-party tools like TCPView from Sysinternals for easier port monitoring.

Issue how to set a static IP address to a Windows Client to ensure consistent network communication, especially for services like file sharing, port forwarding, or hosting. Product Line EcoStruxture Building Operation Environment Windows 10 Windows 11 Windows Server 2016, 2019, 2022 Cause Why use a static IP? Prevent IP address changes that disrupt services Enable reliable access to networked devices Support port forwarding and firewall rules Simplify network management in server environments Resolution For Windows 10 & Windows 11 Method 1: Using Settings App Open Settings → Network & Internet Select Wi-Fi or Ethernet, then click your active connection Scroll to IP assignment → Click Edit Change to Manual, enable IPv4 Enter: IP address (e.g., 192.168.1.100 ) Subnet mask ( 255.255.255.0 ) Default gateway (e.g., 192.168.1.1 ) DNS servers (e.g., 8.8.8.8 , 8.8.4.4 ) Click Save Method 2: Using Control Panel Open Control Panel → Network and Sharing Center Click Change adapter settings Right-click your active adapter → Properties Select Internet Protocol Version 4 (TCP/IPv4) → Properties Choose Use the following IP address and enter the details Click OK to apply For Windows Server 2016, 2019, 2022 Method 1: Using Control Panel Open Control Panel → Network and Sharing Center Click Change adapter settings Right-click the network adapter → Properties Select Internet Protocol Version 4 (TCP/IPv4) → Properties Choose Use the following IP address and enter: Static IP (e.g., 10.1.4.120 ) Subnet mask ( 255.255.255.0 ) Default gateway (e.g., 10.1.4.1 ) DNS servers (e.g., 10.1.4.1 , 8.8.8.8 ) Click OK        Method 2: Using Powershell Get-NetAdapter New-NetIPAddress -InterfaceIndex <Index> -IPAddress <IP> -PrefixLength 24 -DefaultGateway <Gateway> Set-DnsClientServerAddress -InterfaceIndex <Index> -ServerAddresses <DNS1>,<DNS2> Replace <Index>, <IP>, <Gateway>, <DNS1>, and <DNS2> with your actual values.    

Issue The Windows Installer fails to complete the installation of an application. This may occur across various Windows operating systems. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows 10 Windows Server 2012 editions Windows Server 2012 R2 Cause Installation failures may result from: Corrupted system files Incomplete previous installations Conflicts with existing software Unsupported OS versions or outdated service packs Resolution For Windows 10: Use the official Microsoft Program Install and Uninstall Troubleshooter: 🔗 Launch Troubleshooter Note: This tool is not supported on earlier versions of Windows or Windows Server. For Other Windows Versions: Manual troubleshooting steps may be required: Run System File Checker (SFC): Open Command Prompt as Administrator and run: sfc /scannow Check Windows Installer Service: Ensure the service is running: Press Win + R , type services.msc , and locate Windows Installer Right-click → Start (if not running) Clear Temporary Files: Use Disk Cleanup or manually delete files from %temp% Review Event Viewer Logs: Look for installation-related errors under Windows Logs → Application Verify OS Compatibility: Confirm your OS version is supported by the application and has the latest updates. Additional Notes Always verify the official Microsoft support status for your OS version to ensure compatibility and security.

Issue BACnet Service does not start after enabling BACnet IP on a UNC station. The following error messages are seen in the UNC standard output. ERROR: Error initializing IP link layer. [IpLinkLayer.updateLocalAddress] java.lang.NoSuchMethodError: tridium/nre/Platform.getLocalHost()Ljava/net/InetAddress; ERROR: Cannot startService [Sys: BACnetService [12] BACnetService] java.lang.NullPointerException ERROR: Run error [BTrprt] java.lang.NullPointerException Product Line TAC IA Series Environment I/A Series UNC running at version r2.301.5xx prior to version r2.301.535 with BACnet 2.305.535a. Cause Most I/A Series R2 Niagara JAR files are backward compatible. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330? for details.  There were some changes to the BACnet service IP to support the new JACE-603/645 platforms. Because of these changes to the R2 core, the BACnet 2.305.535a JAR file is not backward compatible.  Resolution Upgrade the UNC to version r2.301.535. Refer to the Installation Instructions for upgrade procedure. 

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue When trying to run Workplace Tech 4.0 for the first time, it may not start successfully, and an error message will be displayed: "Microsoft Visual C++ Runtime Library, Runtime Error!" Environment Workplace Tech version 4.0 Visio 2002, SR1 Windows XP Professional, Service Packs 1-3 Windows 2000 Professional, Service Pack 4 Cause The error is typically caused by not initializing Visio 2002 before running WPT 4.0 for the first time. Resolution See Technical Bulletin TB04-02, which details the issue and resolution.

Issue Significant changes and improvements were introduced with firmware revision 11.2P, including a streamlined "Flash clear" procedure. For Ethernet NIMs with firmware revisions prior to 11.2P, the procedure was documented in Technical Bulletin 99-56 (see below). The procedure in bulletin 99-56 was a revision of the procedure in the original NIM Networking and Configuration Practices manual, F-25955, which is no longer available. The current version of the manual, F-25955-4, applies only to NIMs with firmware  revisions 11.2P and 11.2T. Environment Ethernet NIM for network 8000; GCM-ETH-001 with firmware revision prior to 11.2P. Cause "Flash clear" procedure was changed in firmware revision 11.2P Resolution Follow the "Flash clear" procedure per Technical Bulletin 99-56.

Issue Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Environment I/A Series G3, Modbus, Modicon, Schneider Electric PowerLogic PM800 Series Power Meters Cause Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Resolution As a workaround, the Modbus proxy points can be configured to poll the register as four integers and convert or combine the four integers to a single unsigned 64-bit value.  NOTE: that all four registers will need to be polled in a single message.  The following are two examples that can be used to read and convert unsigned 64-bit values.  The first example converts a Modicon power value with data type UINT64.  The second example converts a Schneider Electric PowerLogic P800 Series Power Meter with data type MOD10. Example 1 (Modicon UINT64):  The memory map below indicates the Total KWh+ value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 0500h. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the Modicon address 301280 (0500h) would be configured as follows. NumericPoint1 > Data Address (Address Format Hex, Address 500, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Hex, Address 501, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Hex, Address 502, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Hex, Address 503, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Hex 500, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple UINT64 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 65536.0 Multiply1 = 4294967296.0 Multiply2 = 281474976710656.0   The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToUINT64 program object can be copied into a station database. Example 2 (PowerLogic P800 Series Power Meter MOD10):  The memory map below indicates the Energy (Real Out) value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 1708. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the address 1708 would be configured as follows. NumericPoint1 > Data Address (Address Format Decimal, Address 1708, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Decimal, Address 1709, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Decimal, Address 1710, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Decimal, Address 1711, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Decimal 1708, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple MOD10 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 10000.0 Multiply1 = 100000000.0 Multiply2 = 1000000000000.0 The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToMOD10 program object can be copied into a station database.

Issue Is the I/A Series R2 software compatible with a specific version of Windows? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software Windows 32-bit operating system Cause Only specific releases of the I/A Series R2 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series R2 software and the various 32-bit versions of the Microsoft Windows Operating System software.  NOTE: I/A Series R2 software cannot be installed directly in any 64-bit version of the Microsoft Windows Operating System. Virtual platforms such as VMware Server 2 or Microsoft Virtual Server 2008 are not supported in R2.   R2 522 R2 527 R2 529 R2 532 R2 535 R2Tunnel Clients TunnelAX Clients  VAS 2.50 VAS 3.92                     Windows XP Professional (SP3) (32-bit) Y Y Y Y Y Y Y Y Y Windows XP Professional (SP3) (64-bit) N N N N N N N N N                     Windows Vista Business / Enterprise / Ultimate  (SP2) (32-bit) N Y Y Y Y Y N N N Windows Vista Business / Enterprise / Ultimate  (64-bit) N N N N N N N N N                     Windows Server 2003 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                     Windows Server 2008 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                      Windows Server 2012 (All Versions 32-bit & 64-bit) N N N N N N N N N  Windows Server 2012 R2 (All Versions 32-bit & 64-bit) N N N N N N N N N                     Windows 7 Professional / Enterprise / Ultimate (32-bit) N N Y* Y* Y* Y* Y* N N Windows 7 Professional / Enterprise / Ultimate (32-bit) (XP-Mode) N N Y* Y* Y* Y* Y N N Windows 7 Professional / Enterprise / Ultimate (64-bit) N N N N N N N N N Windows 7 Professional / Enterprise / Ultimate (64-bit) (XP-Mode) N N Y* Y* Y* Y* N N N                     VMWare Server (all versions) N N N N N N N N N Microsoft Virtual Server (all versions) N N N N N N N N N                     Microsoft SQL Server 2000 Y Y Y Y Y         Microsoft SQL Server 2005 N Y Y Y Y         Microsoft SQL Server 2008 N N N N N         Microsoft SQL Server 2008 R2 N N N N N         * Refer to PA-00163 for Windows 7 Support Info. NOTE: When selecting a computer on which to install the I/A Series R2 software, select one that meets or exceeds the recommended hardware for the selected operating system. For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation