Building Automation Knowledge Base

Issue Satchwell "AMS" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. (Actuator Wiring) Product Line Field Devices Environment Satchwell “AMS” series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. Please refer to Replacement of Satchwell "AMS" or "AMSH" (high torque) series Spring Return Rotary Actuator Cause Obsolescence of Satchwell "AMS" series Spring Return Rotary Actuator. Resolution Replace Satchwell AMS Actuator with S-E M700 Actuator. The S-E M700 Actuator may be used to replace an existing Satchwell AMS Actuator. It should be noted however that the S-E M700 Actuator is suitable for use with 24 volt power supplies only, while the Satchwell AMS Actuator is a mains voltage device. The S-E M700 Actuator has an average power consumption of 30 VA and the use of an independent 230 / 24 volt Transformer rated 50 VA is recommended. S-E Transformer Type TR60 (341-3060-000) Please check the latest catalog for current equipment.

Issue No one can get through the door using the reader. Product Line Andover Continuum Environment Pinpoint Cause User may have inadvertently selected "disable keypad/reader access." This mode shuts down the reader. The REX works and left-clicking on the Pinpoint animation allows unlock, and right-clicking stills allows timed and permanent unlock.  Resolution Right-click on the Pinpoint door animation and click on "Enable Keypad/Reader Access" See Key for the standard Door Control Graphic for a description of the various animations used in the Pinpoint Door Control.

Issue Verifying Database returns Table Differences on a Server Client system Performing a database backup and restore is still functional. Environment I/NET Seven Server Client system Server PC, DbCreate Cause When the I/O server is shut down before all of the client PCs some objects were opened and never closed.  Resolution Restart I/NET on the Server PC Shut down I/NET on all the client PCs Shut down I/NET on the Server PC Use Db Create to Verify Database NOTE: The Server Client configuration should only be used if you expect the Server to run 100% of the time.  If you wish to perform backups or other maintenance use the process above or use the tool found on the Buildings Business Community here.

Issue How to remove the Alarm File on a Niagara R2 Enterprise Server. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause The easiest way is to delete the entire (logged data) database; however this will also delete all archived data (logs, alarms, etc.) from the Cloudscape database collected by the Enterprise Server station. For alternatives to deleting the entire logged data, see "Maintenance of the Alarm Archive File" in How to remove data for all logs prior to a specific date in a Niagara R2 Enterprise Server. Resolution To delete the entire database: Close WorkPlace Pro Stop the station Go to the Control Panel and Select Administrative Tools and Select Services (short cut) and Niagara, which should indicate "Started" Right Click on Niagara, and select "Stop" To delete or remove the APP folder (and all included files) from the station folder: Go to My Computer and Select Local Disk (C) and Select Niagara Select the Niagara system desired and Select Stations and Select the desired station Select the app file and Delete it All archived data including the alarms will now be cleared.  The station database will automatically re-create the APP folder and Cloudscape file structure, once it is restarted. Re-start the station:   Go to the Control Panel and Select Administrative Tools and Select Services (short cut) and Niagara’s Status should be blank indicating the service is not running Right Click on Niagara, and select "Start"

Issue The TAC Operator Panel (OP) will not show the controllers on the network and only displays "No Answer." Product Line TAC Vista Environment Classic Vista networks LNS Vista networks Cause Programmable Xenta controllers only support 2 Operator Panels per device. Resolution Each Xenta controller can only have two Operator Panels connected to it at once. To have more operator panels, ensure that you have at least one programmable Xenta controller for every two Operator Panels.  See "No Answer" on an OP when connecting to a Xenta 280/300/400 for some other situations that can cause this issue as well.

Issue Sigma and Windows Server 2012 Product Line Satchwell Sigma Environment Sigma 4.08 Windows Server 2012 Cause Is Sigma 4.08 supported on windows Server 2012 Resolution No version of Sigma is supported on a Windows Server 2012 platform except: Sigma 4.08 can only be installed on Windows Server 2012 when the software is used as a transition into EcoStruxure Building Operation ( EBO ) and used with the correct version of transition component. For full details of Sigma 4.08 versions, build numbers and operating systems supported, see What operating systems is Sigma 4.08 supported to run on?.

