-
Notifications
You must be signed in to change notification settings - Fork 87
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
(Suggestion) Automate switching to known freqs #24
Comments
I think that's a wonderful suggestion! When I get a chance I'll code up a message based block that hops through a set of channels :) |
I have custom python block with automatic frequency scanning for gnu radio that works perfectly. If you're interested I can share it |
Would like to see this code if you can share it |
Please share, would love to take a look. |
Just add .py extension at the end. |
I think I managed most of what your saying. In GR 3.10 I basically drop a python block on the workspace, open the editor option and paste your code in? I connect on the right hand side to the message par to var block, but what's not immediately clear to me is setting up the SDR source block. I'm assuming that somehow the code in the python block is meant to change the frequency of the SDR? I'm not sure of the setup that would be on the left of the python block. |
You have to add variable named frequency for example, set msg pair to var with the same name and set the frequency in source block same name as msg to var block and the variable used to store what the python script do. The variable needs to have default frequency set, but this doesn't matter because the script is changing it constantly. The left hand side are meant to hold on frequency from other block and those ports are not used at the moment |
Would it help any to apply some of the logic here?
https://github.com/jhonnybonny/CleverJAM
Except instead of running the command to change the center freq of the transmission, use it instead to control the xmlrpc portion of
gnuradio in such a way that the receive center freq would change between known/suspected DJI Drone ID freqs.?
A set amount of time to camp on each center freq can be set, that's got to be better then trying to move around manually trying to find it.. right? I figure it's got to get lucky at some point and capture the bursts for post processing or processing in real time?
Had the thought earlier and figured I'd share it before I forgot.
The text was updated successfully, but these errors were encountered: