Building Automation Knowledge Base

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

Issue   Save error There is no file associated with the object It is possible to create the TGML object in TAC Vista and right click and edit it but not to save the changes. Environment TAC Vista 5 Workstation TGML Graphic Editor Cause It is not possible to save any TGML graphic in a TAC Vista folder that has a ":" (colon) in the name. Resolution Change the name of the folder to not include a ":" (colon).

Issue Clicking on Time Schedule in Xenta Server, gives this security warning Java has discovered application components that could indicate a security concern. Name:  se.tac.applet.toe.TOEApplet Block potentially unsafe components from being run? (recommended) After clicking "No" it works to browse different Time Schedules without any problem. After logging out and in again you get the warning again Environment TAC Xenta 5xx/7xx/9xx Java 1.6.-19 or later Cause This is not the recommended Java version for this Xenta server version. Resolution Change the mixed code settings in the Java control panel. For information on how to do this go to: http://www.java.com/en/download/help/error_mixedcode.xml   OR Uninstall Java 1.6.-20 (or later) Install Java 1.6.-17

Issue Vista 5.1 license is not working.  Trying to launch Vista components results in error:  lc_checkout failed: Cannot checkout an uncounted license within a Windows Terminal Services guest session. Environment Vista 5 Terminal Services Virtual Machine VM Cause There is a special feature needed in the license which allows the use of Terminal Services. Resolution You must download the 14 day Demo TS Evaluation License on The Exchange Download Center. *note that Terminal Services are only supported in Vista 5

Issue  System Plug-In returns "Error: 80010105" when downloading a programmable controller. Environment Vista Server NL220 / Lonmaker System Plug-In Cause The cause is unknown at this time.  When downloading a controller through System Plug-in this error will stop the download from proceeding.  It seems to be system-wide once it happens, not controller related. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs Uninstall the TAC Toolpack Re-Install TAC Toolpack (make sure it matches the Vista Server version).

Issue LOYTEC NIC-USB card shows offline in NL220 Cannot communicate to NIC-USB card when opening NL220 Product Line TAC Vista Environment NL220 NIC-USB Loytec Cause Proper setup of a NIC-USB in NL220 is required in order for the NIC-USB card to be able to communicate with NL220 or TAC Vista Server.  Resolution A tool called LConfig need to be installed on the computer before the configuration. Click here to download and install  the configuration tool (NIC - LOYTEC Network Interface Software 4.1.4). Connect the NIC-USB to the computer Use LConfig (Start/All Programs/LOYTEC Network Interface/Lconfig) to configure the NIC-USB Choose the USB tab Check "Enable USB Network Interfaces" Click "Test Device/Serial Number" Go to NL220. In the project open window, select the correct NIC-USB in the "Network interface" box. Click "OK"

Issue How to make a graphic page pop up in Vista Workstation when an alarm occurs. Environment Vista Workstation Cause Steps of making a graphic page pop up in Vista Workstation when an alarm occurs may not be very obvious to many users. Resolution Locate the alarm object in Workstation. Right click on that alarm object and select "Properties" In the "Properties" window, select "Video/Graphic" tab. In the "Linked graphic" text box, browse to your graphic object and click "OK" to save it. Check "Show graphic automatically". This is also discussed in the TAC Administering Manual in Chapter 7.

