Building Automation Knowledge Base

Issue WebClient Pre-Installation Requirements for Server 2016 are not included in the 2.03 webClient installation guide Product Line Andover Continuum Environment Windows Server 2016 Continuum webClient Server 2.03 Cause The Pre-Installation requirement steps provided in the webClient planning and installation guide do not show all the steps needed to install webClient successfully Resolution This material is intended as a supplement to the webClient Planning and Installation Guide   Installing IIS on Windows Server 2016 For Windows Server 2016, install IIS on the designated web.Client application server (LAN systems) or the standalone CyberStation/web.Client workstation (standalone system). 1. Start the Server Manager by clicking on the Administrative Tools menu. 2. In the Server Manager, click Add Roles and Features. 3. In the Add Roles and Features Wizard, Before You Begin tab, click Next. 4. In Installation Type, select Role-based or feature-based installation. 5. Click Next and then select a server or virtual hard disk on which to install roles and features. 6. In Server Selection, click Select a server from the server pool. 7. Click Next and select one or more roles to install on the selected server. 8. In Select Server Roles, please select the items from the following snapshots carefully Note: In previous Windows Server instructions from the webClient pre-installation guide, a reference was made to select Application Server. This option is selected and installed by default in Windows Server 2016. No selection for Application Server is offered.   Once these Pre-Installation steps have been performed the webClient Server is ready for Chapter 4 - Installing web.client on the IIS PC (Found in the webClient planning and installation guide.pdf)

Issue An error message is displayed when trying to save changes to a Programmable Xenta in Menta Editor. The error message is: Tam32 Save Error Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (E) Error message trying to save changes in Menta Editor Product Line EcoStruxure Building Operation Environment Building Operation Workstation 3.0.2 or earlier Xenta 281 Xenta 301 Xenta 401 Cause A defect in Menta Editor causes this error to be displayed when a SNVT name in the Menta application is identical to the programmable Xenta device name.  An example of this is shown below: Resolution This problem has been fixed in Hotfix 3.0.2.2500 and the fix is included in version 3.1. For earlier versions there are two ways to resolve this problem; Either a) rename the Xenta device, or b) rename the SNVT. a) Renaming the Xenta device In Workstation right click the Xenta device and choose Rename Click OK Now you can edit the Xenta in Menta Editor without getting the error message b) Renaming the SNVT Right click the Xenta device and choose Edit In Menta Editor double click the block with the SNVT binding to edit the block Click the Bind... button to edit the binding Change the name, click OK to close the dialogs and Save the changes

Issue When trying to update the OS of a BCX9640 to a BCX4040, the update process seems to succeed but the controller remains unchanged after the update process completes. Continuum indicates no errors during the update process. Environment Convert BCX BCX9640 BCX4040 Update OS Firmware Cause Incompatible bootloader. Resolution Update the controller to the most current version of OS for the same controller model before updating the OS with the new model firmware.

Issue Most systems have an Overview Graphic of the whole building.  The user then navigates from this graphic to specific floors and rooms of interest. If the Workspace is configured incorrectly, navigating to a newly selected graphic does not work as expected. The overview graphic does not disappear and the new graphic is forced to open very small at the edge of the screen. Product Line Building Operation Enterprise Server Environment Workspaces Cause The standard Administration and Engineering Workspaces used in EBO contain a Work Area Window (WAW) which is necessary 'space' to show a selected graphic/trend/schedule If an Overview Graphic Pane is created in a Customer Workspace and this graphic takes up most of the screen, there is no space left to show the new object which the customer wishes to see Note: The Overview Graphic 'Building' is now shown in a Graphic Viewer only   When the system tries to open a new graphic, there is not space to open it in, The graphic is forced to open at the very edge of the screen and is therefore very small. Resolution General information about creating and using Graphic Panes, Work Area Windows and Panel Components can be found in the EBO webhelp, But for specific information on how to prevent a graphic opening at the edge of the screen see below.  Rather than adding a Graphic Pane to the Workspace to show the Overview Graphic add a Work Area Window (WAW) instead. Next, define the required Overview graphic as the initial path for the WAW on startup so the Overview graphic opens at user log on. Note: The Overview graphic 'Building' is now shown in the WAW rather than the Graphic Viewer. Graphics will always close themselves on navigation to the next object by default when used with a WAW (this can be changed). As soon as the user needs to navigate away from the overview page to a new graphic/schedule/trend, the system can use the WAW which will then use most of the screen as the 'space' to show it. In this case, as soon as the link to the next graphic 'Floor' is pressed, the first graphic 'Building' closes according to its default and the new object is shown in its place.

