Building Automation Knowledge Base

Issue Microsoft Visual Studio causes Just-In-Time Debugging Environment Windows Operating System Cause Visual Studio is installed on the PC and when attempting to perform a task, an error appears claiming Just-In-Time Debugging.  Resolution To disable Just-In-Time debugging: On the Tools menu, click Options. In the Options dialog box, select the Debugging folder. In the Debugging folder, select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key. Click OK.

Issue Is there a way to specify that only HTTPS (Hypertext Transfer Protocol Secure) protocol will be used for communicating with an Xenta Server? Environment Xbuilder 5.1.7 Xenta Server firmware 5.1.7 Cause Certain customers wish to block HTTP traffic on their network. Communication with the Xenta Server uses the HTTP and HTTPS communication protocols. HTTPS is an encrypted protocol for increased security. The security setting in XBuilder for the communication with the Xenta Server decides the level of the security to be used. Resolution The following options are available in Xbuilder 5.1.7: Low – the communication always uses HTTP during the entire session between the web browser and the Xenta Server.  Medium – Communication uses HTTPS during log in and user administration. This is the alternative recommended by Schneider Electric. High – The communication uses HTTPS during the entire session. This alternative encrypts all information. It may slow down the information flow between the Xenta Server and the web browser.

Issue The Vista server is not in operating mode. This is indicated by a red X in the corner of the server icon. Environment Vista Cause Sometimes when databases are moved or upgraded the operating mode is turned off. Resolution Check the Online box under the $System object located in the root directory of Vista.

Issue User can open the database in TAC Vista Workstation, but can not run the project database with an LNS network properly when it has been copied from the project site. TAC Vista Workstation is extremely slow when the user operates it in a separate PC or laptop. Product Line TAC Vista Environment Vista 5.1.X Windows Environment LonMaker / NL220 Vista System Plug-In Cause In the user's PC or laptop, the Vista database can not find the proper LNS port which exists in the project site PC. Resolution Define the database which was copied from the project site as the active database in the "Vista Database" tab in "TAC Vista Server Setup" Run TAC Vista Server application (TACOS.exe) Run TAC Vista Workstation. Wait a while for the TAC Vista Workstation to open the database completely Right click the LNS port. Wait a while for the right-click options to appear, then click "Properties" Record the port name in TAC Vista Workstation and its "Device address" in the properties window to a TXT file and save it. Delete all text in the "Device address" in the properties window, and click "OK" to accept the change Repeat steps 4, 5, and 6 to delete all LNS ports' "Device address" After the last "Device address" has been deleted. The TAC Vista Workstation's response speed will be back to normal. If some modifications have been made to the database and need to be applied in the project (which means the database would replace the project site database), remember to restore the "Device address" name according to the TXT file before restoring on the site PC.

Issue How to find the MAC address / Physical Address of a computer. Product Line Andover Continuum, EcoStruxure Building Operation, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment All computers Cause The MAC address of a computer may be required when working on licensing issues. MAC stands for Media Access Control and is a unique identifier assigned to network interfaces for communications on the physical network segment. Resolution Go to the Start > Run.   Type "cmd" into the Open field. In the CMD window, type the command "ipconfig /all". Locate the connection that the computer is currently using (For this example it is the Ethernet adapter Local Area Connection). You will find the Physical Address (MAC address).

Issue When closing out NL220, an automatic prompt comes up asking 'Do you want to make a backup of the project ?". After selecting yes, the message "Error reading source file." is displayed.   Environment NL220 Vista Cause Error reading source file is a result of creating a NL220 backup while running Vista server. Resolution There are two ways to avoid this error. Shut down Vista server before closing down NL220 and selecting to make a backup.   With Vista server and NL220 still running, go to the menu bar and select Project > Backup project... In the Backup a project... screen, select Backup.

Issue Need to perform autosensing on an ethernet port but do not have a cross over cable. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment Ethernet connection to an Automation Server Xenta device ACX BCX Auto-Sensing, Auto Sensing direct connect Auto uplink and trade Universal Cable Recognition Cause Need to direct connect with a straight through or normal patch cable from a computer or laptop to the AS, Xenta, BCX, ACX  Resolution Since 1998, the distinction between uplink and normal ports and manual selector switches on older hubs and switches are obsolete. If one or both of two connected devices has the automatic MDI/MDI-X configuration feature there is no need for crossover cables. Now you can plug your laptop right into the Ethernet port of the device with just a regular patch cable. 

