Issue When using the STR-350/351 as an I/O module in Menta (Options > Device Specification > IO Expansion and Wall Module Table) some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Both STRIN and STROUT Menta simple blocks should be used for the most robust synchronization. Environment STR-350/351 as an I/O Module Menta Cause The STR-350 takes roughly 30 seconds to recover from a power failure. The Xenta is much faster than that resulting in reading an invalid setpoint from the STR-350 on a power cycle. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored (provided the power has not been off longer than 3 days, in which case it would default back to the initial value of the backed up value). Resolution Click the pictures of the Menta macro below to download the source file. Occupancy To control occupancy from the programmable controller time schedule, the occupancy must be sent to the STR-350. In order to allow for local override commands from the stat, the occupancy must be read in from the STR-350. By allowing the programmable controller to control both the schedule and the override, the stat stays in synch with the program. Setpoint The setpoint requires a little bit of extra programming to account for a power failure. The stat will report invalid setpoints for the first 30 seconds, which will cause it to come back in an undesired state. By letting the programmable hold onto the last known setpoint, and write it back to the stat on power up, there is no change in the setpoint after a power loss. Looping the setpoint in/out from the stat keeps everything in synch with the program, including stat adjustments. Note: This code protects against unwanted behavior following a power failure. A download the Xenta base unit will not trigger the Reset block protection and will cause the stat to go outside the bounds of, and then be limited by, either the high or low setpoint limit. Precaution should be taken following a download to manually reset the setpoint to the desired value. Additional logic for controlling the setpoint remotely could be incorporated into this code. If these macros are going to be used with a STR-350/351 set in degrees Celsius; make sure to change all initial values within the setpoint range. If the initial values are outside of the setpoint range, then the setpoint will always default back to the last known value.

Issue Configuring and monitoring the Xenta 102-AX is traditionally done through the LNS Xenta 102-AX Plug-In, but how can it be done in a Vista Classic Network where no LNS plug-ins are available? Environment Vista 5 Classic Network TGML Xenta 102-AX Vista Workstation ONLY -- This plug-in is not compatible with Webstation or XBuilder graphics at this time. Cause LNS Plug-ins are not available in a Vista Classic Network. Resolution All of the values that are written to by the LNS Plug-In are public and available through the Vista front end. So if only one or two signals need to be set for each box, this can be accomplished by locating them in the Vista network and writing the desired values to them.  This does require some fairly intimate knowledge of the Xenta 102-AX and Plug-In. The alternative is: Download the Xenta 102-AX TGML Plug-in by clicking the image below.  Unzip the contents to the hard drive. Open the TGML file. Select File > Save As > Vista Database Object Navigate to the first Xenta 102-AX in the network. Drill down into the 102-AX on the same level with Node_Object and VAV_Controller modules. Give the plug-in graphic a name and save. Right click on the Graphic object in Vista Workstation and select Copy Navigate to the next Xenta 102-AX and select Paste Shortcut. Since all bindings are automatically populated with relative bindings, copying and pasting shortcuts will automatically display data for the associated Xenta 102-AX. Repeat Step 8 for all Xenta 102-AXs in the network.

Issue Exporting/Importing data from taclogdata SQL database tables possibly due to suspected database corruption. Symptoms: 1. Vista is very slow or crashes when retrieving trend charts. 2. Vistas seems to be working slower than usual. Environment SQL Server all editions. SQL management studio. Cause The SQL database is corrupt or the database or tables have been created manually in SQL management studio express and don't have the correct format. Resolution Link to  "Export Import between SQL Tables.pdf"

Issue In some instances, Product Support Services may require you to execute this batch file to record Vista Server errors. This is not a required file and should only be executed under the direction of PSS. Environment TACDumpHelper Vista Server Cause Vista Server fails to run correctly  Resolution To run TACDumpHelper, the batch file is to be run manually. Unzip TacDumpHelper to a directory of your choice. TACDumpHelper_v1.0.zip or TACDumpHelper_v1.1.zip (64bit) Start Tacos.exe (Vista Server) Run start.bat Choose to monitor a crash - Press 2 Choose which process to monitor - Tacos.exe - Press 1 Wait for the application to crash. The dump files will be saved in the same folder where start.bat is located. 

