Issue Need to perform a damper calibration using eCT Product Line EcoStruxure Building Operation Environment Building Operation eCommissioning Tool (eCT) Cause There is no documentation on how to perform this via eCT. Resolution Ensure your MP-V is not in a hosted state within EBO. Connect to your MP-V device using Windows 10, iOS, or Android via Bluetooth, WiFi, or ethernet connection Expand the menu in the top left corner and select "Browse Objects"  Scroll down until you find the DamperCommand object, select it and tap/click OK  In the Initiate damper calibration Property ID, select False and type in True then click Save

Issue While trying to login to either WorkStation or WebStation, or during the startup of the Enterprise Server, an error "Error -25: License server system does not support this version of this feature." appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 2.0.x or later Building Operation Webstation version 2.0.x or later Building Operation Software Administrator version 2.0.x or later Cause The activated license is not at an appropriate version for the corresponding software. The licenses activated in the EBO License Administrator need to be at a version greater than or equal to the version of the Building Operation software being used.  Resolution 1. Workstation - If the Workstation license activated in License Administrator is at Version 1, this license will need to be upgraded to be compatible for any system EBO 2.0 and beyond. To do this, simply notate the Entitlement ID and then return the Workstation License. Once returned, reactivate the license from the previously recorded Entitlement ID. This will upgrade the 1.X License to be used with newer systems. 2. Enterprise Server - If the error is received on an ES, verify that all ES licenses are in place. If the system was upgraded, it is necessary for all previous versions of ES/AS licenses to remain activated in the License Administrator. 

Issue A message that can be intercepted by a guard at a monitoring station. When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries made under duress conditions. For example, if an employee is being forced to provide an unauthorized individual access into a secure area, the employee can substitute the final digit of their PIN with a digit that indicates a duress condition. In this case, I/NET will allow access but will also silently generate a duress message that can be intercepted by a guard at a monitoring station. Product Line TAC INET Environment TAC I/NET Seven with Access Control using a pin pad. Cause Duress entrance causes a security guard to be notified that there is a situation to be resolved. Resolution Duress detection is active anytime a door is operating in a mode that requires the entry of a PIN. I/NET supports selectable duress schemes that you can assign on a per-tenant basis. The following duress schemes are available: Default — I/NET's default duress scheme detects when an individual substitutes their PIN with a substitute number. The default duress last pin is 9. The duress code is the user's PIN number with the last digit changed. For example, 12345 becomes 12349. Add n (where n is a value from 1 to 9) — I/NET detects when an individual substitutes a digit of their PIN with a predetermined digit. For more information on this sensitive topic, contact Product Support to begin a conversation about Duress Notification in I/NET.

Issue When importing Lon variables from Excel, all variables are created as Inputs, even though the "Direction" column in the Excel file says "Output".   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A defect creates all Lon variables as inputs even if the variable is assigned direction as output. Resolution  Create Lon variables with output direction manually.

Issue Is it possible to determine when a Continuum Security Key was removed from a Continuum Cyberstation? Product Line Andover Continuum Environment Continuum Cyberstation Continuum Security Key Cause A Security Key is removed from the Continuum Cyberstation. Being able to pinpoint when it was removed may help in investigating who has taken the key. Resolution It is not possible to determine when the key was physically removed from the PC with the Continuum or Windows Logs. There is no information in the Continuum Error Logs on this removal and in the Windows logs, the disconnect/connect messages for USB devices don't indicate what the device actually is.

Issue Using an EP1501 as a controller and unable to add reader one. Product Line Access Expert Environment Access Expert Server 2012R2 and above Cause Using an EP1501 as a controller as well as a card reader controller. Resolution To resolve the issue, please follow the steps listed: Wire the RS-485 bus to reader port 1, Clock and Data Wire the reader being used on port 2 When programming the reader on the device, it needs to be added as Reader 1 The Door Address needs to be set as 0 as well

