Introduction
These release notes cover AdvanceGuard V4.4 and above.
Contents
Version 4.6.0 Build 457 - 06 February 2020
Tracker 4.4.1.114 Release Notes
Improvements
Improved handling of Display Rotation
Added ability to change port for Mobile Server
Version 4.6.0 Build 453 - 03 February 2020
Tracker 4.4.1.114 Release Notes
Improvements
Added Pending Acknowledge Alarms to alarm report when a client connects to ICD-001
Version 4.6.0 Build 452 - 31 January 2020
Tracker 4.4.1.114 Release Notes
Fixes
Fixed Users can restore and reset the database
Fixed issue with cameras not always populating in Milestone plugin
Fixed issue with retreiving cameras from Milestone
Version 4.6.0 Build 448 - 29 January 2020
Tracker 4.4.1.114 Release Notes
New Features
Added the new Mobile Server and Web-based user interface. This new interface offers a full operator experience through the browser and also opens the option of using the web UI inside other applications, such as VMS and PSIM.
Added the new Genetec integration plugin which utilises the Genetec Web SDK
TUN-3357 - Added coast ratio to the property options for the property check in the rule editor
TUN-3382 - Added logic so that tracks are ignored from a radar / tracker when the radar has been disabled
Latest Dutch translations have been added to the language options
TUN-3482 - Added AlarmKey to Camera and Alarm Reports in ICD-001. This provides a simple mechanism to link alarms with camera reports which can help external systems decide when to start and stop incident recording
Added Camera External Id to ICD-001 Camera Report
TUN-3372 - Added distance labels to area when being edited. Each section of the area will display a dynamic length value which changes as the area is modified. These distance labels can be hidden if required.
Improvements
Improved External Trigger Rule Action that now supports following input or using latched mode. In addition you can choose the output state, which supports using dry relay contacts in fail safe mode
Merged Area and Profile status reports into a single status report for ICD-001. Status reports can now be requested and the request includes a filter which enables external systems to request which parts of the status report they want to see
Improved the ICD-001 Request Status command to use numeric flag value to filter the status report response
TUN-3347 - Improved handling of errors that can cause the Management Server to crash which includes improved RTS connection logic
Improved handling of TCP Clients to ensure internal and external network connections are more robust to major topology changes and connection disruptions
Added improved handling of reading XML data from the RTS system
TUN-3348 - Changed icon for arm / disarm notification message to Light On/Off
TUN-3369 - Updated UI to support 500Km x 500Km display area
TUN-3408 - Improved Integration Simulator Alarm Clear/Acknowledge Handling to match the logic used within the main application
TUN-3467 - Added STC group and tidied up the labels on the system profile page of the radar
TUN-3453 - Made access to user settings for user level accounts permission controlled so users can be prevented from changing their own UI settings if required.
TUN-3446 - Improved the Breach Line and made it easier to select both in and out of edit mode
Allowed an administrator to reset any users settings
TUN-3438 - Added a verification to add a randomly generated key as final confirmation when selecting the database reset option
Added Health Status to ICD-001 Status report for each radar
Added Enable state to ICD-001 Status report for each radar
Added BreakingTrackDbId to Highways Alarm Source Payload in ICD-001
Fixes
Fixed an issue with the global camera settings not applying without a Management Server restart
Fixed an issue where cameras were taking too long to process messages which resulted in erratic camera behaviour
Fixed error when requesting open street map background tiles to avoid
Fix potential memory leak with alarm manager
Added Radar Model to ICD-001 Track report output
TUN-3497 - Fixed radar check rule node so it properly filters tracks based on selected radar and channels
Fixed an issue with Allow Alarm Acknowledge not being visible when adding a new user
Fixed an issue where a track that is breaking the close following rule is not added to the alarm triggers list and therefore is not reported correctly
The Witness services are no longer prefixed with Navtech but with AdvanceGuard
Note that due to the database upgrade, this version must only be installed after upgrading to V4.4.0 first.
Related information
-
Rules (Witness 4.0)
-
Breach Lines (Witness 4.0)
-
Entity Timeouts (Witness 4.0)
-
UI Recording (Witness 4.0)
-
AdvanceGuard® System Design (Witness 4.0)
-
AdvanceGuard® Alarm Panel (Witness 4.0)
-
AdvanceGuard® Configuration (Witness 4.0)
-
Track Correlation (Witness 4.0)
-
Quick Reports (Witness 4.0)
-
AdvanceGuard® Settings (Witness 4.0)
-
AdvanceGuard® Track Queries (Witness 4.0)
-
AdvanceGuard® Alarm Queries (Witness 4.0)
-
AdvanceGuard® Queries (Witness 4.0)
-
Navigating AdvanceGuard® (Witness 4.0)
-
Technical Manuals - AdvanceGuard (Products)