Issue How do you determine how large a database will grow when using Vista? Which version of Microsoft SQL Server is needed? Product Line TAC Vista Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of trend logs and events should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called SQL Server Express. The size limitations are 4 and 10 gigabytes for Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption, data loss, or inaccessible data. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Vista database, to determine which version of SQL should be used. The Vista database estimating spreadsheet takes into consideration 2 main areas: Trend Logs- total amount of logs, intervals and the number of days to retain Events- total amount of access events. The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate which version of SQL Server is needed This spreadsheet can be downloaded by clicking on the following link: Click Here Update: In Vista 5.1.7, there is a Trend Log Calculation Tool included (under Schneider Electric-Tools)

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue TGML graphic do not work Graphics are displayed OK but no values are displayed (crossed out in red) Webstation ports usage No values in webstation Environment Vista Webstation Internet Explorer Cause When the graphic are working but no values are shown it most likely because webstation do not have access to create subscription with TACOS. The function Rendering cache are meant to handle this Subscription Rendering cache are a function that can be changed under "TAC Vista web setting" and it need to be associated with a user that have read write access to the system. Another reason for this issue, can be that the Windows user "ISUR" that is the one used when accessing Webstation ("Anonymous" in Windows terms) for some reason doesn't have the appropriate user rights on the PC Resolution [Option 1 - rendering cache user] For a normal installation you can reach the function by Start - program - Schneider Electric - Tac Vista webapplication (Depending on what version are installed) Click the tab "Performance" Add a  user that have read/write access in Tacos In TAC Vista Web Settings 5.1.8 this Rendering Cache and Security setting is under Graphics>TGML Viewer   [Option 2 - "Anonymous" access user (IUSR)] Open the IIS manager through Control Panel - Administrative tools Edit the properties for "Webstation" In directory security, define a local user on the PC with high user rights NOTE: Also make sure port 80 is open in firewalls/routers, since this port is used to transfer HTTP data. For HTTPS port 443 is used. See attached "Webstation port usage"

Issue Is a Vista license necessary for I/NET Host tool features or is the I/NET CD key sufficient? What is the difference in the I/NET Integrated and I/NET Security licenses? Environment Vista Server I/NET Host Tool Cause The I/NET Host tool requires a Vista license file to run. Certain editors and features in the I/NET Host Tool are common to both the Integrated and Security license. Some features are specific to the Integrated or Security license. To have all of the features purchase of both licenses is necessary. AMT is not included with the I/NET host tool product as Vista is expected to handle alarms messages and transactions Common Features System features Change password Connect/Disconnect Logon/Logoff Quit Work offline Host features Host configuration editor Host password editor Host phone numbers editor Host software restore editor Netcon function editor Network configuration editor System view Tap features Host, link, and site tap configuration Site tap remote configuration Site tap save/restore Controller features 7720 configuration editor Action messages summary Alarm extension editor Calculation editor Control description editor Conversion coefficient editor DCU configuration editor DCU save editor DCU restore editor DCU password editor DPU configuration editor Engineering units editor Event extension editor Event sequences summary I1/I2 state parameters editor Lighting circuits editor Lighting zones editor LCD page definition editor Lookup table editor MCU configuration editor MR configuration editor Resident point editor Special days editor State descriptions editor Time schedule extension editor Trend extension editor Trend plot view dialog Summaries Configuration summary Controller summary Disabled points summary Off-normal points summary Reporting features SevenReports (operates in view-only mode if no I/NET CD key is installed) I/NET Integrated only Controller features Consumption extension editor DDC modules summary Demand control extension editor MR DDC summary Override billing equipment mapping editor Override billing extension editor Override billing parameter editor Runtime extension editor Temperature control extension editor Unitary control configuration editor Unitary control extension editor I/NET Security only Controller access features Elevator extension editor DCU AIC editor Door extension editor Personnel schedules SCU parameters editor Host access features Access control options editor Access control wizard AIC editor Door extension editor Groups editor Individuals editor Key translation editor Personnel schedules Pin generation dialog Recycle bin SCU editor Tenant editor User search Summaries Door tenant summary Resolution Purchase of an I/NET Host Tool license is necessary for the integration with Vista Workstation to function. Use the feature list to determine if only one license or both licenses are required by the customer. Attached is the PA for all the required software Here

Issue Manual override of the damper actuator position or the desired flow setpoint on a Xenta 102-AX can be accomplished with a network variable (SNVT) input. Environment Xenta 102-AX Cause There are times when the damper position or flow setpoint needs to be overridden from a supervisory controller.  It may be a special mode for Test & Balance, a smoke control sequence, or a special circumstance where the internal logic of the 102-AX must be ignored in some situation. Resolution Manually controlling the Xenta 102-AX damper position, and flow value can be accomplished using the VAV_Controller.nviManOverride SNVT. This is a three-part structured SNVT. Values for the state portion of the SNVT are: HVO_OFF disables override HVO_POSITION sets the damper position output to a desired percentage HVO_FLOW_VALUE sets the flow setpoint to a desired flow HVO_FLOW_PERCENT sets the flow setpoint to a desired percent of maximum flow HVO_OPEN fully opens the damper HVO_CLOSE fully closes the damper HVO_MINIMUM sets the flow setpoint to specified cooling minimum HVO_MAXIMUM sets the flow setpoint to specified cooling maximum Values for percent and flow are used according to the selected state. Click here to download a Menta macro for further clarification. It is important to note that in versions greater than 2.1.2 no other auxiliary control will function when using nviManOverride. Example: if nviManOverride is set to control the damper to a fixed position, the external hot water heat or electric heat will not function.

Issue Displayed temperature on the ETR is offset from the actual temperature reading of the controller. Environment ETR Thermostat Cause Factory calibration is offset from actual temperature. Resolution Click here to download the Installation and Operating Instructions Temperature Display Adjustments Temperature display may be adjusted by adjusting the ZERO or OFFSET Potentiometer (P2) as shown on the diagram.  Adjust P2 until the LCD Display reading, matches your controllers temperature reading if necessary. Note that all LCD Displays, are factory calibrated using an NIST Certified Glass Thermometer.

Issue National characters do not look right on the TAC Xenta Operator Panel (OP). Instead of Swedish (Danish, German, Spanish) characters, I get other characters in my OP. Product Line TAC Vista Environment TAC Menta TAC Vista TAC Xenta OP Cause You need to specify what character-set to use. You do this in the OP Configuration Tool. Resolution Open OP Configuration Tool from the Menta application Go to Format, - Character set file Pick the file for your language. Save and generate

Issue When logged in to TAC Vista Workstation it is not possible to see any users. Product Line TAC Vista Environment Vista Workstation Cause Only a user who has Authority level "System manager" has permission to see users.   Resolution If logged in with the system user, make sure that this user has the Authority level "System Manager". If not, try to log in with another System Manager level user. If you do not have one, contact your local Support who will then need a copy of your Vista Database in order to give you a list of all System Manager Users. There must always be ONE System Manager in a Vista system.

Issue What does the "| n" mean when viewing the properties of an OPC variable in Vista workstation? Problems have been encountered with OPC variables Error messages such as "The object is no longer available in the servers address space", Also, canonical data type or OPC data types. Environment Vista 5.1.X TAC Vista OPC client Cause The "|n" is a reference to the data type or canonical data type as it's called in the OPC standard. In the world of OPC, the client application can be created in on one of many diverse programming languages. To resolve potential issues all OPC data types are assigned a specific Canonical Data Type. When a client application adds an OPC Item to an OPC Group it can use the default data type for the item or it can request the item with a specific canonical data type. If the OPC tool is used then the canonical is added automatically by checking with the server. It's only if variables are added manually that this information is required. Resolution The method used for addressing OPC variables is Folder.Variable_Name|Data_Type  The table below details the data types:  Data Type Canonical Type Size Data Range Boolean 11 1 Bit True or False Byte 17 1 Byte 0-255 Byte Array∗ 8209 1 Byte times Array Size 0-255 Short 2 2 bytes -32768 – 32767 Short Array∗ 8194 2 bytes times Array Size -32768 – 32767 BCD 18+ 2 bytes 0 - 9999 BCD Array∗ 8210 2 bytes times Array Size 0 - 9999 Word 18 2 bytes 0 – 65535 Word Array∗ 8210 2 bytes times Array Size 0 – 65535 Long 3 4 bytes -2,147,483,648 to 2,147,483,647 Long Array∗ 8195 4 bytes times Array Size -2,147,483,648 to 2,147,483,647 LBCD 19+ 4 bytes 0 - 99999999 LBCD Array∗ 8211 4 bytes times Array Size 0 - 99999999 Dword 19 4 bytes 0 – 4,294,967,295 Dword Array∗ 8211 4 bytes times Array Size 0 – 4,294,967,295 Float 4 4 bytes -(3.40 E38 – 1.40 E-45) to (1.40 E-45 – 3.40 E38) Float Array∗ 8196 4 bytes times Array Size -(3.40 E38 – 1.40 E-45) to (1.40 E-45 – 3.40 E38) Double 5 8 bytes -(1.798 E308 – 4.941 E-324) to 4.941 E-324 – 1.798 E308) Double Array∗ 8197 8 bytes times Array Size -(1.798 E308 – 4.941 E-324) to 4.941 E-324 – 1.798 E308) Char 16 1 Byte All Characters supported in the standard ASCII table String 8 1 – n Bytes All Characters supported in the standard ASCII table

