Building Automation Knowledge Base

Issue Satchwell VEU 2-port Unit Control Valve is obsolete. Environment Satchwell VEU 2-port Unit Control Valve installations Cause Satchwell VEU 2-port Unit Control Valve requires replacement due to failure. Resolution Satchwell VEU 2-port Unit Control Valve may be replaced by Schneider Electric VZ219 series Unit Control Valve, although dimensional differences may apply. It should be noted that VZ219 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required. It should also be noted that any Actuator installed on the Satchwell VEU 2-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ219 2-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required.

Issue Satchwell V V series Butterfly Valve Body requires replacement. Environment Satchwell V V series Butterfly Valve Body installations. Cause Obsolescence of Satchwell V V series Butterfly Valve Body. Resolution Replace Satchwell V V series Butterfly Valve Body with S-E VF208W series Butterfly Valve Body. Replace Satchwell A R series Actuator with S-E MF20 / MF40 series Actuator as appropriate. It should be noted that where a Satchwell V V series Butterfly Valve Body is to be replaced by a S-E VF208W series Butterfly Valve Body the Satchwell A R series Actuator fitted to the Satchwell V V series Butterfly Valve Body will not be suitable for reuse on the S-E VF208W.Buttterfly Valve Body. Satchwell V V series Butterfly Valves utilise Satchwell A R series Actuators. Satchwell A R series Actuators are not suitable for use on S-E VF208W series Butterfly Valve Bodies. S-E VF208W series Butterfly Valve Bodies utilise S-E MF20 / MF40 series Actuators. S-E MF20 / MF40 series Actuators are not suitable for use on Satchwell V V series Butterfly Valve Bodies. It should also be noted that Satchwell  V V series Butterfly Valve Bodies have screwed connections, whereas S-E VF208W series Butterfly Valve Bodies have Flanged connections. Further it should be noted that the width of a S-E VF208W series Butterfly Valve Body is significantly less than the corresponding length of a Satchwell V V series Butterfly Valve Body of equivalent pipe-size that it is replacing and that this will result in the need for mechanical work including installation of counter flanges to be undertaken to the pipe work at the location the S-E VF208W series Butterfly Valve Body is to be installed.  Please check the latest catalog for current equipment.

Issue How do I format a Comma Separated Variable file (CSV) to create personnel objects via import that will include area assignments and photos. Product Line Andover Continuum Environment CyberStation Cause Need way to mass create personnel objects. Resolution Typically personnel information is provided from Human Resources in a MS Excel file, the data can be saved as a CSV file and easily formatted for import into the Continuum system which will automatically create one personnel object per row using the information (LastName, FirstName etc) included in the file. Assigning areas during import is accomplished by specifying a personnel template (previously created using Continuum). Different areas can be assigned to different personnel objects as a template can be specified per row. When the personnel object is created via the CSV import, it will be assigned all the areas found in the specified template. Importing a photo for the personnel object is accomplished by specifying an image file in the PhotoFile column. Click Here for a sample CSV file.

Issue Availability of IPSEC on older controllers which request higher security constraints on networksLAN sites which have Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which has IPSEC enabled. Environment Network of IP level controllers communicating with Cyberstation Cause Higher Security constraints on networksLAN sites which has Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which have IPSEC enabled. Resolution Older versions of Andover Continuum controllers do not support network security such as IPSEC. However, the new versions of CyberStation and the new controllers, such as NetController II 9680 and ACX57x0, can be configured to communicate with controllers that do not support network security.   Another point to take note of is whether or not your site has purchased the network security option for this NetController II 9680 or ACX 57x0 controller.   IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite. It can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host).   Network Security Configuration Guide (zip)

Issue IAS stands for Intrusion Alarm System. If stopped in "Initializing" then follow these steps. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Intrusion Alarm System (IAS) also referred to as the OP5 or Remote Arming Terminal RAT Environment I/NET Seven with a 7798C and Intrusion Alarm System I/NET version 2.21 and above. I/NET version 2.16 and bellow do not support the OP5 Terminal. Cause Configuration Settings and database download. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Resolution After a software download from I/NET Seven 2.30 to current, the OP5 is always in Initializing Mode.  Hot to correct this? In the MCU Configuration Editor, the type has to be DPU The device has to be saved in Network Configuration If these two are true, it will pass the initialization part of initializing mode. Here are the steps in order to get the OP5 terminal to setup at my desk:  Set the OP5 as link 29 Backup the existing database. If DCU password is requested, it is 4444 Backup existing database. Copy the Database from CD\support\IAS Templates\8_Zones to local hard drive Copy the SAV file from CD\support\IAS Templates\8_Zones to local hard drive in the Sav folder of I/Net. Be sure to rename DCUxxxx.sav Restore database you just copied from CD Go into Network Configuration and delete link 94 Go into Network Configuration and save the link penetrating down all levels Do a station restore from the SAV file you copied to the 7798 and renamed from CD. I recommend SLI then DPU, in that order. Go into Edit, Controller, MCU Configuration and make OP5 29 link DPU Go to Edit -  Controller - Intrusion Alarm System Add point OP5 - 2 (This one is configured to link 29), Choose one or all if so desired. Click OK twice. The led light in the upper left corner on the OP5 will be lit now. Make a station restore and the OP5 keypad appears. Go into pull down menu for Access Add Door to Tenant Add Door Schedule for all three groups Go into MCU Config and check OP5 is on Link 29, and set for DPU If OP5 is still ‘Initializing’ then change MCU Config Link 29 to Internal, exit Go into MCU Config and change Link 29 to DPU My OP5 works using I/Net 2.40, Xenta 527, 7798C, OP5. I have the OP5 link as 29. Please alter the instructions to fit your link number. Step 6 refers to the link 94, which is part of the database here, you can delete since it is not relevant to your location. Here is a pdf with an example of the setup of a typical OP5. Another paper written on the steps they performed using the OP5 is found Here.

Issue In some instances, Product Support Services may require you to execute this batch file to record Vista Server errors. This is not a required file and should only be executed under the direction of PSS. Environment TACDumpHelper Vista Server Cause Vista Server fails to run correctly  Resolution To run TACDumpHelper, the batch file is to be run manually. Unzip TacDumpHelper to a directory of your choice. TACDumpHelper_v1.0.zip or TACDumpHelper_v1.1.zip (64bit) Start Tacos.exe (Vista Server) Run start.bat Choose to monitor a crash - Press 2 Choose which process to monitor - Tacos.exe - Press 1 Wait for the application to crash. The dump files will be saved in the same folder where start.bat is located. 

Issue Cannot establish communications to Modbus RTU using BCX X-Driver on Comm2 Environment BCX 4040 Modbus RTU Cause Configuration of BCX to communicate with Modbus RTU device Resolution This excerpt from the Modbus RTU guide describes the parameters to configure the X-driver for Modbus RTU communications using the BCX. Click Here

Issue Failing communications from a MicroNet View front end. Environment MicroNet View communicating to a MicroNet ARCnet or NCP  LAN. Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position.  Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Place switches 1 to 4 to ON for compatibility with NCP/ARCNET I/O- Server (MicroNet View versions 1.0 and later). Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Personnel.csv file fails to import into Continuum No error message is shown Product Line Andover Continuum Environment Continuum access control Keywords: CSV, Import, cardholder, personnel Cause CSV file gets modified by MS excel such that the import fails During the process of manually changing and saving a personnel.csv file within MS excel, a number of commas are added to the first line (corresponding to the number of column fields in the CSV) Resolution Use notepad or similar to delete commas before importing into Continuum as Microsoft Excel does not show up any trailing commas This will NOT import correctly Personnel,,,,, Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 This will import correctly Personnel Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 For more information on CSV imports Click Here For an example .csv file for testing Click Here Note: If importing X Driver points using a .csv file the comm port attribute "Port" must always be defined before the X Driver parameters Param1, Param2 etc. The Port must contain the full path e.g. "Network1\CXName\Comm1" Example X Driver Numeric: InfinityNumeric Name,Alias,Format,Description,Port,Param1,Param2,Param3,Param4 XDRPoint1,XDRPoint1,##,First X Driver Point,Network1\CX1\comm4,1,3,10001,1

Issue How do you determine how large a database will grow when using Vista? Which version of Microsoft SQL Server is needed? Product Line TAC Vista Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of trend logs and events should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called SQL Server Express. The size limitations are 4 and 10 gigabytes for Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption, data loss, or inaccessible data. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Vista database, to determine which version of SQL should be used. The Vista database estimating spreadsheet takes into consideration 2 main areas: Trend Logs- total amount of logs, intervals and the number of days to retain Events- total amount of access events. The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate which version of SQL Server is needed This spreadsheet can be downloaded by clicking on the following link: Click Here Update: In Vista 5.1.7, there is a Trend Log Calculation Tool included (under Schneider Electric-Tools)

Issue Addressing issues with M-Bus metering application because it is unclear what Storage# or Tariff# to use in Xbuilder. Environment Xenta 913 5.x.x Xbuilder 5.x.x Cause Manufacturers of meters which utilize the M-Bus protocol may not specify the Storage# or Tariff# needed by Xbuilder. They may instead include DIF or DIFE information regarding their meter points. These codes correspond to the M-Bus protocol and indicate the Storage# and Tariff# of the data. Resolution Use the M-Bus DIF calculator to parse the data type, Storage#, and Tariff# of the data point. This spreadsheet should be sufficient for the majority of applications, but some exceptions apply. The hexadecimal codes for the data point must be provided by the manufacturer for the calculator to be useful.

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue The IC-GEN OPC server does not communicate with a third party OPC client across Ethernet. Environment Sigma IC-GEN OPC (all versions) Cause The IC-GEN OPC only supports a local IP address configured in the gateway.txt file. Resolution The IC-GEN OPC server can only be connected to third party OPC clients located on the same PC. For more information see Release Note, click here An example using an EIB I/O server, click here

Issue How can a schedule be added to a personnel records particular area? Environment Continuum 1.xx Cause Adding a schedule a one area in a personnel objects areas list. Resolution This link explains step by step how to add a schedule to a personnel objects area.

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize  - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

Issue Access denied pop up messages occur at the end of a Continuum or Webclient installation MFC error Environment Continuum Webclient Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause At the end of the Continuum or Webclient install an attempt is made to register a number of files and access is being denied. Resolution Reinstall Continuum or Webclient as a local Administrator with Anti Virus and any Firewalls disabled Download AccessDeniedReg.zip and follow the instructions in the RegInstructions.txt to run a batch file to register the files. Note: The workstation may require a reboot after running the batch file.

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter