Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FFT output to ZMQ socket proof of concept #1199

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

willcode
Copy link
Contributor

@willcode willcode commented Mar 19, 2023

When the waterfall is updated with a new fft line, the fft output for that line is copied to a ZMQ ipc socket /tmp/gqrx_zmq_fft.sock. Each message has 2 parts. The first is JSON formatted metadata, containing timestamp, frequency, rate and fftsize.

Sample programs to use this data are included in the scripts directory. There is a recorder program that creates meta and data files in /tmp, and a numpy-based plotter program (a certain, constant fftsize is assumed).

ZMQ development files are required, CMake files now look for ZMQ.

For C++ JSON, nlohmann/json (single file) has been copied in.

This branch is based on another branch currently, to make development easier. It can be rebased elsewhere when needed.

@argilo argilo added the feature label Mar 25, 2023
@willcode willcode force-pushed the feature/zmq-out branch 4 times, most recently from c1dba52 to e59260b Compare March 29, 2023 10:32
@willcode willcode force-pushed the feature/zmq-out branch 4 times, most recently from 93bb4dd to ce1b191 Compare April 8, 2023 13:12
@willcode willcode force-pushed the feature/zmq-out branch 12 times, most recently from baf8e95 to 62f6a0a Compare May 9, 2023 01:37
@willcode willcode force-pushed the feature/zmq-out branch 3 times, most recently from 2ee12e5 to 2703b09 Compare May 15, 2023 13:29
Signed-off-by: Jeff Long <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants