Release Notes Intelli-Site
Author: Lori TassinCreated: 06-18-2019 06:01 PMLast Updated: 08-25-2021 10:50 AM

Products to which this article applies

  • Intelli-Site


This article contains the release notes for Intelli-Site v4.0.41.10.  The following sections describe the release in detail and provide late-breaking or other information that supplements the main documentation.

This is a maintenance release that improves quality, reliability, and performance. All Users are encouraged to upgrade to this release.

New Features

The following software features were added:

  • Access Management View
    • The number of transactions displayed in the Activities tab is limited to Days to Log, a field on the Card Data tab.
      Card Data tab with day to Log Callout
    • When a user with a specific User Level adds personnel and/or card, the user's level is assigned to the personnel and/or card database record. This allows the personnel and card tables to be filtered on a user's level when the Filter card database records by User Level field on the Setup node properties is checked.
      Setup properties dialog
  • Activity View 
    • Includes the Panel name with the point name
    • Includes the seconds in the timestamp for each event displayed
  • Design View
    • Replication of a screen object with child screen objects will also replicate the child objects. The user is presented with the Replicate Object dialog listing the possible common targets. He/she selects those objects that will be replicated in the new object(s).
      Replicate Object with multiple common targets
    • The automatically created screen object for the User Level database field is a combo box (drop-down menu) containing the defined User Levels. This makes adding this screen object to a Card Data screen easier. This is useful when the personnel and card records are to be filtered by User Level. A system administrator can add personnel and cards specifying the User Level for the record instead of his/her own. This is powerful when Intelli-Site is controlling a multi-tenant facility. The system administrator has complete access, but each tenant is logically isolated and can only see and manage its own personnel and cards.
    • For all newly created Door screen objects, the DOTL state uses a blue image if there are not intercoms specified in the Door Construct. This does not affect any existing Door screen objects, only new ones. 

The following Panels were added or upgraded:

  • New! Allen Bradley
  • New! Simple Host Interface Protocol (SHIP)
    • Allows 3rd party software to connect to Intelli-Site via TCP/IP and send commands using simple text strings. 
    • Only Engine-based actions are valid commands. 
    • The target of actions is designated by the node's ID encased in square brackets (e.g. [1932]).
    • At this time, only one command per packet is allowed.
    • Intelli-Site will respond with ACK or NAK to each command. 
      • ACK means the command received was properly formed, valid, and was executed.
      • NAK means the command was improperly formed or invalid. Details on any NAK responses will be written to:
        • The driver's Messages window if it is open. Both the Driver and Translation checkboxes should be checked to see all of the information related to the NAK response.
        • The Activity database is an exception. An Exceptions report will display the error. 
    • When the communications method is TCP/IP (not TCP/IP Listener), Intelli-Site will send a heartbeat to ensure the connection remains active.
    • The user can specify a Frame for each message containing a Start String and/or an End String. If the field is not empty, every message MUST contain the specified string(s). If not, Intelli-Site will respond with a NAK and throw the message away.  For example, the Start String field is "xXx" and the End String is "XxX". A message to toggle node 1334 is "xXxToggle [1334]XxX".  

Resolved Issues

The following issues affecting all products have been resolved:

  • Configuration Utility
    • In version 4.0.40, an error was introduced that caused an exception when a Project was created. It didn't affect existing projects, but new projects could not be created.
    • At installations using MSSQL, every project created now uses the designated database type including the first project.
    • When the project is created, the User Level on the database node in the Tree is explicitly set.
  • Desktop Client
    • Access Management View
      • In Single ID mode, after a personnel/card is added, it is selected by default and the selection arrow in the first column is actually on the correct row.
      • Filtering based on User Level now works as expected in both Single ID and Multi-ID.
    • Information Manager (Alarm Queue)
      • The [View Card Record] button on the Alarm Acknowledge/Clear dialog requires the user to close all open dialogs before it will switch to the Access Management View. If the user is actively adding/editing a personnel or token, this button requires the changes to be saved or abandoned before it will work. The Alarm Acknowledge/Clear dialog is opened by right-clicking on the event in the Alarm Queue. The [View Card Record] button displays if the event is a card read event.
    • Live View
      • Clicking on a rotated screen object works as expected now.
  • Panels
    • Digital Watchdog
      • The Auto Detect progress bar is back.
      • Auto Detect now uses the connection information of the current Digital Watchdog panel. There was an issue where Auto Detect would use not reload the connection information even if the panel was a different panel.
      • An intermittent unhandled exception on Apply in the Quick Config with a large number of cameras being added/updated/deleted is now fixed.
      • Additional logging has been added to the log file
    • MAC
      • The alarm queue no longer shows **Not in Database** for invalid card reads when the card does exist.
      • In the Quick Config dialog, changes to the names of the Inputs and/or Readers update the Quick Door tab drop-down lists (combo boxes) immediately without saving the changes.
      • There was an issue where a card could not be found in the Intelli-Site database if it hadn't been downloaded to the panel. This has been fixed. Auto-download Valid cards work again.
      • For Controlled Doors on the Quick IO tab, the Shunt point's default value is blank.
      • MLC-32i Quick Config dialog, Quick IO tab
      • Controlled Door: Editing an existing controlled door item now loads the saved values into the dialog and properly lists the available options in the drop-down lists
      • Operator Reset Alarm: Editing retains the value for the Alarm field and displaying the available options in the drop-down list
    • Omron
      • Setting the value for Value whose address is greater than 255 works now.
      • When the physical Omron device returns the wrong amount of data for a memory area, Intelli-Site handles it gracefully. It could happen in the case of a retry where the panel responded to both requests but the driver was expecting only one response. If the packet received doesn't contain the expected amount of data, the driver won't process it. The next poll will clear it up. If it doesn't, the problem is that the network is heavily taxed causing an inordinate amount of retries.
      • At one site, polling randomly stopped on one out of several panels. A condition occurred whereby the polling flag wasn't cleared. The design was changed to no longer rely on a flag but to actually search the send queue before scheduling the next poll request.

The following issues specific to Intelli-Site Lite have been resolved:

  • N/A

Below are issues related to specific OEM versions:

  • MASC
    • The screen object created by dragging and dropping a door construct to a screen has been modified
      • The Unlocked state is after the Forced state
      • The Flash To field has been cleared on the DOTL state

Known Limitations


Products to which this article applies

  • Intelli-Site