Building Automation Knowledge Base

Issue External Log Storage PostgreSQL / TimescaleDB schema. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.0 and above External Log Storage Cause Need to understand what is supported with regards to third-party queries to the PostgreSQL / TimeScaleDB  Resolution The PostgreSQL database schema is not published by R&D (The Report Server schema can be generated via WebReports see Obtaining a Database Schema for EBO WebReports / Report Server - Communities, but should not be compared with External Log Storage) In order to get visual diagrams that show relations of the Extended Log Storage PostgreSQL TimescaleDB, you can download tools such as "SchemaSpy ", ERBuilder, or similar to generate it. Sample outputs are attached from SchemaSpy and ERBuilder. The PostgreSQL database schema is likely to change with each EBO version and hence is not published External Log Storage is designed to operate with EBO, rather than provide data directly to a third party - no support is offered with the third-party connection and data transfer Only third-party read querying is allowed Most tables are self-explanatory, the "trend_data" table, "Type" column is detailed below: It's a number representing which record type TrendRecordTypes = { RecordTypes::s_trendrecordTLogValueRecord, RecordTypes::s_trendrecordTLogEditValueRecord, RecordTypes::s_trendrecordTLogCommentRecord, RecordTypes::s_trendrecordTLogEventRecord, RecordTypes::s_trendrecordTLogEventValueRecord, RecordTypes::s_trendrecordTLogMeterChangeRecord, RecordTypes::s_trendrecordTLogNullEventRecord, RecordTypes::s_trendrecordTLogReconfigRecord, RecordTypes::s_trendrecordTransferEventRecord }; The record type that is most common is the TLogValueRecord, and it's 0 and so on   For reference, the only other documents available would be Alarms - Add/Remove Columns Dialog Box (Alarms) (se.com) Events - Add/Remove Columns Dialog Box (Events) (se.com) Trends - Add/Remove Columns Dialog Box (Trends) (se.com)

Issue Does Building Operation use Unicast or Multicast? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Workstation Cause Does Building Operation use Unicast or Multicast? Definitions: Unicast packets are sent from host to host. The communication is from a single host to another single host. There is one device transmitting a message destined for one receiver. Multicast is a protocol for use with IP. Multicast enables a single device to communicate with a specific set of hosts, not defined by any standard IP address and mask combination. This allows for communication that resembles a conference call. Anyone from anywhere can join the conference, and everyone at the conference hears what the speaker has to say. The speaker's message is not broadcasted everywhere, but only to those in the conference call itself. A special set of addresses is used for multicast communication. Broadcast is when a single device is transmitting a message to all other devices in a given address range. This broadcast could reach all hosts on the subnet, all subnets, or all hosts on all subnets. Broadcast packets have the host (and/or subnet) portion of the address set to all ones. By design, most modern routers will block IP broadcast traffic and restrict it to the local subnet. Resolution Building Operation is using only IPv4 and therefore Unicast only. This may change when Building Operation begins using IPv6. At that time, a site may want to use the IPv6 multicast features to address groups of targets.

