Tracking activity is logged in the Event Log. When the system detects a drone candidate, it monitors it for several TDOA measurements to verify movement. Each tracking occurrence that is identified as a signal of interest will get logged into the Event List tab.

If a signal is determined not to be a drone, the AeroShield API software will stop any attempts at tracking. The signal’s frequency and bandwidth will be added to the Ignore List as described in Ignore List. This minimizes the possibilities for false positives, i.e. detecting a signal that is not transmitted by a drone.

The displayed details include estimated location coordinates, time occurred, and status update messages. When the Verbose API Command is set to True, (See API Command DroneTracker.VerboseMode Property) more information becomes available in the Event Log, A warning message will be displayed if the trace data exceeds the mask at more than 50% of the data points. This is an indication that the mask is probably inappropriate and needs to be redone.

Each signal identified as a drone transmission is also identified in the Track Summary.

The information in this screen is sent to the host program to be saved. Right-click in this window to display a dialog as shown in Figure: TDOA Log Window Context Menu.

Pauses adding new events to the log accumulation. Unpause will update events.

Copies the log contents to the Windows clipboard.

Opens save dialog. Save as an (.alg) file

Clears the log display. All entries are lost.

The TDOA correlation ratio will be written to the log after each TDOA measurement. This information relates to technical details of the location algorithm, and will not be of value to typical users. This selection is a toggle and will turn off when clicked again.

Displays all mask violations in the log file. This selection is a toggle and will turn off when clicked again.