Building Automation Knowledge Base

Issue Procedure for replacing an MR-VAV-AX Environment I/NET MR-VAV-AX Cause Hardware is in need of repair or replacement Resolution Ensure that you have a valid .sav file for the ASC.  Remove defective MR-VAV-AX hardware Copy DIP switch settings of the old MR-VAV-AX to the new MR-VAV-AX Re-verify hardware terminations to ensure that wiring did not cause the existing device to need repair Power up the new MR-VAV-AX At the I/NET workstation, connect to the appropriate Sub Lan Interface controller. Select Edit>Controller>ASC Parameters Click Update ASC Select the address of the replaced MR-VAV-AX and click OK Once the download is complete select the address of the replaced MR-VAV-AX Click Restore Once the download is complete verify controller function

Issue Running SevenReports a C++ Run Time error. Happens either in Archive data reports or database reports yyyy-mm-dd hh:mm:ss Environment I/NET Seven version 2.16 to current Cause Scope of Data yyyy-mm-dd hh:mm:ss Resolution    The C++ Runtime error or crash of SevenReports is due to a timeout problem because the archived data is so much information. What you will need to do is a couple of things listed below: Run the archive file SevenReport or ArchiveSevenReport file with the following steps in mind 1. If using Archived reports, mount the archive file with the desired dates to search 2. when the date range comes up on the screen, offering to search with date, hour, minutes, and seconds yyyy-mm-dd hh:mm:ss limit the time range. The whole key here is to limit the time range. Example of range is below.   In other words, search for only 2 minutes on just one day. Do not put in three days, or three hours. Only search within a very limited search window. The crash occurs because there are huge archive or database entries with thousands of transactions that have to be sorted and searched through. The crash was due to the report program attempting to generate a report with to much data to sort through. Be patient. Even on old computers, with XP, 500MB or RAM, and limited resources, the reports will be produced.  Time and time again, this issue comes across. Using my old computer in the lab, the database from the customer is loaded, the archive files are loaded and still it works every time. The C++ Run Time error appears when expanding the search to more data and crashed the report. But limiting the amount of time to minutes or perhaps one hour, produces a report. (For an example of unusual examples: there have been 2 minutes of time for the search criteria, and 38,000 pages of report produced.)     2010-08-16 09:00:00 until 2010-08-16 09:02:00   One thing you may want to look into at your site if you are experiencing large amounts of data for reports is Scan Interval. Read TCON300 for more info. Information on Scan Interval and how this information is collected in the database. This is important because the more data you collect, the faster the scan rate interval, the more data will be in the reports. Input and Output Points Point Database Parameters   The Scan Interval field is used with all point types. Enter a number between 1 and 255. This is the length of time in seconds that elapses between point scans.   If the point is an external input point, the controller scans the point at the interval you specify here, and updates its state/value in RAM memory of the DCU.   If the point is an external output point, or an internal input or output point, the scan interval determines how often a calculated point equation controlling the point (if applicable) is processed.   If the point is an indirect input or output point, the scan interval governs the time it will take to go to the “old data” state.   The default scan interval is 10 seconds for input points and 60 seconds for output points. All points can have their own unique scan intervals. All external discrete input points are scanned for discrete contact changes at 100 millisecond intervals.   Note: Defining an individual scan interval reduces available RAM memory in the DCU by approximately four bytes. You can conserve DCU memory by using the same scan interval for multiple points.

Issue When opening I/NET and getting an Initialization failure error and unable to log on to start the program. Product Line TAC INET Environment I/NET Revision 2.40 and higher on Windows 7 PCs. Cause There was a security update that disabled the Named Pipes and TCP/IP that is required for SQL to run. Resolution Start , All Programs select Microsoft SQL 2005 or 2008 Expand Configuration Tools and select SQL Server Configuration Manager Select SQL Native Client Configuration and expand it then click on Client Protocols Verify that TCP/IP and Named Pipes are enabled Click on SQL Server 2005 Network Configuration and click on Protocols for MSSQLSERVER Verify that Named Pipes and TCP/IP are enabled Open up Services and verify that SQL Agent, SQL Server and SQL Browser are all running and set to automatic. Start the I/O Configuration and verify that the connection is made to the correct database Restart I/NET again and it should allow you to start the program now. For Remote Client with I/O Configuration: Repeat the above on SQL Server PC Ensure that port 50069, 1433 and 1434 are open between the PCs

Issue 7770, 7771, 797, 7801 TAP replacement needed with existing system. Product Line TAC INET Environment Existing TAC I/NET Seven environment Cause The 7771 was the first generation ICI that the 7797 platform replaced. The 7771 was built on the old 7801 tap hardware where was the 7798 was built on the 7790 MRI platform. Neither of which are supported or available to purchase anymore. System upgrade for more capabilities or capacity, or hardware failure Resolution For the 7801 tap hardware, the Xenta 527 would be a suggested choice for replacement. For the remaining TAPs, the Xenta 913 would be a direct replacement. The TAC Xenta 913 is a cost-effective way to integrate a large variety of products into a TAC network. The TAC Xenta 913 supports the most commonly-used open protocols, like Modbus, BACnet and LonWorks. It also supports some manufacturer-specific protocols, like I/NET and Clipsal C-bus. The TAC Xenta 913 acts as a gateway and transfers data point values from one network to another. Configuration is carried out using the TAC XBuilder programming tool. For more info including the documentation, manuals, and datasheets, visit the Schneider Electric Extranet at the following link, which guide you to the replacement for the ICI. TAC Vista > Technical Documentation > Specifications Sheets  

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 Microsoft Visual C++ Runtime Library Error After you install I/NET on a computer containing Microsoft Office XP or one of the Office XP programs, you may receive one of the following error messages: Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSDMN.EXE abnormal program termination Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSEARCH.EXE abnormal program termination Environment XP computers containing Microsoft Office or other loaded programs, one of which may be I/NET  Cause This behavior occurs if a program (not necessarily I/NET) conflicts with the Mosdmn.exe and Mosearch.exe files or with video settings, antivirus or 3rd party programs conflicting with your operating system. Resolution The Mosdmn.exe and Mosearch.exe files are part of the "Support for fast searching" feature in Office XP. This feature is similar to the Find Fast feature in Microsoft Office 2000. Fast searching uses the Indexing Service in Office XP to create a catalog of Office files on your computer's hard disk. To resolve this issue, use the following methods, as needed, in the order presented. Method 1: Clean Boot with Only MoSearch The Mosearch.exe (Microsoft Office Search Service) and Mosdmn.exe (Microsoft Office 10 Search Filter Daemon) Startup items may be conflicting with some other program (or programs) running in the background. Therefore, clean boot your computer with only MoSearch selected on the Startup menu to determine whether this program is the source of the conflict. To do this, follow these steps:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the General tab, click Selective startup. 4. On the Startup tab, click to clear all check boxes except for MoSearch. 5. Click OK, and then click Yes when you are prompted to restart the computer. 6. If the error message can be reproduced, repeat the preceding steps. In step 3, also click to clear the Process System.ini file and Process Win.ini file check boxes.   If the error message cannot be reproduced, this indicates that MoSearch is conflicting with some other program or programs running in the background. Follow these steps to locate the conflicting program:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the Startup tab, click to select one of the check boxes. 4. Click OK, and then click Yes when you are prompted to restart the computer. 5. If the preceding steps reproduce the error message, the last item added to the Startup menu is causing the conflict. If the error message is not reproduced, repeat these steps until all Startup menu check boxes are selected. 6. If all the Startup menu check boxes are selected and the error message is still not reproduced, start Msconfig again, and then click to select the Process System.ini file and Process Win.ini file check boxes.   Restart the computer. You may need to install a clean version of I/NET depending on your computer setup.   This is the solution for the Microsoft Visual C++ Runtime Library error with XP Office. Other solutions may entail removal or reconfigure of video drivers, antivirus programs, or other 3rd party programs conflicting with your operating system.

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 Need to sequence several outputs to be on for 10 seconds then off for 15 then the next on for 10 and so on, but the site has specified no event sequences are to be used. Environment I/NET DDC Cause Need to sequence several outputs to be on for 10 seconds then off for 15 then the next on for 10 and so on, but the site has specified no event sequences are to be used. Resolution Create a DDC relay for output 1 that is an interval timer relay with the time set to 10 (time the device is on) Set the DI select to an input trigger point Create a second DDC relay to function as a delay before make relay. Set its time to 25 seconds, or the device on time plus the interval time before the next output. Set the output of this relay as a Line and the DI select as the trigger point. Copy the DDC relay from step 1. Change the DI select to the line from the previous step and the Output to the next device in the series. Copy the DDC relay from step 2. Change the DI select to the output triggered in the previous step and change the Output to a new line. Copy the DDC relay from step 1. Change the DI select to the line from the previous step and the Output to the next device in the series. Copy the DDC relay from step 2. Change the DI select to the output triggered in the previous step and change the Output to a new line. Repeat steps 5 and 6 until you have completed the series. If you wish for this to cycle in a loop, have the output from the last Relay trigger the DI point which starts the series. If this is an internal point you may want to add a calc to keep it equal to 0.

Issue I/NET Reference Host Suggested Configuration Environment I/NET NPR Xenta 527-NPR Xenta 527 Xenta 913 Xenta 731 Cause There are many opinions about the correct use of Reference Hosts.  This is a suggested use which will be successful for most sites. Resolution  From TCON 298 A Reference Host is any TAC I/NET workstation, NPR, or Xenta 527/527-NPR that will serve as a source of IP addresses. Any of these devices attached to an Ethernet LAN can be used as a Reference Host.  Each time I/O Server is started on a workstation, it provides the workstation’s IP address to each remote host designated as a Reference Host. I/O Server also requests and receives a list of all host IP addresses that are known to the remote host at that time. I/O Server must be running on the remote host for this address exchange to occur. I/O Server compiles and maintains a list of all the remote hosts that it learns about. Ultimately, all hosts in the network will know the IP addresses of all the other hosts.  Ideally, you should determine 1 or at most 2 devices to serve as your Reference Host.  This device would ideally be a Xenta Server or an NPR, but a Host workstation that has I/O Server running 100% of the time will work as well.   All devices on the system will use this as a single Reference Host. No others are needed.  When the device comes online it will contact the Reference Host and get the site’s Routing Table.  The Reference Host can have an empty routing table.  Once the Routing Table is shared, Reference Hosts are no longer needed.  You can leave the single entry in place. This will allow a quick recover, in the event of a critical system failure.  Here are a few reasons for using multiple Reference Hosts: Temporarily add a new device as a Reference Host on the Sites Reference Host or a workstation to aid in bringing it online A large site may desire to have 2 Reference Hosts in case one is offline when a device comes online. An  I/NET site that spans multiple locations may wish to declare a local Reference Host for each building and a network Reference Host

Issue Running I/O Server as a service and an error 1075: The dependency service does not exist or has been marked for deletion pops up. Environment Running I/Net as a Host Tool under TAC Vista and wanting to configure I/O Server to run as a service. Cause I/O Server requires that MSSQL be tied to the dependencies of the service and when it is not listed, it will generate that error. Resolution When this error comes up, there are several things that needs to be checked to verify that it is set and connecting to the correct database in I/NET: Right Click on My Computer and go to Manage. Select Services and Applications, expand that and select Services. Select I/O Server, Right Click and select Properties then click on Dependencies. MSSQL should be listed in there and more than likely it is not and has to be added. To add it, go to run and type regedit, go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\INet7IoSrv] DependOnService – add the SQL instance (for example MSSQL$TACVISTA) and the TAC Vista Server (TACOS). This multi string value should list:RPCSS,TACOS, MSSQL$TACVISTA Restart the PC and it I/O Server should be running as a service now.

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 ASC stopped communicating Continuous Lost/Restore Reset the memory in an ASC Controller Product Line TAC INET Environment I/NET SubLAN Controllers All ASC Controllers Cause When the MR-AHU resides on a communication sub-LAN, it is susceptible to communication errors from external sources. These communication errors could result in corruption of the ASC's NOVRAM. When this occurs, the ASC will stop communicating, or will cause continuous Lost/Restore messages. For this reason, the ASC is provided with a means of clearing its NOVRAM. Caution: Clearing the MR-AHU memory causes the binary instruction set for the controller to be deleted. In order to reload the binary instruction set, you must have a TAC I/NET host with the appropriate UPD files, and the ASC Controller must be communicating through an interface controller (MRI, MCI, or I/SITE LAN). Resolution Prior to clearing NOVRAM of the ASC and you are using MR-VAV's and they have already been balanced, VAV parameters must be recorded (screenshot may be the quickest method). Follow the following steps to RESET the device  Remove power from the ASC. Set DIP switches 6 through 12 to the "On" position and restore power. Remove power again. Set DIP switches 6 through 12 to the "Off" position and restore power. Remove power again and reset the switches to their normal configuration. Normal communication should be restored to the ASC. If not, then the problem lies elsewhere. Once communication is restored, perform an "ASC Update" from the TAC I/NET host to restore the NOVRAM image to the ASC. Refer to the TAC I/NET System Operator Guide for ASC Update instructions.

Issue Downloading a save for a 7793 MCI to a 7798 MCI, what needs to be done to accomplish this task. Environment All versions of I/Net that uses both the 7793 MCI and 7798 MCI. Cause System running multiple controllers and wants to switch out one for another for functional purposes. Resolution Note: This only works if you are using the first address points of the 7793 MCI. Start I/NET and go to the Offline Editor Connect to the 7793 MCI and select copy Create the file and choose the 7798 MCI Once completed, connect to the 7798 MCI and go to Resident I/O point. Verify that the point addresses are correct Make necessary changes to names, add, delete, modify accordingly Once completed, save and exit. Connect to the 7798 MCI and select Software Restore, then download the new save file to the controller.

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 After running LANMON 3 on an I/NET C-LAN, it may return some error codes. The list below will help determine what they mean and the best way to address them. Environment I/NET Controller LAN LANMON output text file Cause Controller LAN errors captured by the LANMON program. Resolution One of the most useful new features of LANMon 3.0 is the detection and labeling of several types of communications errors. The label associated with the detection of a communications error is stored in the disk file just in front of the communications packet to which the error label applies. The error labels are presented in ASCII text along side the hexadecimal data. This text should allow most I/NET technicians to perform some level of useful investigation into controller LAN communications problems and reduce the necessity for sending LANMon files in to Technical Service for analysis. The following paragraphs lists the error descriptions associated with the type of errors detected by LANMon. The Bold text represents the label you will see on the screen or in the capture file when LANMon detects that type of error. ERR: Retry This error indicates that LANMon has detected a retransmission of the same command. This is the most common error type and can be used to find which controllers are having problems receiving from others. You should reference the destination and source addresses listed in the retry packet and accumulate/record this information. If there is a prevalence of specific nodes (destination or source) showing up in the retry packets, this would serve as a significant pointer to examine for network problems in that physical area (possibly in the cabling, environmental disturbances, power, grounding, and controller hardware and/or application software) ERR: LAN reconfiguration This error indicates that LANMon detected the occurrence of a LAN reconfiguration. This is a normal expectation when a controller/node is added or removed from the network as a result of LAN cable disconnect or power. When intentional changes are not in-work on the network configuration, a LAN reconfiguration is typically the result of several sequential errors (typically retry’s) which prompts the sending controller/node to initiate a LAN reconfiguration on the basis that it appears a node has been lost and everyone needs to have a new picture of the network layout. ERR: SDLC CRC Error This error indicates that the LANMon Tap received an RS485 packet with incorrect CRC indicating the packet is corrupted in some way. This error results from data distortion on the cabling or from intermittent disruptions such as from EMI, noise or grounding fault. With this error, the primary address you are interested in is the source address. If you are seeing a number of CRC errors from the same node address, or a collection of node addresses, you may want to look for cabling or loading problems in that area, or the length of cable getting to the area. You should make note of where LANMon is positioned when seeing this error. The error could be expected to get worse as to get further away from the reporting node address. For this reason, it is often recommended that you perform LANMon captures and analysis from at least two points on the network and those points should be the two most distant ends of the network. ERR: LAN master conflict with ## This error indicates LANMon has detected a NULL command output from a controller/node other than the currently recorded LAN master. The ## number will show the address of the node currently understood to be the LAN master. The packet following this error message will contain the address of the contending LAN master. This master conflict error is frequently the result of multiple simultaneous LAN reconfigurations. There should only be one LAN master and it is the function of that one LAN master to output the NULL command each time the token makes one pass around to all the network addresses and arrives back at the LAN master.   The following error descriptions will be encountered far less frequently and are not typically used for LAN diagnosis. ERR: Bad address LANMon detected a destination or source address greater than 3F16 (6310) ERR: Bad NULL LANMon detected that NULL was sent out without the same destination and source address, or without the broadcast header. ERR: Bad reconfigure LANMon detected that reconfigure command “01” was sent out without the same destination and source address, or without the FF broadcast header. ERR: Bad token LANMon observed what appeared to be a token command but had byte count greater than 3, or had destination and source addresses the same. ERR: Frame overrun LANMon received >160 bytes on the Async port from the LANMon Tap which exceeds design limits/expectations. ERR: Frame underrun Async frame from LANMon Tap to PC was considered too short to contain any SDLC (CLAN) data. ERR: Lost frame synch The LANMon program running in the PC got out of synch with the data stream from the LANMon Tap. This should be an unusual error. If it is repeatedly encountered, You can try running the LANMon utility on a faster PC, or you can try running it with Monitor mode OFF. B E1 m N O ERR: Bad frame CRC The LANMon program detected a CRC error in the Async frame of data from the LANMon Tap. With the standard short (6 ft.) RS232 cable between the PC and Tap, this should be a very infrequent error. ERR: Unknown error code This is a catch-all error indication intended to present any error codes returned from the SDLC controller in the Tap that are not currently defined. You should not see this error message. ERR: Frame too short The Async frame of data from the Tap to the PC is considered too short to contain a valid SDLC packet.

Issue When a SHR100-T is setup with a 0-10 volt humidity sensor the temperature reading fluctuates Environment Xenta controllers I/NET Controllers SHR100-T Temperature Humidity Sensor Cause Interference from the 24Volt AC power supply in the same cable causes this temperature fluctuation. Resolution  The two tested fixes that stabilize the temperature reading are. Set the humidity as a 4-20mA signal, this will stabilize the temperature reading. Run the 24Volt AC power supply in a separate cable. This is the better option if this is noted before installation is started.

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 When an Alarm point goes into Alarm, it needs to come up on the forefront. Environment All versions of I/Net using graphics. Cause When creating Alarms and the point goes in Alarm but does not come to the forefront and stays on the graphic page. Resolution For the page to come up front when the point goes into Alarm, the following steps needs to be followed: Select System, Edit Graphic Page. Open the page that the point is on. Select the point and Right Click to display the properties. Select the Automatic Page Display check box. Close the editor and then save the changes. NOTES: In order for the auto pop up feature to function, you will need to have the point masked for messaging. Also set AMT Configuration and Host Masking with the corresponding check boxes.

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.