Issue Site may be migrating from I/NET to another access control system and would like to import the data. Product Line TAC I/NET Environment I/NET Seven SQL Management Studio Cause The site is migrating from I/Net to Continuum or another access control system. Resolution Open SQL Management Studio and create a New Query by clicking on the "New Query" button Run the script below: SELECT * FROM InetDb.dbo.IdWorksView Note:  This view only shows the Primary Group associated with each individual.     Select File>Save Results As... Save the file as a .csv to a location of your choosing

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Cause The Enterprise Server and the Automation Server (ASP/ASB) do not synchronize time to each other, they must use an NTP server for synchronization Resolution The information below is mainly concerned with synchronizing the time setting but not the actual time.   Overview To synchronize the server times an NTP Server will be required, they do not synchronize time with each other. A common misconception is that the Automation Servers sync time with the Enterprise Server via server-to-server communications. To find an external NTP server consult support.ntp.org . Alternatively, an existing internal NTP server can be used or consult Setting up a Local / Internal NTP Server to configure the Enterprise Server computer as a time server The time settings on the Enterprise Server are configured through the operating system settings on the computer where Enterprise Central is installed.  EcoStruxure Building Operation cannot be used to configure the NTP server for the Enterprise Server. Please refer to Network Time on WorkStation, Enterprise Server, and Enterprise Central To find the Network Time Protocol (NTP) configured on a WorkStation, Enterprise Server, or Enterprise Central computer open a command prompt and enter w32tm /query /peers. If configured the peer NTP server(s) will be listed If you need to ensure an NTP server is actually running on certain IP or DNS address, please reference Ensure IP or DNS address is valid NTP server The time settings on the Automation Servers can only be configured via the Workstation. As per the image they can be configured to look at an NTP server (1) or set manually (2). For synchronization, they must use an NTP Server. Please refer to  Network Time Server on an Automation Server on Webhelp Starting in version 1.5, the time adjustment depends on how much the Automation Server drifts from the NTP server. The faster the Automation Server drifts, the more frequently the time is updated.  Please refer to How often will an Automation Server ask the NTP server for the time?  If the time server is a URL, such as time.nist.gov, then it is critical that a Primary DNS is set for each Automation Server, and possibly a Secondary DNS via Device Administrator. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. Please refer to Configuring the Automation Server IP Address on Webhelp The time displayed for a server in Workstation (Properties -> Basic) will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of the server adjusted to client local time zone, while the fields below "Server time" represent the settings of the Automation Server.   How to synchronize date and time settings on multiple Automation Servers   IMPORTANT: Only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.   The synchronizing of multiple Automation servers can be achieved with a lead/shadow relationship. The primary and secondary network time server settings for connected shadow Automation servers are defined on the Enterprise server. Setting up the Primary and secondary time servers in the Enterprise Server only passes those configuration settings to the AS controllers, it does not send the actual time and date value.   Select the Enterprise server (1), click the Date & Time tab (2), select Enable (3) and enter the Primary time server (4) and, if used, the Secondary time server (5) the Automations Servers will use. Ensutre the time zone for the Enterprise Server is set correctly (6).   Save the settings  From EBO version 2.0 all Automations Servers are automatically configured to shadow the date and time settings configured in the Enterprise Server. To verify this expand the System folder of an Automation Server and select Time Settings -> Date and Time (1). Observe the Date and Time are Shadow-Read only (2), replicating the Enterprise Server settings. Attempting to change any of the settings, other than the Lead object (3), will result in an error. All the Automation Servers will be 'looking' to the same Primary (4) and Secondary time servers, i.e. they will all receive the same time and be synchronized Similarly, select the Time Zone (1) of the Automation Server in the System Tree; this will also be shadow-read only (2). The lead object is set to the Time Zone on the Enterprise Server (3) Before EBO version 2.0 the Automation Servers were not automatically set to shadow the Enterprise Server settings but this could easily be achieved en masse using Search . In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search (1) to find the date and time object of all connected servers. In the Search view select the servers (2) that require their Date and Time settings synchronized to the Enterprise Server, the Enterprise Server does not need selecting. Select the Time tab (3) and then click the triple dots (4) to navigate to and select the Date and Time object on the Enterprise Server (5)   You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers Note: To set up synchronization of the time zone settings follow the above search steps for date and time but search on Time Zone Tip/Tricks To see the time of on the Enterprise Server and multiple Automation Servers use the Search to find the Date and Time object (1). Individually select each server (2) and then drag the Date and Time object (3) into the Watch Window (4) It is the Automation Server that initiates the synchronization. To check the Automation Server communication settings select the Automation Server (1) and in the Communication tab (2) select the Enterprise Server (3) and make sure the Automation Server has the correct IP address (4) To check the Enterprise Server communication settings select the Enterprise Server (1) and in the Communication tab (2) select each Automation Server (3) and make sure the correct IP address is specified for each Automation Server (4).  If a firewall exists ensure that the ports are open so the Automation Server can connect to the Enterprise Server. Please search for the EcoStruxure Building Operation IT Reference Guide on Exchange for details Further Information Release 1.2.0 and higher Until the time is set, b3 data will not update in the Watch Window Until the time is set, BACnet COV will not be functional Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server To adjust the Automation Server time, time zone, and DST, access to the Automation Server is through a WorkStation

Issue Need to verify Network Time Protocol (NTP) server is running/listening on IP or DNS address. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Automation Servers require valid local or internet NTP servers for accurate timekeeping. Resolution Check an NTP server using this command at the Windows Command Prompt: w32tm /stripchart /computer:<IP Address> /dataonly /samples:5 Substitute the DNS name or IP you want to test for <IP Address>.   Additional Notes: Windows machine must be on the primary ethernet network, as Automation Server's secondary IP Port will not route NTP traffic. Connected to site VPN may or may not perform as expected based on VPN Configuration for the site. One can always remote desktop the Enterprise Server and run Command Prompt to check locally. If the Enterprise Server is configured in a Virtual Environment or on a separate subnet from the Automation Servers, then Enterprise Server Gateway may be an NTP server, so one change to check that IP address using this method. Examples of Success First screenshot is local Enterprise Server running Meinburg NTP server. Second screenshot is an internet NTP server. Example of Failure Screenshot is local Enterprise Server gateway that is NOT running an NTP Server.  Related Article: Time Synchronization of the ES and AS

