Repository navigation
Trigger window
The Trigger window detects signal events according to selected conditions. It can be used during live spectrum capture and also with replay files.
The trigger must be enabled before conditions are evaluated. When disabled, all trigger settings remain visible but no events are detected.
The trigger can monitor the whole visible sweep range or a selected frequency range in displayed MHz. If frequency shift is active, the trigger range follows the displayed shifted frequency, while HackRF tuning remains internally unshifted.
Cooldown sets the minimum time in seconds after a trigger event before another event can be logged. This prevents one long or noisy signal from producing too many repeated events.
The trigger source determines which spectrum data is used for trigger decisions.
- Realtime spectrum uses the current realtime trace.
- Peaks use detected peak values.
Match mode controls whether all enabled trigger conditions must be true, or whether any one condition is enough.
- ALL requires every enabled condition to match.
- ANY triggers when at least one enabled condition matches.
Maximum level trigger watches the strongest level found in the selected frequency range. Use this for simple signal presence detection.
Total power trigger sums the power across the selected frequency range. This is useful for wider signals where the highest single bin may not describe the whole signal well.
The operator defines how measured values are compared to the threshold. The threshold is entered in dBm.
The trigger can play a sound when an event is detected and can write trigger events to a CSV log. The CSV file is saved into the root dir. Name of the file has the following format:
# TRIG <start_freq>-<stop_freq> MHz <date> <time>.csv
The CSV file can then be easily imported into a spreadsheet.
The event list shows detected trigger events with time, replay offset, frequency and level.
In REPLAY mode, trigger events can also be shown on the replay progress bar as orange line markers.
Find in replay quickly scans the current replay file for events matching the trigger settings. This is useful when you have a long recording and need to locate signal activity without watching the full replay in real time.