Building Automation Knowledge Base

Issue How to redirect from default website to webstation. Want users to get to webstation even if they only type in the server name Environment TAC Vista 5.1.5 Windows 2008 IIS7 Cause It is easier for customers to just type in the server name and not have to remember the /webstation Resolution  Open IIS manager Click on Default Website Double click on HTTP redirect     4.Type in the URL to Webstation (default http://localhost/webstation) 5. Click on apply under actions.

Issue Vista Workstation Errors: 'No such entity' , sometimes accompanied with  'Could not parse blueprint' and 'Failed to parse application' error messages in alarm pane. Error occurred: Failed to retrieve property from database. The property page will be disabled. No such entity Environment Vista Workstation Menta OP tree Cause There is a mismatch between the .mta in the Xenta and the .mta in the Vista database. Vista asks for a value that does not exist in the device and errors. Unused constants in the Menta file Error in the OP tree Transfer of the .mta to the controller upon download was invalid or failed. Memory is low or has been totally consumed in the Xenta programmable controller. PVR blocks that have invalid values, eg. 2,0E-16 or similar. This can happen sometimes if you save in simulation mode in Menta Resolution Most common: If all of the signals are showing "No Such Entity", this is a sign that the controller does not contain a Menta file. Though you may think it should, it does not. The following are reasons why the controller did not download or is applicationless. Applicationless controllers require a "direct connect" and download to the controller. Errors in OP NOTE: if you've customized the OP menu, changes will be lost In Menta editor, Tools>OP Configuration, Tree>test. Test to see if there are errors in the OP tree. Tree>Build and select "Yes" to replace the current tree. Tree >Generate. Tree>Test. This will verify your errors have been fixed. Save the OP file. In simulation mode select Command>Generate, File>Save to Vista database or save the Menta file to your hard drive with the intention of manually browsing in the .mta to the device. Incorrect .mta in the Vista Database Browse in a newly saved .mta, Download the controller. Application Too Large Downloading through Vista may appear to be successful though an error exists. Using a serial connection is the most reliable way to reveal memory errors. Use one or more of the following to free up memory in a Xenta which is "Out of Memory". Checked the free memory in Menta via Options>Memory Usage and make sure that the Application is not too big Reduce application size by limiting the amount of "public" values and "descriptions" by un-checking public in the Menta block properties and deleting the description. Delete unnecessary not connected outputs (TANVO's) Delete the OP Menu if it is not needed. Alternatively, build the OP Tree instead of Auto Generating one for a smaller file. Time schedules/charts consume significant amount of memory. Check all TSCH blocks and delete any unnecessary Week/Alt charts. Replace the Xenta controller with a larger capacity controller (from a X280 to X300 or from X300 to X400) Re-write your program to use all Menta blocks more efficiently. Split the task among controllers but keep in mind limitations with TAC network variables and network traffic. Invalid Values In Menta, go to simulation mode Go to Preferences uncheck view diagram Now you get all the signals in a list that you can easily scroll through and find any value that are to small or large Change the value to the real value Hit F5 and F12 and save in edit more.   If only some of the signals are showing "No Such Entity" there is a mismatch of what signal values are trying to be retrieved from the controller, and the signals that are actually present in the controller. This is known as Unused Constants. Unused Constants In Menta, go to Options>Constants Tables and choose "Delete Unused" to remove all orphan variables Download to the controller.

Issue TAC Vista Webstation licenses are not released after the Webstation browser is closed. When log into Webstation again, get error message: The following errors have occurred. Please correct these errors and/or contact the system administrator. X No license available Product Line TAC Vista Environment TAC Vista Webstation Cause Closing the Webstation browser does not log out the user. Logged in user needs to use the “Log Out” button (as shown in the picture below) or wait till the Webstation times out in order to log out. The default time out period is twenty minutes. Setting can be changed in Webstation settings. Resolution If need to change the time out period setting, please follow the steps below: Go to “Start/All Programs/Schneider Electric/Web Applications X.X.X/Vista Web Settings” (by default). NOTE: for TAC Vista 5.1.3 and prior, go to “Start/All Programs/TAC/Web Applications X.X.X/ Vista Web Settings” instead.   Select “Preferences/Login and Logout/Automatic Logout”. In the right panel, click on the down arrow to expand the drop down list and choose the desired the logout time period.  

Issue When Vista Server starts another window opens up with the title of TAC Central IPCL Interpreter. This window will not close while Vista Server is running. Environment Vista Server 4.xx, 5.x.x Cause TAC Central IPCL Interpreter is a tool used for programming and communication management for legacy System 7 controllers that predate Vista 3.3. In the absence of System 7 hardware the TAC Central IPCL Interpreter was started and configured to run automatically by mistake with the Vista Server interface. Resolution Disable the Automatic Start of the CIPCL Interpreter. Start Vista Server Select File->Log In. Log in to the Vista Server. Select Configure->CIPCL ->Auto Start. Restart Vista Server to confirm the program does not launch again.

Issue Which values in the 102-AX plug-in affect the ultimate airflow reading output on nvoBoxFlow? Formula for converting velocity pressure to flow. Setting air balance parameters -- airflow coefficient, velocity pressure gain, offset, and cutoff, duct area, pickup factor and box constant. Environment Xenta 102-AX Cause Incorrectly configured boxes can cause erroneous airflow readings or unexpected behavior during calibration. Resolution The Xenta 102-AX uses a differential pressure sensor to convert velocity pressure values from 0-1" water column to a 0.25-4.0 volt output. The voltage signal is converted to a 10-bit digital value. The digital value is filtered and passed through the calibration gain and offset adjustments. Any value below the lowest velocity pressure threshold will be treated as 0"wc. Airflow_Sense.UCPTairFlowCoeff Airflow Parameters > Airflow Setting > Airflow Filter Coefficients (%) This value ranges between 0 to 99% where 0 is no filter and 99% is the maximum amount of filter. All process controls using the airflow reading use the filtered value. The default filter is 80%. The filter equation is defined as follows: display value = [previous display value * filter] + [new data value * (1 - filter)]   Airflow_Sense.SCPTgain Airflow Parameters > Airflow Setting > Velocity Pressure Gain (multiplier/divisor) This value is multiplied with the raw velocity pressure reading to provide calibration gain to the final signal. The default gain is 10/10 (1). Resetting the box to factory calibration settings prior to calibrating the box will ensure that no invalid values are adversely affecting the operation.   Airflow_Sense.UCPToffsetPress Airflow Parameters > Airflow Setting > Velocity Pressure Offset (WC) This value is added to the raw velocity pressure reading to provide calibration offset to the final signal. The default offset is 0. Resetting the box to factory calibration settings prior to calibrating the box will ensure that no invalid values are adversely affecting the operation.   Airflow_Sense.UCPTpressCutOff Airflow Parameters > Airflow Setting > Lowest Velocity Pressure (WC) At the low end of the measurable velocity pressure, the sensor is inherently unreliable. The lowest velocity pressure threshold will zero out any value too low to reliably be measured. The default value is 0.016"wc. If airflow is reading 0 CFM despite the velocity pressure being above 0"wc, it may be that the threshold is set too high. The calibrated velocity pressure value is used in the following calculation for airflow: Airflow = Square Root(Velocity Pressure) * Duct Area * Pickup Factor -or- Airflow = Square Root(Velocity Pressure) * Box Constant The operator has the ability to enter the duct area and the pickup factor as separate values, or enter the box constant of the VAV terminal unit. The box constant is the duct area multiplied by the pickup factor. If the duct area or pickup factor is entered last, they will be used in the calculation. If the box constant is entered last, it will be used in the calculation. The pickup factor and box constant are sometimes referenced as the K-Factor(FPM) and K-Factor(CFM) respectively. This information must be taken from the VAV box itself and is usually displayed in a format such as the one shown below. Airflow_Sense.SCPTductArea Unit Parameters > Box Settings > Duct Area (sq feet) The cross sectional area of the duct in square feet. Most ductwork diameters are measured in inches. For round ducts, the equation for area is: Area = π * [(d/2)/12] 2 where d = diameter or Area = π * (r 2 / 144) where r = radius An 8" diameter duct would have a cross sectional area of 0.349 sq feet.   Airflow_Sense.UCPTpickupFactor Unit Parameters > Box Settings > Pickup Factor (Imperial Units) This coefficient is provided by the VAV manufacturer and represents the feet per minute flow speed of the air at 1"wc of pressure. Typical values in HVAC VAV applications are between 2200 and 3300. Default value is 2950.   Airflow_Sense.UCPTboxConstant Unit Parameters > Box Settings > Box Constants (Imperial Units) The box constant is the area multiplied by the airflow pickup factor. Airflow is determined by multiplying the square root of the velocity pressure by the box constant. The final value is reported out the following SNVT: VAV_Controller.nvoBoxFlow Status > VAV Status > Airflow (CFM) This is the final airflow value in CFM as measured by the Xenta 102-AX. After calibrating the velocity pressure probe, the displayed value should match the flow values measured by a highly accurate magnahelic hood.

