Building Automation Knowledge Base

Issue What are the default passwords for a MicroNet Touchscreen? Environment MicroNet Touchscreen controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.

Issue What is the default password for a MicroNet LCD? Environment MicroNet controllers Cause Access level Resolution Default password: -                  1234 It is worth noting that this password can be changed when programming. With the 100 series range of MicroNet controllers a backup of the controller configuration would be required to identify the password if it has been changed from the default. With the 50 series range of MicroNet controllers when the controller configuration is uploaded the LCD configuration should also be uploaded, the passwords can be found under properties when you are in the configuration LCD area.

Issue Time schedules appear to be working backwards. Time schedule that controls occupancy of a LonWorks unit is not controlling properly. The unit is unoccupied instead of occupied. Time schedule outputs need to be reversed to control I/NET points where 0 and 1 may not be off/on. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause SNVT_Occupancy has the following values: 0 - Occupied 1 - UnOccupied 2 - ByPass 3 - StandBy If the time object does not use the correct default and active values then the wrong value will be sent from the time schedule. I/NET controls with the "first of the pair, second of the pair" which may require a 0 to be ON and a 1 to be OFF. Resolution Modify the Time Object for a SNVT_occupancy: In the Show Other Properties editor change the default value to 1 (Unoccupied). In each time event change the Active Value on the Other tab to 0 (Occupied). If edited offline, generate the project and send to the target.

Issue User limitations in a Xenta Server Environment Xenta Server Cause Setting up User rights on a Xenta Server Resolution Web Users: Web Users are created only from the Web Interface, not XBuilder The limitation on web users is based only on available controller memory A normal user should use less than 100 bytes Excess numbers of users will limit your potential use of controller memory Simultaneous Users: In XBuilder, click on the Xenta Server object Scroll down to TCP/IP Settings and select "Max. number of HTTP sessions" the default if 15, but this number can be modified to between 10 and 20 users. FTP Users: In XBuilder, click on the Xenta Server object Scroll down to FTP settings and select "Max Users" The default number is 4, and the maximum is 5 users.

Issue Continuum 1.9x and above will not install correctly on a PC / Laptop that is on a domain, One example: When trying to run the Continuum Database Initialization program the following error message may pop up: You must have local NT administrative privileges to run this application. Environment Windows OS 7 8 10 Continuum 1.9x 2.x Inet SQL 2005 SQL 2008 SQL 2012 Cause Microsoft has introduced the use of a higher level of security in the install of their SQL database software SQL 2005 / SQL 2008 / SQL 2012. When you install Continuum you need to make sure you are logged onto the PC / Laptop as a local administrator, in the case of a lot of a corporate networks, you are most likely logged on as ether a restricted user or a domain administrator, these logons do not have the privileges you need to install an SQL database. Resolution Step by step guide to creating a local administrator user on your PC / Laptop Go to "Start" then "Control Panel" in Windows (Windows 7 and above, top right corner change "view by" to "small icons" this will show all icons) Go to "Administrative Tools" Go to "Computer Management" / "Local Users and Groups" In users, right click on the right panel and add new user Fill in the user name and password, un-tick user must change password Tick password never expires then ok it Now go back into control panel and click on "User Accounts" Click on the name you just created, this will open the properties screen (Windows 7 and above click on "Manage user accounts") Click on "Group Membership" then select others, and highlight administrators (Windows 7 and above double click on name you created, click "group membership" click "other" then in the drop down select "Administrator") Apply this and then ok it. Log off your normal account and log back on as the new user you have just created

Issue Changes made to Device Templates in the XBuilder Device Editor for interfaces with Modbus, BACnet, etc are not seen by the controller after download. Environment XBuilder 5.x.x Xenta Server 5xx/7xx/9xx Cause Device Template files are not recognized by the device until the unit has restarted. Resolution When downloading the project to the Xenta Server select to "Send all project files".  This will force a warm start of the device causing the changed Device Template to be recognized.

Issue I have an obsolete floating / proportional / two-position actuator connected to my controller.  Need to replace the obsolete actuator, preferably without modifying the controller or valve. How do I locate a replacement? Environment Obsolete electronic actuator Cause Find replacement parts for obsolete actuators. Resolution Use the Schneider Electric Cross Reference Tool

