Building Automation Knowledge Base

Issue Utilize the RS-232 port to send text out to a third party device such as CCTV Product Line TAC INET Environment I/NET Seven Cause Integration Assistance Resolution This V-Doc describes the way text output can be set up in I/NET to be sent out to third party hardware such as CCTV through the RS-232 port. The port that will be used for this application cannot be one that is already being used by the serial port section, A/C reader port, or printer port in the peripheral section of the configuration profile.   For the guide of integration with Pelco analog matrix, refer to How to integrate I/NET with Pelco Analog Matrix.

Issue When importing a file from TAC Menta into StruxureWare Building Operation Functional Block Editor, the import of the application file fails. Environment TAC Vista TAC Xenta StruxureWare Building Operation Cause The following characters are not allowed in object names in StruxureWare Building Operation. • / • " • ? • * • ~ • White space is not allowed in the beginning or the end of an objects name. • . (period) is not allowed in the beginning of an objects name. Colon (:) is not allowed either, but will automatically be replace by an underscore (_) when importing   In TAC Vista, signal names could contain the character "/". In SmartStruxure, this character is not allowed. Resolution Remove illegal characters from object names in the Function Block program.

Issue After importing a new template into AET, the different folders and objects are all different colors. What does each color represent? Product Line EcoStruxure Building Operation Environment AET Folder View Cause Each color indicates a different status for the object. Some must be resolved before proceeding and others are information only. Resolution Below is the list of the different status colors and their meanings:  Red – Duplicated object. This must be corrected. Green – Existing folder. Orange – Folder with duplicated object below. Black – New object or folder. Blue – Existing object in EcoStruxure system tree Brown – Device that will be created automatically by AET Light Blue – Empty IO Channel

Issue Need information and help deciding on the correct product and part numbers. Product Line Andover Continuum Environment All current Continuum products Cause Customers do not always know how to find sales and product information on the various websites. (i.e. Catalogue, datasheets) Resolution For EMEA & Asia Pacific markets the Continuum Catalogue defines all current products and associated part numbers, see Andover Continuum Product Catalogue For the Americas information is available from the iPortal website for product selection and part numbers: http://iportal2.schneider-electric.com   Continuum datasheets are available from the Schneider Exchange Extranet link: https://ecobuilding.schneider-electric.com/search#keyword/Andover%20Continuum%20Specification%20Sheets/tab/documents

Issue How to find the MAC address / Physical Address of a computer. Product Line Andover Continuum, EcoStruxure Building Operation, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment All computers Cause The MAC address of a computer may be required when working on licensing issues. MAC stands for Media Access Control and is a unique identifier assigned to network interfaces for communications on the physical network segment. Resolution Go to the Start > Run.   Type "cmd" into the Open field. In the CMD window, type the command "ipconfig /all". Locate the connection that the computer is currently using (For this example it is the Ethernet adapter Local Area Connection). You will find the Physical Address (MAC address).

Issue   Xenta 700 Menta viewer in Internet Explorer displays some blocks at half-size Environment Xenta Server Xenta 701, 711, 721, 731 Menta Internet Explorer Cause Illegal characters in the description field of the point has caused problems with the web interface live Menta viewer. Resolution Verify that there are no strange characters in the description field of the point. In the most recent case, the = sign caused the block to shrink.

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Issue If the result of a divide by zero is sent to a physical AO, Vista Workstation will display this value as -2. The physical output, however, will be sending out the maximum specified voltage (default 10V). In Menta simulation mode, if a divide by zero scenario is simulated, the following error will pop up: tam32 Division by zero Connected to a controller viewing live Menta, a divide by zero equation will result in a displayed value of 1.#QNAN. All subsequent equations using this value will also output 1.#QNAN. Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Division by zero results in an invalid value that is interpreted differently by the controller's physical outputs, the Menta application, and the Vista Workstation. The application will continue to run, but any output affected by the invalid value will not act as expected. Division by zero is not usually intentional (there's no equation that says "A/0"). Instead, it is usually the result of an unforeseen sequence of events where complex equations result in a 0 in the denominator of an equation, and simulations did not ever produce this unique situation. Resolution To troubleshoot whether a divide by zero is occurring: The best solution is to connect live to the controller with a serial cable and watch the live Menta. Look for any values that read 1.#QNAN and trace it back to the source. If live Menta is no available, the simulation mode can be helpful. Recreate the scenario as best as possible with all inputs set to the real life instance. To prevent a divide by zero error: Never allow an equation to write to the denominator of a division equation without programming divide by zero prevention. Add an expression block prior to the division equation that says "if the value is zero, then output a safe value" Add a max block to the input that compares the value with 0.0001, so that a zero will never pass through.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

Issue IDWorks 6.x (on a Remote Client) does not connect to the SQL with Windows 7 64 Bit. Product Line TAC INET Environment Datacard IDWorks 6.x Windows 7 64-bit I/NET 2.43 and above Cause You have to manually install a 32 Bit ODBC connection for this to work correctly. Resolution To resolve this issue, start the EXE file located at: C:\Windows\SYSWOW64\odbcad32.Exe. NOTE: This is NOT the ODBC that is in the Control Panel on the PC. Once you start the EXE file, set this new ODBC Connection up by following the steps that are listed in Setting up ID Works on a Remote Client PC.

Issue If steps used in creating a LNS network are performed in an incorrect order, you can get many errors which can be easily avoided. While this should not replace the Engineering LNS Networks manual  it can be used as a quick reference. Follow this link to access the complete Manual Environment LonMaker 3.X Vista System Plug-in Cause There are several steps to perform in order to create and update an LNS Network using LonMaker. Resolution LonMaker Cheat Sheet Create new LNS Network in LonMaker Set path to Vista DB in Server Setup Start TAC Server Open TAC System Plug-In Drag and drop Devices from Stencils Assign .MTA to Xenta Devices You will be prompted to Resynchronize, say no. Assign I/O Modules Set Neuron IDs Update Vista DB Create Group Bindings Resynchronize drawing (fix up) Download Application and Parameters Commission Base Units and Modules Commence Communication

Issue Which communication paths are secured with encryption when Continuum network security (IPSec) is enabled? Product Line Andover Continuum Environment CyberStation NetController II - CX9680 ACX II - ACX5740, ACX5720 Cause Information required on Continuum network security. Resolution Continuum IPSec implementation secures communications between Continuum controllers and CyberStations.     The following paths are secured: CyberStation to CyberStation CyberStation to controllers Controllers to controllers. Controllers can be configured to allow communications with other controllers that do not support network security such as the CX9900. Consult the Network Security Configuration Guide for further information.   Securing the communication path between workstations running CyberStation and the DB server is outside the scope of the Continuum implementation and is left up to the site’s IT department to put in place.

Issue What protocol of the Ziton ZP3 Fire Detection System does our Xdriver utilize? Environment Continuum Xdriver - Ziton Fire Panel Cause Need to confirm that the XDriver is able to communicate to third party fire panel. Resolution The Ziton XDriver has been developed to the ZCP2 communications protocol V2.01. Contact the manufacturer to confirm whether the panel supplied supports this version of the protocol.   Further information on the XDriver can be found at the link below. Clymac - Ziton Fire Panel

Issue When working with numbers that are 7 digits or longer the number is displayed in exponential format and there is a loss resolution in the lower digits that can cause an issue with metering applications. This can be an issue when using pulse counter inputs. Product Line Andover Continuum Environment All Continuum controllers and modules that support Pulse counting with Counter inputs Cause The number formatting throughout the Continuum product is 32 bit IEEE Floating point notation, for numbers up to 7 digits long they will be displayed as a regular decimal number, for larger numbers they will be displayed in exponential format: Significant digits × base exponent This allows Continuum to work with huge numbers like 123.45 x 10 67 but has the disadvantage that as the numbers get larger there will be a loss of resolution in the lower digits starting with the units. Resolution When working with pulsed inputs from meters try to keep the size of the numbers down, putting scaling factors of x10 and x100 only makes the numbers bigger, so where possible scale the numbers down and upscale the units. For example when scaling an input where you would enter a conversion of: Value+(ElecValue * 10) Instead use: Value+(ElecValue*0.1) and change the units to Kilo Units, Mega Units etc. If you have to measure large pulsed numbers another option is to split the large numbers across 2 Numerics, so in Plain English when a value gets to 999,999 then add 1 more pulse, you get 1 in the upper number and 0 the lower number. This can then be displayed on a graphic with 2 adjacent text boxes. Where very accurate metering is required the best solution is to use meters with an intelligent data interface that supports one of the common open protocols supported by Continuum (i.e. BACnet MS/TP, Modbus or M-Bus via X Drivers). This solution means there is no chance of missing a pulse or Continuum getting out of sync' with the meter. Note: If you need to set the lower number back to zero, then the object first needs to be disabled. If this is a BACnet bCX then the BACnet name (eg BACnetDevices\bCX25\Counter2) needs to be used within the PE Program

Issue The pressure drop across the valve is required. Environment Valve Pressure Drop Cause Customer needs to know what the pressure drop across a 32mm valve will be. Resolution Example: two 32mm V211T valves with flows of 0.549 l/s and 0.483 l/s through them. To calculate the pressure drop use this formula - Pressure drop = (Flow rate in M3/Hr / KVs) squared. Flow rate of 0.549 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.549 * 3.6 = 1.9764 Pressure Drop = 1.9764 / 16 = 0.123525 squared = 0.015258 Bar * 100 = 1.526 kPa Flow rate of 0.483 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.483 * 3.6 = 1.7388 Pressure Drop = 1.7388 / 16 = 0.108675 squared = 0.0118102 Bar * 100 = 1.181 kPa To review the Satchwell Valve sizing data sheet, please click HERE.

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment EcoStruxure Security Expert Cause In the Door object, there is a facility for triggering Outputs on Pre Alarm, Door Left Open, and Door Forced Open but nothing for when a User is denied access. Resolution There were new Door commands added to SP-C firmware 2.08.1018 and newer to add this functionality. AccessDeniedTime = # has been added to the Door commands which will specify the duration in seconds that an output or output group will be activated for when access to the door has been denied. This must also be paired with one of the following 2 commands in order for the functionality to occur. AccessDeniedOutput = # has been added to the Door commands which will specify the output that will be activated when access to the door has been denied. The # will be the database ID of the output/output group. AccessDeniedOutputGroup = # has been added to the Door commands which will specify the output group that will be activated when access to the door has been denied. The # will be the database ID of the output group. As an example, if you wanted the Output with an Id = 3 to turn on for 5 seconds when access is denied at the Door, the following lines would need to be added to the Door object in the Commands section. AccessDeniedTime = 5 AccessDeniedOutput = 3 Door Command - Access Denied Output  

