Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue After importing a point list into XBuilder and downloading the project to the Xenta Server, all values in TAC Vista and on the Xenta Server’s values page display as “Invalid Address.” Despite this, VisiSat continues to function correctly, and connections to controllers via the Xenta Server IP tunnel remain operational. Product Line Satchwell MicroNet, TAC Vista Environment Satchwell MicroNet TAC Vista Xenta Server Cause This issue typically occurs due to duplicate point addresses in the point list. Specifically, two or more points may have different names but share the same table reference, which causes address conflicts during import. Resolution To resolve this issue: Create a New Point List in VisiSat: Open VisiSat and create a new, blank point list. Copy Points to the New List: Select all points from the original point list. Paste them into the new point list. Identify and Resolve Duplicates: During the paste operation, VisiSat will display an error message if any point addresses are duplicated. Review and correct the duplicated entries until no errors are reported. Export and Re-import the Point List: Export the corrected point list from VisiSat for use in XBuilder. Import the updated point list into XBuilder. Download to the Xenta Server: Re-download the project to the Xenta Server. Verify that the values now display correctly in TAC Vista and the Xenta Server. Additional Notes: Ensure that each point in the point list has a unique table reference to avoid address conflicts. This issue is specific to projects involving imported NCP or SNP networks.

Issue What are the default access-level passwords for a MicroNet Touchscreen? Product Line Satchwell MicroNet Environment MicroNet Touchscreen controllers Cause Default passwords are required to access various levels of functionality on the MicroNet Touchscreen. These passwords may be changed during system configuration. Resolution Access Level Default Password Read Only 1234 Read/Write 4321 Super User 1024 ACK Alarm 2513 🔧 Note: These passwords can be modified using VisiSat software. To view or change them, connect to the Touchscreen and check the password settings under its properties.

Issue Satchwell IAC 600 controllers remain offline when connected to a Xenta 555 device. Product Line Satchwell MicroNet Environment IAC 600 Xenta 555 Cause The issue occurs because the DDC253 firmware installed on the IAC 600 controller is not compatible with the Xenta 555. This firmware version was specifically designed for IAC 600 units with unique hardware configurations and cannot be upgraded or modified. Resolution To restore communication: Replace the IAC 600 controller with a compatible version that does not use the DDC253 firmware. Firmware updates are not possible for this specific hardware/firmware combination.

Issue Users may need to access the MicroNet LCD interface but are unsure of the default password required for initial login. Product Line Satchwell MicroNet Environment Satchwell MicroNet Controllers MicroNet LCD Interface Cause The default password is required to access the LCD interface. If it has been changed during programming, users may need to retrieve or reset it. Resolution Default Password: 1234 This is the factory-set password for MicroNet LCD interfaces. Password Change Considerations: The default password can be changed during controller programming. For 100 Series MicroNet controllers, if the password has been changed, a backup of the controller configuration is required to identify the current password. For 50 Series MicroNet controllers, when uploading the controller configuration, ensure the LCD configuration is also uploaded. The password can be found under Properties in the LCD configuration area.

Issue Importing a VisiSat pointslist StruxureWare reports a limit issue and suggests the import is complete. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment StruxureWare Building Operation 1.3/1.3 SP1 Cause On one of the VisiSat points being import, the alarm limits have been incorrectly set. Although StruxureWare Building Operation 1.3/1.3 SP1 reports that the import completed in X minutes and X second, the import would have failed to complete due to the stated issue. Unfortunately the reported limit issue can effect 100 points or just the 1 point. The specific point or points identity is not highlighted in the trace file. Resolution Locate the point and check the alarm limits are entered correctly. The example below show the upper limit and lower limit are reversed. Change it so the upper limit is above the lower limit.

Issue Will VisiSat Version 2.1 Build 148 work with Microsoft Visio 2002? Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 148 Visio 2002 Cause VisiSat Version 2.1 is designed to work with Visio 2003 and later. Compatibility with Visio 2002 is not supported due to architectural differences and feature limitations in the older version. Resolution To ensure full functionality and support, VisiSat Version 2.1 Build 148 must be used with Visio 2003. This requirement is documented in the official VisiSat 2.1 Configuration Tool Datasheet.

Issue Upgrading projects created in VisiSat 1.1 or 1.2 to the VisiSat 2.* format using the VisiSat 2.1 upgrade program. Product Line Satchwell MicroNet Environment VisiSat 1.1 / 1.2 VisiSat 2.0 / 2.1 Projects originally created in VisiSat 1.* Cause VisiSat 1.* stored all project data directly under the main project folder. VisiSat 2.* introduced a new structure, storing project data and controller configurations within a subfolder named "VisiSat" inside the main project folder. Resolution To successfully upgrade a project from VisiSat 1.* to VisiSat 2.*: ✅ Use the official upgrade program provided with VisiSat 2.0 or 2.1. ❌ Do NOT manually copy VisiSat 1.* files into a folder named "VisiSat" under your project directory and attempt to run them in VisiSat 2.*. Doing so will result in project errors due to differences in how point information is stored and accessed between versions. Important Note: VisiSat 2.* uses a completely different method for storing and accessing point information compared to VisiSat 1.*. Manual migration will likely cause compatibility issues.

Issue When multiple control objects are used for multi-loop control, the lower stage output antler of a control loop may fail to function correctly. In some cases, the Antler node connection incorrectly points to '---' , indicating a broken or undefined link. Product Line Satchwell MicroNet Environment MicroNet 50 Series Multi Loop Control objects Cause This issue arises due to a firmware limitation in earlier versions of the MicroNet 50 controller. Specifically, the lower stage output antler fails to maintain proper linkage when multiple control loops are configured, resulting in a loss of control signal routing. Resolution The issue has been resolved in MicroNet 50 Firmware Version 5, released in August 2008. For detailed information on this firmware update, refer to technical publication TPA-LOND-08-0014.00.

Issue Users may notice numerous files located in the following directory: C:\Micronet\binary\vcommon These files have names such as 20101024.AEH to 20121119.AEH and vary in size from 1 KB to 750 MB. Over time, these files can accumulate and consume significant disk space. Product Line Satchwell MicroNet Environment MicroNet View Cause The .AEH file extension stands for Alarm Event Handler. These files are generated by the Wonderware Logger (WWLogger) and contain historical data related to application events, including InTouch error and warning messages. Resolution To manage disk space and maintain system performance, it is safe to delete certain historical .AEH files. Refer to the document below for guidance on which files can be safely removed: 📄 PIB – 00.07.10-3: Files That Can Be Deleted From MicroNet View Note: Always ensure backups are taken before deleting any files.

Issue When accessing the Xenta 555 web interface, certain pages—such as the Time Schedule—may appear grayed out or inaccessible. Product Line Satchwell MicroNet Environment Xenta 555 Controller Xbuilder Software Cause This issue typically occurs due to a mismatch between the Xenta 555 firmware version and the Xbuilder software version used to create or edit the project. Resolution To resolve this issue, ensure that the Xbuilder version matches the firmware version of your Xenta 555 device. Below is a compatibility matrix: Xenta Firmware Version Required Xbuilder Version 5.00 5.00 5.01 5.01 5.02 5.02 5.03 5.03 5.10 5.10 5.11 5.11 5.12 5.12 5.13 5.13 Example: If your Xenta 555 is running firmware version 5.1.1, and your project was created in Xbuilder 5.0.3, follow these steps: Install Xbuilder 5.1.1. Open your project in Xbuilder 5.1.1. The project will be automatically upgraded. Upload the upgraded project to the Xenta 555.

Issue What is the accuracy of the I/A Series MN-Sx S-Link wall sensors? This information is required for project submittal documentation. Product Line Field Devices, Satchwell MicroNet, TAC IA Series Environment MN-SX MN-S1 MN-S2 MN-S3 MN-S4 MN-S4-FCS MN-S5 S-Link Cause Sensor accuracy specifications are needed to meet submittal requirements for building automation projects. Resolution Refer to document TPA-RKFD-09-0021.00 for factory-calibrated accuracy and stability specifications. Sensor Specifications: Element Type: Precision Thermistor Operating Temperature Range: 0 – 50 °C (32 – 122 °F) Stability: < 0.02 °C (< 0.04 °F) per year (typical) Accuracy: Temperature °C Accuracy Temperature °F Accuracy 24 °C ± 0.6 °C 75 °F ± 1.0 °F 0 to 50 °C ± 1.7 °C 32 to 122 °F ± 3.0 °F

Issue You need to configure an output to latch (activate) when any input from a group is enabled (open), and unlatch (deactivate) when all inputs are disabled (closed). Product Line EcoStruxure Security Expert Environment Security Expert Cause Uncertainty around how to use Security Expert's Area and Output features to achieve this logic. Resolution To implement this logic, use the Ready Output functionality within a dedicated Area. Understanding Ready Output The Ready Output is activated when all inputs (including trouble inputs) in an Area are closed, indicating the Area is ready to be armed. It is deactivated when any input is open or the Area is armed. Configuration Steps Create a Dedicated Area In Security Expert, create a new Area specifically for this input group logic. Assign Inputs to the Area Add the desired Inputs to this Area. Set each Input’s type to "Instant" (or another appropriate type based on your use case). Configure the Ready Output Go to the Areas tab → select your Area → navigate to the Outputs sub-tab. Scroll to the bottom and locate the Ready Output section. Assign the Output you want to control based on the state of the Inputs. Optional: Invert the Output If your Output device requires the opposite logic (i.e., activate when any input is open), go to the Outputs tab → select your Output → check the Invert Output option under the Options sub-tab. Ensure the Area Is Disarmed The Ready Output only functions when the Area is disarmed. If the Area is armed, the Output will not behave as expected.

Issue When an Engineering License ("New system") is created and activated on an Enterprise Server (ES) that has been upgraded from EBO 6 or earlier to EBO 7.0.3, the feature licenses do not propagate to Automation Servers (AS) that are still running EBO 6.0 or earlier Product Line EcoStruxture Building Operation Environment Software Companion Device Administrator Centralized Licensing Cause The current Engineering License offering with the "New system" does not support scenarios where the top-level server has been upgraded from EBO 6 or earlier to EBO 7.0.3. In such cases, the license propagation mechanism may not function correctly. Resolution To ensure proper license propagation: Recommended Setup: Create and activate the Engineering License ("New system") on a top-level server with a clean EBO 7.0.3 database. In this configuration, feature licenses will be inherited correctly by AS units running EBO 7.0 and earlier. Alternative Workaround: If the ES has been upgraded from EBO 6 or earlier to EBO 7.0.3 and AS units cannot be upgraded immediately ( Multi-system) : Consider manually assigning feature licenses ( Demo lic) to the AS units. Or, migrate AS units to EBO 7.0 or later to restore automatic license propagation.

Issue You need to transfer your MicroNet View license from an existing PC to a new one. Product Line Satchwell MicroNet Environment MicroNet View Cause Migration of MicroNet View software and license due to hardware upgrade or replacement. Resolution On the Existing Computer Close MicroNet View and all associated programs. Navigate to: C:\MicroNet\Binary\VCommon\License and copy the WWSUITE.LIC license file. Navigate to: C:\MicroNet\Projects and copy your MicroNet View project files. Remove the MicroNet View dongle and I/O server dongle from the parallel port. On the New Computer Install MicroNet View. If using Windows XP, install the Hasp dongle driver from the Hasp folder on the MicroNet View installation CD. Plug in both dongles to the manufacturer’s standard parallel port. ⚠️ Note: Add-on parallel port cards may not recognize the dongles. Copy the WWSUITE.LIC file to: C:\MicroNet\Binary\VCommon\License Copy your project files to: C:\MicroNet\Projects Reboot the computer. Launch the Project Manager: C:\MicroNet\Binary\Project\MNProject.exe From the menu, select: “Find and register a project” Locate and highlight your project, then click OK. You should now be able to run your MicroNet View project on the new computer.

Issue Conflicts may arise when installing MicroNet View software alongside I/O server software from the provided disk. Product Line Satchwell MicroNet Environment MicroNet View software with I/O server Cause MicroNet View includes built-in installation of the required I/O server software. Installing the I/O server software separately from its disk can lead to software conflicts. Resolution To ensure a successful installation: Install Only MicroNet View Software Do not install the I/O server software from the disk supplied with the I/O server. MicroNet View automatically installs the necessary NCP/ARCnet or SNP I/O server components. If Both Have Been Installed Uninstall all related software. Reinstall only the MicroNet View software. Additional Notes This guidance applies to installations involving either NCP/ARCnet or SNP I/O servers. Reinstalling the I/O server software separately may result in communication issues or system instability.

Issue Users require access credentials for IAC Touchscreen devices used in Satchnet IAC controller environments. Product Line Satchwell MicroNet Environment Satchnet IAC controllers Cause Default passwords are needed to access various levels of functionality on the IAC Touchscreen. These credentials may be required during initial setup, troubleshooting, or reconfiguration. Resolution The default access levels and corresponding passwords are: Access Level Default Password Read Only 1234 Read/Write 4321 Super User 1024 ACK Alarm 2513 🔒 Note: These passwords can be modified during programming. 🔍 To verify or change passwords, connect to the Touchscreen using VisiSat software and check the Properties section of the device.

Issue When downloading a configuration to a Unifact controller using VisiSat 2.1, the first byte of the download is incorrectly set to 0 , resulting in a node link mismatch. Product Line Satchwell MicroNet Environment VisiSat 2.1 Cause The initial byte of the configuration download is incorrectly set to 0 , which disrupts the node link table within the controller. This leads to a mismatch between the configuration in VisiSat and the controller. Incorrect entry for Pair 0 Correct entry for Pair 0 Resolution Download the Required Scheme Whether it's a new scheme or the same one already present, re-download it to the Unifact controller. Enter Bubbleland A "links mis-match" message will appear. Select "Fix Later" to proceed. Repair the Links Focus on any object link. Break the link. Then re-make the link. Verify Configuration This action rewrites the node link tables in the controller. Re-enter Bubbleland to confirm that the configuration now matches the one in VisiSat. Important Notes: This procedure must be repeated each time the controller configuration is downloaded.

