Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (701) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Vista, I/NET, LON, MicroNet, ModBus Xenta Servers (Xenta 5XX/7XX/913) Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.4 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Xenta 511 X         C   X Xenta 527 X X     X C   X Xenta 527-NPR   X       S     Xenta 555 X   X     C   X Xenta701 X         ST 10   Xenta 711 X         C 10 X Xenta 721 X         ST 20 X Xenta 731 X X X   X C 20 X Xenta 913 *** X X   X X S     * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service.  NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.5 major features please read Xenta Server after version 5.1.5 (5.1.5 included) Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Cannot download bin file to a MIP upgraded 7700 controller Environment PCU 7700 MIP Cause RAM memory may need to be cleared. Resolution To clear RAM memory on the MIP card: Disconnect Power (failure to do so will permanently damage the device) Determine how many RAM chips are on the MIP card Each RAM chip has a corresponding Capacitor. C4, C5 and C6 ( you can have up to 3 RAM chips) Short across each capacitor 1 at a time Reconnect power

Issue Date and time gets incorrect periodically in TAC Xenta Programmable controllers Time stamp in alarm list is incorrect Time stamp in alarm list is wrong  Vista Server local time and the local time in all Xenta controllers in the network go out of synch.   All local time settings are correct in TAC Xenta Environment TAC Xenta 30x/401/28x Cause The time in a TAC Xenta can be changed by TAC Vista TAC OP, note that a change of the time in one controller is broadcasted to the whole network. TAC Xenta group master will broadcast the time to it's group every 24 hours A Xenta Server (Xenta7xx, Xenta5xx, Xenta 913) Menta, this only affects the controller Menta is connected to. Most likely, the problem is a Xenta Server in the network that has the wrong time. It can be enough that a Xenta server is connected to the network, it does not have to be configured in this network.. Resolution Log in to Xenta server from the web interface. Go to Configuration-time If the date and time is incorrect set the correct date and time. Click on time synchronization, the lonworks time synchronization should only be set to enable  if this is a Xenta Server in TAC Vista or if this is a site that does not have TAC Vista on it and it is the only source to sync the time to.

Issue Remote Client Option is missing from Workstation Options in I/NET 2.40 I/NET Configuration Profile. Environment I/NET Cause The I/O Server must be shut down in order to make this change to an I/NET Configuration Profile. Resolution Close the Configuration Profile Editor Exit I/NET Shut Down the I/O server From the Start Menu, Open I/NET Configuration Profile Editor You should now be able to set the computer to Remote Client

Issue Is there a way to use firewalls to stop routing tables from being delivered? For example, can you shut down port 50069 to prevent routing tables from updating while you cleared device routing tables? Product Line TAC INET Environment I/NET Seven Network with system-wide ethernet Cause There are bogus entries in the Routing tables in the PCs and NPRs in the I/NET system. Resolution Blocking the port will certainly stop I/O servers and NPRs from sharing their routing tables.  The real problem, though, is in getting all devices cleared before you open the port back up. The following would be a reasonable approach to clearing a routing table system from a desk, if the customer does not want to go to each location. Ask the IT department to block port 50069 for each device on the network Telnet into each NPR or Xenta 527 and PC to clear the routing table using the DELALL command Correct Reference Host settings Ask the IT department to open port 50069 to each device on the network after you have cleared all sites. Please note that all of the devices have to be cleared before the firewall is taken down.  If you have one of the devices offline at the time of the cleaning, you could re-populate the deleted routing table again. Another option would be to firewall port 50069 between segments of the network to ensure only part of I/NET was visible to specific regions.

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 Vista Change of State object  monitoring an I/NET point value are in Alarm  but not changing state or getting through to Vista Alarm queue. Environment I/NET point monitoring Vista Alarm Queue Xenta Server Alarms I2V Cause Incorrect settings of the I/NET point Watch Status, and Vista Change of State object. Resolution There are a few settings unique to I/NET points that have to be properly modified in order for an Alarm to be passed into the Vista Workstation Alarm queue. In Workstation, navigate from your Xenta Server to the input/output point generating the Alarm in I/NET. Right click on the point and select Properties.  Set the Watch Setting to "Alarm". Navigate to the Change of State object that is referencing the I/NET point to create the alarm. Right click on the Change of State object and select properties. Set the Alarm triggering text field to the value expected in alarm condition, i.e. 1. Set the Alarm resetting text field to the value expected in back to normal, i.e. 0. Toggle the I/NET point manually into alarm and return to normal once to verify the alarm is in the queue.

Issue Global Point Settings for DLA systems Global / Indirect Points connected over Ethernet continue to report "old data" Environment I/NET Cause When converting to DLA, a router is now between Global and indirect points that may be on the same link. The router will block any message that does not have a global level of "System" The NetPlus Routers (NPR) must have their reference hosts set correctly so that all IP devices know each other exists.  Resolution Connect to each global point on each link or DLA site. Modify each point so that its global point level is "System" If the global points are still not functional, follow this procedure: Modify the Reference host table on each device to point to one master (NPR or Workstation) Reset power on each device to request the routing table Restart the I/O server on the host machine

