Building Automation Knowledge Base

Issue Control HVAC or especially lighting based on the sunrise and sunset times for a given location on a given date, even though this functionality does not exist in Vista like it does in I/NET. Environment Menta Cause Menta/Vista time schedules have no built-in sunrise/sunset capability.  If this is required, it will need to be programmed into a Menta file. Resolution The attached Menta Macro calculates the sunrise and sunset for a given location. Click the picture to download.       Inputs - Menta Simple Blocks Month Date Hour Minute Configurable Parameters Year = Current year.  As Menta has no "Year" block, it must be calculated in the controller and should be set initially for the current year. DST = Does this location participate in Daylight Savings Time?  1=Yes, 0=No. TimeZone = Location's offset in hours from GMT Latitude = Location's latitude in degrees. North is a positive value, south is a negative value. Longitude = Location's longitude in degrees. West is a positive value, east is a negative value. Outputs - Available Data Current minutes past midnight Sunset minutes past midnight Sunset hour Sunset minutes Sunrise minutes past midnight Sunrise hour Sunrise minutes Output integer represents minutes until next transition.  Mimics a Menta time schedule.  Positive values count down minutes until sunrise.  Negative values count down minutes until sunset.

Issue MicroNet controller objects have a maximum allowable value of 10.000 Environment   MicroNet Meters VisiSat Xbuilder Vista 5 Cause MicroNet controller objects have a maximum allowable value of 10.000 some meter readings require a greater value. Resolution 1. In VisiSat add two counter objects. Link the Rollover pulse output of the first counter to the Count input of the second Counter object. Fig 1. Counter Object 1 is used for the 0 - 999 part of the meter count. Counter Object 2 is used for the 1000 - 1,000,000 part of the meter count. 2. In the Xenta 731 add a Menta object and program shown below in fig 2 is one example. Fig 2. This Menta code multiplies counter object instance 2 by one thousand and adds the sum with counter object instance 1 giving an output for total meter reading of up to 9,999,999. 3. This then can be added to value, graphic ETC pages.    4.  If you would like to download an example click on your preferred option below. Click here for the VisiSat project. Click here for the Xbuilder project.  Click here for the Vista database. Click here for All three.

Issue The date and time must be included in the text message. Environment Sigma Micronet Vista BAS2800+ RAM Remote Alarm Manager Cause The basic text messages do not include the alarm date and time, this is a site requirement.. Resolution To change the message format, configure as follows: 1 - Using the RAM Console, select "Configuration" and the required "Action". 2 - Edit the Action, and select "Messages". 3 - Choose the "Advanced" option, and then "Edit Script". 4 - Choose "File" and then "Open File", browse to the location of the script file you want to open. An example script file can be uploaded from here. 5 - The screen capture below shows part of the script editor with the script file opened. This script will provide an alarm message which takes the following form. Message No (This cannot be de-configured), Alarm Priority, Alarm Date / Time, Mnemonic, and Value (i.e. Plant On / Plant Off etc.). The alarm cleared message is slightly different. Message No (This cannot be de-configured), Alarm Date / Time, Mnemonic, and Value (i.e. Plant On / Plant Off etc.).

Issue Create a true PWM output from a Xenta programmable controller using a DOPU block in Menta. Environment Menta Cause Menta does not have a built in PWM functionality, so to control a PWM actuator, some additional programming is required to utilize a DOPO block as desired. Resolution Click the image above to download the Menta Macro. Load the macro into the Menta file. The HFB takes a percent signal input and outputs the required values to control a DOPU block, which in turn will pulse the physical DO on the Xenta controller to control a PWM actuator.

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 Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

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 Addressing issues with M-Bus metering application because it is unclear what Storage# or Tariff# to use in Xbuilder. Environment Xenta 913 5.x.x Xbuilder 5.x.x Cause Manufacturers of meters which utilize the M-Bus protocol may not specify the Storage# or Tariff# needed by Xbuilder. They may instead include DIF or DIFE information regarding their meter points. These codes correspond to the M-Bus protocol and indicate the Storage# and Tariff# of the data. Resolution Use the M-Bus DIF calculator to parse the data type, Storage#, and Tariff# of the data point. This spreadsheet should be sufficient for the majority of applications, but some exceptions apply. The hexadecimal codes for the data point must be provided by the manufacturer for the calculator to be useful.

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 How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize  - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

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 Instructions and programming example for using SNVT_Switch as an input or output in Menta Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The attached programming example is intended to clarify how to properly use SNVT_Switch in Menta. SNVT_Switch is a structured SNVT with two attributes, or members, State and Value. Programmatically this will be one SNVT in the device template, but it will be programmed as two separate analog points in Menta. These two public blocks will have different names in Menta, but they will share the same SNVT name with the exception of one of the points being the state member, and the other being the value member. It is important to remember that these points must always be programmed as analog points in Menta. AI's for input points, and AO's for output points. The state attribute is intended to be used for a binary on-off signal, but also contain the value -1 for Invalid value. The value attribute is intended to be used as a 0-100% signal. This SNVT is typically used in the market for starting and stopping a VFD drive and sending a speed reference with the same SNVT. The 0,1 value on the state member will start and stop the drive, and the value member will send a 0-100% speed signal. Resolution Please see the attached Menta macro as a guide to using SNVT_Switch in Menta. This example shows you SNVT_Switch as an input and as an output to the Xenta controller. To use this macro please follow these steps: Download the attached macro from above. Unzip the file and extract the SNVT_Switch.MTA from the archive to the local hard drive. Open Menta Right-click in Menta and click Load Macro Browse to the SNVT_Switch.MTA on the local hard drive and open it. It should import into the Menta file that is open.

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 Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue TAC Graphic Clipart library is a collection of clipart to use as a starting point for an image based graphic page. There are pieces for building air handler ductwork, controlled equipment, dampers and actuators, and water side equipment. Product Line TAC INET, TAC Vista Environment I/NET gpg graphic Vista ogc graphic Cause Without libraries to build a background image for HVAC equipment, it can be difficult to create user-friendly graphic pages to display dynamic data.  In a graphic editor that relies on bitmaps or jpgs to build the airflow diagrams, floor plans, water side diagrams, etc, this library can be used as a starting point. Resolution Download the attached .zip file. Unzip the contents to a location on the hard drive of the computer that will be used to edit the graphic pages. Browse the contents of the .zip file.  It will be separated into logical folders.

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