Building Automation Knowledge Base

Issue How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  

Issue Received error 'IO Channel number out of range' when creating a door on AC1/AC1A/AC1Plus on an IO module.  The same door configured on a module with a lower IOU number saves successfully. Product Line Andover Continuum Environment Continuum CyberStation Netcontroller  AC Module Cause The IO module is configured with an IOU number that is above the MAX IOU modules supported by the NetController.  Note this is true even if there is only ONE module configured. Resolution Check the IOU module number entered in the door object (1) Check the Max IOU module supported (2)   Delete the IOU module and recreate it using an IOU number at or below the max IOU number supported by the Net Controller.

Issue Infinity controller error: Type not valid for this IO channel Product Line Andover Continuum Environment Continuum Cyberstation Cause ElecType mismatch between what is in the database and the field controller hardware. An example of this problem would be offline creating a voltage output on a DO-4.  It will save to the DB since it is a valid InfinityOutput configuration.   Although when attempting to do a Send to Controller the controller knows that point type is not valid on the specific IOU module hardware. This can also happen when an object is imported into Continuum because the database error checking is less strict than when creating the object online. Resolution Go into offline editing Check the point configuration If it does not match the field hardware, then correct it, save it, go to online mode and reload.

Issue The database is logging multiple alarm entries each time a point goes into alarm. Product Line Andover Continuum Environment Alarms MSMQ SQL Server Event Notifications Cause Various causes. Resolution The following is a list of conditions which may produce multiple alarm event logging. Network Latency  In cases where the network is extremely slow or workstation are overburdened, the process of logging alarms may be slowed to the point where a second alarm is sent by the controller while the previous alarm is still in the process of being logged. In one particular case the logging workstations associated with the duplicate log entries were all in India while the database server was in the US.  The problem was resolved by changing the ACCID of all of the India workstations to 253 or higher so that they were not involved in logging alarms. Database insertion errors If there are database insertion errors in the ACCTrace, Cyberstation cannot send an acknowledgement that the alarm event has been logged. Consequently the controller will continue to send the alarm event until it receives notification that the alarm has been successfully logged. Database Server latency It is not unusual to see Database Insertion errors when a Continuum DB server is struggling to keep up with the demands that the system has placed on it. A use Task Manager and other tools to evaluate the processor and memory consumption. Enhanced Alarm Logging and Enhanced Alarm Delivery. If Enhanced alarm logging/delivery is broken due not shutting down all workstations before doing a database update, it is possible to have combination of enhanced and old style alarm delivery.  The solution is to shut down all workstations and perform a db update with Enhanced Logging and Enhanced Delivery selected. Workstation Resources.  If the logging workstation is over burdened with reports, programs, extended log downloading, etc.

Issue This condition will arise after successfully installing and running Project Configuration Tool for some time. PCT 1.x can no longer initialize the virtual host adapter as a result of the adapter being deleted or removed. The errors may be a result of but not limited to: Introducing a new VPN software package to your PC/Laptop. Manually removing or modifying the Virtual Box Host Only - Network Adapter. Malware or Antivirus platforms that have removed or disabled the adapter. Example: PCT Version - 1.1.2.57 Local mode was set up on a physical laptop and used to offline engineer a project. The job was completed and PCT was not used again for roughly a month. A new project was sold and required PCT for offline engineering. The laptop was booted up and PCT failed to open. The user was presented with the following errors: "Get System State Command: 'Could not connect' " "Get predefined properties command: 'Could not connect' " "GetDashboardErrors Command: 'Could not connect' " "Get System Memory info Command: 'Could not connect' " Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only) Project Configuration Tool 1.x Cause PCT 1.x can no longer initialize the virtual host adapter as a result of the Vbox adapter being deleted or removed. Resolution Reinstall PCT 1.x on top of your current installation. Your projects will not be modified in the process. Locate the installer. Run the installer, it will ask you to remove the previous version. Press ok. Progress will show as uninstalling. PCT will prompt for installation. Click Next. Select default installation paths. Click Next. Select desired PCT mode. Click next. Ready to Install selected mode. Click Next. PCT software installed. Click Finish. Now PCT will set up the Virtual Host Adapter. Press Ok. Status bar. Compted setup dialog. Click Ok. Run PCT. If successful you will see the template sets getting installed via the top right of the window. Open a project and test an AS/AS-P. If the above steps do not work, here are a few more to try:   Restart the machine after the PCT software finishes re-installing Right-click and select “Run as Administrator” Uninstall PCT software and Oracle VirtualBox and re-install once more   If PCT 1.x still will not work, please open a support case with your local Product Support Group.