Issue Menta file Simulates (F12) and Generates OK and even downloads from Vista apparently OK, but monitored values shown the message 'Failed to read signal'. Connecting to the controller with the serial lead and entering online simulation mode gives a 'PARSER ERROR'. The Memory Usage stats show less free space than would be expected for a file of this complexity. Environment Vista Menta Xenta Cause The Menta file has some corruption that is not visible when viewing the Functional Block Diagram. Resolution Some files may be rescued by copying the FBD into a new empty Menta file: Create a new empty Menta file with the same Device and Program Specifications as the corrupted file. Open the corrupted file in a second instance of Menta. Drag a selection box around the entire visible FBD and enter Ctrl+C to copy. Switch to the new Menta file and enter Ctrl+V to paste the FBD. Please note that this procedure will copy references to named constants across to the new file, but it will not copy the constant definitions. Selecting F12 will highlight the function blocks containing the references to the missing constant definitions.  Edit the block and press 'OK'.  A dialog box will pop up for each constant where you can fill in the value, unit and public parameters.  Repeat this procedure by selecting F12 until Menta enters simulation mode without errors.  You will also need to create the OP tree and any trend logs from scratch. If you are lucky, the new file will download and run without errors.

Issue Tolerances for resistors when used for RS485 bus termination and EOL for double balanced inputs. Product Line Security Expert Environment Wiring Cause Resistor specification required for ordering purposes. Resolution 330 ohm EOL resistors are required for the RS-485 bus and 1K ohm resistors for EOL zone (input) configuration. 330 ohm = 5% tolerance, Metal film 1000 ohm = 1% tolerance, Metal Film

Issue I/NET will run in application mode, but will quickly shut down when in service mode Product Line TAC INET Environment I/NET Configuration Profile I/NET Seven Cause The I/O Server can be configured to auto shutdown whenever the I/NET Workstation application is closed. If this setting is used, the service will stop whenever I/NET Workstation is closed as well. Resolution Open the I/NET Configuration application. [Start>All Programs>I/NET>INET Config] Click on the Radial button so that I/O Server is maintained when no clients are present. Do NOT use the shutdown option when using I/NET as a service  

Issue Can the Personnel Manager be launched without using Continuum Explorer? Environment Continuum CyberStation Cause Require quick launch. Resolution Opening Personnel Manager without opening an existing personnel record. Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Start Windows Program Windows Program: C:\Program Files\Continuum\Launch.exe Command Line Arguments: -C –SPersonnel –Offline “-FRoot” If you want to include a Owner folder location use the following arguments Command Line Arguments: -C –SPersonnel –Offline “-FRoot” “-Proot\FolderName” Result: This will launch Personnel Manager from the button on the graphic with no cardholder information configured.   Create a graphic and set it up to launch for the user upon login Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Open object Object: Select a default cardholder to bring up in Personnel Manager Result: This will launch Personnel Manager from the button on the graphic to the cardholder selected.   Create a graphic button from the main menu that launches Personnel Manager to a specific cardholder If you have made any modification to the Main Continuum menu. Make a copy of the file before editing. i.e. the default is c:\program files\continuum\userprofile\continuum.mnu Right click the main page. Create a new hot spot or edit the Personnel hot spot according to instructions in the Configuration manual on Menu Pages. C:\Program Files\Continuum\Launch.exe -O -SPersonnel "-N\Cardholders\Test_Card" (Note:Cardholders is a folder) Result: Personnel Manager will open to that card   Launch the command line and use the Show command This is similar to option 2 except the button config is different In the Personnel button change the parameters to C:\Program Files\Continuum>cmdline Result: This will launch the Command line Type in Show Test_Card (some cardholder the user knows exists) Ex. R> show test_card Personnel Manager will open to that card   Change the Continuum Menu Personnel button that launches a listview to select a cardholder This is similar to option 2 except the button config is different Create a listview called Launch_PM In the listview place the following qualifier. (Name is like Prompt("Name is like", "*")) For the Personnel button configure the command and arguments lines to be: C:\Program Files\Continuum\Launch.exe -O -Slistview "-N\Launch_PM" Result: This will run the listview, the user can then type in the name of the personnel they know exists after the "*". The listview will find the user and then they can double click on the user in the listview to bring up Personnel Manager.