Issue A Schedule or PE program can not change the value of a point because it is set by another process at a higher Command Priority. Product Line Andover Continuum Environment CyberStation bCX4040 B3s Cause Command value must be Relinquished at the priority that no longer needs to control the point's value so that a command with a lower priority can take control of it. Resolution Edit the point from the BACnet view. Go to the Command Priority tab, this tab shows the 16 priorities and their current statuses   Select the priority to relinquish and then click on the Relinquish button. The command with the next highest priority should then immediately take over.

Issue Configuration of BACnet Foreign Device Registration Product Line EcoStruxure Building Operation,  Andover Continuum Environment BACnet IP  BBMD Foreign device Cause  Foreign Devices registration can be confusing Resolution When configuring a Foreign Device Registration on a B/IP BACnet Network. The Foreign Device only needs to register with the one BBMD on its B/IP Network Segment. The BBMD that has the Foreign Device registered with it creates a table called FDT (Foreign Device Table) internally which is different from the BDT(Broadcast Distribution Table) that the BBMD uses to communicate with other BBMDs.   Once the FDT confirms the Foreign Device, it is up to that BBMD to distribute BACnet communications to and from the necessary BBMD's in its BDT. and the all Foreign Devices in its FDT.  In this way the Foreign Devices does NOT perform Broadcasts.

Issue Help with Creating Custom Reports for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment SQL Report Builder 3.0 Cause In order to create a custom report for EcoStruxure, the user must have a basic knowledge of SQL and writing SQL SELECT Statements.  Report Builder 3.0 can walk a user through most of the process but there is a bit of a learning curve. Resolution If you are attempting to create a custom report the most difficult piece of information is determining what Tables store which information.  To get definitions of Table Rows, run the provided Database Schema report in the Web Reports browser.  This will show primary/foreign key relationships as well as give you information on what is stored in each column. Information on Extended Trend Logs is stored in the tbLoggedEntities table and the tbLogTimeValues Tables.   Additional Metering information can be found in tbMeter, tbMeteringLogFilter, tbEntityData and tbEntityRelation

Issue Performing Load Sources in the EcoStruxure ETL tool causes errors with the following headers:   There was no endpoint listening at http://localhost:8080/EcoStruxure/DataExchange that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The HTTP request is unauthorized with client authentication scheme 'Digest'. The authentication header received from the server was 'Digest realm="ews@SxWBM",qop="auth",nonce="AEEE5A9347E49ECADC753B5AA17EECE0",OPAQUE="5B4718"'. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Enterprise Server Automation Server Cause The EBO EWS Extract Task settings are incorrect in regards to the EcoStruxure ES or AS that it is trying to access.    There was no endpoint listening at... This error is due to the use of the incorrect port numbers in the EWS Web Service URL.   The HTTP request is unauthorized with client authentication scheme 'Digest'... This error is due to the use of the incorrect admin Username and/or Password.  Resolution The settings of EBO EWS Extract Task need to be verified and corrected.    Click on the Tasks tab in the ETL tool and select the "EWS Extract Task". The extract task settings will be displayed on the right side of the screen.                                                                               Verify that the port number in Web Service URL address corresponds to the port number being used by the ES or AS  Verify that a valid Username and Password has been entered into the EWS Web Service User Name and Web Service Password fields. 

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

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 How to bring a BACnet controller online after restoring a backup Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Customers may want to take a backup from a site and use it on other setups. If there would be any BACnet controller under the Backup, they may need to know the process of hosting the BACnet controllers under the restored backup on the physical BACnet controllers.   Resolution This video will demonstrate how to bring a BACnet controller online after restoring a backup. NOTE After matching up the Device ID of the BACnet controller under the restored server and the Object ID of the physical BACnet controller, if the hosting status shows “Not hosted”, users need to perform a "Repair Hosting". Please refer to Repair Hosting a BACnet/IP controller 

