Building Automation Knowledge Base

Issue Esmi Transition tool stopped working after upgrading to SX-SOAP version 1.7.0.0 or higher Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Esmi Transition Tool SX-SOAP Cause The SOAP service no longer allows unencrypted communications over HTTP (port 8030) Instead use HTTPS over port 8040. Resolution 1. Open Esmikko Database transition tool 2. Go to the tab "Data Sync Service" the change the SOAP Server Address from http://localhost:8030/SecurityExpertSOAPService/service.svc to https://localhost:8040/SecurityExpertSOAPService/service.svc or https://SERVER_HOSTNAME:8040/SecurityExpertSOAPService/service.svc Note: bolded characters in the second line     3. Click on the button Create Data Sync Service Settings File The tool will stat working.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 For hardware failure or persistent issues, it is necessary to replace Security Expert hardware components Product Line EcoStruxure Security Expert Environment Security Expert SP-C or SP-C-Web controller Expanders (i.e. RDM2 or SP08) Card Readers Cause A hardware failure occurs or a persistent issue happens that requires steps to replace Security Expert hardware Resolution At times it's necessary to replace Security Expert hardware   Steps to replace Security Expert SP-C Controllers: 1. Determine if the original controller has encryption turned on If the failed controller was setup for encrypted communications with the Security Expert server, the newly installed replacement controller will not have the encryption keys to be able to decode the packets from the server. Attempting to bring it online will be unsuccessful. On the controller's Configuration tab press the Disable controller encryption, then Yes to confirm. A replacement controller will typically be unencrypted. As soon as it shows online you can decide if you want to encrypt it. If it was already encrypted in Security Expert before replacing it, you might need to hit the encryption button again to get it in sync. Note: It can be helpful to use the event server diagnostic. If you see messages including “unencrypted” set encryption on the controller and see if it comes online. 2. Disconnect the old controller from its networks unplug ethernet and RS-485 module network and other hardware 3. Replace the Serial Number in Security Expert In Security Expert, navigate to Sites | Controllers. Replace the Serial number of the old controller with that of the new one. 4. Disable encryption In the Configuration tab, click Disable controller encryption. 5. Default the Controller If the controller has been used on a different server, default the new controller. See the SP-C Installation manual for detailed steps on performing a controller default https://ecoxpert.se.com/search?documentUUID=b4fb1237-fd07-2ee5-d9ad-4324178c364c&title=SP-C%20Security%20Expert%20-%20Security%20Purpose%20Controller%20-%20Configuration%20Guide  6. Enter the event server settings on the controller Log in to the new controller's web interface. In Settings, enter the same IP settings, event server and ports as those of the old controller, then restart the controller. Note: Remember to remove the jumper used to default the controller 7. Connect the new controller to the networks and hardware The controller should come online in Security Expert if all the network settings, serial number and encryption settings are in sync. 8. Download the controller In Security Expert, right click on the controller record and select Force download. The controller should receive the download. 9. Enable encryption Once the controller is online, in the Configuration tab click Enable controller encryption in Security Expert if desired. Steps to replace Security Expert SP-C-Web Controllers: 1. Take a backup of the old SP-C Web controller Login to SP-C Web, In System | Backup controller This creates a .bak file prompting to save in a folder or in the downloads folder 2. Disconnect the old controller Unplug the controller from the ethernet network, the RS-485 module network and other hardware. 3. Register the new controller Log in to the new controller and register it in System | Licensing 4. Restore the previous backup taken Navigate to System | Backup and Choose File and browse to the previously created .bak file 5. Configure the IP settings In System | Settings, enter the same IP settings as those of the old controller, then restart the controller 6. Connect the new controller to the networks and hardware and Test Steps to replace Security Expert Expanders: 1. Disconnect the old expander from the RS-485 module network and any inputs, outputs or card readers. 2. Connect the new expander to the module network and hardware. 3. Set the new expander's address to the same as that of the old expander.  In Security Expert, navigate to Sites | Controllers, right-click the controller and select Module addressing.  In SP-C-WEB, use the Expanders Wizard. To address a keypad, power cycle it and then press [X], [Enter]. Enter the new address and press [Enter] to save. Note: Sometimes the old expander can remain in the module addressing window even after being physically disconnected. To free up the address, module update the expander record. This will fail, but the address should become available. 4. Module update the new expander. The expander should start operating normally using the programming from the original expander. Steps to replace Security Expert Card Readers: 1. Disconnect the old card reader from the reader port. 2. Connect the new card reader 3. Apply any Custom Configurations If the reader needs any custom configuration, apply it within two minutes of the reader starting up using the config card. 4. Wiegand and RS-485 readers should connect automatically For OSDP readers, put the card reader into installation mode, then send an OSDP install mode command to the reader expander. Test the replaced hardware to ensure the issue is resolved

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 It may be necessary to replace the Security Expert Server and/or the Security Expert Software Product Line EcoStruxure Security Expert Environment Security Expert Cause In case of upgrade, software issues or PC/Server hardware failure replacing the Security Expert Server may be needed Resolution 1. Hardware Reset If the server footprint changes, for example, the previous server’s hard drive or motherboard died, then a hardware reset will be required before the license can be used on the new server. Contact Schneider Electric Product Support to tell them that your server hardware profile will be changing and a hardware reset is needed. 2. Stop the Security Expert services Right-click on the service and select Stop Note: While the services are stopped, the controllers will save incoming events (up to 50,000 per controller). Once that limit is reached, the events are First in First out. 3. Back up the SecurityExpert and SecurityExpertEvents databases If the database is encrypted, export the encryption certificates. See the Security Expert Installation Manual for specific instructions on backing up and restoring databases and encryption certificates. https://ecoxpert.se.com/search?documentUUID=71d622e3-2fc1-477a-b08a-5b37ac4b2756&title=SX-SRVR%20Security%20Expert%20-%20Client%20Server%20-%20Installation%20Guide  4. Uninstall Security Expert from the old server From Windows Programs and Features, Right-click Security Expert> Uninstall Once the Uninstall is complete, Manually Restart the Server/PC 5. Disconnect the old server from the network. Connect the new server with the same IP address and/or hostname. If the IP address or hostname of the server changes, update the event server settings in the controllers via the controller’s web page to match the new server. 6. Install Security Expert on the new server and activate the license Ensure that the new Security Expert installation is the same version or higher. 7. Stop the Security Expert services Restore the encryption certificates and databases to the new SQL Server instance. 8. Updating the Database If you are restoring a database from an older version to a later version, uninstall and reinstall Security Expert to upgrade the database. 9. Start the Security Expert Data Service 10. Update the Download Server In Security Expert, navigate to Global | Download server and update the Computer name to match the new Server name. 11. Update the Event Server Computer name in Global | Event server 12. Restart the Security Expert Event Service You should start receiving events from controllers 13. Start the Security Expert Download Service

Issue Links to the Technical Tips Papers Product Line TAC INET Environment I/NET Seven Tech Tip Cause Formerly only available on the FTP site, now available in the Knowledge Base. Resolution Tech Tips linked below. Tech Tip 001   System S7000 Upgrade to I/NET 7700 Tech Tip 002   Calculated Point and Docutrend Operator Rankings Tech Tip 003   MIP01 Memory Interface Processor Installation Tech Tip 005   I/NET 7700 Printer Enhancements Tech Tip 006   Use of LAN Repeater on I/NET 7700 Tech Tip 007   I/NET System Messages Tech Tip 009   I/NET 7700 Setup Tech Tip 010   ICI HHC Memory Addresses Tech Tip 011   S/90 Purging Visitors Tech Tip 012   Shipping MIP Products Tech Tip 013   Mechanical Door Interlock Wiring Tech Tip 014   S90 Graphics PCX File Requirements Tech Tip 015   Indala Reader Card Types Tech Tip 016   New RAM Configuration for MIP Tech Tip 017   Transient Protection On DPUs with I/Disc Tech Tip 018   I/NET 7700 Taps and Building Managers Bias Straps Tech Tip 019   Docutrend and Hard Disk Space Tech Tip 020   Docutrend Reports Tech Tip 021   ADAA Tap Addresses Tech Tip 022   Docutrend:Number of Days of Report Tech Tip 023   S/90 Memory Requirements Tech Tip 024   ADAA System Messages and Docutrend Setup Tech Tip 025   I/NET 7700 Work-Arounds and Known Problems Tech Tip 026   I/NET 7700 Controllers BOOT ROM Compatibility Tech Tip 027   S/90 Color Mapping Tech Tip 028   Controller Battery Back-up Tech Tip 029   I/NET 7700 Host Sign-on/off and Host Lost/restored Messages Tech Tip 030   MR Minimum Trip and Close Tech Tip 031   I/Disc Installation Method Tech Tip 032   ADAA S7000 to I/NET 7700 Upgrade Tech Tip 033   I/DISC Reader Maintenance Tech Tip 034   UCI/UC Use of Bit Offset 08 & 09 Tech Tip 035   MR Memory Usage Tech Tip 036   DPI, MRI & MCI Memory Allocation Tech Tip 037   WIRING AND CONFIGURING CSI CONTROLLERS Tech Tip 038   Programming the 7750 Building Manager Tech Tip 039   7910 and 7920 DPU Memory Usage Tech Tip 040   Lantastic 6.0 Installation for use with S/90 Tech Tip 041   Using pcANYWHERE 5.0 with S/90 Tech Tip 042   MR Memory Usage Correction Tech Tip 043   “P” only Mode of Operation for PID Modules Tech Tip 044   I/STAT Functionality Tech Tip 045   I/NET 7700 Backup Station Tech Tip 046   S/90 and RDTAP Dial Tech Tip 047   Mixing Different Types of ADAA TAPs Tech Tip 048   Universal Asynchronous Receiver-Transmitter Chips Tech Tip 049   Special Days Tech Tip 050   Supervised Inputs Tech Tip 051   I/NET 7700 Ethernet LAN System Tech Tip 052   I/NET 7700 Modem Compatibility Tech Tip 053   I/NET 7700 Modem Compatibility Update Tech Tip 054   SETTING UP THE SITE TAP EDITOR TO CALL A PAGER Tech Tip 055   History Recall Report to DBF File Output Tech Tip 056   Use of I/NET 7700 Message Masking Tech Tip 057   LTS80 Series Lini-Temp Sensors Tech Tip 058   MR55X with Kavlico Transducer Tech Tip 059   I/NET 7700 Controller Interface Cabling Tech Tip 060   Use of DC/DM Points with Sub-Lan Devices MRs and UCs Tech Tip 061   AI and PI Fractional Digits Tech Tip 062   PID and Control Point Tech Tip 066   Momentary Release & Automatic Time Schdl. Release w/ I/NET 7700 used w/ Elevator Tech Tip 063   I/NET Personnel Reports Tech Tip 064   Watermark's in S/90 Video Badging Tech Tip 065   System 90 and Video Badging System Installation Tech Tip 067   12 Steps to I/NET Access Control Tech Tip 068   Application to Disable the “1-OPEN” state of a Supervised DI point Tech Tip 069   TTS100 SERIES THERMISTOR SENSORS Tech Tip 070   BATCH FILES FOR REMOTE SITE GRAPHICS PAGES Tech Tip 071   Access Control Doc-to-DIF Report Tech Tip 072   Standalone MR-VAV-AX Start-up Tech Tip 073   I/NET 7700 Modem Compatibility Tech Tip 074   SETPOINT ADJUSTMENT DEVICE PROGRAMMING Tech Tip 075   Using Belimo NM24 Actuator with MR-ASC’s Tech Tip 076   Running I/NET 4 on a Windows95 Tech Tip 077   How to Convert an Idisc Number Tech Tip 078   How to program a Modem without the use of a TerminalEmulator Tech Tip 079   COMMONLY ASKED ASC QUESTIONS Tech Tip 080   S/90 ACI/DACI Battery Life Tech Tip 081   Integrated I/NET Video Badging Requirements for Single PC Systems Tech Tip 082   How to program Forced Door & Door Open Too Long Alarms Tech Tip 083   How to get started with Integrated I/NET Video Badging

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

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 Methods are needed to purge access events with Security Expert running on SQL Express Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Express Microsoft SQL Server Management Studio (SMSS) Cause Security Expert operating on Microsoft SQL Express can exceed the 10GB limitation depending on configuration and system size Resolution There are several things to consider when configuring Security Expert when running on Microsoft SQL Express which has a 10GB size limitation and other limitations. This article will address the following items: Backup of the SecurityExpert and SecurityExpertEvents databases, review of the database file sizes, automatically and/or manually purge access event records, shrink the database(s) to regain hard drive space, and return the system to operational status.   1. Create database backups for the SecurityExpert and SecurityExpertEvents databases (Select a method) a. Configure options in Security Expert under Global Settings> General> Main Database Backup b. Use Microsoft SMSS. Right-click on the database, select Backup and complete the steps Note: It is recommended to save the databases as different file names than the original database  names to keep a copy of the database prior to deleting records. 2. Examine the database file sizes a.  Observe the file size In Windows Explorer, Navigate to:  C:\Program Files\Microsoft SQL Server\MSSQL(version).SECURITYEXPERT\MSSQL\DATA Observe the file size of the SecurityExpertEvents database If the site is using Microsoft SQL Express and the database file size is close to or over 10GB, events will need to be purged. Note: SecurityExpertEvents files. One file is the transaction log and the other is the data file. The file highlighted above is the data file. b. Check the Windows Application log: There may be a message with evidence of database size issues in the Windows application log, i.e. "Primary Filegroup is FULL" 3. Check the database recovery model configured for both databases in SMSS If "FULL" is used instead of SIMPLE the database(s) will grow quickly See the following KB article for more details on Recovery Mode: https://community.se.com/t5/Building-Automation-Knowledge/Security-Expert-functionality-starts-to-degrade/ta-p/441818 An article with additional details about the database table sizes: https://community.se.com/t5/Building-Automation-Knowledge/Security-Expert-Database-Table-Sizes/ta-p/482178 4. Purge the SecurityExpertEvents db (Select a method) a. Purge using Security Expert Under Global Settings> General> Events Database Configure Purge events older than – there is a drop-down with a list of selections See the Security Expert About> Help for more information. Search on Purge and select Global Settings Note: It’s best practice to delete a month or so at a time. Deleting many events at a time can  cause the server to time out. After the Security Expert purge, use SMSS to Shrink DB and Shrink File (These actions remove the recently deleted records from the hard drive freeing up space Right-click on the SecurityExpertEvents database> Shrink> database Right-click on the SecurityExpertEvents database> Shrink> File b. Manually delete access events using SQL queries In SMSS, run the following query to retrieve all access events and make note of the number of records select * from events order by logged time asc Example: Note 2840 rows     To purge the records run the following query: (Caution: these records will be removed from the database) Use SecurityExpertEvents; Delete from dbo.Events Where LoggedTime BETWEEN '2024-06-13' AND '2024-06-14' Adjust the above query to reflect the dates required) 8 rows affected select * from events order by logged time asc – after running the delete query Example:2832 rows Note: It’s best practice to delete a month or so at a time. Deleting lots of events at a time can  cause the server to time out. c. Shrink database This action removes the recently deleted records from the hard drive freeing up space Right-click on the SecurityExpertEvents database> Shrink> database 5. Verify Security Expert functionality Once the purge and shrink are completed, verify Security Expert is operating normally Note: If the system is not working normally, restoring a previous version of the database(s) from earlier backups may be necessary that were taken before exceeding the 10GB limitation. DBCC is a Microsoft tool for checking the integrity of a SQL database which is beyond the scope of SE Product Support. Please refer to Microsoft's documentation on this subject or consult a Database Analyst.