Issue Deny Entry Tenant when entering new badges after restoring from a system crash on a New Host workstation Environment I/NET Cause Devices in the field may still be looking for the former workstation due to a system setting such as automatic DPU restore. Resolution Connect to the controller Select Edit>Controller>Station Save Select Edit>Controller>Station Restore Select The DPU option Select the affected DPU and click okay Try a badge to verify results This error should only occur when badges are added immediately after a system recovery.  If the issue continues, contact product support.

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 The A and B Channels used to communicate to Sublan devices need to interface with FOI (Fiber Optic Interface) devices, but not sure what speed it communicates on or what setting it should be. Environment I/NET Seven Controller Lan on a 7793 MCI. Cause Setting up a 7793 Controller to communicate to a FOI. Resolution On a 7793 MCI, there are several ports that are used for communication to various devices. These ports are: A standard synchronous RS485 controller LAN Port. Two standard asynchronous RS485 sub-LAN Ports. Two asynchronous RS232 ports, one used for the HHC Console and the other for Direct Connect to a PC. An optional plug on-board with an RS232 synchronous connection used for an external modem.

Issue Forced Door and Door Open Too Long Alarms not Showing up in Controller Summary Environment I/NET Cause Request to exit device is being activate triggering  valid entry rather than a forced door. Incorrect Message Type Settings Incorrect Masking Settings Resolution Request to exit device is being activate triggering  valid entry rather than a forced door. Connect to the controller Select Edit>Controller>Doors Modify the door Change the Door Release Switch to "None" Test The door Re-set the Door Release Switch to correct setting and troubleshoot hardware Incorrect Message Type Settings Connect to the controller Select Edit>Controller>Doors Modify the door Verify that the Message type for Forced Door and DOTL are set to "Alarm" Verify the Masking for the Door Test The Alarm Incorrect Masking Settings Connect to the controller Select Edit>Controller>Resident I/O Modify the Reader Point for the door Ensure that making is selected and that there is a message priority and an Alarm Priority. (This should match the previously noted settings from the Door editor) Test The Alarm

Issue Temporary day cards set between 9:00am and 6:00pm, are not disabling until the next day or until the controller has been reloaded Environment All windows versions I/NET Seven version 2.15 or below Cause This was an issue with the I/NET software not synchronizing with the controllers in real time after updates where made to the controllers and personnel. Resolution Upgrade to version 2.16 or above as this was fixed in hot fix 2.15b

Issue Customer gets the error "Denied Entry SEL" when they swipe any of their cards Environment All windows Versions All I/NET Seven Versions Cause This is due to Time Schedules not present in I/NET Resolution Create Time Schedules for the doors. In the 7920 (Mipped) 48 K boards and SCU door controllers, put in a door schedule from 00:00 to 23:59 so it is 24 hours. If a Secondary Schedule is set up for an individual on doors that are controlled by a 7920 DPU that use the standard EPROM chip, a “Deny Entry Select Message” will be generated in the Transactions. If 7910s are present then the same above rule applies.

Issue Graphics points appear OK, but are not dynamically updating. Alarms and messages appear in the AMT. Double clicking on a point on the graphics, the displayed value is significantly different to what is displayed on the graphics page. Graphics have question marks for the data. Rebooting the PC makes data viewable again on the graphics. This happens regularly over time. Product Line TAC INET Environment I/NET Seven 2.15B through to 2.30 Cause Changes in Microsoft Windows video/graphic files have meant changes were required to the I/NET Seven Software.   Resolution Upgrade your I/NET Seven system to 2.31 or above.

Issue Site Using AC or Enrollment Reader getting Denied Entry Tenant message on all new badges Environment I/NET Cause Improper AC Reader Configuration.  This was noticed after restoring from a backup to a new machine. Resolution Using the Start Menu, Open I/NET Configuration Modify the Active Profile Change the AC Reader Type and AC Reader Port to the correct settings for the site Click Okay Restart the I/O Server.

Issue In newer versions of XBuilder, when importing I/NET sav files into the project, an attribute called "flags" is included.  In an I2V integration, this signal can be used to decode the binary flags associated with an I/NET point. Product Line TAC INET, TAC Vista Environment XBuilder 5.1.5 and later Cause In earlier versions of XBuilder, each binary flag was separated out into an individual signal.  These signals include: test manual alarm old unack alarm_ack Binding each of these values (along with value, state, and/or control) for every point displayed on a graphic could quickly cause the number of bindings to expand to a number that caused performance issues with TGML graphics.  To combat this, all of the binary flags were combined into one signal called "flags." Resolution The masking for the flags signal comes from the communications format of I/NET: 7 6 5 4 3 2 1 0 Test Alarm Alm Inh Unack Old Manual Not Used To use these in a TGML graphic, read in the flags signal to a component attribute.  Then read the value and mask off the necessary bits: test = ((flags & 128) == 128); alarm = ((flags & 64) == 64); unack = ((flags &16) == 16); old = ((flags & 😎 == 8); manual = ((flags & 4) == 4); Test, Old, and Manual can be used to append the point value with a T, O, or M, respectively to emulate an I/NET environment.  Logic will need to be written to read in the alarm and unack signals: alarm unack inhibit result false false   No alarm condition true false false Alarm is still active, but has been acknowledged true false true Input active, but no alarm condition false true   Alarm has cleared, was never acknowledged true true   Unacknowledged alarm present

Issue Cannot find part number for 7797 or 7793 Environment I/NET iPortal Cause The 7790, 7793 and 7797 all use the same hardware.  The are configured to be the specific controller type using the Hand Held Consol. Resolution Log into iPortal Go to product Search Select to search for a Part Number Enter %7790% into the search field. The part number for the board is 7790A

Issue Procedure for Splitting Existing Links to DLA architecture Environment I/NET Xenta 527 NPR Cause As cable degrade over time it is more economical to split a controller LAN into multiple DLA sites that to re-run the wire. This is especially true when dealing with broken underground wire. Resolution This is a basic order of operations for how to split a single link.  Please select Start > All Programs > I/NET > Manual-Technical Reference Guide and review section 1-11 before proceeding.  Determine a logical location for the split in the controller LAN Install the Xenta 527 or NPR and ensure that Ethernet communication if available. (DO NOT plug in the Ethernet cable yet) Back up the I/NET database Reconfigure the existing router to be a DLA device.  DO NOT use site 0 Configure the new Router to be a DLA device using a different site address than the first router.  You can use the same station address if needed. Plug in the Ethernet cable At the I/NET workstation verify that each of the devices is online. You may need to restart the I/O server and verify Reference Hosts.  At the Workstation you should now have to connect to the Link, then to the controller. In I/NET configuration, click on Host Masks.  Modify the host mask settings for the existing router and note the settings.  Copy theses settings to the new DLA device(s). Back up the I/NET database Physically break the Controller LAN and connect one leg to the new Router. You may need to remove or disconnect any segment of wire that now leads to no where. At the I/NET workstation you should now be able to connect to each site and see controllers populated under it. If you cannot, a common reason is that you have 2 routers connected to the same controller LAN section and no router connected to the other section. Select Edit>Host Computer>Network Configuration Notice that the Split Link has been renamed to DLA Link #.  You can change this name in newer revisions of I/NET Select the link you have split and click Penetrate. You will see the sites displayed with " * " next to each. Each site will take the Host Name you gave it during configuration. Click Save All Penetrate into the highest numbered site. Click Save all and close.  Then work your through each site from highest to lowest number saving all of the controllers under it. Open a graphics page and test points that are under each of the sites. In an access system. You can test by adding or removing an individual from a door under each site. Backup the I/NET Database. NOTES: You can not have duplicate station addresses under the same link even if they are on different sites. The controllers are addressed LLSS (Link##Station##) no duplicate LLSS address can exist within an I/NET system. The exception to the above is that all Xenta 527 can use the same station address as that address is not visible from the Host workstation. Each 527 must have a unique link and site address.

Issue Filemaster is Full SQL 2005 and Equalized Client is SQL Express fails to equalize.  Environment Full SQL 2005 for the Filemaster SQL Express for the Equalized Client 2.31 version of TAC I/NET Seven 2.4x version of TAC I/NET Seven Cause  SQL Express doesn't start equalization services automatically. Resolution The Equalized Client refused to replicate the database with the Filemaster. Equalization is not succeeding even though the little icon may say it is equalized. Filemaster shows pending. Start I/NET and check the host passwords to see if equalization has taken place. The following steps will cause equalization to take place:  Restart the pc to ensure there isn't a program hanging in the memory. Demote Equalized Client to Stand Alone. Exit I/NET and I/O Server Go to Start/Run/CMD Maneuver to the C:\Program Files\Inet Seven folder and type the following:  ineteqzmerge /unregserver     press the Enter key ineteqzmerge /service     press the Enter key Now go to Services by selecting My Computer/Manage/Services and look for the Service running called InetEQZMerge and start the service and select Automatic. Now you should promote the I/NET workstation to Equalized Client ensuring you put the Filemaster Name rather than IP address. The snapshot will be delivered to the Equalized Client. After equalization you may need to shut down I/Net and the I/O Server one last time and then restart I/NET Seven. Now return to Services by selecting My Computer/Manage/Services and look for the Service running called InetEQZMerge where you should STOP then START the service again.  One way to test equalization from Filemaster to Equalized Client: in I/NET Seven under Edit/Host Computer/Passwords add a user/password. Check the other computer to see if the database replicated the new user/password and Vice Versa. If ineteqzmerge is already running as a service.  Try stopping and starting the service.