Issue Which template should be used for the following TAC Xenta controllers? TAC Xenta 102-B TAC Xenta 102-VF TAC Xenta 102-EF Product Line TAC Vista Environment TAC Xenta 102-B TAC Xenta 102-VF TAC Xenta 102-EF Cause All three controller models—102-B, 102-VF, and 102-EF—share the same configuration and operational characteristics, allowing them to use a common template. Resolution Use the TAC Xenta 102 template in TAC Vista for all three models: 102-B 102-VF 102-EF This ensures consistent setup and functionality across these devices.

Issue Certain Xenta controllers and I/O modules support 10k thermistor temperature inputs. A common question arises regarding the specific type of 10k thermistor that is compatible—specifically, whether it should be Type 2 or Type 3. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always utilized 10k thermistors. More recently, some I/O modules and programmable controllers within the Xenta family (e.g., Xenta 420A and 450A) have also added support for 10k thermistor inputs. However, confusion often arises due to terminology differences. The terms “10k Type 2” and “10k Type 3” are specific to the Continuum product line and are not applicable to Xenta controllers. Resolution The 10k thermistors compatible with Xenta 42XA and 45XA I/O modules are the same as those used in the I/NET product line. These thermistors follow the Vishay Dale Curve #1 specification. For accurate configuration and calibration, refer to the Resistance vs. Temperature Conversion Tables provided in the linked PDF document below: 📄 Resistance vs Temperature Conversion – Vishay Dale.pdf

Issue Can TAC Xenta 401 and TAC Xenta 300 HW1 be upgraded to the latest system version? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 Cause Upgrading to the latest system version is recommended to benefit from the most recent product fixes, performance improvements, and feature enhancements. Resolution   TAC Xenta 300 and Xenta 401 units can be upgraded to any system version. However, HW1 versions are not compatible with EcoStruxure Building Operation. All hardware versions, including HW1, are supported in the TAC Vista Classic system.  

Issue Guidance is needed for configuring the Remote Alarm Manager (RAM), including understanding its components, available documentation, and script customization. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause RAM configuration involves multiple components such as: Configuration Controller Monitoring Scripts Output Interfaces Users may encounter challenges due to the complexity of these elements or lack of familiarity with scripting in RAM. Resolution To assist with setup and customization, three key guides are available: Operator’s Manual Basic usage and interface overview Ideal for day-to-day operations Engineer’s Manual More comprehensive than the Operator’s Manual Covers advanced configuration and troubleshooting Script Editor’s Guide Details on customizing and adapting scripts Useful for tailoring RAM behavior to specific site needs 📁 Location of Scripts: Scripts used by RAM are located in: C:\Satchwell\Binary\Remote Alarm Manager File extension: .scr Best practice: Copy and rename scripts before editing to preserve originals.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

Issue When attempting to directly download Menta code from a Xenta 280 or Xenta 300 controller to a Xenta 401 or Xenta 401:B controller, users may encounter the error: PARSER IO ERROR 13 Environment TAC Menta TAC Xenta 280 / Xenta 300 TAC Xenta 401 / Xenta 401:B Cause The Xenta 280 and 300 controllers have physical I/O points (e.g., M0-X1, M0-U2) directly on the device. These are referenced in the Menta application as M0 terminals. However, the Xenta 401 series does not have onboard physical I/O. When code containing M0 references is copied into a Xenta 401 Menta application, these I/O points become invalid. Since the points were copied manually (not created within the application or imported from a library), simulation mode does not detect the terminal mismatch. This leads to failed downloads and the PARSER IO ERROR 13 during direct serial communication. Resolution To resolve this issue: Open the Menta application for the Xenta 401. Navigate to Options > IO Configuration Table. Sort the table by the "Bound to" column to identify physical I/O references. Locate all points referencing M0 terminals. Reassign these points to valid physical I/O terminals appropriate for the Xenta 401 application.

Issue How can the TAC Xenta OP be used with a TAC Xenta 100-series controller? How does the OP identify which TAC Xenta 100 controller it's communicating with? Which OP mode should be used? Product Line TAC Vista Environment TAC Xenta OP TAC Xenta 101 TAC Xenta 102 TAC Xenta 121 TAC Xenta 122 Cause   The TAC Xenta OP panel allows access to input and output signals from a TAC Xenta 100-series controller. Identification of the specific controller is achieved via a Service Pin message. If connected directly to a TAC Xenta 100-series controller or a STR100-series device attached to it, the controller automatically sends a Service Pin message. If connected elsewhere on the network, you may need to manually press the Service Pin on the desired controller. For troubleshooting connectivity issues, refer to: “No Answer” on an OP when connecting to a Xenta 280/300/400 Resolution 1. Configure the TAC Xenta OP Plug in the TAC Xenta OP. Hold Back and Enter for 3 seconds to access the OP Service Menu. Scroll to Option 10: OP Mode. Set “Xenta 100” to ON using the + key. Press Enter. Set “Mode” to TAC using the + key. Press Enter twice to restart the OP. 2. Connect to a TAC Xenta 100-series Device Plug the OP into the OP jack on the TAC Xenta 100 controller or a connected STR100 device. When prompted “Press to access Xenta 100”, press Enter. At “Connecting to Xenta 100…”, wait or press the Service Pin on the controller. Press Down to proceed. 3. View and Modify Network Variables At the NV Index? prompt, use +/- to select the desired network variable index. Press Enter to view the signal. If the value is an input: Use +/- to modify the value. Press Enter to accept. If the signal is a bit-based application option: Press Enter to navigate between bits. Use + to change the bit value. Press Enter to confirm.

Issue Certain Xenta controllers and I/O modules are compatible with 1.8k thermistor temperature inputs. Users often seek clarification on which models support this and the specific temperature vs. resistance characteristics. Product Line TAC Vista Environment Xenta 122-FC Xenta 122-HP Xenta 121-FC Xenta 121-HP Xenta 200 Xenta 300 Xenta 420A Xenta 450A Cause Users need to understand the temperature vs. resistance curve for the 1.8k thermistors used in Xenta controllers, especially for the Xenta 300 series. Resolution All Xenta controllers and I/O modules except the Xenta 102-AX use the same 1.8k thermistor type: 1.8KA1. Below is a summarized Temperature vs. Resistance table for the 1.8KA1 thermistor: Temp (°C) Minimum kΩ Nominal kΩ Maximum kΩ -50.0   60.87  63.88  67.03  -45.0   45.41  47.5   49.68  -40.0   34.23  35.68  37.2   -35.0   26.04  27.07  28.13  -30.0   19.99  20.72  21.47  -25.0   15.48  16.0   16.54  -20.0   12.09  12.46  12.84  -15.0   9.512 9.779 10.05  -10.0   7.541 7.733 7.929 -5.0   6.021 6.16  6.301 0.0   4.84  4.94  5.042 5.0   3.916 3.988 4.061 10.0   3.189 3.24  3.293 15.0   2.612 2.649 2.686 20.0   2.151 2.177 2.209 25.0   1.782 1.8   1.818 30.0   1.478 1.496 1.514 35.0   1.233 1.25  1.267 40.0   1.033 1.049 1.065 45.0   0.8698 0.8848 0.9001 50.0   0.7357 0.7497 0.7639 55.0   0.6251 0.638 0.6511 60.0   0.5334 0.5453 0.5573 65.0   0.457 0.4679 0.479 70.0   0.3931 0.4031 0.4132 75.0   0.3395 0.3485 0.3578 80.0   0.2942 0.3025 0.311 85.0   0.2559 0.2634 0.2712 90.0   0.2233 0.2302 0.2373 95.0   0.1956 0.2019 0.2083 100.0   0.1718 0.1775 0.1835 105.0   0.1514 0.1566 0.1621 110.0   0.1338 0.1386 0.1436 115.0   0.1186 0.123 0.1276 120.0   0.1054 0.1095 0.1136 125.0   0.094 0.0977 0.1015 130.0   0.084 0.0874 0.0909 135.0   0.0753 0.0784 0.0816 140.0   0.0676 0.0705 0.0735 145.0   0.0609 0.0635 0.0663 150.0   0.0549 0.0574 0.0599

