Building Automation Knowledge Base

Issue Is the Personnel Import Utility (PIU) included with Continuum or is it add-on software? Product Line Andover Continuum Environment CyberStation Cause The PIU is sometimes confused with the Personnel Data Importer, which is add-on software. Resolution The Personnel Import Utility is part of the Continuum system but must be enabled in the CyberStation key before it can be used. The key must have the -D (Data Exchange) option in order for the PIU to work.

Issue "Ethernet 1 Configuration" of a SmartX Server in the Device Administrator for EBO version 3.2.1 or higher shows "Dynamic DNS" as enabled and grayed out. Is it possible to disable "Dynamic DNS"? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium version 3.2.1 or higher Cause The Dynamic DNS service procedure supports the assignment of dynamic IP addresses to a particular domain. A comparison with the internet provider's DNS databases takes place automatically. The Dynamic DNS automatically ensures that changes to the IP address are detected and DNS entries are updated accordingly. Resolution In EBO version 3.2.1 or higher it will not be possible to disable Dynamic DNS, it will always be enabled.

Issue Programming an 8-Bit HID or Indala Prox/Pin Pad reader Environment I/Net Site with Access Control Cause There is a requirement to supply an 8-Bit Prox/Pin Pad reader at a site. How do I program this reader? Resolution Attached is a PDF File that guides you through the setup if this type of reader in an I/Net Seven system. Click here to download.

Issue After upgrading to version 1.7.1 or later, a performance issue is seen when reading BACnet values from BACnet/IP devices. The CPU usage on an Automation Server is continuously high. Product Line EcoStruxure Building Operation Environment Detected in version 1.7.1 Automation Server Enterprise Server BACnet/IP Cause A new "BACnet ReadPropertyMultiple Service" has been included from version 1.7.1. Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behaviour will particularly benefit graphics performance for ReadPropertyMultiple. If a site is upgraded to version 1.7.1 where this improved communication service gets used automatically, it is possible that the server CPU usage increases. This issue will only be seen if the third party device does not support COV subscriptions, does support ReadPropertyMultiple and a large number of values are being requested from the same device e.g. using bindings. This is a result of much more data being requested by the Server in the same time period.  From Release Notes version 1.7.1 3.4.4 Improved polling performance Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behavior will particularly benefit graphics performance for ReadPropertyMultiple.” Resolution Select the BACnet interface where the performance issue is seen Select the advanced properties for the interface Change the “Minimum polling interval for local IP networks (ms) to “3000” In case the BACnet interface is configured in an Automation Server, test other values in step 3 until the CPU usage is stabilized You can check the AS CPU usage, by dragging the CPU usage property to the watch window in WorkStation NOTE It is also worth setting the MSTP polling to 3000mS, to ensure third party BACnet Devices that do not support COV subscriptions, are not overloaded. Without this value set, it has occasionally been seen that Bacnet devices go offline or value readings stop updating the values.

Issue Network Paging System or Network Wide SMS Messaging for I/NET Product Line TAC INET Environment I/NET Site Cause Requirement for Network Paging System or Network Wide SMS Messaging Resolution PageGate allows for network paging or network wide SMS messaging from any combination of the following modules: web, email, commandline/ascii, serial, TAP-in and (GUI) windows workstations. SMS or text messages can be sent to alphanumeric pagers, numeric pagers, cell phones, PIMs, billboards or pcmcia pager cards. For capturing and paging I/NET Seven alarms and messages we use the “Get Serial” module from PageGate. Please see the following link for Technical configuration and contact information: PageGate.doc To download the trial software please use the following website: https://www.notepage.net/ Expectations of Service Schneider Electric does not offer formal support for the third party software or hardware found here. Instead, our role is to provide a platform to provide information for people who want to take advantage of the global community of Schneider Electric customers. Schneider Electric will make every effort to monitor content to ensure the accuracy of the information you'll find, but any information provided by Schneider Electric staff is offered "as is" with no warranties, and no rights are conferred. You assume all risk for your use of third party software and hardware.