Issue Device driver open failure Echelon LonMaker Failed to open network interface device. (Subsystem: NI, #39) Environment LNS LonMaker Vista Cause NI error #39 is a network interface error. It indicates that the network interface driver failed to open the network interface. For the i.LON 10 or i.LON 100, this error occurs when the LonWorks Interfaces driver configuration on your computer does not match the network interface settings in your i.LON 10 or i.LON 100. Improperly seated PCMCIA PCC-10 LON Adapter. Can happen with some regularity when using a NIC852 and going onnet through LNS Server.  Subsequent attempts are usually successful Resolution If the LON Adapter is not properly inserted, you should try removing it and plugging it back in, or by using a second card temporarily and then switching back to the original card. If unsuccessful... To correct the error, open the LonWorks Interfaces Control Panel program and verify that the port setting, authentication key, hostname, and DNS suffix match the settings in your i.LON 10 or i.LON 100. To open LonWorks Interfaces, click Start, click Control Panel, double-click LonWorks Interfaces, and then click the RNI tab. Please reference the i.LON 10 or i.LON 100 user guides or online help for instructions in modifying the configuration of an RNI. When opening your network, make sure you select the correct network interface. For an i.LON 10 or i.LON 100 RNI, the name that you select in the LonMaker tool must match the name that you see on the LonWorks Interfaces RNI tab. Echelon Support KB515 .

Issue How to set up a periodic report in Vista Workstation.  Troubleshooting techniques to solve a periodic report that will not run. Environment Vista Workstation 5 Cause There are three objects required to work together.  They are: Time Event - Object Report Report - Periodical Resolution Verify settings in each of the three Vista objects Time Event - Object Create a Time Event - Object.  Right-click and go to Properties. View the Time Event Settings Tab Choose the interval type and frequency. Ensure a start time is checked and occurs prior to when the report should run. Check a stop time.  If a stop time is needed, leave it checked.  If not, uncheck it. Click OK Right-click again and go to Properties. View the General Tab Description is optional Next Event: should be populated with a date and time. Report Create a Report object.  Right-click and go to Properties. Go to the Report Tab If the report is to be printed, define a printer. If the report is to be saved to the hard drive, define a destination folder. Define a report file name.  This will be the name of the saved folder. If multiple copies are to be saved, uncheck overwrite existing file.  Files will be saved with a datetime extension on the file name. To insert a trend log or value into the report, navigate to the report in Vista Workstation, right click, and go to edit. Select a cell in excel towards the top left of the page where the trend or value will be inserted. In excel menus, navigate to Vista Links > Insert > Trend Log or Value. Browse in the value or trend log out of the vista database, adjust settings to the project preference and click okay. Finally make sure that the report is saved to the Vista database by navigating to Vista Reports > Save.   Report - Periodical Create a Report - Periodical.  Right-click and go to Properties.  This is the object that will tie together the Time Event - Object with the Report. General Report:  Browse to the Report object in the Vista database Settings Active: must be checked. If the report is to be printed, check Print report. If the report is to be saved to the hard drive, check Save copy Event Settings Event:  Browse to the Time Event - Object in the Vista database If the report is to run when the event begins, check Tripped If the report is to run when the event ends, check Reset.  At least one of these should be checked.

Issue Downloading the .chm help file from a Xenta 5/7/9xx controller help button results in the following error: Navigation to the webpage was canceled What you can try: Retype the address. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Content of the compiled HTML file is blocked for security reasons. Windows blocks the content because it assumes it has come from another PC and could be harmful.  Resolution Right click on the .chm help file and go to Properties Click the Unblock button under security Click apply and then OK Re-open the file

Issue How to use Wiegand 26-Bit format cards in Security Expert with the new Custom Credentials Product Line EcoStruxure Security Expert Environment Wiegand 26-Bit Format Access Cards Custom Credentials Cause From the release of Security Expert 4.3, Custom Credentials have been introduced as a 'new' way of handling cards with formats such as Wiegand-26 Bit. Resolution Select Sites > Credential Types and create a new Wiegand Credential Type called Wiegand 26-Bit with the following format: A,FACILITY,8,MSB,BIN_B,CARD,16,MSB,BIN_PAAAAAAAABBBBBBBBBBBBBBBBP_EXXXXXXXXXXXX............._.............XXXXXXXXXXXXO Select Programming > Door Types and create a new Door Type called Wiegand 26-Bit. Under Entry select a Reading Mode of Custom and then select 'Add'. Select the Wiegand 26-Bit Credential Type created earlier. If using Custom Credentials on both Entry and Exit this will need be done for both as shown below. Select Programming > Doors and ensure the Door Type of the Door being configured is set to the Wiegand 26-Bit Door Type created earlier. Select Expanders > Reader Expanders and ensure the Readers for the configured door are set to Custom Credential (Reader 1 Secondary format does not actually take effect and is set to Custom Credential here simply to avoid confusion). Select Users > Users and create a test User.  Do not use the regular Card Numbers section which is filled out for cards which do NOT use the Custom Credential, and instead scroll down to the Credentials section at the very bottom of the General Tab. Add the Wiegand 26-Bit Credential Type and Specify the users cards details in the format: Site Code : Card Number and then test.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.   Issue On a new installation of SmartConnector, the service is not able to start. The log shows a SQL server authenticate error. Product Line EcoStruxure Building Operation Environment SmartConnector Cause For some countries, the administrator account has been localized. (List available here: If the operating system is using one of these localized languages, the Windows administrator account may not be recognized by the SmartConnector service, https://social.technet.microsoft.com/wiki/contents/articles/13813.localized-names-for-administrator-account-in-windows.aspx ) Resolution Workaround 1:  Reinstall a non-localized version of Windows.   Workaround 2: Create a new user in the SQL database.   Workaround 3: Open Microsoft SQL Server Management Studio and connect to the SQL instance the SmartConnector will use. Using the Object Explorer menu, navigate to the logins folder: 'Machine-name > Security > Logins' Right-click on the Logins folder, and select 'New login' A window will appear, to configure the new user account. Provide a Login name: this is the log-in the SmartConnector will use. Then select 'SQL Server Authentication', fill in the password field, and type it a second time in the 'Confirm password' field. Select 'Server Roles' from the menu on the left side of the account windows. Check both 'public' and 'sysadmin' if not already checked. Move to the next page: 'User Mapping' Select 'SmartConnector.Service' row, update 'User' and 'Default Schema' with 'dbo' value. Check the 'Map' box, then in the bottom list check the 'db_owner' box. Repeat steps 10 & 11 for 'SmartConnector.User' entry. Click 'OK'  Now that the user is created Uninstall the SmartConnector and restart the machine Reinstall the SmartConnector, and select 'SQL authentication' when requested Provide the newly created login with the associated password. Complete the SmartConnector installation. Validate the service is running without error.  

Issue Viewing Script time from the editor can show incorrect time Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB, AS Classic Building Operation Enterprise Server Building Operation WorkStation Script Program Editor Cause Scripts use Local Server time, but the Clients like Script Editor or WorkStation expecting a server to be UTC. The result is that during Daylight Saving Time, the time seen in the script editor may appear an hour out. Resolution During debugging of Times or Dates or DateTime Values, it is helpful to "Print" the Datetime to a string as this will show actual time being used rather than the Clients interpretation of the time (See script below).The client will take the Server time as UTC and apply offsets to achieve its "Local" time, which can give an incorrect time. The UTCOffset property can be used to correct for time zones but there is no DST(Daylight Saving Time) offset available until v4.0.

Issue What is the b2 and i2 Controller Object Format property used for? Product Line EcoStruxure Building Operation Environment Continuum Conversion i2 Controller objects b3 controller objects Cause i2 and b3 Controller objects include a a Format field for objects created using the Continuum Conversion tool. What is this used for and how does the value effect the operation?     Resolution These Format values are propagated through the Continuum Conversion Tool for reference only and have no impact on operation in EBO. The values cannot be modified. In EBO there are two ways to configure numeric display formats. -In WorkStation property pane and watch window, the number of decimals displayed to the right of the decimal point is inherited from the WorkStation PC's regional settings. This setting applies to all values displayed in WorkStation except for values in graphics. -In graphics, the number decimals displayed to the right of the decimal point is configured value-by-value in the Graphics Editor.   The format value is not stored in an EBO export and if objects are manually created, then standard formats are used for the type of object created .

Issue Deleting logs from External Log Storage takes a very long time. Workstation becomes unresponsive when deleting trends from External Log Storage. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause The deletion process can take a long time on large PostgrSQL databases, sometimes as much as an hour.   Workstation must complete the deletion process before it becomes available for other tasks.   When logged into Enterprise Server to delete a trend that was hosted by a child server (Automation Server), Workstation tags the log for deletion.  The AS that held the original log, will survey the trend_meta table every hour to check for pending flags, and will then delete logs that are flagged.  This can cause the deletion to be delayed by as much as an hour.   Resolution The following method should be used when deleting trends from External Log Storage: The trend must no longer exist in EBO. Log on locally to the server that hosted the associated trend.  Then deleted the trend from the System\External Log Storage folder. Indexing the trend_data table can improve the speed of deletion dramatically in large PostgreSQL databases (1 TB or larger).

Issue The SmartX Controller Advanced Display requires internet access in order to activate the Kiosk Mode on initial startup. Product Line EcoStruxure Building Operation Environment SmartX Controller Advanced Display v2 and v3 SmartXKiosk Cause The SmartX Controller Advanced Display requires internet access in order to be activated on initial startup, site IT departments may need to allow access for activation to proceed. Resolution Internet access is required only once during initial installation to activate the Samsung license If you are in the Americas, enable access to these servers:  Server Port gslb.secb2b.com 443 us-prod-klm.secb2b.com 443 us-elm.secb2b.com 443 If you are in China, enable access to these servers:  Server Port china-gslb.secb2b.com.cn 443 china-klm.secb2b.com.cn 443 china-elm.secb2b.com.cn 443 If you are in Asia, Africa, Europe, or other regions, enable access to these servers:  Server Port gslb.secb2b.com 443 eu-prod-klm.secb2b.com 443 eu-elm.secb2b.com 443   For additional communication paths, refer to the online help topic Information Technology System Planning Guide

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When restoring a Continuum database the process fails with a Cannot show requested dialog error message. Index was outside the bounds of the array. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Server Microsoft SQL Server Management Studio Cause The version of SQL Server Management Studio is not compatible with the Microsoft SQL Server version. In this example the error occurred when attempting to use SQL Server Management Studio for SQL Server 2005 Express to restore a database on an SQL Server 2012 Express server. Resolution Uninstall the incompatible version of SQL Server Management Studio and then install a compatible version. The database can then be restored.

Issue Security Expert client Status Window is not showing live point status for inputs, outputs, doors. Shows an error message “Status Unknown” instead. The client is still however able to receive access control events such as reader entry/exit. Product Line EcoStruxure Security Expert Environment Security Expert Cause MSMQ (Microsoft Message Queueing) is not enabled. This is a requirement for MSMQ to be installed on the Security Expert Server, the Security Expert Client machines do not need this but the machine where the Security Expert Services are installed does need this feature installed to function properly. Resolution Windows 10 In Windows Features settings (Turn Windows features on or off) turn on the “Microsoft Message Queue (MSMQ) Server” and the “Microsoft Message Queue (MSMQ) Server Core” features. Windows Server 2016 or above  Start Server Manager. Select Manage / Add Roles and Features. Click Next. Select Role-based or Feature-based installation Click Next. Select the server where to install the feature. Go to Features, and navigate to Message Queuing / Message Queuing Services and select Message Queuing Server. Click Install to start the installation. The setup may require a system restart. Click OK to finish.  

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue When launching Security Expert after restarting the PC, a License Expired message is shown. The license is not able to be found. Product Line Security Expert Environment Security Expert Client Security Expert Licensing Cause This is a timing issue. The Security Expert services are attempting to start simultaneously as Windows components that they rely on. Resolution Change the Startup Type of the Security Expert services to use Automatic (Delayed Start), so they start after the Windows OS components. Services - Automatic Delayed   It is also possible that the Security Expert Data Service may be the only service that requires being set to a delayed startup to resolve this problem.