Issue When manually binding the PowerFail system variable via a Numeric Input in the program header of a b3 controller, the value shown in the Binding Variables window may appear incorrectly (e.g., 1536 instead of a binary value like 1 or 0 ). Product Line EcoStruxure Building Operation Environment b3 controllers Script Program Editor Cause The Script Program Editor for b3 controllers does not recognize PowerFail as a predefined system variable. As a result, it displays an unexpected integer value in the Binding Variables window. Resolution Despite the incorrect display (e.g., 1536 ), the PowerFail variable functions correctly when bound to a Numeric Input. During compilation and execution, the system properly interprets the value. Best Practices for Scripting Treat PowerFail as a binary input: use logic based on True/False or ON/OFF . Ignore the displayed integer value in the Binding Variables window. Be aware that PowerFail is only active for one scan cycle immediately after power is restored following a loss. Example Usage Additional Notes This behavior is expected and does not impact the actual functionality of the PowerFail variable.

Issue When using External Log Storage in EBO, the following log message may appear: "Couldn't find a matching record in the internal storage, re-reading everything." Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation External Log Storage Cause This message indicates a failed synchronization attempt between EBO’s internal log storage and the configured external log storage system. It does not imply a misconfiguration or data corruption. EBO attempts to locate the last successfully transmitted record in its internal storage. If that record is missing—typically due to log purging based on retention settings—EBO cannot resume from that point and instead re-sends all available data to the external storage to ensure continuity. Common Scenario EBO is configured with a short log retention period (e.g., 1 day). The external log storage system is unavailable for a period longer than the retention window. The last record previously sent to external storage is purged from EBO’s internal storage before synchronization resumes. EBO cannot find the matching record and re-transmits all current log data. Resolution No action is required. This behavior is expected and intentional. It ensures that the external log storage receives all available data, even if some records were purged from internal storage during downtime. Recommendations Review and adjust log retention settings in EBO to align with the availability and recovery time objectives of the external log storage system. Ensure high availability of the external storage to minimize downtime and avoid unnecessary data re-transmission.

Issue Prior to XBuilder 5.1.1, it was not possible to change the Xenta Server type in an existing XBuilder project. This limitation made it difficult to migrate projects between different Xenta Server models without losing links, bindings, or configurations. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Earlier versions of XBuilder (prior to 5.1.1) did not support changing the Xenta Server type directly within the project’s network pane. This limitation required a manual workaround to migrate projects between different server types. Resolution Option 1: Upgrade to XBuilder 5.1.1 or Later If possible, upgrade to XBuilder 5.1.1 or newer, which allows direct modification of the target device type: Save the Project Locally: If the project is stored in a Vista database, open it in XBuilder. Go to File > Save As and save the project to your local machine. Reopen the Project: Close XBuilder. Reopen XBuilder and load the saved project from your PC. Change Target Device: In the Project menu, select Change Target Type... Choose the desired Xenta Server model from the drop-down list. Option 2: Manual Transfer (If Upgrade Is Not Possible) This method allows transferring an XBuilder project to a different Xenta Server while preserving graphics and object bindings. Ensure the target server supports the same or better Menta and User Graphic capabilities and can handle the existing network types. Example: Migrating from Xenta 555 (with LonWorks and Modbus networks) to Xenta 731. Step-by-Step Instructions 1. Create the New Xenta Server in Vista Open the Vista database containing the Xenta 555 project. Right-click the Xenta 555, select Edit to open the XBuilder project. In Vista, create a new Xenta 731 (name it similarly but not identically to the 555). 2. Transfer the LonWorks Network In Vista, drag and drop the LON network from the 555 to the 731. Right-click the 731, select Edit to open its XBuilder project. Rename the default folder in the System pane to match the top-level folder of the 555 project. In the 731 project, right-click the LON object in the Network pane and select Refresh Network from TAC Vista. 3. Transfer the Modbus Network In the 555 project: Right-click each Modbus device, select Edit Device Template. In the Device Editor, go to File > Save As... and save the template. In the 731 project: Recreate the Modbus network using the saved templates. 4. Transfer System Objects In the 555 project: Right-click each object under the top-level folder and select Copy. In the 731 project: Right-click the top-level folder and select Paste. Repeat for all objects and folders (note: selecting a folder includes all nested items). Do not copy the top-level folder itself; it cannot be pasted. Note: Graphics bindings are preserved. Reference paths are automatically updated (e.g., TAC_Xenta_555 becomes TAC_Xenta_731 ). However, some bindings (e.g., Time objects) may break and need to be manually rebound. 5. Final Steps Close the 555 project. In Vista, delete the Xenta 555. Generate the 731 project. When prompted to copy original TGML files, select Yes. Download the project to the Xenta 731. Tip: If the 555 project only contains a Modbus network, a similar process can be followed for standalone projects. Additional Notes Ensure compatibility between source and target servers regarding network types and resource capabilities. Always back up your projects before performing any migration.