Issue There are two different methods used for calculating the setpoints in a Xenta 121 controller: method A and method B. Environment ZBuilder NL220 LonMaker Vista Cause Not knowing how each setpoint method is calculated in ZBuilder can lead to using the wrong method in certain applications. Resolution Method A When nviSetpoint receives a valid setpoint, this value becomes the new, common setpoint. The cooling and heating setpoints are recalculated to be at the same distance from the new, basic setpoint as they were from the earlier basic setpoint. Therefore, method A removes any existing asymmetry. The controller calculates the different setpoints for heating and cooling in occupied and standby mode, from nviSetpoint, plus or minus half the neutral zone in occupied and standby modes, which are calculated from nciSetpoints. The controller uses the existing unoccupied setpoints in nciSetpoints for the unoccupied mode. Below are the equations that go into calculating method A:     Method B In standby mode you can choose method B to calculate the existing set-points. The result of method B will only differ from method A when the setpoints are placed asymmetrically around the mean value. With method B the asymmetry is kept. The controller calculates the different setpoints for heating and cooling in occupied and standby mode from nciSetpoints. The effective, absolute setpoint deviation is calculated as the mean value of the occupied_heat setpoint and the occupied_cool setpoint. The controller uses the existing unoccupied setpoints in nciSetpoints for the unoccupied mode.   Below are the equations that go into method B:   Note: If nviSetpoint is not being used, then just remove it from the above equation and calculate.  

Issue Licencing error in RAM log Environment Sigma RAM Micronet Vista Cause The following error is seen in the RAM log when Sigma is installed. Resolution In Sigma, RAM licensing is done using the Sigma dongle. In the "Remote Alarm Manager Computer Configuration Wizard" Select: Start > Licence Scheme and ensure that the "Legacy Licence Schemes" is checked.

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

Issue Unable to upgrade SQL log database from a pre-5.1.7 database to the new Version 2 format that is used (for new installations and optional as upgrade) in 5.1.7. Get the error message: Test of connection successful. Connecting to TAC Vista SQL database. Checking SQL server version and database size. SQL Server Version: Microsoft SQL Server 2008 R2 (SP1) . SQL Server Edition: Developer Edition (64-bit). Data Allocated Space: XXXXXMB. Data Used Space: XXXXMB. Log Allocated Space: XXXMB. Checking TAC Vista SQL database schema version. Checking user access. Upgrading TAC Vista SQL database from version 1.0.0.15 to version 2.0.0.0. Failed to execute SQL upgrade script. Error : Error 9002, line 585: The transaction log for database 'taclogdata' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Environment Vista 5.1.7 SQL log database - either upgrade when installing Vista or using the SQL Database upgrade tool. Cause There is insufficient space for the transaction log to grow during the upgrade process. It is important to make sure that there is enough disk space available before upgrading the TAC Vista SQL database layout. During the upgrade procedure the database will increase its size with approximately 40%. If a SQL database is upgraded in a Microsoft SQL Server 2005 Express environment the database cannot exceed 2GB in size; the upgrade will not allow it. It is possible to upgrade to a Microsoft SQL Server 2008 Express environment where the database size limit for the upgrade is 5 GB. After the upgrade is completed, this additional storage space is not consumed by any data; the additional storage space will be allocated for future data entries in the TAC Vista SQL database. The actual data in the SQL database will decrease with approximately 30% after the conversion is completed. Do not shrink the SQL database size after a conversion; doing so will cause major fragmentation. Resolution Firstly, confirm that there is enough disk space (at least twice the size of the log database) for the database to grow during the upgrade. Secondly, changes the file settings for the database to allow for the increase in size during upgrade Open SQL Management Studio (download here if required) and locate the taclogdata database. Connect to TACVISTA (default) SQL instance. Expand the menu-tree and then expand the databases tree. Locate the taclogdata (default) database. Right-click on the taclogdata database and select properties. Go to the sub-property menu Files. Change the autogrowth settings for the database log file. Go to the list of database files and identify the log file (file type Log). Click the button in the field Autogrowth. Check the size given in the Restricted file growth (MB) field. Either increase this to roughly twice the size of the database to be upgraded or Click the Unrestricted File Growth radio button. Upgrade the database to Version 2 layout.

