Building Automation Knowledge Base

Issue Change an IP address on Windows 8 to a static address. Product Line Other Environment Windows 8 Cause Changing the IP address of a PC is often done to ensure it resides on the same subnet and network as the system or devices it is trying to communicate with. Resolution From the Start Menu (Tiles), open the Charms bar by moving the mouse to the right bottom corner of the screen or press the Windows Key + C and click on Search. Highlight Settings. In the Search box type Network to search for any network related options From the list options choose Network and Sharing Center. From the View Your Active Networks section, select Local Area Connection. Go to Properties. Result: The Local Area Connection Properties screen appears. Highlight Internet Protocol Version 4 (TCP/IPv4) and click on Properties. Result: The Internet Protocol Version 4 (TCP/IPv4) Properties screen appears. Click Use the following IP address. Complete the configuration fields as shown below. This part of the configuration requires attention to detail, because one error will prevent you from getting on the network. Be sure you have this information at hand when you start to configure the TCP/IP protocol: IP Address: x.x.x.x Subnet mask: 255.255.255.0 Default gateway: x.x.x.x  Enter these numbers in the appropriate fields and click OK. Continue to click OK or Close as appropriate until you return to the Network Connections screen. The Local Area Connection icon text should now say "Enabled". To test the new IP address: Open a command prompt in Windows 8 Swipe to show apps screen Scroll down and locate Windows system section heading Under Windows system, press or click on Command Prompt (a new Command Prompt window will open up on the Desktop.) You then can type in IPCONFIG then hit Enter and look for the new IPV4 address. You can also try to type in PING (IP ADDRESS) that should reply with the new IPV4 address if set correctly.

Issue Some helpful basic IP commands. Product Line Other Environment Computer with IP NIC or Network Cause Need for basic IP configuration or IP address Resolution Go to start, click run and type in "cmd". This takes you to the command prompt. Type in: "ping xxx.xxx.xxx.xxx" to see if your device is online and its response time. Make sure you put the space between "ping" and "xxx". "ipconfig" and hit enter to get the info of the computer you are currently using. You'll get the IP address, subnet mask and the gateway. "ipconfig/all" and hit enter to get more info on the machine your using. It will give you all the above and then some including the DNS server addresses. "tracert xxx.xxx.xxx.xxx" and hit enter and you can see the servers that you are going through to get to your destination. This can be used when connecting to a Loytec or a iLon and the IP address is being presented to the L-IP or iLon is unknown. Connecting through a firewall/gateway/NAT server, you are not presenting the PC's address - when you do the tracert you will go through your gateway and the next address will be the IP you are presenting- Use this in the iLon as the LNS server address.

Issue User name and password required Environment Satchnet Pro Plus   Cause Unknown access user name and password. Resolution User name = super Password = user

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.

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

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

Issue Upgrading to a MicroNet 50 series, the  option is grayed out in VisiSat. VisiSat version 2.0 stencils held no information regarding the 50 series controllers. Product Line Satchwell MicroNet Environment VisiSat version 2.0 VisiSat version 2.1 Cause VisiSat 2.1 introduced the option to upgrade a MicroNet legacy controller (MN300, MN440, MN500, and MN620) to a 50 series type (MN350, MN450, MN550 and 650). When the original project was created in version 2.0 VisiSat or older, the option was grayed out. 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Save the MicroNet *00 series controller's configuration to disk. Delete the controller. Drop a new MicroNet legacy controller onto the main page. Address the controller with the original address. Load the configuration saved in step 1. Now the option to upgrade is available.

Issue The MN300 with a SLink sensor supported setpoint adjustments of 0.1 unit resolution. MN350, MN450, MN550 and MN650 with firmware version 2 and 3 only supported setpoint adjustments of 1.0 unit resolution. Product Line Satchwell MicroNet Environment MN350 MN450 MN550 MN650 MicroNet Cause 0.1 unit resolution is not supported on MN350, MN450, MN550 and MN650 with firmware version 2 and 3. 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- MicroNet 50 controller firmware version 5 released August 2008, when used with an updated SLink2.FCG file for VisiSat 2.1 Build 148 now supports 0.1 unit resolution changes. Slink2.FCG File for Micronet 50 Controllers Firmware v5 file. Additional information can be found in TPA-LOND-09-0029.00 - Touchscreen TS0H Firmware.

