Issue LMHOST Setup for File Equalization Issues where mapping PC/IP is necessary. (Networking, DSL) Product Line TAC INET Environment I/NET Seven Site Cause Setting up Equalization over a Network/DSL Connection on XP Service Pack II PCs, there may be an issue. At some point in File Equalization, the client needs to connect to the File Master by its machine name even though the setup identifies the FM using an IP address. Resolution For users that are trying to set up Equalization over a Network/DSL Connection on XP Service Pack II PCs, there may be an issue. At some point in File Equalization, the client needs to connect to the File Master by its machine name even though the setup identifies the FM using an IP address. This is a change that was probably introduced by XPsp2 and/or MSDEsp3. In any case, to get the remote client (PC Name=XXXXX1 / IP=X.X.X.X) to connect to the file master (PC Name = XXXXX2 / IP=X.X.X.X), setup a LMHOSTS file in each PC. This file is located in C:\WINDOWS\System32\drivers\etc. Please use the following document to help set up the LMHOST: LMNHOST File.doc. To setup a second client to point to the file master, the LMHOSTS file from the first client will need to be copied into the same location on the second client PC. This will allow the new client to know both the IP address and machine name of the file master. Note: If you are not familiar with the LMHOST instructions, please seek an IT professionals assistance.

Issue Running Windows XP, Service Pack 2 and I/NET Seven Configuration Instructions Product Line TAC INET Environment I/NET Site running XP Cause Windows XP Service Pack 2, it will be necessary to configure the Firewall feature which is on by default in the Service Pack Resolution Please see the following link to configure XP to allow I/NET Seven file equalization to function properly. XP SP2 Configuration and InetSeven.doc

Issue I have a Windows XP PC and I cannot get Seven Reports to print. What do I do to correct this? Product Line TAC INET Environment I/NET Site Cause What are the steps to change the Printer properties on Windows XP which enables printing of I/NET Seven Reports?   Resolution There are some settings that are required to correct this issue. Please see the following link: Printer Properties.doc

Issue Discrete Monitor (DM) and Discrete Control (DC) Points Product Line TAC INET Environment I/NET Site Cause Explanation of Discrete Monitor (DM) and Discrete Control (DC) Points Resolution These points are always used in a pair. They control devices that would otherwise be controlled by an ordinary DO but are considered critical enough to warrant a DM/DC combination. The DC point does the actual controlling (opening and closing of the hardware contact) and the DM point provides positive feedback from an external discrete device (for example, an air flow switch). The DM point is typically wired to a proof-of-flow switch that transitions when the controlled device is started or stopped. It may also be used to monitor an auxiliary contact on a motor starter if a proof-of-flow switch is not installed. However, used in this way, the only information you are really receiving is that the contacts have closed or opened, but not whether the device is actually running. Adding a resident DM point to a controller requires 30 bytes of memory. Adding a resident DC point to a controller requires 37 bytes of memory. When controlling DC/DM points using CU/PCU resident DDC, calculated points, or automatic temperature control (ATC), the Resident I/O Points editor entries of Scan Interval, Time to State, and Alarm Delay are very important. Use the guidelines below to ensure that an alarm is correctly generated any time the DM point’s actual state conflicts with its respective DC point’s Expected State: See Link Below Regardless of which program is used, the time to state and alarm delay entries for the points should always be set large enough that the point being controlled is allowed ample time to change state (start, stop, etc.) before the point is declared to be in alarm. The DM point’s alarm delay value should always be set greater than the DC point’s time to state value. In DCU/PCU resident DDC, the scan interval of the module should be set greater than the time to state and scan interval entries of the DC point being controlled. When using a calculated point extension to drive a DC/DM pair, the DC point’s time to state should be less than the scan interval of the point. When using ATC to control a DC/DM pair, it is important to remember that the point will always be issued a command by the program at the rollover of each minute. If the space temperature exceeds the cooling setpoint plus 1⁄2 the differential at 35 seconds past the minute, the DC point will be controlled ON in 25 seconds, again 60 seconds later, again 60 seconds later, and so on. When using ATC, it is recommended that the scan interval, alarm delay, and time to state entries all be set less than 60 seconds, allowing this alarm checking to be completed prior to the rollover of the next minute, when ATC issues its next command. For further detail please use following link: DC-DM Operation.doc

Issue Troubleshoot an NPR problem with Windows Telnet utility. Product Line TAC INET Environment I/NET Seven with NPR Cause NPR problem for a variety of reason and how to use Windows Telnet utility Resolution Please use the attached link. Warning: Read First, then call Product Support with questions. This utility can cause system communication issues when improperly used. NetPlus Routers.doc

Issue How to view a summary of number of Host (Workstations) on an I/NET network including their Host ID. Product Line TAC INET Environment I/NET Seven 2.13 and above Cause An alternate user interface that you can use to setup your network configuration, and to configure your access control system, rather than using standard menu commands. Resolution This version of I/NET provides an alternate user interface that you can use to setup your network configuration, and to configure your access control system. Rather than using standard menu commands, you can instead use a tree-based interface by selecting View System View from the main I/NET menu. The System View Window When you launch System View, it is displayed as a double-pane window. This window is non-modal; meaning that you can open other windows and editors while the System View window is open. The Left-side Pane The left-side pane contains a hierarchical tree that represents the structure of your system. Along the bottom of the left-side pane is an Access tab and a Netcon tab. By default, the Access tab is active, causing the main area of the left-side pane to display a list of the tenants defined in your access control system. This list contains an “All Tenants” entry as well as an entry for each tenant that you have already defined (if any). If you select the Netcon tab, the access control information in the left-side pane is replaced with network configuration information. The Right-side Pane The right-side pane provides a Context tab and a System tab. By default, the Context tab is active, allowing the pane to display information about items you highlight in the left-side pane. You can use the System tab to duplicate the functionality of the left-side pane in the right-side pane. This is especially useful when you wish to drag items from one pane and drop them into the other pane (refer to “Using Drag and Drop” below). Expanding and Collapsing Items You can expand an item by clicking its plus (+) symbol. This causes subordinate items to display, indented beneath the expanded item. Subordinate items may also have a plus symbol, indicating that they too can be expanded. After expanding an item, the plus sign changes to a minus (–) sign. Click the minus sign to collapse the expanded item. Using Drag and Drop One benefit to using the System View interface is that you can drag and drop items from the right-hand pane to items in the left-hand pane. For example, you could drag a Group from the right pane to an individual in the left in order to assign that group to the individual. Displaying a Context-sensitive Popup Menu By clicking with the right mouse button, you can display a popup menu of available functions. This popup menu is context sensitive, meaning that it can display functions that are only applicable to a selected item, as well as functions that are common among all items. When you right-click a blank area, the popup menu shows functions that are applicable to the System View window. Print and Print Preview At any time you can print the entire contents of the left-side pane by right clicking anywhere in the pane and selecting Print from the resulting context menu. Only the items that are currently displayed in the pane will be included in the printed output. Therefore, no subordinate information for collapsed items will be included in the printed output. You can display a preview of the printed output by right clicking anywhere in the pane and selecting Print Preview from the resulting context menu. Using the preview window, you can switch between a one-page and two-page display, navigate from one page to another, zoom in and out, and send the output to a printer. When you use System View to configure your network, each device displayed in the hierarchical tree can include a status indicator. This indicator shows the device's status as of the latest refresh. The following table describes the status indicators and their meanings.

Issue Displaying 32 Bit Floating Point data in I/NET with an ICI, an I/Link, or a FieldServer bridge. Product Line TAC INET Environment I/NET site Cause How does one display a 32-bit Floating point value in I/NET Resolution An uncommon occurrence, but at times it is needed to display a 32-bit Floating point value in I/NET. The source of such a value could be from devices such as an ICI, an I/Link, or a FieldServer bridge. This document and this I/NET SAV file will describe and demonstrate the process needed to calculate the value of a 32-bit floating point input into I/NET as two AI points. Displaying 32 bit floating data in INET.zip

Issue Configuring Special Day Schedules. Product Line TAC INET Environment I/NET Site with schedules Cause What are the steps to make sure the Special Days works correctly Resolution Special Days are handled a little differently in Access control. The steps to make sure the Special Days work correctly is discussed in the attached white paper, Special Days Setup I7.doc.

Issue How do I create a Multi-Columned report for an A-Sample Trend? Using I/NET Seven and Sub Reports (Seven Reports) Product Line TAC INET Environment I/NET Seven 2.21 and below Cause In most BMS systems the most common report was a tabular (or column report) of data. Seven Reports (Crystal Reports) did not provide this facility easily.  Although it can be achieved using the subreport feature within Seven Reports.   Resolution The Steps to create this report are discussed in the following link. Subreports process w screen captures.doc

Issue Running an I/NET Seven report and only seeing the first 500 people or doors in a system. Keyword search: Crash when an attempt to open, Crystal Reports, and failure. Product Line TAC INET Environment I/NET system and desire to run reports over a lot of data Cause The Crystal Reports that I/NET is using has a default value of 500 objects to be listed in a report. If you require more objects to be listed in a report, this requires a windows registry change to do this. Resolution Note in the attached document the registry location may change slightly based on the version of I/NET and SevenReports installed version.   If unsure or the locations cannot be found search for the following registry keys: BrowseTimeout - This entry controls how long, in seconds, the Info Report Designer will browse for records. MaxNBrowseValues - This entry controls how many unique records the Info Report Designer will browse before stopping and displaying the records found. For the Release 2.40a and above running the NON_RDC release HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer\ For the Release 2.41 and above running RDC version: HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer Component\ In the Crystal Report terminology, an object could be people or doors, in which case make the registry change based upon the largest number you have. For example, if a site has 5000 people and 500 doors, set the registry to accommodate 5000. The steps required to make these changes are in the Crystal Report Tech support paper linked to this article.

Issue Configuring Daylight Savings Time. What is the proper way to do this? Product Line TAC INET Environment I/NET Cause There are two different ways to setup the Daylight Saving Time in I/NET. Daylight Saving Time DST is not observed in Queensland, the Northern Territory or Western Australia, South Africa, and other parts of the world. The document below shows how to set 0 in the DST settings. If using a revision of I/NET prior to 2.21 be reminded that the DCU time sync problem in the ReadmeSeven.txt is not just pertaining to the error generated by not having DST settings for the controller. 2.21 is referring to the version where this was fixed. Also note that when upgrading a site, go all the way to 2.31 at least because it solved problems which were in the previous revisions. Resolution Option #1: Using Windows time and NO controller time synch Set Windows Time for daylight savings changes. Remember to change the time zone for you location. In my example I am in the Central time zone. Set the Inet Host settings to do Time Sync. Function for all the controllers you wish to time sync with the PC. Enable the Daylight Savings settings using the "Setup" button. This is the correct settings for the controller configuration. Note if you set the daylight settings in this format you will get a 2 hour shift up or back. The daylight setting must be set to zero (0)   Option #2 Using Windows time and controller time synch Set Windows Time for daylight savings changes Set the Inet Host settings to NO Time Sync. Function This the correct setting for this controller configuration using the controller to shift the daylight saving time   The Daylight Savings times were set by the Congress of the USA in 2004 The beginning was to be the second week of March on a Sunday. This comes out in I/NET as being Month = 3 Week = 2 Day = 1 (Sunday is always day 1 Thus Saturday is day 7) The ending was to be the first week of November on a Sunday This comes out in I/NET as being Month = 11 Week = 1 Day = 1 (Sunday is always day 1 Thus Saturday is day 7)

Issue No door transactions coming into AMT Transactions are not been sent by only one door. RX and TX lights on DPU / SCU are not flashing as per other DPU's Product Line TAC INET Environment I/NET SCU / DPU Cause If you have the AMT masking set correctly and the Door Editor has transaction defined for the reader entry or exit and there are no transaction messages showing up in AMT. Then one of the issues might be the Quick Poll (QP) is turned off for that DPU.  Resolution Go to Edit > Controller > MCU Configuration Select the Station in question Is QP checked for all DPUs? Here is an example where this is not properly configured: QP needs to be checked, however, it is not possible to check or uncheck this column if the controller site is already set as DPU. Change the controller type from DPU to MR, then select OK. Go back to the Communication Statistics editor and put a checkmark in the QP box for this controller, then select OK. Go back to MCU Configuration and change the controller type back to DPU, then select OK. If the site is ever edited by any earlier version of I/NET, check Quick Poll.

Issue Using a Door's Card Reader to Inhibit and Enable Alarms Product Line TAC I/NET Environment I/NET Cause Access Initiated Control (AIC) can be used to trigger points based on reader entry.  This is triggered regardless of if the door is open or closed. Also, when using multiple commands, such as inhibit/enable alarms, one would need multiple readers to trigger the points.  The following process allows you to use the same reader to trigger both the enable, and inhibit alarm function. Resolution Create Points: If you have not done so yet, build a point for the Door Status.( These directions assume that 1= Open and 0 = Closed) Build an internal point called AIC Trigger. Create a calculation that keeps this point in the off state Configure AIC Create an AIC that will turn the AIC Trigger point on with a reader entry Assign this AIC to the appropriate door Create Event Sequences Create an event sequence called Enable Create an event sequence called Inhibit Modify the Inhibit event Sequence Add lines that will Inhibit each alarm For the last line, set a delay equal to the strike duration and the type as Skip if non-Zero Set the point as the Door Status and the Sequence as the Enable Sequence # Click OK Modify the Enable sequence Add lines that will Enable each alarm Click OK Click close Select Edit>Controller>Point Extensions>Event Definition Double Click on the AIC Trigger Point Set the Event type to Specified State Select "Sequence" and set the sequence number as the Inhibit sequence Select the State/Value as On Click OK Results Entering the door with a valid card read will cause all alarms to go to an inhibit state After exiting the door and allowing it to close, one can scan a card to enable the alarms. This will take effect after a delay equal to the strike duration. This process is based on the door position switch being open or closed as the strike duration expires. So that arming the system will only occur if the door is closed. There is a potential flaw if someone is able to scan a card, enter the room, and close the door before the strike duration expires.  If this happens the system will re-arm itself as the strike duration expires. For this reason, it is important to have as short a strike duration as possible.

Issue DPU Restore, when and what information is downloaded to the Door Controllers Product Line TAC INET Environment TAC I/Net Seven site with DPU or SCU 7910, 7920 1284, 1280 door controllers, download Cause A variety of errors with door access can be attributed to download individual information to the door controller(s). Resolution When changes are made to any one of the following, a download is triggered to each of the DPU/SCU controllers. Name Group Issue Level Card Number If using DPU Restore, remember that during the DPU\SCU restore, these are the items that are being downloaded. Cold Start signal - followed by point data from the SLI Tamper Parameters (SCU Only) Translation parameters Tenant information Floor Mapping\Personnel data for each Elevator\Door Secondary Time Schedules End of the Cold Start process After the Cold Start ends, then the Big Card Numbers (HEX) are restored from the SLI to the DPU\SCU controllers

Issue Where do I find the conversion utilities / files I need to convert my old I/NET data to I/NET Seven? Product Line TAC INET Environment I/NET site Cause Cannot remove the last special day in a 7750 Building Manager Resolution These files as well as many other supporting documents are located on the I/NET Seven CD.

Issue A laptop has USB ports, but does not have serial ports. Can I/NET run using USB ports? Product Line TAC INET Environment Windows XP Windows Vista Windows 7 Cause Most new computers do not provide the “Old Style” serial ports, they now have USB ports instead. Resolution A lot of Schneider Electric have been using the KEYSPAN USB to Serial Adapter. The Part Number is KEYSPAN – USA – 19HS. Click here for a data sheet. This product can be seen by going to https://www.tripplite.com/ Please note that there are other products that are equally as good

Issue Can 78040/50/60 TAPs be mixed in a network configuration with 78041/51/61 TAPs? Product Line TAC INET Environment 78040 TAP 78050 TAP 78060 TAP 78041 TAP 78051 TAP 78061 TAP Cause Mixing these two types has never been tested nor supported. Resolution Never mix these two types of TAPs in a single network. Refer to Tech Tip 047 for more information.

Issue PID module has gone to "control-point" Product Line TAC INET Environment I/NET DDC PID Cause The PID may have gone to "Control Point" due to unforeseen circumstances and is causing a problem. "Control Point" can also be used intentionally as a control strategy. Resolution Four reasons: If the Setpoint’s value crosses above or below the high or low input limits as populated in the PID editor, this will force the PID to go to control-point. If the process variable should reach the low or input sense limits as entered in the Resident I/O editor, the PID will go to control-point. If either the Setpoint or Process variable should go to "OLD" status, the PID will go to control-point until the "OLD" flag goes away. If the user should change any variable within the PID, when exiting the PID editor, the PID will go to control-point until the next scan of the module. For more information on this subject refer to Tech Tip G062.

Issue Can DDC lines in ASCs be displayed on I/NET Graphic Pages? Product Line TAC INET Environment I/NET .gpg graphics DDC Lines Cause DDC Lines are represented different from Resident I/O points. Resolution Yes. The following Lines are the most common to view: Line 1 = Active Cooling setpoint Line 4 = Active Heating setpoint Line 5 = Active setpoint (*see below) Line 10 = Cool CFM setpoint (only on VAV-X2) Line 12 = Airflow setpoint (only on VAV-AX and X1) Line 14 = Mix Air (only on AHU w/ mixed air econ. control) Line 15 = Warm CFM setpoint (only on VAV-X2) Line 26 = Cool Air Flow (only on VAV-X2) Line 27 = Hot Air Flow (only on VAV-X2) * Line 5 should be the same as the value displayed on the STR-250, I/STAT, M/STAT. It will display either line 1 or line 4's value, whichever one is closer to the current space temperature. If average is selected for SPD, then line 5 will show that averaged value even though the controller is operating on the actual heating or cooling setpoint. For a complete listing of all ASC points and lines, see ASCLines.pdf.

Issue Highlighted a door point and selected Schedules; I cannot modify the schedule. What is wrong? Error received: Communication with this SLI could not be established. Editing cannot be done. Product Line TAC INET Environment I/NET Seven Work Offline (Offline edit) Cause When you highlight a door point schedule, I/NET attempts to establish communication with the selected door’s SLI (Sub LAN Interface). If communication with the SLI is successful, I/NET will proceed normally. However, if I/NET cannot communicate with the SLI, you will not be able to modify the schedule assignment for the selected door.  This is the case also for the following editors: Access Initiated Control Personnel Schedules Door Schedules Doors Elevators Resolution Communication must be established with the sub LAN devices (DPU) before schedules can be edited. It is possible to do this in an offline mode as long as you have the Sub LAN Interface's (SLI) SAV file.  Refer to Offline Database Edit  for further information on Offline Edit.