Building Automation Knowledge Base

Issue How to bring SX8000 objects to Continuum when upgrading. Environment Infinity SX8000 Continuum CyberStation Debug document Cause Upgrading from legacy Infinity SX8000 system to Continuum Resolution See Infinity to Continuum upgrade for information on how to convert Infinity SX8000 objects to Continuum.

Issue I/Net Controllers are Supported in the 1.3.x and higher release of Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment Site running I/Net and StruxureWare Building Operation1.3.x or higher Cause Legacy and support for various I/NET controllers Resolution The following controllers are supported: Routers: NPR 2000 TAC Xenta 527 TAC Xenta 527-NPR Site Controllers: 7798b I/Site Controller 7798c I/Site Controller 7793 Micro Controller Interface 7728 I/Site I/O Controller 7780 Distributed Lighting Control Unit 7716 PCU 7718 PCU 7756 PCU 7760 UCI (Unitary Controller Interface) 7700 DCU (MIP01) 7797 ICI (All Versions) SubLAN Controllers: 72xx Unitary Controllers 7760 Unitary Controller Interface (UCI) DPU 7910a Door Processing Unit DPU 7920 Door Processing Unit (DPU 48K) DIU 7930 Digital Input Unit DIO 7940 Digital Input Output Unit SCU 1200 Security Control Unit SCU 1280 Security Control Unit SCU 1284 Security Control Unit MR Controllers (all HVAC) MR-VAV-AX MR-VAV-X1 MR-VAV-X2 MR88 MR88R MR160 MR55 MR55X MR632 MR-AHU MR-HP

Issue SmartStruxure integration to StruxureWare Data Center Expert via EcoStruxure WebServices Environment StruxureWare Building Operation EcoStruxure Web Services StruxureWare Data Center Expert 7.2.0 Cause There is a need to have StruxureWare Building Operation pass data to StruxureWare Data Center Expert using EcoStruxure Web Services. StruxureWare Building Operation Web Services is capable of both 'Serve' and 'Consume' functionality. However, StruxureWare Data Center Expert (version 7.2.0) is only capable of Web Services 'Serve' function. Resolution Use Modbus TCP instead of EcoStruxure Web Services if StruxureWare Data Center Expert is required to read from StruxureWare Building Operation. 

Issue Confusion in documentation of the output type of an STR300 temperatire transmitter Product Line Field Devices Environment STR300 series transmitter Cause The STR300 is an electronic living space transmitter that converts a measured temperature into an electric current signal. The transmitter is delivered as a complete unit, comprising a Pt100 classB sensing element and an amplifier mounted in a housing. STR300 is intended either for surface mounting on a wall or installation in a standard switch box in dry, dust free rooms.   The HVAC Sensors Catalogue incorrectly shows that the STR300 Series has an Output of 0-10V while  the datasheet correctly shows the output as 4-20ma. Resolution The STR300 has an output signal of 4 to 20 mA corresponding to a temperature range of 0-40°C

Issue During SQL install portion of Continuum installation the following error message is received. "SQL Express is not installed properly. Please contact technical support representative." Product Line Andover Continuum Environment Continuum Cyberstation (All Versions) Microsoft SQL Express (Version dependent upon Continuum version) Cause Bit Locker has been installed on the system to which Continuum Cyberstation is being installed. Bit Locker enforces specific password requirements across all Microsoft Windows products. Find the SQL installation log at C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20190627_092341\Summary_WTUSLVSE076617L_20190627_092341.txt *NOTE* The parent folder of the log will include the date and time of the installation. The log file name format will be Summary_(your computer name)_date_time.txt At the bottom of the log, you will see an Exception summary which gives full detail of what the error is: "Exception summary: The following is an exception stack listing the exceptions in outermost to innermost order Inner exceptions are being indented Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x84b40000 FacilityCode : 1204 (4b4) ErrorCode : 0 (0000) Data: SQL.Setup.FailureCategory = InputSettingValidationFailure DisableWatson = true Stack: at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs) at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId) at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) Inner exception type: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x851a0013 FacilityCode : 1306 (51a) ErrorCode : 19 (0013)" Resolution Update or use password for new database that meets the minimum standards of: 8 Characters 1 Capital letter 1 Numerical character 1 Special character (!,@,#...) 1 Lowercase letter This will allow SQL Server to be installed

Issue I/A Series G3 Niagara network points in fault and indicate Subscribed error:invalid permissions. Environment I/A Series G3 (all versions) Cause The credentials being used by the connection does not have the correct permissions to access the data. Resolution Verify username / password and associated permissions related to station to station fox connections.  Modify the associated permissions on the server side or use another set of credentials that have permissions.

Issue Sites need guidance on how to setup custom ABA cards in Continuum. Environment CyberStation NetController I (CX99xx) NetController II (CX9680) AC1Plus IOU Module ACX57xx Cause The implementation of ABA cards in Continuum access control systems was designed to comply with the ISO 7811 ABA standard for magnetic stripe card. Because of this, the system only reads  one field (the PAN or Primary Account Number) from the ABA card, this field contains a number of up to 19 digits which is used as the card number. Continuum Custom ABA feature provides for maximum flexibility by allowing the 19 digit PAN field on track 2 of the mag stripe to be organized in sub fields such as site code etc. Resolution A summary of the steps to configure Custom ABA cards in Continuum is available through the CyberStation Online Help.  Open the help on the Continuum workstation and search for "Defining a Custom ABA String Format"          

Issue TAC ToolPack plug-ins (eg. STR 350 plug-in) do not show up Product Line TAC Vista Environment TAC Vista 5.1.4, 5.1.5, 5.1.6 Windows 7, Windows Server 2008, Visio 2010 TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in STR 350 Plug-in Cause Not all plug-ins in the TAC ToolPack can run on Windows 7, Windows 2008 or Visio 2010. Resolution When installing TAC ToolPack on these operating systems only the supported plug-ins will be installed: TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in If the desired plug-in is missing, configuration of your controller will need to be done manually in NL220, Lonmaker, or Vista. Read details about manually setup STR 350/351 in STR 350/351 manually setup without plug-in (nciOption1 and nciOption2).

Issue Unable to connect to the ENC using its IP address. The ENC Ethernet port LED's appear to indicate normal operation. Product Line TAC IA Series Environment I/A Series Enterprise Network Controller Cause The ENC DHCP function was enabled by mistake on a system that does not have a DHCP server. The ENC when booted up will try to get an IP address from a DHCP server which does not exist and the ENC may not have a valid IP address. Resolution Connect to the ENC via its serial shell and perform the following procedure. Refer to Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal for details on connecting to the ENC serial shell. 1. Connect to the ENC serial shell using Windows HyperTerminal. Allow the ENC to boot up completely and you should see output messages similar to the following.   JACE 4/5 IPL Version 6.40 ECC to stop Autobooting on-board nand james startup version 6.41 launching devc waiting for /dev/ser1 creating symlink for /dev/serconsole Welcome to QNX Neutrino 6.4 on the ppc824x(james) starting /ffs0 filesystem ETFS_FS_2048 fs-etfs-jace2048: Truncating fid 0x2f from 337920 to 316718 bytes fs-etfs-jace2048: Truncating fid 0x64 from 5488640 to 13 bytes fs-etfs-jace2048: Truncating fid 0x1ce from 4096 to 0 bytes i2c: Using 100Mhz freq divider Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:20:96:08:ee:06 media: Ethernet none status: no carrier inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- bad battery detected, A/C power test will not function MESSAGE [12:38:25 19-Jun-2013] [tid=1] niagarad: starting, baja_home=/niagara MESSAGE [12:38:25 19-Jun-2013] [tid=1] webserver: web server started [tid = 4] MESSAGE [12:38:25 19-Jun-2013] [tid=1] app registry: station registry starting MESSAGE [12:38:25 19-Jun-2013] [tid=7] engine watchdog: station TEST0817_TIM watchdog thread started [tid = 8] MESSAGE [12:38:25 19-Jun-2013] [tid=7] station: station TEST0817_TIM starting login: tac Password: [2J [H J404 System Shell ------------------------------------------------------------------------- hostid: Qnx-J404-0000-15C8-14F9 serial number: 584966 build version: 2.5.25 build date: built on 2011-04-04 16:47:24 system time: Wed Jun 19 12:38:43 STD 2013 niagara daemon port: 3011 en0: inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- 1. Update System Time 2. Update Network Settings 3. Ping Host 4. Enable/Disable Ftp 5. Enable/Disable Telnet 6. Update Platform Account 7. Reboot L. Logout   2. Select option 2 for update the network settings. 3. Press 'enter' (enter leaves the field at the original setting) for each field until the 'IP address (clear to use DHCP)' field. 4. Type in the required IP address here and press enter. This will disable the ENC DHCP function. 5. Key in the subnet mask at the next line and select 'n' when prompted to use IPv6. 6. Press enter until you are prompted to save the changes.      [2J [HJACE Network Configuration Utility Enter new value, '.' to clear the field or '' to keep existing value Hostname : Domain <> : Primary DNS Server <> : Secondary DNS Server <> : Route <192.168.10.1> : Primary IPv6 DNS Server <> : Secondary IPv6 DNS Server <> : IPv6 Route <> : NET1 Ethernet interface IP address (clear to use DHCP) <> : 192.168.1.141 Subnet mask <> : 255.255.255.0 Enable IPv6 addressing on this adapter? (Y/n) : n Confirm new configuration Hostname : localhost Domain : Default Gateway : 192.168.10.1 Primary DNS : Secondary DNS : Default IPv6 Gateway : Primary IPv6 DNS : Secondary IPv6 DNS : NET1 settings: IP Address : 192.168.1.141 Subnet Mask : 255.255.255.0 IPv6 Addressing disabled Save these settings? (Y/n) : y    7. Reboot the ENC and connect to the ENC using Workbench. 

Issue Backup and Restore Process for WebReports Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Server 2008 R2 Cause Need detailed backup process Resolution Refer to Online Help Topic for details Backing Up the WebReports Database  On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect.   Note: When using a remote computer to connect to the Report Server SQL database, the Windows Accounts must exist on both machines and have administrative rights for the SQL database otherwise a successful backup will not occur.  In this instance, it is recommended to use the SysAdmin 'sa' login / password details when connecting in remotely.   Expand the Databases folder. Right-click StruxureWareReportsDB, point to Tasks, then click Back Up. Under Destination, click Add. Click OK. In the Destination on disk box, select the backup destination. Click OK. Click OK.   Restoring the WebReports Database Ensure the Enterprise Server is up and running with the correct database.  Stop the SQL Server Reporting Services and WebReports Agent (if installed).  Note: If moving the WebReports Database it is recommended to restore the database then Install WebReports.  Then when Installing WebReports select Upgrade existing (as shown) and NOT New database  Restore the WebReports database to recover reports data from backup.  This will include any Dashboard reports saved. On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect. Expand the Databases folder. Right-click StruxureWareReportsDB and select Tasks, then select Restore, then select Database. In the Restore Database dialog box, select the database set(s) that you want to restore. Click OK. Click OK. If not already installed now complete the installation of WebReports 

Issue Is there a way to translate Cyberstation to a language other than English and use different SQL collation sequences and code page? Product Line Andover Continuum Environment Continuum Cyberstation Cause Standard Cyberstation installation installs the SQL using Code Page 850 1.x Strict compatibility. Resolution The link below is to the Language Translation support guides. These provide detail on how to translate the Continuum Cyberstation user interface to a different language. It also details in Chapter 3 how to use a different SQL sort order. This would allow the use of different character sets for use in personal names Language Translation Support Guide V1.81 Language Translation Support Guide V1.94 Also, there is an additional Continuum Language Support document available in MSWord format Here. For Arabic specifically, additional MSWord Document Here.  There are freelancers that can be of assistance to help with your site. Upwork is a site with potentially low-cost translators. NOTE - No testing has been done with Continuum v2.0 due to a lack of demand for translation See Andover Continuum v2.0 Language Translation

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (701) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Vista, I/NET, LON, MicroNet, ModBus Xenta Servers (Xenta 5XX/7XX/913) Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.4 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Xenta 511 X         C   X Xenta 527 X X     X C   X Xenta 527-NPR   X       S     Xenta 555 X   X     C   X Xenta701 X         ST 10   Xenta 711 X         C 10 X Xenta 721 X         ST 20 X Xenta 731 X X X   X C 20 X Xenta 913 *** X X   X X S     * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service.  NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.5 major features please read Xenta Server after version 5.1.5 (5.1.5 included) Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue A replacement for VisiView is required. Environment Satchnet VisiView Cause The VisiView software is now obsolete. Resolution VisiView can be replaced using a SmartStruxure Automation Server or TAC Xenta 555 Web server. Both the SmartStruxure Automation Server and the Xenta 555 provide web interfaces so that the customer can view their HVAC equipment graphically using an appropriate Web browser. Both the SmartStruxure Automation Server and TAC Xenta 555 Web server communicates with either IAC or Micronet controllers. Further information on the Micronet Transition to SmartStruxure can be found in PA-00228 The Xenta 555 is programmed using TAC Xbuilder, which allows data to be presented in a graphical format. Further information on the Xenta 555 can be found here.

Issue The Xenta 913 supports several different BACnet object types but does not support all object types. Product Line TAC INET, TAC Vista Environment Xenta 913 BACnet Vista I/NET Cause The Xenta 913 is only a gateway device and is not native BACnet and thus does not support all BACnet object types. Resolution The BACnet specification outlines 49 different object types. Objects include physical points, processes and even internal operations. Most BACnet devices, including BACnet certified devices, do not support all of the object types since some of the object types are particular to specific industries and several are not commonly used. The Xenta 913 controller supports the following object types: Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value Multi-state Input Multi-state Output Multi-state Value The following BACnet object types are unsupported by the Xenta 913: Access Credential Access Door Access Point Access Rights Access User Access Zone Accumulator Averaging Bit String Value Calendar Character String Value Command Credential Data Input Date Pattern Value Date Value Date Time Pattern Value Date Time Value Device Event Enrollment Event Log File Global Group Group Integer Value Large Analog Value Life Safety Point Life Safety Zone Load Control Loop Network Security Notification Class Octet String Value Positive Integer Value Program Pulse Converter Schedule Structured-View Time Pattern Value Time Value Trend Log Trend Log Multiple           Note that there is some confusion among object types. For example, while it is possible to have a Life Safety point that is a binary output, this is not the same thing as the standard Binary Output object type and the two points are not interoperable.

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.

Issue Using Xenta Controllers with a Tridium Jace Product Line TAC Vista, TAC IA Series Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Tridium AX / N4 Jace Cause By default, the Tridium Jace acts as a network manager which will disrupt controller addresses, SNVT bindings, and Group bindings previously set up in LonMaker. Resolution  To disable this feature provide these steps to a Tridium Integrator: Use Niagara WorkBench Connect to Jace Under the Services Folder, find "LonNetwork" Go to  "Local Lon Device" Set the "External Config" property to "true" Hit "Save"  

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc.  Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue Using I/NET trends in StruxureWare Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment I/NET StruxureWare Building Operation 1.3 Cause Ideally trends should reside in the controller rather than at the sever level as this prevents sample data loss due to communication errors. Resolution Before you begin, ensure that all I/NET trends are set up correctly and trend data is visible. For assistance with this see Setting Up I/NET Seven Trends. Ensure that messaging is working so that SmartStruxure receives I/NET messages, and ensure that all controls have points to be trended, are already added to the I/NET Interface. NOTE: For the Enterprise Server level integration, the I/NET Trend Object must be configured as a Seven Trend. For the Automation Server level integration, this is not required, therefore skip to step 3. In I/NET, Select Trends>Data Inquiry/Edit View the trend you wish to see in SmartStruxure and verify that it has data. Open StruxureWare Workstation Refresh the system tree and upload any I/NET controllers that do not show a green dot. Right click on the I/NET Interface and select New>Value When the "Create Object" Window appears, name the value and click "Create" The Value will appear in the I/NET Interface Right Click on the newly created Value and select "Properties" Locate the "Point to Trend" Field Click on the "..." and select the point object you wish to trend Click the select button Verify that the Point to Trend field is correct and Click OK Wait enough time for several samples to populate. Right click on the Value object in the I/NET interface and select View>Trend log lists>New Trend log list The New Trend log List should open and values should visible. The Trend Value object under the I/NET interface will now function the same as a trend object in StruxureWare. If you wish for the I/NET trend to show up as part of an Energy Report, you will need to Ensure that the Extended Trend Log is referenced in a Meter's "Meter Trend Log" property NOTE: For the Enterprise Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven Trend to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must have a current save file The Controller with the I/NET point being trended must be online The I/NET workstation located on the Enterprise Server must be masked to receive data from the trend log on the controller to the Seven Trends Definition For the Automation Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven trend extension to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must be online The I/NET trend object and point object must have some level of masking so that the data will leave the controller.

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 Download Service fails to start after an upgrade to v.4.2.251 Product Line EcoStruxure Security Expert Environment Security Expert Server v4.2.251 Cause Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501; (VC++ 2013 Redist v12.0.0.30501.0) is not installed. This package is a pre-requisite to installing Security Expert v4.2.251. It was needed for extending the Suprema integration but did not get added to the installer for that version. This is now packed with the Security Expert installer. Resolution There are two options to resolve this; 1. [Preferred Option] Install the current release of Security Expert. This required package is now included in all new versions of the Security Expert installation file. 2. Install the package from Microsoft before installing Security Expert 4.2.251. Locate the file on the Microsoft site https://www.microsoft.com/en-nz/download/details.aspx?id=40784. Download and install vcredist_x86.exe, the 32 bit version (because Security Expert is a 32 bit application), before performing the upgrade.

Issue How to enable Continuum site for use with Endura DVRs and cameras. Product Line Andover Continuum, Pelco Environment Continuum V1.91 and above Pelco Endura DVR See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, Cause Want to enable Continuum for use with Endura but unsure which security keys support the addition of the option and what the option provides. Resolution Why is this option required? The Endura -E option for Continuum security keys is required to be able to: Configure VideoServer objects in Continuum to use Endura DVRs. Use VideoAdministrator and VideoMonitor to configure and view Endura cameras. It is not required to be able to configure and view cameras from DigitalSentry DVR's or to view Endura cameras using VideoLayout objects that have already been configured. Which Workstations can have the option added? SU and LAN Cyberstation security keys can be enabled with the Endura -E option. This option cannot be added to the WEBC key for WebClient Servers. If configuring Endura cameras is required, a Cyberstation with the -E option must be used. WebClient browser users are able to use the VideoLayout to view DigitalSentry and Endura cameras. The Endura option is only available through the upgrade process through Repairs. There is no part number to specify to enable Endura at the time of ordering the security key. Once you have the serial number of the key, contact Repairs below. Email:  upgrades.continuum@schneider-electric.com How to tell if the option is enabled? If the system is operating normally (not in Demo Mode), open up a Video Server object. If the key is video enabled it should look like this: If it is not enabled, the Pelco Endura option is not available: