Building Automation Knowledge Base

Issue Failing communications from a MicroNet View front end. Environment MicroNet View communicating to a MicroNet ARCnet or NCP  LAN. Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position.  Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Place switches 1 to 4 to ON for compatibility with NCP/ARCNET I/O- Server (MicroNet View versions 1.0 and later). Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Installing VisiSat 2.1 Build 196, when using Visio 2010, or Visio 2016. Product Line Satchwell MicroNet Environment Visio 2010 Visio 2016 VisiSat 2.1 Build 196 Cause Having installed VisiSat 2.1 Build 196, the customer cannot see any of the VisiSat tools. Visio 2010 is unlikely to be available Visio 2016 may be. Resolution To install VisiSat 2.1 Build 185, when Visio 2010 is being used, please carry out the following; Install Visio 2010. Start Visio 2010. Select the "Options" menu Select the "Trust Centre" menu Select the "Trust Centre Settings" menu Select the "Macro Settings" menu Choose "Enable All Macros" and save the changes. PLEASE NOTE - Visio 2016 is not supported by VisiSat 2.1 Build 196, and therefore has not been tested. Install Visio 2016 Start Visio 2016 Select the "Options" menu Select the "Trust Centre" menu Select the "Trust Centre Settings" menu Select the "Macro Settings" menu Choose "Enable All Macros" and save the changes. Select the "File Block Settings" menu Uncheck the boxes of the files you wish to open/save. Shutdown Visio and restart Windows. Restart Windows. Install Visisat. When opening Visisat you should now see the VisiSat tab in Visio 2010/2016 Please note, an occasional error has been seen when selecting the VisiSat "Options" menu, this error does not appear to cause any problems.

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 In the IAC400 and IAC600, a digital output cannot be forced to a different value. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment IAC400 IAC600 SBO Cause When an IAC400 or IAC600 is imported into SBO using the Micronet interface, on a digital output, the output cannot be forced to another value. Resolution In Visisat, create the SBO export file. Before using the 'Data Import' into the Micronet Interface in SBO, locate and open the export XML file with a suitable program, e.g. Notepad++. Locate the respective controller's 'Digital Output Override State' with the line <P1="IsNonVolatile".... (Note: if opened in another application, e.g. Internet Explorer, the word order may be different!) Change Value= "1" to Value="0" Note: IAC420s are unaffected

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 Services for assistance. Issue When clicking the menu point "Utilities"->"ProjectTree" the project tree doesn't open as expected in the window. Environment TAC Xenta Server Cause There is a problem with the file "applets.html" in the Xenta Server. Resolution You need FTP connection to the Xenta Server in order to carry out the following steps 1. Make sure that FTP access is enabled for the root user - this menu is available from Configuration->User administration->User administration                           2. Make sure that the number of concurrent FTP users is higher than 0 Correcting the html file 1. Connect to the Xenta Server with a FTP client 2. Browse to the location "/www/japplets" in the Xenta Server 3. Copy the file "applets.html" to your desktop 4. Make a backup of the file on your PC 5. Edit the file "applets.html" on your PC, e.g. with Notepad++ or another editor 6. Scroll down to line 376 - it should say "function writeXBMenuAppletTag" - if not you need to locate this line 7. Change the text "cyrrDoc" to "currDoc" 8. Save the file 9. In the FTP client, copy the edited "applets.html" file from your desktop to "/www/japplets" in the Xenta Server 10. Restart your browser Check if the project tree is opened now when the menu is clicked     The project tree will also open if you use "Tree2" as the menu type rather than "Menu" and Tree"

Issue Importing a VisiSat pointslist StruxureWare reports a limit issue and suggests the import is complete. 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 The "Stop transmission of the Alarm Message" setting in an "Action" can be lost from the "What should be done when an alarm is acknowledged" menu. Environment RAM Remote Alarm Manager 2.0 Settings Actions Cause It is possible to lose the "Stop transmission of the Alarm Message" setting when reviewing, or changing the configuration of an action. Resolution There are two ways that an "Action" can be modified. 1. - Open the required "Action" and starting on the first page, step, using the "Next" button through the pages, to the "Finish" option. If reviewing an action, this method Work through the "Action" pages in sequence, select "Stop transmission of the Alarm Message" and then finish. If the process is then repeated again, the "Stop transmission of the Alarm Message" option is deselected. 2. - Open the required "Action" and using the boxes on the left-hand side of the page, directly select the required page. Note - If you are modifying an "Action" configuration and require the "Stop transmission of the Alarm Message" to be enabled, then be sure to check that it is ticked before selecting finish.

Issue The 50 series version of the LCD unit can fail to re-poll analogue values when used in conjunction with an old series MN controller, this will only occur after the controller has been power cycled. This problem does not apply to the 50 series controller range.   Product Line  Satchwell Sigma Environment MicroNet 50 series LCD connected to 100 series controller. Cause With older controllers, although the initial poll from the LCD brings back the controller analogue values, the LCD changes the displayed value to zero. This issue does not affect digital state displays or the analogue values contained within the controller’s scheme. Resolution A temporary workaround is to ensure the controller is not power cycled after its configuration has been downloaded. Firmware version MNLCD5W is now available for correcting this issue. If you require updated firmware for your MN50-LCD or MN50-LCDP units. Please contact the Product Support Services department. Specification numbers affected: MN50-LCD  (Firmware version MNLCD5V) MN50-LCDP  (Firmware version MNLCD5V) This issue will only affect the MN50-LCD or MN50-LCDP when used with the MNN-30-100 MNN-44-100 MNN-50-100 MNN-62-100 Liberty (All variants) This problem does not apply to the 50 series controller range. Firmware version MNLCD5W is available from Product Support By supplying the site name, and the number of MN50-LCD firmware EEPROMs required.    Procedure to change the MN50-LCD firmware. Observe standard electrostatic precautions. Power the MN50-LCD/P and MicroNet 100 series controller down. If MN50-LCD remove the LCD from the controller and unplug the ribbon cable. If MN50-LCDP remove the power/communications plug from the LCDP, then remove the back cover. Remove the MN50-LCD/p's firmware EEPROM from IC13 socket. (Highlighted in the below image in blue) Carefully line up the legs of the new EEPROM with the socket. Press the new MNLCD5W firmware EEPROM into the socket. Restore the power to the controller Download the controller and LCD program to the controller. Restore the power and plug the MN50-LCD/P into the controller and allow it to upload is configuration. Check all analogue readings are now reading satisfactorily. 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  A limited number of MNLCD5W firmware EEPROMs are available.

Issue System does not respond correctly to "Off Duty" and "On Duty" messages. Environment RAM 1.2 Ram 2.0 Duty Roster Cause When a reciprocator’s Mobile sends an “Off duty message” to the RAM interface, a duty exception is created on the RAM console, but when the same reciprocator’s Mobile sends an “On duty message” to the RAM interface the duty exception is not cancelled. Resolution This issue will not be addressed at this time as a "Work Around" is available. To enable users to remotely issue an "On or Off duty" commands, their Local access needs to be set to ‘Privileged User’ or above. This is on the Users ‘Access page’ as shown below.  

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 What happens to an alarm message when the clocks go back during the BST/GMT changeover? Environment RAM Remote Alarm Manager Time Changeover BST GMT Cause This is an issue relating to RAM and how it handles BST/GMT changeover. If an alarm occurs, is it handled correctly by the Remote Alarm Manager? What will happen if the PC  time goes back, and the alarm is then cleared before the time passes the original alarm time. Will this cause any issues when viewing the alarm on the Remote Alarm Manager?   Resolution  Tests confirmed that there were no issues with this scenario; An alarm was generated at 15:46 and a text message was received. The PC time was put back an hour, and the alarm cleared at 14;52. . The alarm and the alarm cleared messages are shown in the RAM log below as 15:46 and 14:52 respectively.     The screen shot below shows the alarm status after the alarm was cleared.     The screen shot below shows the alarm properties, and here there is an error, the cleared state shows 15:52 which is incorrect.     When the time catches up everything returns to normal.

Issue Microsoft Visual Studio causes Just-In-Time Debugging Environment Windows Operating System Cause Visual Studio is installed on the PC and when attempting to perform a task, an error appears claiming Just-In-Time Debugging.  Resolution To disable Just-In-Time debugging: On the Tools menu, click Options. In the Options dialog box, select the Debugging folder. In the Debugging folder, select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key. Click OK.

Issue How to find the MAC address / Physical Address of a computer. Product Line Andover Continuum, EcoStruxure Building Operation, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment All computers Cause The MAC address of a computer may be required when working on licensing issues. MAC stands for Media Access Control and is a unique identifier assigned to network interfaces for communications on the physical network segment. Resolution Go to the Start > Run.   Type "cmd" into the Open field. In the CMD window, type the command "ipconfig /all". Locate the connection that the computer is currently using (For this example it is the Ethernet adapter Local Area Connection). You will find the Physical Address (MAC address).

Issue Licencing error in RAM log Environment Sigma RAM Micronet Vista Cause The following error is seen in the RAM log when Sigma is installed. Resolution In Sigma, RAM licensing is done using the Sigma dongle. In the "Remote Alarm Manager Computer Configuration Wizard" Select: Start > Licence Scheme and ensure that the "Legacy Licence Schemes" is checked.

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

Issue When VisiSat 2.1 Build 185 on some Windows XP pro / Visio 2003 computers the following error is displayed. Internal error 0x86DB08A9 VisiSat 2.1 Build 185 Cannot find VisiSat "CustomiseUI" add-on to Visio. Some or all the files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Environment CustomiseUI Add on to Microsoft Visio 2003 VisiSat 2.1 Build 185 Cause Visio 2003 does not recognise or register VisiSat 2.1 Build 185 installation CustomiseUI Resolution Open Visio 2003 (Not VisiSat) On the menu bar, under tools select options.   Select the advance tab.   Select file paths.   Delete all entries. Then select OK   Select OK.   OK the next window Visio 2003 should now close.   Run up VisiSat VisiSat should run up OK now.   If you close VisiSat and open Visio 2003 the paths should now show.   VisiSat should open correctly now. Option: If you are running on Windows 7 you could consider upgrading the Visio 2003 software to Visio 2007 or Visio 2010. If you require further assistance, please contact Product Support.

Issue Selecting the tick box option for the VisiSat server to update the time on the LAN connected, does not work. On an SNP LAN the controller time is not updated even if the VisiSat server is restarted. On a VisiView installation this means the controller time is not automatically updated. Environment VisiSat VisiView SNP IAC LAN Server Time Update Cause Unknown at this time, no fix planned. Resolution The suggested work around would be to supply a Touchscreen (IAC-TS) and possibly a Remote mounting kit (DDC 2601), if the site does not currently contain a Touchscreen. The Touchscreen can then update the time in the controllers on the SNP LAN with the time contained in the Touchscreen. Updating the time in the Touchscreen would have to be done manually. The controllers would have to be re-addressed and the VisiSat project would require reconfiguring for the new controller addresses. Additionally if the site is running a VisiView project, the VisiView project would also need to be re-engineered to align it with the new controller addresses.