OmniPreSense workstream
OpenFlight hardware-trigger capture
I implemented and tested an opt-in OPS243 internal-trigger capture path for OpenFlight while preserving its sound-trigger default.
I built the radar-side trigger workflow for golf-swing capture and saw the implementation merge upstream.
StatusMerged upstream PR #221
problem
The problem
The existing rolling-buffer capture relied on an external SEN-14262 sound-trigger edge. I needed an opt-in OPS243 internal hardware-trigger strategy so the radar could make the speed-trigger decision and dump rolling I/Q history without that external module.
contribution
What I built
I configured and validated OPS243 firmware and trigger settings, waited for the board-generated dump, parsed the capture, and re-armed the workflow before passing parsed radar data into OpenFlight processing.
I tested trigger, signal, capture, and parser behavior against the OpenFlight integration path. The PR validation path requires OPS243-A firmware v1.3.2 or newer in the 1.3 release train, while sound-trigger mode remains the default.
result
Where it stands
The implementation merged into OpenFlight through upstream PR #221 in October 2026, giving this contribution a public upstream implementation record.
Public references