Building Automation Knowledge Base

Issue Not possible to download a MTA file to a Xenta from the System Plugin. The download was really slow and finished with an error. When the Xenta was decommissioned in Lonmaker it was possible to do the download.   Environment Tac Vista 5.1.7 System plugin 5.1.7 Lonmaker Cause The download problem is probably due to too much traffic to or from the Xenta on the Lon channel or that the Xenta have to much to do. If the problem is too much traffic to the Xenta is most likely to the I/O modules, one reason I have seen before is that an I/O module is specified in the Xenta but it doesn't exist, then the Xenta will try to reach it over and over again and it is very hard to get a download of the mta to work.   Resolution Workaround to get the mta file down:, Decommission the Xenta, Download the file  Commission it again.   To solve it check that no I/O modules is specified in the Xenta which don't exist on the network.

Issue Is it possible to calibrate a Controlli TQ-A31 Air Quality sensor? Environment Controlli TQ-A31 Cause In field calibration procedure. Resolution It is not possible to calibrate the TQ-A31 sensor on the field. You should read a 0..10Vdc voltage between B and C terminal. If the signal between these two terminal is not in the 0..10Vdc range than it can be the product is defective and therefore I suggest you to send it back to us through the usual claim system.

Issue When attempting to create a SOAP Web Service in StruxureWare,  WorkStation crashes after pressing the "Get operations" button for a WSDL file. Environment StruxureWare Workstation version 1.2.0.767 (released 1.2 build) Cause StruxureWare only accepts simple data types in the WSDL file.  Some WSDL files (e.g. Microsoft Exchange Server) uses complex data types (types.xsd) for input parameters and StruxureWare cannot process these data types.   Workstation crashes because of an unhandled exception. Resolution The unhandled exception error crash will be addressed in a future release so that Workstation does not crash upon receiving the error.  At this time, StruxureWare cannot process complex data types in WSDL files, and there are no plans to add this feature.

Issue With the valve obsolete, are the spare stuffing boxes available? Environment V294: 7219406000 7219410000 7219414000 7219418000 7219422000 7219426000 7219430000 7219434000 7219438000 7219442000 Cause Obsolete products and their spare parts Resolution V294 and all accessories/spare parts are obsolete since the end of 2010. No direct replacement parts are listed.  

Issue Popup window displays "License Invalid", "License Registry Error", "License on wrong machine" or other related error when starting the WPT software. Environment WPT software (any release) Cause License information stored in license file does not agree with the WPT/WPTL license information stored in the Windows registry. Resolution Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file.  NOTE: If the old computer has WorkPlace Tech release 4.0.0 or release 5.x.x prior to release 5.7, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed).  If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open".  This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. Locate the license file listed on line 1 of the WIB License Diagnostic display. Email the complete displayed text error message along with a zipped copy of the license file and diagnostic output file to Product Support A product support case will be created for you with the submitted information.  A product support engineer will contact you after reviewing your submitted information to assist you in correcting the issue.

Issue In some cases, the annual drift of sensors are requested. Environment STR500 004606000 STR502 004606100 STR504 004606200 STD500 5123074010, 5123078010 STD501 5123082010 Cause The annual drift of the sensors is not documented in data sheets or similar. Resolution Unfortunately, this information is not available from the manufacturers of the sensor elements.

Issue With the M42 series actuators being obsolete, they need to be replaced. Environment M42 Actuator M42/230 8401000000 Actuator M42/230 8401300000 Actuator M42P/24 8402100010 Actuator M42PBB/24 8402400010 TAC Forta series M9/EM9 Cause Replacement of obsolete actuators. Resolution Spare part for actuator for valves with linear moving stem the complete actuator TAC Forta should be used. When a 230 Volt actuator is requested the TAC forta needs a supplementary 230/24 Volt transformer. Depending on the electrical installation certain modifications may be necessary. For valves with rotating stem, actuators M9/EM9 can be used.

Issue The TAC Xenta Operator Panel does not hold steady when navigating down into programmable controller point lists. At random times the OP will back out and return to the main screen with the list of programmable controllers. Environment Operator Panel (OP) Vista Cause The XENTASYSREG bit 0 does not work in version 3.87 of the Xenta programmable controllers.  Resolution The latest firmware hotfixes need to be downloaded and installed for the corresponding TAC Xenta programmable controllers. For all Xenta Versions, download Hotfix version 3.87-02 on The Exchange Download Center.

Issue What effect does it have on a BACnet network if the Network Id - UDP setting in bCX40x0's on the same BACnet IP network have been set to different values? Product Line Andover Continuum Environment Continuum BACnet bCX4000 bCX4040 Cause A site had it's routers configured with different Network Id - UDP values and communications between controllers were not reliable. Resolution In the scenario below, the routers have different Network Id's for the UDP network. They may still be able to talk with each other, but they will all think they are on different networks which could cause routing issues and much more traffic than is required.  Controller         UDP NET ID                                         UDP COMM2 1                                  1                                                            2701 2                                  2                                                            2702 3                                  3                                                            2703 4                                  4                                                            2704 5                                  5                                                            2705 6                                  6                                                            2706 7                                  7                                                            2707 If all of these bCX's are on the same IP network then they will need to have the same Network Id - UDP value. By default we (and most other BACnet vendors) use a Network Id of 1. Change all of the bCX's so they are on Network ID - UDP of 1, as below. Controller           UDP NET ID                                         UDP COMM2 1                                  1                                                            2701 2                                  1                                                            2702 3                                  1                                                            2703 4                                  1                                                            2704 5                                  1                                                            2705 6                                  1                                                            2706 7                                  1                                                            2707

