Building Automation Knowledge Base

Issue Door goes to Secure mode even when there is no ATS on it. Environment All versions of I/net Software. Cause The software puts the door in the secure mode by default. Resolution The access control functions within TAC I/NET Seven depend partly on schedules to determine when access will be granted to individuals or groups. The following door related schedules are used for access control: 1. Mode Schedules — You can assign a mode schedule to each door in order to control what mode the door will operate in during specific times of the day. When a door is in the Locked mode, access will not be permitted regardless of any other schedules. 2. Personnel Schedules — You can define up to 31 personnel schedules for each door. Personnel schedules are only used to control access when a door is operating in the Secure or PIN Enable mode. Mode Schedule A door Mode Schedule controls the operating mode of the door at specific times of the day. The following door Mode Schedule actions are available:  APB Reset — Use this action to reset anti-passback memory for this door.  Lock — This mode inhibits entry and exit through the door. All readers and release buttons for the door are disabled while this door mode is in affect.  Unlock — This mode allows open access through the door.  Secure — This mode allows access only after a valid key/card has been read. All key/cards will be validated based on personnel schedules, tenant, key/card issue number, anti-passback, and access level.  When a door equipped with a PIN pad is operating in the "Secure" mode, the PIN pad will not be enabled (that is, entry of a personal identification number will not be required in order for an individual to gain access).  PIN Enable (firmware version 3.20 or earlier)  OR Sec/PIN (firmware version 3.21 or later) — When this mode is active, the PIN reader on the DPU will be enabled. This mode is the same as the "Secure" mode except that it also requires the individual to enter a valid PIN after a valid key/card read. If an individual enters an invalid PIN, the setting of the PIN Retry Count parameter in the Door Extension Editor will determine how many retries (if any) the individual can use to enter a valid PIN.  You can schedule a door's PIN pad to become disabled without unlocking the door by following this mode with a "Secure" mode. When the "Secure" mode becomes active, individuals will no longer be required to enter a PIN in order to gain access through the door.  Sec/Code (firmware version 3.22 or later) — This mode is similar to the "Secure" mode; however, rather than using a key/card to gain access, the user simply uses the PIN pad to enter the door's assigned code. If the individual enters the correct door code, the door will open.  When the door is operating in the Sec/Code mode, user-definable door attributes or PIN pad functions are not available. Note: If the door needs to be unlocked then they can manually be unlocked for that period then return to the secure mode when needed.

Issue If user exits I/NET (Using System > Exit) and then re-starts I/NET again with logging off, the previously logged on user is automatically logged back in. When starting I/NET, user is not required to enter a password.   Environment I/NET Seven Cause The I/O Server with no clients has three settings which can be configured for its active profile as defined below: Maintain – Enable this option to allow the I/NET I/O Server to continue running in the background, even when no I/NET client is currently active. In this case, you will remain logged into the I/NET system. Logoff – Enable this option to be automatically logged off of I/NET when you shutdown the host software application. The I/NET I/O Server will continue running in the background, even when no I/NET client is currently active. Shutdown – Enable this option to shutdown the I/O Server after all I/NET clients have been shutdown. Resolution Change the active profile I/O Server setting to either logoff or shutdown.  Both Logoff and Shutdown will deactivate the last user logged into I/NET so if this is the functionality required, then either of these two settings should be used.

Issue Upgrading a 779703 bin file from a pre-I/NET Seven release to current. Station conflict errors occur after upgrading a 779703 ICI Environment 7797ICI I/NET Seven I/NET ICI Configurator Cause The 779703 ICI can be configured to use up to 4 channels using the DCU address feature HHC.  This information is then stored on the Save file. We have found that this information can be corrupted when upgrading a save file from a very old build to a very new build. The Controller will reserve the same number of addresses as configured in the MXL Panel Address. Resolution   Verify with the customer that it is safe to take the ICI offline Direct Connect to the ICI and perform a station save Disconnect the ICI from the controller LAN Verify that the ICI is configured as the correct type using Edit>Controller>Configuration If needed, save the controller in Network Configuration Download the bin file While the file downloads, verify it is a 779703 build Once the download is complete connect to the controller and perform a station restore Open the ICI Editor Confirm with the Fire alarm contractor that all points are monitoring correct variables Select Edit>Configuration Note the current configuration Set the ICI Port as Enabled Set the Baud Rate as 9600 – Confirm this is correct with the Fire Alarm Contractor Set the Data Bits to 7 Set the Stop Bits to 1 Set the Parity to Even Set the Inter message delay to .05 Set the Response time out to 2 Set the MXL Panel Address to 1 (this is set incorrectly intentionally on the first download after a major upgrade) Disconnect from the controller in the ICI editor In I/NET perform a station Save In I/NET perform a station restore Reconnect to the controller in the ICI Editor Change the MXL Panel Address to the correct address of the panel. This number will have to be provided by the fire alarm contractor. Use the Handheld to verify that the DPU address is correct. If the panel is 0358 this should read 005858. If 000058 then the bin file is incorrect, if 0058xx then repeat steps 20-25 In I/NET perform a station Save In I/NET perform a station restore Test a point with the fire alarm system. Copy the save file to disk and save it for future reference

Issue When adding multiple cards to a user where does the number go. Environment All versions of I/Net Seven Cause When adding multiple cards to a user, depending on which format is being used, the adjacent field is automatically updated. Resolution When adding multiple cards to an individual, depending on which format is being used it automatically put the adjacent number in that field. 1. For big card numbers or HEX numbers, those have to be entered in the HEX field and would automatically populate the decimal field. 2. For card number equals individuals, the card number must be entered in the decimal field which will automatically populate the HEX field.

Issue Making changes to I/O Server with out logging into I/Net or I/Net Configuration Environment All versions of I/Net Seven prior to 2.40 Cause Without login on to I/Net or the Configuration Editor, changes can be made to the system and accepted. Resolution When I/Net is launched it authenticates the user thus allowing the changes, however, if the user does not log on, the buttons that require this authentication are all grayed out., So it may look like changes can be made but notice that the OK button does not become available, so no changes will be saved in version 2.40 and above.

Issue I need to re-order some replacement 7700 Expansion Boards Environment Any Windows OS and I/Net System Cause I need to get the Part Numbers of the replacement Expansion Boards for the 7700 Controller Resolution All of the Expansion Boards are no longer available on the Iportal site.

Issue How to set up Automatic DCU Save Environment All versions of I/Net Seven. Cause Setting up Automatic DCU Save and it does not work. Resolution To resolve this issue the following steps needs to be followed: 1. Go to Edit/Host Computer/Network Functions 2. Select the link that the controllers need to be saved on 3. Click on Setup and check the box to enable Daylight Savings Time 4. Put in the parameters 3-2-1 and 11-1-1 and click Okay.

Issue SQL Server or SQL Express errorlog files can reveal what is the health of your site Environment I/NET site with Full SQL or SQL Express installed for the database. Cause Ensuring processes within SQL are completed successfully. Errorlog file is so large it is filling the Hard Drive. Resolution View the SQL Server error log to ensure that processes have completed successfully (for example, backup and restore operations, batch commands, or other scripts and processes). This can be helpful to detect any current or potential problem areas, including automatic recovery messages (particularly if an instance of SQL Server has been stopped and restarted), kernel messages, or other server-level error messages. View the SQL Server error log by using SQL Server Management Studio or any text editor. For more information about how to view the error log, see How to: Open Log File Viewer. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files. A new error log is created each time an instance of SQL Server is started, although the sp_cycle_errorlog system stored procedure can be used to cycle the error log files without having to restart the instance of SQL Server. Typically, SQL Server retains backups of the previous six logs and gives the most recent log backup the extension .1, the second most recent the extension .2, and so on. The current error log has no extension.

Issue How to Take a Controller to boot from the I/NET Host workstation Environment I/NET PCU DCU Cause Performing a station restore or bin file restore fails. Resolution In I/NET Select Edit>Host Computer>Software Restore Select the Controller you wish to take to boot Select the checkbox marked "Software" Click OK When the software download reaches 10% of the total size click Cancel You can verify the controller is in boot by attempting to connect to it, or by using netcon Repeat steps 1-4 to allow the bin file to completely load before using the controller Make sure you do a station restore to the controller after the "Boot" process

Issue Forgotten or deleted default password. Product Line TAC INET Environment All versions of I/NET Seven Cause Users either delete the default password and then forget what theirs is and is unable to log into the system. Resolution To resolve this, the following steps need to be followed: Close I/NET and I/O Server Open up DBCreate and choose the option to back up the database. Put the backup database on the ftp site so that engineer can get to it. They would then reinsert the default tac/dacs password back into the database. Place it back on the ftp site so that the customer can retrieve and restore it back on the system again.

Issue Report when previewed appears in a very small square on the screen with unreadable characters. Environment All versions of I/Net Software. Cause The default printer is set to a badging printer. Resolution To resolve this issue the following steps should be followed: 1. Check the Printer Setup for Seven Reports. 2. In the Design Tab, right click on left side of the Report Designer to display the context menu. 3. From the context menu click Design > Printer Setup. Using the Printer Setup dialog select the appropriate printer or select "No Printer" option in the upper left corner of the dialog

Issue Access Control Button not visible on the Toolbar. Environment All versions of I/Net Software. Cause The check box that enables access control in the configuration editor has been unchecked. Resolution To resolve this issue, the following steps needs to be followed: 1. Right Click on I/O Server, select the Configure link and modify the active configuration. 2. In the configuration editor, there is a radio button next to Enable Access Control. 3. Check this box, click on the Okay button, click on the make active button and close I/Net and I/O Server. 4. Restart I/Net and I/O server again, log in and the Access Button should be available now.

