Building Automation Knowledge Base

Issue Intrusion Alarm System for TAC I/NET Building Automation Systems Environment I/NET Site using Intrusion Alarm System for TAC I/NET Building Automation Systems Cause Certification Requests Certification Requests including Grade 3 Resolution The I/NET Access Control security products are certified and Listed under Underwriters Laboratories standard UL294. We do not have certification with NSI or SSAIB. Reference to NSI and SSAIB suggest a probable European security application. If that is the case, the application may be a candidate for our recently released TAC I/NET security products listed below - ICPB - Intrusion Control Panel Base ICPE - Intrusion Control Panel Expander ICPD - Intrusion Control Panel Distributed OP5 - Operator Terminal The above system panels were certified to the European Security System Standard EN50131 and the Swedish standard SSF1014 by - SP Sveriges Tekniska Forskningsinstitut SP Technical Research Institute of Sweden Box 857, SE-501 15 Borås, Sweden Tel: +46 (0)10 516 50 00 Telefax: +46 (0)33 12 50 38 Internet: www.sp.se The Security system panels and their functional performance were tested and certified to the following standards - EN50131-3:2009 Alarm systems - Intrusion and hold-up systems - Part 3: Control and indicating equipment EN50131-6:2008 Alarm systems - Intrusion and hold-up systems - Part 6: Power supplies The above two standards are used to test/evaluate intrusion systems for compliance with EN50131-1 SSF1014:2005 System components – Intruder Alarm Systems Requirements and test methods EN60950-1:2001+A11:2004 Information technology equipment - Safety EN61000-6-3:20007 Electromagnetic compatibility (EMC) - Generic Standards - Emission standard EN50130-4:1996/A1:1998/A2:2003 - Electromagnetic Compatibility - Product family standard: Immunity requirements for components of fire, intruder and social alarm systems. The TAC I/NET EN50131 compliant system is documented in TCON314 Installation Manual and TCON315 operators Manual. The security system detailed above was certified and registered with the organization - SBSC SBSC is Sweden’s leading organization for certifying companies, products, management processes and personnel within fire protection and crime prevention. This is covered under SBSC Certificate number 10-523 (copy available at link provided) PA-00148 Vista Security Intrusion Certification.

Issue Unable to update an ASC when adding a new MR to an existing system. Product Line TAC INET Environment All versions of I/Net utilizing HVAC applications. Cause On a system that has multiple sublan devices and adding a new or several devices to the controller, when updating the UPD files it appears to get downloaded but when the MCI update is done, only one point is written to the database. If the points are added manually, a Memory Error would come up indicating that there is not enough memory in the controller to do this. However, this is not seen when doing the UPD file update nor MCI Update. Resolution To resolve this issue, the following steps needs to be done: Connect to the controller Go to Edit/Controller/Configuration Verify that the controller does in fact have memory left If not, look at the trends that are on the resident I/O Points If possible, delete unwanted trends that are using up memory to free it up to allow these devices to be added Once done, go back to ASC Parameters and then update the ASC and MCI again.

Issue Filtering The AnalogSamples_xi.rpt SevenReport using the cell definition Environment I/NET Seven Reports Cause In some cases, the cell number can be used on a 7 trend to allow only trends of a certain type to show up in reports. If this rule is applied, you will need to change the stock reports to allow for this function. Resolution Open the AnalogSamples_xi.rpt file in Seven Reports Cancel the Date Time range selector In the Design View, click on the second icon from the left, directly underneath the word "Design" the tool tip labels it as "Select records to be used in report  Select Expert" Click on the " " tab browse to the bottom and expand "RptTrendDefinitions" Click on "CellNumber" Click OK In the left hand drop down select "is equal to" In the Right hand drop down, enter the cell number you wish to filter for. Click OK Preview the Report Save it using a different file name. 

Issue How to estimate the thermal load (BTU/hr) that your controllers and equipment will produce. Environment All electrical equipment. Cause Need to know what the thermal load of our equipment will be for calculating air conditioning capacity. Not all of our equipment has this information provided in data sheets. Resolution It is possible to calculate the thermal load based on the power consumption of each device. See here for an online calculator. You can calculate the BTU/hr using the following formula. BTU/hr = Power (W) * 3.1412141633 As an example, looking at the Continuum AC-1 I/O module's datasheet, we see that it consumes 2.6W without the attached reader (you would need to add the power from the reader as well if it is being powered by the AC-1). Which gives us; AC-1 = 2.6W * 3.412141633 = 8.87 BTU/hr Use this same calculation for any other devices that you require the thermal load for.

