Issue Users encounter problems assigning entitlement licenses to AS-B and AS-P controllers in EcoStruxure Building Operation (EBO) 2022 (v4.0) and later using Device Administrator. Common symptoms include: Entitlement assignment fails for AS-B/AS-P. Assignment option is greyed out. Entitlement added but no license product appears. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA) Cause Starting with EBO 2022, Schneider Electric introduced a scalable licensing model that decouples hardware and software: Hardware is sold at a lower price. Sites purchase license bundles sized for their needs (Standalone, Standard, Enhanced, Full). Impact: Pre-2022 AS-P/AS-B models included most software capabilities and require upgrade SKUs when moving to EBO 2022 or later. Post-2022 Secure Boot AS-P and Scalable AS-B models require new entitlement bundles and support flexible licensing. Secure Boot adds cryptographic firmware validation. Resolution Verify Hardware Model AS-B: SXWASBXXX10001 → Requires upgrade bundle license. SXWASBXXHP10001 → Compatible with EBO 2022 and later bundle. AS-P: SXWASPXXX1000X → Requires upgrade bundle license. SXWASPSBX10001 → Compatible with EBO 2022 and later bundle. Check EBO Version For EBO 2022 and later, confirm entitlement compatibility. Assign Correct License Use upgrade license for older controllers. Activate via Device Administrator with internet access. Confirm Assignment After activation, assignment option should be enabled. If “No license product available” appears, verify entitlement type. Reference: Part Number Summary and Hardware-Software Compatibility Matrix. License Compatibility by Hardware Model Hardware Model EBO Min Version License Type Notes AS-P (SXWASPXXX1000X) 1.7.1 Upgrade Bundle Non-secure boot, pre-2022 hardware AS-P Secure Boot (SXWASPSBX10001) 2022 New Entitlement Bundle Standard, Enhanced, Full bundles AS-B (SXWASBXXX10001) 1.8.1 Upgrade Bundle Older AS-B models require upgrade AS-B Scalable (SXWASBXXHP10001) 2022 New Entitlement Bundle Standard or Full bundles  

Issue Zoning is reverting to the original state set on the RP-C controller after deployment or runtime changes. Product Line EcoStruxure Building Operation RP-C Series Controllers Environment Building Operation Workstation  RP-C firmware version: any Zoning configuration applied within a Custom 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. Cause Zoning functionality is being used within a Custom Type, which causes the zoning configuration to revert to its original state. This occurs because Custom Types are designed to enforce consistency across instances, and any runtime changes to zoning are overridden by the base definition of the Custom Type. Resolution To prevent zoning from reverting: Avoid using zoning within Custom Types. Zoning should be configured directly on individual RP-C controller instances rather than within a Custom Type. Recommended Practice: Create zoning configurations on the RP-C controller outside of any Custom Type. If a Custom Type is necessary for other aspects of the configuration, exclude zoning from the type definition and apply zoning manually to each instance.

Issue Users are unclear about how to complete the offline registration process in EcoStruxure Building Operation, particularly regarding the location and use of the System ID and Registration Code. Product Line EcoStruxure Building Operation Environment EBP Systems requiring offline activation Cause This confusion arises due to: Misinterpretation of the registration email: Users expect both the System ID and Registration Code to be included, but only the System ID is provided. Limited visibility of the registration code: The code is only shown in the browser on the online machine used for registration. Manual transfer requirement: Users may not realize that the registration code must be manually copied to the offline machine. Uncertainty around System ID resets: Users may not know how or when to reset the System ID, especially after hardware changes or reinstallation. Resolution System ID Visibility: The registration email contains only the System ID. The registration code is not included in the email. Where to Find the registration Code: The registration code is displayed in the web browser on the online machine during the registration process. This code must be manually copied and entered into the offline machine to complete activation. Resetting the System ID: If a reset is required, refer to the official guide: 🔗 Reset System ID – EcoStruxure Building Help Offline registration Instructions: 🔗 Offline Registration Guide 🔗 Registering Your System Offline Dialog Box

Issue How to calculate and display Mean Kinetic Temperature (MKT) for a temperature sensor in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment EBO version 3.2 or later (required for Log Processing Trend Log functionality) Trend logs available for temperature sensors Customer requirement: MKT based on hourly averages or 30-minute intervals over a 24-hour period Cause Mean Kinetic Temperature (MKT) is a derived temperature that represents the cumulative thermal stress experienced by a product over time. Unlike a simple average, MKT gives greater weight to higher temperatures because chemical degradation accelerates exponentially with temperature (based on the Arrhenius equation). Why it matters: Used in pharmaceutical, food, and logistics industries for stability studies and cold chain monitoring. Sensitive to temperature spikes—short excursions at high temperatures significantly increase MKT. Recognized by FDA, EMA, and ICH guidelines for stability and excursion analysis. Formula for equal time intervals: ​ Where: TK​ = Mean Kinetic Temperature (Kelvin) ΔH = Activation energy (~83.14472 kJ/mol for pharmaceuticals) R = Gas constant (0.008314472 kJ/mol·K) T1,T2,…Tn​ = Temperatures in Kelvin n = Number of readings EcoStruxure Building Operation does not have a native MKT function, so it must be implemented using custom calculations in Log Processing Trend Logs. Resolution Use three Log Processing Trend Logs to compute MKT from trend logs: Step 1: Prepare Hourly Average Temperature Create a Log Processing Trend Log named HourTemp. Period Interval: 1 hour Calculation Type: Average Input: Temperature trend log Persist Data: False Step 2: Calculate Denominator for MKT Formula Create a second Log Processing Trend Log named MKTdenom. Period Interval: 1 hour Calculation Type: Average Input: Reference HourTemp log Log Unit: Celsius → Target Unit: Kelvin Custom Calculation: var dH := 83.14472; // Activation energy (kJ mol^-1) var R := 0.008314472; // Gas constant (kJ mol^-1 K^-1) exp(-dH / (R * @(HourTemp))) // Temp in Kelvin Step 3: Compute Final MKT Create a third Log Processing Trend Log named MKT. Period Interval: 1 day Calculation Type: Summary Input: Reference MKTdenom Custom Calculation: var dH := 83.14472; var R := 0.008314472; ((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15 This converts back to Celsius. For Fahrenheit: (((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15) * (9/5) + 32 Important Note You may have to adjust the substitution code based on what you have named your log references. Ensure the variable names in the formula match your Log Processing Trend Log names. Additional Notes Ensure @(MKTdenom:Count) matches the number of samples per day. Adjust constants if customer specifications differ. Set the unit on the final Log Processing Trend Log (°C or °F). You can alarm on MKT values or display them in dashboards and trend charts.

Issue When upgrading a TAC Vista site to EcoStruxure Building Operation (EBO), LonWorks devices may not be discovered during the device discovery process in the AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P). Cause This issue typically occurs when the original TAC Vista database was configured using a third-party network management tool such as LonMaker or NL220. These tools can assign a custom domain ID to the LonWorks network. Default Domain ID in TAC Vista: 1/11 Default Domain ID in EBO: 1/254 If the domain ID used during the initial setup differs from EBO’s default, the AS-P will not detect devices on that domain. Resolution Identify the Current Domain ID Use the existing TAC Vista database to determine the domain ID configured on the LonWorks devices. Alternatively, use NodeUtil to identify the domain ID. Refer to the article: Finding LON devices under a different domain length with NodeUtil  Configure a Spare AS-P Set the domain ID on a spare AS-P to match the existing domain ID used in the site. For guidance, see: How to locate and change the LonWorks domain ID  Discover Devices Use the spare AS-P (now configured with the matching domain ID) to perform device discovery. The previously undetected devices should now appear and be accessible. Decommission Devices In the AS-P, navigate to the Actions menu for each discovered device. Select Decommission to revoke the device’s address and stop communication. Reintegrate Devices After decommissioning, re-add the devices to the LonWorks network. They should now be discoverable by an AS-P configured with the standard EBO domain ID (1/254).