Issue Visio 2010 crashes whether or not LonMaker is running and both LonMaker and Visio 2010 crash together often when LonMaker is running. Echelon LonMaker An unexpected error occurred. Please save your drawing and exit Visio/LonMaker. Environment LonMaker Turbo Edition Visio 2010, possibly Visio 2007 Cause The "Send to Bluetooth" Add-In in Visio 2010 has been known to cause Visio to crash thus bringing LonMaker down with it. This often occurs when Bluetooth is disabled on the computer. When Visio is not able to access the bluetooth, the program crashes. Another possible cause is that the Add-In is not compatible with DEP. Resolution Steps to remove the Bluetooth add-in The simplest resolution to this problem is to disable the Send to Bluetooth add-in in Visio by following these steps: In Visio 2010 click File and select Options near the bottom of the left-hand pane. Select Add-Ins from left-hand pane then find and highlight the Send to Bluetooth add-in. In the Manage drop down box select COM Add-ins and click Go. Uncheck Send to Bluetooth and click OK. Shut down Visio and start LonMaker.     Steps to disable DEP in Visio In Visio 2010 click File and select Options near the bottom of the left-hand pane. Select "Trust Center" and click "Trust Center Settings" Click "DEP Settings" and remove the tick mark in "Enable Data Execution Prevention Mode" Shut down Visio and start LonMaker.

Issue It may be desirable to the building management to remove web users and operators' privileges to change their own password. Environment Xenta Server Cause By default all users are able to change their own passwords. Resolution While the privilege that each user has to be able to change their password cannot be removed through standard configuration methods, it can, nevertheless, be removed through the FTP server of the Xenta controller. However, these changes will apply to all web users or to all operators rather than just specific users. Connect to the FTP of the Xenta 5/7/9xx controller by typing FTP://x.x.x.x (where x.x.x.x is the IP address of the controller) in the Windows Explorer address bar. Login with the root username and root password. Browse to the ftp://x.x.x.x/www/config/ folder and copy the either the file named operatormenu.xml or webusermenu.xml (depending on which type of user needs to be edited) and copy it to the desktop of the local machine. Open the ftp.cfg file with notepad on the local machine. If you are editing the web user file then delete the following lines: <MENU name="User Administration" value="/wm/useradmin" type="CFGDIR"> <MENU name="Change Password" value="/wm/useradmin/change_password" type="CFGPAGE"/> </MENU> If you are editing the operator file then only delete the following lines: <MENU name="Change Password" value="/wm/useradmin/change_password" type="CFGPAGE"/> </MENU> Save the file to the desktop without changing the name. In the FTP rename the original file by adding a "1" to the end of the name. For example webusermenu.xml would now be named webusermenu1.xml. This way you can keep the original file in the FTP if you ever need to revert back to it. Copy the newly edited file from the desktop to the FTP folder. If you are already logged into the Xenta server then log out and log back in. The menu should no longer be available. Important Note: If the system program is reloaded in the Xenta Server, these changes will be over-written and will need to be re-done.

