Building Automation Knowledge Base

Issue In WorkPlace Tech Tool, the Definition tab of a Custom Object, right click on any object to request Properties info. The response is an error "Exception happened finding Visio shape". What does this mean? Environment WorkPlace Tech Tool 5.7.x Cause There was an error in Visio. The custom object may have been copied from a newer version of Visio to an older version. There may have been an error when creating the custom object. Shapes may have been added to the custom object when opened directly in Visio instead of being opened in WPTech. Some other corruption to the drawing took place. Resolution Do a “Rebuild Application”, and then try opening the shape properties again.  If this does not work, try creating a new custom object, and then try copying the contents of the old custom object definition page into the new custom object definition page (while in WPTech).  Then delete the old custom object, and then try the shape properties in the newly created custom object.

Issue Not possible to get a Xenta Server / 911 online in TAC Vista. It is possible to ping it and connect to it via a Web browser using ports 443, 80, and Port 1068 is open, but it is not possible to get online in Vista. Product Line TAC Vista Server Environment TAC Vista TAC Xenta 911 TAC Xenta Server Cause The problem, in this case, was that another Vista server was connected to the Xenta Server / 911.  This could have been from a technician or the customer who started Vista with this database loaded and had the device online in their Database. The Xenta Server / 911 will only communicate with one Vista Server at a time and will close the connection if another Vista tries to communicate with it.    Using Wireshark it is possible to monitor this scenario as shown below:  Packet number 57439: Vista is trying to establish communication with the Xenta Server or 911( sending an SYN). Packet number 57440: The Xenta sends an acknowledgment on the SYN from Vista, but with the window size set to zero, this is because the Xenta can't buffer information as a computer does. Packet number 57441: Vista  sends an acknowledgment on the message from the Xenta Packet number 57448: The Xenta sets the correct window size. Packet number 57449: Vista starts to communicate Packet number 57452: The Xenta closes the communication to the Vista server  Resolution Ensure only one Vista server is started when the Xenta server / 911 is included in the database.

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

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 When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor Cause Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.

Issue nvoSpaceTemp from TAC Xenta 100 series used with the room unit STR150 does not read temperatures greater than 33.4 °C (92.3 °F). Product Line TAC Vista Environment ZBuilder Xenta 121 Xenta 122 STR Sensor Cause The STR150 and the Xenta 100 line of controllers are capable of displaying temperatures greater than 33.4 °C (92.3 °F) or less than 8 °C (46.4 °F). However, the communication protocol between the STR150 and the Xenta 100 series is limited and thus restricts the temperature that the TAC Xenta 100 can read from the STR150 device. Resolution The STR150 data sheet states that temperature range transferred to a TAC Xenta 100 device is limited to 8 °C through 33.4 °C (46.4 °F to 92.3 °F). If temperatures outside of that range are needed an STR100 (simple 1.8k thermistor) or an STR-350 (communicating Lon stat with display) could be substituted. The ranges of those devices connected to a TAC Xenta 100 device are as follows: STR100: –10 °C to +50 °C (14 °F to 122 °F) STR350: 5 °C to 45 °C (41 °F to 113 °F)

Issue Time Zone Database shows +0 for all time zones when the platform date is in 2016. IA Series G3 version 3.6.407 IA Series G3 version 3.7.108 IA Series G3 version 3.8.41 Product Line TAC IA Series Environment IA Series G3 versions 3.6.407, 3.7.108, and 3.8.41 Cause This error appears when listing the contents of the Niagara Time Zone database where the Time Zone Database shows +0 for all time zones when the platform date is in 2016.  The issue is related to an error within the 3.8.41 baja and hx modules and only affects the display within the Platform view only.  The actual behavior and operation of the Time Zone remains accurate.  Prior IA Series G3 versions (e.g. 3.8.38, 3.7.106, and 3.6.406) or earlier will not exhibit this issue. Resolution Download and upgrade the baja and hx modules available in the latest consolidated patch files. baja 3.6.407.3 (or higher) and hx 3.6.407.1 (or higher) baja 3.7.108.3 (or higher) and hx 3.7.108.1 (or higher) baja 3.8.41.2 (or higher) and hx 3.8.41.1 (or higher) The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area (reference Latest consolidated patch files for I/A Series G3 maintenance builds with details).  Download and install the appropriate patch for the version.