Issue After installing an update to SmartXKiosk, an error message is shown when trying to launch the app License file not found. Please contact Schneider Electric. Product Line EcoStruxure Building Operation Environment SmartX Advanced Display SmartXKiosk Cause The SmartXKiosk update (apk file) needs to be installed on top of the factory delivered version. If the current version of SmartXKiosk is removed before installing the update, some files are missing on the tablet. Also refer to Which address and port does the SmartX Controller Advanced Display use for activation for additional information regarding license activation. Resolution A full installer of the app is needed. Contact Product Support and request a full installer.

Issue A message indicates only one Personnel record processed when using the PIU Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause By default the CSVtoContinuumTransformation.xsl transform file sets the alias column to concatenate (TAC + SerialNumber).  Resolution The transform needs to be edited in a text editor (not IE) to change the concatenate line to be a unique alias. Example: (Before) This displays the alias records in the preview as TAC < select="concat(‘TAC’, SerialNumber) " value-of=""> (After) This will import the records correctly < select="concat(‘TAC’, EmpNumber) " value-of=""> If all was working at one point and the site was upgraded then the old PC may have the CSVtoContinuumTransformation.xsl that was working. If this is a new install, select a number that will be unique for the records. For more information on editing the PIU see the following article: Personnel Import Utility documentation

Issue A site has to replace a legacy device with newer hardware and wants a continuity of values being read into trend logs. Product Line EcoStruxure Building Operation Environment This has been tested for I/NET hardware replacement, but the process will work for any device which has values stored in the Extended Trend Log Cause The Extended Trend Log allows users to change the Monitored trend log attribute as needed for continuity of data. This process can be used to ensure that regulations are met regarding requirements for trend data. It is important to ensure that the new trend log is created in such a way that no significant time is lost between samples on the old log and samples on the new log. The Extended trend log will be the warehouse for the long term data of the two source logs to be stored.  Resolution In this example we are looking at an Extended Trend Log which has been collecting values for some time. To Ensure all values are transferred from the Old Log to the Extended Trend Log, Right-Click on the Extended Trend Log and select Activation>Force Transfer Edit the Properties of the Extended Trend Log and delete the Monitored Trend Log which was monitoring the old input value. Save the change to the Extended Trend Log. At this point the log will no longer collect data from it's original input source Locate the new location of the value being monitored. This could be the input an Automation Server, Field device or a logical output of a program. NOTE: Steps 6-9 show the basic process for creating an Interval Trend Log. This may change depending on the new device type or location. For creating I/NET trends, please see Using I/NET trends in StruxureWare Building Operation   Right Click on this new object and select New>Trend Select the identical type and use the identical (or similar) configuration settings. Click OK View a Trend Log list of the new Trend log to verify that it is functional. Edit the Properties for the Original Extended Trend Log Click on the ellipsis to change Monitored Trend Log setting so that the Extended Trend Log now references the newly created trend log. Save the Changes Right click on the Extended Trend Log object and select Activation>Force transfer. View the Extended Trend Log list. You should see the new values after the record of the property changes.

Issue The Xenta controller has limited memory free and causing download issues. Can I add existing Menta into HFB,s to free memory up? Product Line TAC Vista Environment Xenta controllers 200, 300 and 400 series Cause The Menta application is too large for the controller Resolution A HFB will actually use more memory than a application with no HFB's  with the same program. See Menta Advanced Memory Usage: BPR Size Calculator for more information on memory description and allocation.

Issue Can Blade Servers be used? Product Line Andover Continuum Environment Continuum installation at site on Blade servers. Not to be confused with virtual servers or environments. Cause A customer would like to use a blade server to install Windows Server 32-bit directly on to run Continuum. Resolution Not to confuse Virtual Servers with these Blade Servers, but there is no official support for Virtual servers on Continuum up to release 1.94. The Compatibility matrix details all the full supported system configurations that are qualified by our R&D department. Any systems running on Virtual servers are un-qualified. For the Andover Continuum Compatibility Matrix, visit Software and Firmware compatibility matrix for older versions of the traditional product lines. Now, to Blade servers; Blade Servers have not specifically been targeted with problems as long as the system meets the requirements found in the install guides. Be reminded that the Workstation need to have a USB security key port which needs to be seen by the Cyberstation software. The minimum hardware requirements for the latest Cyberstation 1.93: Intel CoreTM 2, Duo, 1.66 GHz or better 2 Gb RAM or higher 15 Gb free space CD ROM drive Video resolution: 1024 x 768 pixels Parallel or USB port Recommended Quad Core, 2 GHz or better 4 Gb RAM 30 Gb free space CD ROM drive Video resolution: 1024 x 768 pixels Parallel or USB port Blade Servers are often more energy efficient and save space in server racks.

