Building Automation Knowledge Base

Issue Expanding a system with a 7798B and unable to connect to other controllers. Product Line TAC INET Environment All versions of I/NET Cause There is no expansion card to connect the LAN Controllers together. Resolution The 7798B requires a CLX Expansion Card to be plugged into the slot to allow it to communicate to other controllers. The part number for this is LAN EXPANSION OPTION FOR RS-485, CLX. See Additional information on CLX LAN Expansion Option for RS-485 for more information on the CLX part. Take the device off the wall, unplug all wires including power. Insert the CLX card into the slot on board, be careful not bend any pins while doing this. Connect the wires again in their respective terminal with the LAN wire connecting to the CLX card, Sublan to those devices and power. Put the device back on the wall, set up accordingly and it should be communicating to the controllers now.

Issue Should we upgrade to the latest revision for the SCU 1284 If we do not upgrade the SCU will I/NET work properly. Product Line TAC I/NET Environment I/NET Seven Security Control Unit (SCU) 1200 series firmware 3.2x and above Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the SCU. The recommendation is to always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. If you have any additional concerns then please contact Product Support. The following table lists the release firmware revisions and associated fixes and new features: Rev Date DCN Changes 3.21 05/06 5593 Add support for SCU tamper to the SCU1200 and SCU1280 3.22 01/07 5610 Start adding intrusion alarm support to SCUs Add issue level support to SCU1284 Fix defect where deleting last tenant from DPU causes incorrect schedules Add door code 3.23 08/07 5627 Fix defect where changing a door to "unselect" did not prevent access through door 3.24 10/07 5631 Expand individual count from 24,000 to 32,000 per tenant 3.25 07/08 5657 Implement various changes to intrusion alarm system that were identified during EN50131 certification 3.26 01/10 5677 Fix corrupt reader LED due to OP5 monitoring board Fixes to SCU1284 expansion board for IAS power monitoring 3.27 07/11 5717 Make AMT show person who commanded PIN functions 3.28 12/12 5739 Fix for bad card read on reader number 4 with internal AO at bit offset 04 3.29 08/13 5745 Fix so that a change of date from one month to the next will work correctly when using special days 3.30 10/14   Support for 130-bit Wiegand card New event named “Key reassignment” 3.31 12/14 5754 Support for 86-bit Wiegand card For DPU range of controllers refer to I/NET Door Processing Unit (DPU) 7910A / 7920A EPROM Feature matrix.

Issue Error message "Invalid Object Name" Error message "Failed to transfer application file to TAC Vista"   Product Line TAC Vista Environment LonMaker NL220 Menta TAC Vista System Plug-In Cause Error message "Invalid Object Name" appears when browsing in a Menta file in TAC Vista. Add it via the System Plug-in results in an error saying "Failed to transfer application file to TAC Vista"  Resolution This could have different causes. There could be a signal name that is to long (longer than 20 characters). The problem can also be that there is an ALARM that have an alarm controller object defined that are using a $ (other than the default $Alr_Cntrl). TAC Vista will try to add the object and you are not allowed to add objects with $ in them. For more help see "Update Vista database failed" Error in Vista System Plug-In.

Issue When trying to log into SBO Workstation receive the following error: Invalid returned data from license server system. (Error code: -12) Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Cause This error has been caused when a Workstation license is present but no Enterprise Server license is present. Resolution An Enterprise Server license must be purchased and added. Please see EcoStruxure Building Operation License types for license options and part numbers.

Issue Alarms or Events are not being received as soon as they occur and there is a large delay before they are written to the Database. Product Line Andover Continuum Environment Continuum Cause Review the controller error log. If there are 6c0e errors, this indicates the comms buffer is filling up (see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR)). Another indicator is in the ACCTRace logs. Check if Alarms are being logged in the Database when the WS thread is receiving them. The time in the ACCtrace may be logged as the TimeOfLog. Investigate the programming to see if it is polling data from a BACnet controller constantly. There may be no delay in poll requests which can overload the controllers comms buffers. This will in turn delay some Alarms from being delivered to the Workstation to be displayed and logged in the Database. Resolution Fix programming so there are wait lines between each poll. Also see Controller error log: error transmitting (LAN_ERR_TRANSMIT_ERROR).

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

Issue When adding points to your OPC Client from a Schneider Electric Vista OPC Server that contains points from Xenta Servers error "The item definition does not conform to the server syntax". Product Line TAC Vista Environment Vista 5.x Vista OPC Server 1.6.x Xenta Server 511-B, 731, 527, 913 Cause There are certain characters that are invalid in an OPC Server environment which are allowed in the Vista Server database. Invalid names include I/NET, RS232/485 A, and TCP/IP. Resolution Create a folder in the Vista database and create shortcuts for the points that are suffering this problem. This avoids any invalid characters, but grants full functionality for the data in question. For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue When there are dual NICs on the computer, you will get host number conflicting error. The IP address causes this conflict is just the local IP address. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET prior to Version 2.44a Win 7 or higher OS Cause When there are two NICs on the computer, I/NET needs to know which NIC is used for communication. I/NET support for dual Network Interface Cards (NIC) can be used for dual NIC configuration for I/NET. But under Win 7 and higher OS, wireless NIC can't be recognized in I/NET, which makes it impossible to choose wireless NIC to be used for I/NET. In the I/NET configuration, it just shows 0.0.0.0. Resolution I/NET will fix this issue in the new release. For I/NET prior to version 2.44a, there are two workarounds for this issue currently: Refer to I/NET support for dual Network Interface Cards (NIC) to choose onboard NIC to be used for I/NET communication. Disable onboard NIC or just disconnect it from the network. Then you will see the option for choose NIC for I/NET communication will be grayed out. That will force I/NET to communicate with wireless NIC. Remember to reboot I/NET I/O server after this to make it take effect. 

Issue When running a listview on the alarm log it appears there are instances where the alarm was acknowledged before the timestamp. How can this happen? Product Line Andover Continuum Environment Time Sync Cause This issue can occur if  the Continuum system is not properly time synchronized. In order to properly sync the system time, it's helpful to understand where the various alarm time attributes are set: TimeStamp comes from the controller's time TimeofLog comes from the SQL Server's time TimeofAck comes from the Acknowledging CyberStation's time Resolution Make sure all the components of the system are properly time synchronized. Methods of synchronizing server and workstation times may vary based on the workstation operating system and if your network is using active directory. Refer to the network administrator to verify if time sync is being done, and under what conditions (logon only and/or a schedule) and how often. If Continuum is on an isolated network refer to http://support.microsoft.com and search on network time synchronization to learn about the different options for the particular network configuration. As for the workstation-to-controller time sync, Time sync controllers to workstations includes a program to which will sync the workstation time to the controllers. TimeOfLog and TimeStamp columns in an Alarm or AccessEvent listview are different covers a couple of conditions where the TimeStamp and TimeofLog may vary considerably. Periodically, verify that all the components are in sync.

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue When using SQL 2008 or SQL 2008 R2, I/NET will crash randomly. Referring to the system Event Log, you can see a SQL error happened just before I/NET crashed, called "There is insufficient system memory in resource pool 'internal' to run this query." Product Line EcoStruxure Building Operation,TAC INET Environment I/NET SmartStruxure Cause According to Microsoft Knowledge Base, this problem occurs for all the following reasons: There is a bug in the code that is used to evaluate how many rowsets are required to perform a sorting operation. Therefore, the code greatly overestimates the numbers of rowsets. The required grant estimate in full-text is 64 pages for each rowset that is required to sort. There is a large request that blocks the system from using the memory that is reserved for the full-text query. Resolution Install the newest SP to the SQL 2008 or SQL 2008 R2 being used. Download Microsoft SQL Server 2008 SP3 Express Edition or Microsoft SQL Server 2008 R2 SP2  Express Edition from the Microsoft website. If this doesn't help, please follow Create Error Log for I/NET to turn on the error log for I/NET and then send the log in to your local country product support group for further troubleshooting.

Issue Commission and Download command from Vista Workstation on a controller/network beneath a Xenta 911 communication port results in "Error: Failed to connect to TAC Xenta 911 - Invalid User/Password" Product Line TAC Vista Environment Vista Classic Network Communication Port - Xenta 911 Xenta 511/911 Cause Vista port properties has User name and Password stored.  If the user name or password are changed in the controller, these changes must be made to the Vista server settings as well. Resolution Obtain the most current user name and password for the Xenta hardware device If the password is not known and cannot be obtained, a temporary password can be assigned.  Please see Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost. Right-click on the Xenta 911 communication port and select Properties Enter the new user name and password under TCP/IP settings Attempt the Commission and Download command again.

Issue Workstation displays power in Btu/s when VA is required. Product Line EcoStruxure Building Operation Environment Workstation Cause The units displayed in Workstation are based on the Regional and Language Options settings in Windows Control Panel as talked about in Metric vs. English (Imperial) Operating System. Resolution The Unit Conversion Exception tool can be used as a solution for this issue. This is located in the Domain portion of Workstation's Control Panel. For more information on the Unit Conversion Exception see Unit Conversion Exceptions feature or the Online help located here. In the situation where VA has been set as the power unit but Btu/s is still displayed, the unit conversion shown below will resolve the issue. Note: If your desired value units have a prefix, then this needs to be done in the Unit Conversion Exception as well (kVA). Note: WebStation (as of v1.3 SP1) does not use the Windows OS setting because the AS does not currently have localization - it uses only the International System of Units (SI) - not the Imperial or US units.

