Issue Are symbols allowed in the name of the NPR 2000? Environment I/NET site Cause Are symbols allowed in the name of the NPR 2000? Resolution No. Spaces, underscores and other symbols may not be used. (TCON209, 2-27)

Issue Are NPR 2000s designed to withstand more rigorous conditions than PCs? Environment I/NET Site Cause Are NPR 2000s designed to withstand more rigorous conditions than PCs? Resolution Yes. (TCON 209 Series 2000 NetPlus Router, 1-16)

Issue Using anti-passback and the transactions are delayed by 5 (or more) seconds after the actual card is presented to the reader. During this period (while LED is green) no additional transactions are been recorded to AMT Transaction window. As a result of this the anti-passback is not working for the concurrent swipes.  The interval time between 2 swipes in the controller is configured to 2 seconds. We have tried changing it to zero, but we are not seeing more than transaction within this period come through to AMT. Product Line TAC INET Environment I/NET Seven 2.xx – with Anti-passback Cause When using anti-passback this is usually caused when you have defined the Door Sense setting in the Door Editor and it is either physically not wired or not working. By default this setting is set to Normally Open.   If you have this setting set to normally open or normally closed - the strike will remain energized until the system detects that the door has opened through the sense switch or the strike duration has elapsed, whichever occurs first, the default strike duration setting is 5 seconds. This means any badges that occur during this time are ignored; (only when anti-passback is enabled). Changing the Intercard interval will not make any difference in this situation. Resolution If the door status is not been monitored, you must set the door sense to none. If you are monitoring the door sense then make sure that the door sense activates on each card presentation so that the system recognizes the individual as entering the ‘zone’, therefore allowing the next card to be read.  Note: Implementing anti-passback also requires that you define access control zones. When you use Anti-passback in the true sense it is strongly recommended to use the door sense switch, this is to ensure the individual has actually entered that zone. In situations where this is not possible you can tell the system to ignore the door status by setting the door sense to none, it will then assume that the individual has entered the zone and provide the transaction thereof once the strike duration has expired.  In this case the door strike must be configured to suit the environment. Anti-passback requires that a door controller have both an entry reader and an exit reader. An elevator door controller will support only an entry reader, and therefore, will not support anti-passback. Refer to TCON 300 Chapter 9 – Access Control Anti-passback section for further information.  I/NET Anti-Passback (APB) rules may also be of assistance in setting up Anti-passback.

Issue Difficulty reading the Display Screen on a 7798 SLI back-light is too dark Product Line TAC INET Environment 7798 SLI Cause It is possible to adjust the brightness of the back-lit SLI display screen. The brightness may have been adjusted too low to allow for easy reading of the screen. Resolution Adjust the brightness level using function keys: F7 increases brightness F8 decreases brightness For more information, refer to TCON 138.

Issue Add a stand-alone 7798 to the existing controller LAN Environment I/NET site Cause How to add a stand-alone 7798 to the existing controller LAN Resolution A CLX card is required. Refer to TCON 138.

Issue Accumulate KW consumption for seven days, then clear the data. Product Line TAC INET Environment I/NET Site Cause How to accumulate KW consumption for seven days, then clear the data. Resolution Add a Consumption extension (CN) to the PI point. Collect the data in a docutrend cell. Consumption data is always reset to zero at midnight, even if the PI point is in test mode. Set the transient duration for seven days. Refer to TCON 237 and TCON 239.

Issue Accommodating Individual numbers greater than 24000 Environment I/NET site Cause How do older I/NET systems accommodate Individual numbers that are greater than 24000? Resolution Traditionally, I/NET has required that the key/card numbers assigned to individuals fall within the range of 1 to 24,000. This range supports the maximum limit of 24000 individuals that can be defined for a single tenant. However, it is not uncommon to find that the actual number preprogrammed on a key/card is greater than 24,000. In order to accommodate these higher key/card numbers, I/NET provides a Key/Card Translation table for each tenant. Using the translation table, you can define up to 128 ranges of high key/card numbers and the starting target number. Refer to TCON 300 for more information.

Issue Access Initiated Control (AIC) and Event Sequence (EV, Seq) do not work reliably on site, but the applications work on my simulation test equipment. Environment I/NET site with Access Initiated Control Cause My customer's Access Initiated Control (AIC) and Event Sequence (EV, Seq) do not work reliably on site, but the applications work on my simulation test equipment. Resolution An AIC or an Event is executed once. They are not "re-enforced." An otherwise small communication problem could inhibit the application. So if the control process is critical, use a calculation or module to re-enforce the triggering process. Refer to TCON 237, Calculations, page 7-4 and TCON 236, Direct Digital Control 14-1.

Issue Access Control Application Issues including: Using large number keys Translation tables - when and how Importing and converting existing I/NET 2000 databases Environment Access Control Application Cause Getting started with an access control application. Resolution Detailed information described in: I/NET Getting Started Guide (TCON298 Chapter 1) I/NET Technical Reference Guide (TCON300 Chapter 9) Upgrade.txt file included on I/NET Installation CD.

Issue AMT message stop coming through after re-installation of I/NET Product Line TAC INET Environment I/NET Seven all revisions. Cause If you re-install I/NET from a clean install.  That is you have uninstalled I/NET initially, AMT masking is cleared from the Host PC. Resolution Go to AMT Configuration (Edit > Configuration) Select the correct distribution group and mask settings for the site They must match the source points so that you receive the correct alarms and messages for that Host PC. For further information refer to TCON 299 - Chapter 6 "Message / Alarm and Printer Masks" If this still does not resolve your issue then refer to article AMT not receiving Data for additional items to check.

Issue AMT is Displaying Link 200 and a partial point address. Environment I/NET site Cause Error Message AMT is Displaying Link 200 and a partial point address Resolution AMT can report a LINK 200 + a partial point address. When this occurs the system has defaulted to an error handling code to let the system programmer know that there is a hardware addressing conflict in a direct connect system. To correct this; open active profile in the I/NET configuration editor and modify the link configuration editor. The error generally occurs when the host hardware address is different then the actual hardware address. For example: 7801 Tap is addressed "0" and the Host hardware address is something other than "0". When connecting to a Host/Link/Lan tap (either a 78010 that connect directly to the controller lan or an emulated 78010 on a controller), the hardware address is always 0 and cannot be any different. Please read TAP and Repeater TCON 101 for a more detailed explanation on configuration parameters.

Issue AMT Event Messages Environment I/NET Seven AMT Cause AMT messages are used to diagnose certain system problems. This table can be used to interpret data when an alarm comes in, or needs to be acknowledged, the user can easily reference what is going on. This table was taken from TCON300.  This TCON is updated regularly, so to view the version which works best with your release of I/NET, select START>All Programs>I/NET>Technical Reference Guide. Look on page 3-26. Resolution Note: Most AMT Message "Event Types" are appended with the I/NET Users initials as defined in the Host Passwords.  It is also possible to see the "root" user name appear here, this is when you are using a Xenta Server that is controlling points in the I/NET system.  For example you may see the term "Control root" under the Event Type column.  This indicates that the associate I/NET point has been control by a Xenta Server.   Use this table to interpret AMT messages  

Issue How to find the IP address information on a PC? Product Line EcoStruxure Building Operation Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows including and after Windows7 run a COMMAND window and run IPCONFIG.  

Issue A 7792 is used specifically for what? Environment I/NET site Cause A 7792 is used specifically for what? Resolution It is the interface to Micro Regulators (MRs) and Application Specific Controllers (ASCs), (TCON 209, 1-21)

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 7718 and Expansion Modules Environment I/NET Site Cause What Expansion Modules come with the 7718 controller? Can those be bought separately? Can the ribbon cable or stand-offs be purchased separately from the P16UI expansion module also referred to as the P16UISO Resolution P16UISO 16 Point Universal Input Module 7718 PCU module, 8.6” x 3.4” (21.8 cm x 8.6 cm). Standoff mount. The Sixteen Point Universal Input (P16UI) expansion module provides sixteen universal (analog or contact) inputs. The expansion module card is 3.25"L x 8.60" W (8.25 x21.8 cm). It attaches on top of the 7718 with standoffs supplied with the module. Signals are passed from the P16UI through a ribbon cable type connection between the terminals of the two boards. The input points on the Sixteen Point E16UI Expansion Board occupy point addresses 0100 through 0107 and 0200 through 0207. Please find the 7718 Expansion board Input testing procedure below. Also here is the Datasheet Below is the part number from iPortal: This is the Model numbers and brief description:  Expansion Board Testing Procedure: 7718 Expansion board Input testing All 8 AIs (TBX1-1,4,7,10 and TBX2-1,4,7,10) come in thru the same analog multiplexer IC U3. The only components in front of the Mux is a .47uF capacitor on each input and a 100K resistor on each, and then the user plug-in resistors. I assume reference to TBX1 is associated with 1st input channel on pin 1 and 249 ohm is being plugged in to SIP socket RS3 position A1. Assuming no other resistors are plugged in to any of the Bx, Cx or Dx positions, there isn't much left that can be wrong. Get the specifics of what input signal level is causing what count to be seen. Use M & B of 1 & 0 to report straight counts. Make voltage measurements on the TBX1-1 and TBX2-1 terminals with signal being injected, and record the counts seen on the HHC, or PC, for a low medium and high level signal. An external power supply can be used in place of the sensor to easily set a 0V, 2.5V and 4.90V signal input. We want something less than 5V so we don't get the high end max count of 4095 which can mask a high end + error. If they don't have a supply, differing values of resistance can be plugged in to positions A1 (pull down) and B1 (pull up) with J10 set to B-C position so the B positions are pulling up to 5V. 1K in A1 position and B1 open produces 0V input. Measure and confirm volts and counts 1K in both A1 and B1 positions produces mid scale of approx 2.500. Measure and confirm volts and counts 10K in A1 and 1K in B1 positions produces high end of approx 4.545V Measure and confirm volts and counts This can be repeated on TBX2 using resistor positions A5 and B5 The A/D Counts should equal (measured volts / 5 * 4095) 2.500V = 2047 counts 4.545V = 3722 counts See what the above shows as a possible indication of where something is going awry. An A/D count that is correct on one input and wrong on another with only the specified resistances plugged in, or no resistances plugged and an external voltage source being used, would suggest a faulty multiplexer chip (on only specific selected channels) or a faulty capacitor. Return for repair.  

Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above 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 Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 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 The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost.  The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40.  Link the logs in each group to a different time object and stagger the times at which they are sent.  If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Needing to change the IP address on a Legacy NPR. Environment All versions of I/Net 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 When the IT department changes a subnet or network setting that prevents the device from communicating to I/Net. Resolution There are two ways to change the IP address on the Legacy NPR. 1. This can be done on a Direct Connect by creating a new configuration called NetPlus Router. 2. Make this active and connect the CBL 072 to the upper left connection on the back of the device. 3. Start I/Net and when connected, go to NP Routers, the device will be online with the name that was previously in it or Wantap 1 which is the default. 4. Select it and then modify the IP address and put the new one in, save the changes and hit the okay button. The second way to do this is from the Host PC, 1. Right click on I/O Server and select Configure  2. Modify the Active Profile. 3. Select NPR Routers and follow steps 3 and 4 above.

Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.