Building Automation Knowledge Base

Issue An error pop-up is encountered when trying to use WorkPlace Tech Editor (WPTE) ERROR: WorkPlace Tech Editor does not function using Visio 2000. A supported a supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2013, 2016, 2019 Cause The Visio installed is corrupted or not updated to the required version. Resolution Procedure for doing the repair required for the WPTE to function Ensure that the Visio installed is approved for the version of WPTE you are using by reading the EBO release notes. Confirm that Visio if licensed and activated, and not using a temporary license Install any required Security Upgrades  Perform an Online Repair, not the Quick Repair, as illustrated  The picture above shows doing this repair to the installed Office.  Perform this on the installed Visio as well. It is important to search the installed applications to make sure no 64-bit Office products are installed.  Smartware Studio 360/Design 360 installs a 64-bit Microsoft Access DB application by ignoring the 32-bit/64-bit version check.  This can cause the fluent ribbon for WorkPlace Tech to fail and if the Online Repair is done, it can force all Office applications to be removed from the PC. 

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue When is an "additional 500 points" license required for an Enterprise Server? Product Line TAC IA Series Environment I/A Series R2 IA-ENT-1 Enterprise Server licensed with the IA-DRV-OSD Open Systems Device driver license Cause The basic Enterprise Server license does not include any external point driver capabilities.   Adding the IA-DRV-OSD allows the enterprise server to communicate with up to 25 points of each type, BACnet, OPC, SNMP and ModBus, all using IP communications. Resolution An Enterprise Server can be licensed to directly communicate with  BACnet, OPC, MODbus and SNMP points by adding the IA-DRV-OSD license and will support communication with up to 25 points of each specific type of points. For each additional block of 500 points of a specific type, you need to purchase an additional points license, IA-BAC-500, IA-OPC-500, IA-MOD-500 or IA-SNMP-500.  Here is an example of how these licenses are used.  The Enterprise Server needs to communicate directly with 1250 BACnet IP points and 60 SNMP points.  The following licenses will be required: IA-ENT-1 -- Enterprise server license IA-DRV-OSD -- Open System Driver for direct point communication, includes 25 points each of BACnet, SNMP, OPC and ModBus. IA-SNMP-500 -- allows ES to communicate with the 60 SNMP points, technically allowing communications with a total of 525 SNMP points (25 points included with IA-ENT-1 and 500 with IA-SNMP-500). IA-BAC-500 -- allows the ES to communicate with an additional 500 BACnet points bringing the total to 525 BACnet points IA-BAC-500 -- this second IA-BAC-500 license will allow the ES to communicate with the additional 500 BACnet points, bringing the total allowable BACnet point count to 1025 points IA-BAC-500 -- this third IA-BAC-500 license will allow the ES to communicate with the required additional 225 BACnet points, actually bringing the total allowable BACnet point count to 1525 points. NOTE: On most computers an IA-ENT-1 with the Open System Driver is capable of supporting a maximum of 4000 external points regardless of the number of points licensed in any one communication type.

Issue How to use a digital point card with a Network 8000 MicroZone II controller. Product Line TAC IA Series Environment Network 8000 MicroZone II controller Digital Point Card Cause To use the digital input cards (DPC-3-1 & DPC-3-2) with a MicroZone II controller, it requires a custom application file. Resolution The MicroZone II controller supports two digital input cards:  DPC-3-1 & DPC-3-2. A custom application file (1-DPC3.MZ2) is required to properly read the digital input card, review technical bulletin TB01-26 for more details. (Note: The DPC-5 series cards were designed for the MNL and MNB controllers.  They are compatible with the DUI Expander Object available for both controller lines.)

Issue Can the DUIC-5P-12V digital point card be used on a MNL-200? Product Line TAC IA Series Environment IA Series MNL-200 Cause Integration of multiple status inputs Resolution The DUIC-5P-12V will function with the MNL-200 controller.  Do not use the BACnet DUI_Application.  Use the WorkPlace Tech's DUI Expander object instead.  Also, remove the JP1 jumper on the DUIC-5P-12V board.

Issue Can the DUI expander be used with a MNB-1000-15 remote I/O module? Product Line TAC IA Series Environment MNB-1000 MNB-1000-15 Cause Integration of multiple status inputs Resolution The DUI expander was never tested with the MNB-1000-15.  Therefore it is not supported.