Issue Configuring Security Expert Readers Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause Security Expert Smart Card Readers have options such as Mifare Reading Mode, LED colors, etc. that can be configured. How the readers are configured will depend on the reader's firmware. Resolution The method used to configure a Security Expert Smart Card Reader depends on the firmware version it is using. There is no way to visually determine the firmware version. To identify what firmware the reader was shipped with from the factory refer to Knowledge Base article Identifying Security Expert Smart Card Readers Firmware. 1. Smart Card Readers with firmware below build 200 - (I.e. 1.04.64) These are older readers which were configured with a serial terminal program by connecting to the reader using a USB-RS485 converter. Please refer to the 'Installer Programming' section of the attached Smart Card Reader Installation Manual - Feb 2017. This has been replaced by a newer version of the manual on Exchange which no longer includes this information. 2. Smart Card Readers with firmware build 200 or above (I.e. 1.04.229) These newer readers do not have a serial interface and will require a configuration card to change reader options. The configuration card (SX-ISO-CONFIG) is ordered from Schneider Electric, see the Security Expert Credentials Order Form for details.

Issue How can the firmware version of Security Expert Smart Card Readers be determined. Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause It is not possible to easily identify the firmware which a reader has been shipped with. Serial Numbers are not sequential and cannot be used as general guide. Resolution To find out a reader's original shipped firmware version raise a case with Product Support including the Reader's Serial Number and they will be able to check with manufacturing to determine which firmware version was loaded at the time.

Issue If more than 3 Operators are created in Security Expert, the License page of the Thick Client will show more Licenses in use than the maximum three (3) clients provided with the standard SX-SRVR License. To see what the site is using, select About > License and scroll down to the Feature: Web Operators. As shown below, there are four web operators active out of the three (4/3) allowed. Product Line EcoStruxure Security Expert Environment Licensing Cause A Web Operator is defined as any Operator who can log onto the Security Expert Server using a browser.                           In the example shown below there are four Operators: admin 2nd Operator 3rd Operator 4th Operator The system allows each to log in successfully: The License option SX-WEB-OPR enables 'x' number of browser connections depending on customer needs and should effectively ensure that the correct number of Operators are purchased. However, the feature is currently in development and is not yet enforcing limits on the number of web operator connections.  This allows the number of connections to exceed the maximum limit (I.e.4/3) for the time being. Resolution Note: The Operator does NOT even need to be logged on for the count to register 4/3, the fact that 4 operators have been created is enough. The restriction of operators via Web Client could be enabled/enforced at any time in the next release of the software, so it is strongly advised to purchase the correct number of Licenses required at the time of installation, to prevent a loss of user connectivity going forward.

Issue Request for database schemas for SecurityExpert and SecurityExpertEvents databases. Product Line EcoStruxure Security Expert Environment Security Expert Client, Security ExpertServer Cause Various entities request database schemas for SecurityExpert and SecurityExpertEvents databases for reasons like access to the stored data for third party reporting packages. Resolution Schneider Electric does not publish or provide the Security Expert database schemas. Database schemas change over time with new revisions which may result in broken tables. Anything required should be available using the Security Expert SOAP Web Service Software Development Kit (SX-SOAP-SDK). The SDK will allow the extracting, transforming and storing of data into a separate database. Third-party applications/tools can then report on that data stored in a separate database. This allows the integrity of the Security Expert databases to remain intact. The Security Expert SOAP SDK can be purchased as part number SX-SOAP-SDK.

Issue Does Security Expert meet "FIPS Compliance"  Product Line EcoStruxure Security Expert Environment Security Expert Cause Unable to locate documentation for the FIPS compliance. Need to verify before Continuum access control system is migrated to Security Expert. Resolution Security Expert Software is currently not FIPS compliant. See Transition Guide Security Expert - Continuum Access Control to Security Expert - Reference Guide for more more details on what is, and is not, supported with a Continuum Transition to Security Expert.