Issue Open Tgml Graphics Not enough storage is available to process this command. Environment Vista Workstation TGML graphic Cause This is a Windows error having to do with how many applications are running simultaneously/how much memory is available. Resolution A reboot of the PC should free up allocated memory that is no longer needed.

Issue Cannot see any licenses when I log in to schneider-electric.flexnetoperations.com using an Activation Id Environment Vista 5.1.5 Vista licensing website (schneider-electric.flexnetoperations.com) Cause Once the license has been activated the Activation Id is no longer valid. Invalid Activation IDs are not shown in the user interface. Resolution After the initial activation of the license, use the Entitlement Id to login to schneider-electric.flexnetoperations.com instead of the Activation Id. The Entitlement Id will remain valid each time you log on to the licensing website.  

Issue Trend log creation is successful, but no values are recorded in the Vista SQL database. Error message “Failed to write values to log database” is visible in Vista Workstation alarm window and review of the b0warlog.txt in the $log folder of the Vista database reports errors: TLogHandler :: ObjectInitEnd: Failed to setup event log queue directory (hr=-2147024773) TLogXenta :: ServiceExecuted: Log (Path to Trend Log) not successfully read. Error: -2147024893 Environment Vista 4.3.0 - 4.5.0, 5.x.x Cause Corruption in the Vista database directory $queues folder causes disruption in recording of trend log values. A file with the name of insertlogvalues exists in the $queues directory when Vista Server is expecting a directory to exist with that name. Attempts to write queue files to the \$queues\insertlogvalues\ directory fails with a ERROR_PATH_NOT_FOUND error ( -2147024893). When Vista Server starts it tries to create the directory, but due to the presence of the file with the same name the process fails with a ERROR_INVALID_NAME error (-2147024773). Resolution Shut down Vista Workstation and Vista Server. Start Vista Server Setup from Start Menu\All Programs\Schneider Electric\TAC Vista Server 5.1.x\Server  Setup. For Vista version lower then Vista 5.1.4: Start Menu\All Programs\TAC\TAC Vista Server x.x.x\Server Setup. Click the Vista Database tab to view the Vista database directory: Open a Windows Explorer and browse to the Vista database directory. Open the $queues directory. Delete the contents of directory. Start Vista Server. Trend Log operation should now be restored.

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.

Issue Double clicking a .tgmlcomponentarchive file should automatically add the Component Archive to the Editor's component libraries. Sometimes it does not work and instead shows the following windows: TAC Vista Server Please wait while Windows configures TAC Vista Server Gathering required information... TAC Vista Server The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'TAC Vista Server.msi' in the box below. TAC Vista Server Error 1706.No valid source could be found for product TAC Vista Server. The Windows Installer cannot continue. Product Line TAC Vista Environment TGML Graphics Editor Cause There are five libraries that are included by default with every installation of the editor. They are: TAC Vista Symbols (EN) ISO Symbols DIN Symbols (EN) My Components Basic Controls If any of these libraries are removed by navigating to C:\Documents and Settings\All Users\Application Data\TAC Graphics Editor\Components and deleting the folder, attempts to add new libraries will fail. Resolution Navigate to the Buildings Business Extranet Go to Products > TAC Vista > Vista Software Click on the correct version of TAC Vista in the left-hand column. Choose Downloads Download the TAC Graphic Editor 1.1.X. Double click to install The directories are restored. Do not delete them.

Issue Configuration instructions for setting up a communications VX Log in the Xenta 5/7/9xx for communications troubleshooting. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 VXI Cause Configuration instructions for setting up a communications log in the Xenta 5/7/9xx for communications troubleshooting. Obtaining the communications log for a Modbus or BACnet network is crucial in finding communications errors, or other unforeseen problems with integrating to third party devices. Resolution Step by step instructions for creating the communication log for troubleshooting or for data analysis: Log In to the Xenta 5/7/9xx controller and navigate to the Utilities Folder:   Click on the Target System Folder and choose VXI Web Shell Commands:   The command line should appear with VX populated in the command line:   Logging to file in the Xenta controller will first need to be enabled to by typing VX L 1 and press submit:   VXI Web Shell Commands should return a messing indicating logging has been enabled for 1 hour:   After logging has been enabled, the verbosity will need to be set in order to capture each layer of communications on the wire. In the command line type VX V 9 and press submit:   VXI Web Shell Commands should return a messing indicating the verbosity has been set to 9 and what messages you will see with this verbosity level :   Let the communications log run for 5-10 minutes. Create as many changes on the 3rd party wire as possible to get various data changes to and from the Xenta Server.   In the command line type VX O and press submit:   This command will output the communications log the Xenta Server has collected. Highlight this entire output log and copy, then paste it into notepad for archiving or emailing:   To set the communication logging back to default type "vx V 1" or power cycle the Xenta Controller. To stop the logging to file, type "vx L".   For TCP/IP logging you can only monitor one client at a time: Complete Steps 1- 8 above Enter "vx d" This will display a list of the TCP available devices Enter vx d # where # is the number corresponding to the deice you wish to monitor To view the log, follow steps 9 and 10 above

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue Xenta group bindings are used for group communication between Xenta group masters and members.  They also transmit TAC Network Variables between two programmable controllers.  Redoing group bindings is a common troubleshooting technique to address issues with these functions.  However, it can often be time consuming, especially if using LonMaker which requires the Visio drawing to be resynchronized.  Verifying that the Xenta group bindings in the device's address table are correct prior to redoing them can save time on an unnecessary troubleshooting step. Product Line TAC Vista Environment Vista programmable controllers LonMaker, NL220 Cause Checking to see if the group bindings need to be redone instead of always using it as a standard troubleshooting technique can save time. Resolution To access the Device Address Table of an application device in LonMaker: Right-click on the controller in LonMaker and go to Properties. Go to the Address table tab. Look at the first two entries (0 and 1) and note the value in the ID column. Go to another controller in the same group and compare the values in the ID column. Every controller on a network should share the same ID in row 0. Every controller in a group should share the same ID in row 1. If the group bindings are correct, there is no need to redo group bindings.   To access the Device Address Table of an application device in NL220: Select the application device in the tree Press Ctrl+A keys or right click on it and select the option Network\Network tables ... in its context menu Select the tab Addresses    The grid contains one line for each entry in the address table. Index = The index of the address entry MT = Yes if the entry is reserved for message tags connection Type = Type of the entry, Unbound (Not used or "free"), Turnaround, Subnet/Node, Broadcast, Group Size = Size of the group (zero for a large group) and Used only if Type is Group Domain = Domain index (0/1) Mb/Node = Member if Type is Group (not used for a huge group), Node id if Type is Subnet/Node or Unused Repeat timer = Value of the repeat timer  Retries = Retries count Rcv timer = Value of the receive timer  Tx timer = Value of the transmit timer  Gp/Subnet  = Group id if Type is Group, Subnet id if Type is Subnet/Node or Unused   Refresh will refresh the table.

Issue In order to make the correct determination when selecting an actuator, it is important to first understand the difference between sourcing and sinking triacs.  A triac will act as a switch. By triggering its gate electrode, it will either conduct alternating current or impede it. While it can be thought of as contacts on a relay, it is important to note that it is decidedly different. Environment Xenta 121-FC, 121-HP Xenta 101-VF, 102-VF, 102-ES, 100-D (legacy) Cause A digital output on a Xenta 121 (labeled V1 through V4) utilizes a ground sourcing triode for alternating current (TRIAC). In general, a TRIAC will either be voltage sourcing or ground sourcing (also referred to as voltage sinking). The Xenta 121 using ground sourcing TRIACs will be a determining factor when selecting actuators to be driven by digital outputs. Resolution A TRIAC output is similar to a hardware switch in that it will either open or close a circuit, allowing or stopping the flow of current.  Whether the internal side of the triac is connected to power or ground will determine whether it is a sourcing or sinking TRIAC. If the internal side of the TRIAC is connected to power, as shown in Figure 1, it will be considered a voltage sourcing TRIAC.  When the output is activated, current will flow from the output, through the actuator, to ground.  Most actuators are designed to accept voltage sourcing outputs from controllers. Figure 1. Voltage Sourcing Triac Configuration If the internal side of the TRIAC is connected to ground, as shown in Figure 2, it will be considered a ground sourcing (or voltage sinking) TRIAC.  When the output is activated, current will flow from a power source, through the actuator, and into the output.  Some actuators are designed to accept both voltage sourcing and voltage sinking outputs from controllers.  Figure 2. Voltage Sinking Triac Configuration The digital outputs on terminals V1 through V4 of a Xenta 121 utilize ground sourcing triacs.  The G terminal between each pair of triac outputs sources 24 Vac.  It has direct continuity with the G power terminal.  When the output is active, the triac will conduct current to ground completing the circuit. Said another way, if the output is inactive, there will be a 24V potential between V1 and G0 (ground), but a 0V potential between V1 and G.  When the output is active, there will be a 0V potential between V1 and G0, but a 24V potential between V1 and G.  An actuator is wired between V1 and G, so the potential across these two terminals will dictate whether the actuator is on or off. In one example, a 3-wire floating actuator is wired with OPEN, COM, CLOSE connected to V1, G, V2 respectively.  There shouldn’t be a problem if the actuator is using the 24Vac signal to drive an AC motor.  When the open command is active, the actuator will see a 24V potential across its contacts and drive the motor. In another example, a 4-wire floating actuator is wired in the same manner, but now also requires its own 24Vac power signal to run some on-board logic.  This example will not work because that actuator is expecting to see COM wired to ground, but it is in fact wired to the same 24Vac, resulting in 0V potential between power and ground of the actuator. One solution is to use caution when selecting actuators to be driven by the Xenta 121.  Avoid actuators designed to be controlled with voltage sourcing outputs.  Another option is to use the triac outputs to close contacts on external relays that will source the necessary 24V as needed. Another application of the digital outputs is to control the coil of a relay in order to open or close the circuit of another device, such as a low voltage terminal strip, fan motor contactor, etc. While some low voltage applications may function without the use of the relay between the 121 outputs and the device being controlled, this is generally not recommended and may negatively impact the reliability of the triac outputs. Because the triacs are ground sourcing and G provides 24V power to the circuit, they can be wired directly to the 2 legs of the relay coil, as shown in Figure 3 below. Using this configuration, the triac is isolated from any harmful current that may travel through the external relay contacts. Figure 3. Wiring Configuration for Relay Control with Triac

Issue When right click on the user account, the Delete choice is grayed out and all Properties textboxes are grayed out. Or, the error message “Access is denied” is displayed when trying to delete or edit the account. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause The account was locked for database protection. The access rights were removed. Resolution Log in Workstation as the administrator Right click on the user account, and select “Authority” Uncheck “Require signature on database object change” and “Protected database object”. NOTE: need to uncheck twice to release those two requests. If the $Administrators is missing or does not have “Full Control (All)” right under "Access Control list", do the following: Under Groups/Users, expend the list,  until find $AdministratorsSelect $Administrator, then click Add. $Administrators should appear under the "Access control list" now with "Read (R)" permission. Select $Administrators under "Access control list". Expend the "Access level" drop down list, and choose Full Control (All). Click Apply, and then click OK. Refresh the window (F5) Now the user account can be deleted or edited.

Issue TGML Graphic Alert: TypeError: Cannot call method "getAttribute" of null (cmd#52) TGML Graphic Alert: TypeError: Cannot call method "setAttribute" of null (cmd#52) Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML file has attempted to perform an action on a null pointer.  Oftentimes this is due to a component being deleted or renamed without realizing that a script elsewhere in the graphic was pointing to it. Resolution Determine which script tag is generating the error. When did the error occur?  When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 52 of the code. The text in quotes tells which method was being used.  In this example "getAttribute."  Investigate what is in the parameters of the getAttribute() function.  Verify that object exists as defined. Edit the script to point to a valid object, rename or restore any deleted object.

Issue TGML Graphic Alert:  Unable to cast object of type 'org.mozilla.javascript.UniqueTag' to type 'org.mozilla.javascript.Function'. Product Line TAC Vista Environment Vista Workstation 5 TGML Graphic Cause A script tag somewhere in the TGML graphic file has a function defined in the Behavior attributes that does not have a corresponding function in the script Content or is misspelled in the script. Resolution This error tells you that a script tag in the file has a function defined but not used.  It does not tell you which script tag it is.  The first step is to identify which script tag has the extra function defined.   Click on the script tag.  Look at the Behavior attributes.  Compare the function names defined next to the events with the content of the script.  Click the "..." button next to the Content attribute to open the script editor.       In this example, the event OnDocumentLoad has a function named "load" defined.  But in the content of the script there is no function load defined.   Identify the unused event and delete the function name assigned to that event. If this is not the issue, verify that the function names defined next to the events with the function names declared in the script editor for spelling errors. 

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

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

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