Issue 'Error waiting service pin' when attempting LonWorks communications in WorkPlace Tech Environment I/A Series WorkPlace Tech Echelon U10 USB Network Interface Cause WorkPlace Tech is not recognizing the Echelon U10 USB Network Interface.  The U10 USB Network Interface is recognized correctly in Windows Control Panel > LonWorks Interfaces.  Resolution Reinstall the U10 USB Network Interface and the Echelon Open LDV driver. To uninstall the U10 Network Interface (with the U10 Network Interface physically connected to an USB port): In Windows, go to 'start' > 'run', type in 'devmgmt.msc' and click 'OK'. This will bring up the Device Manager.  Expand 'Universal Serial Bus controller'. You should be able to see 'Echelon USB Network Interface'. Right-click on the 'Echelon USB Network Interface' and select 'Uninstall'. Remove the U10 Network Interface from the USB port. To reinstall the Open LDV driver: Uninstall Echelon Open LDV driver from Windows Add or Remove Programs. Install Echelon Open LDV driver using the installation file.  After completing the above steps, connect the U10 Network Interface to an USB port on the computer. It should automatically install. Test with WorkPlace Tech. 

Issue Request for technical documentation and data sheets for Senseair aSENSE m III Environment Senseair aSENSE m III 6553064000 Cause The requested documentation is not available through Schneider Electric. Resolution Since this is a Class3 product, the manufacturer is providing technical documentation. Please see www.senseair.com for details and download.

Issue Can't get the net.x automation KNX OPC server to work with Vista on Win Server 2008 R2 Environment Win Server 2008 R2 TAC Vista 5.1.X Cause A non-compatible version of NetX's OPC server is being used. Resolution Use the netX automation Voyager Server UD (Unified Driver) software. This is supported on 64-bit operating systems.

Issue Error reads....BACnet Device for this Infinity controller is not created, please perform a ‘Find new BACnet devices’. Site does not have any BACnet devices Environment CyberStation CX Infinity controllers Cause Some how Event Notification objects are configured under the infinity controllers in the database Resolution Delete non applicable BACnet only objects that some how got configured under the infinity controllers

Issue Screen resolutions may be distorted on a tablet PC Environment Webclient Tablet PC Windows 7 Cause Screens, graphics displays and drivers on Tablet PCs are very specific hardware for that device and can cause distortion when rendered in Continuum Resolution No QA testing has been done with any Tablet PC so results may vary as to how the screens are displayed on these devices

Issue Adding a named RI (Function Block Diagram) does not appear as a Input in AS or ES Environment StruxureWare Building Operation site with AS or ES using Function Block program Cause Adding a RI (FBD) with the name for example '_PB', it does not appear as a Input in AS or ES Resolution It shouldn't appear as an input on the AS or ES since it is only an input on the Function Block program. You must create the input on the resistive (physical) input on the AS and bind it to the real input on the Function Block. Function Block is a program running on the AS or ES and only will talk to the outputs when bound to the I/O or Input Output object.

Issue What is the difference between the M1500 and the M1500A actuators? Environment Forta M1500 M1500A Cause Why has the "A" been dropped from the specification number? Resolution Originally there were two specifications; M1500A which fitted to the control valve using a "U-Bolt". M1500A-VB which fitted to the valve using a "Screw Mount". The M1500 actuator is fitted to the valve using an "U-Bolt", if a "Screw Mount" is required, then the appropriate linkage kit should be used.

Issue The NV in my Xenta 401 is not updating the value defined in a Xenta 913 Environment Vista 5.xx Cause Network variable is only setup to work between Xenta controller. The network variable will not work between a Xenta 913 and a Xenta programmable controller Resolution The best solution is to insert the LNS or classic network into the Xenta 913 then use a connection object in the Xenta 913 to transfer the value

Issue What are all of the Key and Reserved works used in Plain English and object naming? Environment Names and Alias used in Plain English programming and object creation. Cause Keyword list required. Resolution Reserved Words are split into different types: Statements (used in Plain English) Functions Operators Local Variables System Variables System Constants A full list of all reserved and keywords are in the Plain English Language Reference, see Chapter 7: Keywords also Appendix B: Reserved Words.

Issue ClimateMaster controllers are an OEM version(s) of the I/A MNL LON controllers and can only be added as third party devices in SmartStruxure.   Environment ClimateMaster controllers SmartStruxure Cause ClimateMaster is a channel locked product and will not permit  WorkPlaceTech or WorkPlace Tech Editor to have access to the application via upload or download. Resolution ClimateMaster controllers can only be added as third party devices. For help on adding third party devices consult the StruxureWare Building Operation Web Help. There are three web help topics on adding third party devices: Enterprise Server Automation Server Third-Party Licenses

Issue Trying to pass data between a Niagara G3 station and an R2 station via oBix, but receive an error message, "Write Fault: java.lang.illegalStateException: name is already set." Environment Niagara G3 station with obix driver version 3.4.51 or earlier Niagara R2 station, any version Cause The cause of this issue has been corrected in newer versions of the oBix driver. Resolution This problem has been resolved in newer versions of the oBix driver.  Version 3.4.52 and newer will include the changes that fix the issue. The maintenance build 3.4.67 can be downloaded from The Exchange Download Center, and the obix.jar and obixDriver.jar can be extracted from it and installed in the station.