Issue A McQuay MicroTech 2000 water source heat pump controller may be addressed as a Level 3 device under an MCG (MicroTech Communications Gateway). This can be confusing when addressing WSHP1 blocks in a SIM-MTECH. Environment Network 8000 SIM-MTECH McQuay  MCG (MicroTech Communications Gateway) McQuay MicroTech 2000 water source heat pump controllers Cause The MCG needs to use an Echelon communications protocol with the water source heat pump  (WSHP)controllers, which uses level 2 internally, and puts the WSHP controllers at LEVEL 3 Resolution The way to address the WSHP blocks under the MCG is HBYTE = 1, LBYTE = x, where x is the address of the controller.  Unlike earlier McQuay controllers where the unit address is set by rotary hexadecimal switches, the addresses of the MicroTech 2000 heat pump controllers are set in software by the McQuay  technician who commissions their network. Click here to see an excerpt from F-26133, Systems Integration Module- MicroTech, SIM-MTECH. See Fig 2.1, and Table 2.1, pp 2-2 through 2-4

Issue The need to verify the proper wire positions on a Xenta Server device Environment Vista XBuilder Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Installing a Xenta Server device on a network Resolution Table 2.1: Connections on the Xenta device Position Description 1-2 Power supply. Minimum cross-sectional area 0.75 mm2 (AWG-19). 1 (G) - 24 V AC (or DC+) 2 (G0) - Ground 3-4 LonWorks TP/FT-10 connection 3 (C1) 4 (C2) 5-8 Internal port A RS-485 A connection 5 (RX/TX+) 6 (RX/TX-) 7 (RX+) 8 (RX-) Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 9 Ground 9 (G0) 10 Fail-safe Note Jumping these pins together while cycling power will flash the device and load the minimum amount of drivers necessary for communication. If an IP address has already been assigned fail-safe will NOT remove it. 11-15 Unused 16-17 Ground 16 (G0) 17 (G0) 18 Unused 19-20 Internal port C RS-485 C (SDLC) connection 19 (RX/TX+) 20 (RX/TX-) 21 Internal port A RS-232 A connection. Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 22 Internal port B RS-232 B console connection 23 Ethernet 10Base-T connection 24 Service pin Caution G0 equals GROUND. Only G0 may be connected to protective ground.

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 In some cases, the event and trend databases can grow really big, although not all the space in the files is used. Therefore, one needs a way to verify that vacuuming the database will help. Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Definitions are documented here: https://www.sqlite.org/pragma.html  PRAGMA schema.freelist_count; Returns the number of unused pages in the database file. PRAGMA schema.page_count; Returns the total number of pages in the database file. PRAGMA schema.page_size; Returns the page size in bytes (B), which must be a power of two between 512 and 65536. Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: SELECT (SELECT freelist_count FROM pragma_freelist_count()) AS FreeList_Count, (SELECT page_count FROM pragma_page_count()) AS Page_Count, ((SELECT page_count FROM pragma_page_count()) - (SELECT freelist_count FROM pragma_freelist_count())) AS Used_Page_Count, ROUND(CAST((CAST((SELECT freelist_count FROM pragma_freelist_count()) AS REAL) / CAST((SELECT page_count FROM pragma_page_count()) AS REAL)) * 100 AS NUMERIC),2) AS Percent_Free, (SELECT page_size FROM pragma_page_size()) AS Page_Size_B, ROUND(CAST(((SELECT freelist_count FROM pragma_freelist_count()) * (SELECT page_size FROM pragma_page_size())) / (1024.0 * 1024.0) AS NUMERIC),3) AS Estimated_Space_MB; Click the blue play button above the Query tab.  Review the Percent_Free and Estimated_Space_MB, which will be returned at a minimum, to decide if you want to perform the 'vacuum' command. The vacuum process is slow, as it was designed to operate in the background. Shrink the SQLite event and trend databases. If the Percent_Free is above 80, this is the better option: Shrink the SQLite event and trends databases (Option 2) by creating a new file.

Issue Problem with Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters The Controller was unable to poll all of the meters installed on the field bus. Environment Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters Cause When connecting multiple Class 3000 meters to a field bus, ONLY the last Class 3000 meter in the field bus string should have the biasing resistor pack installed. Having multiple termination resistors will load the bus down. Resolution All other biasing resistors should be removed from J17 on meters attached to the field bus. If there is still a problem Change the E-Mon "key2000" to the RS232 protocol. Using the E-Mon Repeater will provide a stronger RS-485 signal to drive their devices. Put the X-Driver on an RS-232 port of the controller.

