Building Automation Knowledge Base

Issue When trying to launch the Energy Expert Integration Utility (formerly the Power Manger Integration Utility) the following error is given. Product Line EcoStruxure Building Operation Environment Energy Expert Power Manager for SmartStruxure Integration Utility Cause This error message can be the result of different causes. Check the IntegrationUtility.log file found in the same location as the Integration Utility for more information.  Example of Integration Utility Log error: ERROR: Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "IntegrationUtility.Shell", name = "(none)". Exception occurred while: Calling constructor IntegrationUtility.Pme.Services.PmeUserDataStore(). Exception is: ConfigurationProviderException - Could not locate a connection string provider. Resolution NOTE: If you have already downloaded the software, you must first delete the folder you unzipped before doing the process below.  Unblock the Zip file The first thing that MUST be done after downloading the Power Manager software from the Exchange is to unblock the zip file. Right click on the zip file and select Properties. Under the General tab, towards the bottom click Unblock. Click Apply and close the properties window.  You can now unzip the software and use it as normal.  Compatible .Net Framework Versions Different versions of the Power Manager / Energy Expert Integration Utility require certain versions of Microsoft .Net Framework. Note: Having multiple versions of .Net Framework installed may cause issues.    Pease refer to the Energy Expert Compatibility Matrix for further detail.

Issue After installing SigmaX version 5.0 or later, when running the software an error message reports a missing DLL. Product Line Satchwell Sigma Environment SigmaX version 5.0x, 6.0x and 7.0x Cause System Path variable is missing C:\Sigma\Bin in Environment Variables Resolution Make the following modification to the PC's System Properties. Note: This addition is only required on machines running SigmaX.   For Windows XP and Windows 7 Right click the My Computer icon on the desktop and select Properties Choose the Advanced tab and select the Environment Variables button From the System Variables section, highlight Path and select Edit The statement ‘;C:\Sigma\Bin’ must be added to the end of the Variable value line For Windows 10 In the search bar type and type 'environment' and go to 'edit the System Enviroment Variables' Bottom right go to Enviroment Variables In the bottom window 'System variables', find 'Path' and double click In the 'Edit environment variable pane - create a 'New' variable and add in c:\sigma\bin

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.  

Issue In the Niagara G3 ASD Device Manager, MicroNet 2000 devices can not be discovered. Product Line TAC IA Series Environment I/A Series G3 ENC-410 or ENC-520 MN-ASDI integrator with attached MN-FLO / MN-FLO3T / MN-HPFC devices Cause It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them. Resolution When using the ASD Device Manager to discover MicroNet 2000 devices (MN-ASDI integrators on the ASD bus, and the controllers on the U-buses under the integrators), set the Start Address and End Address in the range of 1 -31. For example, assume there is an MN-ASDI with DIP switch address = 2, and on the U-Bus under the integrator there is an MN-HPFC with DIP switch address = 3. In the Discovery Filter, set the Discover Mn2k flag= true, Start Address = 1, and End Address = 31. The Device Manager will put a MnHPFC_35 object and a MnGen_32 object in the upper pane. The ASD Device Manager assigned an ASD device address = 32 to MN-ASDI, and an ASD device address of 32+3 = 35 to the MN-HPFC. It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them, and then assigns an ASD device address in the range of 32 – 224 to the integrators, and in the range of 1-254 to the MN-FLOs and MN-HPFCs.

Issue Creating new user roles and knowing the access that is needed for it to become active. Product Line Access Expert Environment Cloud or Premise Installations V2 Win 7 Win 8 Server 2012 Server 2014 Cause Knowing what the role the user is playing would determine what selections need to be activated for them. Resolution To achieve this the following steps need to be followed: Open up General Configuration Select the Roles icon Click on the tab for New Role (everything is blank by default) Name and configure accordingly Check all tabs to make sure everything is Viewable and Editable Save and close Now this role can be selected for any user once created

