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.

Issue Should the Touchscreen "Time Master" setting still be enabled when the Touchscreen is connected to a Xenta 555? Product Line Satchwell MicroNet Environment Satchwell MicroNet Xenta 555 Cause In standalone configurations, the Touchscreen is typically designated as the "Time Master" to ensure consistent time synchronization across connected controllers. When integrated with a Xenta 555, users may question whether this setting remains necessary. Resolution Yes, the Touchscreen should still be configured as the "Time Master" even when connected to a Xenta 555. The time synchronization behavior remains unchanged: The Touchscreen will broadcast the time every 10 minutes by default. This ensures that all connected controllers maintain accurate and synchronized time settings.

Issue Users require the default login credentials to access the Satchnet Pro Plus system. Product Line Satchwell MicroNet Environment Satchnet Pro Plus Cause The default access credentials are unknown or have not been documented during initial setup or troubleshooting. Resolution To access Satchnet Pro Plus, use the following default credentials: Username: super Password: user ⚠️ Note: These are factory default credentials. If they have been changed during configuration or by an administrator, they may no longer apply. Always verify with your site administrator or refer to system documentation if login fails.

Issue The LON communications option is not available for selection in the Network Options within the VisiSat software. Product Line Satchwell MicroNet Environment VisiSat software Cause The issue occurs because the LON Plug and Play (PnP) driver has not been installed on the system. Resolution   To resolve this issue: Install the LON Plug and Play driver. This driver is included as part of the VisiSat installation package. If the driver was not installed during the initial setup, it can be installed manually. Download the driver: Download the pcx1020Win.zip driver package.  Installation Steps: Extract the contents of the ZIP file. Run the installer and follow the on-screen instructions. Restart your PC after installation is complete. Verify Installation: Open VisiSat. Navigate to Network Options. Confirm that the LON communications option is now available for selection

Issue When using VisiSat or VisiView, selecting the option for the server to update controller time over the LAN does not work. Even after restarting the VisiSat server, the controller time remains unchanged. This affects both VisiSat and VisiView installations. Product Line Satchwell MicroNet Environment VisiSat VisiView SNP IAC Controllers Cause The root cause is currently unknown. No official fix is planned. Resolution To ensure controller time is updated: Install a Touchscreen (IAC-TS) If the site does not already have one, consider installing a Touchscreen device. Optional: Remote Mounting Kit (DDC 2601) This may be required depending on site layout. Manual Time Update The Touchscreen must be manually updated with the correct time. It will then propagate this time to controllers on the SNP LAN. Re-address Controllers Controllers must be re-addressed to align with the Touchscreen. Reconfigure VisiSat Project Update the VisiSat project to reflect the new controller addresses. Re-engineer VisiView Project (if applicable) If the site uses VisiView, the project must also be re-engineered to match the new controller configuration. Additional Notes This workaround does not automate time synchronization but provides a reliable manual method.

Issue VisiSat 2.1 allows two S-link sensor instances to be added to a controller scheme. Users have asked whether both instances can be used simultaneously. Product Line Satchwell MicroNet Environment MicroNet Touchscreen controllers VisiSat 2.1 Cause The VisiSat stencil permits two instances of the S-link sensor to be placed on a controller scheme. This may lead to confusion regarding the actual number of supported S-link sensors. Resolution Only one S-link sensor is supported per MicroNet controller. The second instance in the stencil was introduced to support addressable S-link sensors, but this functionality was not implemented.

Issue In a MicroNet MN 550 controller, the output of Instance 31 of the Priority Value Select object consistently returns a value of 0, while all other instances function correctly. Product Line Satchwell MicroNet Environment MicroNet MN 550 controller Cause This issue occurs due to a firmware limitation in earlier versions of the MicroNet 50 controller. Specifically, Instance 31 does not behave as expected unless the controller is updated. Resolution Upgrade the MicroNet 50 controller to Firmware Version 5, released in August 2008. This version resolves the issue with Instance 31. Refer to TPA-LOND-08-0014.00 for detailed information about Firmware Version 5.

Issue Can MN View be installed and run on Windows Server 2003 or newer operating systems? Product Line Satchwell MicroNet Environment MNView Windows Server 2003 and later (e.g., Server 2008, 2012, 2016, 2019, 2022) Cause MN View was originally designed and tested for compatibility with Windows XP. It has not been officially tested or validated on Windows Server 2003 or any subsequent versions. Compatibility issues may arise due to differences in file system handling, user access control, and drive labeling conventions in newer Windows Server environments. Resolution While MN View may install on Windows Server 2003 and later, successful operation is not guaranteed. One known issue is related to the installation drive: MN View must be installed on the C: drive. If the software installs to a different drive label (e.g., 😧 or E:), it will not function correctly. Recommendations: Ensure the target system has a C: drive available and set as the primary installation path. Run the installer with administrative privileges to avoid permission-related issues. If using a newer Windows Server version (2008 or later), consider compatibility mode settings or virtualization as a workaround. For production environments, it is recommended to use a system that matches the original tested platform (Windows XP).

Issue What is the maximum number of network variables that can be configured on Micronet ARCnet controllers? Product Line Satchwell MicroNet Environment Micronet controllers, all variants. Cause This article provides general guidance on the limits of Network Variable Received (NVR) and Network Variable Transmitted (NVT) settings within Micronet ARCnet controllers. Resolution All Micronet ARCnet controllers support the following configuration limits: Network Variable Received (NVR): Up to 6 Network Variable Transmitted (NVT): Up to 6 These limits apply across all controller variants within the Micronet ARCnet family. For detailed engineering guidance and best practices, refer to the latest VisiSat Engineering Guide. This document includes comprehensive information on ARCnet configuration, controller setup, and network design considerations. Refer to the VisiSat Engineering Guide for further information.

Issue After reinstalling VisiSat, all network and remote site information appears to be lost. Product Line Satchwell MicroNet Environment Visisat Cause During the uninstallation process, VisiSat removes the SITES.DAT file, which contains critical remote site configuration data. Resolution To preserve your remote site information during a VisiSat upgrade or reinstallation: Before Uninstalling: Navigate to C:\Satchwell\Binary\VisiSat\ . Copy the SITES.DAT file to a safe backup location. After Installing the New Version: Paste the backed-up SITES.DAT file back into the same directory: C:\Satchwell\Binary\VisiSat\SITES.DAT Verification: Launch VisiSat and confirm that your remote site and modem configurations are restored.