Building Automation Knowledge Base

Issue Several doors need to be removed in an existing I/NET Seven System. What is the proper way to do this? Product Line TAC INET Environment I/NET Seven with Access Control Cause Steps to remove Doors in an existing I/NET Seven System Resolution It should be sufficient to just deselect the door from the tenant and then NETCON on one equalized client, the file master, or Standalone PC. If the door physically goes away, the next time an operator enters an individual or group that had that door it will display a * for the offline/deleted door. At that time just select "Unselected" option and that door will be removed from that list. If all trace of the door needs to be removed: Remove all access privileges from a door. Be sure to check System View to verify they are all removed. Remove the door from all tenants Connect to the Controller and select Edit>Controller>Doors Delete the Door Close of the Door editors and select Edit>Host Computer>Network Configuration Penetrate to the Door level and delete the door objects. Next, In the Resident I/O editor delete any points associated.

Issue I/NET Cold Case "Card Reader" Mystery. Product Line TAC INET Environment I/NET site with Access Control Cause There are some basic differences between the Indala/Motorola and HID/Dorado card readers. Resolution Please look at the attached link point for this information. Mystery of the card readers.doc

Issue Need to examine an Xenta 28x or 30x but don't have the MTA file Environment Xenta Programmable controllers Xenta 281, 282, 283, 301, 302, 401, 401:B Menta Cause It is not possible to extract a Menta .MTA file from an existing controller. The function block diagram is not downloaded or stored in the Xenta unit itself. You must have a backup of the .MTA or the Vista database. It is, however, possible to extract the machine code file (.COD) and it is also possible to view live values in table format of any public value in the Menta file. Resolution Open Menta Connect to the controller via serial cable Hit F12, then connect. Select upload and enter a name for the .cod file that will be created. You'll get a list of all of the public signals (which will usually include the physical IO), will be able to see the values and control them if they're set to R/W. Keep in mind that the program will still be running and will change them again upon the next program cycle. You may also be able to detect that the program has failed if the signals are not changing.

Issue Performing database maintenance with Vista 4.5.0 Product Line TAC Vista Environment Vista 4.5.0 SQL Server Cause It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database. Resolution Vista has a means of backing up databases on a Vista Server.  It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database.  The Vista database probably won’t grow very much after the initial engineering activity but the event and trend log database grows as events are received in Vista.  In many installations maintaining an archive of event data is required so that is another reason for backing up the database.  This paper presents a way to accomplish the backing up of the Event and Trend database and creating an archive file. Before the backup process can be implemented it is first necessary to have a good estimate of the Event and Trend Log traffic anticipated for the installation.  In the Vista 4.3.0 Technical Product Information (TPI), Ref No: C88-1-D43, there is section entitled Strategies for Calculating and Controlling Database Size.  On page 5 the method for determining database size is explained and used in the following example: Right clicking on the $Backup_LDB object in the Server View brings up this dialog.   Note that this example has an Event and Trend database that has reached 1121 (MB) in size.  The default Size Alarm Limit is shown to be 1640 and if the database grows past that size, Vista may not operate reliably. The TPI states on page 4 that events contain on average 2Kb of data.  Combining that value with the expected traffic provides a reasonable estimate of the database expansion rate.  If the installation traffic estimate is 4000 Events and Trend samples per day, the database expands at the rate of 8Mb per day.  If the installation traffic estimate is 10,000, the database expands at the rate of 20Mb per day. A conservative approach would limit the size of the active database to half of the alarm limit.  That means the backup process must be done so that the size does not get to 820Mb.  At 10000 Events and Trend samples per day that value would be reached every 41 days.  Vista is designed to allow Event driven backup operations and the closest choice it offers to the 41 days is once a month so that is what will be chosen. The configuration of backup is done in Vista Workstation by opening the Properties of the Workstation object in the tree.  The first step is to select a location for the backup files to be saved.  In the example shown below it is the folder outlined in red.   The “Max number of files” limits the number of backups that are retained by Vista on the hard drive.  The number chosen here was two (2).  The procedure that is described further down will actually move backup files to new directories which could be a network drive or a CD/DVD rom.  (The latter option requires operator action so it might not be the most desirable especially since backups are usually done at off times when an operator might not be available)  Next the event that is to trigger the backup must be defined.  The configuration of when the backup is done is set on the Log Backup tab of the Vista Server Properties dialog.  In the example shown below the backup is scheduled to occur on the first of every month at 12:40AM. The selection of Event object is made from the options made available by the browse button.     The browse selection brings up the Select dialog from which the selection of Event type and properties is done.  In the following example the selection is Monthly.   Right clicking on the $Event_LDB object opens the properties dialog box to configure the Event_Month object.  The final configuration option is what to do with older records.  Vista will remove Events from the database if you so desire.  The removal does not shrink the database but does make space available for new events to be written without expanding the size of the database.  This is the key to keeping the database from exceeding the Alarm Limit. The Event Log tab provides a way to delete old records from the database.  In the example shown below records older than 30 Days will be deleted after the backup that was done be the Event_Month object has been completed.  This means that each month the backup should have the most recent 30 days of Events and Trend samples.   The final step that can be taken is to also copy the backup file to a server that is backed up or to a CD/DVD Rom. This operation creates an archive in which Event and Trend data is stored.  Windows task scheduler can be used to run a cmd at some time after the backup operation was scheduled.  For the above example schedule it to run a 1:00am on 1 st of each month.  If backing up to a network drive create a folder such as shown below.  J:\Engineering\Vista Event Log BU.  In order for the task scheduler to run it is necessary to setup a user account on the pc that is not related to any actual user.  I added a user to the User group named, vista xcopy dbmgr.  This will be the user account used by the task scheduler.  The Vista backup folder must have modify/write permissions for this user and the folder into which the backup is going to be copied must have Full control.   The command line for this example is shown below: C:\WINDOWS\SYSTEM32\xcopy.exe "C:\Program Files\TAC\TAC Vista 4.5.0\Db2\$bkp" "J:\Vista Event Log BU" /M The Windows task scheduler is configured in the Control Panel, Scheduled Tasks as shown below:   In the Run as: box enter the name of the new User created described above: vista (xcopy dbmgr) Schedule the task to run on the first of each month at 1:00AM.   The backup files can be restored to a Vista Server that is not performing actual site monitoring.  This method is only way the “archived” event and trend data can be viewed as of Vista revision 4.5.0.

Issue While attempting to import files to through WorkStation or libraries from the Script Editor, the program crashes with the error message below. It can even happen when doing mass create or mass change, or when adding columns to a list view. "StruxureWare Building Operation has stopped working" Environment Building Operation WorkStation Building Operation Script Editor Cause It has been identified that a program called "F-Secure Key" interferes with other installed programs, and can ultimately leed to other programs crashing. "F-Secure Key" hooks into the Microsoft dll "UIAutomationCore.dll" which is used to idenitfy and manipulate elements in the user interface. If "F-Secure Key" is installed, it can easily be identified, as you will see a blue circle with a key when logging in through WorkStation Resolution Uninstall all "F-Secure Key" related program from "Programs and Features" in the Control Panel on the PC

Issue An error occurred while installing DSS: MSDTC 2 Product Line TAC Vista Environment DSS Installation MSDTC Cause Users that get the following error message when installing Vista ‘Error occurred when installing DSS’ can be caused by the MSDTC (Distributed Transaction Coordinator) not being able to start. In the service list Distributed Transaction Coordinator (MSDTC) is not started and it fails when you try to start it. Resolution Check the windows event log. If you see the following error events logged in the Application log:  Event Type: Error Event Source: MSDTC Event Category: LOG Event ID: 4163 Description: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file. Event Type: Error Event Source: MSDTC Event Category: TM Event ID: 4185 Description: MS DTC Transaction Manager start failed. LogInit returned error 0x5. Follow the steps in http://support.microsoft.com/kb/916926 to fix the problem. For other possible causes for this problem see: An error occurred while installing DSS: MSDTC An error occurred while installing DSS: The account already exists An error occurred while installing DSS:COM+ installation corrupt An error occurred while installing DSS: Cannot Start Service

Issue The properties of a BACnet or Infinet Schedule shows Next transition time as 2106-02-07 07:28:14. Where does this date come from? EBO BACnet schedule shown below Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 BACnet Schedule Infinet Schedule Cause The reason it displays the date of 7 Feb /2106 is that there are no events in the controller for the current week. Resolution The next transition time is evaluated and will display the next transition time when the following week has an event scheduled.

Issue S-E L2SV Linkage Kit and S-E L7SV Linkage Kit compatibility with Satchwell Plug and Seat Valve Bodies. Environment Satchwell 1 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 2 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 3 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 7 series Plug and Seat 2-port and 3-port Valve Bodies. Cause Use the correct S-E Linkage Kit with Satchwell Plug and Seat Valve bodies. Resolution 1.  Observe specification number of Satchwell Plug and Seat Valve Body Generally where a Satchwell AL series Linear Actuator is fitted to a Satchwell plug and seat Valve Body, the Actuator may be replaced by an equivalent S-E Forta or MV15B series Linear Actuator and appropriate S-E Linkage Kit. It should be noted however that neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series MZ/MZF or a Satchwell 7 series VZ/VZF plug and seat Valve Body. The internal screw threads of the Neck Adaptors included in the S-E L2SV Linkage Kit (880 – 0124 – 000) and S-E L7SV (880 – 0126 - 000) Linkage Kit are compatible with the external screw threads on Satchwell 1, 2 & 3 series Valve Body necks only. The external screw threads on Satchwell 7 series Valve Body necks however differ to those on Satchwell 1, 2 & 3 series Valve Body necks. Consequently neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series Valve Body. A S-E Forta series Linear Actuator may be mounted on a Satchwell 7 series Valve Body however using Linkage Kit 880 – 0135 – 000.  No equivalent Linkage Kit is currently available for use with the MV15B series Linear Actuator. The Satchwell Valve Body series may be determined from the Valve Body specification number stamped on the Valve Body Identification Collar, where the single middle digit of the specification number denotes the series. In the case of a Satchwell 7 series Valve Body for instance the single middle digit of the specification number will be the number 7 (e.g. 626 – 7 – 402)