Issue What binding methods can be used and how is the data transferred when binding objects between two b3  or Infinet controllers? Product Line EcoStruxure Building Operation Environment Automation Server, AS, ASP, ASB BACnet b3 Infinet controllers i2 Cause When binding objects between b3(infinet) devices/controllers, the type of Objects being bound will effect the properties of the binding. Resolution When binding between two Controllers, several methods can be used: Value/Point to Value/Point - The data goes via the Automation Server and the speed/rate is set in the Transfer Window, thus more bandwidth used and communication is lost if the Automation Server fails. Script to Value/Point - The data goes direct using BACnet COV subscriptions, thus less bandwidth is used. NOTE - The BACnet b3 and Infinet controllers, have no facility for direct binding of Value/Point to Value/Point, thus if a direct binding is made within the same controller, an EBO binding will be created. This will cause data packets on the MSTP or Infinet network. This should usually be avoided, as it can easily overwhelm the network. Bindings should usually be made from scripts. See Infinet under the hood for more details on Infinet setup

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. If the device is new out of the box, or has attempted recovery after a format command, please see Default IP address following Xenta Server "format" command is different than from factory for the known default IP addressing. Resolution Preparation: You need to have an RS-232 serial cable (TAC Xenta Programming Serial Kit 0-073-0920-0). Plug the RS-232 cable in to the RS-232 B port. The RS-232 B port is the second left port at the front. Then connect the other end to the computer. Configuration steps: Go to Start > All Programs > Accessories > Communications > HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. Type the appropriate information for DHCP, IP-address, Subnet mask, Default gateway, DNS, Website name, Domain name, and Host name. Type “yes” for “Do you want to restart the IP interface”. Quit HyperTerminal when the restart is finished. See [Video] Setting the IP address of a Xenta 5/7/9xx through serial communication to watch a video of this process.

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue Preparing LonWorks Configurations for Upgrade You use this procedure when you want to prepare LonWorks configurations for a version 1.5.x upgrade, a version 1.6.x upgrade, or a version 1.8.x upgrade to a final 1.9.X or Higher version. WorkStation ONLY hotfixes are needed to Prepare the LonWorks configuration in order to upgrade to an SBO system 1.9.X or higher. Links to locating hotfixes on Exchange are needed. Product Line EcoStruxure Building Operation Environment SBO Workstation Hotfix Only v1.5.0.17121 SBO Workstation Hotfix Only v1.6.2.1220 SBO Workstation Hotfix Only v1.7.2.11111 Note: AS-P HW.62 required for a LON system with a minimum SBO Software revision at 1.7.2.X Note: For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 -Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 Cause Difficulties experienced in locating these files on the Exchange. Resolution Prepare LonWorks Systems Running Version 1.5, 1.6, or 1.7. For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 - Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 SBO Workstation Hotfix v1.5.0.17121 - Contact Country Level PSS SBO Workstation Hotfix v1.6.2.1220 - Contact Country Level PSS SBO Workstation Hotfix v1.7.2.11111- Link To prepare LonWorks configurations for upgrade via the WorkStation Only Hotfix: Bring the system up to the base version within your respective site to SBO V1.5, 1.6.2, or 1.7.2. Then apply the WorkStation Only Hotfix from the list above to your respective version. 1. In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to prepare for the upgrade. 2. On the File menu, point to LonWorks and click Pre-upgrade LonWorks configuration. 3. Click Next. 4. Click Finish. NOTE: Any EcoStruxure BMS that is currently at 1.8 or higher can be upgraded directly to 3.1 with one added note,  if the system has LON it will need to go through the LonWorks Pre upgrade before you can upgrade to 1.9.X or HIGHER. If you are upgrading from a version that is older than 1.8, read the documentation that describes the upgrading process for the relevant version.

Issue Created a digital schedule in an Automation Server folder and it never changed the value of the digital value Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause Digital value bound to a digital schedule failed to change the value at a time when a scheduled event should have triggered. The probable cause is that the Automation Server time setting is incorrect. Resolution Configure Date and Time of an Automation Server: Click on the Automation Server in workstation Go to the Date & Time tab Set the proper time zone and save the changes. Use Network time synchronization or manually adjust the time if needed and save the changes again. Note that it might take some time before changes to the Date & Time settings affects the Automation Server system clock if you use Network time synchronization.

Issue What is the correct procedure for replacing a Continuum bCX 4040 controller Product Line Andover Continuum Environment CyberStation bCX 4040 Cause Considering both Continuum and BACnet 'sides' replacing a bCX4040 can seem a complicated process. Resolution Commission new/replacement bCX through its default webpage just as the as old bCX except for the BACnet Configurable Properties section. Set the BACnet Device ID = The same ID in the old bCX (serial number of controller by default) Set the BACnet Port Number UDP = same as old bCX (BAC0 by default) Set the BACnet Network ID UDP = same as old bCX (1 by default) Set the BACnet Network ID Comm2 = same as old bCX (2765 by default) Set the BACnet MAC ID Comm2 = Same as old bCX (0 by default) Set the BACnet MS/TP Enhanced Mode = Same as old bCX (TRUE by default) Set BACnet BBMD Enabled/Disabled = Same as old bCX (False by default) Bring the bCX online in Continuum Explorer, Select menu item Options | Send to Controller options Select "Reload attached objects, but not attached controllers" - select ok Verify the bCX Comm2 settings and baud rate speeds. In Continuum Explorer, right click on the bCX and perform a "send to controller" Verify points and communications.

Issue Is there a way to tell if the battery is bad in a controller? Product Line Andover Continuum Environment BCX - 4000, 4040, 9640 ACX5740, 5720 Netcontroller II 9680 Infinet II controllers B3 controllers Cause Determine if a battery is good Resolution Battery health is tricky to measure.  Open circuit voltage COULD look ok with a marginal battery.  The only sure way is to pull the power on the Netcontroller and see if it holds the data for our specified time.  Most sites will not want to take their controller down for that long. Take the battery out and measure it with a voltmeter, it should read not much lower than --- BCX and ACX model controllers  3.6V Netcontroller II, Infinet II and B3 controllers 2.7V BCX Spec Battery section: Replaceable, rechargeable battery. Provides 30 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. ACX Spec Battery section: Replaceable, rechargeable battery. Provides 7 days typical accumulated power failure backup of RAM memory All data stored in Flash on power loss. I2/B3 Coin type battery: The small coin battery in the i2 / b3 is rated 41mAH;  if you calculate based only on the SRAM and RTC current draw you get about 85 days.  Netcontroller II: The battery type here and SRAM are typical of infinet II controller battery life and will maintain backup of SRAM down to 2.7v. NOTE: Backup Flash is non-volatile memory and once written will hold unless manually cleared. SRAM is a part of memory that holds information as to where to start programs when power is re-applied to the controller in cases of main power loss. The problem is that battery life is highly dependant on number of charge / recharge cycles which is beyond our control.   You don't find the battery manufacturers giving such specs either.  Example:  The coin cells in our i2 / b3 have a shelf life "up to 10 years". Day to day use it is suggested that batteries should be replaced every 5 years.

