Building Automation Knowledge Base

Issue Why do Continuum controller MAC addresses have less than 12 digits as required by IT Departments? Product Line Andover Continuum Environment ACX, bCX, CX level controllers NC2 Cause Leading zeros are removed from the MAC addresses of all Continuum controllers Resolution The MAC address is listed as the attribute "Ethernet Id" in Continuum List views. The digits do not display leading 0's, so all Continuum controller addresses start 0:40:11.... To provide the 12 digit MAC address you will need to restore the leading 0's as required by IT departments. e.g.. 00:40:11:0e:00:00. See How to locate a computer's MAC address to obtain a computers MAC address.

Issue Trying to run a Script program from a Graphic but getting error Read Only Property. The control in the Graphic has been bound to a VALUE object, in the Script program an output variable (ManualChange in the code below) is bound to the same VALUE object. The program is supposed to toggle the value of 'theOutput' when triggered by setting 'ManualChange' from the Graphic, this works in versions prior to 1.4. Numeric Output theOutput, ManualChange LEAD_CHANGE:   ManualChange = Off Goto WaitForManualCHG WaitForManualCHG:   If ManualChange = On then   if theOutput = on then theOutput = off else theOutput = on   Goto LEAD_CHANGE endif Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS Enterprise Server - ES Cause Starting in version 1.4, SmartStruxure does not allow more than one write reference to the same VALUE, once a write reference is defined for a value or other references to the same value are READ ONLY. (See Reference Guide and References beginning with 1.4.x) Resolution Change the ManualChange variable in the Script to a PUBLIC and then from the Graphic bind directly to it. Numeric Output theOutput Numeric public ManualChange LEAD_CHANGE: ManualChange = Off Goto WaitForManualCHG WaitForManualCHG: If ManualChange = On then if theOutput = on then theOutput = off else theOutput = on Goto LEAD_CHANGE endif   See screen shot below of the binding in the Graphic

Issue Group bindings are correct, Xenta programmables download successfully, and all controllers are commissioned and online in LNS. However, no programmable units will show online in Vista Workstation. Check the alarm queue in Vista Workstation (sorted by Last Change) for the following alarm (or similar):  Server-$EE_Mess  Physical device not defined/configured - TAC301: 040294360200 The controller type and Neuron ID will change each time the alarm updates (every 30 seconds or so) as it cycles through each programmable controller in the network.   Product Line TAC Vista Environment TAC Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Group names must not exceed 20 characters in length and must not contain any spaces. Resolution Change all group names to adhere to the standard that they must be 20 characters or less in length and must not contain any spaces. It is also good design practice to change the subsystem names in LNS if that is where they originated from. This will help future service technicians to make sense of the network structure. For alternative solution, view System alarm message, Physical device not defined/configured.

Issue If remote buildings have an internet connection using DSL, will this configuration work with Continuum controllers? Are there any known issues? Is the connection fast enough? Product Line Andover Continuum Environment Netcontroller 9680 Netcontroller 99xx BCX ADSL (Asynchronous Digital Subscriber Line) Cause Buildings in remote areas may use DSL(Digital Subscriber Line) to access Netcontrollers instead of a corporate LAN. Resolution Netcontrollers can be used with a DSL connection. Two things to keep in mind when implementing this configuration are: Do not employ NAT(Network Address Translation) of any kind. Continuum requires a static IP. This can be requested from the ISP(Internet Service Provider) of the DSL line. All network ports required for Continuum operation will need to be opened. See Router required open port numbers to run a Continuum system for this information. DSL speeds are typically fast enough to not cause connection issues. Note: Where DSL lines have equal up and download speeds, ADSL (Asynchronous Digital Subscriber Line) have upload speeds that may be 100 x slower than the download speed, typically 128K maximum and are unlikely to provide a reliable network connection.

Issue No more address table slots for a device involved in the attempted connection. (Subsystem:  NS Connections, #15) Product Line TAC Vista Environment LonMaker 3.X NS Connections Error codes are not specific to any one LON environment, the display of the error may vary, but the steps to resolve should be the same.   Cause Every LON Neuron chip has 15 total address table slots inside, which store addressing information for SNVT communication.  Xenta programmable controllers utilize Address Table slots 0 and 1 for TAC and Xenta Group Binding information for reporting online status to the Vista Server and transferring TA Network Variables to each other.  This leaves 13 available address table slots in a Xenta programmable controller.  There are many scenarios by which address table slots are consumed (both in the sending and receiving controllers).  If you have exceeded the address table limitations, no further SNVT bindings (which would require additional address table slots) will be allowed.   Resolution The error message should indicate which controller has exceeded its address table limitations (sending or receiving).  First verify the current status of the address table. Right-click on the controller Select Properties Navigate to the Address Table tab.   This will tell you (a) if the address table is indeed full or (b) how many slots you have left.  Knowing this can help you determine the easiest recourse to the problem. If the address table is full in the sending controller: Information can only be sent via one-to-one bindings to 15 controllers (13 from a Xenta programmable).  Sometimes combining data into a one-to-many can save address table slots.  Instead of sending an individual occupancy to 20 VAVs, which consumes 20 address table slots, send them all the same one-to-many occupancy command, which consumes only 1 address table slot. Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. See Bind to more than 13 unique LON devices without running out of address table entries for details on creating Broadcast SNVT Bindings. If the address table is full in the receiving controller: If the binding is a one-to-one binding type: This is typically not an issue. The receiving controller does not normally have an address table slot consumed by a one-to-one SNVT binding. The only time a receiving controller has an address table slot consumed by a one-to-one SNVT binding is if that SNVT input is set to ""Poll."" (Unacknowledged, repeated, acknowledged profiles have no bearing on the number of address table slots consumed by one-to-one bindings.)   Unless dictated by the manufacturer of the device with which you are integrating, it is very rare to require polled inputs in a Menta file. Check the SNVT AI blocks in Menta and uncheck the "Poll" checkbox. Binding these inputs will no longer consume an address table slot in the receiving controller. If the binding is a one-to-many group binding type: Every member of the binding (sending or receiving) will have at least one address table slot consumed by the group binding. Freeing up address table slots may require some creative manipulation of the bindings. Options are: Convert to one-to-one bindings where the receiving controller will not lose an address table slot Do not customize every individual combination of group bindings (i.e. send the setpoint to the same controllers that are receiving outside air temp, even if they won't be using it). Every unique combination of controllers will constitute a new group and thus consume a new address table slot in each controller.

Issue Cycling power 10 times doesn't clear Xenta base units version 3.61 or later. Product Line TAC Vista Environment Xenta Programmable Controllers rev 3.61 or later Cause A change to the firmware got rid of the 10 power cycles clearing the application. Resolution To clear the memory of a Xenta 2xx/3xx/40x running system program 3.61 or later, i.e. clear out the Menta application, insert a reset plug into the RJ-45 serial connection and then give the controller power. If you don't already have one, it is quite simple to make. See How to Clear the Xenta Application for instructions on how to make a reset cable.

Issue What are the limitations of the Xenta 527 when used with TAC Vista and I/NET. What do I need to consider when integrating I/NET with TAC Vista. Product Line TAC INET, TAC Vista Environment TAC I/NET TAC Vista 5.1.6 and above TAC XBuilder TAC Xenta Server 527 5.1.6 and above I2V Cause Integrating I/NET into Vista. Resolution Below are a few considerations associated with the Xenta 527 Server that may assist when integrating existing I/NET systems with TAC Vista: As in all case the latest versions of both hardware and software should be used on any integration project. The attached datasheet indicates that the TAC Xenta 527 Web Server has been tested with up to 1000 I/NET points, if you require to integrate more points than this it is then recommended to add additional Xenta Servers to cater for this.  You may also consider segregating your I/NET System to improve performance. Currently it is not possible to pick and choose which points are imported into the XBuilder project, it can only be limited to which SAV file (or controller) is imported . Note: Each I/NET point type, as shown below, creates the following number of TAC Vista objects - these include; Alarm, State, Value, Control, Test, Manual, Alarm_ack etc, and vary according to the point type used. I/NET Point Type Number of TAC Vista Objects created DO 14 AO 11 AI 10 PI 10 DI 11 DA 11     The impact to consider here is the time it takes when adding or modifying your Xbuilder Project. This usually means that importing a large number of SAV files will cause the Vista server to get extremely busy creating / importing all of these objects.  It is best to let the process complete before selecting any other window.  Note that the total number of objects created during the import of the I/NET points is not counted as part of the 'tested' 1000 point limit stated in the above datasheet. This is a separate consideration. Network performance can be affected when a large number of connection objects are in use (so direct transfers between I/NET and Vista). There is no documented limitation, but the recommendation is not to exceed 300 connection objects per Xenta 527 Server.  For information on what the effects a connection object on the I/NET controller LAN has and how to calculate this, refer to Connection Objects in Xenta Server effect on I/NET system. Engineering of any I/NET feature apart from Point Control, Trends, Time Schedule and Alarm Configuration can only be done using the I/NET Host Tool or via an I/NET workstation.  Access to these features are via the Xenta 527 web server feature, so pages appear as HTML pages within TAC Vista, this will have a different look and feel to both Vista and I/NET users.   Other Knowledge Base Articles as listed below are also available to assist on integrating I/NET and Vista: Unit conversions when integrating LON to I/NET Vista to I/NET Integration Tips    Decoding the I/NET signal "flags" attribute Viewing I/NET Point Names in Vista Workstation instead of Addresses User Defined Units on I2V integration were accidentally set incorrectly SQL Host not passing data to Xenta 527 Web Server

Issue An I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled." What does this error message mean? Product Line TAC IA Series Environment An I/A Series R2 (Niagara) UNC. Cause When a station is in the disabled mode, it indicates that the station has rebooted multiple times in a five minute period. Possible causes are rapid fluctuations in the AC power supplying the UNC, a bad battery, or a station with less than 20% idle time. Resolution Disconnect the battery, then cycle power to the UNC and see if it boots up normally. Run the system spy: in a browser, enter  http:// (ipaddress of UNC):3011/system/spy. Login with the hardware user name and password. At the bottom of the page, click on "Reset Counter", then check to see if the idle time exceeds 20%. If not, the station will need to be tuned to increase the idle time. Check battery per Niagara R2/G3 UNC/JACE reboots every 15 minutes with "Battery test failed" logged. See Batteries for the UNC-410 and UNC-520 are interchangeable for battery part numbers.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, fails with the below error being shown. Hardware details do not match Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The hardware details on record do not match the hardware details of the machine that is trying to be licensed. Resolution Contact support to have the hardware profile reset.

Issue CyberStation and webClient on same computer. Second Security Key disables one or more features of the fist Security Key Product Line Andover Continuum Environment Andover Continuum CyberStation Andover Continuum webClient Cause Second Security Key inserted into USB port on workstation or only one computer to use. Resolution Only one Security Key (dongle, USB Key) per workstation(PC Computer). It is required that the key be installed to run the Continuum Cyberstation or WebClient server. Never install Cyberstation and webClient on the same workstation. Even on a LAN environment, there needs to be separate computers for Cyberstation and Webclient.  Note: webClient has some services disabled to allow for a more robust web capabilities. To see what is enabled on a Security Key, check out How to identify what is enabled on a Continuum Security Key.

Issue Tables needed for linearizing a 10K thermistors for an I/Net 7716, 7718, 7728 and 7756 (upper board). Product Line TAC INET Environment 7716 7718 7728 7756 Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on PCU's 7716, 7718, 7728 and the upper board of a 7756 Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature: -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.065942; b=-22.11377 Point Value in °C: M=0.03663447; b=-30.063207 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.1872172 153 4095 100 680 0.000468 0.074521 99.93 211.87 0.3183521 261 3548 90 917 0.000458 0.096177 89.90 193.83 0.4199872 344 3275 80 1258 0.000444 0.12407 79.88 175.78 0.5587138 458 3001 70 1753 0.000425 0.158633 69.84 157.71 0.745767 611 2727 60 2489 0.0004 0.199471 59.80 139.64 0.9964769 816 2453 55 3045 0.000383 0.223671 54.78 130.60 1.1671138 956 2316 50 3602 0.000368 0.243359 49.76 121.56 1.32407 1084 2179 45 4368 0.000348 0.264484 44.74 112.52 1.5200445 1245 2042 40 5326 0.000326 0.283435 39.72 103.49 1.7375701 1423 1905 35 6691 0.0003 0.300218 34.70 94.46 2.0043736 1642 1768 30 8056 0.000277 0.308878 29.69 85.44 2.2308374 1827 1631 28 8777 0.000266 0.311174 27.69 81.84 2.3371678 1914 1576 26 9572 0.000255 0.312351 25.69 78.24 2.4453301 2003 1522 25 10000 0.00025 0.3125 24.69 76.44 2.5 2048 1495 24 10450 0.000244 0.312349 23.69 74.64 2.5550122 2093 1467 22 11420 0.000233 0.311127 21.69 71.04 2.665733 2183 1413 20 12490 0.000222 0.308669 19.69 67.44 2.7767897 2274 1358 18 13680 0.000211 0.304953 17.70 63.85 2.8885135 2366 1304 16 15000 0.0002 0.3 15.70 60.26 3 2457 1249 14 16470 0.000189 0.29383 13.71 56.67 3.1110691 2548 1195 12 18090 0.000178 0.286579 11.71 53.08 3.2200071 2637 1140 10 19900 0.000167 0.278241 9.72 49.50 3.3277592 2725 1086 8 21920 0.000157 0.268921 7.73 45.92 3.433584 2812 1032 6 24180 0.000146 0.258715 5.74 42.33 3.5371562 2897 977 0 32660 0.000117 0.224329 -0.22 31.60 3.8279419 3135 815 -4 36200 0.000108 0.211999 -4.21 24.42 3.9177486 3209 706 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 3468 543 -14 69000 0.0000633 0.138199 -14.14 6.55 4.3670886 3577 435 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.5332773 3713 272 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 3876 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced For the look up table to the 7756 lower board, see 10k Thermistor Look Up Table for an I/Net 7756 (lower board).

Issue Vista Server can read values on a LON device, but when this same device is used in an Xbuilder project for a Xenta Server no values can be read. Product Line TAC Vista Environment FT-10 LON Network Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The XIF file of the LON Device does not conform to LonMark standards for self documentation. Vista Server can recover from this and assumes all SNVTs are from the default function block, but XBuilder cannot. On the third line of each variable declaration is the self documentation: 1: VAR nvo01Value 2 0 0 0 2: 0 1 63 1 0 1 0 1 0 1 0 0 0 3: "@1|2 The correct format is to show the functional block number and the member number separated by either a | or # character. Improperly formatted self documentation include the following: "nvo01Value - Does not define the function block or member number. "@_1|_1 - Uses _1 which is not a valid number. "&3.4@0,20000-MP580 - Uses a - (dash) which is not valid It can also be because SNVTs from devices are bound directly to Menta programs in a Xenta 7XX. If the procedure below doesn't solve the issue, refer to Graphic values not updating in a network that includes a Xenta 7XX. Resolution The XIF file must be edited to correct the self documentation. Right click on the controller in Vista Workstation and open the properties window. On the XIF file tab find the file name of the XIF file. Open this file from the $thisfil directory in the Vista database folder. Modify the XIF by manually correcting these invalid lines of self documentation. It is recommended to use the default function block (0) and start with member index 50 to ensure no overlap. Increment the member number for each SNVT. "@0|50 "@0|51 .... Once the XIF file has been updated save it under a new name in the $thisfil directory. In the device properties browse to the new XIF file. Log out of workstation. Log in to workstation. Insert the LON network into Xbuilder. Generate the project and send to the device.

Issue Receiving "Deny Entry Sched." (Schedule) transaction message for all individuals on a single Interface (SLI). Receiving "Deny Entry Sel." (Select) transaction message for all individuals on a single Interface (SLI). Product Line TAC INET Environment I/NET Seven Traditional Elevator Control Cause In traditional elevator control, the Reader (Door Point) must have a schedule assigned for the Group / Individual to allow access to the Lift (reader) itself. Then in Floor Maps you can allocate access to the individual Floor Points. In the floor mapping you must also remember to allocate the associated floor points otherwise the Individual is not Scheduled to have access to the floor (Hence a Deny Entry Sched message is received). Recommendation is to migrate sites to Extended Elevator Control which makes this process much simpler. For details of this refer to Extended Elevator control (Step by step instructions). Resolution Under Access Elevators check that the Floor mapping is correctly set for each Floor DO point. If no DO 's are selected for that particular Tenant Schedule, the individual will receive a Denied Entry Sched when attempting to gain access to the floor. Deny Entry Sel (Selection) is received when the Elevator Reader is not selected for the Tenant / Group or Tenant / Individual. A schedule (Group or Personnel) must exists on the reader (door ) point for the Group or Individual in question. A list of all Event messages, and their descriptions, received in AMT is available in AMT Event message definitions.

Issue Xenta 102-AX version 2.19 included 6 major updates and changes. They are outlined below. Product Line TAC Vista Environment Vista Xenta 102-AX Cause M/STAT Air Flow Calibration Errors Error Description: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is not generated in circumstances where one would be generated in the 102-AX Plug-in. This adversely affects the accuracy of the calibration, in particular at the low flow setting. Note: All steps for calibration using the M/STAT are found in Calibrating Airflow on a Xenta 102-AX (or MR-VAV-AX) using the M/STAT. Workaround: Perform the calibration using the LNS 102-AX plug-in tool or the TMGL plug-in tool Xenta 102-AX does not perform wink function properly Error Description: Attempts to perform the wink function fail. When a wink function is performed, the red light on the controller is expected to come on and flash to identify the controller and the STR-250 should display "00" with the man logo displayed as well. This should last approximately 45 seconds. STR-250 connected to the Xenta 102-AX is not controlling the fan properly Error Description: The STR-250, stat when connected to the Xenta 102-AX, reacts incorrectly to buttons being pressed when in the fan menu. The increase button causes a decrease and the decrease button causes an increase among other odd behaviors. Also, if the fan is set to shut off (this action should not be allowed) the Xenta 102-AX performs a resynchronization. Pressure dependent mode erroneously requires airflow and fan enabled Error Description: The 102AX requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Error Description:  When the Xenta 102AX does a hot water floating control valve resynch based on being in the 10-90% "happy" zone for 60 seconds and then goes to 100% it does not resynch at the 100% open position for the full stroke time. It gets to 100% commands the resynch, then closes the valve, re-opens the valve to 100% then allows the valve to control back to a normal position. Xenta 102-AX Floating Hot Water valve control failures Error Description:  Heating outputs stop working on Xenta 102-AX sporadically causing hot water valve to open even though application is calling for it to be closed. This occurs when the 102-AX is set up for a floating valve actuator (PWM 2) and occurs sometimes within a day but could take a few of days to show up. The resynchronization of the valve seems to have no effect and the only way to fix the controller is to cycle power or by switching nviEmergCmd to something other than its default and then back again a moment later. Resolution If any of these errors are occurring, upgrade the Xenta 102-AX to version 2.1.9 or higher. Click here to download the APB file. Complete upgrade instructions can be found at Upgrading a Xenta 102-AX to version 2.16 or later Version 2.19 addresses the problems listed above as follows: M/STAT Air Flow Calibration Errors Fix: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is now properly generated. Xenta 102-AX does not perform wink function properly Fix: After clicking Wink the a red LED on the controller flashes to identify the controller and the STR-250 displays "00" and the man icon. After approximately 45 seconds both the controller and the STR-250 return to normal. STR-250 connected to the Xenta 102-AX is not controlling the fan properly| Fix: The ability of the STR-250 to override the fan command on the 102-AX is disabled by default. If this functionality is required it can be turned on by setting DamperActuator.SCPTdirection.bit15 to 1. Pressure dependent mode erroneously requires airflow and fan enabled Fix: The 102AX no longer requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Fix:  Logic has been corrected to only resynch open or resynch closed as needed. Additionally, the heating output resynchronization algorithm has changed to operate as follows: Two internal timers have been added to track the accumulated amount of time that heat load is 0% and at 100%. Once either of these timers reaches 30 minutes, a resynch is initiated in the respective direction of the timer. The resynch consists of activating either the open or close triac output for an amount of time equal to the user defined stroke time. Xenta 102-AX Floating Hot Water valve control failures Fix:  Heating output logic corrected to prevent failure.

Issue Fluctuating temperature readings where they jump up to +327 randomly. Product Line Andover Continuum Environment Continuum controllers i2866-V Cause Readings like that are usually caused by wiring or power issues. There was also a Firmware fault that caused this in an old version of the i2866-V Firmware. Resolution Confirm the following wiring considerations:   That your input and output cables shield is wired to Earth ground at one end of the run only (preferably the controller chassis). That your controllers power supply is earthed on the secondary side of the 24vac transformer to ensure a proper controller ground to Earth. Confirm that the power supply is not being shared with any field devices, especially field devices feeding inputs back into the controller. One way to troubleshoot if it is a cabling or controller problem is to replace the sensor cable with a 10K ohm resistor. See Temperature inputs not reading the correct value for details. Also, in i2866-V controllers with firmware versions less than v3.501049, temperature inputs could randomly go to +327 when Analog Outputs were changing value frequently. Uprev your controller. See TPA-BOST-09-0007.00 for details.

Issue When starting the Vista Server, the splash screen displays the current state of the startup.  It gets to the "Trend Log Initialization" screen and then hangs. Product Line TAC Vista Environment Vista Server Cause Queued files in the $queues folder in the Vista database are being written to the SQL database.  If the queued files folder has grown very large, it can take a very long time (hours) to write this data to SQL.  If the connection to the SQL database has been broken, then it will take an infinite amount of time. Resolution Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. Allow time for the files to write the SQL Start Vista Server. Insure that TAC DSS Writer Service is running. When it gets to trend log initialization, leave the PC alone and allow time for the files to write to the SQL server.  If the size of the $queues folders are shrinking, then the process is working and after enough time, the server will start. Note: If you have cleared the $queues folder but it still hangs on trend log initialization, still allow plenty of time for the server to come up. There is a good chance that the Xenta controllers are passing all of their trend logs over to the SQL server. This could take hours or even overnight to complete. Delete the queued files If the data is not of dire importance, delete all the files inside both of the $queues folder.  For an efficient method for deleting many queued files, see An efficient method for deleting all queued files in the $queues folder. Check the SQL connection Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Remove TRL files This can also occur if the database has been upgraded from a lower versions, and still has information in the TRL files in the database. Stop the server Locate all TRL files in the $thisfil folder Delete any TRL file over 32Kb. Start the server again.

Issue Personnel does not have access. Invalid Attempt messages stating "Personnel record is not yet active" seen in the Access Events. Product Line Andover Continuum Environment Continuum Access Control Cause Personnel object Activation Date attribute is set to a future time. Resolution Open the Personnel object and confirm the Activation Date and Expiration Date fields are realistic. Make sure the Activation Date is in the past. Check that the time on the Controller and Cyberstations are synchronised properly. See Configure Time Zone and UTC Offset settings so that time is synchronized across your system for how.

Issue I/NET Physical Layer Issues, Lan Reconfigure, and/or Controllers going on or offline 1 at a time. Product Line TAC INET Environment I/NET Cause Physical Layer Issue Resolution Some or all of the following may indicate a physical layer issue. Abnormally large number of Lan Reconfigure messages Controllers going offline individually or in groups and sometimes all together Large numbers of Station Lost/Restore Messages Frequent problems connecting to controllers and data interruption To Troubleshoot a suspected Physical Layer error: Determine if this is a Controller LAN layer issue by direct connection to the Controller LAN using a tap.  If you continue to experience the same errors, as while connected via TCP/IP then the issue is on the Controller LAN Verify that you are using the correct wire gage (22 or 24) and that you controller LAN is less than 4000 feet for 24 AWG and less than 5000 feet for 22 AWG. Verify shield drain wire. Shield drain wire continuity must be maintained as the LAN cable passes through each controller. Shield drain wires from each controller LAN cable must be twisted together, insulated, and tied back such that wires do not come in contact with ground or any conductive surface within a controller. Shield drain wire must be directly connected to Electrical Service Earth Ground at only one end of the cable. The issue at this point can either be a wiring fault or a controller that is broken. Disconnect all controllers from the controller LAN by removing the LAN terminal strip from each controller Reconnect each controller one at a time and watch for the original errors. During this process a LAN Reconfigure is expected each time a device comes online While at each controller watch for any frayed wire, unusual/unneeded splices and if needed re-seat each wire into the terminal block When a controller is brought online and the error returns, examine that leg of the LAN wire for shorts or replace that section of wire Replace the suspect controller with a different device to ensure that the controller is not the source of the problem. (On critical systems you can plug in a spare controller at the location for testing without taking the existing controller offline) Typically if a controller is causing the error it will display alarms or LAN reconfigure on it's LEDs. Consult the TCON for the specific controller for more details (TCON Cross Reference available in TCON Number and Title Cross Reference (with links)). If it is not feasible to replace long sections of wire, or if it is determine that the controller LAN exceeds the specified length, then you may want to consider using Distributed Link Architecture.

Issue WebPinpoint crashes on "Failed to call piLiveData>GetLiveData(). AccdataServices has an error" on both WebServer and Client PCs. Product Line Andover Continuum Environment WebClient IIS WebPinpoint Pinpoint  Cause The asp_net account does not have permission to access the ILiveData interface. ILivedata is an internal engine that WPinpoint uses for polling points values.   Resolution In Workstation Preferences on the Web Server, increase the value of WPinPoint Continuous Polling Rate until  from crashes no longer occur.  If this is for a Windows Server 2008, Windows 7 or Windows Vista, make sure the web.config file has been edited. See also Error: "DNWacserverFactory/WACServerFactory.soap" when accessing Webclient 1.9x Pinpoint.

Issue Does I/NET support dual NICs (Network Interface Cards)? Is it possible to change which network interface card I/NET uses? Dual Network Interface Cards (NIC) will not allow selection between the Networks, option is grayed out. Product Line TAC INET, EcoStruxure Building Operation Environment I/NET 2.40 and above Cause Requirement for I/NET to have dual NIC support and option to change which network interface card I/NET uses. Resolution A New feature released with I/NET Seven 2.40 now allows I/NET to support dual network interface cards (NIC). The intent is to allow I/NET and Video the capability of using different Ethernet networks. This option also allows which network I/NET (and / or Video) uses. These settings are changed via the Advanced WAN Configuration (Advanced IP button) via the I/NET Configuration Editor (see image below). Requirements: I/NET Configuration needs to have TCPIP enabled and hardware (Ethernet card) needs to be installed on PC, I/NET (or I/O Server) must be running to select the Advanced IP button (Advanced WAN Configuration). If the PC is configured with multiple network cards, the above shown drop-down lists will be active: I/NET network Video network Use the drop-downs to select a network card for each network. You can use the same card for both networks, or you can use a unique card for each network. By using two networks, you can separate I/NET traffic from video traffic and conserve bandwidth on each network. NOTE: If you have dual Network Interface Cards and you are not able to select between these networks (so they are grayed out) you must have the following minimum requirements configured for this option to be available in the I/NET Editor: A Physical connection to its connection media. (i.e. A connected network status. If you have a status indicating Limited or no connectivity you will not be able to select between Interface cards). Valid IP address and subnet mask Valid Gateway IP address. (If you have no gateway router on the network then select a valid IP address within the same IP range, usually the IP of the PC is the best option here.) If you are using wireless NIC and have issue to choose it, refer to Host number conflict on a computer with dual Network Interface Cards (NIC).