Who rated this article

Possible causes and solution(s)

Symptoms

We have received reports that some customers are having issues with Intelligent tracking when it’s enabled manually or via script.

This is seen in scenarios when the user does not want to have intelligent tracking on all the time because of compounding alarms or other environmental variables.

We found that there was a change in the way intelligent tracking worked after CPP 7.3 firmware v7.62.0005. With these changes if an object triggered an alarm that turned on intelligent tracking, the camera would not track the object. It would wait for another object to trigger an alarm to track it.

Solution

Currently, there are 2 workarounds to get the desired behavior with CPP7.3 firmware:

1. Using a duplicate alarm with a debounce timer:

Example

• First task may be used to turn on autotracker (mode: auto)
  //@Task T:2 V:0 I:2 "Crossing line 2" { //[1.a=(s1:1);1.b=2;1.h=32;11.a=o:20.0;] Event #32:={CrossedLine#1}
  ;
  external Event #2 := {Event #32 !before(0,20.0) Event #32 where first.oid == second.oid};
  //@}
  
  
• And second Task will be most properly triggered by the same object may be followed by the autotracker
  //@Task T:2 V:0 I:3 "Crossing line 3"
  Unknown macro: { //[1.a=(s1}
  ;
  //@}
  
  

2. Use the VCA task editor to remove triggers from the VCA task:

Example

• //@Task T:1 V:0 I:1 "Object in field 1" { //[1.a=(s1:1);1.b=1;] external ObjectState #1 := InsideField #1; external Event #1 := OnSet ObjectState #1; //@}