Building Automation Knowledge Base

Issue Error message "Unable to display events. To view or change, go to Text view on the Advanced tab." in a Schedule in Workstation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The error message appears when attempting to view events with a duration of five minutes or less in the graphic view of Schedules in Workstation. Additionally, the message can also occur when the time between two events is five minutes or less.  The screenshot below shows an event with a duration of four minutes that causes the error message to be displayed. Resolution Two potential solutions are available to address this issue: Utilize Webstation: Webstation does not have the same limitations as Workstation. Users can leverage Webstation to view and edit events with a duration of five minutes or less, or where an event starts five minutes or less after another event ends. Switch to Text View: As indicated in the error message, users can switch to the Text view on the Advanced tab to list short-duration events. To do this, navigate to the Advanced tab (1), then click on the Text view button (2) to switch to text view.

  Issue EBO 5.0 and all other revisions, In workstation When selecting `View history` of an alarm, we get columns more focused on alarms such as Alarm state, Alarm text,.. etc  But  in WebStation, we have “ View Events “ that shows columns that are more focused on object event history (including Value before, Value After, etc) rather than alarm history.       Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Cause Navigating to View Alarm history in webstation is different than in workstation Resolution Alarm is a subset of Event, so it is reasonable to see it is under 'Event viewer'. There is no such a thing called 'Alarm history record' in webstation.This is Function as Designed (FAD) If we click on any of the events, after opening it we can see full alarm details.

Issue Want to modify the type of a block in the Function Block Editor while retaining the original block's name Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Function Block Editor. Cause Altering the block type without removing the block first can result in the persistence of old block parameters even if they are incompatible with the new block type. For instance, transitioning from an "Integer Input" block type while the input is in a forced state may cause the new block to retain the forced state, even if it is not applicable, leading to potential issues with un-forcing. Resolution To ensure correct functionality, it is recommended that the old block is removed and the application saved before adding the new block with the original name. This process effectively clears out the old configuration, enabling the new block to contain only the parameters of the new block type.

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 In some cases, the event and trend database can grow really big, although not all the space in the files is used. In extreme cases, there is more free space than used space and it is quicker to create a separate file. Product Line EcoStruxure Building Operation Environment SQlite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: VACUUM main INTO 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 6.0\Enterprise Server\db\Historical\event2.db'; Update the path to match your installation. One can SHIFT-RIGHT-CLICK the event.db or trend.db and select Copy as Path, then select everything inside the single quotes and paste. The paste will include double quotes, so delete those and leave the single quotes Update the database name to ensure it is unique. Click the blue play button above the Query tab. Depending on the size and amount of free space, this can take seconds to days to complete. One can monitor the progress in Windows Explorer by seeing the Size and Date Modified field update. Append .old to the end of the original file and rename the new file, event.db or trend.db, so it replaces the original. Start the Enterprise Server or Enterprise Central.

Notice NOTICE COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support for assistance. Issue Want to access door with 'Card only' or 'PIN only' not both of them.   Product Line TAC INET Environment I/NET Seven Access Cause I/NET has two door mode schedules, Secure, the default setting, which provides access via card number or Secure with PIN, which requires card entry AND a PIN entry.   In this case it is possible to use either card or PIN to gain access if using specialized readers that support a Wiegand PIN output. Resolution It is possible to achieve this provided the PIN output from your card reader supports one of the supported card types of I/NET (i.e. 26-bit, 32-bit Wiegand etc) you can assign a "card number" (PIN) for each individual. The PIN pad will output the entered PIN in Wiegand format and I/NET will then treat it as a normal card entry. Once the PIN pad / card reader has been configured you simply enter this into the Individual editor as the card number card and it acts exactly the same as swiping a card. What this means is that the Individual can use either their card or PIN to gain access (if entered in this fashion). So provided you have a suitable reader / pin pad (such as the P-640 Patagonia Proximity Reader from Keypad Farpointe Data, Inc (www.farpointedata.com))- here are the steps to configure this to work: In the Door editor set the reader type to Wiegand 26-bit (or other) Configure the PIN Type to 26-bit The Door mode is either left blank (Secure mode) or configured as 'Secure' Configure your Tenant (Refer to note below regarding Large Card number usage) Add your individual; The individual will have to have two card numbers associated to them: The number associated to the card, The number associated with the PIN number - what not to get confused with is that this PIN number is NOT the PIN number associated (or shown) in the Individual editor. Large Card number usage: How to calculate the "card number" if using Large Card Numbers: The following two Excel spreadsheet calculators; 26-bit and 32-bit can be used calculate you the large card number. Enter the details (Facility Code / Card number) and the calculator produces the large card number in both decimal and hexadecimal. For example if you use Facility Code 26 and card number 255, the results would be 1704191 (Decimal) and 001A00FF (Hexadecimal). Alternatively I/NET also displays this 'large card' number in the Message column if added to the Transaction window - you can use this also to ensure you have everything wired and configured correctly. How to calculate the "card number" if using the Facility Code / Card number: Once the reader has been programmed with the facility code and this number entered into the Tenant Code of the Tenant editor. The PIN number assigned to the individual then becomes the 'card number’. So for the same example used above, the Facility Code used is 26 and card number 255, the Tenant editor will have the Tenant code configured as 26 and the Individual number (ID) of 255 is used - so no card number is entered into I/NET. This ties the card number to the Individual ID. This is important and the major difference between using large card numbers and facility codes.