Issue What is the maximum density of people that the Insight sensor (SXWREISBLE10001) can detect? Product Line Field Devices, EcoStruxure Building Operation Environment Insight sensor. Cause There is no official specification available that defines the exact density of people the Insight sensor can detect. This limitation makes it difficult to provide a precise number for maximum detection density. Resolution The maximum raw count for the people counter is 32 individuals within the detection area. Accuracy of detection is up to 90%, but it decreases as the number of people increases within the detection zone. The detection area is influenced by the mounting height of the sensor. A higher mounting position typically results in a larger detection area but may reduce accuracy in crowded conditions. Additional Notes For optimal performance, ensure the sensor is mounted according to published guidelines. Consider environmental factors such as lighting, movement patterns, and obstructions that may affect detection accuracy. If higher accuracy or density detection is required, consider deploying multiple sensors.

Issue The Bluetooth adapter fails to power on when connected to the SmartX Sensor. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause The “Commissioning Tool Enable” property is set to Off, which prevents the Bluetooth adapter from receiving power. Resolution To resolve this issue: Open WorkStation. Navigate to the Sensor Bus Settings. Locate the “Commissioning Tool Enable” property. Set the property to On. Save the changes and verify that the Bluetooth adapter powers on.    

Issue Customer is unable to install the Security Expert Mobile app on newer Android devices. The app does not appear in the Google Play Store. Reported devices and OS versions: Samsung A15/A16 running Android 16, OneUI 7 Samsung S22 Ultra running Android 15, OneUI 7 Product Line EcoStruxure Security Expert Environment  Application: Security Expert Mobile App Platform: Android devices Store: Google Play Store Affected OS: Android 15 and Android 16 UI Version: OneUI 7 Cause The updated version of the Security Expert Mobile app has not yet been released on the Android Play Store. It is undergoing Cyber Security penetration testing and review, which is expected to complete by end of Q1 2026. Resolution Currently, the Security Expert Mobile app is not available for download on Android. Follow these steps for a workaround: Use the Protege Mobile app as an alternative: Go to the Google Play Store link. Download and install Protege Mobile. Log in using existing Security Expert credentials: Open the Protege Mobile app. Enter your Security Expert username and password. Confirm connectivity to your Security Expert system. Plan for future availability: The official Security Expert Mobile app for Android will be released after the Cyber Security review process (ETA: end of Q1 2026).

Issue During the offline license activation process for EcoStruxure Building Operation, the process fails at Step 3 with the following error: FlexNet Embedded Error: FLXERR_RESPONSE_EXPIRED – The allowed time to process the response has expired. (Public Code: 1879048218 | Location: 4522804)  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Offline License Activation Cause This error occurs because the response file has exceeded its valid processing window. According to FlexNet documentation, the default expiration period for response files is 7 days from the time of generation. Additional contributing factors: System clocks on involved servers may be misaligned. The response file was not activated within the allowed time frame. Resolution Response file expiration is fixed and cannot be extended. Ensure that: All EBO servers involved in the activation process have accurate date/time settings. The response file is activated within 7 days of its creation. Best Practice: Always verify system time settings on all EBO servers before generating request files and activating response files.

Issue Automation Servers in an EcoStruxure Building Operation (EBO) system are unexpectedly changing their time. Investigation shows that a third-party BACnet IP device is sending BACnet Time Sync messages, causing the time drift. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet IP Cause A third-party BACnet device is broadcasting BACnet Time Synchronization messages on the IP network. By default, older EBO versions honor these messages, resulting in unintended time changes. Resolution Option 1: Modify Third-Party Device Configuration If possible, disable BACnet Time Sync on the third-party device. This is the most direct solution but depends on vendor capabilities. Option 2: Upgrade EBO From EBO 5.0.3.16010 (CP15) onward, AS-P controllers ignore BACnet Time Sync by default. This behavior is first included in: EBO 5.0.3.16010 (CP15) EBO 6.0.4.6003 (CP4) EBO 7.0.2 release To re-enable honoring BACnet Time Sync (if required): Configure a service_blacklist Add the following to the file to enable the time sync: <blacklist> <global> <enable-execute-time-sync/> </global> </blacklist>