Issue Is there a limit on the number of action steps for a sequence? Is there a memory limitation on the number of action steps for a sequence? What prevents me from adding any more than 13 steps to a event sequence?  Environment I/NET Seven - Event Sequences Cause Due to memory limitations, if using any of the Output commands, you are limited to only use 12 lines items per event sequence instead of the normal 18 line items per event sequence. An allocation of 128 bytes of memory is allocated for each sequence, adding an action sequence to a point requires 8 bytes of memory plus additional bytes for each action defined in the sequence. The memory required for each event sequence action is shown in the table below.  The system will notify you when this memory limitation is reached via this "Sequence to complex" error. Action Memory Required Start Start with Lock Stop Stop with Lock Lock Door Lock Door with lock Inhibit alarm Enable alarm Event Unlock 5 bytes Output Output with Lock 9 bytes Skip if Zero Skip if Non-Zero Unconditional Skip 6 bytes Resolution If your are using only the "Output with Lock" or "Output" event sequence action in one sequence, only 12 lines are allowed.  If more lines are required, the SKIP command can be used to connect as many sequences (maximum of 64 per controller) as required.

Issue Failure with extended or long path or filename Environment I/NET Cause Failure or crash with long path name or filename Resolution In rev 2.41 the length of the path+filename went from a total of 128 characters to max path: 260, max filename: 256 Example: The following path is 132 characters long and therefore would not be compatible with revisions prior to 2.41: C:\Documents and Settings\Houston\My Documents\My Sites\Disco Inferno\DesignScape Files\20120411_MirrorBall_Points by Controller.xls

Issue When a Xenta Server alarm object generates and email, the email is accompanied by several emails showing alarms from objects that did not go into alarm. Environment Xenta Server 5.0.2 through 5.1.7 Cause When the system program in the Xenta server polls multiple point simultaneously it may interpret one alarm signal as multiple alarm signals from all polled points. Resolution Option 1 - Edit the Xenta Servers Xbuilder project Change the scan time on all alarm objects so that they are at different scan rates. Generate the project Send the project to target. Option 2 - Connect to the affected I/NET controllers Modify the points in Resident I/O Change the scan rate of each point so that all alarms have different scan rates.

Issue Hardware address Wrong address Direct connect Environment I/NET Direct Connect Cause Hardware addresses where used with the old TAPs and this address needed to be the same as the address configured on the TAP set by their dip switches. These TAPs are hardly used anymore and when you use a Direct connect to say a 7798C and a hardware address are set, you will get unknown address data in AMT Resolution Right click I/O server and choose properties and modify your profile Modify your Direct connect settings Set hardware address to "0" Software address can still be used

Issue Upgrading to the newer versions of I/NET Seven and Crystal Reports are not working. Environment All versions of I/NET Software using Crystal Reports. Cause Because of differences between versions of the Crystal Reports runtime engines, any reports that you save in SevenReports 2.21 or later will not be compatible with SevenReports 2.20 or earlier. If you intend to continue using a report on SevenReports 2.20 or earlier systems, do not save the report in SevenReports 2.21 or later. Resolution The reports that come with TAC I/NET Seven are preconfigured to use the default instance of SQL Server. If you have configured your system to use any other instance of SQL Server for TAC I/NET Seven’s database, you must manually define the database settings for each TAC I/NET Seven report you intend to use. The SevenReports application allows you to create and print reports containing information from one or more databases, including TAC I/NET Seven database views. Using SevenReports, you can generate: Standard Reports – Standard reports are pre-configured to contain basic TAC I/NET Seven data. Each report contains the full range of data available (i.e., all of the database records in the appropriate tables). TAC I/NET Seven includes over 30 canned reports. Custom Reports – SevenReports allows you to create custom reports by selecting database views, selecting fields, creating links between the fields, and designing the report layout. All reports may be previewed on the monitor screen prior to printing. Some reports, such as those containing tenant information, allow you to specify a range of data to include in the printed report. This allows you to print a report that concentrates on specific information.

Issue Version of I/NET software and StruxureWare Building Operation software Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 I/Net versions 2.40 and greater Cause With the release of StruxureWare Building Operation's integration with I/NET, customers want to be prepared for it when it comes out and needs to know which version of I/NET software they need to be running to do so. Resolution For the initial rollout, 2.42 was listed as the preparation build to upgrade to for StruxureWare.  Users can upgrade to this build or the current build (2.43 at last edit) and begin upgrading all bin files. This will be required for StruxureWare integration. The bin files did not change between 2.42 and 2.43. Each release of StruxureWare may have a corresponding release of I/NET.  For the time being users will be required to upgrade both I/Net and StruxureWare at the same time. The upgrade from 2.42 to 2.43 is a no-cost upgrade. It should be considered a best practice to upgrade I/NET and StruxureWare at the same time even when not required.  The 1.3.0.938 release of StruxureWare requires I/NET 2.43. If the site upgraded to 2.42 they will not need to upgrade bin files for the controllers.

Issue Data not showing up in the consumption report. Environment All versions of I/Net. Cause The points that are trending data are not matching up with the new host, therefore it is not collecting any data. Resolution After restoring the database, open up the trends editor and create or match the trends on the new Host PC.

Issue Can Pelco's Control Point Software run on the same PC as I/NET Seven Software? Product Line Pelco, TAC INET Environment All Windows OS I/NET Seven Software Pelco Control Point Software Cause The two software packages are not compatible with each other. Resolution Pelco's client software cannot be installed on the same PC that is running TAC I/NET Seven. See TCON 301 - Chapter 6.