Issue The majority of the Satchwell MicroNet and Satchnet product ranges is now re-branded to Schneider Electric. Product Line Satchwell MicroNet Environment IAC-420-F IAC-420-P IAC-440-F IAC-440-P MN350-LON MN450-LON MN550-LON MN650-LON MN50-TS-LON MN50-TSP-LON MNN-COM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM MNN_RTC M50_RTC MN-TK MN-VWIO-NCP MN-VWIO-SNP MN-VW100-UK MN-VW500-UK MN-VWP500-UK MN-VWP2K-UK MN-VWP10K-UK MN-VWP60K-UK Monitor Tool MicroNet View Cause The branding exercise provided some insightful information regarding sales volume. As a result, a number of products that were low or zero sales have been discontinued. 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- For more information on the re-branding of the Satchwell MicroNet product range, see PA-00145A - Satchwell MicroNet Range Rationalisation and Schneider Electric Re-branding. Old Part Number New Part Number IAC420-F IAC420-P MN350-LON MN350-NCP + MNL-C (LON card) MN450-LON MN450-NCP + MNL-C (LON card) MN550-LON MN550-XCOM + MNL-C (LON card) MN650-LON MN650-XCOM + MNL-C (LON card) MN50-TS-LON MN50-TSP-LON (Panel Mounted Only) MNN-COM MN550-XCOM or MN650-XCOM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM  

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

Issue ARCnet Routing with MicroNet 50 series controllers. The MN50 Series controller did not transmit the ARCnet network variable across different Subnets. Product Line Satchwell MicroNet Environment MN50 Series controller Cause MicroNet 50 controller must be upgraded to firmware version 5. Resolution This has been corrected with MicroNet 50 controller Firmware version 5 released August 2008. Additional information on firmware 5 can be found in TPA-LOND-08-0014.00   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 and PA-00528

Issue Can you use either Micronet ARCnet or LON version Touchscreen on an NCP network? Environment MicroNet ARCnet Touchscreen MicroNet LON Touchscreen NCP Network Relates to specification numbers: MN50-TS-ARC MN50-TSP-ARC MN50-TS-NCP MN50-TSP-NCP MN50-TS-LON MN50-TSP-LON Cause Touchscreen compatibility Resolution ARCnet The MicroNet 100 Series ARCnet Touchscreen ((MNN-TS-100 or MNN-TSP-100) + MNA-C). The Touchscreen has NCP communications by default, they were supplied with an ARCnet daughter board. Removing the ARCnet daughter board, would revert the Touchscreen to an NCP type. The MicroNet 50 Series ARCnet Touchscreen (MN50-TS-ARC or MN50-TSP-ARC) The Touchscreen has NCP communications by default, they were supplied with an ARCnet daughter board. Removing the ARCnet daughter board, would revert the Touchscreen to an NCP type. LON The MicroNet 100 Series LON Touchscreen, (MNL-TS-100 or MNL-TSP-100) removing the LON board would not revert the Touchscreen an NCP type. The LON Touchscreen firmware allows for a limited Bubbleland program and is different to that of the NCP version. The NCP touchscreen firmware is no longer available to be retrofitted. A specific MicroNet 50 Series Touchscreen version was not produced, the hardware remained the 100 Series model.

Issue TAC Xenta 511/527 Help cannot be opened. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment I/NET or Vista site Cause TAC Xenta 511/527 and the Help information will not open Resolution With the new product versions of the 511/527 the help file is now downloaded to the computer rather then viewable online. If you receive an "Action canceled" error when you try to open the help file right click on the file (Help511-527.chm) and choose "Properties". Then under the General tab at the bottom of the window you will see "Security: This file came from another computer and might be blocked to help protect this computer." Click "Unblock" and then open the file and you should be able to view the help section. This error message appears to only occur when downloading the help file with Internet Explorer.