Issue How can a webpage be integrated into Vista graphic pages for a seamless transition between a graphic page and a 3rd party website such as: Static information, such as a site webpage Device webpage (power meters, sensor, etc. Product Line TAC Vista Environment Vista Server 5.x.x Cause The Hyperlink database object in Vista can store a URL address. By linking to this Hyperlink object with a standard link in a Vista graphic page, standard components can be used and support common graphic pages for different sites and reusability. Note:  More complicated integration can be accomplished with javascript, but this requires custom components such as accessing web services such as weather.com data for actual display on your graphic page. Resolution Create a Hyperlink object in the Vista database for each page you want to make available. Use a link in the TGML graphic page to access this Hyperlink object. Clicking the link on your graphic page will display the webpage in the Vista Workstation window. Target Property The target property can be configured for Webstation display to control the window or frame the link is opened in. The options _top, _self, and _parent will be ignored in WebStation and treated as _blank, which will open a new tab or frame depending on your browser settings. If you specify a target frame you must match the exact syntax of the WebStation frame names from the following list: TAC_WebStation_header TAC_WebStation_left TAC_WebStation_contents TAC_WebStation_footer

Issue In many situations, customers need to integrate more than one LNS database into a single Vista database. Product Line TAC Vista Environment Vista LNS LonMaker NL220 TAC Vista System Plug-In Cause This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database. This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database. Resolution Some general rules must be followed when integrating multiple LNS databases into one Vista database. These rules are: You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication. NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack. When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously. If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed. Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server. It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below. The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2. Please follow these instructions: Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.   The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database. As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400

Issue .MTA file not updated .MTA file does not show the correct value when exported/imported The Menta project does not have the correct value when imported into a new database Product Line TAC Vista Environment Vista Menta Xenta OP Cause The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save. Resolution  Below is the correct way to edit a project in a new database.  On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database. Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.  Export the database/project Import the database/project to the new PC Make the desired changes Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file. Export the database/project Import the database/project into the client's PC Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE StruxureWare Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Lost/Forgot/Modify the SysAdmin SQL default password created during the installation of TAC Vista 5.X.X in typical mode. Product Line TAC INET, TAC Vista Environment TAC Vista 5.x.x SQL 2005 Express Microsoft SQL Server Management Studio Express: (http://www.microsoft.com/download/en/details.aspx?id=8961) Local Admin rights Required. Cause Procedure if SQL Password is Lost/ Forgotten or Modification required. Resolution When you click on Microsoft SQL Server Management Studio Express, it will open the below page and require you to choose the way you want to log in: either by “Windows Authentication” or “SQL Server Authentication”. If you want to log in using Windows Authentication, choose this option and go in. (It uses the Windows login credentials). If you want to log in using SQL Server Authentication, choose this option and enter Login and password. If you want to change this Login and Password: Enter using the Windows Authentication Choose Security > Logins > Select the login ID Right click and go to Properties Change the password and re-login using the new password. Below is an example where the password for the login 'sa' has been changed:

Issue Error in Xenta 527 HyperTerminal     This error happens over and over (with different file sizes each time), and the controller essentially locks up and requires a restart to recover. Product Line TAC Vista, TAC INET Environment TAC Vista  below version 5.15 Xenta 527 using Controller LAN (RS-485) I/NET Cause Vista will poll I/NET for the past 1000 entries. Normal internal events consist of much less data than the I/NET events; 1000 I/NET events in one message make the message too large. The VSD Response too large error indicates Xentas max message size has been reached. TAC Vista ignores the error and repeatedly tries, leaving the Xenta 527 stuck in a loop. Resolution Polling I/NET for fewer events fixes this problem. The max number of events in one message has been adjusted down to 400. This change is included in TAC Vista revisions 5.1.5 HotFix 16 and later.

Issue Measuring dry bulb temperature and relative humidity and need to use them to calculate the following Enthalpy Wet Bulb temperature Dew Point temperature Product Line TAC Vista, Ecostruxure Buildings Operation Environment Function Block applications Cause Need to calculate Enthalpy, Wet Bulb Temperature, or Dew Point Temperature.  These values are typically used to compare the latent heat in the outside air versus inside air for economizer cycles, in chilled water applications where condensation must be avoided, or in humidity control applications. Resolution Enthalpy - the total energy of both the dry air and water vapor per pound of dry air. Wet Bulb temperature - the temperature a volume of air would have if cooled to saturation by evaporation. Dew Point temperature - the temperature to which a volume of air must be cooled for water vapor to condense into water. Download the appropriate HFB below: Psychrometric Calculations in US Imperial Measurements Psychrometric Calculations in SI Metric Measurements

Issue How to use AutoCAD layout in TGML Graphic Product Line TAC Vista Environment Vista 5.1.9 and earlier versions of Vista 5 TGML Graphic AutoCAD Cause Sometimes it is necessary to use the AutoCAD layout in TGML graphic, for example, to use the plant layout as a background. The official support for importing AutoCAD files was removed early in the life of TGML. It can’t be guaranteed that EVERY file will import without a problem, so it is an unsupported feature. Resolution The following steps need to be followed: Open the drawing in AutoCAD Save as .DXF Open TGML Editor File Open the .DXF A screen should pop up saying converting DXF to SVG followed by converting SVG to TGML It is recommended to use the "Create path" command in the Object window in TGML for the converted graphic. Because the response speed of the computer will be very slow if used without this action. Note: Line widths and text will be in disorder because they are not imported along with the object. If the DXF file fails to import, here are some steps to try: Move every object in AutoCAD to a single layer Delete all unused layers in AutoCAD "Explode" complex objects in AutoCAD

Issue An unexpected database error occurred. "There can only be one LCA Object Server ActiveX control per process. Please make sure that you only have a single Object Server control in this process." "Could not listen on _poet/tcp: The address is already in use or another server already running. (-2532)" Environment LonMaker NL220 Vista LNS Cause Microsoft Exchange 2003 Server and other OEM software sometimes use TCP ports 6001 or 6002. This causes a conflict since the POET server (FastObjects DB) defaults to TCP ports 6001 and 6002. Resolution For an automated solution, refer to: https://community.se.com/t5/TAC-Vista-Forum/LonMaker-POET-Port-Changer/td-p/271427   For a full explanation from Dialog Semiconductor, refer to: https://edgesupport.diasemi.com/hc/en-us/articles/206494283   Further details   Check that the ports used by LNS are not being blocked (firewalled) or used by another application. To verify this, type in the following command from a DOS prompt: netstat -bn You should now get a list of in-use TCP ports. Look for an entry saying {your computer name}:6001 or 6002. If you find one, you have located a conflict and you will need to change the POET Port numbers. Check if you run a firewall on this PC. If yes, you need to find the list of Programs with their Internet Access level and make sure you have given access to the appropriate files. To run LonMaker/LNS , you need to give access to ptserv32.exe, LonMaker.exe, lonpoint.exe, visio.exe, lmwbrw32.exe and lsass.exe. You can modify the ports used by the POET server and clients by modifying the "Services" file (%WINDIR%\System32\Drivers\Etc\Services) using a text editor like Wordpad.exe or Notepad.exe. For example, to change the POET port numbers to 7001 and 7002, add/modify the following lines in the "Services" file. The  '#' in the example indicates that the following text is a comment. For Win XP: use "Windows\System32\Drivers\Etc\Services". If you see the "poet" and "_poet" entries, go ahead and change the port numbers from 6001 and 6002 to 7001 and 7002. If you don't see these entries, simply add the lines below. poet          7001/tcp    #FastObjects services _poet        7002/tcp    #FastObjects services https://echelon.force.com/support/s/search/All/Home/562?tabset-95728=2

Issue Is it possible to configure a Xenta 121/122 controller with an STR-150 and lock the thermostat so that the user cannot change the temperature setpoint from the STR-150 device?   Product Line TAC Vista Environment STR-150 Xenta 121 Xenta 122 STR Sensor Cause In some applications, you do not want anyone to change the setpoint from the room unit. Resolution It is possible to configure the STR150 device so that it is not possible to adjust the actual setpoint. Enter configuration mode for the STR150 by Pushing the fan and bypass buttons simultaneously for 2 seconds to enter P0. In P0, hold down the bypass button and push the fan button three times. Press the fan button until you see P7, and change the P7 value to zero. To Exit Configuration Mode, push the fan and man button for 2 seconds. The timeout will exit configuration mode if idle.

Issue How to change the STR-150 temperature display, setpoint adjustment range, etc. Product Line TAC Vista Environment STR-150 STR Sensor Cause The communication between the STR-150 and the TAC Xenta 121/122 device is one way, space temperature and setpoints are sent from the sensor to the controller. Therefore some STR-150 functions (for example, the setpoint adjustment) can not be configured though Zbuilder, but needs to be done manually in the STR 150 device. Resolution Buttons on the thermostat: Increase Button Decrease Button Bypass button Fan button Wrench symbol   Steps of changing the STR-150 configuration are listed below: Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0 In P0, hold down the bypass button and push the fan button three times to enter configuration mode. NOTE: the wrench symbol is lit when the STR-150 is in configuration mode.   In configuration mode: Press the fan button repeatedly until reaches desired parameters (refer to the configuration table below). NOTE: the two digits farthest to the left on the display show the parameters, while the two digits farthest to the right show the value Use increase button or decrease button to change the value.   Exit configuration mode: Push the fan and bypass button simultaneously for 2 seconds. Or, the timeout will exit configuration mode if idle.   Configuration Options: Parameter Function Value/Range Default value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 1=°C P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 22°C / 72°F P3 Setpoint or room temp. 1=Setpt, 2=Room 1=Setpt P4 Timeout 5-90 seconds 10 seconds P5 Fan Settings 0=No fan 1=On/Off fan 2=Two-speed fan 3=Three-speed fan 3=Three-speed fan P6 Room temperature and setpoint display resolution 0.1 or 0.5 °C 0.2 or 1.0 °F 0.5 °C or 0.2 °F P7 Max adjustable setpoint span above or below Reftemp (P2). +/- 0 - +/- 5°C +/- 0 - +/- 10°F +/- 3° or +/- 6°F P8 Bypass button and occupancy indication When = 2, no bypass command is sent  to the controller 1= Symbol on, off Or flashing 2=Symbol always off Default 1=on, off Or flashing P9 Setpoint as Absolute or Offset value 1=Absolute 2=Offset 1=Absolute   Click here to read STR-150 user's manual.

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  

Issue Test and air balance procedure for balancing airflow Product Line TAC Vista, EcoStruxure Building Operation Environment Building Operation Automation Server Premium  TAC Xenta 102-AX  TAC Xenta 102-AX Plug-in Cause Each 102-AX controller must be calibrated on-site to report accurate airflow readings.  The LNS Plug-in provides this functionality, but it may not be immediately clear what the correct procedure is to perform a valid calibration. Resolution Check the firmware version of your 102-AX controllers in the plug-in, Node Configuration tab. It will be shown under Program Revision. If it's anything earlier than 2.1.6 then the calibration won't work properly. The airflow setpoint changes but the damper does not modulate to maintain setpoint in the calibration mode. Your options in that situation are to manually manipulate the damper to maintain airflow setpoint in order to facilitate calibration or upgrade the controllers firmware. Also verify that the box is set to "Pressure Independent" mode on the Unit Parameters tab.  Pressure dependent boxes do not use airflow sensors, and therefore cannot be calibrated. To balance the 102-AX in Building Operation version 1.4 or higher where the LNS plug-in is no longer provided, review the article TAC Xenta 102-AX TGML plug-in for Building Operation To calibrate airflow using the 102-AX LNS plug-in:  Go to the Node Configuration Tab. Select "Set Default m & b." This is a good idea before each calibration attempt since incorrect calibration values can make it more difficult to perform a valid calibration. (NOTE: The m & b values can be viewed under the Airflow Parameters Tab of the 102AX LNS plug-in...m = Velocity Pressure Gain & b = Velocity Pressure Offset) Select "Start Calibration." At this point the airflow setpoint should go to the minimum. You can check the Cooling Minimum airflow setpoint on the Airflow Parameters tab. The damper now modulates to maintain the minimum cooling flow setpoint. Watch the VAV Reading (Low) and wait for it to hit the minimum flow setpoint and level out. If the airflow is fluctuating a lot, it could be that the low setpoint is below the threshold the box can confidently supply. Or it could be bad placement of the flow sensor in a turbulent area of the duct. It can affect your calibration greatly if the value is fluctuating too much. A relatively level reading will provide a good calibration. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (Low) and select "Continue." The damper now modulates to maintain the maximum cooling flow setpoint. Watch the VAV Reading (High) and wait for it to hit the maximum flow setpoint and level out. When it levels out, measure the actual airflow with a highly accurate magnehelic hood. Enter the actual value into Reference (High) and select "Finish." The new calibrated m & b values are shown. The gain (m) is shown in the format of multiplier/divisor. Divide the values to get a decimal format of the gain. The closer to 1 this value is, the less calibration was required. actually gains of 2 or more indicate probable airflow reading problems. It may be advisable to reset factory calibration values and try the calibration again. The box should now be displaying values very close to actual measured readings. Test the low and high flow during normal operation using the Status Tab, Right click on the Space Temp and override the space temperature to a value equal to or greater than the Occupied Cooling Setpoint plus half the Cooling Band to drive the airflow setpoint to the cooling maximum airflow setpoint (you can find the Occupied Cooling Setpoint and Cooling Band on the Operating Tab).  With the space temperature already in override, left click the Space Temp to change the space temperature without taking it out of override, and set the space temperature to the Occupied Cooling Setpoint minus half the Cooling Band to drive the airflow setpoint to the cooling minimum airflow setpoint.  With the space temperature in override, right clicking it will take it out of override.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue The SLO Label shows an incorrect value range for kL. Product Line Field Devices Environment SpaceLogic SLO series Lux sensor Cause The label on the SLO shows the incorrect value range for kL. Resolution SLO: The product specification sheet states the Ranges for the jumper as: - 0 to 500 lx and 0 to 20 kLx The range to 500 lx can be seen on the circuit board. The product’s label shows 0 – 4kL The manufacturer has confirmed the label is incorrect the value should be 500 lx, New labels will be used in production from August 2022.   SLR: The tense delivery situation during the pandemic, especially for electronic components, has forced the manufacturer to make technical changes to the SLR in order to stay able to continue to deliver reliably. The range has extended from 0.4 to 0.5 kLux. These changes are incorporated in the corresponding instructions, provided with the devices. New labels will show the extended range.

Issue Certain Xenta controllers and I/O modules can accept 1.8k thermistor temperature inputs. Product Line TAC Vista Environment Xenta 121-FC Xenta 200 Xenta 300 Xenta 420A Xenta 450A Cause What is the temperature vs resistance curve of the 1.8k thermistors for Xenta 300? Resolution All Xenta controllers and I/O modules, except the Xenta 102-AX use the same 1.8k thermistor (type 1.8KA1). The following table shows details the Temperature vs. Resistance characteristics for this thermistor. Temp (°C) Minimum kΩ Nominal kΩ Maximum kΩ -50.0   60.87  63.88  67.03  -45.0   45.41  47.5   49.68  -40.0   34.23  35.68  37.2   -35.0   26.04  27.07  28.13  -30.0   19.99  20.72  21.47  -25.0   15.48  16.0   16.54  -20.0   12.09  12.46  12.84  -15.0   9.512 9.779 10.05  -10.0   7.541 7.733 7.929 -5.0   6.021 6.16  6.301 0.0   4.84  4.94  5.042 5.0   3.916 3.988 4.061 10.0   3.189 3.24  3.293 15.0   2.612 2.649 2.686 20.0   2.151 2.177 2.209 25.0   1.782 1.8   1.818 30.0   1.478 1.496 1.514 35.0   1.233 1.25  1.267 40.0   1.033 1.049 1.065 45.0   0.8698 0.8848 0.9001 50.0   0.7357 0.7497 0.7639 55.0   0.6251 0.638 0.6511 60.0   0.5334 0.5453 0.5573 65.0   0.457 0.4679 0.479 70.0   0.3931 0.4031 0.4132 75.0   0.3395 0.3485 0.3578 80.0   0.2942 0.3025 0.311 85.0   0.2559 0.2634 0.2712 90.0   0.2233 0.2302 0.2373 95.0   0.1956 0.2019 0.2083 100.0   0.1718 0.1775 0.1835 105.0   0.1514 0.1566 0.1621 110.0   0.1338 0.1386 0.1436 115.0   0.1186 0.123 0.1276 120.0   0.1054 0.1095 0.1136 125.0   0.094 0.0977 0.1015 130.0   0.084 0.0874 0.0909 135.0   0.0753 0.0784 0.0816 140.0   0.0676 0.0705 0.0735 145.0   0.0609 0.0635 0.0663 150.0   0.0549 0.0574 0.0599

Issue Error received when attempting to login to Vista Workstation:   Could not connect to Vista Server.  Login error. Or, error received when trying to login to Vista Server: Invalid entry. Username and/or password cannot be verified in the system. Product Line EcoStruxure Building Operation Environment Vista Workstation Cause The username or password is incorrect. Resolution Check the username and password and try again. Log in with the default System account (Username= system / Password= system), or any other $Administrators username.  Reset the user's password. Open Vista Server Setup and ensure the security level has not been changed on the Authority tab. If a Vista user account no longer works set the security level to "Low Level". If a NT account no longer works set the security level to "High Level". If all system level logins have been lost, contact Product Support.  Send a backup of the database to be unlocked.

Issue Modbus slaves are programmed according to device documentation, but either the wrong values are returned or error codes complaining about invalid address. Product Line TAC Vista Environment Xenta 913 Xenta 731 Xenta 511:B Cause The XBuilder Device Editor has two ways to address modbus registers. The improper usage of these methods can cause communication problems because the wrong register is polled. 1. Fixed Address Blocks This method combines the function code and register address to produce a single number format that serves multiple function codes. This is sometimes referred to as numerical notation. A poll of a holding register uses function 03 and an address from 00 00 to FF FF. When using Fixed Address Blocks a message of function code 03 and address 00 00 is displayed as 40001. Due to this combination it is limited to 9,999 addresses per function code. Type Function Code  Address  Coil Status  01  00001-9999  Input Status  02  10001-19999  Holding Register  03  40001-49999  Input Register  04  30001-39999 When the device editor is using Fixed Address Blocks then the numerical number is parsed from the Register in the following way. Register Function Code Address 1-9999 01 Register - 1 10001-19999 02 Register - 10001 30001-39999 04 Register - 30001 40001-49999 03 Register - 40001 2. Function Code Tables (Discrete Input, Coil, Input Register, Holding Register) This addressing format is closer to the actual protocol and keeps the function code separate from the register address. It also provides full use of the addresses from 0 to 65535. Table Function Code Discrete Input 02 Coil 01 Input Register 04 Holding Register 03   If the wrong format is used it can result in failure to communicate because the wrong register is used. For example polling register address 40010 on function code 03 when it should have been address 9 on function code 03. Resolution The documentation of the product being interfaced with is the best guide on the register addressing and the format they use. If the documentation does not directly specify the information then use the follow hints to guide your selection: Hints to use Function Code Tables Addresses that fall on zero (0, 10000, 30000, or 40001) Non binary data that is less then 30001 or greater then 40001. Devices states it is J-Bus. Register address is displayed in Hexadecimal format. Hints to use Fixed Address Blocks Any address register above 30000 or 40000, unless it claims to be a JBus device. If it is still unclear which addressing format to use then experiment with read only data and value pages in the Xenta Servers. Pick a point that you can easily confirm the value, add both address formats to a device template, and then confirm the proper format with a values page. Once you know how to read one point the rest of the product documentation is easier to work with.

Issue What is Domain Name Service (DNS)? Product Line Andover Continuum,EcoStruxure Access Expert,EcoStruxure Building Expert,EcoStruxure Building Operation,EcoStruxure Security Expert,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment TCP/IP Networks Cause DNS is a distributed hierarchical system for resolving host names into IP address. Under DNS, there is no central database with all of the Internet host information. The information is distributed among thousands of name servers organized into a hierarchy similar to the UNIX file system. DNS has a root domain at the top of the domain hierarchy that is served by a group of name servers called the root servers. Source: TCP/IP Network Administration by Craig Hunt, O’Reilly & Associates, Inc. Resolution Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.