Issue Disable FTP (File Transfer Protocol) in all X5/7/9xx controllers Environment Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 Cause In some high security project installations, local IT groups require that FTP (File Transfer Protocol) be disabled on all devices within their network. Resolution FTP into the Xenta 5/7/9xx controller by typing FTP://x.x.x.x (where x.x.x.x is the IP address of the controller) in the Windows Explorer address bar. Login with the root username and root password. Browse to the sys/system/ftp.cfg file and copy it to the desktop of the local machine. Open the ftp.cfg file with notepad on the local machine. Set the FTPMaxUsers="4" line to FTPMaxUsers="0" and save the file. Copy the file back to the FTP session on the controller and paste / replace it over the existing file. Logout of the FTP Session Cold start the controller Now the Xenta 5/7/9xx controller will not have FTP access. If there is a need to re-enable FTP please follow this steps on the Xenta 511, 527, 555, 701, 711, 721, 731, & 913 Login into the controller via the web interface with the root level username and password. Navigate to Configuration > Servers > FTP Server Set the Max. number of users back to a valid number of 1-5 and click save. Cold start the controller. If FTP needs to be re-enabled on the Xenta 527-NPR the only option will be to reload the system program. This is because the 527-NPR does not have a full web configuration interface like all other Xenta 5/7/9xx controllers to set the number of users.   Update note: In later versions of the Xenta Server, FTP is disabled by default (the number of users are set to 0). If you still can't login to FTP, try to format the controller, reload the system program and try it again. Then it should work now.

Issue Can I send live data over SNMP? How many trap pages can I define? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731 Cause All Xenta Servers (except Xenta 913 and Xenta 527-NPR) have a built in SNMP agent. However, the SNMP protocol in them cannot handle sending live data over SNMP. It can only send alarms along with specific fields of those alarms.   Resolution The Xenta Server supports SNMP version 1 and SNMP Traps. It can only be used to send SNMP and not to receive. The first step to setting up SNMP is to create alarms in XBuilder and link the points to the alarms that are to be monitored. Then, the filters used by the SNMP traps should be defined. This is done using SNMP trap pages. SNMP Trap Page The SNMP trap page is where you define a set of rules in Xbuilder of when to send a trap to the SNMP manager. This includes severity of the alarm or a wildcard string based on the address of the point.  In XBuilder you can create up to 10 SNMP trap pages, which will give you possibilities to define 10 different alarm filters. An SNMP trap page is created by right-clicking a folder in the System pane of XBuilder and then selecting New > Page > SNMP Trap Page. (It is recommended that a separate folder be created for SNMP trap pages and that this folder be restricted to only system administrators.) Once the SNMP trap page has been created it is then configured by right-clicking on the SNMP trap page object and selecting SetupSNMP Trap Filter.   SNMP Field Configuration The SNMP field configuration is where you define what 8 pieces of data will be sent to the SNMP manager (due to the UDP limit of 8 fields). That data consists of things like date/time, type, address, priority, description, etc. The SNMP field configuration is accessed by clicking on the Tools menu and selecting SNMP Field Configuration.     For more information on SNMP in Xenta Servers please see the TAC Xenta Server - TAC Networks Technical Manual, section 16. Note: SNMP is only supported by Xenta Server devices and is not supported by TAC Vista.  

Issue Modifying alarm tripped text and reset alarm text on a Xenta programmable controller under a Xenta Server is not reflecting these changes. Environment Vista 5.x.x/4.5.0 Xbuilder 5.x.x/4.5.0 Cause When the Xenta programmable controller is added to the LonWorks network under a Xenta Server an alarm object is created in Xbuilder with the Tripped Alarm Text and Reset Alarm Text from the MTA file. Updates to the MTA file or alarm object in Vista server does not update the Xbuilder project. Resolution Edit the Xenta Server object and modify the Tripped Alarm Text and Reset Alarm Text for the in the Alarms folder under the programmable controller in the Network pane of Xbuilder.

Issue Installing VisiView on Windows 7 Environment Windows 7 VisiView   Cause Supported operating systems Resolution VisiView will not work on Windows 7. Windows XP Pro is required. The upgrade path would be to use a Xenta 555 or Xenta 731.

Issue What resources are available to get more information on the M-Bus protocol? Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment M-Bus Cause The M-Bus protocol information is available on www.m-bus.com. Select The M-Bus: A Documentation Rev 4.8 Resolution The M-Bus protocol specifications is broken down in multiple chapters. Basics of Serial Bus System Overview of the M-Bus Physical Layer Data Link Layer Telegram Format, Meaning of Fields, Communication Process Application Layer Structure of fixed and variable data blocks. Network Layer Appendix Table of units, medium, data field codes, VIF extensions.

Issue When Remote Alarm Manager sends a SMS message via a GSM to a mobile phone, the message is truncated.  Environment Sigma, Micronet, BAS, RAM Cause Message type - Long Message (Descriptive multi line message) Output interface - GSM to mobile phone. If an alarm is sent from an output interface e.g Sigma to an output interface e.g SMS mobile phone, the end of the message disappears (truncated).  Resolution The message sent to the mobile device is too long. A maximum length of 160 characters is permitted - this is a SMS message characteristic. Consider changing the message type to a Normal message or Short message or The Index Title and Point Title are very long, can these be shortened. e.g change Temperatures to Temps.

Issue Attempts to login are unsuccessful and device reports that logins are blocked. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server tracks attempts to log in by recording the IP address and Username of the login attempt. After 5 login attempts it will block any attempts to login to with that username and IP address for 10 minutes. Resolution Use a different user account on the Xenta Server to login and perform the necessary work or wait 10 minutes for the lockout to expire. If the lockout is continuing after 10 minutes then ensure that if the Xenta Server is in a Vista database that it is not running and trying to communicate to the Xenta Server with an incorrect username and password. Any changes to the root user password must also be changed in the Vista database to avoid perpetual blocking of login attempts on that computer and IP address.

Issue What LonWorks data is accessible from a Xenta Server and what can the data be used for? Environment Xenta 500 Xenta 700 Xenta 900 XBuilder Cause There are different types of data accessible on a LonWorks network. TAC network variables / Public Signals - TAC proprietary communication for signals from Xenta programmable controllers SNVT - network variables available for bindings SCPT/UCPT - Configuration properties for LonWorks devices. UNVT - User defined SNVT. Data accessible from a Xenta Server can be used in Xbuilder in multiple ways: Polling - value polled for use in graphics page, values page, alarm, trending, and scheduling. Connection object - poll and send process to pass value from one device to another (could cross protocols). SNVT binding - binding from a SNVT created on the Xenta Server. Resolution Use the following table to identify which signals types are supported and how they can be used. Data type  Polling Connection Object  Binding  Public Signals  Yes 1  Yes 1  No  SNVT  Yes  Yes  Yes 2  SCPT/UCPT  No  No  No  UNVT  No  No  No 1 Xenta Server must be commissioned to have the TAC group address in its address table. Create group bindings in TAC System Plug-in for LNS networks Commission LonWorks network for Xenta Servers in Classic networks Commission and download Xenta Server acting as LonWorks unit in a LonWorks group in Classic network. 2 SNVTs must be created by Xbuilder on the Xenta Server device. These SVNTs are then bound using a network management tool such as LonMaker or NL-220.

Issue XBuilder project was upgraded and OGC graphic pages were converted to TGML using the automatic conversion. The same names were used for the graphic pages, but they will not display in the web interface. Java console reports: java.io.IOException: Wrong file format feature < 0 or reature > 7  at se.tac.applet.graphics.ogc.OGCStreamHeader.load(Unknown Source)  at se.tac.applet.graphics.ogc.OGCPicture.loadPicture(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.go(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.init(Unknown Source)  at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)  at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 711, 731 Cause The graphic object was properly converted, but the graphic page is still using the old template (Graphics.html) which is designed for OGC graphics instead of the new graphics page template (TgmlGraphics.html). This causes the java to interpret a TGML graphic file as an OGC graphic file. Resolution This can be resolved two ways Manually edit the Template property of the Graphic page objects in XBuilder to be TgmlGraphics.html. Delete the graphics page in XBuilder and recreate it. When the graphic object is linked to the graphics page it will properly assign the correct template based on the type of graphics file type.

Issue In XBuilder there is a setting called "Max number of HTTP sessions" that can also be found using the web interface by navigating to Configuration > Servers > HTTP Server. What does this setting do? Does it limit the number of users who can log in simultaneously? Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause This setting is somewhat vague and is sometimes believed to be a limit on the number of simultaneously logged-in users. Resolution The Max. number of HTTP sessions is set to a default value of 15 and can be set to anywhere from 10-20. This setting does not limit the number of simultaneously logged in users, however. The TAC Xenta Server - TAC Networks Technical Manual explains this setting as follows: HTTP The Xenta Server is an HTTP (Hypertext Transfer Protocol) server. Several users can view the web pages at the same time, but they are limited by the number of HTTP sessions allowed. Max. simultaneous HTTP sessions, choose a number from the list. The default setting is 15. Several users can view files at the same time. What is an HTTP Session? Internet Explorer is an HTTP client, sending requests to the Xenta Server. The HTTP server in the Xenta Server receives the request and, following any necessary processing, the requested file is returned. An HTTP session is the connection that exists during data communication between the web browser and the Xenta Server. The session ends when all the data has been received. Rules of Thumb Each web page (values page, alarm page, and the graphics page), sets up a full HTTP session. When loading a web page, a number of sessions may be used simultaneously, depending on the number of sessions available.

Issue Can Inovonics wireless equipment be used with Xenta Servers? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Inovonics Frequency Agile product line which is compatible with the Xenta Server driver is being obsoleted by the manufacturer Inovonics at the end of 2011. Resolution If you have existing devices installed in the field then they should continue to work and function. New installations should explore other options for wireless sensors due to unavailability from the manufacturer. The ability to add a RS232 wireless Inovonics interface was removed from XBuilder beginning in version 5.1.8.

Issue After importing a pointlist to XBuilder and downloading the XBuilder project, all values both in TAC Vista and on a values page in the Xenta Server are shown as Invalid Address. VisiSat is still working and you can connect to the controllers using the Xenta Server as a IP tunnel. Environment MicroNet Xenta Server Cause This is due to a problem with a double point address in the pointlist, meaning that two points have different names, but the same table reference. Resolution Make a new pointlist in VisiSat. Mark all the points in the pointlist and copy all the points to the new pointlist. You will now get an error message showing you which point is represented more than once in the pointlist. Correct the points until errors stop, copying the entire pointlist. Export the pointlist for XBuilder, and import it again. Download to the Xenta Server.

Issue MN-LCD Uploading Environment Micronet LCD Display (MN50-LCD, MN50-LCDP, MN-LCD-100, MN-LCDP-100) Cause There are instances where an Micronet LCD has failed to upload a configuration from a MicroNet controller correctly. Resolution The following describes the correct process for downloading an LCD screen to a controller and uploading this to an LCD. If these procedures are followed, no problems should occur. How the LCD upload process works When an LCD configuration is sent to a MicroNet controller it is placed into controller RAM. When an LCD is connected to the controller it looks for the presence of this file and if it exists, this file is transferred to the LCD and stored permanently in EEPROM. This transfer process removes the controller copy of the LCD configuration; this means that should replacement of the LCD be required later the LCD scheme will need to be downloaded to the controller again. It is important to note that because the LCD file is initially stored in the controllers RAM it will be lost if the controller power is cycled or the controller is reset. LCD Download procedure Switch on power to the controller and then use VisiSat to configure and download the LCD configuration to the controller. If the controller is NCP and is to operate standalone, disconnect the communications from the controller before connecting the LCD and ensure that the LCD comms links are fitted to the controller (this is important). If the controller is NCP and is networked an MNN-COM card is required in the controller and the LCD must be remotely mounted. Make sure that the controller power is still switched on. Connect the LCD to the controller and apply power to the LCD. Note: Do not depress or hold any keys when connecting the LCD, this is only required if LCD firmware is revision J or earlier. Wait for the LCD to load its configuration. If the LCD configuration fails to load, check that the controller’s “Configuration Locked” property is not set to ”Yes” in VisiSat. Remove the protective strip from the LCD battery.