Issue Remote Client Configuration Issues I.Net 2.31 and prior Product Line TAC INET Environment I/Net Seven version 2.xx with need for Remote Client configuration. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.21 to 2.31 release. Resolution There are two different configurations for the Remote Client setup in I/Net Seven. Clicking the links below will open a PDF document which will show how the communication should be setup. This configuration is in the I/O Server under the current profile and can be found in the Workstation Options.   *IP Addresses are for demonstration purposes only.

Issue System alarm message, Physical device not defined/configured, in the alarm window. Product Line TAC Vista Environment TAC Vista (all versions) TAC Xenta programmable controllers Cause This message is displayed when there is a TAC Xenta 401/30x/28x that is attached to the physical network, but the name is not in the TAC Vista database. It is there to alert that there are unconfigured controllers on the network. Resolution Download to the controller from TAC Vista Remove the controller if it is not needed. For an alternative cause and resolution for the message, see Physical device not defined/configured.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

Issue How is the MAC ID for an AS calculated? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause MAC ID for an Automation Server calculation Resolution A Mac address ID of an IP level Automation Server is made up a 48 bits. The first 3 bytes are unique to each vendors organization and has a unique IEEE 3 octet identifier. The last 3 bytes are created by the individual companies and EBO's last 3 bytes are automatically pulled down from a database to a buffer in the product level test equipment where one is assigned for each tested AS, printed at the side sticker and logged in the Trace test report. Example  00-50-06-00-D0-15

Issue The ACX 57xx series controller supports up to 2 xP or xPB (bi-directional) expansion modules, plus a display for extended input and output configurations. The ACX 57xx series controller is compatible with all of the TAC expansion modules. For more information about expansion modules, see the xP Expansion Module Reference, 30-3001-840 and/or the xPB Expansion Module Reference, 30-3001-883. What are the valid channel numbers for expansion IO on the ACX5740/5720? Environment CyberStation ACX5740 ACX5720 Cause The expansion IO channel number assignments is different in the ACX5720 due to the fact that it has only half the onboard IO as the ACX5740 Resolution The ACX5740 has 12 onboard inputs and 4 onboard outputs, therefore the first expansion input channel is 13 and the first expansion output channel is 5 The ACX5720 has 6 onboard inputs and 2 onboard outputs, therefore the first expansion input channel is 7 and the first expansion output channel is 3

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue Nuisance forced door alarms are showing when exiting through doors with panic bars. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Need to stop a forced door event from registering an alarm notification when a doors panic bar is used. Resolution Enable the feature "Forced Door Sends Door Open" on the Door Inputs tab.

Issue Which files can be backed up safely with an automatic/manual method. Environment Sigma (All) Cause Backing up a live Sigma system is not a recommend as copying ‘live open’ files can not guarantee the integrity of the data. Resolution For either backup method (automatic or manual) those files which could be potentially 'open' by Windows should not be backed up unless the Sigma server and clients have been shut down.  1. Those data locations that can be backup safely while the Sigma is running are those in which archive data is stored, namely; a.  C:\Sigma\Data\ArchivedAlarms b. C:\Sigma\Data\ArchivedLogs c. C:\Sigma\Data\ArchivedTransactions Removing the files from these locations should only be done as a space saving measure as Sigma can be configured to view these data files by the user. 2. For all other files the recommendation is to shut the system down (clients and server) before taking the backup. 3. Restoring data must only be performed after shutting down the system first.

Issue I cannot logon to an AC256 or AC8 controller. My AC256 Xdriver has stopped communicating with the AC256. Environment AC256 AC256+ AC8 AC8+ Cause Unable to establish communications with an AC256 type controller. Resolution The attached document contains a thorough set of procedures for troubleshooting communication issues between an AC256 controller and a computer that is running a terminal emulator program such as ProComm or HyperTerminal. This requires that the computer have a available serial port or a USB to serial converter.  Troubleshooting AC256+ Comm Issues.doc

Issue Have Cyberstations and BCXs and/or 3rd party devices on different subnets Product Line Andover Continuum Environment Cyberstations BCX 40xx 3rd Party MSTP/IP BACnet Cause Unable to communicate with B3 devices or get B3 point values. Resolution Review LAN configuration. Each separate subnet requires a single BBMD for communication. See BACnet documentation on line via Cyberstation or "Introducing BACnet" document in Cyberstation. See Simple BBMD setup.

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 Services for assistance. Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.