Label: tac vista - Building Automation Knowledge Base

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for  the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

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.  

Issue Trying to open TGML Graphics Editor and an error appears before the editor crashes.  Crash report shown below: Font 'Arial' does not support style 'Regular'. ArgumentException at System.Drawing.Font.CreateNativeFont() at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont) at System.Drawing.Font..ctor(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit) at SE.Graphics.Viewer.Windows.GDIPlus.RenderText..ctor(Double left, Double top, String textContent, Double fontSize, String fontFamily, Int32 fontStyle, Int32 fontWeight, Int32 horizontalAlign, Int32 verticalAlign, Int32 textDecoration) at SE.Graphics.Viewer.Windows.GDIPlus.DrawingFactory.createText(Double left, Double top, String textContent, Double fontSize, String fontFamily, Int32 fontStyle, Int32 fontWeight, Int32 horizontalAlign, Int32 verticalAlign, Int32 textDecoration) at SE.Graphics.DOM.TGML.TgmlText.getUncachedShape() at SE.Graphics.DOM.TGML.TgmlStrokeShape.getShape() at SE.Graphics.DOM.TGML.TgmlTextShape.getShape() at SE.Graphics.DOM.TGML.TgmlStrokeShape.getUncachedBoundingBox() at SE.Graphics.DOM.TGML.TgmlShape.getBoundingBox() at SE.Graphics.DOM.TGML.TgmlShape.HandleAfterBoundingBoxChanged() at SE.Graphics.DOM.TGML.TgmlShape.OnAfterBoundingBoxChanged() at SE.Graphics.DOM.TGML.TgmlShape.OnChildElementChanged(Node element, ChangeType changeType) at SE.Graphics.DOM.TgmlInheritedElement.FireChildElementChanged(Node element, ChangeType changeType) at SE.Graphics.DOM.TgmlInheritedElement.insertBefore(Node newChild, Node refChild) at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(Node newChild) at com.sun.org.apache.xerces.internal.dom.ParentNode.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ElementImpl.cloneNode(Boolean deep) at SE.Graphics.DOM.TGML.TgmlShape.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ParentNode.cloneNode(Boolean deep) at com.sun.org.apache.xerces.internal.dom.ElementImpl.cloneNode(Boolean deep) at SE.Graphics.DOM.TGML.TgmlShape.cloneNode(Boolean deep) at TAC.Graphics.Editor.Core.GraphicsComponent.ExtractContent() at TAC.Graphics.Editor.Core.ComponentStencilItem.LoadItem(String file, String imageFile, String& description, Image& image) at TAC.Graphics.Editor.Core.FileStencilItem.Load(String file) Product Line EcoStruxure Building Operation TAC Vista Environment TGML Graphics Editor Multiple installations of Microsoft Office Cause If a PC comes with Microsoft Office 2010 (which is not currently compatible with Vista) and additional versions of Excel 2007 are installed, for example, it could remove or corrupt the installation of certain fonts. Resolution Obtain a fresh copy of the font .TTF file.  In this example, Arial.ttf. Install the font by dragging and dropping the .TTF file into C:\Windows\Fonts directory.

Issue When using CIDR (Classless Inter Domain Routing) or Supernetting it is not always obvious what range of IP addresses can be used. Product Line EcoStruxure Building Operation Environment Device Administrator Building Commissioning Tool Cause When subnet masks with values other than 255 are used it is not always obvious what is the range of valid IP addresses allowed.  There is a need for an easy way to determine the range of valid IP addresses for the Subnet Mask being used. Resolution The IP address range can be calculated mathematically but the simplest method is to use a subnet calculator.  The website links below are both examples that will calculate the range of valid addresses for any specified subnet value.   http://www.subnet-calculator.com/cidr.php https://www.calculator.net/ip-subnet-calculator.html   Visit either of the websites for a CIDR / Supernet calculator, enter an IP addresses in the network along with a subnet mask and the calculator will provide the range of addresses that can be used within the subnet.   In addition to online calculators, a number of different subnet-calculator programs are available for Android, Apple and Windows Smartphones.  

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue What is the difference between the three stretch behavior buttons in the TAC Vista graphic viewer.   Product Line TAC Vista Environment Vista Workstation Cause The explanation of what these buttons do has never been explained well. Resolution TAC Vista Workstation   There are five types of stretch&zoom buttons in TAC Vista Workstation (see figure below).   The three stretch behavior buttons are: Reset the strech behavior to what is defined in the TGML document. Set image to uniform size, which means that the image is stretch out to show it as large as possible and still show the whole image and with correct aspect ratio. Fill the entire client area/window, which means that the image is strechted out as large as possible to fill the whole area without maintaining the correct aspevct ratio.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus.     TAC Vista Graphics Editor TGML In the graphics editor there are two ways of looking at the TGML image; Design or Preview mode. The second view should simulate what is shown in the Workstation.   Design mode: When starting the editor, the TGML image is shown in its actual size -100% (i.e., no stretching or zooming is done).   By clicking on the Zoom button one can get to the rest of the sub-buttons for stretching/zooming. When this sub-toolbar is shown (and only then) the shortcut keys for the strecth/zoom button works (Ctrl-Asterisk, Ctrl-Plus and Ctrl-Minus). The restore stretch button (Ctrl-Asterisk) resets the strech behavior 100%.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus. By using the shortcuts Ctrl-Plus or Ctrl-Minus, selects the correct button (and the cursor changes to the spyglass when moved) and then one can click in the image to zoom.       Preview mode: When the preview mode is entered, the strech behavior will follow what is defined in teh TGML document.  By changing the behavior in the TGML document, the stretch mode changes in the preview window (unless zoomimg has been performed - se below).   In preview mode there are no strech/zoom buttons to use in Vista (the zoom buttons are present in Struxureware). However the shortcut keys plus (+) and minus (-) can be used for zooming if the TGML image has the focus.   In Struxureware's version of the graphics editor one can use Ctrl-Asterisk to reset the strech behavior to what is defined in the TGML document if the zooming has been used. However, in Vista's version the Ctrl-asterisk does not work in preview mode. But it seems that most shortcut keys for the toolbar buttons does not work in Vista.   Note: The stretch button has different meaning in the two views.          

Issue Error: 8000401a Retrieving the COM class factory for component with CLSID {2B768E20-89F2-11D2-99FD-00104B6D2299} failed due to the following error: 8000401a.Server process could not start because the configured identity is incorrect. Check username and password. (Exception from HRESULT: 0x8000401A).Code: -2147467238 When starting Vista Server, a fatal error happens: TACOS: COM Initializing failed, error code: -2147417831 Product Line TAC Vista Environment Remote desktop TAC Vista Windows 2008 Server or Windows 7 Cause When using Remote Desktop with a Windows 2008 Server and disconnecting, the TACOS process may end up in a "sandbox" and can not be reached by other people trying to log in remotely. Or, the Vista Server can't be started. Resolution The attached Tacos RDP Disconnect contains scripts that will disconnect a Remote Desktop session back to the physical session if tacos.exe is running. If tacos.exe is already running on the physical session or is not running at all, nothing happens.

Issue How can I add a SmartStruxure Automation Server to TAC Vista using BACnet/IP and what is needed Product Line TAC Vista,  EcoStruxure Building Operation Environment TAC Vista Xenta 913 Automation Server Cause Building Operation versions earlier than 3.2 are not FDA 21 Part 11 approved, In instances where the version is lower than 3.2 it can be achieved by using  TAC Vista as a front end, and having Automation Servers as field controllers. In Building Operation version 3.2 and later an optional Regulated Industries Compliance Pack is available that can be used without the need for  TAC Vista as a front end. Resolution 1. Create a BACnet interface in Automation Server. 2. Create BACnet points in the "Application" folder 3. Browse the Automation Server with a BACnet browser (Here is a free tool) 4. Note the instance id's of the points 5. In TAC Vista, create a Xenta 913 6. Edit the Xenta 913 7. Create a "BACnet IP Client" interface and give it the IP address of the Automation Server 8. Create a BACnet device template containing the points you need - refer to the id's previously discovered 9. Add the device template to the "BACnet IP Client" interface in XBuilder 10. Save and download the project 11. Now you get the live values from the Automation Server in TAC Vista

Issue Needs to know how often Vista (or Xenta Servers) do online/offline polls for Modbus and MBus devices Product Line TAC Vista Environment Xenta Server Modbus Mbus Cause The devices may go offline for several different reasons. It's not possible to give a precise answer to this question, since it depends on your setup and the number of devices. Resolution In general, if a Modbus device has been detected as offline by the Xenta Server, it will wait 60 seconds until it tries polling that device again. That doesn't mean that a device will come online after 60 seconds if it has been offline because as described below, other factors comes into play, such as the number of devices and registers, and invalid registers. Mbus: The Mbus protocol is designed so that all information in the device will be received at every poll, regardless of what is defined in the device template. If the Xenta Server doesn't receive any information it will retry twice and if still no reply it will set the device to offline. All offline devices will be transferred to an offline queue in the Xenta Server, and at every new poll one device (the oldest) will be moved to the poll queue again. The reason for not retrying all is that if you have lots of devices that are offline at the same time, each poll would take very long time to complete and if using a short poll interval it may not be finished in time before the next poll. That will also mean that if you have many offline devices and have set a long poll interval in Xbuilder (default 1 min) it may take quite a while until all devices are online again. Note: In Xbuilder 5.1.9 and later it's possible to set the number of offline devices to poll each cycle. In some cases, for example when there are few meters and/or long poll times you may want to increase this number. Modbus/TCP: You will have a Server address for the TCP Client and if that server's ip address can't be reached all the Modbus devices below it will go offline. However as soon it can be reached again (will be tried constantly), it will scan all devices below it, and if they reply they will be set to online. If there's no response from a single device, it will retry twice before it's set to offline. The time it will take depends on the slave timeout setting in Xbuilder (default 3 seconds). As for Mbus, you have an offline queue where 1 device will be moved to the poll queue every poll cycle. The total poll time also depends on how many devices and registers you have defined (many devices/registers = longer poll time = longer time to detect if a device is offline/online). Modbus/RTU: It works similar to Modbus IP, except for the server part (which is not present). Besides that, you also have the "transmit delay" setting in Xbuilder (default 0 ms, max 1000 ms) which may effect the time it takes for a device to be reported as online/offline

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 How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.