Issue Is it possible to get a offline alarm in Vista if  the communication with a LON device is lost? Environment TAC Vista 5.1.7 Cause Vista doesn't have a built-in online/offline detection for LON devices. Vista will set the device offline if it  can't read a value from the device.   Resolution Set the "Watch setting" on one of the values in the LON device to "alarm" or "watched", then Vista will continuously poll the value and set the device offline if it can't read the value from the device.

Issue Can I add the group bindings manually as the option to create group binding in the System Plug-in takes time and controllers are taken offline for the period of the process Environment Lonmaker Vista Cause This is  possible to do and works very well and effectively if you understand the process  Resolution Follow these steps to add TAG 0 system bindings and TAG 1 Xenta bindings to your new Xenta controller. In Lonmaker find the source of the TAG 0 binding buy finding any TAG 0 existing binding. Then right mouse click on the tag number and select Go to reference. This will take you to the source of the TAG 0 bindings. If a list of controllers appear then you are already at the source controller. Then Carry out a connection as normal in Lonmaker on that function block. Right click on the Virtual function block with the TAG 0 source and select the connect option. Select the TAG 0 option under the Hub tab then select the target tab and add the new Xenta controller to the system with the Add FB/SNs button. Then select the TAG 0 in the virtual function block of the new Xenta and click on the Add button. The select the OK button. This will add the TAG0 binding to the new Xenta device with the correct binding type. The next step is similar to the TAG 0 but for the TAG 1. You need to locate the TAG 1 Xenta group that you are adding the new Xenta controller into. Once you have located the TAG1 source use the same connection method as TAG0 but use the TAG1 in the virtual blocks. The final step is to download the added controller and the group master.

Issue When Vista reports are opened in Microsoft Excel, various columns show trend log values as times.  The columns above in green are correct, they are formatted correctly. The column in red is in a time format instead of the expected percentage format. Environment Vista 5.1.7 Microsoft Excel Cause There is a formatting incapability between Vista 5.1.7 and Microsoft Excel. Resolution The formatting issue will be corrected in Vista 5.1.8. If using Vista 5.1.7, Hotfix 18 will correct this issue and can be downloaded here. The work around for this problem is to reformat the affected column(s) before saving or printing the report. To reformat a column in Microsoft Excel, following these steps: Open the Vista report. Select the entire column that has been formatted incorrectly. Right click on that column and go to Format Cells... Under the Number tab, select the format that is desired for these values. Click OK. Now print or save the report. Note: Once this change is made and saved into Vista, the issue may still occur in the future. This is just a way to correct the problem temporarily to view the correct values.

Issue Cannot adjust the setpoint up or down on STR-250, STR-202 or M/STAT that is connected to Xenta 102-AX. Also, effective setpoint may not be changing when device goes from unoccupied to occupied modes. Product Line TAC Vista Environment Xenta 102-AX Plug-in STR-250 M/STAT STR-202 Cause This problem is most often caused by a scenario similar to the following example: A 102-AX is in cooling mode with an effective cooling setpoint of 70°F. An STR-250 stat is connected to the 102-AX and has a stat adjustment range (nviSetpoint.SCPTmaxRnge) of 6°F. This allows the occupant to adjust the setpoint ±3°F from the stat. The occupant is hot and adjusts the stat down to its minimum of 67°F. (3°F less than the cooling setpoint) The building operator decides that ±3°F is too much adjustment range and changes nviSetpoint.SCPTmaxRnge to 4°F (±2 degrees F) from the front end. The effective setpoint is still 3°F less than the cooling setpoint but now the stat cannot adjust the setpoint up or down since it steps in .1°F increments and both 66.9°F and 67.1°F are outside of the adjustment range. Since the stat adjusted setpoint offset is not a visible point and cannot be adjusted from the front end, the setpoint offset will be stuck until the stat adjustment range is expanded to include the effective setpoint and the setpoint offset is changed from the stat. Resolution To correct this problem the nviSetpoint.SCPTmaxRnge should be set high enough to include the effective setpoint. This can be done from Vista and can be found in the VAV_Controller object of the 102-AX or it can be done from the 102-AX Plug-in where it is called Stat Adjustment Range and is found on the Operating Parameters page. The setpoint should be changed at the stat to match the setpoint of the mode in which the 102-AX controller is currently operating. (eg occupied cooling setpoint) The stat adjustment range can then be returned back to its previous setting and the occupant can adjust the setpoint up or down and it will stay within the limit.