Issue No license is available for Vista Webstation Webstation installation issues ASP.NET Authority issue Product Line TAC Vista Environment Vista Windows 2003 Windows 7 Windows 2008 R2 Cause Sometimes it is not enough to let ASP.NET be run by NetworkServices. The user LocalSystem needs to be used instead. Resolution Windows 2003:  Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Expand application Pools Right click on  "SE ASP.NET v4.0 Classic" and choose Properties. Under "Identity" choose user "LocalSystem" from the Predefined drop list. Click OK and restart webstation. Windows 7: Right click on my Computer and choose "Manage" Go to Services and Application Click on Internet Information Services Click on application pools Right click on  "SE ASP.NET v4.0 Classic" and choose Advanced settings Under "Identity" choose user "LocalSystem" Click ok Restart webstation Windows 2008R2: Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Click Application Pools under the serve Right click on SE ASP.net v4.0 Classic and choose Advanced setting. See attachment IIS manager 1 Click the button beside Identity under the process model. See attachment IIS manager 2 Change the built-in account from networkservice to LocalSystem. Click OK and restart the webserver in Internet Information Services (IIS) Manager. If the problem persists, please see Problems installing Vista Webstation 5.1.5 or newer for additional helpful information.

Issue Gets error message "GCM Not responding" when he attempts to make a connection to a device on the ASD bus under the UNC. Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series R2 TunnelAX jar file, version 2.301.534a or later I/A Series ibsASD jar file, version 2.301.534a or later I/A Series G3 Serial Tunnel 2.0 Client Cause Misconfiguration of tunnel name Resolution Before attempting to configure the AX Tunneling, verify that the correct versions of the R2tunnelAX and ibsAsd jar files have been installed as documented in How to install an I/A Series R2 JAR File. Tunnel Name in AX Tunnel Client must match the Tunnel Instance name in the ASD Service. When you add the AxSerialTunnel to the ibsAsdService, the identifier is automatically assigned based on the port defined in the communications configuration of the IbsAsdService itself.  This name is displayed under the Status tab of the AxSerialTunnel: Figure-1 When configuring the "Niagara AX Serial Tunnel 2.0", the following window is displayed. Figure-2 The tunnel name (See Figure 2) entered in this window must match the port identifier shown in the AxSerial Tunnel definition (See Figure 1).  If these identifiers do not match, the Ax Serial Tunnel Client will not be able to connect to the tunnel in the I/A Series R2 station. NOTE: When installing the I/A Series G3 Serial Tunnel 2.0 Client, no control panel applet is created as with the earlier version of the I/A Series R2 Serial Tunnel Client.   To configure the I/A Series G3 Serial Tunnel 2.0 Client,  run the program C:\niagara\VserAx\vseraxConfig.exe.  If you need to frequently reconfigure this client, you can create a Window Start Menu shortcut or Desktop shortcut pointing to this file.