Issue Switching between LON communication methods within WorkPlace Tech may require a WorkPlace Tech and a LON tunnel client service restart. Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.9.3 and previous Cause When dynamically switching between LON communication methods within WorkPlace Tech (i.e. LON interface card to LON tunnel client), WorkPlace Tech communications may not initiate communications through the tunnel client properly. Resolution When this condition occurs, restart both WorkPlace Tech and the LON tunnel client as follows.   Save and close any open WorkPlace Tech applications and projects. Shut down the WorkPlace Tech tool. Restart the LON tunnel client service (Niagara LON Tunnel) within the Windows operating system services.  Verify the Niagara App Tunneling settings in Windows Control Panel. Please note, that any changes to the LON Port Name require a reboot of the computer. Start WorkPlace Tech and verify the WorkStation Communications Settings (i.e. network interface device driver and VLon device check box). Note: This does not apply to WorkPlace Tech 5.9.4 and newer encrypted tunneling in N4 Jaces.

Issue TAC Valve Body published Cv values may differ markedly to equivalent Kv values.  Environment TAC Valve Body published data utilised when sizing and selecting S-E / TAC Control Valves. Cause TAC Valve Body published Cv values based on flow rates measured in U.S. Gallons per minute rather that U.K.Gallons per minute., Resolution Check published Cv value relative to published Kv value stated for TAC Valve Body. If published Cv value is within 3% of published Kv value then Cv value may be used for sizing / selection of Valve Body. If published Cv value is up to 17% higher than Kv value then Cv value should not be used for sizing / selection of Valve Body. Cv values published in older TAC Valve Body Data Sheets should be checked before considering use in U.K. valve sizing formula. Numerous TAC Valve Body Data Sheets show that for a particular Kv value, the equivalent Cv value is approximately 17% higher than the Kv value. For example, where TAC Valve Body Data Sheet shows Kv = 10, then equivalent Cv = 11.7 or in other words Cv = Kv x 1.17 Cv values published in Satchwell Valve Body Data Sheets however show the relationship between Kv and Cv as:- Kv = Cv x 1.03 or in other words Cv = Kv x 0.97 This difference in equivalent values is due to Cv values stated in some TAC Data Sheets being based on flow rates measured in U.S. Gallons per minute, while those Cv values stated in Satchwell Data Sheets however are based on flow rates measured in U.K. Gallons per minute. If flow rates are measured in U.S. Gallons per minute, then the following conversion factor applies :- Kv = Cv x 0.86, as the U.S. Gallon is smaller than the U.K. Gallon. Taking published TAC Valve Body Data Sheet information therefore, where the Cv value is stated as 11.7 and the Kv value is stated as 10, confirms that the conversion factor Kv = Cv x 0.86 ( 11.7 x 0.86 = 10 ) has been applied, further confirming that published Cv values are in fact based on U.S. Gallons and not U.K. Gallons. Consequences of this are as follows : - If it is assumed that the published Cv value is a U.K. Cv value, when in fact it is a U.S. Cv value, and the published Cv value is then used as a basis for valve sizing and selection, then this will result in a smaller Valve Body being selected than would otherwise be the case. Consequently, once installed, the selected Valve Body will produce a much higher pressure drop and correspondingly higher authority for a given flow rate than would otherwise have been the case. In practice the installation of an undersized Control Valve can result in starvation of flow to the item of plant being controlled and the potentially costly replacement of the Valve Body for another of a larger size. Similarly, the installation of an undersized Control Valve will result in a greater pressure drop being applied to the hydraulic circuit than may be desirable and could lead to an adverse effect on the performance of the associated circulating pump. It is important to ensure therefore that where both Kv and Cv values are published for a given Valve Body, the Kv value is utilised when undertaking valve sizing and selection.  This should ensure that a Valve Body of the correct size is selected. Measures are currently in place to actively remove all references to Cv values from both S-E / TAC Data Sheets and all future editions of the S-E HVAC Valves and Actuators Catalogue.