Issue User has a backup of my files that they have restored onto a new workstation PC but now they are unable to edit the files.  For example: A Continuum graphic needs to be edited and cannot save changes but can save as a new graphic. Environment Window OS Windows XP Windows 7 8 8.1 10 Windows Vista Cause This is caused by Microsoft Windows OS. Windows will automatically make a file "Read only" if it has been moved from another PC  Resolution The solution is to change the files back to read / write. Example: Open Windows Explorer and find the folder you want to change, for this example it is "Continuum graphics." Right click on the folder and select properties, which shows a tab that will be ticked next to "read only" deselect this tab and then select apply. Once windows has finished changing the folder and its contents to read/write the user will be able to go into continuum and edit graphics.

Issue When using Conversion Coefficient slope m = 1.0, the return to normal (RTN) Alarm Limit on an AI point appears to have a built-in offset. Environment I/NET Seven - Analog Inputs (AI), all revisions. Cause There is a built-in hysteresis of 3 counts on the return-to-normal settings for both the low and high limit setting of an analog input (AI) point.  When using a conversion coefficient slope (M) of 1, this provides a 1:1 scale between counts and engineering units which could provide undesired results.  So this built-in hysteresis needs to be considered when using a slope (M) of one or higher on analog input alarm points.    Resolution Consider using a conversion coefficient slope (M) of 0.1.  Alternatively if this is not possible, creating an internal AI point (using a m = 0.1) or a DA and applying a calculation to reflect the points value or alarm state as required as a workaround.

Issue Receive data from Trend log (Seven Trends) with incorrect base time hh:12 even though it is set to 00:00.   Environment I/NET Seven  Seven Trends Xenta Server 527 / 527-NPR / 731 Cause When using a Xenta Server as an I/NET NetPlus Router (NPR) and have configured a Trend (Seven Trends) with a sample count of 24 and sample interval of 60 minutes it appears that the time is incorrectly reported to the I/NET Host.  This issue will be rectified in a future release of the Xenta Server firmware.  Resolution As workaround to this issue, the Sample Count value below 24 should be used.   This is issue is not seen when using a Direct Connect configuration 

Issue I/NET Host Tool with StruxureWare Building Operation Environment I/NET Site StruxureWare Building Operation Site Cause I/NET Host Tool support with StruxureWare Building Operation Resolution With the current release of Building Operation, I/NET Host Tool is not supported. Licensing of the Host Tool comes from a TAC Vista server and the graphics converter is not in the I/NET Host Tool. 

Issue Explanation and detail required for Client Access License (CAL). Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET Environment Windows  SQL Server Cause Information on Client Access License (CAL). Resolution Server licensing and Client Access Licenses (CALs) for the MS Server or MS SQL can become complex. It may be worthwhile to research further through Microsoft resources. SQL Server 2008 is available under three licensing models: Server plus device client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device. Server plus user client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each user. Processor license. Requires a single license for each CPU in the operating system environment running SQL Server. This license includes unlimited client device access. SQL Standard will normally come with 5 CALs. If more than 5 connections exist, then ore SQL CALs need to be purchased. See Microsoft Volume Licensing for more information. Note: MS Server CALs are separate and are also required. EcoStruxure Building Operation does not check CAL Client Access Licensing. EcoStruxure Building Operation Reports Server can be run using Microsoft SQL Express.  

Issue Changing one Filemaster to another Environment All versions of I/Net Cause Possible corruption on Filemaster and needs to be changed to a different Filemaster then repromote as a client. Resolution To resolve this the following steps needs to be followed: Demote the original Filemaster to a stand alone option and backup the database Demote all the clients to stand alone option Restore the backup from the original filemaster to the PC that will be the new Filemaster Promote to Filemaster Option and allow the icon to change states to where it allows clients to connect Promote all other clients to Equalized Clients by pointing to the new Filemaster Once Equalization is online again, the system should be working again.