Issue Installing VisiSat 2.1 Build 196, when using Visio 2010, or Visio 2016. Product Line Satchwell MicroNet Environment Visio 2010 Visio 2016 VisiSat 2.1 Build 196 Cause Having installed VisiSat 2.1 Build 196, the customer cannot see any of the VisiSat tools. Visio 2010 is unlikely to be available Visio 2016 may be. Resolution To install VisiSat 2.1 Build 185, when Visio 2010 is being used, please carry out the following; Install Visio 2010. Start Visio 2010. Select the "Options" menu Select the "Trust Centre" menu Select the "Trust Centre Settings" menu Select the "Macro Settings" menu Choose "Enable All Macros" and save the changes. PLEASE NOTE - Visio 2016 is not supported by VisiSat 2.1 Build 196, and therefore has not been tested. Install Visio 2016 Start Visio 2016 Select the "Options" menu Select the "Trust Centre" menu Select the "Trust Centre Settings" menu Select the "Macro Settings" menu Choose "Enable All Macros" and save the changes. Select the "File Block Settings" menu Uncheck the boxes of the files you wish to open/save. Shutdown Visio and restart Windows. Restart Windows. Install Visisat. When opening Visisat you should now see the VisiSat tab in Visio 2010/2016 Please note, an occasional error has been seen when selecting the VisiSat "Options" menu, this error does not appear to cause any problems.

Issue Continuum runs very slowly. Taking up to two minutes to first startup. Generally opening up Continuum Explorer and any other objects are seen to be slower than normal as well. Product Line Andover Continuum Environment Continuum v1.94 and above Cause There was no Security Key connected and Continuum was running in Demo mode.  This symptom can also be caused by a missing or corrupt driver for the Security key, see Re-install of Continuum system and security key is not being recognized for details on re-installing the Security Key driver. Resolution Install valid Security Key and restart Continuum. Note: Want to know what features are supported in Demo mode? See How do we run Continuum in Demo mode and what features are available?

Issue Will the data in the Xenta Server still be intact after a power failure? How long is the "power outage protection time" for the various Xenta servers? Environment TAC Xenta 511 TAC Xenta 527 TAC Xenta 555 TAC Xenta 701 TAC Xenta 711 TAC Xenta 721 TAC Xenta 731 TAC Xenta 911 TAC Xenta 913 Cause Needs to know how the Xenta Server handles a power failure Resolution Power Outage Protection – Settings like configurations and web pages are stored in the non-volatile (flash) memory and will not be lost in the event of a power outage. A built-in capacitor maintains operation of the RAM memory for at least 72 hours in the event of a power outage. More information may be found in the TAC Xenta 500/700/911/913 Product Manual, chapter 2.1

Issue Popup window displays "License Invalid", "License Registry Error", "License on wrong machine" or other related error when starting the WPT software. Environment WPT software (any release) Cause License information stored in license file does not agree with the WPT/WPTL license information stored in the Windows registry. Resolution Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file.  NOTE: If the old computer has WorkPlace Tech release 4.0.0 or release 5.x.x prior to release 5.7, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed).  If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open".  This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. Locate the license file listed on line 1 of the WIB License Diagnostic display. Email the complete displayed text error message along with a zipped copy of the license file and diagnostic output file to Product Support A product support case will be created for you with the submitted information.  A product support engineer will contact you after reviewing your submitted information to assist you in correcting the issue.

Issue Summary view for Forced Value on I/O Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Automation Server or any of connected devices can potentially have many points or values. Need to discover which ones are in Forced state. Examples: A Digital Output with default value: Digital Output with Forced value and ON: Digital Output with Forced value and OFF: Resolution You can search for forced values using the search function in WorkStation. Enabling In device option will enable finding forced values on devices hosted under EBO, as SpaceLogic and EasyLogic devices, MP and RP controllers, IP-IO modules and RP-IO modules. For more information, see Searching for Forced Values . You can also view the search in WebStation:   In EBO 2023 or later, You can search for forced values in WebStation using Diagnostics. For more information, see Displaying a List of Forced Values in WebStation .  

  Issue List of Mercury Controller Types and Features Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Mercury Controller Types and features to use with Access Expert Resolution Overview Mercury controllers are an open architecture controller made by Mercury Security. Feenics currently supports the LP series boards, the series 2 and series 3 MR SIO series boards.   Mercury Controllers   Equivalent Features FN-C1501 EP1501 The EP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-C3202 EP1502 The EP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Reader Ports 1 SIO bus FN-C3200 EP2500 The EP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 SIO Buses FN-C4502 EP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 2 SIO Buses FN-LP1501 LP1501 The LP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 130 inputs and 130 Outputs 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-LP3202 LP1502 The LP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 520 inputs and 516 Outputs 2 Onboard Reader Ports 1 SIO bus FN-LP3200 LP2500 The LP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 SIO Buses FN-LP4502 LP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 Onboard Readers 2 SIO Buses FN-M5-IC M5-IC An intelligent control device for the replacement of the Casi PX, PXN and PXNplus CPU controller. The single controller supports up to 64 readers across multiple enclosures. 128 Access Levels per cardholder FN-M5-ICS M5-ICS A multi-device interface panel that is a direct retrofit of Software House’s Pro GCM module. A 64 reader capacity 600,000 Cardholders Mercury - PW6K1IC Prowatch 6000  The PW6K1IC is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 15,000 Cardholders 10,000 Transaction buffer 32 Access Levels per cardholder   EP Controllers - End of Life  Feenics used to support the EP Series controllers, however, they have been replaced with the LP series. Related article - Updating Mercury Firmware https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Updating-Firmware-on-an-SSC-or-Mercury-Controller/ta-p/410961  