Issue The Xenta application may crash or become corrupted, resulting in one or more of the following symptoms: Controller not online in Vista Workstation I/O modules fail to associate with the Master Controller does not accept downloads via System Plug-in Product Line TAC Vista Environment Xenta version 3.61 or higher, Xenta 280 (281, 282, 283), Xenta 300 (301, 302), Xenta 401 Cause Crashes may occur during interrupted downloads or due to other system anomalies. Resolution Step 1: Power Cycle First, try cycling power to the controller to see if the issue resolves. Step 2: Forced Application Clear (if power cycle fails) If the controller still refuses to accept downloads from Vista or Menta: Create a Reset Dongle: Use an old Cat5 network cable. Cut off one end, leaving 4–6 inches of cable. Short-circuit the specific pins required for reset (refer to pinout diagram or manufacturer instructions). Perform the Reset: Power off the controller or remove it from the base plate. Insert the manufactured RJ45 jack into the RS-232 port. Power on the controller or reinsert it into the base plate. This will trigger a forced Clear Application. Remove the RJ45 jack. Cycle power again to complete a fresh boot-up.

Issue Users may want to configure a delay on EE_mess alarms in TAC Vista to avoid unnecessary or premature alarm triggers. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Cause The EE_mess object in TAC Vista does not support a delay attribute. This limitation means that alarms triggered by EE_mess events occur immediately, which can lead to excessive or unwanted alarm notifications. Resolution It is not possible to configure a delay on an EE_mess alarm in TAC Vista. The EE_mess object lacks a delay attribute and therefore cannot be modified to include one.

Issue When managing a large site, adding a new Xenta controller can be time-consuming if using the System Plug-in to create group bindings. This process often requires taking controllers offline. This article outlines a manual method to add group bindings efficiently without downtime. Product Line TAC Vista Environment TAC Vista Server NL2220 Cause The manual method is effective and reliable if the steps are followed correctly. It allows integration of a new Xenta controller into existing TAG 0 and TAG 1 bindings. Resolution Follow these steps to manually bind a new Xenta controller in NL220: Step 1: Enable Message Tags Connections Tree Open NL220 and go to Project Settings. Under the Trees tab, enable Message Tags Connections Tree. This will add a new tree view labeled Message Connections. Step 2: Add to TAG 0 Binding In the Message Connections tree, locate the TAG 0 connection (covers all Xenta controllers). Right-click TAG 0 and select Edit. In the Connection Window, switch to Subsystem View. Drag the TAG 0 from the new Xenta controller into the window. Click Update to apply changes to the database. Step 3: Add to TAG 1 Binding Locate the appropriate TAG 1 Xenta group for the new controller. Identify the correct TAG 1 connection by the controller name. Right-click the TAG 1 connection and select Edit. In the Connection Window, switch to Subsystem View. Drag the TAG 1 from the new Xenta controller into the window. Click Update to apply changes to the database.

Issue Can a single transformer be used to power both full-wave and half-wave devices, such as an AS-P controller and a DuraDrive actuator? Product Line Field Devices, EcoStruxure Building Operation, Andover Continuum, Satchwell MicroNet, TAC INET, TAC Vista Environment Full-wave and half-wave devices Cause There may be a need to simplify power distribution by using a single transformer for multiple device types. Understanding Rectifier Types Full-Wave Rectifiers Function: Converts both halves of the AC waveform into DC. Components: Uses four diodes in a bridge configuration. Efficiency: More efficient than half-wave rectifiers, providing a smoother DC output with less ripple. Half-Wave Rectifiers Function: Converts only one half of the AC waveform into DC. Components: Uses a single diode. Efficiency: Less efficient, resulting in higher ripple in the output voltage. Resolution Yes, a common transformer can be used to power both full-wave and half-wave devices provided the following conditions are met: External Isolation Transformers Non-isolated, connected devices of varying rectifier types require their own external isolation transformers. Use external isolation transformers for each device if there is doubt regarding whether an installation may cause equipment damage Transformer Sizing: Ensure the transformer’s VA rating exceeds the combined power requirements of all connected devices. Undersized transformers can lead to voltage drops, overheating, or device malfunction. Installation Guidelines: Before installation, refer to the document titled “Guidelines for Powering Multiple Actuators From a Common Transformer - Integration Guide.” Isolation & Compatibility: Confirm that devices do not interfere with each other’s operation when sharing a transformer. Avoid connecting devices with incompatible grounding or isolation requirements.

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 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 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.