Issue What are the NEMA or IP ratings for a specific product? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment All devices Cause Users often need to know whether a product is protected against: Water ingress Intrusion by foreign objects (e.g., dust, fingers) Resolution To determine a product’s protection level, refer to the Degrees of Protection document, which includes: IP Rating Chart NEMA Enclosure Rating Chart 🔹 Understanding IP Ratings An IP rating consists of two digits: First digit: Protection against solid foreign objects Second digit: Protection against water Examples: IP20: Protected against fingers (≥12.5 mm), no water protection IP10: Protected against objects up to 50 mm, no water protection If a product datasheet does not specify water ingress protection, the second digit defaults to 0. 🔹 Typical Building Products Many building automation products: Prevent insertion of fingers (≥12.5 mm) Do not offer water protection → Common rating: IP20 📎 Attachment Degrees of Protection.pdf (Includes full IP and NEMA charts)

Issue When using a Windows PC with Microsoft Visual Studio installed, an unexpected error message appears referencing Just-In-Time (JIT) Debugging. This can interrupt normal operations and confuse users unfamiliar with debugging tools. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Cause Visual Studio includes a feature called Just-In-Time Debugging, which attempts to launch the debugger when a program crashes or encounters a critical error. If enabled, this feature can interfere with other applications or workflows by prompting unexpected debug dialogs. Resolution To disable Just-In-Time Debugging, follow these steps: Open Visual Studio. Go to the Tools menu and select Options. In the Options dialog box: Expand the Debugging section. Select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, uncheck the relevant options: Managed Native Script Click OK to apply changes. Note: Disabling JIT debugging modifies a registry key. You must have Administrator privileges to make this change.

