Issue Configuring an enrollment reader to automatically enter access card information in personnel objects. Product Line Andover Continuum Environment CyberStation NC1 - CX99xx NC2 - CX968x ACX2 - ACX57xx ACX7xx Cause Automate data entry for personnel object's credential information Resolution You MUST use the Personnel manager in order to configure an enrollment reader.  Edit a Personnel object in order to launch the Personnel Manager Select “Configure” (bottom left) Select the “Settings” tab Check the “Enrollment Reader” check box and then browse to the Door that you intend to use as the enrollment door/reader. Typically a controller is located next to the Workstation that will be used as the enrollment WS, this controller has a dedicated door/reader for the purpose of enrollment. Click OK to save your changes. You are now able to get card information automatically into any personnel object by first presenting the card at the enrollment reader and then in the personnel object selecting the “Read Card Info” button, from the “Card Information” window click the “Insert Data” button to transfer the data into the personnel object.

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (511/555/527/913) can not create Menta object. Xenta Server (701 and 913) 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 Xenta Server version after 5.1.5 (5.1.5 included) TAC XBuilder version after 5.1.5 (5.1.5 included) Vista, I/NET, LON, MicroNet, ModBus Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.5 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Menta Supp. Xenta 511 X       X C   X   Xenta 527 X X     X C   X   Xenta 527-NPR   X       S       Xenta 555 X   X   X C   X   Xenta701 X       X ST 10   X Xenta 711 X       X C 10 X X Xenta 721 X       X ST 20 X X Xenta 731 X X X   X C 20 X 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.4 major features, please read Xenta Server 5.1.4 Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Can Newron NL220 or Echelon LonMaker systems run on a 64-bit operating system? Product Line TAC Vista Environment Windows 7 64-bit Windows Server 2008 64-bit LNS Newron NL220 4.5.12 Echelon  Lonmaker Turbo SR4 Cause Support is  provided for Newron NL220 4.5.13 on 64-bit operating systems. Lonmaker SR4 does provide some support for 64-bit systems. Resolution The current supported operating systems for this environment are as follows: Newron NL220 4.5.12 Windows NT Windows 2000 Windows 2003 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 (32-bit)   Newron NL220 4.5.13 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 32-bit and 64-bit Server 2003 32-bit and 64-bit Server 2008 32-bit and 64-Bit http://www.newron-system.com/index.php?Page=soft&Traite=download&Prod=nl220te (Account needed to view this document) Lonmaker Turbo SR4 32-bit version of Windows 7, Server 2008, Windows Server 2003 R2 with MSXML 6.0 Windows Vista with Service Pack (SP) 1, or Windows XP with SP3.  http://www.echelon.com/support/documentation/datashts/370xx-324_LonMakerTurbo_SR4.pdf 64-bit versions For 64-bit operating systems, please refer to Echelon's Software Compatibility List for restrictions and approved configurations: http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0339-01A   Lonmaker 3.1.3            32-bit version of Windows 98. Windows 2000. Windows XP. http://www.echelon.com/Support/documentation/datashts/370x0.pdf

Issue Values for a MODBus address are not coming in while using the MODbus RTU X-Driver Environment Controller MODBus X-Driver Cause The data type configured in the X-Driver point did not match the data type from the address on the third party device Resolution Review the data type from the third party documentation and configure the X-Driver point with the correct data type

Issue Has Bomgar been tested with Continuum and is it supported Environment Continuum Cyberstation Bomgar Cause Compatibility of Bomgar remote desktop software with Continuum Resolution Bomgar has not been tested with Continuum and therefore is not supported. NOTE: This is not to say that it will not work. It appears to be a remote desktop type of software. The issue with remote desktops, is that most will work for accessing a system. But where things go wrong are installations of software over remote connections. Also there can be video and graphic issues with remote desktop applications.  

Issue Can the backplane, which consists of the Power Supply, Automation Server, and I/O Modules be installed in the cabinet horizontally or vertically? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation hardware installation in a cabinet with limited space. Cause Customer would prefer vertical installation rather than the typical horizontal installation. More than one Automation Server per Power Supply** Resolution What could happen if you mount the system vertically? Due to the lack of ventilation the temperature will increase, which will have negative impact on component life time. The operational temperature is defined up to +50°C. At this temperature, the horizontally mounted system will fulfill the specified lifetime of the different electrical components. In a vertically mounted system the temperature will be higher inside the modules, having negative impact on the component lifetime. Unfortunately it is not a linear relationship between temperature and lifetime - the lifetime decreases rapidly with increased temperature. Not all modules are generating the same amount of heat, and are therefore more or less sensitive to mounting direction. In my view, the most critical component is the AS. The CPU generates heat (even more important on the coming AS-P). In the AS there are also critical components that maintains power during shut-down. These component's life time is effected if the temperature becomes too hot. These components are, as stated, critical during power-down. How will this be visible to the user? During normal operation, there will be no visible effect. However, after some years when the AS goes through a power cycle, it will not restart. So, what to do if you have a cabinet with the conduits running vertically? The official answer is that the system shall be mounted horizontally. This is how the system is designed and tested. What can you do to minimize the risk you choose to take if not mounting the system horizontally? The key is operational temperature. If you are far from 50°C, then the risk is less. One thing you always should consider is to mount the PS+AS in the bottom of the cabinet horizontally, and then have the CIO modules vertically, connected via an S-Cable. This is even more important on AS-P. If you are close to 50°C operational temperature, you need to consider external cooling or at least ventilation in the cabinet in addition to mount the PS+AS horizontally.** To conclude - the system is designed for horizontal mounting and this is the only supported mounting. If you choose to mount it vertically it is at your own risk. Operational temperature is key - you need to make sure it is far from max to decrease risk. Always try to mount the PS+AS horizontally. Negative effect of not managing operational temperature is not visible short term, but can and will effect the life time of the product. **Ambient temperatures for operating should be taken into consideration. For vertical installations, ambient temperature should not exceed 35 C (95 F) and the load on the power supply should be reduced from 30 watts to 25 watts. Convective Air Cooling is used in the modules anticipating the currents of warm air being allowed to escape the confines of the module casing to be replaced by cooler air from the bottom. Since warm air normally rises, this method usually requires venting at the top and bottom of the casing to be effective. This is why horizontal installations are preferred. **One PS can supply one or more units connected to the backplane, consisting of several terminal bases connected together. At the moment you cannot connect more than one AS to the backplane though, because the backplane provides a path for communication between the connected units, and two AS cannot communicate on the backplane. StruxureWare Building Operation allocates 32 slots for the I/O Bus including the Power Supply and Automation Server. All devices can be installed on one linear section of DIN rail or they can be installed on multiple parallel sections of DIN rail by using connector cables*. Be reminded an empty position (back plane without module) will still keep a position (slot). As a general rule, there are 10 I/O modules followed by a Power Supply, then 10 I/O modules followed by a Power Supply and 8 remaining slots for I/O modules.Please keep in mind the I/O Bus backplane requires a particular order. Position 1 is always the Power Supply, Position 2 is always for the Automation Server, and then up to 30 remaining I/O devices interlaced with additional Power Supply modules.

Issue MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Environment Continuum 1.9X Windows XP and 2003 Server Cause Message Queuing Not installed Resolution Open Control Panel Select Add and Remove Programs Select Add / Remove Windows Components Select Message Queuing Restart System and test.

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 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 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.