Building Automation Knowledge Base

Issue How often does a Bacnet MSTP B3 controller broadcast alarms? How often is the Bacnet MSTP B3 polled for alarms? Environment Bacnet MSTP Andover Continuum B3 MSTP controller Cause Determining the process of MSTP B3 alarming Resolution The Bacnet B3 communicates on a token passing Bacnet MSTP protocol. When a B3 is configured for alarming and an alarm occurs, it will broadcast the alarm when the controller has the token.

Issue Shared Newgraphics file not accessible thru IIS connections. Environment Continuum WebServer 1.92 MS Server 2008 Standard. Cause Security Enhancements caused Pass-Through Authentication Failure with MS 2008 server IIS application. Resolution On the System that the graphic files are located share the folder and give everyone full control permissions. On the IIS server create a new virtual directory. Name it Newgraphicsfiles and path to where the graphics are located In IIS Manager, scroll down to Directory Browsing and enable it. On the Webserver system, Map a drive to the share for newgraphicsfiles. In all the Continuum Graphics add the mapped path to the options tab. A service account will need to be created in Active Directory. The account will need to have log on locally rights. For example, create an account ContinuumService and add the account to the Back up operators group. The IT group will need to be involved at this point. They will determine what the name and what group the account will belong to. Once the account is created  open IIS manager and right click on the newgraphicsfiles directory and select Manage virtual directory / advance settings. In the Physical Path Credentials add the account IT created domain\account Test the account by going to http://servername/newgraphicsfiles

Issue The Xenta 102-AX can be set to NIGHT_PURGE mode using the plug-in or VAV_Controller.nviApplicMode.  The documentation does not state what this mode does. Environment Xenta 102-AX Cause The Xenta 102-AX Product Manual enumerates all of the possible modes for the controller, but does not go into detail about night purge or any of the other modes. Resolution NIGHT_PURGE mode will: Set the unit mode (nvoUnitStatus.MODE) to HVAC_NIGHT_PURGE Set the airflow setpoint (nvoFlowControlPt) to Cooling Maximum (SCPTmaxFlow) The Xenta 102-AX will enter NIGHT_PURGE mode automatically when the unit is UNOCCUPIED and the terminal load is 100%. NIGHT_PURGE mode will end and return to the active nviApplicMode when the terminal load reaches 0% or below. Note:  Heating outputs are not disabled in this mode. If the Xenta 102-AX is in night purge mode when it goes occupied it will be stuck in that mode. The box will not come out of night purge until the terminal load reaches 0% just as when it is unoccupied

Issue Echelon LON USB not recognized by TAC Vista 5 in a Classic network. Echelon U10/U20 USB interface is not supported in Vista installations. It oftentimes will not come online under a Vista Server. Product Line TAC Vista Environment Echelon LTA U10/U20 USB to LON converters Vista Server Classic Network Cause Because of numerous problems integrating an Echelon U10/U20 USB interface, Echelon's USB to LON converters are not supported by TAC Vista. Resolution Download the TAC Vista Server Data Sheet and reference page 11 for supported LTAs. The supported LonTalk Adapters are: PCLTA TAC Xenta 511 PCLTA-10 TAC Xenta 527 PCLTA-20 TAC Xenta 555 PCC-10 TAC Xenta 701 i.LON 1000 TAC Xenta 711 NIC709-PCI TAC Xenta 721 NIC709-USB TAC Xenta 731 NIC709-USB100 TAC Xenta 911 NIC709-IP TAC Xenta 913 NIC852       FT 10 TP 1250 RS 485 IP 852 Ethernet NIC709-PCI X X N/A N/A NIC709-USB X X N/A N/A NIC709-USB100 X X N/A N/A NIC709-IP X X N/A N/A NIC852 N/A N/A N/A X

Issue When presenting a card to a card reader I see a message in the Active Event view that says "Custom Card" instead of "Valid Access" Environment AC1 ACX78x ACX57xx Netcontroller 1 Netcontroller 2 Active Event View Access Event Cause This is being caused by the controller not having an "AccessFormat" numeric set up.  The AccessFormat numeric is used to define the fields when using a Custom Card. Resolution   Use the below procedure to set up a Custom Card.  This procedure uses a Corporate 1000 35 bit card as an example. Custom Card Format for:  HID Corporate 1000, 35 bit Here is the information on creating a custom format in the Andover System. A custom format must be used when the card format is not one of the standard pre-defined formats. Only one custom format can be used in an ACX controller or NetController. Setting Up a Custom Wiegand Format In each ACX700 and ACX780/781 and NetController, create an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 19 entries to the point. Create he following Infinity Program, once created, can be copied to all other access controllers that need it. Program Name: SetArray FlowType: FallThru AutoStart: True Code: Set AccessFormat[1] to 35      'overall number of bits Set AccessFormat[2] to 0        'control mask Set AccessFormat[3] to 0        ' manufacturer’s code Set AccessFormat[4] to 0       ' start bit of man. Code (first bit is 0, not 1) Set AccessFormat[5] to 0       ' end bit of man. code Set AccessFormat[6] to 2       ' start bit of site code Set AccessFormat[7] to 13      ' end bit of site code Set AccessFormat[8] to 14      ' start bit of card number Set AccessFormat[9] to 33      ' end bit of card number Set AccessFormat[10] to 0      ' odd parity mask, first 16 bits Set AccessFormat[11] to 0      ' odd parity, next 16 Set AccessFormat[12] to 0      ' odd parity, next 16 Set AccessFormat[13] to 0      ' odd parity, next 16 Set AccessFormat[14] to 0      ' even parity, first 16 Set AccessFormat[15] to 0      ' even parity, next 16 Set AccessFormat[16] to 0      ' even parity, next 16 Set AccessFormat[17] to 0      ' even parity, next 16 Set AccessFormat[18] to 0      ' card number multiplier Set AccessFormat[19] to 0      ' card number divisor In each Door Configuration, select the Custom Wiegand card type. Other card types may also be selected. For each Personnel, select the Custom Wiegand card type, and enter the correct card number and site code.   If the card is not working, check the Event Log and determine the cause. For Invalid Card Parity errors, set all the parity masks to 0 and try again. For proximity cards, the parity check may be eliminated with little consequence.

Issue Cannot create a Netcontroller2 in CyberStation version 1.74 Environment CyberStation version 1.74 Netcontroller2 CX9680 Cause CyberStation version 1.74 does not support Netcontroller2 Resolution Install Sp2 for CyberStation version 1.74 to support the Netcontroller2

Issue Xenta 5/7/9xx System Report shows "Menta: Overrun error (Error#:62468)" Environment Xenta 701, 711, 721, 731 version 5.1.4 and below Cause A Menta application took to long to run a loop. Probably due to temporary high load of the system. Resolution Upgrade the Xenta 700 to version 5.1.4 SP1 or greater, preferably the most recent release of Xenta Server software.

Issue Does a single controller (2nd generation controllers such as NC2 and bCX) support two(2) Modbus TCP/IP xDrivers on two(2) different comm ports?    Product Line Andover Continuum Environment Modbus TCP/IP XDriver NC2 (CX9680) bCX4040 Cause Need to have Modbus TCP/IP interface with 3rd party devices for both Server mode (Slave mode) and Client mode (Master mode).  Resolution You can have only one Modbus TCP/IP XDriver on a Controller(NC2 or bCX).  In order to have Modbus TCP/IP XDriver for both Server mode and Client mode, there should be two different CX controllers, and  different mode of Modbus TCP/IP XDriver should be installed and configured on different controller.   Note: This also includes any IP XDrivers. You can only enable one IP XDriver per Controller. (Ex. You can not enable a BACnet IP XDriver on one comm port and a Modbus IP XDriver on another, you would need two Controllers for this - one IP XDriver on each)

Issue Sending an email from the controller via PE or Web Page shows incorrect sent time. Environment NC2 - CX968x ACX2 - ACX57xx bCX Cause Time settings not configured correctly from controller's web page. Resolution From a web browser login to the controller's web configuration (point your browser to the IP of the controller) Go to "Controller Configuration\Time Setting" Enter the appropriate UTC offset for your time zone, for example if the controller is in the Eastern time zone enter -300 Use the "Daylight" Savings option to specify whether daylight savings time is in effect Finally click on the "Submit to Controller" button, there is no need to commit changes and re-start the controller.