Issue Instances 29 and 30 of the Logic Block objects (8-input AND/OR/NOR/NAND) did not function correctly: Instance 29 remained OFF regardless of input. Instance 30 remained ON even with no inputs connected. Product Line Satchwell MicroNet Environment Satchwell MicroNet MN550 Controller Cause The issue was due to a firmware defect in earlier versions of the MN550 controller software. Resolution This issue was resolved in MicroNet 50 Firmware Version 5, released in August 2008. For detailed information, refer to technical publication: TPA-LOND-08-0014.00

Issue Determining whether Micronet ARCnet or LON version Touchscreens are compatible with an NCP network. Product Line Satchwell MicroNet Environment MicroNet 50 Series & 100 Series Touchscreens ARCnet and LON communication protocols NCP (Network Control Protocol) infrastructure Cause Touchscreen compatibility is dependent on the communication daughter board and firmware type. ARCnet and LON versions differ in hardware and software capabilities. Resolution ARCnet Touchscreens MicroNet 100 Series (MNN-TS-100 / MNN-TSP-100 + MNA-C) These units are supplied with an ARCnet daughter board but have NCP communications by default. ✅ Action: Removing the ARCnet daughter board reverts the touchscreen to NCP type. MicroNet 50 Series (MN50-TS-ARC / MN50-TSP-ARC) Similarly, these are supplied with an ARCnet daughter board and default to NCP communications. ✅ Action: Removing the ARCnet daughter board reverts the touchscreen to NCP type. LON Touchscreens MicroNet 100 Series (MNL-TS-100 / MNL-TSP-100) These units are supplied with a LON board. ❌ Note: Removing the LON board does not revert the touchscreen to NCP type. ⚠️ The LON firmware supports a limited Bubbleland program and differs from the NCP version. 🔒 NCP firmware is not available for retrofit. MicroNet 50 Series A specific LON version was not produced for the 50 Series. ✅ The hardware remained consistent with the 100 Series model.

Issue When launching VisiSat 2.1 Build 185 on certain Windows XP Pro / Visio 2003 systems, the following error may appear: Internal error 0x86DB08A9 VisiSat 2.1 Build 185 cannot find the “CustomiseUI” add-on to Visio. Some or all files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Product Line Satchwell MicroNet Environment VisiSat 2.1 Build 185 Cause Visio 2003 may fail to recognize or properly register the VisiSat 2.1 Build 185 installation, particularly the CustomiseUI component. Resolution Open Visio 2003 (not VisiSat). From the menu bar, go to: Tools → Options Select the Advanced tab. Click on File Paths. Delete all entries listed. Click OK to confirm and close the dialog. Close Visio 2003. Launch VisiSat again. It should now start without error. If you close VisiSat and reopen Visio 2003, the file paths should now be correctly displayed. Additional Option If you're running on Windows 7, consider upgrading Visio to Visio 2007 or Visio 2010 for improved compatibility.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Invalid Address for All Values Shown in TAC Vista for Imported NCP or SNP Network

Default Passwords for a MicroNet Touchscreen

Xenta 555 - Satchwell IAC 600 Controllers Remain Offline When Connected to the Xenta

What is the Default Password for a MicroNet LCD?

StruxureWare Building Operation 1.3/1.3 SP1 reports "The upper limit must be greater than or equal to the lower limit and indicates the import is complete".

Will VisiSat Version 2.1 Build 148 work with Visio 2002?

VisiSat 2.1 Project Upgrade Program

Control loops linked via antlers

MicroNet View file extension .AEH

Why Are Pages Grayed Out on Xenta 555 Web Interface (e.g., Time Schedule Page)?

Accuracy of I/A Series MN-Sx S-Link Wall Sensors

How to latch an output when any inputs are enabled and unlatch when all are disabled

Feature License Propagation Issue using Engineering License ("New system")

How to Transfer Your MicroNet View License to a New Computer

Installing MicroNet View Software with I/O Server Installation

Default Passwords for an IAC Touchscreen

Links Reported as Mis-match After Downloading Configuration to Unifact Controller

Logic Block Instances 29 & 30 Malfunction in MN550 Controller

Can You Use Either Micronet ARCnet or LON Version Touchscreen on an NCP Network?

VisiSat 2.1 Build 185 Cannot find VisiSat "CustomiseUI" add-on to Visio.

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!