Building Automation Knowledge Base

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue Necessary Accounts for DCOM and Firewall Security Settings. Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Remote Workstation DCOM Configuration Cause DCOM Parameters must be set to allow for remote connectivity to the Vista Server. Resolution You will notice in the "Security Settings for MS Windows XP SP2 and MS Windows Server 2003 SP1" instructions that several changes are needed for the accounts "ANONYMOUS LOGON" and "Everyone". If these accounts do not exist, they must be created and set to allow local launch and remote activation permissions. See also Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for an automatic DCOM utility.

Issue Transfer pressure values with units of inches of water between I/NET and LON with a 913/527/731. Environment I/NET Xenta 913/527/731 XBuilder Cause When reading pressure from LON, the value is always in metric units, Pascals, on the LON wire. When the value comes into I/NET, it will be a large, unexpected number. Resolution To read in a LON pressure value into I/NET: Create two internal points in I/NET. AO to receive the raw pressure value in Pascals AI to perform the conversion to inches of water Add a calculation to the AI to perform the conversion: P0*C0 P0 = AO created to receive the raw pressure value in Pascals C0 = 0.004 to convert value from Pascals to inches of water Set the connection object in XBuilder: From = LON SNVT_press To = AO to receive the raw pressure value The AI should be reading the correct value in units inches of water. To write a setpoint value out of I/NET to LON: Create two internal points in I/NET: AO where the user enters desired static setpoint in inches of water AO to perform the conversion to Pascals Add a calculation to the AO to perform the conversion: P0*C0 P0 = AO created to enter desired static setpoint in inches of water C0 = 249 to convert value from inches of water to Pascals Set the connection object in XBuilder: From = AO to perform the conversion To = LON SNVT_press The SNVT should be reading the correct value in desired units.

Issue When using a HyperLink in Vista WebStation graphic page the error message "This content cannot be display in a frame" is shown. Clicking the link to open this content in a new window will properly display the web page. Environment Vista WebStation 5.x.x Cause Newer web browsers support a HTTP header flag named X-Frame-Options which allows the remote web server to block display of its content within a web page frame. This is a security measure to stop "click jacking". Internet Explore 8, Internet Explorer 9 will display the error message Google Chrome will ignore the hyperlink. Resolution Instead of linking directly to the web page link to the folder that contains the Hyperlink object and then clicking on the hyperlink object will open the web page in a new window if the target property is empty or "_blank". Another alternative is simply click the "Open this content in a new window" link.

Issue The customer requests End User License Agreement (EULA) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Requests for the End User License Agreement (EULA) Resolution The EULA can be found in the following locations:   "About" box for WorkStation under the "Help" menu. See the screenshots below. WorkStation Help menu EULA   WorkStation Log on Page It is also available in the installation folder (under Workstation\language). WebHelp LICENSING END USER LICENSE AGREEMENT

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

Issue On always overrides Off in weekly schedules in TAC Xenta Environment TAC Xenta programmable controllers Xenta Time Schedules Menta Cause If you have defined Week schedule event to be on and then add another overlapping event to be off all day the schedule will stay on. This is confusing because the off schedule will be added on top of the on schedule in the editor so you can't see the on schedule anymore. Resolution If you want to turn the schedule off temporarily, use an alternative event (uncheck weekly in the editor). Alternative events override all weekly events for the period. If you want to permanently change the schedule to be off just delete/edit the existing event. Remember, if no events are defined for a day the schedule will be off all day.

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 The error below occurs as soon as the Management Console is launched.  Environment Power Manager Power Monitoring Expert (PME) Management Console Cause In order for the Management Console to work properly it needs to see the correct dll files in three separate locations. If the install process of PME was not completed successfully or did not have full administrative rights while installing then some of these files may be missing.  Resolution The issue was that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll was not present in all of the three following folders:     C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin Verify that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll files are present in all three of the locations below. If they are missing in any location, copy and paste the files accordingly.      C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin     Note: Replace "Program Files (x86)" with "Program Files" if you are working on a 32 bit computer.   

Issue Microsoft Hotfix changes the HostId on I/A Series (Niagara) R2 and G3 Enterprise Server or Engineering workstations. See TPA-IA-11-0007.00 for details. Product Line TAC IA Series Environment I/A Series R2 and G3: All 32-bit versions of software installed on 64-bit versions of Windows 7, or Windows Server 2008 R2. Cause Microsoft recently released a hotfix for an issue that affects machines running x64 versions of Windows 7 and Windows Server 2008 R2, described in knowledge base article 2603229. The Windows registry contains entries to designate the organization and owner name that correspond to the computer. Each of these registry entries has a 32-bit and 64-bit version. Prior to applying the hotfix, when the OS was installed and setup for the first time, only the 64-bit version of the registry entries were written, leaving the 32-bit registry entries at the factory default value. I/A Series software HostIds are generated from multiple pieces of information gathered from the registry and hardware components of the host platform. The changes made by this Microsoft hotfix will cause the HostId to change on Windows 7 x64 or Windows Server 2008 R2 x64 machines running 32-bit I/A Series G3 or R2 software. Resolution See TPA-IA-11-0007.00 for recommended solution. NOTE: The TPA indicates that the patch is in the I/A Series G3 "Recovery Files" folder.  The files are version dependent and are located in the Release 3.4.64, Release 3.4.67,  Release 3.5.34, Release 3.5.39 or Release 3.6.31 folder, as appropriate for the specified version.  For other versions, option #1 must be used.