Issue Cannot find a wiring diagram for the ETR800 Temperature Sensors Product Line TAC IA Series Environment ETR-800 temperature sensors Cause Not available in the Publication Zone Resolution Click the link to view and download the wiring diagram:  F-27619 ETR800 Sensors Wiring Instructions Click the link to view and download the data sheet (also available in the Publication Zone):  F-27601 ETR800 Sensors Data Sheet

Issue Cannot access SP-C web interface due to TLS error. Chrome error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Edge error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Firefox error: SSL_ERROR_UNSUPPORTED_VERSION Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause As per the table below, SP-C with OS  2.0.24 or lower does not support TLS 1.2.  A modern web browser will block access to sites that use TLS 1.0 or 1.1.     Resolution  If TLS 1.2 support is required, an OS upgrade to 2.0.25 or higher is required: Upgrade the controller's firmware to a version that supports HTTPS, as explained in:  AN 314 Security Expert - HTTPS Connection to the Security Expert Controller - Integration Guide If the current SP-C OS version is 2.0.24 or lower, contact Schneider Electric support to acquire the upgrade package and further documentation.

Issue How to create i2xxx and b3xxx controllers from a CSV dump file. Environment Continuum i2xxx Controllers b3xxx Controllers Cause In this scenario they wanted to create the beginning of a site database from CSV dump files before deploying on site.  Resolution It seems that when creating an i2 or b3 object, the path is also required when defining the comm port. Make sure to add the path to the Port field and this should allow the controller object to be created. See the original CSV I exported below, how it was modified, and then imported back in successfully. Original Export to CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_850,32,Comm1,Network1\ACX11_10th,11111,i2_850,i2920 Modified Import CSV InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920,i2920 Now, this import does complain about the CntrlType in the distribution Properties window but does create the controller and sets the type correctly. If you don't want any errors you can remove the CntrType attribute and the controller object will still be created but will default to a 240 controller. See below. Import CSV without CntrlType InfinityInfinetCtlr Name,InfinetId,Port,DeviceId,SerialNum,Alias i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920   This can then be changed to whatever controller you require through the controller Device object dialog.  

Issue A large room has multiple SpaceLogic Sensors SXWS (formerly SmartX sensor) and the temperature setpoint is changed in one of them. Is it possible for the temperature setpoint to be changed in the other sensors?  Product Line EcoStruxure Building Operation Environment Building Operation SpaceLogic Sensor Building Operation Room Controller (RPC) Building Operation RP-V VAV Cause In EBO (EcoStruxure Building Operation) version 3.1 a functionality called HMI references is introduced which can be used in this case. This new functionality makes it possible to have bi-directional bindings for the following value types in the RP series controller Blind position: analog value Occupancy override: digital value Fan speed: multistate value HVAC mode: multistate value Light level: analog value Selected scene: analog value Blind slat angle: analog value Temperature setpoint: analog value Resolution This is done by creating a value of the value types supporting the HMI reference functionality in the Application folder of the RP IP controller which the SpaceLogic Sensors are connected to. Then bind that value to the Display properties of each SpaceLogic Sensor       For example an Analog value is created in the Application folder of the RP-C and then bound to the Display Temperature Setpoint property of each connected SpaceLogic sensor. If then changing the Temperature setpoint from the RP-C that will be distributed to all SpaceLogic Sensors. But also if changing the Temperature setpoint in any of the SpaceLogic Sensors that value will be distributed to the other SpaceLogic Sensors and the RP-C.   To see an example on how this can be done please see video:  

Issue A new Niagara R2 UNC is installed with a license. The license installs correctly. After a reboot, the station fails to start. The standard output window displayed a fatal error as illustrated below: Product Line TAC IA Series Environment Niagara R2 Cause Certain foreign characters are not recognized by Tridium's License Generator.  In this case, a French character (with a symbol above the letter) was used in the customerSite name.  When the license was generated, the French character converted to a question mark (?): customerSite=Rotondle des S?urs The ? symbol is not recognized by Niagara.  So, when an UNC is rebooted, it will read the license file and stop when it comes to the customerSite name. Resolution Contact the factory to have the license modified. After correction by the factory, the customerSite line in the license example above reads: customerSite=Rotondle des Seurs

Issue In a Niagara G3 station, whenever someone logs into the graphics (with any web browser), the following error appears in the application director output: javax.baja.xml.XException: Root element must be "nav" [line 3]  at javax.baja.nav.NavFileDecoder.err(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.user.BUser.getHomePage(BUser.java)  at com.tridium.fox.sys.user.BUserChannel.fetchPrefs(BUserChannel.java)  at com.tridium.fox.sys.user.BUserChannel.process(BUserChannel.java)  at com.tridium.fox.sys.BFoxConnection.process(BFoxConnection.java)  at com.tridium.fox.session.SessionDispatcher.dispatch(SessionDispatcher.java)  at com.tridium.fox.session.SessionDispatcher.run(SessionDispatcher.java)  at java.lang.Thread.run(Unknown Source) Product Line TAC IA Series Environment Niagara G3 Cause The G3 user account has the nav file property pointed to a file that is not a nav file. Resolution Correct the nav file property setting.

Warning 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. Issue Proper configuration of supervised inputs, Mercury IO modules (i.e MR52) versus Continuum IO modules (AC1/AC1Plus) for transitioned Continuum sites. Product Line EcoStruxure Access Expert Environment Access Expert Controller Access Expert Reader Interface Access Expert Premise Software Access Expert Hosted Software Continuum AC-1 IO Module Cause Guidance is needed on the proper configuration of Access Expert custom EOL resistor tables in order to achieve full supervision of inputs associated with readers/doors. Full supervision in this context means not only being able to detect normal input operation (activation/deactivation) but also detection of attempts to tamper with the input's circuit (short circuit, open circuit, grounding, the introduction of foreign voltages, etc.) Please note that not all resistor configurations can detect all the various circuit issues, for example, a NO Series resistor configuration can't detect a cut in the wire given that the open circuit is the normal state for the Deactivated value of the input. The resistor configuration that provides the most supervision is the Series/Parallel configuration, using 2 resistors is possible to detect both short and open circuits. Resolution Continuum supported a fixed 10K Ohms resistance for supervised inputs, furthermore, Continuum IO modules (AC1/AC1Plus) transitioned to Access Expert under an AX-SSC controller continue to operate with Continuum firmware, this means that they do not support the custom EOL tables in Access Expert, the only configuration that is possible for AC1/AC1Plus modules is the mode of connection of the resistor (parallel, series or both).   Also, when using 2 resistor configuration, the placement of the resistor is different in Continuum compared to Mercury hardware   CONTINUUM When the switch is open only the resistor on the left is seen by the input. When the switch is closed, the two resistors are presented to the input in parallel with each other resulting in the input reading half the sum of the total resistance value.   SECURITY EXPERT       When the switch is open, the two resistors will be presented to the input in series with each other resulting in the input reading the sum of the two resistors value.  When the switch is closed only one resistor is presented to the input   For the above reasons, Continuum transitions sites where the AC1/AC1Plus has been replaced with Mercury hardware like the MR52 for example, need to configure one or more custom EOL table(s) for 10K resistors.   *** The sample tables provided below contain resistance values calculated to take into account wide variations in total supervised loop resistance due to wire distance, gauge etc., supervised loops should be installed in accordance to distance and gauge guidelines for wires as well as recommended resistor tolerance. It may be necessary to make adjustments to the resistance values in the tables on a site by site basis.   See below sample tables for all six possible 10K resistor configurations   Normally Open Parallel (10K-NO-P) Normally Closed Parallel (10K-NC-P) Normally Open Series (10K-NO-S) Normally Closed Series (10K-NC-S) Normally Open Series/Parallel (10K-NO-SP) Normally Closed Series/Parallel (10K-NC-SP)+ 1. Normally Open Parallel (10K-NO-P) 2. Normally Closed Parallel (10K-NC-P) 3. Normally Open Series (10K-NO-S) 4. Normally Closed Series (10K-NC-S) 5. Normally Open Series/Parallel (10K-NO-SP) 6. Normally Closed Series/Parallel (10K-NC-SP)+