Issue TAC 200 OTP Controller replacement battery information Product Line Field Devices, TAC Vista Environment Site with TAC 200 OTP Controller  Cause On-board battery is in need of replacement, Part number - 200-1005-000. Here is additional information: TAC 200 OTP compensator and optimiser TAC 200 OTP is a compensator and an optimiser. It controls the heating via a boiler output and a mixing valve or via two stages of gas boilers. TAC 200 OTP can be operated with or without a room sensor. The controller has an easy-to-use operator's panel and needs virtually no maintenance. TAC 200 OTP is also described in the following documents, all available in English: Data sheet TAC 200 OTP C-10-31 The data sheet contains a comprehensive specification of the controller and should be read together with the handbook (part number 0-003-1148). A brief instruction A small leaflet normally placed in a slot in the operator's panel (part number 0FL-3564). User's manual TAC 200 OTP The user's manual (part number 0FL-3563) is a description for installation and start-up, packed together with the unit. The contents are a condensed version of chapter 2 in this manual and a mounting instruction. Manuals are available in TAC 200 OTP User Guide, TAC 239W DHW User Guide. Resolution Replacement battery is 342200360 CAP, .22 F 5.5V RM5 

Issue I/A Series R2 OBIX Driver part number Product Line TAC IA Series Environment I/A Series R2 Enterprise Server I/A Series R2 UNC Cause In order for an I/A Series R2 Enterprise Server or UNC to function as an OBIX server, the Enterprise Server or UNC needs to be licensed for it. This is required for integration to I/A Series G3. Refer to Configure oBIX to integrate a Niagara R2 station and a Niagara G3 station. Resolution Part number: IA-DRV-OBIX This is the part number required for each Enterprise Server / UNC that needs to function as an OBIX server.   *Update - I/A Series R2 has been discontinued. As of January 1, 2015, the part number IA-DRV-OBIX will no longer be available for purchase. 

Issue Error while creating the Continuum DataBase in 64-bit Operating System. SQL Server Installation Package cannot be opened. Microsoft SQL Server 2005 Setup SQL Server 2005 Setup cannot continue because the installation package could not be opened. The installation package has a missing file, or you are running a 32-bit only Setup program on a 64-bit computer. To continue, verify the SQL Server 2005 package you are running is supported on WOW64. If you are certain that you are running a supported SQL Server 2005 package, and you continue to see this message, contact the application vendor. Product Line Andover Continuum Environment Continuum 1.93 and below 32-bit Operating Systems Cause Continuum 1.93 and below versions do not support in 64-bit Operating Systems. Resolution Install Continuum in a supported Operating System. Read and follow the Continuum compatibility matrix before installing.   Download the Andover Continuum Compatibility from Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue When saving program changes adding new data sharing points an error is displayed; Infinity controller error: The controller has reached its BACnet binding limit. Product Line Andover Continuum Environment Continuum Cyberstation Cause The controller has reached its known devices limit and is rejecting any further target devices from being added. The known device limits are 255 for bCX controllers and 32 for b3 controllers. See Limit of how many devices a Bacnet controller can know about (Known devices)  for more details. Resolution Make a change in the controllers to reduce this number of known controllers by modifying how much data is shared and/or reduce the number of Workstations that alarms are delivered to. Once this is done then restart the controller for the known devices table to be rebuilt.

Issue Can a BACnet Automation Server and b3's be programmed offsite with temporary IP addresses? Are there any considerations to be made when moving the system to site and configuring with new IP addresses for the Enterprise Server and Automation Server? Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server b3xxx Controllers Cause Do not have complete IP address details for the new project but need to start programming the controllers in the office. Not sure if there will there be any issues when moving this to site. Resolution You can do this programming with a temporary IP address for the AS and then when you get to site Change the AS IP address to whatever is required. See Changing IP address of Automation Server that explains how to change the AS IP address.