Issue A user wants to deploy the RTD-DI-16 module with a 3-wire PT100 sensor in an environment where temperatures drop below -50°C. The concern is whether the module can accurately read such low temperatures. Product Line Field Devices. EcoStruxure Building Operation, Environment Building Operation I/O Module 16 Ch RTD Cause The RTD-DI-16 module is designed to operate within a temperature measurement range of -50°C to +150°C. This limitation is defined in the product datasheet and reflects the module’s internal resolution and calibration capabilities. Temperatures below -50°C fall outside the supported range, which means: Resolution and accuracy are guaranteed only within this specified range. Values below -50°C will not be read and may result in inaccurate or undefined behavior. Resolution Do not use RTD-DI-16 for applications requiring measurements below -50°C. Consider alternative modules or solutions that support extended temperature ranges, such as those designed for cryogenic or ultra-low temperature environments. While the PT100 sensor itself may be capable of measuring lower temperatures, the RTD-DI-16 module cannot process those values accurately.

Issue The IP rating for the ETD200-6 is not specified in the product documentation. Product Line Field Devices Environment ETD200-6. Cause Documentation does not include the enclosure's IP rating, leading to uncertainty during specification or installation. Resolution The enclosure of the ETD200-6 has an IP10 rating. Note: IP10 indicates limited protection against solid objects greater than 50 mm and no protection against liquids. This rating may affect installation environments where higher protection is required.

Issue Guidance is needed to enable reading of PIV (FIPS-201) cards using the AX-SSC controller and AC1 downstream devices within EcoStruxure Access Expert. Product Line EcoStruxure Access Expert Environment AX-SSC Cause Sites migrating from Continuum systems require a clear, step-by-step process to ensure PIV cards are properly enrolled and recognized in Access Expert. Resolution What is FASC-N? FASC-N stands for Federal Agency Smart Credential Number. It is a 25-byte (200-bit) identifier embedded in PIV cards, used to uniquely identify the cardholder across federal systems. It is composed of multiple fields, including: Agency Code System Code Credential Number Credential Series Credential Issue Person Identifier Organizational Category Organizational ID Person Org Association These fields are encoded using Packed Binary Coded Decimal (BCD) with odd parity, and together form a unique string used by access control systems to authenticate users. Understanding the FASC-N Structure In the Continuum Personnel object below, the fields highlighted are those that make up the FASC-N The PIV enrollment tool generates a character string when a card is presented. For example: 32013733334894141152472674132011 This string is composed of the following FASC-N fields: Field Value Agency Code 3201 System Code 3733 Credential Number 334894 Credential Series 1 Credential Issue 4 Person Identifier 1152472674 Organizational Category 1 Organizational ID 3201 Person Org Association 1 Note: If no enrollment tool is available, manually concatenate these fields in the order shown to create the FASC-N string. Configuration Steps 1. Card Format Setup Configure the card format in Access Expert as follows: Card Format Type: Standard Bit Length: 128 Large Encoded Card Number: ✅ Checked Convert 200 FASCN Bit to 128 Bit: ✅ Checked Card Number Starting Bit: 0 Card Number Bit Length: 128 2. AX-SSC Controller Configuration Ensure Enable Large Encoded Card Number is checked. Assign the card format created in Step 1 to the controller. 3. Person Object Configuration Navigate to Add Card Assignments. Paste the full FASC-N string into the Display Card Number field. This will auto-populate the Encoded Card Number field. Since the Encoded Card Number field is limited to 16 characters, truncate the string from the end until only 16 characters remain. Paste the full FASC-N string into the Hex Value field. ⚠️ Although labeled "Hex Value", enter the string as decimal digits. Save the Person object. Additional Notes Only the editors mentioned above require configuration for PIV card support. Editors such as Reader, Access Level, etc., do not need special configuration for PIV cards.

Issue After installing and configuring the LP4502 (online) and downstream devices per the Installation instructions, KGC devices remain offline. (See highlighted snapshot below) Link to Kone Integration Instructions: Access Expert Kone Elevator Integration  Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Kone Elevator Integration LP4502 Comm2 with Micro-B USB adapter (Pluggable USB2-OTGE100) Cause Using the LP4502 comm2 port with a Micro-B USB adapter for elevator communication on a separate subnet is NOT supported. Note: Other Elevator integrations (Thyssen Krupp, Otis) support this setup, which can cause confusion. Resolution 1. Use Comm1 for LP4502 to connect to the internet and site instance. 2. Ensure LP4502 and Kone elevator equipment are on the same subnet. 3. Configure site IT switch: Block internet-to-Kone communication. Allow local traffic on port 2005. KGC downstream IPs must communicate with the LP4502 primary NIC IP. Once completed, the LP4502 and the KGC downstreams will come online and will communicate with the Kone Elevator equipment. Summary KGC downstream devices fail to come online when LP4502 is configured using Comm2 with a Micro-B USB adapter. This setup is not supported for Kone Elevator integration.  

