Building Automation Knowledge Base

Issue Xenta 5/7/9xx locks up during boot up sequence. Plugged into the service terminal (RS-232-B) during the boot up sequence, it can be observed that it stops processing on the "InstallDrivers" command. In some situations the error log produces the 49154 error code. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In some situations the error log produces the 49154 error code. If the Xenta 511/527/913 is not booting correctly and stops processing on the "InstallDrivers" command, visible via a Hyperterminal connection, the cause typically is that the Xenta controller is underpowered. Resolution The Xenta controller can survive some drop in power after the initial boot up sequence, but it vulnerable to an insufficient power supply during the boot up sequence. To avoid this problem simply provide the Xenta controller with a stable power within the documented range. The 49154 error code is typically an issue with the power coming to the Xenta, the transformer or something, and a smaller chance of a short from the LAN which is causing this power instability. Mark said they can recycle the power, the Xenta comes back and works for a bit, then the same error. Check the transformer, then with a replacement Xenta in hand, upgrade firmware if possible. If not able, replace Xenta and if not to expensive, replace transformer at same time. 

Issue No stencils in VisiSat software for the new MicroNet 50 series range Environment MicroNet 50 series range VisiSat Cause An upgrade is required to receive these stencils. Resolution Go to the help menu, and select about VisiSat. If you are running VisiSat 2.0 then you need to request the latest version of VisiSat 2.1. VisiSat 2.0 to VisiSat 2.1 is a free upgrade If you are using VisiSat 1.1 or VisiSat 1.2, then you will need to purchase VisiSat 2.1.

Issue Installing VisiView and VisiSat 2.1 build 14,17 and 137 Environment VisiView and VisiSat 2.1 build 14,17 and 137 Cause Installation Resolution The installation of VisiView automatically installs VisiSat 2.0 If you have installed VisiView, you will need to Uninstall VisiSat 2.0 Then install VisiSat 2.1 If you install VisiSat 2.1 first, When you install VisiView your VisiSat 2.1 installation will be left at VisiSat 2.1 VisiView will not work with VisiSat 2.1 Build 148

Issue Installing MicroNet View software with I/O server installation. Environment MicroNet View software with I/O server Cause Installation Resolution If you have purchased MicroNet View and an NCP/ARCnet or SNP I/O server, only install the MicroNet View software. You should not install the I/O servers from the disk supplied with the I/O server. When MicroNet View installs it also installs both NCP/ARCnet or SNPI/O server software. Installing the I/O servers again can cause a conflict. If you have installed both, then Uninstall all the software and re-install MicroNet View only.

Issue Transferring VisiSat version 2.0 license to Computer running VisiSat 2.1 Product Line Satchwell MicroNet Environment VisiSat 2.1 Cause A computer needing to run VisiSat 2.1 with a transferred license from a computer running VisiSat 2.0. Resolution Install VisiSat 2.0 onto the target machine. Transfer the license. Once you have a licensed copy of VisiSat 2.0, you should Uninstall VisiSat 2.0 and install VisiSat 2.1. Your VisiSat 2.* license will be held in the registry.

Issue VisiSat 2.1 project upgrade program Environment VisiSat 2.1 Cause The VisiSat 2.1 upgrade program supplied with VisiSat 2.0 and 2.1, is to upgrade projects originally created in VisiSat 1.1 or 1.2 to the VisiSat 2.* format. VisiSat version 1.* stored all project information under the main project folder. VisiSat 2.* stores all project information and controller configurations under a folder "VisiSat" under the project folder. Resolution Projects must be upgraded and import if originally created in VisiSat 1.*. DO NOT just copy VisiSat 1.* files into a folder named VisiSat under your project folder, then run it in VisiSat 2.*. You will experience problems with your project if this is done. Note: The way VisiSat 2.* stores and accesses the point information is completely different to VisiSat 1.*.  

Issue Configure a Xenta 5/7/9xx for no timeout log out. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause A Xenta 5/7/9xx controller is set up with certain predefined time out durations for logging out inactive users.  While you cannot disable this feature, you can set the duration sufficiently long to effectively eliminate the log out if desired. Resolution Generate a certificate.  To avoid the certificate error every time you connect to the Xenta 5/7/9xx, go to XBuilder, and generate a certificate that has the same name as the IP address of the Xenta. Edit the file viewuser.html.  Connect to the Xenta using FTP.  For example Internet Explorer ftp://:@ viewuser.html is located in the folder www/config.  Save the file on your hard drive.  Edit the file with Notepad, and add the following correction to viewuser.html Line 159:  Add another Option tag with a value of "259200000" and description of 3000 days following the form of the previous entries. Carry out the changes.  Connect to the Xenta using FTP.  Change the name of the file in the Xenta (Backup) Copy the file the you have on your hard drive to the Xenta. Activate "no logout."  Go to the configuration page in the Xenta.  Select "3000 days" for log out

Issue Is there a fix for MN50 Controller Optimisers and the Run-up/down influence node error. PIB 07.11.02-1 Environment MN50 PIB 07.11.02-1 Cause A firmware upgrade is required. Resolution Version 5.02 Firmware now fixes this problem.

Issue What is the replacement communication card for a MNA-R10 or a MN50-MI-RTR? Environment MNA-R10 MN50-MI-RTR Cause Part number is needed to replace the communication card. Resolution The MNA-R10 Router is obsolete but the ArcNet Card is still a current product MNR-C (ArcNet Plug-in Card) and NOT MNA-C. This is detailed on the MN50-MI-RTR datasheet.

Issue When you run VisiSat after a reinstall you have lost all your network and remote site information. Environment Visisat Cause The process of uninstalling VisiSat removes the file. C:\Satchwell\Binary\VisiSat\SITES.DAT (default installation folder). This file holds the remote site information. Resolution Copy the SITES.DAT file before uninstalling VisiSat. When you have installed the later version of VisiSat copy the SITES.DAT file back to C:\Satchwell\Binary\VisiSat\SITES.DAT (default installation folder). Create a remote network The modem numbers should be there

Issue Points not reading in Xenta 555 Environment VisiSat 2.1 Build 148 Xenta 555 Cause If the Xbuilder points have been exported from VisiSat 2.1 Build 148. The .s (dots) that should separate the table offsets ETC are replaced by _s (Underscores). The X555 does not understand these. For example: The value page shows a reading of 0, but no red cross ETC.   Resolution You need to install VisiSat 2.1 build 148 Service pack 1. Service pack 1 is available from: https://ecobuilding.schneider-electric.com Click here to download it from here Or by emailing Product Support Additional information can be found in TPA-LOND-08-0006.00 VisiSat 2.1  build 148

Issue Can MN View run on Windows 2003 Server? Environment MNView Windows 2003 Server Cause MNView has not been tested on Windows 2003 Server, the 'latest' software being XP. Resolution If you attempt it you may find that the software is loaded to a different drive label other than 'C'. If this is the case then it will definitely not work, it MUST be loaded to drive 'C'.

Issue I have a MN500 with a broken display, what can I replace it with? Environment MN500 Cause Replacement part for broken display. Resolution You can purchase a MN50-LCD as a direct replacement if that is all that is required. If the MN500 is also faulty you will need to upgrade to the MN550 which will require Visisat 2.1 Build 137 (as a minimum) to program/convert it. If the MN500 is on a network then you will need to purchase the MN550-XCOM to enable both comm and LCD to be connected.

Issue Will VisiSat Version 2.1 Build 148 work with Visio 2002? Environment VisiSat 2.1 Build 148 Visio 2002 Cause VisiSat version 2.1 only support Visio 2003. Resolution VisiSat Version 2.1 must use Visio 2003 as stated in the VisiSat 2.1 Configuration Tool Datasheet. The following contents are related to VisiSat 2.1: VisiSat 2.1 Engineering Guide VisiSat 2.1 Installation and User's Guide VisiSat Version 2.1 Build 148  (Note: File size = 40Mb.)

Issue Priority Value Select object. The output of Instance 31 of Priority Value Select was always 0 in a MicroNet MN 550 controller. All other instances function correctly. Environment MicroNet MN 550 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

Issue Logic Blocks: Instances 29 & 30 of the Logic Block objects, 8-input AND/OR/NOR/NAND, did not function correctly in an MN550 controller. Instance 29 was always OFF and instance 30 was always ON (even with no inputs connected). Environment MN550 Cause Firmware update is required. 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

Issue Control loops linked via antlers. Environment Control objects Cause When a number of Control objects are used for multi loop control. The lower stage output antler of Control loop in some cases failed to function correctly; the Antler node connection going to '---'. 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

Issue Will VisiSat work with Windows Vista? Environment VisiSat Windows Vista Cause Compatibility with Microsoft OS Resolution VisiSat Version 2.1 build 148 service pack 1 can either be used on a computer running Windows XP Pro with Visio 2003 or it can be used on a computer running Windows Vista with Visio 2007. As detailed in the VisiSat 2.1 Configuration Tool Datasheet, available via Exchange OnLine, where you will also find the Installation/User's guide and the VisiSat Engineering Guides. VisiSat Version 2.1 Build 148 service pack 1 is available for download via Exchange OnLine. Note: File size = 41.5 Mb.

Issue Will VisiSat work with Visio 2002 Environment VisiSat Visio 2002 Cause VisiSat Version 2.1 build 148 service pack 1 will not work with Visio 2002. Resolution Although we would recommend using the latest version, VisiSat Version 2.1 build 137 can be used with Windows XP Pro and Visio 2002. VisiSat Version 2.1 Build 137 is available for download via Exchange OnLine. Note: File size = 30 Mb.  

Issue What to check when viewing your Xenta 555 webpages and finding areas/pages grayed out, For example the Time Schedule page. Environment Xenta 555 Cause Xenta 555 firmware must match the correct version of Xbuilder.   Resolution Xenta firmware Xbuilder Software 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 For example: If your Xenta 555 is running firmware version 5.1.1 and your project is Xbuilder version 5.0.3. Install Xbuilder 5.1.1 Open your project in Xbuilder 5.1.1 Your project will be upgraded. Then upload project to the Xenta 555.