Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)" Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers include: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series. Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message.   Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem.   XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.  

Issue Every time the computer reboots, LMGRD errors are shown at startup.   LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue Receive a temporary session password in exchange for the Session ID for a Xenta 5/7/9xx if the password has been lost. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 SessionId Cause Lost root password for the controller or was changed from the original Username and password Resolution This option is used if the valid password has been lost or if a situation occurs that disables login. Get the session-id from the system. The session-id is displayed during startup login procedure. Email this session-id to Product Support. Product Support will then supply a corresponding password to let you access the unit. This password will expire at midnight, so if it has not been used until then, a new session id needs to be sent to Product Support. Login with user = session-id password = received password

Issue Connecting a serial cable to a Xenta 5/7/9xx controller Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Xenta Servers have a service portal for use with HyperTerminal with a serial connection to the RS-232B port. Resolution Connect a serial cable, Programming Serial Kit, part no. 0-073-0920-0, between the PC and the RS232 port B on the TAC Xenta.  For more information about the cable see Cable Guide OFL-3972. Go to Start/All Programs/Accessories/Communications/HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. NOTE: Product support has also witnessed strange behavior with serial connections when certain laptops were not plugged into a power source or the Xenta Server was not grounded. If connection problems persist after the connection setting above are verified, make sure the Hyperterminal PC is plugged into a 120 vac power source.

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7 Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7 Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue Procedure to replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 Environment Satchwell MicroNet series controllers: MN300, MN440, MN500, MN620 MN350, MN450, MN550, MN620 Satchwell VisiSat version 2.1 and above. Cause Satchwell MicroNet series MN300, MN440, MN500 and MN620 are no longer available for sale and they are replaced by the MN350, MN450, MN550 and MN650 controllers respectively. See Product Announcement for details. MN300, MN440, MN500 and MN620 controllers installed on existing installations that are required to be replaced would have to be replaced with the new range of controllers. Resolution To replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 follow the procedure below. Pre-VisiSat 2.1 projects (VisiSat 1.2 and VisiSat 2.0) should be upgraded to VisiSat 2.1 using the Project Upgrade Utility. Download VisiSat 2.1 Engineering Guide here. Refer to pages 47 - 50 for using the Project Upgrade Utility Open the VisiSat project Right-click on the existing controller and select "Upgrade Controller." There is a prompt to save the controller configuration (.CLC file). Select 'Yes'. The controller object in VisiSat will now be converted to a MN50 Series controller. Replace the controller hardware. Make sure the jumpers are set correctly and that communications card, if existing should  be taken out and installed into the new controller. Right-click on the controller object in VisiSat and select 'Configuration Library'. Select 'Download Configuration' (2nd button from the left in the Configuration Library). This will download the configuration to the new controller. Refer to pages 135 - 140 in the VisiSat 2.1 Engineering Guide for using the Configuration Library. NOTE: In the Configuration Library, the first button from the right is the "Upgrade Controller" option. This performs the same function as the "Upgrade Controller" mentioned in step 3 above.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Using the ribbon cable provided with the Satchwell MicroNet Touchscreens & Satchwell MicroNet LCDs to supply power from a MicroNet 50 series controllers that are powered with 24VDC. Product Line Satchwell MicroNet Environment Satchwell MicroNet Touchscreens Satchwell MicroNet LCDs Satchwell MicroNet 50 series controllers Cause The Satchwell MicroNet 50 series controllers were built on new hardware. MN350-ARC, MN350-NCP, MN350-LON MN450-ARC, MN450-NCP, MN450-LON MN550-ARC, MN550-NCP, MN550-XCOM, MN550-LON MN650-ARC, MN650-NCP, MN650-XCOM, MN650-LON This new 50 series hardware design added support to the controller to be powered by 24 VAC or 24 VDC The Satchwell MicroNet Touchscreens & Satchwell MicroNet LCDs displays used an adaption of the 100 series hardware, which does not support being powered by 24VDC. Resolution When using a Satchwell MicroNet Touchscreens or Satchwell MicroNet LCDs on Satchwell MicroNet 50 series controllers that are being supplied with 24VDC, the ribbon cable cannot be used to supply the Satchwell MicroNet Touchscreens or Satchwell MicroNet LCDs with power. A separate 24VAC transformer should be used to power the Satchwell MicroNet Touchscreen or Satchwell MicroNet LCD. The MicroNet 50 series controller MLi's and Data sheets are available to download by searching for article “MicroNet 50 series controller MLi's and Data sheets” The MicroNet 100 series controller MLi's and Data sheets are available to download by searching for article “MicroNet 100 series controller MLi's and Data sheets”

