Building Automation Knowledge Base

Issue ODBC used with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause ODBC (Open Database Connectivity), a standard C programming language middleware API. is used to access database management systems (DBMS). Resolution ODBC is not supported with the current or previous releases of EcoStruxure Building Operation.

Issue How can I insert the points name or path into the alarm text? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Building Operation WorkStation Cause Require dynamic text insertion in the alarm text. Resolution The following substitution codes exist for alarm messages: All SBO/EBO versions:  @(F) – The path of the monitored variable.  @(O) – The monitored object name.  @(P) – The monitored variable. In addition to the above, Version 1.2 also includes: @(V) - Displays the value of the monitored variable at the time of the state change. e.g. If you create an alarm that is monitoring a temperature object named Room1Temp and write an alarm message that says: “The point @(O) is too hot.” When the alarm is triggered it will display: “The point Room1Temp is too hot.” Refer to: Alarm Messages  

Issue Is it possible to set/change the time for a time schedule in TAC Vista from a OPC client? Product Information TAC Vista Environment Vista Server Vista OPC Server Cause  In the OPC standard supported by TAC Vista time schedules are not included Resolution No it is not possible to set/change the time for a time schedule in TAC Vista from a OPC client?

Issue Extended LonTalk is supported In Vista 5.1.5 but it doesn't work, it is possible to read but not write to the device. Error message when writing: "Local network management failure" Product Line TAC Vista Environment Vista Server Cause When adding a Extended LonTalk device in to TAC Vista, TAC Vista will see in the xif file that this is a Extended LonTalk device and set a Extended LonTalk device flag for that device. It is possible to see the flag if hold down shift+Ctrl and click in properties for the lon device, it is called "EXTENDEDLONTALK".  If the xif file is imported to a TAC Vista with a version earlier than Vista 5.1.5 the Extended LonTalk will not work. Resolution Make sure the "EXTENDEDLONTALK" flag for the lon device is set, if not import the xif file again in Vista 5.1.5.  

Issue Nothing happens when starting the OGC editor Product Line TAC Vista Environment Vista Server Vista Workstation Cause The issue is with data execution prevention (DEP) not allowing the tacdraw application to run.  Resolution If DEP is not required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for essential Windows programs and services only" Reboot the computer and the editor should launch like normal.  If DEP is required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for all programs and services except those I select" Then click the add button and navigate to: For Vista 5.1.4 and up: C:\Program Files\Schneider Electric\TAC Vista 5.1.4 and choose the tacdraw.exe file. For Vista 5.1.3 and prior: C:\Program Files\TAC\TAC Vista 5.1.X and choose the tacdraw.exe file. Reboot the computer and the editor should launch like normal.  

Issue Error "Not enough space in RTI device"   Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Memory in PSU is corrupt. Resolution Run Dongleutil, a dongle reset utility software. This utility resets the memory in the PSU that is connected to the PC. You need to install the license file again after this operation. This problem is usually seen when Inhouse PSU is used. In TAC Vista version 4.10 and later, it’s no longer necessary to install the engineering file when Inhouse PSU is in use. Just connect the PSU to the PC, and everything should work fine.

Issue TGML numeric presentations rounded to integers with no decimals displayed. Product Line TAC Vista Environment Vista Workstation Vista Server   Cause Depending on the component being used to display the numeric data, it may be as simple as a property not set to display decimals. It may also be due to presentation values. Resolution If using the default Numeric Presentation from the provided Snippets library, change the property in TAC Graphics Editor for 'Decimals' to the number of decimals to be presented i.e. 4 decimals = .0001, 2 decimals = .01, etc. If not using this Snippet, check to see if getPresentationValue() is being used in a script, or if the binding itself has the Format attribute set to Presentation instead of None. Presentation value will inherit all formatting from the Vista database and not from the TGML source file.

Issue There was a problem with the SQL server and the logs and events were queued in the $Queues folder.  The SQL problem is resolved but the $Queues folder has grown so much that it can't be opened to check. Is there a way of checking if Vista has restarted logging to SQL? Product Line TAC Vista Environment TAC Vista Server Microsoft SQL Server Cause When a problem occurs with the SQL server, the log values and events are saved in the $Queues folder in the TAC Vista database, so that no information is lost. As long as there is no connection to SQL, the logs and events will be queued in $Queues. Once a connection to SQL is re-established, Vista will start logging all the values in the $Queues folder, gradually emptying the folders, although this may take some time if the SQL server has been down for a while. Resolution Query the SQL database and check for logs with today's date. Download & install Microsoft SQL management studio (2005 or 2008 depending on which version of SQL is being used) Query the trend log table for logs using the following query: Start SQL management studio and log in to the TACVISTA sql instance. Click on New Query and type in the following query: use taclogdata go select * from TrendLogValue where LogTime > '2011-11-03 00:00:00.000' Note: if you have a custom configured SQL database change taclogdata to your database name. -Change the date to today's date and execute the query. If the query doesn't return any matches, change the date to an earlier date and repeat.   -Keep going until the date when contact with SQL was lost. If no matches are returned, check that the service TAC DSS writer is running. If it is then it maybe that the Vista is till trying to clear the backlog. Try again later.

