Building Automation Knowledge Base

Issue SCU in double-address mode and the second station is not responding. Once a card is read at any of the readers, a Reader Entry is displayed in the Transactions Window but the strike never fires. The DO point can be manually controlled through Software but not by any of the readers. Environment I/NET SCU1284 Cause The MCU Configuration must be set to restore the DPU. Resolution Connect to the controller, then go to MCU Configuration. Both of the addresses on the DPU should be Blue. Turn the second address to Internal and exit the editor. Open the Editor again and change the setting to DPU. Perform a DPU restore and try the card again. A Reader Entry should show up in the Transactions Window and the strike should fire, indicating that it is working properly.

Issue Anti-PassBack (APB) Flag functionality Environment I/NET Seven APB Cause Anti-Passback flags will not broadcast across links Resolution Keep in mind the limitations of the APB flag. The broadcast of the APB flag will not cross links nor is it intended to cross links. An NPR is used to connect links to a front end or to another link. The APB flag cannot be broadcast through this device. Only doors and controllers on the same Link (CLAN) as the sending device can receive the APB broadcast. When designing APB systems, ensure that doors for the same zone are all on the same link.  

Issue Creating a Backup of the SQL Database Environment I/NET Seven Cause A backup of the database should be done once a month, at least, to ensure that everything is saved in the event of a crash or an upgrade is needed. This will assist in getting the system up and running again with little or no downtime Resolution Close I/NET and I/O Server Go to Start > Programs > I/NET and select DBCreate Utility Log on using the username/password that was created when I/NET was installed Select the option for backup database Select the location where this backup would be placed. Preferably on another folder outside of I/NET Select Start and name the file the date that it is being done on for easy reference and then let the program run Upon completion, verify that the file was created with the date and time stamp.

Issue Trying to run an ARG (Auto Report Generation) and nothing happens. Environment I/NET SevenReports Cause Unused fields may be preventing report from running Resolution When setting up the specific report, delete any unused parameters like date, time etc. Then delete any unused fields in the Select Expert field. Save the report and then set up the Options, Duration and Recurrence fields. Once the time has elapsed based on the settings, the report should run and print or export to whatever device or format you selected.  

Issue User Defined Pin Environment I/NET site with Access Control Cause user defined PIN issue Resolution User defined PINs require door controller firmware revision 2.30 or later. If a door controller has a firmware revision prior to 2.30, the only valid PIN is the system-generated PIN, regardless of the entry in the Individual Parameters editor. If you have mistakenly set user-defined PINs on a system with older firmware, simply disable the user defined PIN in the Access Control Options editor, and restore the DPU(s) to return to system-generated PIN numbers. Note: For best results, do not mix DPU firmware version 2.30 or later with older DPU firmware versions if you wish to enter user defined PINs. It is possible to create a situation where the user's PIN is one number (system-generated) for certain doors, and another number (user-defined) on other doors, in which case the PIN shown in the Individual Parameters editor would not be accurate for all doors. Six-digit PINs Six digit PINs are supported on the SCU1284 and on the DPU7920 with MIP (firmware 3.16 or later). All other door controllers support PINs with a maximum of five digits. If your system includes a mix of door controllers (i.e., some controllers that do support six-digit PINs and some controllers that do not support six-digit PINs), you should avoid assigning six-digit PINs. This will prevent users from being locked out of a door because the door's controller will not accept the user's complete PIN.

Issue Programming a 7798C controller with a Virtual HHC Console Environment 7789C HHC Hand Held Console Cause The 7798C controller can only be programmed with the Emulated HHC Console (The TacHHC.exe is located in the support folder of the INET install CD) using CBL 082 connected to the PC and RS 232 port on the controller. Resolution Before following these steps, make sure you have closed down I/NET, AMT and the InetIOServer applications.    Locate the HHC file on the I/Net CD, Support Folder and copy it to the Root of I/NET. Once copied, double click on the file to launch it, I/NET should not be running at this time. Connect the CBL 082 (Grey shroud connects to the PC)  The virtual HHC is displayed at this time. Right Click and Select the Com Port and Baud Rate. To Set the Controller Type: On the HHC, select Code 90, Enter to set the Controller Type. To Set the Controller Address Select "DCU Address" Enter he desired Address To Set the Baud Rate Code 06 for C-LAN Code 91 for Sub-LAN baud rate. To Direct Connect Once completed, disconnect the CBL 082 from the PC and replace it with CBL 072 for a direct connect to the controller. Start I/NET and open the configuration editor, create a new profile for a direct connect, if it has not been created already. Make this configuration active, close the configuration editor down as well as I/Net, and then restart it again. At this time communications should be established with the controller and the user can start programming the controller. 

Issue In an SCU1284 what is the "DO" addressing scheme for a Single Address unit. Environment I/NET site with Access Control Cause desire to know the DO addressing scheme Resolution The "DO" addressing scheme on a Single Address SCU 1284 is DOxx00 thru DOxx07

Issue In an SCU1284 with a dual address what is the addressing scheme for the "DO's"? Environment I/NET site with Access Control Cause Addressing issue with SCU1284 Resolution In the Dual Address mode of the SCU1284 the "DO's" addressing scheme is as follows First four relays are associated with the first address DOxx00 thru DOxx03. The Last four relays are associated with the second address DOyy00 thru DOyy03

Issue Clearing IP address in the 527 routing table Product Line TAC INET Environment I/NET TCP/IP Cause Routing Tables build themselves by self discovery. Resolution Routing tables build themselves by self-discovery on the network. If there is more than one device/host PC, similar function(s) may need to be performed on each device. Telnet utility for Host PCs, I/NET NPR2000 are examples. NOTE: Anytime you use the I/NET Command Line: inet(space) and the command you want to use for example; inet ip. Steps to clear a 527 routing table. Log into X527 with your web browser. Select the utilities folder. Select I/NET folder. Select I/NET Command Line. Make sure the word inet is in the command line and press submit. Then type inet delall to delete all the routing tables for the Xenta 527. You can type in inet help and this command will list all the all Web Shell Commands. ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all listsv ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records  

Issue If you are integrating LON to I/NET with a Xenta 527 or Xenta 913, you may run into a unit conversion problem in the integration process. Product Line TAC INET, TAC Vista Environment I2V I/NET LON Integration Xenta 527, Xenta 913 System Program Version 5.0.0 or higher XBuilder 5.0.0 or higher Cause When integrating LON to I/NET, all data will make its way to I/NET in SI units. Resolution View the units of the points on the LON side of the connection object in XBuilder. On temperature, for example, XBuilder uses the unit "F" to show Fahrenheit on a temperature signal. However this temperature value will show up in I/NET in Centigrade.  Engineering units on the AO point in the I/NET controller will have to be "F" to mirror the unit on the LON signal in XBuilder. These two units have to match exactly, and they are case sensitive. When the engineering units match on both points, I/NET will convert to the correct value. If the value on the I/NET side is left blank, it will just pass on the Celsius value. There are limitations to this conversion since I/NET has a four-character limit and some units in XBuilder will exceed this. Pressure, for example, will have to be sent in Pascals or PSI. 

Issue Cache Time for Record Changes - Xenta 527 for Vista - I/Net systems. Environment I/NET Seven integrated under Vista Xenta Server 527 / 731 Cause When using the Xenta 527 Web Server to view records in Vista from I/Net Seven, changes that are made do not show up immediately. Cached data does not reflect any recent changes made in the original SQL Host database. Once data has been stored in the local cache, the Cache timeout must expire before the data can be updated by retrieving it from the SQL Host. The default time is set to 720 minutes, which allows the device to store data read from the SQL host for twelve hours.   Resolution The default time is set to 720 minutes, which allows the device to store data read from the SQL host for twelve hours. If the user wants to see the changes made and not wait for that period, they can connect to the device and change the Cache Time. If the system is large, this may affect performance and cause slow down because of the volume of data that is coming through. Choose a time that is best suited for the application. However, by restarting the device it also gets an update from the SQL Host.

Issue Deny Entry Tenant Message on an SCU Environment I/NET site with Access Control Cause Messages in AMT Resolution Programming an SCU 1284 for the first time on an I/Net Seven System would more than likely give a Deny Entry Tenant message in the Transaction Window when a card is read at the reader. This would usually occur if the Card Number equals individual scheme is being used. Although all the normal parameters have been checked, there could be one of these that would have been overlooked. Access the doors that are on the SCU, and then modify them. When the editor comes up, there is a Check box for Card Translation. This comes up checked by default, uncheck it, hit the OK button and then read the card again. A Valid Card Read or Reader Entry Message should show up in the Transactions Window. Perform a software and database download, then an SLI and DPU Restore to the DPU in question.  

Issue First Key Auto/Unlock Environment SCU 1284 Cause The first key Auto Unlock feature that was available on the SCU 1284 is not displayed on the Door Editor, in revisions 3.22 and above. This can only be seen in revisions 3.21 and below. Resolution To access the feature, the following steps need to be followed: Select the door from the list and then click on the Modify button. Select the ATS button and select the first Entry. Select the first schedule and click Modify. Select First Key Mode and click on the drop down box. Select the Unlock option and then click on the OK button. Close the editor and then read a valid card to ensure that it is working properly.

Issue I/NET Utility Patch - Upgrading I/NET 2.14 and above. Environment I/NET Cause Two directories are required C:\Program Files\INet Seven and C:\INet Seven Data. These changes occurred as a result of requirements for future release revisions of I/NET and Microsoft Vista - Microsoft 2005 Server Operating System.   Resolution When upgrading I/NET Seven revision 2.14 and above to the later versions using the patch on the web, you are required to run the utility patch twice. Note: When I/NET is compatible with MS Vista and MS 2005 Server a release announcement will be published. Caution: You should always perform a data base backup before you start any upgrade process. A new install of 2.14 will create the data directory in a different location than prior revisions. An upgrade install will not move the data directory from its current location. The patch utility is unable to determine that the data directory has moved. Therefore, it needs to run against both the program directory and the data directory. The following steps should ensure this is done properly: Using the patch utility, point to the program directory by selecting C:\Program Files\INet Seven and execute. Once completed, run the utility again and now point to C:\INet Seven Data and execute. This ensures that both the program files and bin files have the correct version for that revision. Note: Prior to starting I/NET force an upgrade on the database using the DBCreate Utility.

Issue All NPRs on a site are giving 'Host Lost / Host Restore' alarms, but the TCP/IP network is functioning 100%. Environment I/NET Cause Changes to bin file revisions sometimes include updates to communication Resolution This can be caused by a mis-match in .bin file revisions on all downloadable controllers. Verify all the .bin files in each downloadable controller are from the current I/NET revision at the customer's site. The mis-match can come from a tech loading a .bin file from his laptop (with a different rev than the customer). It can also occur when I/NET is upgraded, but the controllers aren't.

Issue Upgrading from rev 2.1X to 2.16 Environment I/NET 2.1x site Cause desire to upgrade to newer release of I/NET Resolution When upgrading from revision 2.10 and higher to 2.16, there is an additional step that is required. If you get to 2.16, start I/NET and only question marks are displayed when you connect to the controller, or it takes a long time to connect. There are two work-around things to try for this. Run the 2.15 patch or reinstall 2.15 and then upgrade to 2.16. Run DB Create, force an upgrade to the database and verify that the database version does in fact match the revision that you are running. To get to the revision number, click on the header on DB Create, then select about, it would show this information. The other work around is to just close I/NET and I/O Server and restart them again.

Issue I/NET shortcut utility in Vista 5.1 does not create shortcuts when browsing in the I/NET link. Environment I2V Integration Vista 5.1 Cause The shortcut utility will fail if there is a "\" in any of the I/NET point names contained in the .sav files. This character is not a legal character in Vista, however the shortcut utility should replace it with an "_" and it doesn't. Resolution Change any "\" characters to "/" Re-run the wizard.  As always, it is good practice to only use Vista legal characters when integrating anything to Vista. Vista legal characters (space) [ ] _ : /

Issue Site 0 on DLA Applications Environment I/NET site Cause For future expansion of the system, address 0 has been reserved when implementing DLA (Distributed Link Architecture). This causes the Host to distinguish when making contact with an NPR, whether it is set up for DLA or not. There are certain flags that are set in this configuration internally by each device on the way it will communicate with other Hosts and NPRs Resolution It is recommended that address zero("0") be used for Non DLA applications and 1 to 63 for DLA. This should be implemented just to avoid conflicts with existing sites. Furthermore, it is also necessary to clear out the Routing tables for each device that this is being incorporated on.

Issue Pin Pad Functionality on HID Readers Environment I/NET site with HID Pin Pad Cause Incorrect wiring in the PIN Pad Resolution Using the PIN Pad function in HID Card Reader applications requires that the D1 and D0 wires be terminated on terminal 3 and 5 respectively. If regular door modes are being used i.e. Secr/Unlk/Lock then this does not affect how the DPU interprets the card read. If PIN is being used for Arm/Disarm or gain entry, then this termination needs to be addressed. If terminated improperly, a valid card read will be seen at the reader but a Deny Entry t/o will be registered in the Transaction Window of AMT and the desired function will not be accomplished.

Issue Online Messages on an SLI Environment I/NET site Cause Messages coming from the Sub Lan Interface (SLI) Resolution A door controller (DPU) has a limited amount of memory space available for storing individual records and messages. "Resident in DPU" individual records are given priority in storage: they are never discarded. Transient (non-resident) individual records and messages are stored on a space-available basis. If a communication outage between the SLI and the door controller causes the door controller's memory capacity to be reached, older records must be discarded as new messages continue to be generated. All records are discarded on a first-in, first-out (FIFO) basis, so that the remaining records are the most recent ones. A "DPU queue ovflw" message will also be generated to warn that data was lost. Records are discarded in the following order: Transient individuals. Messages. If there are no more transient individuals to discard, routine messages will be lost. When communications between the SLI and the door controller are restored, the contents of the door controller's queue (including the "DPU queue ovflw" message) will be delivered, freeing memory in the door controller. The SLI continually requests messages from its door controllers. Retrieved messages are queued within the SLI until they can be sent to appropriate host workstation(s). When the SLI queue is full, it will continue to accept messages from door controllers (i.e., the SLI will not cause its door controllers to discard messages). With its memory queue full, the SLI will discard older messages as newer messages are received. This ensures that the remaining records are the most recent ones. A "DCU queue ovflw" message will be generated to warn that data was lost. When communications between the SLI and the host PC are restored, the contents of the SLI's queue (including the "DCU queue ovflw" message) will be delivered, freeing memory in the SLI. There is also a TPA-DALL-09-0001.00 that was written on this issue.