Issue Step-by-step instructions for calibrating Space Temperature sensor on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating temperature in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution  Step 1: Connect M/STAT Plug the M/STAT into the jack on the thermostat.  The initial display shows the set temperature.  Step 2: Enter Password Press the Service button.  This prompts you to enter the service mode password.  Default password is 183.  Use the +/- keys to set each digit and the enter key to submit.  If the password is incorrect, the display will blink.  Step 3: Operational Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed.  Hit the select button down until Operational Parameters (oP) is displayed.  Press enter.  Step 4: Calibrate Space Sensor Hit the select button until Calibrate Space Sensor (CSS) is displayed.  Press enter to view the current value.    Step 5: Enter Actual Value Use the +/- keys to change the value beginning with the tenths of degrees.  Press select to change to the degree and ten degree digits.  When the display matches the Actual Value, press enter.  Step 6: Escape Service Mode Press the service key to escape out of the menu.  If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT.  Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue The StandAlone workstation is not getting alarms delivered to the active alarm view. Environment Continuum Cyberstation standalone. CX Controller Cause Alarms are not being delivered to the workstation. When the point is edited, the point shows that it is in alarm. Resolution Cyberstation was gracefully shut down. Start Continuum Database Initialization for StandAlone Enhanced Alarm Delivery was deselected. Database was initialized Continuum was restarted Points were set to an alarm value Alarms were delivered.

Issue When creating an Equalization bed with a Filemaster and several clients, a full version of SQL 2005 or 2008 needs to be installed on the Filemaster. All the clients need to have SQL 2005 Express or SQL 2008 Express installed on the remaining PCs. Environment I/Net Seven revision 2.40 and higher running on Windows 7. Cause Setting up Equalization using full SQL 2005 or 2008 and SQL 2005 Express or 2008 Express on the clients. Resolution Install full SQL 2005 or 2008 on the PC that is dedicated to the be the Filemaster. Launch the I/O Configuration and create a new profile. Connect to the instance that is full SQL. Set this as the Filemaster in Workstation Options. Load remaining PCs with SQL 2005 or 2008 Express. Launch I/O Server and create new profile. Set this as Equalized Client in Workstation Options. Once connectivity has been made, verify that Equalization is working.

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (701) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Vista, I/NET, LON, MicroNet, ModBus Xenta Servers (Xenta 5XX/7XX/913) Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.4 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Xenta 511 X         C   X Xenta 527 X X     X C   X Xenta 527-NPR   X       S     Xenta 555 X   X     C   X Xenta701 X         ST 10   Xenta 711 X         C 10 X Xenta 721 X         ST 20 X Xenta 731 X X X   X C 20 X Xenta 913 *** X X   X X S     * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service.  NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.5 major features please read Xenta Server after version 5.1.5 (5.1.5 included) Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Micronet ARCnet controllers - Maximum network variables, allowed per controller. Environment Micronet controllers, all variants. Cause General information about network variables configured in a Micronet controller. Resolution All Micronet ARCnet controllers can be configured to received six NVR's (Network Variable Received), and six NVT's (Network Variable Transmitted). To review the latest VisiSat Engineering Guide, and more details on ARCnet, please click here.

Issue Can an IOU bus be wired in a Star topology Environment Netcontroller 1 Netcontroller 2 IOU Wiring CyberStation Cause What are the wiring guidelines for the IOU bus Resolution An IOU bus can only be wired in a Star topology if you are using the FTT models of controller and IOUs.  See the section on the IOU reference guide starting on page 10 at the below link. Andover Continuum I/O System Reference

Issue When polling BACnet points with an I/A Series R2 (Niagara) UNC, a warning frequently appears in the Standard Output Window that reads "Warning: BACnet Read Property Multiple Error" followed by a property name and device or object name. Environment I/A Series R2 (Niagara) UNC or BACnet Server Cause The warning is reported when a UNC or BACnet Server station polls a BACnet device, and that BACnet device does not support the Read Property Multiple" function.  All data will be retrieved because the station will detect the warning and will poll each requested property, one property at a time. Resolution This is not an issue, just normal operation.  The startup warning messages could be suppressed by setting the device's Read Property Multiple property to false.  However, disabling read property multiple will slow the polling of this device. 

Issue When trying to edit or create a new Plain English program the editor fails to open. Environment CyberStation Plain English Editor Cause Corrupted PlainEnglish.ini file Resolution Open Windows Explorer Go to the Windows directory Find the PlainEnglish.ini file and delete it. When the Plain English editor is opened after this file is deleted it will recreate a new PlainEnglish.ini file with all the default settings.

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 What is the best way to upgrade Continuum Single User system from 1.5x to 1.9x? Product Line Andover Continuum Environment Continuum 1.5x, 1.5, V1.5 Continuum 1.6x, 1.6, V1.6 Continuum 1.9x, 1.9, V1.9 SQL Server Cause Continuum Upgrade from older versions of Continuum. Resolution First upgrade to 1.74, then upgrade from 1.74 to 1.9x.    PART I - Preparation: Acquire all software necessary to bring the workstations into compliance with 1.9x platform requirements. For each Cyberstation machine, make a record of the following Workstation name Folder name Device Node ID Network ID. From https://ecobuilding.schneider-electric.com Download Cyberstation 1.74 Download Cyberstation 1.9x Download Microsoft SQL Server Management Studio Express Run Continuum Analyzer and resolve any issues.  An upgrade should not be done until the analyzer test report is clean. IMPORTANT - Make a backup of the Continuum database just prior to upgrading. PART II - Upgrade Workstation 1 (Database server PC) Uninstall 1.5x or 1.6x Shut down the Cyberstation applications on all workstations. Power down the workstations that are not running SQL and leave off until Part III Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Backup the contents of the graphics file directory to a flash drive or another folder. Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 (DB server) Install 1.74 Install Continuum 1.74  (SQL 2000 SP4 will be installed automatically as part of the install) Run Database Initialization Create new database Initialize workstation using information from Part I. Launch Continuum to test that Cyberstation startup normally. Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore database backup from PART I Run Database Initialization. Update Continuum DB Update Workstation using information form Part I Launch continuum and verify that everything looks normal. Verify the integrity of the database by running Continuum Analyzer and correct any database issues before proceeding.. Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Backup Database – name file so that it is clearly 1.74 Uninstall 1.74 Uninstall Continuum Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 Install 1.9x Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Install Continuum 1.9x - (SQL Express will be installed automatically as part of the install) Run Continuum Database Initialization Create new database Update workstation with information from Part I. Launch Continuum to test that Cyberstation startup normally Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore 1.74 database backup. Run Continuum Database Initialization Update database Update workstation with information from Part I. Launch Continuum and verify that everything looks good. Run Continuum Analyzer and verify the integrity of the database. Backup Database PART III - Upgrade Workstation 2 and 3 Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Uninstall Continuum from Workstation  Delete C:\Program Files\Continuum Install Continuum 1.9x Run DB Initialization and update database and workstation. Launch Continuum and verify that all looks well. Backup Database

Issue What kind of preparation must be done prior to upgrading a Continuum LAN system? Environment Continuum Cyberstation SQL Server Cause Continuum Upgrade Resolution Study the Continuum Compatibility Matrix and the Continuum Video Compatibility Matrix.   Plan the upgrade of supporting software applications and hardware using the Continuum compatibility matrix as your guide.  .Net versions and SQL versions must be compatible with the final version of Continuum before you begin the upgrade process.  Older CX controllers (with firmware <= 1.500029) use a different algorithm for defining handles so they should be up-rev’d prior to the upgrade process.   For all other controller the controller firmware can be upgraded after the front end systems upgrade has been completed.    The upgrade process presents an opportunity to make an assessment of all computer hardware that is currently being used in order to make recommendations for upgrading hardware.  This is especially important with respect to the Continuum Database server.   Selecting the right server is a process that involves determining the customer’s needs and defining the systems requirements.  This is an engineering decision that is beyond the scope of Product Support Services.  The customers IT department will likely be involved in this process also.  When are adding a new database server, it may be advantageous to build your Continuum server and prepare the Continuum database off-site. Completing a Continuum LAN system upgrade is a complex process and not something that you can accomplish simply by following a step list. It is crucial that an engineer who is experienced with the Continuum LAN upgrade process on site to direct the upgrade.  This is both to ensure that the upgrade process is handled correctly and to mentor technicians who will be involved in future upgrades on LAN systems.

Issue What is the default IP address for BCX, ACX57xx, CX9702 & Netcontroller II? Product Line Andover Continuum Environment Controller Netcontroller II (9680) BCX ACX57xx CX9702 Cause Default IP address for BCX, ACX57xx, CX9702 & Netcontroller II Resolution The default for all these controller types is: IP address: 169.254.1.1 Subnet: 255.255.0.0 Gateway: 169.254.0.0