Building Automation Knowledge Base

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 Require details on how to migrate Users from an SP-C-WEB to Security Expert. Product Line Security Expert Environment SP-C-WEB Security Expert Cause Have a site that has outgrown it's SP-C-WEB installation and is upgrading to Security Expert to expand. Resolution Door configuration and programming cannot be migrated from an SP-C-WEB installation to Security Expert, but the User database can be exported to a CSV file and then imported into Security Expert to help with the migration. Exporting User database from SP-C-WEB to CSV file From the SP-C-WEB user interface navigate to Users | User Search. In the User Search page on the top right (under date) is the Export button. Clicking the Export button will generate a .csv file of all User details. (See attached example Exported Users.zip) Editing User CSV file for importing into Security Expert The Security Expert User import requires the CSV file to be in a specific format: FirstName,LastName,FullName,Facility,Card,PIN,AccessLevel The rules for this format are that: Each field must have a value however the firstname/lastname can be omitted if the fullname is used and vice versa. The facility can be omitted if it is prepended to the card number and separated with a colon (eg 123:4567). If a matching Access Level is not found, a new access level is created. The PIN and Card must be unique for each user. The file cannot contain a header row. Some examples of correctly formatted data are: Joe, Stanley,Joe Stanley,123,4587,1418,Warehouse Staff Georgia, Smith,,123,4654,6884,Warehouse Staff ,,Billy Randall,123,4727,3492,Warehouse Staff Frank,Powell,,,123:4639,3160,Warehouse Staff Importing Users from a CSV File into Security Expert In the Security Expert Client navigate to Sites | Import Users to launch the Import Users Wizard. Browse to and select the CSV File you wish to import the users from, then click OK. Figure 1 - User Import Dialog The Users records are created and a message is displayed to indicate the action was successful.

Issue When saving a Plain English program, Continuum shows error messages and cannot save the PE program. 'Error: Unable to lock an object because it is already locked', or 'Unable to find an object in the database' Environment Continuum system Plain English program Cause FiringOrder attribute of the controller (or the workstation) is editlocked PE is not registered in the FiringOrder attribute of the controller (or the workstation). Resolution When saving a PE program, Continuum gets error of 'Error: Unable to lock an object because it is already locked' followed by 'Error Text Undefined [TBD 0xc2ff1410]'. This happens when the FiringOrder attribute of the controller (or the workstation) is editlocked. Unlocking the FiringOrder (Set CXName\FiringOrder Editlock = False) will fix the problem. When saving a PE program, Continuum gets error of 'Unable to find an object in the database'. This happens when the PE is not registered in the FiringOrder attribute of the controller (or the workstation). In order to Verify, open the program in the PE editor, right click inside the program, select the Firing Order, check if the program is listed on the Member List page. In order to fix the issue, verify the FiringOrder Editlock is false (ie, print CXName FiringOrder Editlock), export the PE program to a dump file, delete the PE program, import the dump file of the PE program back to the controller (or, create a new program and copy the source code from the dump file.). 

Issue When installing SE7000/SE8000 Room Controllers to connect them to a BACnet MS/TP network, multiple issues can arise: Leaving the Room Controller's COM address at 254 (default value out of the box) will make the room controller undiscoverable by the front end. Choosing a Com address value between 128 to 253 will cause the front end system to convert the com address to 127, causing duplicates when working with multiple Room Controllers. Room controllers with COM address set to 0 will prevent the front end from discovering any devices Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Other Environment SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Viconics branding VT8000 Series SE7000 Series Controllers, VT7000 Series Controllers, 7600, 7300, 7200 Cause Master devices, those who participate in the token-passing protocol, must be addressed from 1 to 127. Addresses from 128 to 253 are reserved for slaves who do not participate in the token passing; however, they can occupy lower addresses as well. Resolution COM address must be changed to a value in the range of 1-127.

Issue Writing directly to a SR (set-reset) simple block in a Xenta 700 Menta application where that SR output is sent to a Delay block, the Delay block may not delay. The output on the Delay block will be set immediately, without any delays. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around by not writing to the SR block itself, but to a block in the logic before the SR block.