Issue In DUI-5R modules on installed MNL-800's the LED indications on the DUI follows the contact closure signals connected to them, but the values being read based on those status points do not match. Eg. DUI-5 has LED's on for inputs 1, 3, and 5 however the controller values have 1 and 5 on only. Product Line TAC IA Series Environment WorkPlace Tech MNL-800 Cause MNL-800 Inputs require an external parallel resistor (Rp=22.1 kohms, 1%) be placed across the UI input to which the DUI is attached. Some DUI models may incorporate this resistor that may be either switch or jumper selected. Resolution MNL-800 Inputs require an external parallel resistor (Rp=22.1 kohms, 1%) be placed across the UI input to which the DUI is attached. Some DUI models may incorporate this resistor that may be either switch or jumper selected. For example the DUI-5R available in Asia Pacific notes the following: Switch 1 set to ON for MNL-800 and OFF for all other controllers. In some models the switch is replaced by a jumper. Bridge the jumper for MNL-800s and leave open (jumper on one pin only) for all other MNL controllers.

Issue DUI-5N Digital Input Expander Module availability Product Line TAC IA Series Environment I/A Series Micronet LON and BACnet controllers Cause Third party product which Schneider Electric Asia Pacific (Invensys Building Systems) used to carry.  Resolution Schneider Electric no longer supplies this third party product. This product is manufactured by Barcol Industries in Taiwan. Anyone requiring this part should contact Barcol Industries directly. Contact Mr. Alex Lung at alex_lung@barcol.com.tw.    * Schneider Electric does not provide support or warranty for this product, all support requests should be directed to the manufacturer. An equivalent product which expands an universal input on an I/A Series MNL or MNB controller to 5 digital inputs is the BCS-DUIC-5P. This is also a third party product and is available from Schneider Electric Rockford. 

Issue Are the RoamIO and RoamIA interchangeable? Product Line TAC IA Series Andover Continuum Environment I/A Series WorkPlace Tech, Continuum Service Tool Cause Need to communicate directly on the field bus wiring to controllers. Resolution There is a firmware difference between the RoamIO and RoamIA, so they are not interchangeable.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Recovering non-functioning Jace 8000 caused by image corruption Product Line TAC IA Series Environment Jace 8000 Cause Improper management of the files on the Micro SD card of the Jace 8000, power brownouts, and other issues have been known to cause corruption of the installed "Golden Image" of the Jace Resolution Download and review the Product Announcement to determine which image should be used on your Jace based on the software to be installed and the Micro SD card version: PADV-IA-22-0001, JACE 8000 Hardware Changes Soon To Be In Effect Note item 8 in the FAQ for information about the correct image for use in version 4.0 Micro SD card.   Download and select the image and tools for completing the process detailed in the video: I/A Series Niagara JACE 8000 Images and Raw Copy Utility - Installation Software   

Issue Error message in Platform Application Director; SEVERE [00:25:32 08-Feb-21 EST][sys] Cannot boot Product Line TAC IA Series Environment I/A Series N4.9 and later I/A Series N4 Enterprise Server I/A Series N4 WorkBench Cause In 4.9.1.30 and later, the JDK distributed with Niagara was upgraded to 8u271. Starting in JDK 8u261, the target Visual C++ version was changed. While the updated libraries are available in the jre/bin folder, this folder is not on the PATH for NRE binaries. This can cause Niagara to fail to launch on Windows if another copy of the Visual C++ Redistributables is not present. Resolution Install the Visual C++ 2017 Redistributables. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads At the time of this article, Microsoft packages the 2015, 2017, & 2019 redistributables together. Select and install the x64 version.      https://aka.ms/vs/17/release/vc_redist.x64.exe    

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Issue Does the Niagara R2 Modbus driver support a 6-digit address format? Product Line TAC IA Series Environment Niagara R2 Modbus driver Cause Modbus 6 digit addressing is not supported when using modbus format in the driver. Resolution The six-digit address format and the five-digit format are just two different notations for the same thing - there is no difference in the protocol. For example, the first one thousand holding registers are normally represented as: (modbus) 40001 to 49999 -or- (decimal) 0 to 9998 -or- (hex) 0 to 270E When using modbus format in the driver, the left most digit, '4' in this example, is part of a convention that indicates the 'type' of point and, when using that convention, the point type does not have to be specified.  For example, for modbus point 40001 the '4' indicates that it is a holding register. But there are actually 64000 holding registers available and, using the common 5-digit modbus notation, it is not possible to specify more than 9999 of them. The six digit convention just moves this 'type' digit one space to the left. In this six-digit notation, the first one thousand holding registers would be 400001 to 409999. This 6-digit convention for 'modbus' formatted addressing is not supported but it is still possible to use decimal or hex notation to specify these addresses with Niagara R2. When 'modbus' formatted addresses are used, the driver subtracts 1 from the entered address, since modbus uses base 1 formatting and decimal uses base 0.  When using decimal or hex, the leading digit is dropped and subtract one from the register value and optionally convert to hex and use that as the point address. For example, to read data from register address = 422202 Drop the leading character = 22202 Subtract 1 = Decimal address 22201 or hex address 56B9