Issue Summary view for Forced Value on I/O Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Automation Server or any of connected devices can potentially have many points or values. Need to discover which ones are in Forced state. Examples: A Digital Output with default value: Digital Output with Forced value and ON: Digital Output with Forced value and OFF: Resolution You can search for forced values using the search function in WorkStation. Enabling In device option will enable finding forced values on devices hosted under EBO, as SpaceLogic and EasyLogic devices, MP and RP controllers, IP-IO modules and RP-IO modules. For more information, see Searching for Forced Values . You can also view the search in WebStation:   In EBO 2023 or later, You can search for forced values in WebStation using Diagnostics. For more information, see Displaying a List of Forced Values in WebStation .  

Issue When an attempt is made to activate a License, the following error is displayed, and the license is not activated.   Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In this case the Entitlement was inactivated due to a double registration made by mistake by the Orders Dept.  Resolution Used the second active Entitlement ID to activate the license.   For more information, refer to WebHelp articles 6367 and 7440.

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).  

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue What is the maximum binding count per graphic when polling OPC tags? Product Line TAC Vista   Environment Vista Server Vista OPC Server Cause There is no limit to the number of OPC tags, but performance may be affected when a large number of binding are used. Resolution The load on the Vista server should be considered. E.g. datatypes and the update period: Does an outside air temperature tag need to be updated every 10 seconds or is 10 minutes maybe more appropriate? Can binary signals be combined into a single register?

Issue How to install Vista/Xenta Language packs Product Line TAC Vista   Environment Vista Server TAC Xenta Server Vista Webstation Vista Workstation   Cause There are 4 different components that you can change the language on Vista server Vista workstation Vista webstation Xenta server's The files you need for this can be downloaded on Extranet, if your preferable language does not exist it might be because they are not done with the translation for that current version or the language does not exist. The most used one are Danish Finnish German Norwegian Polish Spanish Swedish The native language is English NOTE: Remember, in order to download the correct version, the language pack needs to be same version as the current software installed. Resolution There are 4 files that need to be downloaded and executed. The example below points to Swedish language pack files for version 5.1.6. To find the correct files search the download center for "Language Pack" as well as the desired language and version. The install order does not matter. TAC Vista Server 5.1.6 Language Pack Swedish TAC Vista Workstation 5.1.6 Language Pack Swedish TAC Web Applications 5.1.6 Language Pack Swedish TAC Xenta 700 5.1.6 Original Language Pack The first three files are straight forward.  After the install is complete, the language files have been changed and you can run the software with the new language (Vista software should be installed prior installing the language pack). The Xenta Server web interface will not change language until you download a project with the correct settings. When you do the download make sure you choose "Send all project and language files"  (see picture).     Note: For new Windows it sometimes require a multilingual file to be installed from Microsoft. Make sure the OS supports the language you want to install. After that file has been installed, change the Language for non-unicode program to the preferred language (requires a restart of PC).

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.     Open Windows Command Prompt Enter :telnet <address_of_remote_server> <port_number>" - telnet 192.168.1.2 443 Result if Port open: blank window with blinking cursor Result if Port closed: error message displayed similar to "Connecting To 192.168.1.2…Could not open connection to the host, on port xx: Connect failed" The example above test for connectivity against the remote server that has the IP address of 192.168.1.2 over port 443

Issue How to setup a Pelco DVR in Security Expert. Product Line Pelco, EcoStruxure Security Expert Environment Security Expert Pelco DVR Endura DVR Cause Unsure what the Service Port and DVR port settings are and how to configure the rest of the settings for a DVR object in Security Expert. Resolution When configuring your DVR in Security Expert you use the Custom DVR Type, all the preset DVR types are for legacy systems. In earlier builds of the software Video Services were integrated directly, these are now being run as separate services. When you install the Video Service you specify a Service Port – it can be any unused port whatsoever, the default is usually fine – take note of this port number. Once installed you need to manually start the service. In Security Expert you set the DVR Type to "Custom", set the IP Address, and then the Service Port same as above – the DVR Port is configured from the DVR software/Web interface, usually their documentation will cover this. Then just add the Username and Password used to login to the DVR. (See image below which shows the relevant settings highlighted in red.) If you make any changes to the DVR settings you will need to restart the Video Service and the Security Expert DVR B service for them to take effect. In Security Expert, add DVR objects by going to Monitoring > Setup > DVRS IP Address: IP of the DVR. DVR Port: Defined in the DVR software/Web interface. The default for the more recent Pelco DVRs is 60001, and the older models is 18772 (consult your specific DVR documentation for details). Service Port: Port configured during installation of Pelco Video Service. (This field appears when DVR Type is changed to Custom) DVR Type: Select Custom. Username / Password: Credentials for the DVR.   Also refer to Support for Pelco VideoXpert Integration and Pelco's partners website for up to date information on Pelco integrations with Security Expert.

Issue A correct IP, Subnet Mask, and Default Gateway addresses are required for the MNB-1000 to communicate properly via BACnet/IP but what about BACnet Ethernet? BACnet IP requires a valid IP address to be routed in a TCP/IP network. please read the example below in the resolution BACnet Ethernet requires a valid six-byte MAC address assigned by the manufacturer and only operates within layer 2 of the OSI model.  It is non-routable protocol Example of Ethernet address:  00:00:AC:56:78:90 Product Line TAC IA Series Environment I/A Series MNB 1000 Cause BACnet IP is a requirement and needs information on configuring the settings to enable communications. Resolution MNB-1000 controllers must have a valid IP address, Subnet Mask address, and Default Gateway address for the communication ports to function properly if BACnet/IP is enabled. If 0.0.0.0 is used, the communications ports may be disabled and no longer communicate after the controller is reset. In the event that 0.0.0.0 was entered and the communications port is disabled, there is currently no field workaround or way to repair it. The controllers will have to be returned to the factory for repair. Never enter an invalid IP, Subnet Mask, and Default Gateway address for new installations. Review and update current installations. To connect to the MNB-1000 for the first time it will require an Ethernet connection.  When you select the BACnet IP tab and enable IP the default IP address from the factory is a valid address of 10.1.10.2 with a subnet mask of 255.255.255.0. Default example: IP address 10.1.10.2 Subnet mask 255.255.255.0 Gateway 0.0.0.0  (If you do not have a default gateway IP address then enter 0.0.0.0 in the default gateway section)

Issue Downloads to some, or all, controllers are not working. Controllers are online to Security Expert but do not receive updates to Users or other changes and forcing a download does not work. Product Line EcoStruxure Security Expert Environment Security Expert Cause One of the Controllers download files has become corrupt. Resolution On the Security Expert Server browse to ..\ProgramData\Schneider Electric\SecurityExpert\Download. Review the Controller .dat files, there is one file for each Controller Id in the Database. Check if any of these files have a 0 bytes file size. Shut down Security Expert. Shut down the Security Expert Download Service. Delete each of the .dat files that does have a 0 bytes file size. These will be automatically recreated from the data in the Database. Start the Security Expert Download Service. Start up and login to Security Expert. Attempt to perform a forced download to the controllers and review the Download Server Diagnostics Window to confirm the controller has been downloaded and .dat file created.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue Require method on how to latch unlock a Door by Triple Badging. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require Door to be controlled normally with card access but also to allow a valid User to latch unlock the Door with three consecutive valid badges. Resolution Required Objects virtual Output - Flag to trigger latching (v_TripleBadgeLock) Programmable Function - Latches Door when virtual output ON (Door_UnlockLatch) Programmable Function - Unlatches when virtual output OFF (Door_UnlockLatch_Restore) Door - Door to control (MainEntrance) Configuration Create virtual Output v_TripleBadgeLock. Set Module Type to Output (PX) and Module Address and Module Output channel to ones that do not exist. Virtual Output On the Reader Expander > Reader 1 tab - Set Reader 1 Arming Mode to Toggle Function Output on 3 Reads Set Reader 1 Function Output to v_TripleBadgeLock Reader Expander - Configuration Go to Automation > Programmable Functions and create Door_UnlockLatch  - Set Type to Door Control - Set Mode to Normal Programmable Function - General Under Door Control tab - Set Door Function Mode to 2 - Follow Pulse On Output - Set Door Control Mode to 1 - Latch Door Unlock - Set Output To Check to v_TripleBadgeLock - Set Door To Control to MainEntrance - Save changes - Right-click Door_UnlockLatch function and select Start Programmable Function - UnlockLatch - Door Control Go to Automation > Programmable Functions and create Door_UnlockLatch_Restore - Set Type to Door Control - Set Mode to Normal Under Door Control tab - Set Door Function Mode to 5 - Inverted Follow Pulse Off Output - Set Door Control Mode to 0 - Emulate Unlock Menu - Set Output To Check to v_TripleBadgeLock - Set Door To Control to MainEntrance - Save changes Right-click Door_UnlockLatch_Restore function and select Start Programmable Function - Unlatch - Door Control