Issue Information for replacement for the SPA1505 and SPA1506 Product Line Field devices Environment Pressure sensors Cause "PA-00167 Sensors and Input Devices New SPP930 Relative Pressure Switch" suggests SPP930 replaces SPA 1505 and SPA 1506. The link provided for the SPP930’s manufacturer’s data sheet, no longer works Resolution SPP930 Part number 004701160 replaces the SPA 1505 SPP930 Part number 004701170 replaces the SPA 1506 The site wiring should be checked, to ensure it complies with replacement switches reduced current ratings.   SPA 1505/1506 data sheet Huba Controls type 620/625 data sheet.

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 Creating a report that shows which visitor is being visited Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause The standard visitor report does not record who at the site is being visited Resolution This video demonstrates how to create a visitor report that includes which users have been visited in the Security Expert System.   The advanced Visitor Report is created in 4 main steps: 1. Create an Access level for each user who receives visitors 2. Assign this Access level to the user's visitor tab 3. Create (or use existing) User report with the new "access level" column selected 4. Configure and run the user report   Creating Access levels 1. In Security Expert client, go to Users|Users a-Select a user who receives visitors (ex: John Doe) b-Go to the Visitor tab c-Check the "User supports visitors" box d-Click the ellipsis (3 dots) to open the Access Level window e-Click Add button f-Name it '[User]'s Visitors' (ex: John Doe's Visitors) g-In the configuration section, configure the access level required for the user's visitors h-Save and repeat for each user who normally receives visitors. Close the window and go back to the User table.   Assign Access level 2. Select "John Doe's Visitors" for Visitor access level -Save changes   Create User Report 3. Go to Report|Setup|User -Create (or use existing) report for visitors -Go to the Columns tab -Click Add and choose "Access Level" User Field -Save report setup   Configure User Report 4. Return to the general tab and expand the "Default user report filter" section. Press "edit in report view" and edit your desired layout -Save report view   The next time you run the visitor report it will print who's being visited in the "Access level 1" column

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:

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 Create a report of all expired cards Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause A custom report and its configuration are needed to find all expired cards at the site Resolution This video demonstrates how to create and configure a report to find all expired cards in a system   Create a User Report: 1. In Security Expert Client, go to Reports|Setup|User and Add a new (or use an existing) report. 2. Configure the desired Report Type and Sorting 3. Go to the Columns tab, click the Add button and select Columns.  Make sure to have: -Expiration date of badge AND/OR Expiry date 4. Save your report   Please note: The "Expiration date of badge" column pulls the date from Users|Users|Extended Tab|Expiration date of badge. The "Expiry date" column pulls the date from Users|Users|General Tab|User expiry date/time section's End date.   Customize the User Report's layout: 1. Go to Reports|Setup|User| General Tab| Default user report filter and click the "Edit in report view" button 2. Right-click "Expiration date of badge" (or "Expiry date") column and select the Filter Editor 3. Change the "And" condition (in red) to "Or" 4. Change Equals to DateTime Operators: Is Yesterday 5. Click "+" sign in green circle to a line and repeat changes 5 more times for the following: - Is Earlier This Week - Is Last Week - Is Earlier this Month - Is Earlier This Year - Is Prior This Year 6. Click Save Report Layout

Issue EBO server (ES/AS/Edge) Trace.log shows COV publisher errors. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server - Standard Cause A BACnet device is misconfigured and trying to perform COV subscription that produces an error. Resolution Review EBO server Trace.log EXAMPLE:  2023-12-28 13:54:05.124 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:54:07.354 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:55:05.173 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:55:07.420 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:02.921 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:56:05.213 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:56:07.673 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:09.862 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:57:02.932 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:57:05.247 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:57:07.719 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:57:09.874 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:58:02.945 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:58:05.288 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:58:07.767 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:58:09.889 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f​ Lookup the BACnet Error Code: Decoding BACnet Errors - Schneider Electric Community (se.com) EXAMPLE:  0x8001001f is unknown object, so a device is trying to subscribe to an object (Object Type + Object ID) that does not exist. NOTE: There could be other error codes not used in this example that are reported. Enable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Information to Trace. Wait for time to pass so Trace.log can collect more records. Review EBO server Trace.log to find the new line before the error, identifying the controller with the misconfiguration. Example: MSTP device (MAC 3) on local MSTP network is misconfigured for unconfirmed COV to BV 202  2023-12-28 14:11:08.439 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 3 process 1: <binary-value, 202>, lifetime 18000s, unconfirmed 2023-12-28 14:11:08.441 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f​ Example: IP Device (MAC 192.168.198.136:47808) is misconfigured for confirmed COV to AV 204  2023-12-28 14:07:03.073 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 192.168.198.136:47808 process 1: <analog-value, 204>, lifetime 18000s, confirmed 2023-12-28 14:07:03.075 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f​ Disable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Trace to Information. Inspect the listed BACnet devices and correct the misconfiguration.

Issue Spare Addresses for use as internal points on an SCU 1284 dual address Product Line TAC INET Environment I/NET Access Control SCU1284 dual address mode Cause What are the ramifications of using the spare point addresses for internal points in an SCU 1284 Resolution Note! It's generally not recommended to use the available address on a subLAN. Addresses marked as "Internal" in the MCU configuration are reserved for internal software points. However, it's crucial to consider that doing so may limit the potential expansion of the subLAN to utilize these addresses in the future.   When a SCU1284 is set to dual channel, it only uses 12 inputs, 8 outputs, and 4 reader points.  Here is a list of all software points and their uses:   XX00 DI - XX03 DI Hardware Inputs used by doors XX04 DI - XX07 DI Spare Hardware Inputs XX08 DI & XX09 DI SCU tamper and power monitoring points XX00 DO - XX03 DO Hardware Outputs XX04 DO - XX07 DO Spare software only points XX08 DO & XX09 DO Reader Points YY00 DI - YY03 DI Hardware Inputs used by doors YY04 DI - YY09 DI Spare software only points YY00 DO - YY03 DO Hardware Outputs YY04 DO - YY07 DO Spare software only points YY08 DO & YY09 DO Reader Points   See the following documentation: TCON312-0910.book (schneider-electric.com)

Issue Can the serial port on the NetPlus Router (NPR) communicate at 9600 baud? Product Line TAC INET Environment NetPlus Router (NPR) 2000 Cause Configuration inquiry Resolution This specific configuration port is capable of transmitting data only at a rate of 19,200 baud.

Issue Sequence zero does not run when power is restored to the Micro Regulators (MR). The MRI is on a UPS in another part of the building and never loses power. Product Line TAC INET Environment MicroRegulator (MR) SubLAN devices MicroRegulator Interface (MRI) Controller LAN Interface Cause By design, sequences are stored in the MRI. Sub-LAN controllers do not store sequences. Resolution Sequence zero is designed to trigger the power restore event (Sequence 0) in the event of the Interface (MRI) power failure being restored, hence the MR will not trigger this sequence 0 in the MRI.  The action is correct.

Issue How do I set the Tap emulation for a Process Control Unit (PCU)? Product Line TAC INET Environment Process Control Unit (PCU) 7716/8 Process Control Unit (PCU) 7756 Cause Need to set TAP Emulation type on PCU  Resolution Using the HHC, press [Code], 90 [Enter] Press [Inc] or [Dec] through 7801, 7803, 7806 Tap emulation Press [Enter] to accept your choice 7801 for direct connection and Integrated dial operation 7806 for direct connect, integrated dial, and ADAA For additional details, please see the following documentation:  PCU 7718 TCON106-0910.book (schneider-electric.com) PCU 7756 TCON127-0910.book (schneider-electric.com)

Issue Where can I get example programs and programming information on the Smart sensors? Product Line Andover Continuum Environment Smart Sensors: TTS-SD-LCD-1 TTS-SD-LED-1 Cause Smart sensors require specific Plain English programming that is different from other controllers, where is the documentation to support this? Resolution The Smart Sensor Installation and User's Guide and Example programs for the Smart Sensors are available for download from The Exchange Extranet.   PSS Example programs

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

Issue When is an "additional 500 points" license required for an Enterprise Server? Product Line TAC IA Series Environment I/A Series R2 IA-ENT-1 Enterprise Server licensed with the IA-DRV-OSD Open Systems Device driver license Cause The basic Enterprise Server license does not include any external point driver capabilities.   Adding the IA-DRV-OSD allows the enterprise server to communicate with up to 25 points of each type, BACnet, OPC, SNMP and ModBus, all using IP communications. Resolution An Enterprise Server can be licensed to directly communicate with  BACnet, OPC, MODbus and SNMP points by adding the IA-DRV-OSD license and will support communication with up to 25 points of each specific type of points. For each additional block of 500 points of a specific type, you need to purchase an additional points license, IA-BAC-500, IA-OPC-500, IA-MOD-500 or IA-SNMP-500.  Here is an example of how these licenses are used.  The Enterprise Server needs to communicate directly with 1250 BACnet IP points and 60 SNMP points.  The following licenses will be required: IA-ENT-1 -- Enterprise server license IA-DRV-OSD -- Open System Driver for direct point communication, includes 25 points each of BACnet, SNMP, OPC and ModBus. IA-SNMP-500 -- allows ES to communicate with the 60 SNMP points, technically allowing communications with a total of 525 SNMP points (25 points included with IA-ENT-1 and 500 with IA-SNMP-500). IA-BAC-500 -- allows the ES to communicate with an additional 500 BACnet points bringing the total to 525 BACnet points IA-BAC-500 -- this second IA-BAC-500 license will allow the ES to communicate with the additional 500 BACnet points, bringing the total allowable BACnet point count to 1025 points IA-BAC-500 -- this third IA-BAC-500 license will allow the ES to communicate with the required additional 225 BACnet points, actually bringing the total allowable BACnet point count to 1525 points. NOTE: On most computers an IA-ENT-1 with the Open System Driver is capable of supporting a maximum of 4000 external points regardless of the number of points licensed in any one communication type.

Issue Reader Expander loses communications to the SP-C, how are Users authenticated when they attempt to access Doors controlled from this Reader Module? Which Users will still have access through Doors when the Reader Expander is offline to the (SP-C) Controller? Product Line EcoStruxure Security Expert Environment Security Expert SP-C SP-RDM2 Cause The SP-RDM2 Security Expert - Door Expansion Module - Installation Guide lists three options for how the SP-RDM2 should behave when it is offline from its SP-C controller.  The resolution below describes what each of these modes means. Resolution There are three options for how to handle access when the Reader Expander is in offline mode (not communicating with the Controller).  1. No Users Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “No Users” option removes access for any cards badged at these Readers. no one will have access while the Reader Expander is offline to the Controller. 2. Any Card Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “Any Card” option allows for any card at all to be granted access when the Reader Expander is offline to the Controller. This is the least secure option as anyone with a valid technology card, which is correctly formatted to either the Primary or Secondary formats defined for the Reader Expander, will be granted access. There is no validation of the card's Facility Code or Card Number. At present there is no option available for providing valid access on reading a card's Facility Code only. 3. First 10 Users plus Cache Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “First 10 Users plus Cache” option allows for the below Users to be granted access when the Reader Expander is offline to the Controller. The first 35 Users in that Controllers Database. The last 150 Users that have badged with valid access. Note: This options text description is an old reference and will be updated in a new software version to reflect that this supports the first 35 Users.

Issue The default LED Output names for Reader Expanders (eg. RD Red R1) do not always match the colour of the LEDs on the card reader Product Line EcoStruxure Security Expert Environment Security Expert Controller Security Expert Reader (New version only) Cause The default LED output names/labels don't accurately describe their function. Resolution The "RD Green R1/R2" Outputs represent the reader's LED colour in its "active" state. By default: These outputs are not inverted; (in Programming|Outputs|Options General section, "Invert output" checkbox) When the output is activated, the reader's LED is green; When the output is deactivated, the reader's LED returns to blue; The "RD Red R1/R2" Outputs represent the reader's LED colour in its "resting" state. By default: These outputs are inverted When the output is activated, the reader's LED colour is also green When the output is deactivated, the reader's LED returns to blue To have the Red LED in the active state, you must add the following to the output's command console (found in Programming|Outputs|General Commands section): LEDColour = 1, where 1 is Red.   Here is a list of available colours: 1= Red 2= Amber 3= Orange 4= Yellow 5= Lime 6= Green 7= Mint 8= Turquoise Note: Please refer to AN 270 to identify new from old versions of the reader hardware