Issue Should automatic updates be turned on for Continuum workstation? Are there certain known issues of updates that have caused problems with Continuum or Webclient? Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows 10 Windows XP  Windows Vista Windows Server 2003 Windows Server 2008 Cause Microsoft Windows has an automatic update feature and frequently releases updates which can potentially affect Cyberstation and Webclient Server. Resolution Automatic updates should not be turned on for a Continuum or Webclient workstation. The Continuum compatibility matrix indicates Windows Operating Systems, Windows Service packs, SQL Server, .Net and Internet Explorer versions that were tested by Quality Assurance at the time of product release. Continuum Quality Assurance does not perform regression testing where new Microsoft updates are tested with Continuum products released in the past. Product Support recommends setting Windows updates to one of the other two options to allow for testing of Microsoft updates: Additional details can be found at: http://support.microsoft.com/kb/306525 Download updates for me, but let me choose when to install them Notify me but don't automatically download or install them   There are several specific updates that have caused issues with Cyberstation or Webclient. This is not a comprehensive list. Occasionally updates will break certain features and we discover this from our internal testing or from reports from partners or branches. Here is a list of some updates that have caused issues. KB835732-  Pinpoint 1.52 crashes when installed on a machine and you are accessing graphics from a network share. If you remove the hotfix the problem goes away.  This is the same hotfix that caused the SmartHeap out of Memory errors that was fixed with SP5 for 1.6.  KB828741- IIS (Webclient) machines without this patch may receive “Unable to establish a link to the remote Infinity services” Webclient 1.73 - Any patches that will install .Net Framework 2.0 will cause problems with webclient 1.73 since we don’t start using .Net 2.0 until webclient 1.74. KB911280 - this update blocks the acc.scp script from setting controller to PPP mode. This will a cause a Cyberstation using RAS controllers to not allow a connection. It will authenticate, but not connect. KB928366 – Webclient machines that use .Net 1.1(Listed on the compatibility matrix) will receive the error "Could not connect to server cause; type missing for member of type object _context id'. Could not create acwppserverproxy."  when opening web pinpoint graphics.  Remove this hotfix or upgrade to webclient 1.74 or greater. KB929969 – this hotfix does not require a reboot by Microsoft, but can cause the Cyberstation install to fail, if the install is performed before rebooting after the installation of the hotfix. See the Technical bulletin. KB968749 - SQL Express install fails on XML6 SP2 See SQL Express install fails on MSXML 6.

Issue When reloading a Net Controller II you receive an OMS error. A send to database doesn't complete Environment Continuum 1.92 Windows XP NetController 1/II Cause Programming Busy Controller Resolution First Method: Go to off line editing. Export the programs and save them to the desktop. Delete the programs. Go onLine. Reload the controller. Go to off line editing. Import the programs for the saved export file. Go onLine. Reload the controller. Second Method: Go to off line editing. Web over to the NCII  http://ip-address Select  "Clear Database Backup" Commit Changes. Go Online. Reload the Controller. Note: At times if the reload is still not working and is failing on certain objects, reloading class by class allows the reload to go through. Delete programming half of the code at a time to find out what code is causing the issue by process of elimination. Use a laptop with wireshark installed and a hub and connect to the NC directly and try the reload or send to db and examine the capture. Replace the controller and see if it works, if so, the controller may need to be permanently replaced.

Issue Cannot Delete Personnel  Product Line Andover Continuum Environment Continuum  1.8X & 1.9X Windows XP Windows 2003 Server Continuum ACX5740 Microsoft SQL 2005 Cause Stored Procedure packPersonneldeletion failed to run Resolution Duplicate personnel.   Remove Areas from the personnel object. Delete duplicate personnel objects.