Issue Trendlog Server is busy. Please try viewing the page again later Diagram The error looks like a java popup with error "Server is busy. Please try viewing the page again later" Environment Xenta webserver Cause It may take up to 15 minutes before a trendlogs actually starts (Depending on how many trendlogs that are available in the Xenta) after a restart of a Xenta webserver. During this time a Java error might appear if you try to call something including values from a trendlog i.e. Diagram Resolution The server is trying to startup all the trendlogs so please wait up to 15 minutes and try to view the page again.

Issue Confusion over behavior of the Xenta 121 when using a occupancy sensor. Environment Xenta 121-FC Xenta 121-HP Cause When an occupancy sensor is not defined in the configuration of a Xenta 121 controller the effective occupancy will follow the command given by nviOccManCmd. However, when an occupancy sensor is defined, either as a network bound point or a hardwired sensor, the effective occupancy of a Xenta 121 will behave differently. Resolution The Xenta 121 operates as follows when using an occupancy sensor: The most notable difference in how the Xenta operates are: When nviOccManCmd is in either the OC_UNOCCUPIED or the OC_STANDBY modes then the Xenta 121 will ignore the state of the occupancy sensor. When nviOccManCmd is in the OC_OCCUPIED mode the Xenta 121 will follow the state of the occupancy sensor. Note that this means that the controller could actually enter the unoccupied mode even though nviOccManCmd is set to be occupied. When nviOccManCmd is in the Oc_Nul mode the effective occupancy of the Xenta 121 will Oc_Standby until a signal is received from the occupancy sensor at which time it will change to be Oc_Occupied. This behavior should be taken into consideration when deciding on how to implement an occupancy sensor. It may be desirable to set the nviOccManCmd to Oc_Nul whenever the occupancy sensor should be considered and to set it to Oc_Unoccupied when the occupancy sensor should be ignored. This effectively utilizes the occupied, unoccupied and standby modes as three distinct modes of operation to maximize comfort and efficiency.

Issue After migrating a TAC Vista export containing TAC Xenta IO modules to SBO, some or all TAC Xenta IO modules are missing the neuron ID's Environment Migration TAC Xenta IO module Cause During the migration, the TAC Xenta IO modules are matched on their name. If the name in TAC Vista differs from the actual name in the associated Menta file, the match can't be made and the properties on the IO modules can not be set. Example of this scenario In TAC Vista   In TAC Menta Resolution 1. Edit the Menta application through TAC Vista Workstation 2. Rename the IO modules in Menta 3. Save to Vista 4. Device gets dirty and need download - download to get rid of the dirty mark 5. Export database in through TAC Vista Workstation 6. Convert to SBO using the Conversion Tool

Issue When generating a XBuilder project, the following error is shown in the "Output" window "Error: Could not open x7parser.exe." Environment TAC XBuilder TAC Menta Cause For some reason TAC Menta has not been properly registered during installation. The file x7parser.exe is part of the TAC Menta installation, if TAC XBuilder can not located the TAC Menta executable, x7parser.exe (which generated the Menta objects in the XBuilder project) can not be launched. Resolution The solution is to manually register TAC Menta 1. Open a command prompt (Start - Run - cmd) 2. Navigate to the TAC Menta installation directory (Typically "C:\Program Files (x86)\Schneider Electric\TAC Menta 5.1.9" but this depends on OS and Menta version) 3. Enter the following command: tam32.exe /regserver 4. Press enter 5. Reopen XBuilder and generate

Issue For maintenance of the site we would like the possibillity to turn a "User Group - Alarm" on or off Environment TAC Vista 5.1.9 Cause "User Group - Alarm" is used when you want specific users to be able to see specific alarms.  For example an alarm control bound to a specific "User Group - Alarm" will only send its alarm to users added to User Group Alarm. When doing maintenance on a site there is often many alarms which the users are not interested in, and this is why the users need to be able to disable a certain alarm user group. Resolution It is possible to connect the alarm user group to a timechart. The alarm user group will only be active as long as the time chart is on. 1. Define a "Time Chart - Local" in TAC Vista 2. Select and open the appropriate "User Group - Alarm" object 3. On "Time chart" select a timechart object created in step 1 and click OK   Now none of the users in the alarm group will receive alarms, as the time schedule linked to the alarm user group is inactive. To return to normal alarm handling, remove the time schedule reference created in step 3, and delete the time chart created in step 1.