Issue When creating a new database an error pops up that indicates that the Windows login name or password is invalid. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is already a Continuum database created. Permissions for the Windows user are not allowing the database creation. Resolution Check to see if there are Continuumdev and ContinuumLog files in the folder. (Look for the folder path in database initialization) Use My Computer to navigate to that folder and see if the files already exist. If they do, copy them if needed and then delete them. Try the database creation again after that. The Windows user may not have the appropriate permissions as an admin Create a new local admin user and then login using the new login Try the database creation 

Issue Vista webstation - Error message in FIPS-compliant systems first time the logging screen is entered and red X instead of values in TGML pictures Error message in FIPS-compliant systems when Windows Communication Foundation is used to serialize generic types: “This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms” Red X instead of values EcoStruxure Building Operation registration WorkStation Error Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Webstation Cause System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing This security setting determines if the Transport Layer Security/Secure Sockets Layer (TL/SS) Security Provider supports only the TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher suite. In effect, this means that the provider only supports the Transport Layer Security (TLS) protocol as a client and as a server (if applicable). It uses only the Triple DES encryption algorithm for the TLS traffic encryption, only the Rivest, Shamir, and Adleman (RSA) public key algorithm for the TLS key exchange and authentication, and only the Secure Hashing Algorithm 1 (SHA-1) for the TLS hashing requirements. For Encrypting File System Service (EFS), it supports only the Triple Data Encryption Standard (DES) encryption algorithm for encrypting file data supported by the NTFS file system. By default, EFS uses the Advanced Encryption Standard (AES) algorithm with a 256-bit key in the Windows Server 2003 family and DESX algorithm in Windows XP for encrypting file data. For information about EFS, see Encrypting File System. NOTE - The same errors can occur in EcoStruxure Building Operation when registering. Resolution Go to Local Security Settings Security Settings > Local Policies > Security Options System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing = Make sure its disabled to get to local security you can go to 1. go to start 2. Go to run 3. enter secpol.msc 4. press enter NOTE - The same errors can occur in EcoStruxure Building Operation when registering. The Resolution is the same

Issue Does Building Operation use Unicast or Multicast? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Workstation Cause Does Building Operation use Unicast or Multicast? Definitions: Unicast packets are sent from host to host. The communication is from a single host to another single host. There is one device transmitting a message destined for one receiver. Multicast is a protocol for use with IP. Multicast enables a single device to communicate with a specific set of hosts, not defined by any standard IP address and mask combination. This allows for communication that resembles a conference call. Anyone from anywhere can join the conference, and everyone at the conference hears what the speaker has to say. The speaker's message is not broadcasted everywhere, but only to those in the conference call itself. A special set of addresses is used for multicast communication. Broadcast is when a single device is transmitting a message to all other devices in a given address range. This broadcast could reach all hosts on the subnet, all subnets, or all hosts on all subnets. Broadcast packets have the host (and/or subnet) portion of the address set to all ones. By design, most modern routers will block IP broadcast traffic and restrict it to the local subnet. Resolution Building Operation is using only IPv4 and therefore Unicast only. This may change when Building Operation begins using IPv6. At that time, a site may want to use the IPv6 multicast features to address groups of targets.

Issue Can I use a 1.9 key on a 1.74 system? Product Line Andover Continuum Environment CyberStation Cause Key compatibility with Continuum versions Resolution A version 1.99 Andover Continuum key can be used on an older ( Ex. 1.74) system. Andover Continuum Keys are backward compatible. However, you cannot go in the other direction. For example, you cannot put a 1.8x key in a 1.9x system, this will require an upgrade.   All versions of a major revision are supported on the key. Ex. 1.90, 1.91,1.92,1.93, 1.94, and any future revisions of 1.9x are supported.   If you read the key with Excel or MMC, it will actually show as 1,79,1.89, 1.99.    Note: All upgrades are handled through the Licensing Team, requests should be directed to the following email address: BMS.Licensing@se.com