Issue Continuum general preferences show the system is configured to purge extended log data after X days, yet the extended log data is not purged. Product Line Andover Continuum Environment CyberStation Cause LAN System The SQL agent responsible for purging extended log data is missing or disabled. For Single User system see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table Resolution LAN Systems (for Single User see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table) In SQL Server Management Studio expand SQL Server Agent, then expand Jobs If ExtLog_Purge_ContinuumDB job is present verify its properties (see image below), make sure the job is enabled and properly configured to run.  If the job does not exist it can be recreated by following these steps: Close ALL Continuum Cyberstations/Web Client From SQL Server Management Studio run the following query against the ContinuumDB update ACDBVersion set ACDBVersion = 0 Run Continuum DB Initialization and update the database from the server tab, when prompted to run the ImportExport fixup tool select NO Verify the job was created then run Continuum

Issue No Trends are showing up in the Data/Enquiry Editor when a point is selected. Product Line TAC INET Environment Xenta 527-NPR Webserver 5.1.6 Cause Changes in the Xenta 527 firmware in version 5.1.6 and later have resulted in some problems I/NET trend data displaying in the Xenta 527-NPR. Resolution To resolve this, the best option is to downgrade the Xenta 527 to version 5.1.5, per Download an .MOT file into a Xenta Programmable controller and restart the device and I/NET again.

Issue Operating System Selection when using SQL Server Product Line TAC INET Environment I/NET Seven Site Cause Making decisions on operating system selection while using SQL Server 2000 Resolution If your site has grown beyond the capabilities of the Microsoft SQL Desktop Engine (MSDE) as discussed in Customer Advisory CA-2004-04 then you need to decide upon an operating system to use when you upgrade to SQL Server 2000. SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems: Windows Server 2003, Standard Edition Windows Server 2003, Enterprise Edition Windows Server 2003, Datacenter Edition Windows® 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server Source: http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.mspx An option to consider based on the needs of the customer is whether Windows Small Business Server 2003 Premium Edition can meet their needs. This version sells at almost the same cost as SQL Server 2000 (5 CALs), however it includes much more. Windows Small Business Server 2003, Premium Edition includes the following components: Microsoft Windows Server 2003 Microsoft Exchange Server 2003, Standard Edition Microsoft Shared Fax Services Microsoft Office Outlook 2003 Microsoft Windows SharePoint Services 2.0 Health Monitor 2.1 Remote Web Workplace Microsoft Internet Security and Acceleration Server 2000, Standard Edition with Service Pack 1 (SP1) Microsoft SQL Server 2000, Standard Edition with Service Pack 3a (SP3a) Microsoft Office FrontPage 2003 It is important to note that there are some restrictions built into this version of Windows Server 2003. These restrictions limit it to only a single domain solution and can only expand up to 75 users or device connections. Windows Small Business Server restrictions Windows Small Business Server provides a cost-effective suite of programs for small businesses that have 75 or fewer users or devices. To help you prevent unapproved network installations and to help you protect your networks against viruses and other attacks, Microsoft has placed the following restrictions on the use of Windows Small Business Server: You must install all the component server programs in Windows Small Business Server on a single computer. No component may be installed on a separate computer. If you want to run one or more of the component services on a computer other than the Windows Small Business Server-based computer, the other computer requires separate licenses. You can connect a maximum of 75 users or devices to a Windows Small Business Server-based network. This requirement limits the number of users or workstations that can access one or more of the component server programs. Windows Small Business Server is a single-domain solution that is not intended to be integrated with other Windows-based domains. You are not permitted to establish explicit trusts to other Microsoft Windows NT-based domains or to Active Directory directory service domains. Also, Windows Small Business Server does not let you create child domains. The computer that is running Windows Small Business Server must have all operations master roles and must be at the root of the Active Directory forest. The following features that are available in earlier versions of Small Business Server are not available in Windows Small Business Server: Microsoft Shared Modem Service Microsoft Terminal Server Windows Small Business Server supports up to two physical CPUs and up to four virtual CPUs with hyperthreading. Note: Earlier versions of Windows Small Business Server support up to four physical CPUs. You can have other domain controllers and member servers in your Windows Small Business Server-based network. However, the computer that is running Windows Small Business Server must be set up as the root domain controller of an Active Directory forest. This requirement may prevent the computer that is running Windows Small Business Server from serving as a corporate branch office server or as a department server of a large organization that is based on Active Directory or on Microsoft Windows NT 4.0. You cannot add Windows Small Business Server to an existing domain. You must install a Windows Small Business Server-based domain and then add additional domain controllers or member servers to the domain. When you run Exchange 2003 on a Windows Small Business Server-based network, Exchange 2003 cannot be part of a larger Exchange 2003 organization. Because Windows Small Business Server is installed at the root of the Active Directory forest, you cannot install Exchange 2003 components that belong to an existing Exchange 2003 organization. Source: http://support.microsoft.com/default.aspx?scid=kb;en-us;842690 Windows Small Business Server 2003 Premium Edition is a good solution for jobs where the controls contractor will be managing the server operating system that is the core of the BMS.  Many customers today will allow controls contractors to utilize their IP infrastructure but want the system managed and maintained by that same controls contractor.  This software allows that contractor to provide a turn key installation and include all PC hardware and software.  Windows Small Business Server 2003 Premium Edition is also a very cost effective solution for jobs where the specification requires a server operating system or a full version of SQL server that the contractor must provide.  It is recommended that if Windows Small Business Server 2003 Premium Edition is used, any software that is not needed on the server is disabled (i.e. Exchange Server, Fax Services, SharePoint Services).  In conclusion, Windows Small Business Server 2003 Premium Edition is a cost effective way to provide SQL Server at a site if all criteria are met.  Update: If using I/NET 2.40 and above, please check this compatibility matrix for Operating Systems when using SQL Server For other compatibility issues, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Can Sigma system controllers sit on multiple VLANs? Product Line Satchwell Sigma Environment Sigma all Ethernet controllers Link Addressing Cause Question by IT departments before upgrading BAS to Sigma systems Resolution You can put Sigma controllers onto different VLANs. But there are considerations: Sigma global data to be passed between controllers on different VLAN's will require Link Addresses to be configured. This is because Sigma globals are transmitted using the Ethernet broadcast address. Typically, most broadcast address messages are blocked by the routers used to link/connect the VLANs. Hence Link Addressing is used to 'tunnel' through the VLAN routers. A DNN will have to be added to each sub-LAN for Link Addressing configuration.  For configuration details click Link Addressing.pdf. All Sigma devices (controllers, Servers and DNN's) will have to be configured with default gateway IP Addresses. For controllers use pocket terminal command GW +  192.168.0.1  (where 192.168.0.1 is the default gateway for the local network) For DNN's set a Static Route as defined in Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work. For Sigma servers set the PC default gateway IP address via network settings - Internet Protocol (TCP/IP) - properties. Therefore, although the answer is yes - Sigma controllers are supported on different VLANs, a 'flat' VLAN architecture is a simpler solution.

Issue How to use the Known Occupancy Count (KnownOccupCount) number of an Area in Plain English (PE) programming. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Access Control Cause Need to be able to retrieve the Known Occupancy Count number of an Area for use in Plain English programming for limiting access to an Area. The attribute does not show up in the list of attributes in  the Area Listview. Resolution Even though we can't see the attribute in an Area Listview, you can use the "KnownOccupCount" attribute at the command line or in Plain English programs. Example 1 - Print Known Occupancy Count to command line. print AreaFolder\Area1 KnownOccupCount Example 2 - In a Workstations Program, set a pre-defined AnalogValue to the Known Occupancy Count of an Area. Area1KnownCount = AreaFolder\Area1 KnownOccupCount Note: The Known Occupancy Count will not function with Entry only doors. Both Entry and Exit readers are required on the doors within the Area. See Known Occupancy Count number does not increase when Personnel enter the Area on this.

Issue Cannot get comms stats from the DNN or controllers below the DNN. Product Line Satchwell Sigma Environment Sigma Communication DNN RIP Listener Windows XP Persistent routes Cause The Sigma server 'learns' the network architecture by listening to RIP messages broadcast by the network DNN's.   This is performed by RIP Listener which by default is not enabled on Windows XP. Resolution Enable RIP Listener on the Sigma Windows XP server by; In Control Panel select 'Add or Remove Programs' From the left hand bar select 'Add/Remove Windows Components' Highlight 'Network services' and select 'Details' Enable 'RIP Listener'   Select 'Next' and then 'Finish' OR Add persistent routes as an addition to RIP Listener as a backup or if RIP v1 is not permitted on the system see Persistent routing on the Sigma server. Use the DOS Command ROUTE PRINT to list the dynamic and persistent routes, check that the gateway address and network addresses are correct.

Issue Ordering, installing, wiring of CLX LAN Expansion board. Product Line TAC INET Environment I/SITE 7798 CLX Cause There is not any CLX-specific installation guides or manuals. This article is intended to give some basic information about the expansion board and its use. Resolution Part number: CLX Part name: LAN Expansion Option for RS-485 Part description: I/SITE Expansion Board - adds controller LAN communications to network other controllers to 7728 & 7798 - RS-485 CE/EMC Compliant Comments: Plugs on to 7798 base unit, RS-485: 19,200 or 9600 baud, SDLC, token-passing. Wiring: Terminals 1 and 2 on the CLX are Controller LAN +,- respectively. For more information on installing the CLX expansion, see CLX Expansion Card for 7798B .