Issue After installing the Feenics Keep Bosch Service to integrate Bosch panels with Access Expert the service will not start Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Bosch Service and panels Cause A configuration issue is preventing the service from starting successfully Resolution The Feenics Bosch Service will fail to start for a number of reasons: 1. Check that the Feenics Keep Bosch Service exists and hasn't been deleted. "C:\BoschService" 2. The service is unable to authenticate to the Access Expert Instance.  Double-check the username and password being used for the service. Ensure they haven't been recently changed or the username and/or password is correct. Typically the username is Bosch with a configured password. 3. While attempting to start the Bosch service open Live monitoring and see if there is a failed login attempt or other related errors. 4. Open the Windows application log on the PC that has Access Expert and the Bosch service installed and check if there is an exception or a similar error like the following: 5. Install and use the SEQ Log to troubleshoot For Install Instructions for SEQ, see the following article:  https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Installing-SEQ-Logs/ta- p/436521  Once installed, run the SEQ Log http://localhost:5341 while attempting to start the Bosch Service and see if errors are being posted. Example:   6. Check the last ping from the Bosch service to the Feenics host API : This date/time will give an idea of the last successful ping which can help target what may have been changed on the system or network that has affected the service. 7. Run the telnet command to access the Feenics host server If the DOS page is blank/black after hitting enter on the telnet command, that is a good sign. If there are any errors these can be a clue as to what is happening. If a firewall is blocking this connection you won't be able to reach the Feenics server.   Note: If the telnet command isn't recognized, telnet may not be enabled on the PC If none of these steps help to identify the issue, please open a Support case.