Issue During Vista Installation, receive error message “SQL server service cannot be started” or "Failed to start SQL Server service!". Product Line TAC Vista Environment TAC Vista 5.X.X (Tested on Windows XP SP3 with SQL server 2005 EXPRESS) Cause This issue typically happens after uninstall an earlier version of Vista, and then install a newer version of Vista with the built in SQL server (SQL server 2005 express). Sometimes the SQL server registry key is remained on the computer during the uninstall process. When new installation happens, Vista thinks there is an existing SQL sever; however a failure will occur when try to start the SQL Server service. Resolution It is recommended to use the installation file to uninstall TAC Vista 5.X.X. Follow How to uninstall and completely remove TAC Vista 5 to make sure all files and folders are removed.   Check if SQL Server Service still exists: Right click on “My Computer” and choose “Manage”. Chose “Services and Applications" -> "Services". Check if “SQL Server (TACVISTA)” is listed, if yes, go to next step. Otherwise, restart the computer then run the installation again, issue should be solved now.    Go to “start->Run->regedit” to open “Registry Editor”.   Go to “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/”. Find “MSSQL$TACVISTA” and “MSSQLServerADHelper”. Then delete both registry folders.   Repeat step 4 for “CurrentControlSet001” and “CurrentControlSet003” under “HKEY_LOCAL_MACHINE/SYSTEM/.   Restart computer and run the installation again. Issue should be solved now.

Issue Active alarm view shows alarms in a distorted way or the colors are aren't correct. Click in the alarm area in different places may cause some additional pieces of the fields to display Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Usually this happens on one PC and the others in the system are still working ok. Something on the PC has been installed or is interfering with the painting of the alarm screen.  Resolution Check to see if any MS updates have been applied to the system Run an antivirus and/or malware scan Remove the Silence Column and that should take care of the issue.

Issue How fast does the software run in an AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Cause Knowledge about application cycle time is important when designing project solutions. Resolution Both Function Block and Script programs run at a speed defined by the specific time task they are linked to, the available tasks are: Task 1 - 100mS Task 2 - 500mS Task 3 - 1 Second Task 4 - 5 Seconds Task 5 - 10 Seconds Programs that are not cyclic or time based can be run from a main or executive sequencing program. The AS cycle speeds are comparable to other Building control systems, but the power of the AS allows many more programs to be run in parallel at higher speeds. See also the WebHelp topic Application Scheduler for more information.

Issue The Xenta 102-AX VAV controller does not indicate any terminal load even though the demand is present at the VAV. IE the VAV setpoint is 23°C degrees and the room temperature is 26°C degrees. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX VAV controller Cause The 102ax has been left in calibration mode. When the 102ax is in this mode the terminal load remains at 0% To check this from Vista locate the two points "UCPTvavselection.CPH" and "UCPTvavselection.CPl". These object are located in the VAV_controller object of the 102-AX controller. If one indicates "CALIBR ACTIVE" then the 102-AX  is in airflow calibration mode. This screen capture shows a Normal state of a 102-AX. Resolution To allow the terminal load to respond complete the Airflow calibration. If this has been left this way and no calibration is required a power cycle of the 102-AX will remove the 102-AX from airflow calibration mode. If above was not resolution, then perform the following: Record all settings (screenshot or photos of TGML Configuration pages) Commission controller with Default values. Re-enter all values that were changed from default. Override temperature above effective setpoint + cooling band, and see if terminal load goes +100. Override temperature below effective setpoint  - heating band, and see if terminal load goes -100.

Issue Is it possible to monitor the status of a Modbus interface/device from within a TGML graphic? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Building Operation Server Serial Modbus device Cause It's a very common requirement to monitor Modbus devices and interfaces and show this value on a TGML graphic page. Resolution The attached TGML graphic gives a simple example of how to do this. The screenshot below shows the property to bind the TGML binding to. To see the property "NetworkStatus" for the Modbus network in the binding view double click on Modbus Master Network. To see the property "Status" for the Modbus device double click on the Modbus device in the binding view.   

Issue How to disable UNC power monitoring Environment I/A Series R2 Universal Network Controller (UNC) I/A Series Niagara R2 version 2.301.318 or later Cause UNC that is installed with I/A Series Niagara R2 version 2.301.318 or later has power monitoring enabled. UNC-410 and UNC-520 have the following parameters monitored. Power Loss - alarm on AC power loss Battery fail - alarm if backup battery test fail There could be situations where the monitoring of these parameters needs to be disabled.  Resolution You can disable the UNC's power monitoring function by editing the UNC's driver.properties file.  To access the driver.properties file, in WorkPlace Pro Admin Tool, connect to the UNC and go to the 'Installation' tab. Click on the 'Edit drivers.properties' button.  The line 'power.enabled=true' enables the power monitoring. To disable power monitoring, change the line to 'power.enabled=false'.  After the change, save the changes (File > Save) and reboot the UNC.   For more details, refer to the Niagara System and Power Monitoring Engineering Notes.