Issue When creating Vista trend log or Xenta trend log, there are no data in it. The status on the trend log has already been on. And there are a lot of dump files in the $queues folder of the Vista database folder. Environment Vista Trend log Xenta Trend log Cause There is something wrong the SQL Server database so that the trend logs can’t be stored into the SQL Server and have to been stored in the $queues folder temporarily. Resolution Assign another SQL Server database for Vista. Open the Vista Server setup, and switch to the SQL Server tab. Choose the SQL configuration to Custom, and rename the Log database name to a new one, which is shown as below:   Pay attention that at that time TAC Vista integrated SQL backup/restore function will not be available in Custom configuration.

Issue The delay on and delay off functions do not work correctly inside of the 700 Menta alarm block. Instead of delaying the signal for the configured amount of time, the signal is delayed for a random amount of time before being passed on or turned off. Environment Vista XBuilder Menta Xenta Server 701, 711, 721 and 731 Cause Documented defect in 700 Menta alarm block. This defect has been confirmed in XBuilder 5.1.5 through 5.1.7. Resolution This 700 Menta issue has been corrected in XBuilder 5.1.8. If using a version of XBuilder 5.1.5 through 5.1.7 the following workaround can be used. Leave the delay on and delay off settings in the alarm block at zero. Add a delay block in front of the alarm block. Set the desired delay on and delay off values in the delay block.

Issue Vista user would like to search the network for property value settings on specific input and output points.  Including the ability to search for all physical points that have been forced by operator. Environment Analog Inputs Analog Outputs Binary Inputs Binary Outputs Physical Points Vista Search Function Cause User needs to obtain a list of physical points within a network to monitor values or to see a list of points that have been forced by operator. Resolution In workstation, select the search function icon in the taskbar located directly above the network pain. Select the browse button  located next to the drop down menu labeled "Types of devices and objects:" and a new search window will appear titled "Select Type"  In the "Select Type" window you will navigate through the tree to Points > Analog Point > Analog Input > Analog Input - RPU and check the box on the left. Repeat step 3 for Analog Output, Binary Input, and Binary Output To complete the search for ALL physical points in a network you will select "Search Now".  Once complete your points will appear in the lower view pain in workstation. NOTE: You will select "Forced by Operator" from the drop down picker under Property Value if you wish to search the network for all points that have been forced by operator (Typically, String: "*" and Equal to: "1"). You will select "Value" to get a list of points showing the live values of the points.

Issue Can not edit time schedules (time objects, TSCHI, time object page) in TAC Xenta Server Changes in time objects doesn't get saved No times shown in time object  (no schedules shown in time object) Environment TAC Xenta Server 731, TAC Vista Server 721, TAC Vista Server 711, TAC Xenta Server 701 Cause If there are a time object (time schedule) that has an corrupt definition all following schedules will not work. We suspect that the corruption comes from a upgrade. Resolution To check for corrupt schedules Log in to the TAC Xenta Server Go to Configuration-time objects-View definition. Here is an example of a correct definition and a incorrect definition of the same schedule Once you have identified any definition that looks suspect open Xbuilder Edit the time object that contains the definitions Right click and select "Show events" Take a note of the times you want to keep Delete all schedules Close the schedule editor Edit the time object again and add back the schedules Download the project again.

Issue Trend chart settings aren't saved. The properties dialogue is opened by right-clicking on the open trend chart and then one or more of the settings are changed. After that OK is pressed and then the chart is saved using the save button. Product Line TAC Vista Environment TAC Vista 5.1.7. Cause It appears that the new settings aren't being saved, but by clicking the save button before refreshing the trend chart the current "view" is saved - not the new settings entered in the properties dialogue. Resolution Change the settings as described Click OK when finished with the settings Refresh the trend chart immediately Save it. The view with the new settings will be saved. Another option in Windows 7: Right click on the chart object. Go to the "general" tab Uncheck Autoscale Enter the desired value.