Issue The official documentation lacks clarity on how the EPU305LCD behaves in bi-directional mode, especially compared to unidirectional mode, and how reverse flow is interpreted. Product Line Field Devices. Environment EPU305LCD. Cause The confusion arises due to: Limited explanation in datasheets regarding how pressure differentials are calculated and displayed in bi-directional mode. Misinterpretation of analog output scaling, especially when switching between modes. Assumption that reverse flow is directly measured, whereas the sensor only calculates differential pressure between its ports. BMS misconfiguration, where systems expect unidirectional scaling and misinterpret negative values. Resolution Key Differences Between Modes Mode Display Range Behavior Unidirectional 0 to 50 Pa Only positive pressure differences are displayed. Bi-directional -50 to +50 Pa Displays both positive and negative pressure differences.   Note: The EPU305LCD does not directly measure reverse flow. It calculates the pressure differential between the positive and negative ports. Example Calculation Positive Port: 10 Pa Negative Port: 15 Pa Bi-directional Mode Result: -5 Pa Unidirectional Mode Result: 0 Pa (negative values are suppressed) Display Behavior When DIP switch 3 is enabled for bi-directional mode: Display shows “SEL -50” to indicate the selected range. Briefly shows “SET” when a new range is selected. Analog Output Ranges Configuration Analog Output Unidirectional Range Bi-directional Range 3-Wire 0–10 V / 0–5 V 0 to 50 Pa -50 to +50 Pa 2-Wire 4–20 mA 0 to 50 Pa -50 to +50 Pa   All ranges are configurable for either mode. Lower ranges are ideal for detecting small pressure differences. Higher ranges suit larger pressure measurements. Application Notes   Use bi-directional mode when monitoring both positive and negative pressure differentials is required. When switching modes, SCADA systems may show different readings due to scale changes—this is expected and normal.

Issue Can the SHO2XA2A humidity sensor be safely exposed to hydrogen peroxide (H₂O₂) during decontamination procedures? Product Line Field Devices. Environment SHO2XA2A. Cause The SHO2XA2A, along with SHD2 and CP series humidity sensors, are not resistant to hydrogen peroxide. Exposure to H₂O₂ can degrade sensor components, leading to inaccurate readings or device failure. Resolution For environments requiring decontamination with hydrogen peroxide, use the SH5 or ST5 series instead. These models feature probes specifically designed to withstand H₂O₂ exposure.

Issue SAFR Face Scan successfully detects faces but does not authenticate users or grant access.        Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 SAFR Scan Reader using OSDP Cause The default SAFR Scanner Access Feedback Timeout is set to 300 ms, which is too short for proper authentication. In some cases, physical impact during transit may also require light sensor recalibration. Resolution   Access the SAFR Scanner configuration web page and log in. Navigate to System > OSDP settings. Change the Access Feedback Timeout from 300 ms to 1000 ms and click Apply. Test authentication. If issues persist: Perform light sensor calibration (refer to SAFR documentation). SAFR portal: https://safr.com/safr-portal/ (login required)

Issue Confusion exists around which MicroNet controllers are supported in EcoStruxure Building Operation (EBO), especially during upgrades to EBO 7. The term “MicroNet” covers multiple product families with different protocols and support timelines. Product Line EcoStruxure Building Operation, TAC IA Series, Satchwell MicroNet Environment EcoStruxure Building Operation (EBO) MicroNet 2000 (NW8000) I/A MicroNet (MNL and MNB) Satchwell MicroNet Cause The term “MicroNet” can refer to multiple unique product ranges. In EBO documentation, MicroNet typically refers to Satchwell MicroNet, the European range of controllers using NCP, ARCnet, or LON protocol, which are not supported from EBO v4.0 onward. Other MicroNet families (MicroNet 2000 and I/A MicroNet) have different support histories. Resolution Refer to the table below for family types, lifecycle dates, and EBO support history: Family Protocol Introduced Withdrawn EBO Support History MicroNet 2000 (Barber Colman) MNet under ASD Late 1980s 2011 Supported up to EBO v3.2 Not supported in EBO 4.x–6.x Reintroduced in v7.0 I/A MicroNet – MNL Series LonWorks ~1998 2023 Supported in all SBO/EBO versions I/A MicroNet – MNB Series BACnet ~2003 2023 Supported in all SBO/EBO versions Satchwell MicroNet NCP / ARCnet / LON ~1998 2013 Supported up to EBO v3.2 Not supported from EBO v4.0 onward Additional Notes: MicroNet 2000 support was reintroduced in EBO 7 after being dropped in EBO 4–6. I/A MicroNet (MNL and MNB) support has never been removed from EBO. Satchwell MicroNet is unsupported from EBO v4 onward.

Issue When adjusting the Elevator Relay Time in the elevator reader, the option to save appears, but the setting does not persist. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Mercury MP1502 controller (version 08-2.4.0.653) OSDP Reader Cause The Access Expert Client has an issue with saving individual elevator relay time settings. Resolution Workaround: Navigate to Instance Settings and set the relay time globally. This applies the same relay time to all readers; individual reader settings cannot be saved until the underlying issue is resolved. Additional Notes: Client version: 25.9.26 Controller version: 08-2.4.0.653 A permanent fix will be provided in a future release.

Issue The NW8000 Optimal Start-Stop (OSS) block in EcoStruxure Building Operation (EBO) shows “Abnormal Input” status even when configuration appears correct. Bound parameters display valid values, but the object status remains abnormal. Product Line EcoStruxure Building Operation Environment Building Operation Server NW8000 OSS objects available for use outside NW8000 interface from EBO 2022 onward. Cause Incorrect Input Configuration: Both Heat Enable and Cool Enable inputs are set to ON (true) simultaneously, forcing conflicting modes. Missing Bindings: Required bindings to the Value and TimeToNextTransition properties of the digital schedule are not configured. Parameter Mismatch: Heat/Cool changeover temperatures and PreStart/PreStop tables must use correct values for the measurement system used (Fahrenheit/Celcius). Digital Schedule Misconfiguration: OSS relies on the TimeToNextTransition value from the referenced Digital Schedule. If the schedule has no events within the next 8 days, the schedule outputs a “maximum” value (millions of minutes until year 2106), causing OSS to enter Abnormal Input. Resolution Correct OSS Inputs: Set Heat Enable and Cool Enable to Null for normal operation. If forcing mode is required, only one input should be ON at a time. Both ON = Abnormal Input. Verify Bindings: Bind OSS block to: Digital Schedule → Value Digital Schedule → TimeToNextTransition Ensure schedule outputs correct ON/OFF states. Configure Digital Schedule Properly: Include an accurate weekly schedule and exceptions. Ensure at least one event exists within the next 8 days. Refer to: Adding a Weekly Event Adding a Date Exception Event Adding a Date Range Exception Event Adding a Calculated Exception Event Check Parameters: Heat/Cool changeover temps (OA values) must use correct values for the measurement system used (Fahrenheit/Celcius). PreStart/PreStop table range must match the measurement system used. Heat and Cool Enable Truth Table Heat Enable Cool Enable Actions EMPTY / NOT ACTIVE EMPTY / NOT ACTIVE Use Heat/Cool Changeover Temperatures OFF OFF No Heating or Cooling Pre-start or Pre-stop EMPTY / NOT ACTIVE OFF No Heating or Cooling Pre-start or Pre-stop OFF EMPTY / NOT ACTIVE No Heating or Cooling Pre-start or Pre-stop ON OFF / EMPTY / NOT ACTIVE Enable Heating for Start. Use Heat Start/Stop Tables OFF / EMPTY / NOT ACTIVE ON Enable Cooling for Start. Use Cool Start/Stop Tables ON ON Outputs set to ABNORMAL INPUT