Building Automation Knowledge Base

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 Access Initiated Control with Anti-passback (APB) /Anti-tailgate Product Line TAC INET Environment I/NET Cause Application Assistance Resolution Please see the following link: Access Initiated Control & APB/Anti-Tailgate.doc

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.

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 Need for a custom report for the customer, client, user. How to create custom reports. Product Line TAC I/NET Environment I/NET Seven system with the need for Reporting Cause Reports which come with I/NET Seven software preloaded reports may not give the desired report needed or wanted Resolution Clients or Customers often come up with specific reports needed for their site. PSS does not support custom reports, make custom reports for clients, or assist in the development or production of custom reports. You can understand, the report's clients are endless and we simply would be covered up with requests and changes at every site worldwide. It is recommended to take a look at TCON301 (TAC INET Seven Database Connectivity and Reporting) beginning on page 4-1 which explains SevenReports. It is also suggested to look at and compare the different tables and what information they contain. Here you can get a better understanding of reports and take a canned report.  the reports which are available on the install CD and change to fit the needs of your client. This is the fastest and best approach to the manufacturing of custom reports.

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 On a 7718 controller, why do none of the discrete outputs provide 24vdc when energized? Product Line TAC INET Environment I/NET site Cause Using the 7718 controller, why do none of the discrete outputs provide 24vdc when energized Resolution Verify that fuse F9 is not open. (TCON106)