Issue Initiate Xenta 102-AX service pin messages (Neuron ID) from an M/STAT It is not required to hit the service pin button on the Xenta 102-AX itself, this can be done remotely from the room stat, provided it has an M/STAT jack (STR-250). Environment Xenta 102-AX M/STAT Cause If the Xenta 102-AX is installed up in the ceiling out of arms reach (which is typical) it can be cumbersome to get to each board to press the service pin button. Resolution Plug in an M-STAT to the room sensor (assuming you ordered the sensors with the M-STAT jack) Hold the service button in for about 5 seconds. This will tell the controller to broadcast its Neuron ID.

Issue After allowing Mozilla Firefox web browser to automatically install the latest security updates (v3.6.14), I/A Series (Niagara) R2 or G3 graphic screens cannot be displayed. Environment Mozilla Firefox 3.6.14 Graphic pages served by a UNC/ENC or Enterprise Server/ENS with any version of I/A Series R2 or G3 (Niagara) software Cause Known and documented issue with the way Mozilla Firefox 3.6.14 handles the loading of Java applets. The issue has already been documented on the Mozilla Firefox support forum. Resolution Downgrade to an older version of Mozilla Firefox or use a different compatible web browser. Older Firefox releases are on the Mozilla FTP site (Mozilla FTP).

Issue 'Unable to request license' message when using Demo license with Remote Workstation. Product Line TAC Vista Environment Vista 5 Vista 4 Cause The Demo license only works when installed on the same PC as Vista Server. Resolution Install demo license on the Vista Server PC and run Workstation on the same PC.  If remote Workstation operation is required or the license server is on a different PC to Vista Server, purchase an end user license.

Issue There is a beeper inside some of the card readers. In some cases when alarms happen, such as Door Forced or Door Open Too Long, the beeper can be activated with a sound to deliver alarms. Product Line TAC INET Environment I/NET Cause In some cases this application is needed. Resolution Open the Door parameter in I/NET. Set the relative alarm message. For example, set the Door Open Too Long or Door Forced to Alarm.   Click the "Sounder" button Change the polarity to "Low". Set the relative beeper type and condition. For example, when the Door Open Too Long or Door Forced happens, the beeper activates continuously. For more issues about beeper in I/NET, refer to Reader beeps continually when connected to the door controller.

Issue StruxureWare for Building Operation User Interface Matrix Environment SmartStruxure Cause Need information about which User Interface Option has which features Resolution You can download the User Interface Matrix from The Exchange Download Center: User Interface Summary

Issue What is the maximum character length a value (object) name can have? What is the maximum character length an alarm name can have? What is the maximum character limitation on the Description? What is the maximum character limitation on the Alarm and Reset messages? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation (all versions to 1.3 SP1  (1.3.0.10100))  Cause Require an understanding of what character limits are applied within Building Operation Workstation Resolution There is no documented limitation, the following numbers are those that have been tested: An object and alarm name: 1900 character limit. An object and alarm Description:  No found limit here, either in entry or saving. An Alarm message and Reset message - no found limit here, either in entry or saving. It is important to note these are limitations on StruxureWare objects only, when the actual object is also represented in another device, like a BACnet or LON device, then there may be restrictions at that device. A b3 is an example of this where you can make the object name with 1900 characters but the BACnet name will be limited to 32. Also refer to StruxureWare Building Operation object names limitation on what characters are allowed to be used.

Issue Setting a TAC Xenta OP to show IP (US) units instead of SI units Product Line TAC Vista Environment Xenta OP Cause Switching the TAC Xenta OP between imperial and metric units. Resolution Connect to a TAC Xenta 100 After pressing "down," there is a setting "unit as" Toggle between SI and US (IP) by pressing the "up" button Please note that this only changes the presentation, and that both absolute as well as relative values are re-calculated. This means that a difference in temperature may be shown incorrectly.