Issue Is there a recommended  repeater for BACnet MSTP networks?   Product Line TAC I/A Series   Environment R2 G3 (Niagara) MNB-1000 Cause MSTP repeaters may be required to extend trunk length or provide isolation in the smoke purge application.   Resolution Consider B-Links which were actually used on the MSTP trunk during UL 864 testing. B-LINK-AC-S (AC powered)    B-LINK-DC-S (DC powered)   B-LINK-F-DC-S (Fiber Repeater) 

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue DHCP server is required to assign addressing to IP devices Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Jace 8000 I/A Series ScheniderMPx Modules Building Operation Multi-purpose VAV  Building Operation Multi-purpose Controller Building Operation Room Controller (RPC) 24 V Building Operation IP-IO Cause When working with the SchneiderMPx modules for engineering Spacelogic devices, the Jace can be used as a DHCP server for the field devices. Resolution This video discusses how to; - Configure the second IP network port for DHCP server use - Add an additional IP Port to the Jace station  

Issue When viewing the "Device Properties" of an MNB device in the Workplace Commissioning Tool (WPCT) the controller status indicates "Operational, Read-Only"? Product Line TAC IA Series Environment BACnet MNB controllers WorkPlace Commissioning Tool all versions Cause The MNB-xxxx series controllers contain circuitry that is designed to protect the integrity of the embedded flash memory under low-voltage or questionable input voltage conditions.  In the event of a controller-perceived low-voltage condition, the controller will set a read-only flag and lock out all writes to memory, as well as turn off controller outputs. Resolution The Read-Only status can help serve as an indicator that the input voltage to the controller may be questionable. Attention should also be paid to the wire distance between the central transformer and the secondary loads, especially in the case of half-wave input devices like the MNB-70, MNB-V series and MNB-300 controllers and the MNB-1000-15 remote I/O module. With half-wave type input devices, significant AC input current spikes can occur during the positive half-cycle of the AC input. Large resistances due to the wire lengths can cause significant voltage drops as seen from the controller AC input. In extreme cases, the controller may enter the read-only mode at apparent AC voltages exceeding 20 Vac due to the asymmetrical nature of the AC input voltage waveforms. In these cases, reducing the load on the transformer, reducing the wire length between the controller and the transformer, and using higher current rated wire will correct the problem.  For complete wiring guidelines consult the Micronet BACnet, Wiring, Networking, and Best Practices Guide. Once the power issue is resolved cycling power to the controller will clear the read-only portion of the status. 

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue Procedures and processes to secure I/A Series Niagara 4 Systems Product Line TAC IA Series Environment  I/A Series Niagara 4 Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara 4 system.  While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara 4 system more secure by carefully configuring and using: Passwords System Passphrase Platform Account Management Station Account Management Role and Permission Management Authentication TLS and Certificate Management Module Installation Additional Settings External Factors Please note that while all of these steps should be taken to protect your I/A Series Niagara 4 system, they do not constitute a magic formula. Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn’t mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it. Note: Schneider Electric strongly recommends upgrading to the latest I/A Series N4 version maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build-included documentation to understand the behavioral impacts of the security enhancements and JACE hardware platforms supported. Download the Niagara 4 Hardening Guide_2023 for more details.