Issue Cardholders and door schedules are no longer working and they were yesterday Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause There is likely a holiday or holiday group that is affecting the entire system Resolution A holiday in Access Expert will make every schedule in that instance NOT run that day. Holidays are exceptions to a normally scheduled interval. The holidays within the system apply globally to all schedules. Schedules normally activate at the beginning of an interval and deactivate at the end, however, on a holiday, the schedules do not activate. This creates Holidays as global exceptions to schedules.   Example: A site recently lost all card access and schedules did not work on Veteran's Day. Not all cardholders were out of the office that day.  Reviewing the Instance's Holidays showed that Veteran's Day was configured, so schedules and cards were not working.   ** To resolve this issue: 1. The Veteran's Day holiday was deleted from the above list 2. Next, the controller(s) needed a right click and then "Push controller database" After doing this, the schedules and cardholder access worked normally.

Issue Need to change from the Small Number Format (Card Number) to the Large Number Format (Facility Code + Card Number). Requirement for Security Expert Transitions with I/NET Hardware.   Badging card on SCU1284 Reader using Security Expert, the reader event displays "Format error RD xx Port x Error Number of Bits" From Security Expert Client Events Product Line TAC INET, EcoStruxure Security Expert Environment I/NET Seven Security Expert Transitions Cause The I/NET system is limited to a maximum number of access cards, 32,000 per Tenant.  If a larger number is required, then I/NET must be configured to use large card numbers.  The Large card number format described in the Resolution MUST be completed before transitioning from I/NET to Security Expert and utilizing the I/NET SCU hardware as detailed in the Transition Guide Security Expert - INet Access Control to Security Expert - Reference Guide. Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this, use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Wiegand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can determine the Decimal number of the first card in the system (e.g., Card #970 Facility code 199) is the Decimal number 13042634, using a 26-bit Wiegand Excel spreadsheet.  This number will become the Source number in the Key/Card Translation table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the I/NET Seven Access Control editor.  This table will be removed after running the provided SQL Script.  The Key/Card Translation must contain: Source - Decimal number calculated in Step 3 above (13042634) Target - First Individual number shown in the Tenant (970) Count - Number of Individuals as shown in the Tenant (10000) Tenant - Tenant number this translation refers to (1) If there are multiple Tenants, then this process MUST be repeated for each Tenant Tenant Editor and Key/Card Translation Editor Shut down I/NET completely and run the attached SQL Script. Then once the script runs then, restart I/NET and look in the Individual Parameters editor, as shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify a Hex number and the decimal number matching that from the Excel spreadsheet (Step 3) is seen in the Individual Editor Card section. NOTE: There may be multiple card entries here; the Last entry shown is that entered by the SQL Script.  It will depend on whether an existing Card entry was entered for the Individuals before running the SQL Script.  To have large numbers working on a site DipSw #7 has to be turned ON for the 7910/7920 DPUs. For the SCU1284 in the door editor, at the top center of that editor, there is a check box, "Card Translation," which has to be enabled for large numbers to work in the SCUs. An SLI “SAV” should then be done because that is where the Card numbers and Door settings are stored. Then perform an SLI restore. Followed by a DPU restore to all of the door controllers. NOTE: Steps 6d. and 6e. are NOT required when performing the transition to Security Expert as this information will be performed by the SP-C.   

Issue When a card is presented at the Smart Reader it beeps but no card data is sent through to the Security Expert Controller. The Reader LED is flashing red then green every second continuously. Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers which support both 125Khz and 13.56Mhz (SX-DRD-xx, SX-DRK-xx, SX-RK-xx) Cause The Smart Card Reader is not able to communicate with the Controller as it is in RS-485 mode but the connection being used is Wiegand. Once connecting to the the Smart Reader in RS-485 mode the reader will not communicate if it is then connected up to a Wiegand port. Resolution Once a Security Expert Smart Card Reader is used in an RS-485 configuration it will not work in Wiegand configuration until it has been re-programmed with a configuration card designed for that purpose. The configuration card  (SX-ISO-CONFIG) must be purchased through Schneider Electric. See the Security Expert Credentials Order Form for details.   This is because RS-485 is a two-way communication, intelligent wiring protocol. Once the reader is set in this two-way communication mode there is currently no way, without the configuration card, to go back to a less intelligent one-way mode like Wiegand.   Note: Readers manufactured in 2017 or before may have a firmware version that uses a configuration mode that will not respond to a configuration card. If you contact Schneider Electric for a configuration card, supply the serial number (SN) from the back of the reader on your request.

Issue Continuum Cyberstation running on Windows 7 machine.  Cyberstation crashes unexpectedly.  Cyberstation crashes when an alarm come is reported. Product Line Andover Continuum Environment Continuum CyberStation WebClient Outlook Cause Event notification alarm delivery configured to send email alarms when Outlook is not installed on the workstation. Resolution Either remove the email option from the event notification, or install Outlook and set it up for alarm emailing. If enhanced alarm delivery is selected (Database Initialization> Server(Stand alone)> See check box for enhanced alarm delivery Ensure that recipient Cyberstations do not have page, log, forward options selected. Only use email if it is being used. Example: Ensure that if an object is selected in an event notification action (i.e display graphic) that the point that is being alarmed on has that object (graphic) selected. Related article:  https://community.se.com/t5/tkb/workflowpage/tkb-id/knowledge-base_public/article-id/6986 

Issue EcoStruxure Building Operation WorkPlace Tech Editor Supported Microsoft Visio Versions The following error context is encountered when trying to run WorkPlace Tech Editor to edit a program: WorkPlace Tech Editor returned errorClass not registered 0x80040154 REGDB_E_CLASSNOTREG Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation WorkPlace Tech Editor I/A Series MNL, MNB Controllers (MNB - from SBO v1.8.1 and newer) Cause Only the 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. The error is seen when a 64-bit version of Microsoft Visio 2010 is installed. Resolution Currently, only 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. SBO 1.5, 1.6, 1.7 Microsoft Office Visio 2010 SP1, 2007 SP2, 2003 SBO 1.8 Microsoft Office Visio 2010 SP1 (32-bit), 2007 SP2, 2003 SBO 1.9, EBO 2.x, 3.x Microsoft Office Visio 2016 (32-bit), 2013 (32-bit), 2010 SP1 (32-bit) EBO 2022 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2023 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2024 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit)

Issue The ACCDataServices application is crashing on start up of CyberStation Product Line Andover Continuum Environment CyberStation Windows XP Cause Windows permissions issue Windows Firewall Configuration  Resolution Make sure when installing CyberStation the user has Local Admin rights to the computer Make sure Windows Firewall is turned off during the install Make sure all VirusScan software is turned off during the install. Check the event notifications and verify that none of them are set for the recipients to have pager, log, forward or any unused option which can create unnecessary traffic when using enhanced alarm delivery. To check if you are using enhanced alarm delivery Database Initialization > Server (or Stand Alone) > see check box for enhanced alarm delivery An example of possible unnecessary check box recipient options:  Check that each action in the event notification i.e. 'Display Graphic' has a corresponding object for the point alarming. If no object is selected it may cause accdataservices errors. Run acctrace and/or the Continuum error  log and wireshark to determine if there are errors. Cleaning up these issues can relieve the system and these errors. The Windows application/system logs and system.nfo/Belarc advisor can help gather info about the PC. See Top 10 Steps for Troubleshooting Cyberstation and webClient issues. If there is a 3rd party bacnet device, disable or unplug the device to see if the issue is related to the flooding of traffic into Continuum Liebert Sitelink- If you are on 1.93 and below, the Sitelink trendlogs could affect Continuum. Upgrade to 1.94 and disable trendlogs. Engineering is working on a hotfix for this issue. (Not released as of 11/29/12) Stand Alone Windows 7 system - A stand alone system can easily tax resources when extended logging, graphics, SQL Server, Cyber, etc. are all running on the same system. Eliminate any errors in the error log and disable certain functions to see if this helps. Consider a server class PC depending on what the system functions that are required by the site. Install Cyberstation 1.94 SP1 and related firmware updates as there are many fixes to address accdataservices.exe crashes (See Continuum 1.94 SP1 Service Pack to address accdataserices.exe crashes and other issues) Do not mix 1.94 and 1.94 SP1 Cyberstations on the same db, this could cause accdataservices crashes

  Issue Cardholders are getting automatically changed from Active to Inactive (deactivated). When the LDAP/AD integration is configured to map the Active Directory attribute UserAccountControl to Card Status in Access Expert; records that have useraccountcontrol = 512 (normal active account) are getting their cards deactivated. These records should NOT be deactivated.   An LDAP query mapped to UserAccountControl Card(s) showing Inactive in Access Expert   Event History record showing the date and time the cardholder record was set to Inactive by LDAP Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Active Directory Cause A version of the LDAP service less than 24.2.1 Resolution Manually set the cardholder to Active as a workaround Ensure the LDAP service installed is greater than version 24.2.1. See the following link to a KB article showing how to "Identify which LDAP service is currently installed" : https://community.se.com/t5/Building-Automation-Knowledge/Identifying-which-Access-Expert-LDAP-integration-version-is/ta-p/480424    If the version installed is older than 24.2.1, perform the following steps: Uninstall LDAP from Windows Programs and Features Navigate to C:\ProgramData\Feenics_LDAP and delete the .dat file Restart the PC Install an updated version of LDAP from Feenic's web site: https://s3.amazonaws.com/download.feenics.com/ldap/Feenics.Keep.Installer.ActiveDirectory.msi  Test to ensure the issue has been resolved with the updated LDAP service

Issue Can Cyberstation setup and configure 3rd party BACnet devices. Product Line TAC IA Series, Andover Continuum Environment Cyberstation BACnet I/A Series MNB-1000 Cause It is desirable to configure all products from the same software. Resolution Cyberstation and the BACnet protocol do not allow you to do basic setup and configuration of 3rd party devices, most products will have their own configuration software or local display/ keypads for setup. The I/A MNB-1000 BACnet controllers will require I/A Series Software to setup and configure the controllers, this can not be done through Cyberstation. Once setup and communicating Cyberstation will be able to make changes / adjustments depending upon the PIC's statement of the device.

Issue Not able access a new MNB-1000 via its default IP address. It will not respond to when pinged. Product Line TAC IA Series Environment WorkPlace Tech all versions, WPT Version 1.50E and later Cause The ability to ping the MNB-1000 controller was removed starting in Firmware version 1.50E. All MNB-1000s are shipped with IP port disabled. Resolution Starting with firmware revision 1.50E, the ability to ping a MNB-1000 controller was removed; so any MNB-1000 controller at or above firmware Revision 1.50E will not respond to a ping. Reference Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E or higher for further details. All new MNB-1000 controllers are shipped from the factory with their IP and MS/TP ports disabled. The Ethernet port is the only port enabled. The MNB-1000 controller must first be accessed via its Ethernet port. Once gaining access, its BACnet/IP port can then be enabled.  Note: Both BACnet/Ethernet and BACnet/IP ports should not be enabled at the same time. So if BACnet/IP is being used and once the BACnet/IP port is configured and enabled, then disable the Ethernet port. NOTE:  Firmware 1.537 made the MNB-1000 visible via the ping command again.

Issue Can a MNB-1000 be configured to get an IP address via DHCP? Product Line TAC IA Series Environment MNB-1000 Cause End user does not want to use fixed IP addresses on their network. Resolution The MNB-1000 does not support the use of DHCP for setting the IP address.

Issue How can the MNB-1000 be set back to factory defaults? Product Line TAC IA Series Environment I/A Series MNB-1000 Cause Reconfigure the MNB-1000 Resolution Do the following: Set all of the dip switches on the MNB-1000 to the ON position (all ones)  and cycle power.  Wait until the controller completely boots up (solid green status light), then change dip switches from all ones back to the desired address. Cycle power again. Note - Setting the MNB-1000 back to factory defaults will delete the installed application.

Issue How to determine if the IOU modules neuron chip is manufactured by Toshiba or Motorola? Product Line Andover Continuum Environment Continuum Cyberstation I/O modules (All modules affected except the AC-1 Plus, VT-1, Infistat, and LC-1) Cause Up-revving I/O modules to new firmware and there are 3 types that have been used,  Motorola, Toshiba and the most recent Cypress neuron chips. The program ID can help determine which neuron is in the IOU module to select the correct firmware. Resolution To determine the chip type, look at the Program ID using the object editor or a list view. The second digit or position of the second number of the Program ID is the chip set indicator. If the second digit is 2, the I/O Module has a Toshiba chip. If the second digit is 1, the I/O Module has a Motorola or if shipped after 2014 a Cypress chip.  See example of object editor below:   ***** Note: The image above doesn't show the Cypress information. a 1 could be Motorola(old) or Cypress (new). If the flash revision is 21 the it is the most recent flash version for the Cypress chip. The IOU modules that could have the Cypress chip are AC-1(Not Plus), A0-4,DI-8,DM-20, D0-4, D0-6, MI-6, UI-8. Motorola or Cypress Ui8s that have an 11 in the second position of the ProgramID are either Motorola or Cypress chips. The modules with ProgramID 11 in position 2 and firmware version 11 in position 4 of the ProgramID are Motorola and 11 is the most up-to-date version. The modules with 11 in the 2nd position of ProgramID and firmware version 21 in position 4 of the ProgramID are Cypress chips.  I have not seen a separate firmware version 21 file for the Cypress chip on Exchange or anywhere. 21 is the most up-to-date version and was shipped with those modules. The email we found indicates that since the Cypress chip was a direct replacement for the Motorola chip they used the same number (1) in the 2nd position of the ProgramID (instead of using 3). To summarize the most up-to-date firmware versions for the Ui8: Motorola: 11 Toshiba: 20 Cypress: 21   There is an old TPA that describes this in detail. You can download the TPA Technical Bulletin 1041 - Continuum IO Modules Now Using the Toshiba Neuron Chip from The Exchange Download Center.

Issue Can the UPS option be added to an existing Continuum power supply? Product Line Andover Continuum Environment Continuum Power Supply PS120/240-AC85 Cause Can the UPS option be added in the field to a Continuum PS120/240-AC85? Resolution No. There is no field upgrade kit to add the UPS option to a Continuum power supply.