Issue The Remote Alarm Manager sends a message to the recipient indicating that an alarm has been inactivated. The screen shot below shows how a typical message will appear on the receiving mobile phone. Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause An alarm message is generated, and the Remote Alarm Manager processes it in the normal way. After three days and at midnight, the Remote Alarm Manager will send a inactivation message to the on-call recipient, indicating that this alarm has been inactivated. Resolution This is not a fault with the system, it is operating as designed. When a new alarm is received by the Remote Alarm Manager, it is acted on in the way the configuration dictates. If the alarm remains on the system, without being retransmitted, then after three days the inactivation takes place. The 3 days is the default setting and can be changed if required.

Issue Replacing battery Product Line Satchwell Micronet Environment Panel Wall mounted Controller mounted Cause Obsolescence Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Battery part number Type LS14500 The battery is available from RS Components

Issue (2019-06) The current version supplied is 2.1 build 196 Also available for VisiSat 2.1 Build 196: Service pack 1 (Build 200) Service pack 2 (Build 201) Product Line Satchwell MicroNet Environment MicroNet controller programming IAC controller programming MMC controller programming.  VisiSat MN-VSCORE Cause Different versions of VisiSat must be used with specific Windows operating system and Microsoft Visio versions. The latest version/build of VisiSat may not be compatible with the users current system.. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- VisiSat 2.1 Build 196 (MN-VSCORE) is available to download from the Exchange Extranet , since January 2018, VisiSat can be freely used without the need for a license. Refer to PA-00597 - MN-VSCORE End of Commercialization - Satchwell MicroNet for further details on the availability of the VisiSat Configuration Tool . The VisiSat data sheet provides information on operating system and Microsoft Visio compatibility for different builds of VisiSat 2.1. SOFTWARE VisiSat 2.1 Build Number Windows Operating System Visio Release 185/196 Windows 7 2003/2007/2010 XP Professional 2003/2007 148 Vista Ultimate 2003/2007 XP Professional 2003 137 XP 2002/2003 17 XP 2002 14 Two service packs are available for VisiSat version 2.1 Build 196. Service pack 1 provides the following corrections: In the ARCnet debug Excel spreadsheet, the property editor can now be run. Exporting points to MicroNet View or Xenta Xbuilder, now allow up to 32 characters for the name and up to 50 characters for the description. In SBO (StruxureWare Building Operation) or EBO (EcoStruxure Building Operation) WorkStation, MicroNet Interfaces can no longer be exported/imported. All MicroNet engineering should be done in VisiSat first and then imported into SBO/EBO. Newly created blank pointslists can now be saved, without production an error message. Exports to SBO/EBO no longer produce Memory leaks. Adding service pack 1 takes the VisiSat 2.1 build number of 196 to 200 Service Pack 1 is available to download from the Exchange Extranet and VisiSat version 2.1 Build 196 service pack 1 Service pack 2 provides the following correction: Import file replaces all non-ASCII chars with replacement character. Once added the characters are converted correctly and points with alarms and trends results in the import file is generated. Adding service pack 1 takes the VisiSat 2.1 build number of 196/200 to 201. Service Pack 2 is available to download from the Exchange Extranet and VisiSat version 2.1 Build 196 service pack 2 Further information on VisiSat installation and operation can be found in Download latest VisiSat Data Sheets, Engineering Guides, Installation and User Guides, and Release Notes.

Issue On a NCP network where there are two or more MicroNet Touchscreens on the system, some values in MicroNet controllers on the Sub-LAN of a MicroNet Touchscreen are found to be changing unrepentantly. Product Line Satchwell Micronet Environment Communications Cause Micronet Touchscreen error Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The problem generally occurs when there is heavy communication traffic through the Touchscreens. New Touchscreen firmware version MNTS0H has been released fixing this issue. The firmware has been tested with VisiSat 2.1 Build 148 Service pack 1, MN50 series controllers, Xenta 555 and Xenta 731 hardware. Please refer to TPA-LOND-09-0029.00 Touchscreen TS0H firmware.

Issue No Communications when directly connecting to a MicroNet Controller. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) using VisiSat Cause Controller subnet setting incorrect. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Go to the VisiSat server on the taskbar by the clock.      Drop down the Network menu Then select restart. This will reset the controller subnet setting to 1 Now the Visisat server should be able to connect to the controller.  

Issue How to set up a MicroNet Mi for use on a Xenta 555 Product Line Satchwell MicroNet Environment MicroNet Mi Xenta 555 Cause Installation instruction for setting up MicroNet Mi with Xenta 555. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Cold start the MN50-Mi-ARC or MN-MI-100 with ARCnet card (MN-Mi). Unplug any RS 232 cables that are connected to PL3 or PL4. Energise the MN-MI and verify that the RUN LED flashes at about once per second. Set all bit switches to off. Place bit switch 8 to the on position and then return to OFF position. Place bit switch 1 to the ON position. Place bit switch 8 in ON position and then return to OFF position. The RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, and then the RUN LED should flash at about once per second. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. Plug the RS 232 cables to PL3 or PL4. Connect the Xenta 555.