Issue When attempting to run LonMaker, the following errors may occur in succession: Could not listen on poet/tcp: The address specified is already in use (Error -2532) Database error: (Subsystem: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) Additional errors that may be caused by the same underlying issue: Problem connecting with the database server process: (Subsystem: LNS, #36) [DB#-2523] Error opening LCA Global database Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC IA Series, TAC Vista Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause  The issue is typically caused by a conflict between the Sentinel Protection Server and the POET Server, as both attempt to use the same port(s). Sentinel Protection Installer 7.6.1 installs the Sentinel Protection Server, which manages Sentinel SuperPro and UltraPro keys used with Satchwell Sigma and other products This service is not required for the dongle driver to function and can interfere with LonMaker’s operation. Refer to: Error: LNS #25 lcaErrDatabase for more technical details. Resolution To resolve the issue: Stop the Sentinel Protection Server: Open the Windows Services console: Press Windows + R , type services.msc , and press Enter. Locate Sentinel Protection Server. Right-click and select Stop. (Optional): Disable the service if not needed: Right-click > Properties > Set Startup type to Disabled. ✅ This will allow POET Server to operate without port conflicts.

Issue How to estimate the thermal load (in BTU/hr or Watts) that your controllers and equipment will produce. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Applicable to all electrical equipment used in building automation systems. Cause Understanding the thermal load is essential for: Sizing air conditioning systems Ensuring proper ventilation Avoiding overheating in enclosures Not all equipment datasheets provide thermal dissipation values, so manual calculation may be necessary. Resolution You can estimate the thermal load using the power consumption of each device. Formula To convert power (in Watts) to thermal load: BTU/hr = Power (W) × 3.412141633 Watts = Power (W) (already known) Note: 1 Watt = 3.412141633 BTU/hr Example Calculation Using the Continuum AC-1 I/O module: Power consumption: 2.6 W (without attached reader) Thermal load: BTU/hr = 2.6 × 3.412141633 = 8.87 BTU/hr Watts = 2.6 W If the reader is powered by the AC-1, include its power consumption in the total. International Units Reference Unit Conversion 1 Watt 3.412 BTU/hr 1 BTU/hr 0.293 Watts Additional Notes Use this method for any device where power consumption is known. For grouped equipment, sum the total wattage before converting. Consider using an online calculator for quick conversions.

Issue A BS5308 Part 1 Type 1 cable was installed under the assumption it would be used for Modbus communications. However, it was later determined that the application required M-Bus communication. This raised the question: Is the BS5308 cable suitable for M-Bus? Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC Vista Environment M-Bus communication systems BS5308 Part 1 Type 1 cable (2-pair, individually screened) Cause The incorrect assumption that the communication protocol would be Modbus led to the installation of a BS5308 cable. Upon discovering that M-Bus was required, concerns arose regarding the cable’s compatibility with M-Bus communication standards. Resolution While the recommended cable for M-Bus communication is J-Y(ST)Y, which is specifically designed for indoor telephone applications and optimized for analog/digital signal transmission, the BS5308 Part 1 Type 1 cable can still be used for M-Bus under certain conditions. Key characteristics of J-Y(ST)Y cable: Designed for indoor telephone and data transmission Aluminium-laminated plastic foil static screen with tin-plated drain wire to minimize high-frequency electromagnetic interference Twisted pair (TP) structure to reduce crosstalk BS5308 Part 1 Type 1 cable considerations: Originally designed for instrumentation and control applications Features individually screened pairs, which can help reduce interference Electrical characteristics must be evaluated to ensure compatibility with M-Bus requirements Conclusion: Yes, the BS5308 Part 1 Type 1, 2-pair individually screened cable can be used for M-Bus communications, provided that its electrical characteristics meet the M-Bus system requirements. Refer to the attached calculation chart and datasheets for detailed compatibility analysis.

Issue The H909HV-S6 current transformer does not change state, even though current flow is present. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet Environment H909HV-S6 Current Transformer Cause The issue is due to incorrect wiring between the current transformer and the DDC controller. The installation instructions may appear to indicate that four connections are required to the DDC controller. However, this is not correct—only two connections are necessary. Resolution To resolve the issue: Review the wiring diagram in the installation instructions carefully. Ensure that only two connections are made between the CT and the DDC controller: The status output has two terminal sets, but only one connection is required from each set. Correct the wiring to match the proper configuration. 📄 Download the H909HV-S6 Datasheet

Issue Technicians require accurate resistance values for Satchwell and Sontay sensors to validate performance and troubleshoot temperature-related issues. Product Line Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet Environment Satchwell BAS & Sigma Satchwell MicroNet Cause Resistance values vary by sensor type and temperature. Having a reference chart ensures correct diagnostics and sensor replacement. Resolution Below is a reference table showing resistance values for various Satchwell and Sontay sensor types across a range of temperatures. Sensor Resistance Table DRT, DOT, DDT, DWT, DST, DOS   DD 1401, DW 1202, DR 2253, DWS 1301   DW 1204, DWS 1202   DO 2202       Sontay SAT 1   Sontay SAT 2   Sontay SAT 3   Sontay SAT 4                       °C Ohms   °C Ohms   °C Ohms   °C Ohms                       -40 9711   0 2094   20 2708   -40 2317 -35 9604   1 2079   25 2592   -35 2246 -30 9465   2 2063   30 2474   -30 2163 -25 9288   3 2046   35 2346   -25 2067 -20 9067   4 2027   40 2216   -20 1962 -15 8796   5 2010   45 2086   -15 1849 -10 8472   6 1992   50 1950   -10 1733 -5 8093   7 1973   55 1818   -5 1617 0 7661   8 1953   56 1792   0 1504 5 7182   9 1934   57 1766   5 1397 10 6667   10 1911   58 1741   10 1298 15 6126   11 1892   59 1718   15 1208 20 5573   12 1872   60 1694   20 1128 25 5025   13 1851   61 1669   25 1057 30 4492   14 1830   62 1646   30 996 35 3987   15 1809   63 1622   35 942 40 3518   16 1787   64 1600   40 897 45 3089   17 1764   65 1578       50 2702   18 1740   66 1553       55 2358   19 1716   67 1530       60 2056   20 1690   68 1508       65 1792   21 1667   69 1484       70 1563   22 1644   70 1461       75 1364   23 1621   71 1439       80 1193   24 1596   72 1417       85 1047   25 1574   73 1396       90 921   26 1549   74 1375       95 815   27 1524   75 1353       100 722   28 1500   76 1333       105 643   29 1476   77 1312       110 575   30 1452   78 1293       115 517   31 1430   79 1276       120 466   32 1406   80 1258       125 423   33 1383   81 1240       130 386   34 1359   82 1222       135 353   35 1336   83 1205       140 324   36 1312   84 1188       145 300   37 1289   85 1171       150 278   38 1267   86 1154             39 1243   87 1138             40 1219   88 1122             41 1198   89 1107             42 1176   90 1089             43 1155   91 1075             44 1134   92 1061             45 1113   93 1047             46 1092   94 1033             47 1072   95 1020             48 1052   96 1004             49 1033   97 991             50 1013   98 978                   99 964                   100 950       📎 Note: These values are approximate and may vary slightly depending on installation conditions. Always refer to the official datasheet or use calibrated instruments for precise diagnostics. Click here to download a pdf with this information.

Issue Continuum 1.9x and above may fail to install correctly on domain-joined machines. A common error during installation is: "You must have local NT administrative privileges to run this application." Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows 7, 8, 10, 11, Server 2016 and later SQL 2005, 2008, 2012 and later Cause Microsoft SQL installations require elevated local administrator privileges. Domain accounts often lack these rights due to group policies or security restrictions. A local administrator account is required to complete the installation successfully. Resolution Resolution: Create a Local Administrator Account 🔹 Windows 7 / 8 / 10 (Classic Method) Open Control Panel → Administrative Tools → Computer Management Navigate to Local Users and Groups → Users Right-click in the right pane → New User Enter a username and password Uncheck User must change password at next logon Check Password never expires Click Create → Close Right-click the new user → Properties → Member Of tab Click Add → Type Administrators → Check Names → OK 🔹 Windows 10 / 11 (Modern Method) Open Settings → Accounts → Family & other users Under Other users, click Add someone else to this PC Select I don’t have this person’s sign-in information → Add a user without a Microsoft account Enter a username and password After creation, click the account → Change account type Set to Administrator → OK 🔹 Windows Server 2016+ Open Server Manager → Tools → Computer Management Go to Local Users and Groups → Users Right-click → New User Fill in the details and assign to the Administrators group as above 🔹 Command Line (All Versions) Run the following commands in Command Prompt (Admin): net user LocalAdmin P@ssw0rd123 /add net localgroup Administrators LocalAdmin /add Replace LocalAdmin and P@ssw0rd123 with your preferred username and password. 🔐 Additional Notes Ensure the account is local, not domain-based. You may need to disable UAC temporarily for installation, but re-enable it afterward. For Server OS, PowerShell can be used for automation if needed.

Issue There is a lack of clarity regarding the necessary preparation steps for upgrading a Continuum LAN system. Inadequate planning can lead to compatibility issues, data loss, or system downtime. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Cause Upgrades without proper preparation may result in: Software and hardware incompatibility Data integrity risks Extended system outages Resolution To ensure a successful upgrade, follow these best practices: 1. Review Compatibility Matrices Consult the Continuum Compatibility Matrix and Continuum Video Compatibility Matrix. Use these tools to plan upgrades for all supporting software and hardware. 2. Verify Software Compatibility Ensure that .NET and SQL Server versions are compatible with the target Continuum version before starting the upgrade. 3. Update Controller Firmware Older CX controllers (firmware ≤ 1.500029) use a different handle algorithm and must be upgraded prior to the LAN upgrade. Other controllers can be upgraded after the front-end systems are updated. 4. Assess Hardware Requirements Evaluate all current computer hardware, especially the Continuum Database Server. Choose hardware based on customer needs and system requirements. This decision should involve engineering expertise and likely the customer’s IT department. 5. Consider Off-Site Preparation When deploying a new database server, it may be beneficial to build and prepare the Continuum server and database off-site. 6. Engage Experienced Engineers The upgrade process is complex and should be led by an engineer experienced in Continuum LAN upgrades. This ensures proper execution and provides mentorship for technicians involved in future upgrades.

Issue Clarification is needed on whether the Xenta 555 controller can synchronize time with MicroNet controllers connected under its LAN. Product Line Satchwell MicroNet Environment Xenta 555 MicroNet Controller Cause MicroNet controllers require accurate time synchronization for scheduled operations and logging. The Xenta 555 is often used as a central controller in such setups, raising the question of its ability to propagate time updates. Resolution Yes, the Xenta 555 does update the time on MicroNet controllers under its LAN. The Xenta 555 uses Network Time Protocol (NTP)—a standard TCP/IP protocol—to synchronize its internal clock. This synchronized time is then distributed to connected MicroNet controllers, ensuring consistent timekeeping across the system.

Issue The Stopwatch object in the VisiSat Bubbleland object list behaves erratically when configured to trigger on a daily basis. Specifically, when set to issue a pulse once per day, it may issue multiple pulses (2–3 times) within the same day. Product Line Satchwell MicroNet Environment VisiSat Cause This is due to a software/firmware error. Note: No fix is currently planned. Resolution Avoid using days as the unit for the stopwatch trigger. Instead, use hours to achieve the desired timing: Replace 7 days with 168 hours  Replace 14 days with 336 hours If you need to display the value as days or weeks in MicroNet View, follow these steps: Steps to Convert and Display in MicroNet View In VisiSat: Locate the Stopwatch object Add the Stopwatch Rollover to the points list Go to Tools > Export and export the points list to MicroNet View In MicroNet View (Development Mode / Window Maker): Open the relevant window Add a text field (e.g., "###" ) to display the value Add the tag for the stopwatch rollover value To display the value in weeks, append /24 to the tag name Example: TagName/24 Using a Data Change Script: Create a tag with appropriate min/max values Add a data change script to convert and display the value in weeks Set the "###" field to User Inputs > Analog Link it to the data change tag To Set Rollover in Days: Click the days set area Enter the desired number of days Press Return to confirm ⚠️ Remember: The controller stores the value in hours (e.g., 14 days = 336 hours). The conversion to days is only for display in the MicroNet View interface.

Issue Lost or unknown access password for a MicroNet View project. Product Line Satchwell MicroNet Environment MicroNet View Cause User password for MicroNet View has been lost or forgotten. Resolution   Important: Always back up your MicroNet View project before making any changes. Follow these steps to reset the password: Locate the default password file: Navigate to: C:\MicroNet\Projects\Project1\View\password.bin Copy the password file: Make a copy of password.bin from the default project. Paste into your project: Replace the password file in your project directory: C:\MicroNet\Projects\YourProjectName\View\password.bin This will reset the password using the default credentials from the original project.

Issue By default, VisiSat only allows up to three property windows to be open simultaneously. This limitation can hinder productivity when programming complex controllers. Product Line Satchwell MicroNet Environment VisiSat MN50 Series controllers Cause The limitation is defined in the project’s configuration file ( settings.ini ). The default setting restricts the number of property windows to three. Resolution To increase the number of property windows: Locate the settings.ini file in your project directory. Open the file using a text editor (e.g., Notepad). Find the line: Number of Property Forms=3 Change it to: Number of Property Forms=9 You can adjust the number to suit your workflow, up to the maximum supported by your system. Save the file and restart VisiSat for the changes to take effect.

Issue When accessing an SNP network using TAC Vista, no values are displayed. Product Line Satchwell MicroNet, TAC Vista Environment Satchwell MicroNet TAC Vista Cause TAC Vista does not support LAN number 0. If the XBuilder-exported file assigns a LAN number of 0, TAC Vista will fail to display values from the SNP network. Resolution To resolve this issue: Locate the XBuilder Exported File Find the .XMLM file generated by XBuilder. Edit the File Open the .XMLM file using a text editor such as Notepad. Modify the LAN Number Search for any instance where the LAN number is set to 0 . Change the LAN number from 0 to 1 . Save the File Save the changes and reload the file in TAC Vista. Verify Reconnect to the SNP network and confirm that values are now displayed correctly.

Issue Users may need to log into MicroNet View but are unaware of the default username and password. Product Line Satchwell MicroNet Environment MicroNet View Cause Default credentials are required for initial access or after a system reset. These credentials are often needed during setup or troubleshooting. Resolution To access MicroNet View, use the following default credentials: Username: Administrator Password: MicroNet ⚠️ Important: For security reasons, it is strongly recommended to change the default password after initial login to prevent unauthorized access. Additional Information: These credentials apply to factory-default configurations. If the credentials have been changed and are unknown, contact your system administrator or Schneider Electric support for assistance.

Issue When selecting a graphic from the Xenta 555 menu structure, the graphic window opens but only displays the Close (X) button. No other visual elements or data are shown. Product Line Satchwell MicroNet Environment Xenta 555 Micronet Cause This issue is typically caused by an incompatible or outdated version of the Java™ Runtime Environment (JRE). The graphics engine relies on specific Java components that may not function correctly with older versions. Resolution To resolve the issue: Update Java Runtime Environment Download and install the latest supported version of Java™ Runtime from the official Java website. Ensure that the version is compatible with the Xenta 555 and your operating system. Clear Java Cache Open the Java Control Panel → General → Temporary Internet Files → Delete Files. Restart the browser or application accessing the Xenta 555 graphics. Verify Browser Compatibility Use a browser that supports Java applets (e.g., Internet Explorer or legacy versions of Firefox). Ensure that Java is enabled in the browser settings.

Issue MicroNet controllers using VisiSat do not provide a direct enthalpy value. The existing enthalpy object in Bubbleland only outputs a digital state based on comparison logic, which is insufficient for applications requiring actual enthalpy values. Product Line Satchwell MicroNet Environment Satchwell MicroNet VisiSat Cause The Bubbleland stencil includes an enthalpy object that provides a digital output (on/off) based on temperature and humidity comparisons. However, it lacks a standard object to calculate and output a true enthalpy value. Resolution Option 1: Create a Simple Bubbleland Scheme Use temperature and humidity as dynamic inputs. Use fixed values for other parameters (e.g., pressure = 1 bar). This provides an approximate enthalpy value. A downloadable custom object is available to simplify this process. 🔗 Download Enthalpy Custom Object.zip Installation Instructions: Unzip the file to create a Satchwell folder. Copy the folder to your C:\ drive. Files will be placed in the correct VisiSat directories automatically. ✅ Option 2: Use Preconfigured Controller Schemes Download configuration files for your specific controller model. Load the scheme with enthalpy objects directly into the controller. 📦 Available Downloads: Custom Enthalpy Scheme 300.zip Custom Enthalpy Scheme 350.zip Custom Enthalpy Scheme 440.zip Custom Enthalpy Scheme 450.zip Custom Enthalpy Scheme 500.zip Custom Enthalpy Scheme 550.zip Custom Enthalpy Scheme 620.zip Custom Enthalpy Scheme 650.zip ✅ Option 3: Use a Prebuilt VisiSat Project Includes all controller types with enthalpy schemes. Configuration files are saved under a Configs folder within the project. 📦 Download Full VisiSat Project (4.2 MB) Additional Notes These schemes are intended to provide estimated enthalpy values for operational use. For precise calculations, consider integrating external sensors or software.