Issue Importance of correct selection / installation of Satchwell 3-port Valve Body to provide Mixing function or Diverting function. Environment Satchwell 3-port Valve Body to provide Mixing function or Diverting function in heating or cooling circuit.   Satchwell MB, MBF, MJF, MZ, MZF, MZX Cause Incorrect selection / installation  of Satchwell 3-port Valve Body to provide Mixing function or Diverting function may result in poor control, damage to the Valve Body, damage to the Valve Actuator or damage to the hydraulic installation. Resolution Determine which of the following types of hydraulic circuit the Satchwell 3-port Valve Body is to be installed in. Constant Temperature Variable Volume (CT) circuit e.g. AHU Heating / Cooling Coil or Calorifier Coil  Variable Temperature Constant Volume (VT) circuit e.g. Radiator System For Constant Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) MB, MBF install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) OR MB, MBF may alternatively be installed in FLOW pipework Port 3 - Connect to Bypass (OUT) Port 2 - Connect to Coil Flow (OUT) Port 1 - Connect to System Flow (IN) For Variable Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) MB, MBF install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) OR MB, MBF may alternatively be installed in RETURN pipework Port 3 - Connect to Bypass (IN) Port 2 - Connect to System Return (IN) Port 1 - Connect to Boiler Return (OUT) N.B. It should be noted that the alternative installation methods are valid for the MB and MBF Valve Bodies due to the ROTARY SHOE construction of the MB and MBF Similarly it should be noted that the alternative installation methods are not valid for the MJF, MZ, MZF and MZX Valve Bodies due to the PLUG AND SEAT construction of the MJF, MZ, MZF and MZX . Failure to install MJF, MZ, MZF and MZX Valve Bodies correctly in the pipework may result in VALVE VIBRATION in the pipework caused by WATER HAMMER    INSTALLATION OPTIONS - MJF, MZ, MZF and MZX 3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO MIX IN THE FLOW VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO DIVERT (BY MIXING) IN THE RETURN VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   INSTALLATION OPTIONS - MB, MBF  3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE FLOW USING TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE RETURN.USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Ports 2 & 3)) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE RETURN USING TWO “IN” PORTS (Port 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE FLOW USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Port 2 & 3)   RELATED INFORMATION - DIVERTING IN THE FLOW It should be noted that some manufacturers produce 3-Port Plug and Seat Valve Bodies specifically designed to DIVERT in the FLOW.  Such Valve Bodies have 1 IN Port and 2 OUT Ports   Please check the latest catalog for current equipment.  

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue The communication with TAC Xenta controllers is slow or inconsistent Product Line EcoStruxure Building Operation Environment TAC Xenta LonWorks communication Cause The Non group receiver timer is not properly set. Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones. If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application. The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time. If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms. Resolution Change the Non group receive timer of the Xenta devices. The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:   Number of network variables Non group receive timer value < 50 768 ms (default) 50 – 100 1024 ms > 100 1536 ms     The default value for the AS and AS-P  is 8,092 ms. There is no need to change that value.

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

Issue System tree pane not working in webstation Get failed "Unable to locate path /your/path/../ Either the path is invalid or the location is currently offline" Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause If the root path is changed in a workspace then the issue below occurs. Webstation is trying to locate the system pane in the folder indicated in the Root path. Resolution Go to Server > System > Domains > Your domain > Workspaces Click on the workspace that us used Click on the content tab Change the root path back to ~

Issue Clarity is needed on the new ES License Inheritance feature available in EBO 3.x Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Enterprise Central Building Operation SmartX Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in SmartX Servers, such as SNMP Licenses, since EBO 2.x.  The concept of Inheriting Licenses from an ES into a SmartX Server is a new option which can be used from EBO 3.1 onward, although the original Embedded License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   In EBO 3.2 SNMP and TimescaleDB. Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   'Inheritance' means that an ES License will be shared down to its child SmartX Servers while also being retained for use by the ES.   Note: SmartX Servers must be running the minimum supported 3.x version for Inheritance to function There is no such thing as a 'Site License' that can accommodate multiple ES There is no Licenses Inheritance from an EC

Issue Menta Parser Error when attempting to direct download a Menta application. Warning Reference to unsupported I/O Error in COD file - Error:13 (Y=___ X=___) Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The application may contain an I/O terminal that does not exist in the device type to which the application is being downloaded.  This error could also occur in situations where the same I/O terminal reference is used more than once in the application (this could be on the Xenta or the I/O module). Typically caused by copy/paste. Resolution It is possible to have a Menta application that looks to be error free during simulation or the generation of the XIF file, but when the application is downloaded to the controller and it is being parsed by the device it reports a warning about unsupported I/O and leaves the controller without an application. The error window that pops up when trying to perform the download directly from Menta is attempting to show where in the Menta file the error is occurring.  If you can read the point names that are highlighted it can help direct toward the invalid I/O termination.  The other option is to look in Options > I/O configuration and make sure there are no duplicates or invalid I/O terminations.  For example, a 401 doesn't have any onboard I/O so a termination of M0-K1 wouldn't be valid. Note: It is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.

Issue How many MSTP networks can you connect to an Automation Server (AS or AS-B)? Product Line EcoStruxure Building Operation Environment Version 1.3 and newer MSTP Network on an StruxureWare Building Operation Automation Server (AS or AS-B) BACnet MSTP Devices Cause Require 2 separate MSTP networks, either to use 2 different Baud rates or to speed up the network and split the devices across the 2 ports. Resolution You can create 2 separate MSTP networks under the BACnet interface of an AS-B or AS (version 1.3 or higher), one on Comm A the other Comm B. Each can run at different Baud rates if required. For the number of supported devices please reference, Maximum number using StruxureWare Building Operation (Scalability and Capacity). Please be aware that the listed maximum is for the Automation Server allowing you to distribute between the two comm ports.

Issue TAC Xenta I/O modules do not come online after a download from System Plug-In Rapidly blinking green light on I/O modules show offline status (fast blink) Product Line TAC Vista Environment Xenta 400 series I/O modules Cause No I/O assigned to the module in the Menta file Needs a power cycle after download to associate with the base unit Resolution Verify that at least one hardware input or output is assigned to a terminal on the I/O module. If the I/O module is a spare that has been added for later expansion capabilities, it will never associate with the master or report an online status. If this is the case, assign a "dummy" input to the module temporarily if the rapidly blinking LED is a concern. Sometimes even if all of the correct information is downloaded to the TAC Xenta controller, the green light is still blinking rapidly (not configured) on the TAC Xenta I/O module. If this happens try to power cycle the TAC Xenta controller.

Issue How to setup and use the Plain English Alarm function?   Product Line Andover Continuum   Environment PEAlmFunction, PERtnFunction CyberStation Alarm Workstation PE function Cause Manual configuration is required to create the Plain English alarm function and set certain registry keys.   Resolution As a function of Continuum CyberStation Alarm Engine, user written Plain English functions are automatically invoked at a workstation when an alarm occurs when an alarm is acknowledged when a return-to-normal condition occurs. The user optionally specifies the names of those functions in the Windows registry, and they will be called appropriately. Registry keys used for calling Plain English Alarm function PEAlmFunction : The name of the user-defined PE Alarm Function. (Ex. “AlmProcess”) PERtnfunction : The name of the user-defined PE Return-to-Normal Function. (Ex. ”AlmProcess”) Example of the Plain English Alarm function is as follows: Arg 1 A ' Network AliasName(16) Arg 2 B ' Controller AliasName(16) Arg 3 C ' Infinet Controller AliasName(16) Arg 4 D ' Object name(32) Arg 5 E ' Object AliasName(16) Arg 6 F ' Object Description(32) Arg 7 G ' Object Value(Numeric) Arg 8 H ' Alarm State(3) ALM,RTN,ACK Arg 9 I ' Graphic Object AliasName(16) Arg 10 J ' Alarm Enrollment Alarm Message(String) Arg 11 K ' Alarm Enrollment AliasName(16) Arg 12 L ' EventNotification AliasName(16) Arg 13 M ' EventNotification Priority (Numeric 1~255) Arg 14 N ' TimeStamp(16) Arg 15 O 'Logging Flag (1~255) ' String 1 Q String 80 AlmDir, Fnam File AlmF ' If M < 100 then AlmDir = "C:\" Q = chr(96) Fnam = NumToStr(random(Second)) OpenFile(AlmDir ; Fnam ; ".alm", WriteOnly, AlmF) Print L ;", " ; K ; ", " ; A , B , C , D , ", " ; G to AlmF CloseFile(AlmF) Endif Return Success Create the following registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls \Continuum\Settings: PEAckFunction (REG_SZ) PEAlmFunction (REG_SZ) PERtnFunction (REG_SZ) PEMaxBufferedAlarms (REG_DWORD) PEPopAlarm (REG_DWORD) Set PEAlmFunction to “AlmProcess” Set PERtnFunction to “RtnProcess” Restart Continuum. Create PE programs in the workstation called AlmProcess, and RtnProcess with source code similar to the example function. Files will be created in the specified directory containing the alarm and return to normal information.

