This command turns on monitoring. It is equivalent to pressing the Monitor button on the AeroShield Demo app button bar while not monitoring. The UI button is a toggle. If you send this command while Monitoring is already ON, nothing will happen.

This command turns off monitoring. It is equivalent to pressing the Monitor button on the AeroShield Demo app button bar while monitoring. The UI button is a toggle. If you send this command while Monitoring is already OFF, nothing will happen.

This command returns the current state. The Response will be one of:

AeroShield is not monitoring or tracking anything.

AeroShield is accessing the RSMS and creating the masks for detection.

AeroShield is actively monitoring for drones. As shown, a and b are placeholders. A will be 0 if track 1 is not tracking, and 1 if track 1 is actively tracking. B will be 0 if track 2 is no tracking, and 1 if track 2 is actively tracking.

Begins tracking at the designated frequency. Replace ‘fffffffff’ with the frequency in Hz. So, for instance, to start tracking at 2.426 GHz, you would wend ‘START:2426000000’.

Stops tracking on track N. N is either 1 or 2. If track N is not currently tracking, then the command is ignored, but still returns ‘OK’.

Causes AeroShield to collect sweep traces at the designated bands and save the traces as masks to determine power violations to trigger tracking events. If you want to control the mask creation parameters (dB offset, for instance), you will need to load a configuration file (see below). You cannot send mask creation parameters with this command.

Causes AeroShield to communicate with each of the Remote Spectrum Monitors in its active list. The return for each includes the ping time, and the probe responses to the SCPI commands ‘*IDN?’, ‘FETch:GPS’, INSTument:ACTIve:STATe?’ The values returned are tab delimited. If the RSM does not respond, then the entries will be blank. Refer to the RSM user’s guide for more information about the responses to the SCPI commands.

Saves the current configuration to disk file. You cannot set configuration parameters through this interface, however, the configuration file includes the masks. So using this command is a way to preserve the masks for the current configuration. You can enter a new file name, or reuse one that already exists. You will not be prompted if you overwrite a file. Do not include the angle brackets in the command (‘<’ or ‘>’). Use a fully qualified path name.

Loads a configuration from disk file. AeroShield automatically loads the last used configuration file when it runs. However, you may not want to leave this to chance. As there is no real way to configure AeroShield directly through this interface, using saved configuration files is the best way to do so. Use a fully qualified path name.

This will forward the specified SCPI command to the specified RSM. Please refer to the instrument Programming Manual for details on SCPI commands. This function will return the SCPI function response as the command response. The normal time-out value for this function is 3-seconds. It does not parse the command to determine if it should wait longer. So commands that take a long time to process may not return expected response values.

The RSM number is the ordinal number of the desired RSM in the RSM list in AeroShield. If you want to send the same command to all RSMs in the list, then use RSM number 0.

Returns a list of RSMs in the AeroShield RSM list. This will be in the same order as they appear in the UI.

This command clears the Frequency Ignore List in AeroShield.

This will return the current track point list. This is an array of latitude and longitude values.

The averaging level corresponds to the Track Smoothing setting in AeroShield and is a numeric value.

0: Track averaging off (returns raw data points)

1: Low averaging

2: Minor averaging

3: Medium averaging

4: High averaging

5: Very high averaging.

Any other value will be ignored.

Track number is either 1 or 2.

The RSMs need a high quality network connection to the AeroShield server. If the latency is variable, then the IQ data returned from each RSM may not cover the same time period and it will not be possible to do the TDOA calculation. This function can test for latency consistency and adjust the data collection to better match the network conditions. A parameter called Latency Factor takes a value between 1 and 10. This value controls how much data is downloaded from the RSMs. When the network connection is not consistent, collecting more data helps ensure that there will be a time overlap in the IQ data.

With this function, you can set the Latency Factor directly be specifying a value. Or use ‘Test’ to let AeroShield calculate an appropriate value.

The calibration can take up to a minute, depending on the number of RSMS and the network throughput. It typically takes a couple of seconds per RSM. You can determine if it is complete by sending the Monitor:Status command. This will time-out if the test is still running, and return ‘Idle’ when the test is complete.

Sets/Gets a value determining how much information is displayed in the Event log. Verbose set to True provides more information to be displayed in the Event log. This is useful when setting up a system and wanting to know more about what it going on under the hood. It is not useful when things are operating normally, as it can be too much information to parse easily.