Issue Get a hard copy of all points in a controllers / system Get a hard copy of I/NET controllers' databases (SAV files) Environment I/NET Seven Cause Require a hard copy to view all points and database and / or extensions Resolution There is a feature under Network Functions which allows you to print (screen or default printer) any or all controllers save in your Network Configuration. This lets you get a printout of exactly what points and point extensions you have added to the controllers on your system. Select Edit >Host Computer >Network Functions from the main menu. The system displays the screen shown Choose the link of the controller(s) you wish to print from the drop-down list. The system now displays the controllers on the link you selected. Above the list are six push-buttons. Select the Print push-button. Choose the controllers you wish to mark for printing by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for printing will show a “Y” in the Print column of the list. Each click on a controller in the list will toggle the Print function between “–” and “Y”.  Select the Setup push-button at the bottom of the window. The window shown below appears. If you want the database report to print to the screen activate the Print to screen checkbox. Select the database items that you want to print by clicking on the Select checkbox. To select multiple links follow Steps 2 through 6 for each link and controller, selecting Close from the Database Print window to return to Network Functions, until you have selected each controller. Note: The TAC I/NET Seven system lets you select more than one link at a time but this results in a very lengthy printing session. If you do not want to tie up the printer for an extended period of time select only one link at a time. If N/A appears in the print column this means that the station exists for this controller, but no save file exists in the save file directory.   When you have selected the appropriate parameters, select Print to start the printing. When you have selected the appropriate parameters, select Close to return to the Network Functions window. Since database prints may be very long, make sure no manual control commands from the PC are needed during the time required for printing.   Select Close to return to the Network Functions window. This information is also available in TCON299 I/NET Seven Operators Guide - Chapter 2 Setup and Network Configuration

Issue DDC Control Override MR Control Override Environment I/NET MR-AHU 7718 7716 7756 7798 7793 Cause A control is needed to override the standard control for a point. Possibilities include using an ASC point for a different purpose. Resolution The most effective means to program an over-ride all logic is to use an Event Sequence containing the with Lock element. This will over-ride anything other than a point in manual control. Please see Appendix A "DCU Control Hierarchy" from TCON300 for complete Control Hierarchy.

Issue A 7791 is used specifically for what? Product Line TAC INET Environment I/NET Site Cause A 7791 is used on security/access control installations. Resolution It is the interface for Door Processing Units (DPUs). (TCON209, 1-20) TCON Number and Title Cross Reference (with links) is TCON information. Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication is a chart to explain further.

Issue Can a 7716 emulate a 78061 Tap? Product Line TAC INET Environment I/NET site Cause This emulated Tap requires the use of an optional RS232 expansion module. Using this Tap function, you can connect a Hayes compatible modem to port P2 of the RS232 expansion module. You may then configure the modem for auto-dial/auto-answer (AD/AA) operation. Resolution A 7716 can emulate a 78061 Tap. Using the Hand Held Console (HHC): Press [Code], 90, [Enter] The emulated device type model number displays in the read out Press [Inc] or [Dec] to toggle through 7801, 7803, or 7806 Tap emulation Press [enter] to accept your choice You will need the RS-232 expansion card for ADAA See TCON 096 for details.

Issue Does I/NET 2000 launch "EqualCli" automatically? Environment I/NET 2000 Cause File equalization is required if you have more than one host workstation which will need access to any of the above files. One host workstation is designated as the filemaster. This designation is performed in the Configure program and is maintained in the configuration profile. When you select the Set as filemaster option, Configure automatically completes the filemaster name field with the Computer name (found in the Identification tab under Windows Network settings). The filemaster name field is read-only on the filemaster station and cannot be changed. Resolution Yes, EqualCli will launch automatically. For more information see TCON 209, The Filemaster, 1-13. When the workstation is designated as the filemaster, I/NET stores a master copy of each equalized file in the \MSTR directory. It is important that the designated workstation be constantly powered and that the EqualSrv program be running. EqualSrv will dock an icon in the system tray to indicate it is active. Both EqualSrv and EqualCli are launched automatically by I/NET on the filemaster workstation and stay running as background tasks, even when I/NET is shut down. If necessary, you can manually shut down EqualSrv from the system tray icon menu. Warning: If the filemaster workstation is powered off, or if EqualSrv is not available, file equalization cannot occur. Furthermore, other host workstations will not be able to modify any of the equalized files. It is recommended that the filemaster workstation be powered by a uninterruptable power supply (UPS). All other host workstations must enter the Computer name of the filemaster workstation in the Filemaster name field. I/NET launches the EqualCli program on the host workstations automatically. Before any host workstation can access an equalized file, the EqualCli program contacts the EqualSrv program running on the filemaster station to ensure that any modifications can be passed to the filemaster copy. If, for some reason, EqualCli cannot make contact with EqualSrv, the operator will receive an error message and will not be able to access the equalized file. This ensures that no updates to the file are lost. If EqualCli makes contact with EqualSrv, the operator is permitted to access and modify the equalized file. EqualCli passes the updates to EqualSrv, who then updates the filemaster copy. If the update is successful, EqualSrv will make the file available to all the host workstations. There are three events which trigger the file equalization procedure. When I/NET is launched on any host workstation. When an operator attempts to access an equalized file. When any operator successfully updates an equalized file.

Issue How long will I/NET 2000 be sold? Is I/NET 2000 still supported? Environment All Revisions of I/NET 2000 Cause The last release of I/NET 2000 was Revision 2.34 which was released in April 2003. Microsoft has announced that it will terminate all Windows® 98 support in 2006. Resolution As of January 1, 2006, support for I/NET 2000 is no longer available. Please review the following Customer Advisory available on The Exchange Download Center which details support information for I/NET 2000. All I/NET 2000 customers should upgrade to the latest revision of I/NET.

Issue Two different revisions of I/NET 2.31 were created: 2218 and 2227. How do you know which one to use? Environment I/NET 2.31 Cause Inet 2.31 was released with two different builds 2218 and 2227. Resolution The latest build for I/NET 2.31 is the 2227 build. If a site is running the 2218 build, it is recommended to upgrade to the later build since many functions have been greatly improved. Log in to The Exchange Download Center to download I/NET v2.31.

Issue How to tell if the Filemaster or Client is equalized Product Line TAC INET Environment I/NET Seven Cause Equalization Questions Resolution Take a look at the INET Seven Icon at the bottom right portion of the client’s screen.   For full details see TCON 298 - Getting Started page 3-2

Issue How do I set up Seven Trends? Environment I/NET site Cause How to setup Seven Trends Resolution I recommend you read about this in TCON 299 (INET Seven System Operator Guide). The overall sequence for using the SevenTrends features of I/NET Seven is as follows: Configure DCUs to collect data. Define trends in host stations to receive data. Configure host stations to receive collected data. Set transfer parameters. Archive SevenTrends data. Create SevenTrends reports (may be done any time after Step 3 is complete).  Refer to the SevenReports help file for more information on creating reports.

Issue How to remove the "Y" selected in the Alarm Inhibit Editor Environment I/NET site Cause How to remove the "Y" selected in the Alarm Inhibit Editor Resolution This node may not be saved in the workstation’s Network Configuration Editor. First save this device in network configuration, then attempt to modify the settings in the Alarm Inhibit Editor. Refer to TCON 237 Alarm Inhibit (AI)

Issue Want to be able to import a list of individuals quickly without having to retype all the details from a spreadsheet or text file again into I/NET Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft Access 2003 Microsoft Access 2007 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. Cause Customers usually have a spreadsheet or database of employees and / or users which they want to quickly import into their I/NET Seven Access control database.  The process below describes how to do this along with its limitations. Resolution Process to import Individuals via the IDWorksView table using Microsoft Access 2003 / 2007 The import process will NOT update any existing data; it will only add new entries and leave existing entries as they were.  So this is typically a process used for a new installation.  If you are attempting to import into an existing Access control database with individuals then it is strongly recommended to backup your I/NET SQL database. It is also strongly recommended you test this in an ‘offline’ state, that is, it is not connected to any physical controllers until you are comfortable that the process provides the desired results. The same limitations that apply with ID Works (Refer to TCON 301 Chapter 5) apply to this import process. TAC I/NET Seven (not just I/O Server) must be running on the server specified in TAC I/NET Seven’s ODBC data source in order for records created or modified from ID Works to be downloaded to affected DPUs. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record. You cannot disable an individual’s card without disabling the individual. You cannot create a new group or a new tenant.  All Tenant and Group information must already exist in I/NET You cannot make an individual’s record be DPU resident. You cannot assign a decimal card number to an individual. You cannot set an individual’s APB scheme (that is, hard, soft, or graced anti-pass back). You cannot assign a PIN to an individual. The steps to import are as follows: Download ZIP file containing necessary files here. If you are using Microsoft Access 2007 use the following files Format customer data into the Excel template (dbo_IdWorksView.xlt in the ZIP file) or provide this to the customer to complete the Employee details.  Pay attention to required data shown in the comments for each title cell. Open db1.mdb file in the ZIP file using Microsoft Access 2003 /  idworks.accdb if using Microsoft Access 2007. Double click (open) the table dbo_IdWorksView to establish the connection to I/NET on the respective machine.  You may be prompted for login details – you must use the ‘sa’ login and password installed on the PC. If successful you should see any individuals that already exist in the database (unless blank).  Close the table. If you are using Microsoft Access 2007 Click Here to view the changes for steps 6 though to 8. Right–click in any of the white space and select Import (or go to File>Get External Data>Import) Browse to the location of the Excel Spreadsheet, saved in step 2, containing the data to be imported.  Be sure to change the File Type to *.xls otherwise you will not find the file.  Select the file. Import wizard should appear, now select the following options within the import wizard: Select the Check box “First row contains column headings..” Select Next Select “In an Existing Table” and select the table from the drop down list – there should only be one there. dbo_IdWorksView. Select Next. Select Finish. Be patient – the process can take a few minutes based on the number of entries that you are trying to import.  Once imported you should receive a message indicating that the import was completed.  Select OK. If you have images referenced in your import file, be sure that the Images are in place before modifying ANY individual in I/NET.  Otherwise the image path will be deleted.  The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality. There is also a way to realize this function using Microsoft SQL Server Management Studio Express instead of Microsoft Access. See How to Import a Large Number of Individuals from Excel to I/NET SQL Database at One Time for more information. 