Issue Download a Menta application file to a Xenta controller using the Menta software tool and a directly connected serial RS-232 cable. Product Line TAC Vista Environment Menta Programming Tool Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cableguide Kableguide Programming Serial Kit 0-073-0920-0 Note: The Online command is not available for the Xenta Server 700 devices so the following procedures do not apply to these devices. Cause Throughout the engineering, installation and commissioning phases of a project it may be necessary to download directly to a Xenta programmable controller. Also, performing a directly connected Menta download may be necessary in order to fix certain issues. See the following: The device is applicationless, or is not associated with a program record. (Subsystem: NS, #5) Resolution Use Menta Setup program (this is found in the TAC Tools menu) to select the Com port that is being used. Do not change any other setting before clicking Close. Connect the RS-232 cable and Programming Adapter between the PC and the RS232 port on the TAC Xenta. (these are part of the TAC Xenta: Programming Serial Kit, part no. 0-073-0920-0 For more information about the cable and adaptor see Xenta Cable Guide , Adaptor A1 and Cable L1 or Schematic for the RS-232 cable used to direct download Menta applications and system files.)  Open the Menta file to be downloaded. Change to simulation mode in Menta by clicking Options menu and selecting Simulate. In the simulation mode click Online. In the Connecting to Device dialog click Download. In the Tam32 dialog choose whether or not to generate files for an OP menu. For more information regarding Menta direct downloads see the TAC Menta Technical Manual  Section 16.4.1. Notes: Network information containing network addresses and other properties for the Xenta device and it's I/O modules is included in the download. For more info about this network info see the TAC Menta Technical Manual listed above or for problems with downloading the network information see No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network!. If Menta returns Parser Errors during download see Menta Parser Errors. If Menta returns Unsupported I/O Warning during download see Reference to unsupported I/O Error in COD file - Error:13. If a serial connection is not available on the PC a USB adapter can be used. The appropriate version of the TAC Menta Engineering Tool can be downloaded from the Exchange

Issue Scenario 1 Attempting to log in to Web Client you are presented with an error message "Error - SOAP connection failed". SOAP-ERROR: Parsing Schema: can't import schema from   Scenario 2 Upon successfully logging in to Web Client you are presented with "Thank you for logging in" and then immediately presented with another message saying "Log out successful".   This continues in a circuit until it may allow you in but displays a partially populated page with no data showing. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client   Cause The option "Use HTTPS to communicate with SOAP service" was enabled in the Web Client Installation Wizard and antivirus was dropping the connection because of this.   Resolution Uninstall and re-install Web Client without the  "Use HTTPS to communicate with SOAP service" enabled or Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include. Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, fails with the below error being shown. Hardware details do not match Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The hardware details on record do not match the hardware details of the machine that is trying to be licensed. Resolution Contact support to have the hardware profile reset.

Issue Getting error message when reloading a Continuum controller: "Unable to reload attributes for \ \ . Reload Object's Type mismatches with object's in WCU Controller. Please Reload WCU Controller." Environment All Continuum controllers Cause The most common cause of this error message is duplicate alias names. For example, a controller object named "W Lobby" and a door object in the controller named "WLobby" (without the space) will have the same alias (WLobby). Resolution Rename one of the duplicate objects so that the alias is unique to the system.

Issue There is a need to know which card formats are supported by Continuum Product Line Andover Continuum Environment Access Control Continuum Cyberstation Cause There are many different card formats available from HID, so there is a need to know which formats that Continuum allows. Resolution Here are the formats that HID offers: 26-Bit Format: H10301 HID Proprietary 37-Bit Format: H10302 **** HID Proprietary 37-Bit Format with facility code: H10304 Corporate 1000 Formats HID Long Format Card Programming OEM Proprietary Formats (i.e. Continuum 37) 35-Bit Card Format Formats 1, 4, and 6 above are supported natively We support all the other formats (as custom cards) so long as the format does not exceed 64-bits and the format can be supplied or understood. (i.e. start/end bit of the site code, card number, etc.)   ****IMPORTANT Continuum supports a maximum of 32 bits for the Card Number field, any format above, such as the H10302, that defines more than 32 bits for Card Number field will only work if the card number range used at the site is between 1 and 4,294,967,295, any card number above 4,294,967,295 will NOT be read correctly by the controller. A possible solution for this limitation is to use the Extended Custom Cards feature supported ONLY in the ACX5720 and ACX5740 controllers.   More information about Extended Custom Cards https://community.se.com/t5/Building-Automation-Knowledge/Extended-Custom-Wiegand-features-available-for-ACX57xx/ta-p/1215