Issue How to estimate the disk space required to accommodate a given Security Expert installation. Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Security Expert databases will grow in size depending on the configuration and logging requirements. Therefore, estimating how much a database will grow over time should be done to determine which Microsoft Database solution and hard drive requirements. Resolution The Installation Guide does have some hardware recommendations under the System Requirements section, and these should be used as a baseline for allowing appropriate database storage. 10 controllers w/ 16 modules each - 40GB More than 10 controllers w/ any number of modules each - 100GB. The configuration database (SecurityExpert) is relatively small and will typically not grow much. The events database (SecurityExpertEvents) is what logs all events and alarms, and it will grow over time, rapidly depending on what is being logged and how often. There are many variables in play from one site to another. The space required for a standard Security Expert Database is dependent on, but not exclusive to: The amount of Inputs/Outputs/Readers you have with Log Events enabled. The amount of traffic through the site. The number of Expanders and other Records. The frequency of backups and purging of events from the SecurityExpertEvents database. As a guideline, we can broadly calculate storage requirements based on the size of each event being logged. Typically this will be 564 bytes per event. If you have 2000 Events per day, here is the calculation for how many MB will be used per day: 564 B x 2000 = 1128000 B = 1.07 MB per day If those events that are being logged are alarms as well, then this total would be doubled. Another way to calculate this is to take what a typical usage requirement would be for a site or monitor a live site over a week/month to calculate the sites' average usage and extrapolate that to fit. For example, a site with 130 doors being used 8 hours a day and with door openings and closings 10 times an hour would equate to just under 1GB a month. Please note these are very rough guesses; individual sites might be busier/quieter. Performing regular SecurityExpertEvents database backups and purges will ensure that the database size does not get too large for the installation. For instructions, see the System Backups section in the Installation Guide and AN 279 Security Expert Differential Backups.

Issue Activation of the Security Expert SSN with a new installation of the client software, software extensions (e.g. SX-VIM, SX-DOR-50) and integration licenses (e.g. SX-NVR, SX-CAM-10) need to be completed manually because there is no Interne access. Product Line EcoStruxure Security Expert Environment Licensing Cause The computer which the Security Expert client is installed on, does not have Internet access to use the 'Automatic License Update' method to activate the license. The manual method must be used to register and obtain the new license. Resolution In the Security Expert client go to About | License | information make a note of your system's SSN In the Security Expert client go to About | License | License Update and select Generate a License Request File for this System Copy the 'ICT_LicenceRequest.req' license request file produced onto a machine that has Internet access. Navigate to https://se.ict.co/license/ and enter your details on this web page. Enter the SSN for your system Upload the 'ICT_LicenceRequest.req' license request file generated previously and Submit. You should then be able to download a 'Security Expert YJWB...............O4PJ5W License.lic' file. Return to your offline Security Expert Client and go to About | License | License Update , Select Browse for your Downloaded License file Select the 'Security Expert YJWB...............O4PJ5W License.lic' file downloaded previously. Once the license update is complete shut down the client and restart the services   Support for manual activation: v4.2.194 - Manual activation is supported. v4.2.216 - Manual license activation's are no longer supported and an Internet connection is required on the Security Expert installation to be able to perform a new activation or update a license. v4.2.243 - Manual activation is supported. v4.3.x - Manual activation is supported.

Issue A previous version of the client software badged SecureStruxure is installed, and needs to be upgraded to Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert SecureStruxure Cause The offer had the name changed between versions and it's not straight forward how to update the software, and databases, to the newer version. Resolution SecureStruxure can be upgraded to Security Expert by following these steps: Contact Product Support to upgrade the site license to Security Expert.. Backup the SecureStruxureOperations and SecureStruxureOperationsEvents databases via SQL Server Management Studio. Uninstall SecureStruxure. Rename the SecureStruxureOperations and SecureStruxureOperationsEvents databases to SecurityExpert and SecurityExpertEvents When you run the Security Expert installer, use the new Security Expert SSN. You will need to point Security Expert at the MS SQL database instance you were previously using for SecureStruxure (this is likely "localhost\SECURESTRUXURE"). The installation wizard should pick up the databases and upgrade them, retaining all the SecureStruxure programming. Log into Security Expert and re-license the software by going to the About | License menu option.. If you are unable to connect to the license server (no internet connection), you can use the manual method for registering a license.

Issue Require details on how to setup multiple inputs to popup the same camera window if any of them are true. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Unsure how to setup program for multiple inputs to display video from one camera when any of them are set to true Resolution 1. Under Events | Event Filters create a new Event filter 2. On the Event Types tab untick "Include All Event types" and select the Add button  3. Browse for "All Input Events", select "Input <ZONE_NAME> Opened" and click OK 4. On the Records tab select the Add button, select Device Type "Input" and your Controller, then the inputs that you want to popup this video 5. Save the Event Filter 6. Under Events | Actions create a new Action 7. Select the Type "Popup Camera Window", select the Event Filter you created in step 1, select the camera you want 8. Save the changes and test the scenario.