Issue Unable to Bind to an I/NET Point Command Error Alarm after Binding to an I/NET Value Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Workstation Cause As of version 1.4, I/NET input points can not be bound to SmartStruxure outputs. A Command Error Alarm will occur when attempting to bind to an I/NET controller that does not have the current bin file Resolution If needed create an additional I/NET output point and use that to control the I/Net input point via a Calculation Point Extension. In I/NET, connect to the controller. Select Edit > Controller > Configuration If the Build Date is older than April of 2012, you will need to upgrade the controller. In StruxureWare, when setting up the bind to the I/NET point, be sure to edit the I/NET point objects bindings, if that is what is being controlled. Bind the desired StruxureWare value to Control Value (DO) or Value (AO) property of the point for I/NET.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Environment Remote Control Software. Cause Not all features are seen when a BMS platform is viewed using remote control software. One example is: When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. Resolution When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. The above example is one scenario. There are a number of other remote control software applications where similar instances may occur. If such an issue occurs, check that the BMS software is functioning correctly by both being viewed and ran in the same environment. Because of the number of different remote control software options that are available, anomalies will prevail.

Issue Card Reader gets a valid card read but does not unlock the Door. Environment All versions of I/Net using DPU's 7910, 7920 and SCU 1284. Cause The Door does not have an Exit Reader but the parameters are set for Anytime. Resolution To resolve the issue, the following steps need to be followed: Connect to the Controller Select Controller/Doors Select the door in question and click on the Modify button In the Editor, at the Exit Reader, click on the drop down menu and select None from the options. Click on Okay and close out the Editor.

Issue Trouble with I/NET to Building Operation bindings. Site can bind an internal I/Net AO to a analogue value in Building Operation but the value won't update. Value appears with a blue triangle that says "unresolved".  Environment I/NET Seven together with StruxureWare Building Operation Cause I/NET points are integrated into Building Operation as points. When you upload the device configuration to the Enterprise Server, the configuration and point information are created in the System Tree pane. You edit and command the points as needed, using WorkStation and I/NET Seven editors. There are ten possible point types available in I/NET: Analog input (AI) Analog output (AO) Discrete input (DI) Discrete output (DO) Discrete alarm (DA) Discrete monitor (DM) Discrete control (DC) Digital input (GI) Digital output (GO) Pulsed input (PI) Resolution For any I/NET inputs (AI, DI, DM, GI and PI) it is only possible for operator changes to be made via the Building Operation Properties. It is not possible to programmatically control I/NET inputs and therefore not to be able to bind an output to an I/NET input point. It is also not possible to programmatically change any points Test state, any outputs (AO, DC, DO and GO) Manual state. And finally it is not possible to programmatically acknowledge an alarm. Therefore it is not possible to bind any script, schedule, FB, etc to any I/NET Points Test, Manual, Alarm Acknowledge or input point.

Issue DMO and SMO from SQL Environment DMO and SMO from SQL Cause A site which was running I/NET and StruxureWare Building Operation, and as required, I/NET is running as a service. The SQL DMO caused an issue with I/NET running as a service and interrupted the INET service. What is SMO and DMO DMO is part of SQL 2005 backwards compatibility. Which has to be installed when going to SQL 2008 to allow the old I/NET database to be imported. With SQL 2008 they now use SMO instead of DMO. You cannot remove DMO without creating a new data base.  Resolution I/NET SQL interface is based on DMO (Distributed Management Objects) so it will not work with SMO (Server Management Objects). That is the reason the backward compatibility must be installed.  Sites that are using a 64 Bit Workstation and 64 bit SQL then there is a 64 bit backward compatibility that should be installed. The 64 bit BCM is in the Support folder on the original install CD called SQLBCM_64Bit.

Issue The thermostat appears to be in OFF mode and can't be cycled through the modes as indicated by the manufacturer's directions.   Environment Venstar T2700, VST2700 thermostats for red-wire control connected physically to a controller Cause It seems that the polarity of the dry contact was set to the default Normally Open (NO) state. Using the Venstar EZ-Programmer to apply the correct settings for use with an occupancy point did not overwrite the polarity of the Venstar's dry contact, but did overwrite the Dry Contact Operation. Also, by wiring everything up first, we did not power up the thermostat to change the mode before it got the closed dry contact command from the BAS. So when we did power everything up, the dry contact was closed, but the thermostat understood that this was an "unoccupied" command since it was still set to NO. Even though the security settings allowed the mode to be changed, when Dry Contact Operation is enabled, the mode can only be changed in occupied mode. When the thermostat goes unoccupied, it stays in whatever mode it was in previously, and controls to the unoccupied setpoints. By not realizing that the EZ Programmer didn't overwrite the polarity, we assumed the dry contact operation and polarity were correct and a closed dry contact would enable the occupied mode.   Resolution This issue can be resolved by powering up the thermostat before connecting the dry contact relay and changing the mode to "auto". If already wired, make sure the dry contact polarity is set to Normally Closed (NC) and Dry Contact Operation is "Yes". Then the modes can be cycled while occupied. < acc0432manualrev1.pdf="" manuals="" support="" www.venstar.com="">

Issue DDC lines from I/NET sublan devices are not showing up in StruxureWare Workstation Environment I/NET to StruxureWare integration Cause I/NET ASC devices, particularly the MR-VAV series, can sometimes be configured as MRs. When this is the case, most of the I/NET processes will function, so that this is easy to overlook. Resolution Open I/NET Workstation Connect to the controller that is not showing the DDC lines from the subLAN Select Edit>Controller>MCU Configuration Change any controller that is an MR-VAV to an ASC Change any MRxx series controller to an MR. Perform a Station Save Open StruxureWare Workstation Right Click on the Selected Controller and select Upload Check to see if the DDC lines are now showing up If not, you may need to update I/NET Network Configuration, then deleted and rediscover the I/NET devices affected.

Issue How long does PSS support a product after it is released? Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment All Schneider Electric Buildings Business software platforms Cause After a few years, the majority of issues with a release product are documented in the Knowledge Base.  At this point, if the customer is having issues requiring Product Support, we ask that they upgrade to the current version. Resolution Please read the following Product Announcements: PA_00271 Software Support Policy - General Overview.pdf PA_00272 Software Support Policy - Supplementary info for_Andover_Continuum.pdf PA_00274 Software Support Policy - Supplementary info for TAC Vista.pdf PA_00279 Software Support Policy - Supplementary info for TAC INET.pdf PA_00280 Software Support Policy - Supplementary info for TAC IA Series.pdf

Issue Unable to Edit I/NET Trends, Schedules or DDC from StruxureWare Building Operation Workstation on certain computers. Environment StruxureWare Building Operation Workstation Cause I/NET functions are launched from StruxureWare Building Operation Workstation using both graphics and Right Click menu items. These functions are not part of Building Operation Workstation, but are simply portions of the I/NET workstation application being launched from Building Operation. Resolution I/NET workstation should be considered an Engineering Tool for I/NET controllers. Any User that needs to make programming changes must have I/NET installed.

Issue When adding a filter, an error shows that Entry already exists. But this name is not listed in the Filters window. Sometimes the filter is defined, but it is not shown in Filters window, especially after a database restore in DBCreate. After defined a filter on the server, this filter can be chosen on the remote client or remote client with I/O. It works fine for the server, but after selecting it on the client, nothing shows up with a blank screen. Product Line TAC INET Environment I/NET Server/Remote Client or Remote Client with I/O Cause If your workstation type is configured as a Client or Client w/IO, a Global Filter option will be available. If you activate this option, this particular filter will be available to other workstations that use the same server. But if not, this filter will only show up on that specific client. So each filter will be bound with a hidden parameter called FilterHost. If the FilterHost is 0, then all the server and clients can see this filter, while if the FilterHost is a specific number, only the client with that Host Number can see this filter. But sometimes there is something wrong with the database that the setting of the filter setting doesn't match the record in the database. Resolution For issue 1, check the setting on all the clients to avoid name conflict with each other. The filter setting for all the clients are stored in the database of the server. For issue 2, change the Host Number of current client to match the original Host Number setting when the database is backup on this client. For issue 3, delete this filter, maybe defined in old version of I/NET, and re-add it again. If all the solutions don't work, please contact Product Support for help.