Issue A network of GCM-86000s with EtherNet NIMs does not have bi-directional communications between all GCM/ NIMs. It is a shared network with routers. Some symptoms reported include: A GCM/ NIM may be able to send to some GCM/ NIMs, but not to others. A GCM/ NIM may be able to receive data from some GCM/NIMs, but not from others. A GCM/ NIM may be able to send to a GCM/NIM, but not receive data from that GCM/NIM. You might be able to "ping" all GCM/NIMs on the network, and ACCESS all of them from the GCM menu, but still have issues as in 1-3 above. Product Line TAC IA Series Environment GCM-86000 series (including LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK) EtherNet NIM (GCM-ETH-001) Shared (customer's) EtherNet LAN with routers Cause In the NIM block of one or more of the affected GCM/ NIMs, the IP Multicast address (IPMLT) is set incorrectly. In the following example, the NIM block parameters were taken from a network of four GCM/NIMs, experiencing all four of the issues noted above.     GCM#1 GCM#2 GCM#3 GCM#4   5.4A 5.3A 5.4A 5.4A   11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.019 010.020.000.019 010.020.000.019 010.120.000.019 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 Resolution On a shared network with routers, the IP Multicast address (IPMLT) should be the same as the Panel IP address (PNLIP); IPMLT = PNLIP. Using the appropriate FLASH clear procedure, and set the NIM block parameters so that IPMLT = PNLIP. In the example below, make the changes to the IPMLT as high-lighted in yellow.   GCM#1 GCM#2 GCM#3 GCM#4 GCM Rev. 5.4A 5.3A 5.4A 5.4A NIM Rev. 11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 See the Nim Networking and Configuration Guide, F-25955-4, Chapter 2, "GCM Shared Network Address Guidelines (Routed Network)" for details. For EtherNet NIMs with firmware revisions 11.2P or 11.2T, see "Special NIM Address Switch Functions" for the REVISED FLASH clear procedure. For EtherNet NIMs with firmware revisions 11.1F or earlier, see "Flash clear" procedure for GCM Ethernet NIMs (GCM-ETH-001) with firmware prior to revision 11.2P.

Issue TGML Graphic Alert: ReferenceError: "test" is not defined. (cmd#16) Product Line TAC Vista Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML has used a variable that has not been defined. Resolution Determine which script tag is generating the error. When did the error occur? When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 16 of the code. The variable name is in quotes.  In this example, find where a variable named "test" was used. Verify that the variable has been declared and defined prior to being used. Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue I/NET Seven running on a Windows 7 computer that has an issue with fields not aligning as shown below: Product Line TAC INET Environment I/NET Seven Cause This is caused by increasing the text size of the workstations display from the default setting of 100%.  It will occur on any Operating System not just Windows 7. Resolution Make sure the Display settings Text setting is at the "Default setting (100%)".  If it's any larger then it will distort the text and editor titles will be miss aligned with the text displayed in the summary / editors.  You change this as follows: Windows 7:  From the Control Panel: - Select Appearance and Personalization Under the heading Display select “Make text and other items larger or smaller” Change setting is set to Smaller – 100% (default). You will then need to log off and then back in for these changes to take affect. If this does not resolve the issue, refer to Windows Alignment Issue for I/NET display. Windows XP / Server 2003: From Control Panel: Double-click on Display Select the Settings tab (top right) Click on the Advanced tab Within the Display section select the "Normal size (96 DPI)" from the DPI setting drop down box. A restart of the workstation may be required to apply these changes.

Issue It is not possible to extract a Menta file directly from a Xenta programmable. If a backup of the Menta file, or a backup of the Vista database is not available, there is no way to extract the program from the controller. "File object contain no actual MTA file" when trying to open a Menta file. Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Going out to a job site without a database backup, or a backup of the Menta applications (.MTA), leaves no way to view the Menta that is running in a Xenta programmable controller. Resolution Options are: Find a backup of the .MTA Menta application that has been downloaded previously into the controller. Find a backup of the Vista database.  Menta files are stored in the Vista database for each programmable controller. To extract a Menta file from a Vista database, the preferred method is described in Get all MTA files saved from a Vista Database. To extract the files one at a time, right-click on the controller and select Edit. Connecting to a live controller, it is possible to view all public values inside the controller and to extract a .COD code file.  Unfortunately, these cannot be used to create a .MTA to view the logic.