Issue When using Advanced Display and logging in to Webstation, it startups in kiosk mode with limited functionality. Example:   Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display Cause When running Webstation in Advanced Display it is by default started in kiosk mode Resolution Open SmartX HMI Kiosk in Advanced Display In "Webstation setup" delete the part ?kiosk# Example: https://192.168.42.116/?kiosk#  Webstation be started in kiosk mode https://192.168.42.116/  Webstation will start normally

Issue Need to replace discontinued Erie actuator model AH13U020-Z but unsure if the current model AH13U020 can be used as a direct replacement Product Line Field Devices Environment Erie actuators Cause Unable to find any documentation for the AH13U020-Z Resolution The '-Z' models for the Erie actuators indicates it is the Made in China version of the actuator. We have since stopped manufacturing the actuator in China.  The AH13U020 can be used to replace the AH13U020-Z

Issue Controller fails to backup to flash. See error message "Unable to backup objects to flash ..." ACCStatusFlash variable should be ACCFlashValid not ACCFlashFailure Product Line Andover Continuum Environment Continuum Controllers NetController 2, bCX9640, bCX4040 Cause A Program or Function in the Controller is corrupt and cannot be compiled or is blank and does not have any Plain English code in it. Resolution Go to the config page (Controller Configuration) Clear database backup Fix up or delete the offending programs Re-attempt to save the database to flash

Issue Cannot delete personnel. A personnel object will not be deleted due to distribution failures. Product Line Andover Continuum Environment Cyberstation Cause If a person has an area assigned and the controller or door has been deleted, the distribution to remove that person from that controller cannot be accomplished successfully. Resolution First, remove all areas from the personnel object before deleting the object. This is by design. The reasoning behind this is to allow a person to be removed from the network before disabling access. Other things to check if distributions are failing: If running MSDE or SQL2000: Check to make sure the Agent is running. Check for duplicate tables and make sure they're all DBO Check Security Continuum DB make sure there is only one DBO linked to Andover97. If using SQL 2005: Look at the jobs under the Agent. They trigger every 5 minutes and are responsible for the task of deleting the personnel objects marked for deletion. At times there are errors for why the jobs are not running properly. If the above steps do not correct the issue then it could be an issue with the database. The PSS engineer may request the database to perform analysis to reproduce what is happening and offer suggestions to correct the problem.

Issue An error message is displayed when trying to save changes to a Programmable Xenta in Menta Editor. The error message is: Tam32 Save Error Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (E) Error message trying to save changes in Menta Editor Product Line EcoStruxure Building Operation Environment Building Operation Workstation 3.0.2 or earlier Xenta 281 Xenta 301 Xenta 401 Cause A defect in Menta Editor causes this error to be displayed when a SNVT name in the Menta application is identical to the programmable Xenta device name.  An example of this is shown below: Resolution This problem has been fixed in Hotfix 3.0.2.2500 and the fix is included in version 3.1. For earlier versions there are two ways to resolve this problem; Either a) rename the Xenta device, or b) rename the SNVT. a) Renaming the Xenta device In Workstation right click the Xenta device and choose Rename Click OK Now you can edit the Xenta in Menta Editor without getting the error message b) Renaming the SNVT Right click the Xenta device and choose Edit In Menta Editor double click the block with the SNVT binding to edit the block Click the Bind... button to edit the binding Change the name, click OK to close the dialogs and Save the changes

Issue MNB controllers do not have internal trend log capability.  Product Line TAC IA Series Environment I/A Series MNB controllers I/A Series R2/G3/N4 Jace Building Operation Automation Server Cause The MNB family of controllers does not have internal trend log capability.  To log these internal calculated values, a different method must be used to allow the values to be logged in an EBO Automation Server or a Jace Resolution The BACnet objects "Analog Monitor" and "Binary Monitor" in the Workplace Tech tool may be added to an MNB controller application program. When connected to internal data values in the application, the values can be uploaded to an EBO Automation Server or a Jace for trend logging.

Issue Alarm code, configuration code passwords for DC1100 and DC1400 Product Line Field Devices Environment DC1100 controller DC1400 controller Cause Configuration Resolution Passwords are: 0112 for configuration mode 0402 for fast run mode

Issue Configuring a SetPoint in EcoStruxure Building Operation so that the set value of the SetPoint is retained after a Warm or a Cold Start rather than defaulting to zero. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The value retention configuration is not held in the initial properties page of the Analogue Value when used as a SetPoint. Resolution Navigate to the actual value within the properties page of the Analogue Value. On the right hand side of the GUI there is a Configure button. Pressing on this button then takes the user to a sub menu where the Retain level option can be enabled. Once enabled it is then possible to decide whether the SetPoint needs to retain its value under a Warm Start or a Cold Start condition.

Issue Vista webstation - Error message in FIPS-compliant systems first time the logging screen is entered and red X instead of values in TGML pictures Error message in FIPS-compliant systems when Windows Communication Foundation is used to serialize generic types: “This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms” Red X instead of values EcoStruxure Building Operation registration WorkStation Error Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Webstation Cause System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing This security setting determines if the Transport Layer Security/Secure Sockets Layer (TL/SS) Security Provider supports only the TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher suite. In effect, this means that the provider only supports the Transport Layer Security (TLS) protocol as a client and as a server (if applicable). It uses only the Triple DES encryption algorithm for the TLS traffic encryption, only the Rivest, Shamir, and Adleman (RSA) public key algorithm for the TLS key exchange and authentication, and only the Secure Hashing Algorithm 1 (SHA-1) for the TLS hashing requirements. For Encrypting File System Service (EFS), it supports only the Triple Data Encryption Standard (DES) encryption algorithm for encrypting file data supported by the NTFS file system. By default, EFS uses the Advanced Encryption Standard (AES) algorithm with a 256-bit key in the Windows Server 2003 family and DESX algorithm in Windows XP for encrypting file data. For information about EFS, see Encrypting File System. NOTE - The same errors can occur in EcoStruxure Building Operation when registering. Resolution Go to Local Security Settings Security Settings > Local Policies > Security Options System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing = Make sure its disabled to get to local security you can go to 1. go to start 2. Go to run 3. enter secpol.msc 4. press enter NOTE - The same errors can occur in EcoStruxure Building Operation when registering. The Resolution is the same

Issue Alarms about BACnet devices with duplicate names These are not required on the site Product Line EcoStruxure Building Operation Environment Third Party BACnet Devices Building Operation Enterprise Server Cause In EBO, BACnet device name uniqueness enforcement has been removed but an alarm is sent regardless to alert of the problem. Resolution Disable the alarm if it is not require in the alarm view. This is achieved by right clicking on the alarm in the Alarm Pane and 'Disable Alarm'

Issue LON Network - Cable Transient Suppression Product Line EcoStruxure Building OperationTAC IA Series, TAC Vista Environment LON networks that extend beyond the walls of a single building Cause Surge arrestors dissipate transient energy before the cable can provide a low resistance path to the building ground, preventing potential electrical damage. Resolution Click here to download the white paper on this topic: Cable Transient Suppression It is recommended that a Transient Suppression protection device be installed on the LON communications cable at any point where the cable enters or exits the building. The LON is frequently used to connect a collection of controllers in one building with a collection of controllers in one or more other buildings in a campus. The LON may also extend outside the protection of an office building when servicing communications to roof-top equipment and/or outside monitoring equipment. At any location where the LON cable penetrates and extends outside the building compartment, it is recommended that a gas discharge type lightning arrestor be installed across the LON conductor pair and earth ground as shown below. This should be positioned as close as possible to the wall penetration location. The objective is to keep the cable distance as short as possible before the cable suppression is provided. It is important that a heavy gauge earth ground connection be provided to the gas discharge protector with as short a length as possible. Here we want to dissipate the transient energy as soon as possible before the cable extends on into the facility and provide a low resistance path to the building ground. SA2-U8 Surge Arrestor TAC provides a Model SA2-U8 Surge Arrestor which can be used for this purpose. This SA2-U8 device is a gas discharge arrestor packaged in a small DIN rail mountable enclosure. The SA2-U8 is UL864 listed and is the only device that can be used on TAC UL864 listed system. It must be installed on the LON cable at any entry/exit locations. Other Gas Discharge Suppressors On non-UL864 systems, the SA2-U8 may also be used, or the installer may use any one of a number of available 90V gas discharge tube devices. These are typically tubular shaped components and since you need two tubes (one for each of the two LON conductors) a dual element three lead discharge tube is recommended. The device’s leads may be attached to a standard screw terminal block and mounted in most any size electrical box. A collection of some of the suitable gas discharge devices that could be used is as follows: Manufacturer Part Number Bourns 2026-09-C Epcos B88069X8440B202 Citel BTS-90 SRC Devices PMT-090-14   There are other acceptable part numbers available from each of these manufacturers with variations provided in the lead configuration and lengths while maintaining the same 90V protection rating. Devices To Avoid It is not recommended that you use any semiconductor type (Transzorb / TVS / Diode) protection devices. Their higher speed and lower clamping voltage characteristics is not necessary with the inherent protection offered by the FTT-10 and FT-X1 LON transceivers. Such semiconductor based transient suppression devices frequently add some undesirable capacitance to the network which impedes communication performance and most inject signal clamping at voltage levels much lower than necessary or desirable for the Free Topology FTT-10 and FT-X1 based LON networks. The common mode noise immunity of the FTT LON should be much better than that provided by the typical RS485 network. This should provide more tolerance for electrically noisy environments. However, it has been observed that some semiconductor based network protection units have been used that can drastically degrade communications performance. One such device is the Model 91287 from Atlantic Scientific Corp. which was identified by the manufacturer as a LON System protector. This device clamps the signal at one diode drop below ground level which virtually destroys the LON’s common mode noise tolerance. The presence of one of these devices has been found to be the cause of communications problems in a system operating is an electrically noisy environment. This type of communications impairment may be encountered immediately. In other instances, LON retries may cover the problem and the system may operate for extended period of time before environmental or equipment changes raise noise levels above the tolerable threshold. This threshold is now much worse than RS485 networks. This device, and any similar, should be avoided on any LON systems.

Issue Workstation Pro License fails to allow running of v2.0 or v3.x EcoStruxure WorkStation following an upgrade Product Line EcoStruxure Building Operation Environment WorkStation Licensing Cause Workstation Pro License SXWSWWORK00002 (SW-STATION-PRO-0) is the same for v1.x and v2.x, so that WorkStation Pro should continue to operate after an upgrade. However, there was a License upgrade/change at v1.7 (from v1 to v2) and if the License was registered before this the version remains at v1 and this will not run v2.x WorkStation Resolution The WorkStation Pro License needs to be returned, then re-installed using the online Licensing system.   Before License is returned   After license is returned  The process to return a license can be found in Webhelp.

Issue How do you add a "CAUSE" for electronic signature? Product Line TAC Vista Environment TAC Vista 5.1.x Cause The "Cause" for electronic signature is located in the $System object. Resolution Open the $System object located in the root folder in Workstation Open the tab "Cause" Add the "Cause"

Issue Door needs to be set to SiteMode+CardMode for weekdays and SiteMode+CardMode+PinMode for weekends. Product Line Andover Continuum Environment NetController (CX9900 , CX9940 , CX9702 , ACCX5740 , ACX5730) InfinetController (ACX780, ACX781) Cause Customers want to have a PE program that changes the door mode to be more secured for the weekend according the building schedule. Resolution In the PE program ; Set DoorName\EntryNormMode = 3 ' Set the door mode to SiteMode+CardMode for weekdays Set DoorName\EntryNormMode = 11 ' Set the door mode to SiteMode+CardMode+PinMode for weekends. The values for the different modes are: 1 = SiteMode 2 = CardMode 4 = GeneralMode 8 = PINMode 16 = ScheduleMode The individual values are added together to obtain the desired mode. As seen above, setting the mode to 3 makes the door validate site + card. It is recommended that both the normal and nocomm modes be set (EntryNormMode, EntryNoCommMode) For a dual reader door, use the corresponding ExitNormMode and ExitNoCommMode.