Issue Changing BACnet Port for Continuum Cyberstation Environment Continuum Cyberstation BACnet controllers Cause Changing the BACnet Port number that Continuum Cyberstation communicates on Resolution By default Continuum Cyberstation communicates on port 47808 in hexadecimal that is BAC0. The BACnet controllers BCX & B4920 have the ability to have their default ports changed. If you change the BACnet port of a BACnet master and want to communicate with the Continuum workstation, you'll need to make a registry change in each workstation. Changing the Continuum Workstation BACnet port This key location is different in 32-bit and 64-bit systems. In 32-bit; the key to change is located in the registry at the path "HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings". In 64-bit; the key location is now under the "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Andover Controls\Continuum\Settings\" key. Once you're at that path you'll notice a key named "Cyberstation Port" .The value is stored in hexadecimal, so to change it make sure that you enter your new value in hexadecimal. After changing the value in the registry, the Continuum Cyberstation will need to be restarted. Changing the BCX or B4920 BACnet port To change the port on the BACnet controllers either BCX or B4920, open the configuration page in Internet Explorer by putting in the IP address and edit the port settings to the port number that you are changing to. This number will be in regular decimal format. Once changed make sure you save your change and commit the changes to the controller which will restart the controller. Changing the Continuum Workstation BACnet port example. Open the registry editor from Start\Run and enter regedit from the workstation. and explore down to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings and open the Cyberstation Port key and enter BAC1 which is hex for 47809. If you have the Continuum Cyberstation running you'll need to restart the Cyberstation Once restarted, open the continuum explorer and select the Root and right click and select find new BACnet devices. The controller you have changed will appear as will all of its MSTP devices. Changing the port on a BACnet master controller example. To change the BCX/B4920 BACnet port to 47809 which is BAC1 in hexadecimal. Then log onto the configuration page of the BCX and change the BACnet Port Number -UDP, notice it is displayed in hex but on the controller configuration page you'll change the number using regular decimal. We'll change this to 47809, apply our changes and then on the left hand side select commit and apply on the commit page, which will restart the controller and the new port changes will be in effect. NOTE: If you already have BACnet network established, first delete my whole BACnet side, since after making port changes you don't want other controllers making an attempt to communicate with the previous port number in its known routing table.  IMPORTANT: Anytime you edit a registry, make sure you have backed up the registry and have a contingency plan in case you edit or delete some that that you should not have.  

Issue Alarms need to be sent to specific Workstations and then escalated to other Workstations if they have not been acknowledged within a specific amount of time. Product Line EcoStruxure Building Expert Environment Security Expert Cause Documentation does not describe specific steps for how to configure alarm escalation. Resolution You will be able to do the alarm escalation with Security Expert by using the Alarm Routing options under the Events Menu. 1. Create your Workstations by going to Events | Workstations. The name of the new Workstation object in Security Expert will need to correspond to the actual Windows PC name for alarms to be routed properly. 2. After you have created all of the Workstations you will need to create Workstation Groups under the Events menu. One group for each level of alarm routing that you want to do. If you have three workstations and want to route from one to the next to the next, then you would need to create three Workstation Groups and add one Workstation to each of them. 3. Next you will need to create an alarm routing list under Events | Alarm Routing. On the Workstation Groups tab add the time for Transfer After (this is in seconds) which is when the alarms will be routed to the Workstations in the next Workstation Group. Set the Routing Order for those groups, the first group is 0. Next set the Transfer Priority if you have specific alarms that are to be routed to these Workstation Groups, leave blank if all alarms are to be routed. Set the routing group active to enable routing. 4. The last bit is to go to your Alarms that you want to route and add the routing list you created in step 3 to the Alarm Routing List field. This will now route these alarms to the Workstations you've configured.

Issue Before installing Access Expert on premise server software, the Mongo DB must be installed and the Mongo service started, this requires creation and editing of a configuration file where the data and log directories are specified. There have been many cases of YAML errors seen during V3 on premise installation when attempting to start the Mongo service. Product Line EcoStruxure Access Expert Environment V3 Mongo DB Cause The YAML parser that reads the "mongod.cfg" file is very sensitive to the format of the configuration file including some very strict rules about spaces, double quotes and back slashes. When editing the file, it helps to setup the text editor to display ALL characters which will show any hidden characters that might be causing a parsing error. Ex. In Notepad++: Select View>Show Symbol> Show All Characters Resolution Space is needed between key and value pair. Enclose paths in double quotes. Double back slash required in Windows systems.

Issue Sigma IC-GEN 4.05 SEB and supported operating systems Environment Sigma IC-GEN release 4.05 SEB Cause New installation of IC-GEN and customer wants to know the latest version and its supported operating system(s). Resolution The latest version of Sigma IC-GEN is Sigma IC-GEN 4.05 SEB. Release 4.05 SEB IC-GEN provides rebranding to Schneider Electric. There are no other changes except for new build and release numbers. This release is shown as Sigma IC-GEN Build 3.43.07 in the installer, uninstaller and ‘About’ box. This release supersedes the previous Release 3.17 for IC-GEN (shown as Build 3.34.12 in the About box and Build 3.34.24 when uninstalling). This version is supported to run on Microsoft Windows XP Professional (32-bit) and Microsoft Windows 2000. (Microsoft Windows Vista and Windows 7 are not supported) Refer to 'Sigma Release 4.05 SEB IC-GEN' release notes for details. The IC-GEN 4.05 SEB software can be downloaded from the Exchange Extranet. Once logged on, go to 'Products' > 'Satchwell' > 'Sigma' > 'Downloads' > 'Upgrades and Software'. The release note can be downloaded from 'Products' > 'Satchwell' > 'Sigma' > 'Release Notes' > 'Options'.

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.  

Issue After launching WebClient logon screen appears but attempt to logon results in "Webclient is unavailable"  Product Line Andover Continuum Environment Windows Vista Windows 7 WebClient Cause Incorrect Internet Information Services (IIS) configuration. Resolution 1. Open Internet Information Services Manager 2. Expand the Computer Name in left pane and click on Application Pools in treeview 3.  Select DefaultAppPool and click Set Application Pool Defaults 4. In Application Pool Defaults dialogbox select Identity under Process Model. A selection control should appear in the second column. Click this button 5. Under Built-in account select Network Service in the dropdown listbox. Click OK 6. Click OK button in Application Pool Defaults dialogbox

Issue What type(s) of 125 kHz proximity cards are supported by Security Expert Card Readers? How to configure Secure Expert to read an Indala card (125 kHz)? Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Reader Cause Card readers work by modulating the electromagnetic wave in different ways to resolve between 1s and 0s. There are several different ways to bring card data across 125 kHz; ASK, FSK and PSK. ASK : Amplitude Shift Keying FSK : Frequency Shift Keying PSK : Phase Shift Keying Since the technology used is determined at the hardware level,  a reader would need to have the hardware to read a specific type. Security Expert 125 kHz readers make use of FSK only, which means that e.g. Indala cards (125 kHz PSK technology) will not work with them. Resolution Use FSK technology 125 kHz cards with Security Expert Smart Card Readers.

Issue A third party BACnet device does not support segmented messages but the bCX4040 does. Can the two devices communicate? Environment Continuum BACnet MS/TP MSTP bCX Cause A third party boiler BACnet MS/TP interface card is having difficulty communicating with a bCX4040. The manufacturer of the interface card has commented that the Continuum bCX uses segmented packets and the Bacnet interface card cannot communicate with a segmented packet delivery system.  Are these devices incompatible? Resolution The problem should not be related to message segmentation. This is because the bCX will try to send a segmented message and the third party device should send a response to the bCX indicating that segmentation is not supported. The BCX will then send only non-segmented messages to the device. So, the bCX supports message segmentation but can do both segmented and non-segmented messages on the same MS/TP bus.  Get an MS/TP capture with both devices on the wire while doing a Find BACnet Devices request from CyberStation and send to Product Support for review.

Issue How to upgrade from Continuum v1.4 Product Line Andover Continuum Environment Continuum Cyberstation Cause What are the steps in upgrading from Continuum 1.4 Resolution For a smaller site it may be quicker and more reliable to install the current Cyberstation version, then upload from the controller, this has the advantage of ensuring you have a clean database. The alarms, workstations etc, would needs to be rebuilt from scratch. If the current database is clean (Passing continuum analyzer is NOT proof of a clean database, only a helpful initial step) and it is decided to upgrade the existing database from 1.4, you will first need to upgrade to v1.5x, then follow Upgrading Continuum from 1.5x to Continuum 1.9x. The overall process can be a little complex as various operating systems need to be available/installed. See the Continuum Compatibility Matrix for details for the PC and Controller firmware requirements Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation See the Continuum installation guides for the PC hardware requirements The v1.4 graphics could be .pan or .pin files. The .pan would need to be re-drawn as .pin files, in order to be compatible Run Continuum Analyzer before/after each upgrade, also run Continuum to ensure it runs correctly.

Issue The limits on how many AI/AO/BI/BO/RI/RO, Function Block number, Constant number, public signal number...etc.. one can create in one Functional Block Application? Environment StruxureWare Building Operation site with Functional Block Application Cause What are the limits on how many AI/AO/BI/BO/RI/RO, Function Block number, Constant number, public signal number...etc.. one can create in one Functional Block Application? Resolution There are no limits about how many blocks that could be created, but the Function Block parser has a memory limit. When this limit is exceeded an error text is prompted to the user. There is no way to tell if a site is getting close to that limit.