Issue Xenta 5/7/9xx locks up during boot up sequence. Plugged into the service terminal (RS-232-B) during the boot up sequence, it can be observed that it stops processing on the "InstallDrivers" command. In some situations the error log produces the 49154 error code. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In some situations the error log produces the 49154 error code. If the Xenta 511/527/913 is not booting correctly and stops processing on the "InstallDrivers" command, visible via a Hyperterminal connection, the cause typically is that the Xenta controller is underpowered. Resolution The Xenta controller can survive some drop in power after the initial boot up sequence, but it vulnerable to an insufficient power supply during the boot up sequence. To avoid this problem simply provide the Xenta controller with a stable power within the documented range. The 49154 error code is typically an issue with the power coming to the Xenta, the transformer or something, and a smaller chance of a short from the LAN which is causing this power instability. Mark said they can recycle the power, the Xenta comes back and works for a bit, then the same error. Check the transformer, then with a replacement Xenta in hand, upgrade firmware if possible. If not able, replace Xenta and if not to expensive, replace transformer at same time. 

Issue "Software file not found: 7797**.bin" when downloading bin on a 7797 ICI Product Line TAC INET Environment I/NET site with 7797 Cause Error Message in software file not found: 7797**.bin when downloading bin on the 7797 ICI Resolution The reason the Software Restore command is looking for a 7797**.bin file during the download is due to one of two reasons. The ICI has not been configured in the Edit->Controller->Configuration screen to specify the ICI type. Example: 12 for BacNet, 15 for Modbus. Copy corresponding bin file under /Support/Bin/ in the installation CD of I/NET to the Data directory. The download should be OK now.

Issue Cards are being read, but no transactions are being displayed in the AMT Window on a Direct Connect. Product Line TAC INET Environment I/NET Seven Card Reader AMT Cause Hardware address must be set to 0 when using direct connect Resolution Open the I/O Server Modify the active profile Modify the Link Configuration Verify that the Hardware Address is set to 0 Software Address can be 0 as well but you can change this is if you like Save the changes and restart I/O Server. Open AMT, Transactions Window, read a card and verify that it is being updated with card reads.

Issue Error message "The Parameter is incorrect" when clicking OK in TAC Vista Server Setup Emailing alarms from TAC Vista is not working Product Line TAC Vista Environment TAC Vista Server Setup Cause The text encoding method has not been selected. Resolution Open TAC Vista Server Setup Click on the Mail Tab Check if the Text encoding Field is empty. If it is, select an encoding from the dropdown. Unicode (UTF-8) is suggested in the US with an Exchange Mail server.

Issue The following error message appears when adding a LON application to a project in WorkPlace Tech 5.x from the pre-engineered "WPT Applications" zip file: AppXMLAddon Error Code: -2032465751 Code meaning: Unknown error 0x86DB08A9s. Environment WorkPlace Tech 5.x WPT Applications.zip Cause Workplace Tech encountered one or more values in the application that contain invalid characters. Generally, the most common value that causes this issue is the nciLocation SNVT. The value that should be in this SNVT is "/0", but through a previous Microsoft Visio conversion, it was replaced with a "vertical bar" character. Resolution Locate the invalid characters Replace them with valid ones or delete them. Once this is done, select "Application - Rebuild Application" from the drop-down menu.

Issue Trying to connect to a Xenta 527 over the web and cannot see it in I/NET, but can access it over the Ethernet Environment Xenta 527 Cause This occurs mainly because the reference host of the Xenta 527 and the Host PC are not seeing each other. Resolution Verify that all applicable ports are open, especially #50069, all C-Lan terminations are correct, # 19 and 20 on the Xenta 527. Start I/NET on the Host PC, open I/O Server, verify that TCP/IP is enabled. In the reference host, put in the IP address of the Xenta 527then save the settings. Connect to the Xenta 527 over the Ethernet, select Configuration Profile and put the IP address of the Host in reference #1 then save the settings. Restart both the Host and Xenta 527. Open I/O Server again then click on NP Routers and verify that the Xenta 527 appears in the table. Close this, then go to Edit Host Computer, Network Configuration, penetrate the link, it should be the Xenta 527’s name, save it. Penetrate the controller and its sub-lan devices should be seen as well, save all at this point. Close out of these editors and then connect to the controller, go to Summary and verify that you can control the points.