Issue Using a VPN with I/A Series Niagara Systems Product Line TAC IA Series Environment I/A Series Systems Cause A VPN's purpose is to provide a secure and reliable private connection between computer networks over an existing public network, typically the Internet. Resolution What is a VPN? "Virtual Private Network" or VPN is a mechanism to extend a private network across a public network such as the Internet. A VPN creates a point-to-point connection or "tunnel" across the Internet between two computers. The tunnel encrypts the data between VPN endpoints, preventing data from being deciphered without the required encryption keys. Why use a VPN? VPN provides an additional layer of security to your Niagara system without compromising your ability to access Niagara. A VPN can help protect your Niagara system from Internet-based attacks by requiring an additional layer of authentication to access Niagara resources. It can prevent automated Internet port scan tools from detecting the Niagara system. How can I set up a VPN? The following document describes how to use an Internet Security Gateway to provide VPN access to your ENC/JACE.  Click on the link to download Using a VPN with Niagara Systems for more details. In addition, the document describes setting up a VPN using a ZyWALL gateway.  The ZyWALL USG-20 unified security gateway (from ZyXEL) is a cost-effective device that you can add to an existing installation to provide VPN server capability. IMPORTANT NOTE: The information in this document is based on the assumption that the only IP devices on the network are Niagara devices. If Niagara devices share a network with other devices (such as a corporate LAN), DO NOT follow the approach described in the following pages. Instead, work with the customer’s IT department to determine the best method to protect both the Niagara and corporate systems while providing required access to the Niagara systems. In any scenario, if the VPN is installed or configured improperly, you can expose devices to the public Internet. If you are unsure about how to best configure and test your configuration, please consult an IT expert. Frequently Asked Questions I already use SSL, do I still need to use a VPN? The use of a VPN is still recommended as an additional layer of security. Attacks can come from both inside and outside of your network. Once I set up a VPN, do I still need to use SSL? Yes. The VPN only provides encryption between the VPN endpoints – the VPN client and server. Traffic from the VPN endpoint to and from the Niagara Station is not encrypted unless SSL is used. I’m running AX 3.6 or earlier without SSL support – should I still install a VPN? Yes. The VPN still helps protect against Internet-based attacks on your system. Do I still need a firewall? Yes. You should set up firewall rules to restrict Internet access to the VPN server port only. You should also consider setting up rules with the VPN server to restrict VPN access to only the required IP addresses and ports. For example, there may be non-Niagara devices on the LAN, but the VPN should be configured to only allow access to the Niagara systems. Additionally, you should only allow access to required Niagara services. Will a VPN affect LAN access to ENC/JACEs? No. LAN access to the Niagara devices remains the same as always. VPN only affects the ability to reach Niagara devices from external networks such as the Internet. If I use a VPN, will Niagara HTTP, Fox, and Platform tunneling work? Tunneling works normally over a VPN. You will need to update IP address assignments. What is the impact of VPN on Niagara Networking? Niagara Networking between systems on the LAN still functions the same whether or not there is a VPN installed. When I connect to a VPN, do I lose all other network connectivity? While your VPN client is connected to the remote VPN network, your Workbench (client) PC will have a new "Default Gateway" to allow you to make connections to stations on the VPN network. Typically, this happens without your knowledge and is mostly transparent. The change is undone after disconnecting from the VPN, and re-done when you reconnect. However (while you are connected to the VPN network) if your Workbench (client) PC tries to connect to sites on the [public] Internet or any other network through any router, you will find that you cannot reach those sites. If you must be able to reach those sites while connected to the VPN network, you will need to add static routes (temporary or permanent) to your Workbench PC’s TCP/IP configuration. The setting of those routes is beyond the scope of this document because they are specific to your PC’s network, your VPN network, and any other networks you try to reach. It is possible (but unlikely) that you cannot resolve these routing issues. This may happen if one or more of these networks have overlapping addresses. Consult with a TCP/IP expert if necessary. Likewise, if you use L2TP, PPOE, PPTP, or PPP for any part of your underlying network connection, the VPN client will probably conflict with it. Specifically, Windows only allows one connection of these four protocol types to be active at any given time. What is the impact on Single Sign On? You will need to define the SSO Domain and the hosts of the SSO Domain in your Workbench PC’s "hosts" file or default DNS server. The DNS server of the VPN will not be able to provide name services without changing your Workbench PC’s TCP/IP configuration. I use Dynamic DNS, can I still use a dynamic DNS provider with VPN? Yes. You will need to register the IP address of the VPN gateway and firewall with the DDNS provider. What is the impact of VPN on my system performance? Impact on performance should be minimal. It does take a little longer to set up the connection. References: Microsoft TechNet VPN Overview