Issue Not all commands in Plain English are available in Building Operation Script. Product Line EcoStruxure Building Operation Environment Script editor in Building Operation Cause Conversion of PE to Building Operation script is unsuccessful. Unsupported Script commands. Resolution Plain English may be imported into Building Operation; however, there are some minor edits that must be performed to make it work. Bindings must be applied. There is some automated manipulation of PE to Script upon import and it should continue to improve in future releases. By creating a "dump" file in Continuum and editing the file to remove the Header and Footer areas, the remaining code can be imported into Building Operation as Script. There are some functions Continuum uses that will not be used in Building Operation, the Script will error upon event to save if unsupported code is used in the imported script. Notification of each line of code is in error will occur upon a save attempt. Navigate to the lines in error and correct the code. The following link has information on PE to Script changes. Log in is required to access full online help: StruxureWare Building Operation Online Help

Issue Emailing alarms if Microsoft Outlook is not used on the site? Product Line Andover Continuum Environment Continuum Cyberstation 1.73 and above bCX 4040 Netcontroller II (9680) ACX57xx Series (ACX II) Cause The customers site IT system is unable to provide reliable Email communications from Microsoft Outlook on the Continuum Workstations. Resolution The documented Outlook support: Initially Full Microsoft Outlook or Microsoft Exchange was specified as the requirement 1.92 to 1.94 specified Microsoft Outlook 2007 for Windows XP and Vista (Full Microsoft Outlook or Exchange) 1.94sp1 to 2.03 specified Microsoft Outlook 2007 Microsoft Outlook 2010 (Full Microsoft Outlook or Exchange software package)   For further information on outlook versions see the KB article Outlook 2007 and Outlook 2010 with Continuum email alarms. Notes Only 32bit Outlook was tested/supported Continuum does not support MS Outlook Express for emailing alarms From v2.0 CyberStation has internal SMTP email options see  SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 There are other email option for emailing directly from controllers. There is a feature in the bCX (also NetController II, ACX II) controllers to be able to email messages directly to a SMTP server either manually or via Plain English programs, although this is not directly linked to the Continuum Alarm system and would require a Plain English program to determine what emails are to be sent. See the "bCX1 Controller Technical Reference" Commissioning section for details on how to set up the controller to send out emails to a 3rd party SMTP email server.  There is also the Continuum SNMP Configuration guide for use with SNMP alarming with a Network Management System. Then in the CyberStation online help see the "SendEmail" function help on how to use Plain English to get the bCX (Netcontroller II or ACX II) to send out messages via email.  

Issue Is there any way I can transfer a value between 2 LUA programs without using a BV or AV? Example: A Lua program (PG1) is created to turn on lighting, a variable called LightOn is created but other Lua programs PG2, PG3, PG4 cannot reference the "LightOn" variable. Is there any way a variable from one Lua program can be accessed from another Lua program? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Lua programming Cause Each PG script has its own dedicated environment, which basically means variable names cannot be shared between scripts. The only things that can be referenced are actual objects (AV, BV, etc.) Resolution An AV or BV object will need to be created within the EcoStruxure Building Expert controller to store the value and make it available for other programs to read. For example a BV1 could be created and read from or written to by multiple Lua programs by referencing ME.BV1 For more information, please reference the EcoStruxure Building Expert Software - User Interface Guide document on the Exchange.

Issue In many situations, customers need to integrate more than one LNS database into a single Vista database. Product Line TAC Vista Environment Vista LNS LonMaker NL220 TAC Vista System Plug-In Cause This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database. This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database. Resolution Some general rules must be followed when integrating multiple LNS databases into one Vista database. These rules are: You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication. NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack. When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously. If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed. Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server. It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below. The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2. Please follow these instructions: Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.   The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database. As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400

Issue How do Automation and Scripts work in Security Expert? Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause Lack of understanding regarding the usage of Automation and Scripts features in Security Expert. Resolution 1. Automation Automation is used for C-Bus interface programming in Security Expert. It allows Security Expert to send signals to the C-Bus Network or change the state of Security Expert outputs based on control signals from C-Bus. Note: This integration is not currently validated or supported. 2. Programmable functions: Programmable functions in Security Expert enable you to directly monitor and display analogue values, such as those from HVAC systems, using Data values and Variables. These values can then be used to trigger functions within Security Expert. You can set up programmable functions to control logic within Security Expert, Doors, Areas, Elevators, and more. For further information, please consult the help file. 3. Scripts: Currently, Scripts are not available in Security Expert. The "Run Script" option under Events > Actions > Configuration > Type does not have any functionality.