Issue How do I setup the Custom Pin Numbers In I/NET Seven Product Line TAC INET Environment I/NET Seven site Cause How to setup Custom Pin Numbers in I/NET Seven. Resolution Please use the following link: Custom Pin Numbers.doc

Issue I/NET Seven Upgrade Check List Product Line TAC INET Environment I/NET site in need of upgrade Cause Check List for I/NET Seven Upgrade Resolution Please see link: I/NET Seven Upgrade Check List.doc

Issue Reset Instructions for 1200 Series SCU Product Line TAC INET Environment SCU 1200 series controllers I/NET Cause Need to restart SCU, perhaps after a reload of firmware or dip switch settings Resolution Follow the written instruction carefully.   Reset Instructions: Locate the 3-pin connector labeled P610 and the reset push button switch. Refer to the above diagram. Momentarily short P610 pins 1 and 2 while simultaneously pressing the reset push button switch. (Note: P610 pins 1 and 2 are the pins located nearest the dip switch.) Re-download the proper BIN file to the SCU.

Issue I/NET Seven Rev 2.10 and IP Filtering Product Line TAC INET Environment I/NET site Cause IP Filtering on an I/NET Seven site with Rev 2.10 Resolution I/NET displays this summary when you select IP Filters from the I/NET Configuration Profiles editor. This summary lists each I/NET host that is currently communicating with this host workstation. Using IP filtering, you can configure each I/NET host to only see specific sections of the overall network. This allows you to create segmented networks that can be secured from outside access. I/NET displays this dialog when you highlight a device in the Device Filter Summary and select Modify. This dialog lists all filters currently defined for the selected device. IP filters are listed in order of their priority. The first IP filter in the list has the highest priority. The last IP filter in the list has the lowest priority. By default, a device will have a single IP Filter entry that allows the device to communicate without restriction.

Issue System Security and I/NET Seven with Window XP Product Line TAC INET Environment Windows XP SP3 Cause A list of editors available in I/Net Seven under various Windows Rights  Resolution There are two components of security available to users of I/NET Seven, I/NET Seven passwords and Windows User accounts. Please see the following document: System Security and I/NET SevenR.doc

Issue I/NET Seven custom installation/upgrade tips Product Line TAC INET Environment I/NET Site Cause Desire to install/upgrade I/NET Seven Resolution Please see following document: Installation Precautions.doc

Issue I/NET Seven and Key Card translation What is the Key / Card Translation table and how do I use it? Can I use the Key / Card Translation table for other card types other than I/DISC? Product Line TAC INET Environment I/NET all revisions Cause Need to understand what is the Key / Card Translation table and how do I use it. Resolution As I/NET evolved it first used what might be called a sequential look up table to translate I/DISC keys from number much to big for the DPU / SCU to interpret to one of the 1 to 24,000 (32,000 current) individual numbers permitted in a Tenant. The I/DISCs are shipped in lots from the manufacturer and the container states the starting key number, e.g. 897541, and the number of keys in the container. I/NET has an editor called Key / Card Translation that allows associating those I/DISCs with an individual. The box labeled Source is used to enter the first key/card in a lot of keys (usually read off the container). The Target box is used to assign the key to an individual in a Tenant. The Count box is used to set how many sequential keys will be associated with individuals. There are four card types that can be read directly without a translation table, Wiegand 26 and 32 bit and ABA 115 and 85. On the Wiegand cards the Tenant Code must match the site or tenant code on the cards and the card number must be less than 24,000. For all four types of card Switch 7 on the DPU is set to off. Wiegand 66 bit, Custom Wiegand and Custom ABA must be selected to use a translation table, and Switch 7 on the DPU is ignored. The next evolution involved allowing the “big (large) card number” to be stored with the Individual. This removes the requirement of using the key / card translation editor. Please see the following document for additional details and examples: Card Numbers.doc

Issue Have an I/NET System that has existing I/DISC that are listed in a Key / Card Translation table. The last bag of I/DISCs I received were un-sorted. How do I add these new I/DISC in the I/NET system? Want to enter the Individuals with new I/DISCs as large numbers Product Line TAC INET Environment I/NET all revisions Cause The manufacturer of the I/DISC is no longer supplying the I/DISC sorted.  As such the range of the I/DISC can be outside the limit of 32,000 users per tenant as limited in I/NET. Resolution This is the process of adding NEW people in the system that has existing Key / Card Translation table and you want to enter the NEW Disk as large numbers. Please see the following document: Add Idisc.doc

Issue While Running I/NET Seven Rev 1.17 and above a new SCU is added to replace an existing DPU. "Software Restore" was run by mistake, and the SCU no longer works. Product Line TAC INET Environment I/NET site Cause "Software Restore" was run by mistake Resolution Please use the following document link: How to load SCU1284 BINS.doc

Issue How do I import the "Version 5.1 Sample.IWX" from the I/NET Seven CD into ID Works 5.1 Software? Product Line TAC INET Environment I/NET site with IDWorks Cause How to import the "Version 5.1 Sample.IWX" from the I/NET Seven CD into ID Works 5.1 Software Resolution Please use the following document link: Import_ Project_IDW5p1.doc

Issue I have an I/NET 2000 system with ID Works Version 2.xx. How do I convert this ID Works Version 2.xx Project to run on I/NET Seven? Product Line TAC INET Environment I/NET 2000 site Cause I/NET 2000 system has been upgraded to I/NET Seven. Resolution Please see attached Document Link: Conversion of I/NET 2000.doc

Issue 7798C does communicate with a PC with either cable -- CBL082 or CBL072 Product Line TAC INET Environment I/NET Controllers including the 7798C Cause Improper Grounding Resolution There must be an earth ground connected to pin #3 of the 24 VAC power connector in order for communications to work correctly. Click on these pictures for a larger example:     Note: Never use the shield as the ground. Grounding is accomplished by connecting a 14–18 AWG (2.081–0.897 mm2) wire from terminal 3 to true ground.

Issue Network Paging System or Network Wide SMS Messaging for I/NET Product Line TAC INET Environment I/NET Site Cause Requirement for Network Paging System or Network Wide SMS Messaging Resolution PageGate allows for network paging or network wide SMS messaging from any combination of the following modules: web, email, commandline/ascii, serial, TAP-in and (GUI) windows workstations. SMS or text messages can be sent to alphanumeric pagers, numeric pagers, cell phones, PIMs, billboards or pcmcia pager cards. For capturing and paging I/NET Seven alarms and messages we use the “Get Serial” module from PageGate. Please see the following link for Technical configuration and contact information: PageGate.doc To download the trial software please use the following website: https://www.notepage.net/ Expectations of Service Schneider Electric does not offer formal support for the third party software or hardware found here. Instead, our role is to provide a platform to provide information for people who want to take advantage of the global community of Schneider Electric customers. Schneider Electric will make every effort to monitor content to ensure the accuracy of the information you'll find, but any information provided by Schneider Electric staff is offered "as is" with no warranties, and no rights are conferred. You assume all risk for your use of third party software and hardware.

Issue ID Works 5.1 badge printing error and I/NET Seven rev 1.16B. Product Line TAC INET Environment ID Works 5.1 I/NET Seven rev 1.16B Cause Attempt to save or print a badge in ID Works 5.1, the following error occurs:   Data Source Error A cursor with the name 'SQL_CUR06B8F1D0' already exists. State:37000,Native:16915,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] Resolution In order to correct this issue, contact Schneider Electric Product Support and ask for the “I/NET Seven 1.16B/IDW 5.1” patch. We will e-mail this patch to you. A better solution is to upgrade to I/NET Seven Rev. 1.17, which includes the patch in the software.

Issue How to configure Automatic DPU restore host functions? What is Automatic DPU Restore Host? Product Line TAC INET Environment I/NET Seven up to 1.15 to 2.10 Cause On larger I/NET Seven applications configured for File Equalization on building network backbones, it was found that temporary visitor badges and schedules were downloaded by multiple Hosts to multiple door controllers increasing network communications simultaneously caused this. By selecting a Primary Download Host (or a Secondary Download Host), I/NET can manage and assign responsibility for downloads concerning this information. Resolution Combining DPU Online Message Restores, DPU Memory Failure Restores and Temporary badges in the DPU Restore Host functionality, I/NET Seven more efficiently manages network traffic.. Please use the following white paper for configuration setup: Setting up Restore Host.doc For more detail please see customer advisor CA-2004-05.

Issue Reader wiring pin out for replacing a 7910 with a 7920 reusing the CAT 5 cable for the reader. Product Line TAC INET Environment I/NET Seven site with DPU Cause Need to know pin out for DPU Resolution Please use the following link to view PIN out: 7910 Reader to 7920 Reader Pin Out.doc

Issue Processor % Loading and LAN % Loading; What do these mean and how can they impact my system. Processor % Loading -  This field displays the Controller processor (CPU) percent loading (0–100%). This number is an indication of how busy the controller is.  LAN % Loading - This shows the percentage of controller LAN communication attributable to this controller only. It is not the total control LAN loading figure. Product Line TAC INET Environment ALL I/NET Controllers (Controller LAN (CLAN) based) Cause A greater understanding of the values seen at each controller can greatly assist in having a more efficient I/NET network. Resolution The controller Processor % loading and LAN % loading are available from each controllers' configuration/status editor. You must be connected to the controller in order to use this editor. This information can also be obtained using the hand-held console, Code 3 (CPU %), and Code 4 (LAN %). These fields are display only. You cannot make changes. However, you can make changes to the database and observe the relative loading statistics after. The readings should be taken with all graphic pages and DCU controller point summaries closed. Processor % Loading This field displays the Controller processor (CPU) percent loading (0–100%).  This number is an indication of how busy the controller is.  If this number is 100, control actions may be lost or delayed. You should not let this reading go above 80%.  If kept to below 80% then if the processor peaks for some reason, it has 20% to peak in without locking up for a number of processor machine states. The conditions that affect the processor loading are as follows: Resident Point scan interval.  All resident points are processed by the firmware.  If you find that the processor loading is high, then edit all the AOs and DOs that do not have a calculation extension and adjusting the scan intervals to 255 seconds.  In heavily populated controllers this will bring down the processor % loading somewhat. Calculated Point frequency.  All resident points with a calculation extension will have their calculation processed at the scan interval of the target point.  If you find that the processor loading is high, then, on the calculation extensions that perform less important tasks, you may edit the target point’s scan intervals to a larger figure. Event Initiated Sequences.  A number of sequences that are in a loop, that is to say, running sequences with a skip back to themselves causing the sequence to run continuously, will cause the processor % loading to rise.  Edit and modify to create a more efficient database.  Ensure that a minimum of 1-second delay is implemented between each action within a sequence.  Do not leave all actions at the default value of zero.   DDC Module Sample Interval.  All DDC modules are processed at their respective sample interval.  If you find that the processor loading is high, then, on the DDC modules that perform less important tasks, you may edit the DDC module’s sample rates to a larger figure. Global or Indirect Traffic.  Naturally, large quantities of global and or indirect traffic to and from the controller will cause the processor % loading to rise.  See the next section “LAN % Loading” for more details. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the processor % loading to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the processor % loading to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the processor % loading to rise.  You will have to identify the origin and alter the “Cell Sample Counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  LAN % Loading This shows the percentage of controller LAN communication attributable to this controller only.  It is not the total control LAN loading figure.  Treat the control LAN as a 100% resource.  If this controller has a LAN percent loading of 23%, then the control LAN has only 77% of resources left to service the other controllers on the control LAN. Another way to look at it is, in the above example, out of every 100 token passes on the control LAN this controller has used the token 23 times. The best scenario is to have the lowest figure possible, e.g. 0%.  Just imagine a control LAN with 25 controllers connected, each controller with a ‘LAN % loading’ of 5 %.  The LAN is flooded and will cause messages to be lost and or buffered, graphic pages will not update as expected and the system will dramatically slow down. The empirical rule is as follows: The ‘LAN % loading’ is allowed to rise to a figure above 0%, but within 20 seconds, it must go back to 0%. The conditions that affect the ‘LAN % loading’ are as follows: LAN Reconfigures.  Every time a LAN reconfigures all global points in every controller on that control LAN transmit their values on to the LAN, and all indirect points request, at their scan interval, an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Global Point Traffic.  Large quantities of global point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of global traffic are: Global point’s “Broadcast Change Counts”.  Remember that multiplying the analog point’s conversion coefficient’s ‘m’ value with the broadcast change count value will be the resolution of the analog value to be exceeded to cause a broadcast onto the LAN. Just imagine a globalized analog point with a ‘m’ value of .05 and a Broadcast Change Counts set at 1.  Then this sensor will globalize its value every time the value exceeds 0.05 creating globalized traffic. The faulty sensor being globalized.  The sensor’s value being unstable to the extent that the point’s value changes exceed the “Broadcast Change Counts”, in extreme cases creating globalized traffic. Controller’s Power Line Frequency, HHC function [Ctrl 92], not set correctly.  This is for setting a notch filter to filter out power supply noise being imposed over the sensor’s input signal thereby helping to eliminate the sensor’s value appearing to fluctuate.  These fluctuations could send a global sensor’s value change to exceed the “Broadcast Change Counts” in extreme cases creating globalized traffic. Pulsed Input (PI) points.  The PI points “Scans between Broadcast” incorrectly assigned. Beware: a PI point with a “Scan Interval” of 1 second and a “Scans between Broadcast” set at 1 second will cause the controllers ‘LAN % loading’ to rise by 10% and stay there, even though the PI point’s value may not have changed. Indirect Point Traffic.  Large quantities of indirect point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of indirect point traffic are: LAN Reconfigures.  Every time a LAN reconfigures all indirect points, at their scan interval, request an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Indirect Point scan intervals set incorrectly.  If an indirect point does not see a change in its state/value from the global point after 2 scan intervals then the indirect point will request an update from its associated global point to be reported at the indirect point’s 3 rd scan.  With global points that are reasonably static, i.e. not altering a lot e.g. status points, etc., the associated indirect points will carry out their requests for updates.  Therefore the indirect points scan intervals should be staggered system-wide, not just controller-wide.  If all the indirect points have the same scan interval they could conceivably request at the same time and queue and hang onto the control LAN’s token. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the ‘LAN % loading’ to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the origin and alter the “Cell sample counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  

Issue Understanding DbCreate Utility Product Line TAC INET Environment DbCreate Cause Various Database errors Resolution The DbCreate utility provides you with the basic tools you'll need to create and remove an I/NET SQL database. After creating an empty database, you can use DbCreate to import data from a previously installed I/NET 2000 version 2.x system in order to upgrade to I/NET Seven. Note: In most cases, you will probably use DbCreate's graphical user interface (GUI) in order to interactively perform tasks. However, you also have the option of performing DbCreate tasks silently from a command line. For information about using the command line, refer to Using DbCreate from the Command Line. Ref; Online Help "Using DbCreate". Use DbCreate to perform any of the following tasks: Create an empty database To create a new SQL database.doc Import I/NET 2.x data Importing I/NET 2000.doc Import a Docutrend archive Importing a Docutrend Archive.doc Verify the existing SQL database Verifying the Existing SQL Database.doc Remove an existing I/NET SQL database Removing an Existing I/NET Db.doc Backup an SQL database Backup an SQL Database.doc Restore an SQL database Restore an SQL Database.doc Upgrading the database Upgrading the database.doc Recording a Log File When you activate () the Record logfile, DbCreate will record a log file. The path and filename may be specified. If no path is specified, the file is created in the current directory. Also, if the path specified is invalid, the current directory is used. There are two levels of logging: normal and verbose. By default only significant events are logged. When the –V (verbose) flag is set, other informational events are also logged. Monitoring Progress Once an operation has started, its progress can be monitored in the lower half of the DbCreate dialog. Side-by-side progress bars show the overall progress of the operation (left progress bar) and of the individual task being performed (right progress bar). A scrollable text area keeps a list of actions that are being performed. The text includes the result of each action performed. If you have chosen to import I/NET 2000 2.x data, the Start button changes to Abort, and all other controls are disabled. Pressing Abort will attempt to stop the operation in progress. In this case, the database will contain only partial data from the I/NET 2000 system that was being imported.

Issue AMT Windows locking up the PC Too many active windows opening in AMT causing the PC to hang AMT stops working Product Line TAC INET Environment I/NET Seven 2.30 and below. Cause In AMT each Critical, Priority, Routine, Messages or Transactions button opens a new window on each press.  On the surface it appears to switch between these windows.  Along with this all open windows and positions are retained for each user login, hence this will cause different results for different users. A problem eventually occurs when there are too many active windows open in AMT. Resolution In most cases the problem is due to a user having opened too many AMT windows but you could also verify the following:  Verify that you have only the default windows opened. Not more than one of the same window opened (usual symptom). If filtering is done, allow the filter opened to fill the screen. Check the rights for the Logged on user if they have window controls in Host Passwords. If you have multiple users, and are able to log in without AMT hanging then, recreate the other user account and delete the first one. If the problem is still occurring, please use the attached SQL script. The script resets the window positions of ALL windows to default for ALL of the operators in the I/NET database. This will fix the issue. Close I/NET completely Copy this file to your desktop: AMT Reset.ZIP Unzip and run the file It will ask for a logon, this is your sa user name and password Once run, this will have reset the AMT screen and the system should run again.

Issue A Seven Report will not print; however, most of the other reports print just fine. What is wrong with this single report? Product Line TAC INET Environment I/NET Seven Site Cause Share options on the defined default printer are preventing the reports from being printed. Resolution Steps to change the Printer properties On an Windows XP PC so it will print I/NET Seven Reports: Go to the following location: Windows Start Button > Settings > Printers and Fax Section   Right click on the Default Printer and choose Sharing...   Choose the Share this Printer option. The Printer name and other information will appear by itself after you choose the Share option.   Select the Apply button This should allow the Seven reports to print.