Issue In Webstation, when clicking on a hyperlink located on a TGML that references another TGML, nothing happens. Product Line EcoStruxure Building Operation Environment Webstation Cause Sometimes when a graphic is saved, it gets compiled incorrectly. When this happens, the graphic will generally work inside Workstation because Workstation is a closed environment and much more forgiving then Webstation. Resolution Edit the graphic that you cannot open Save it again It will get recompiled correctly

Issue Site has a personnel database with about 10K records, the site is switching to dual credentials and has configured the Personnel Manager to use HIDCorp1000 as the default for card type 2 and xxx as the default for Site Code 2. Problem is when going to change the personnel the Card Type 2 field still comes up with Infinity37 and Site Code 2 of 0 instead of the configured defaults. Environment CyberStation Cause Any existing personnel in the database will come up with Infinity37 for the card number 2 and 0 for the site code 2 as those were the values populated in the SQL database for those fields when the system was configured for only one credential. When creating NEW personnel objects the fields show the configured default values. Resolution When creating NEW personnel objects the fields show the configured default values.

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue WorkStation crashes when opening some TGML graphic pages following a windows update Product Line EcoStruxure Building Operation Environment Windows 7 64 bit SBO v1.6.1.5000 with KB3045171 windows update Cause Windows Security update KB3045171 can cause WorkStation to crash if some fonts have been used within the TGML graphic The example seen was using font "Dotum" Security Update for Windows 7 for x64-based Systems (KB3045171) http://support.microsoft.com/kb/3045171 If this does not resolve your issue see Graphics Editor will not open and causes a font related error. Resolution Microsoft have produced a fix for this problem (KB3065979) see https://support.microsoft.com/en-us/kb/3065979 The PC must be rebooted following this update before the problem is corrected.

Issue When using the LPA through an Automation Server (AS) as described in Using Loytec LPA with SmartStruxure AS, only traffic to and from the AS is captured. Product Line EcoStruxure Building Operation Environment LPA Automation Server Cause Due to a hardware limitation in the AS, it's not possible to capture all traffic on the segment Resolution Connect the LPA to the segment using a NIC-USB100 or similar

Issue Who to contact for Continuum - Easy-Lobby integration support.  Environment Continuum Security Cause Unsure of who to contact for Continuum - Easy-Lobby integration support.  Resolution The Continuum - EasyLobby integration is supported directly by HID - EasyLobby.     For sales or technical support: EasyLobby support email is support@easylobby.com . U.S. support phone number 866-607-7339 (option 8). International support phone number: +1-949-732-2000, option 3, then option 8.   If you have EasyLobby sales questions, or need a quote or a web demo, please call 781-455-8558 or contact jmooradian@hidglobal.com, jmurzycki@hidglobal.com, vrowan@hidglobal.com or your HID sales rep If you need EasyLobby technical support, please contact support@easylobby.com or call the HID tech support line at 866-607-7339 and select Option 8 If you are placing an EasyLobby order, please resend it to easylobby-sales@hidglobal.com or fax it to 781-455-6766 If you have questions about the status of an order already placed, please contact Customer Service vrowan@hidglobal.com, kzarrow@hidglobal.com If you have questions about adding a feature or doing custom engineering, please contact Product Management nwahlander@hidglobal.com

Issue Need to use the Automation Server port log to view BACnet MS/TP communication Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to capture BACnet MS/TP traffic for troubleshooting. Resolution In EBO 2024 (V6.0) and higher, there is an integrated packet capture feature available in EBO Servers with BACnet Interfaces. This feature allows users to create packet captures that record the BACnet messages that are visible to the EBO Server’s BACnet/IP and BACnet MS/TP networks. Refer to: Packet Captures in EcoStruxure Building Operation

Issue PID module has gone to "control-point" Product Line TAC INET Environment I/NET DDC PID Cause The PID may have gone to "Control Point" due to unforeseen circumstances and is causing a problem. "Control Point" can also be used intentionally as a control strategy. Resolution Four reasons: If the Setpoint’s value crosses above or below the high or low input limits as populated in the PID editor, this will force the PID to go to control-point. If the process variable should reach the low or input sense limits as entered in the Resident I/O editor, the PID will go to control-point. If either the Setpoint or Process variable should go to "OLD" status, the PID will go to control-point until the "OLD" flag goes away. If the user should change any variable within the PID, when exiting the PID editor, the PID will go to control-point until the next scan of the module. For more information on this subject refer to Tech Tip G062.

Issue It is recommended to save often when working with Menta. Product Line TAC Vista Environment Menta Cause We have experienced lockups of Menta when we conduct very long programming sessions. Resolution Save often. When you take a break, shut down Menta and then restart it when you return. This will help you to avoid losing time should Menta freeze up which is known to happen. It is good practice to let Vista DB folder structure be the file cabinet. When a change is required, export the application from Vista, make the changes, then re-import to Vista and download the controller. This will keep your field environment in synchronization with the operator interface.

Issue What is Tuning? (History, DDC, PID, FLT) Environment I/NET Site Cause When speaking of History, DDC, PID, and FLT, what is Tuning?  Resolution Tuning is the on-line, automatic adjustment of PID or Floating module parameters. For more information refer to your System Operator Guide or TCON 083.

Issue If I add a TAC Xenta device to an existing TAC Xenta group, do I have to update other Xenta devices as well? Product Line TAC Vista Environment Xenta programmable controller (e.g. 401, 301, 281) Xenta groups TAC Vista system plugin Cause Each programmable Xenta device needs to know the name of all the other Xenta groups, as well as all the Xenta device names in its own group. Each time a new group member is added, all Xenta devices in that group need to be downloaded. If a new Xenta group is added, all Xenta devices in all groups need to be downloaded.   This provides new network description files to the controllers so they can communicate properly. Resolution All Xenta devices in that group must be updated. LonMaker or NL220 and your Vista databases need to be updated as well. TAG bindings will also need to be added to the new TAC Xenta device if an LNS database is being used. The TAC Vista System plugin has the feature under the LNS Network menu. "Create Group Bindings" If this is a large site this will take some time and cause offline devices during this process. In this case, these bindings can be added manually to the new controller. This will prevent all the other devices having there TAG bindings deleted and the new TAG bindings created. The following articles show the process for manually adding TAG bindings. Manually adding a Xenta Device with Group bindings in NL220 Manually Adding Xenta device with Group bindings in Lonmaker

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 How do I create a Multi-Columned report for an A-Sample Trend? Using I/NET Seven and Sub Reports (Seven Reports) Product Line TAC INET Environment I/NET Seven 2.21 and below Cause In most BMS systems the most common report was a tabular (or column report) of data. Seven Reports (Crystal Reports) did not provide this facility easily.  Although it can be achieved using the subreport feature within Seven Reports.   Resolution The Steps to create this report are discussed in the following link. Subreports process w screen captures.doc

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 How do I import the "Version 5.1 Sample.IWX" from the I/NET Seven CD into ID Works 5.1 Software? Product Line TAC INET Environment I/NET site with IDWorks Cause How to import the "Version 5.1 Sample.IWX" from the I/NET Seven CD into ID Works 5.1 Software Resolution Please use the following document link: Import_ Project_IDW5p1.doc

Issue Some customers may specify that the login screen to a Xenta Server be bypassed. Environment Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When accessing a Xenta Server using a web browser a username and password are required by default. Resolution Configure the user you want to automatically log in to the Xenta Server Generate a certificate To avoid having the certificate error pop up every time you connect to the Xenta Server, go to XBuilder, and generate a certificate that has the same name as the IP address of the Xenta Server. Edit Slogin.html and loggedout.html Connect to the Xenta Server using FTP ftp:// XXX.XXX.XXX.XXX The Slogin.html and loggedout.html are located in the folder www/index Copy the files to your local hard drive Edit the files with, for instance, notepad and change the following Slogin.html Line 54 document.AuthForm.UserID.focus();" document.AuthForm.UserID.focus(); send(AuthForm);" Line 98 input type="text" name="UserID" value="" size="20" > input type="text" name="UserID" value="user" size="20" > Line 104 input type="password" name="PassWord" value="" size="20"> input type="password" name="PassWord" value="password" size="20"> loggedout.html Line 5 (extra line, add < symbol at beginning of line) meta http-equiv="refresh" content="2;url=/www/index/Slogin.html"> Carry out the changes Reconnect to the Xenta Server using FTP Change the names of the files that are already in the Xenta Server (Backup) Copy the files that from your hard drive to the Xenta Server