Issue Can I direct connect a workstation or laptop to an NPR? Environment I/NET site Cause Can I direct connect a workstation or laptop to an NPR? Resolution Yes, a workstation can be directly connected to an NPR. Refer to TCON209 for more information.

Issue Can a Remote Client run I/NET Reports (SevenReports) from the I/NET Seven Server's SQL database? Product Line TAC INET Environment I/NET Seven SevenReports Cause In a Remote Client configuration, the local SQL database is not used and is typically blank.  To enable the local SevenReports engine to connect to the I/NET Server the ODBC data source must be configured to successfully connect to this server workstation.  Resolution To download more detail instructions please Click Here Remote Client: The following procedures describe how to configure the local I/NET Seven ODBC data source to communicate with the SQL server on another I/NET Seven workstation. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab, highlight the Seven ODBC data source, and click Configure.... In the DSN Configuration editor, use the Server field to specify the name of the I/NET Seven workstation and SQL Server instance that will be used as the server for this workstation. Click Next and enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be passinetdb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Click OK to close the ODBC Data Source Administrator editor. Third-Party Applications Use the following procedures to create a new ODBC data source on a PC that is not running I/NET Seven. The purpose of this task is to allow local third-party applications to communicate with I/NET Seven running on another PC. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab and click Add.... In the resulting window, scroll through the list and highlight the driver appropriate for the version of SQL Server installed on your PC:  - For MSDE/SQL Server 2000, select SQL Server. - For SQL Server 2005, select SQL Native Client. - For SQL Server 2008, select SQL Native Client 10. Click the Finish button. In the DSN Configuration editor, make the following settings:  - Define the data source Name as “Seven ODBC”.  - Define the Description as “ODBC Connection for I/NET Seven”.  - Use the Server field to specify the name of the I/NET Seven workstation that will be used as the SQL server for applications on this PC. Click Next and make the following settings:  - Select the With SQL Server authentication using a login ID and password entered by the user option. - Near the bottom of the editor, enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be PassInetDb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Verify that the new ODBC data source has been added to the list of System Data Sources. Click OK to close the ODBC Data Source Administrator editor. More detailed information is also available on Extranet in TCON301 Chapter 2 - ODBC Driver Interface section.

Issue How do I change the power line frequency setting on the 7716 / 7718 / 7756? Environment I/NET  Hand Held Console (HHC) 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. Cause How do I change the power line frequency setting on the 7716, 7718, 7756? Resolution Physically remove the I/O points from the controller. See TCON 096 for details. Using the HHC, press [Code] , 92, [Enter] to select the AC line frequency Press [Inc] or [Dec] to switch between 50 an 60 hertz Press [Enter] to accept your choice After downloading the software and database, place the external points on the 7716 (or 7718 and 7756) Place the controller on the LAN Note:  Code 92 is not required for any of the 779x Interface's. Entering this code on the Hand Held Console will produce the error LED to illuminate. 

Issue Remove the Routing tables from I/NET and Xenta 527 devices Host conflict or station conflict error messages displayed at the I/NET Host. Incorrect Links, Hosts and IP addresses that do not exist in your Network are shown when penetrating Network Configuration. Product Line Other, TAC INET, TAC Vista Environment I/NET IP Routers Xenta 527 Cause Host or station conflict errors can be caused by old information stored in a routing table. From time to time, it may be necessary to purge that information and allow the tables to be rebuilt automatically. The only way that routing tables can become corrupted is if a laptop was used to connect to the system from a different Network or from the Outside. Once connected, its IP table is broadcasted to the other devices like PCs and NPRs, thus populating the table with entries that does not belong or is non-existent for this location or system.  Resolution Managing I/NET Routing Tables   I/NET Host Workstation View the I/NET Routing Table See Viewing the routing tables on a PC using I/NET Seven for complete instructions. Delete a Single entry in the I/NET Routing Table Go to Start > Run Type Telnet and hit Enter Type open, hit the space bar, then enter the IP address of the PC Press Enter When the login comes up, type csi, hit enter Type LA  and hit enter to list all routing table entries Type ipdel xxx.xxx.xxx.xxx with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table Shutdown the I/O Server Open Windows Explorer Browse to C:\INET Seven Data (or C:\Program Files\INET Seven) Delete the .dat files (you may want to save a backup to another location) Delete the routing table from any device listed as a Reference Host or the table will repopulate Start I/NET Other Method: See Bogus Links, Hosts and IP's in Netcon for instructions on using the delall command in Telnet     Xenta 527-NPR; Xenta 913; Xenta 527 Web Server (See Clear the IP routing tables of a Xenta 913)  Viewing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ip” Press enter Deleting a Single entry in the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ipdel” then the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet delall” Press enter Type “inethost” and press enter Verify or set the Reference Hosts Clear the routing table from any referenced device to ensure old data is not repopulated Restart the Controller to re-populate the routing table   You can also realize this through the web page of Xenta device. Open the web page of Xenta controller, browse to Utilities-I/NET-I/NET Command Line, and type the command below or above. The result is the same as using HyperTerminal, which is also an easier way. Typing “inet help” or “inet” gives every I/NET option within the controller inet - I/NET Help ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all lists ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records   NPR-2000 Viewing the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Deleting a Single entry in the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “ipdel xxx.xxx.xxx.xxx” with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table (See Bogus Links, Hosts and IP's in Netcon)  Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the PC Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “delall” and hit enter to clear the table   Appendix A: I/NET Telnet Commands Glossary: Help – Displays all available commands in the NPR or I/O Server.  Note there are some differences between the NPR and I/O Server. ipadd a.b.c.d – Adds the IP to the routing tables. ipdel a.b.c.d – Deletes the IP from the routing tables. gpadd LLSSPPBBTT XX | a.b.c.d – Adds a global point link or global point IP to the routing tables. delall – Deletes “all” local routing table entries. setpass password – Change the telnet login password (6 characters max). +cpdel LLLL SS – Deletes the specified link/site address from the CP table. +debug gp on|off – Turns global point debugging on or off. +reboot – Reboots the NPR. +wdog – Reports watchdog errors. +wdogrst – Clears the watchdog errors. +Dx – Toggle debug output to COM3.  x=0/1; 0 = off, 1=on.   List Commands: +LR – IP Stack routing table. LI – IP routing table. LM – IP routing masks. LL – Link/Station routing table. LG – Global point routing table. +LC – Compressed routing table. +LS # - Compressed routing table: station to site maps for the specified link #. LA – All routing tables. LU – System metrics. *LD – Dial maps.  + = NPR only * = Host PC only   Appendix B: Method for Clearing Routing Tables at a Large Site See Possible solution to doing a Telnet session with a system wide firewall setup.   Appendix C: Suggested Reference Host Settings   Click here to be linked to the TAC INET Seven Getting Started. Click here to be linked to the TAC INET Seven Operator Guide.   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 How many workstations and NPRs can be placed on one Ethernet LAN? Environment I/NET site Cause How many workstations and NPRs can be placed on one Ethernet LAN? Resolution 63 workstations and 99 NPRs. (TCON 209 1-4)

Issue How many subLAN controllers can a 7798 support? Environment I/NET site Cause How many subLAN controllers can a 7798 support? Resolution A 7798 can support up to 32 MRs, ASC, DPUs, or any combination on a subLAN. (TCON 209,1-23) Please note that if you are using bin file 1.09, the number of controllers is limited to 27.

Issue How many Universal Inputs are on the base card of the 7716? Environment I/NET Site Cause How many Universal Inputs are on the base card of the 7716? Resolution There are 8 Universal Inputs (UIs) on the 7716's motherboard. See TCON 096.

Issue How many Link Taps are supported on a Host LAN? Environment I/NET Site Cause How many Link Taps are supported on a Host LAN? Resolution Sixteen. (TCON 209, 1-5)

Issue How many Host Taps are supported on the Host LAN? Environment I/NET site Cause How many Host Taps are supported on the Host LAN? Resolution A host LAN supports up to 8 Host Taps and 16 Link Taps. Each Host Tap can connect directly to a workstation or indirectly to a workstation through a modem. Use the host LAN to connect multiple host workstations over a large area, segregating functions at each station. Devices on the host LAN communicate with each other at 19.2 Kbaud or 9600 baud. The host LAN reconfigures automatically as devices are added or removed. (TCON209, 1-5).