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

Some problem #33

Open
shaftmom opened this issue Feb 20, 2023 · 1 comment
Open

Some problem #33

shaftmom opened this issue Feb 20, 2023 · 1 comment

Comments

@shaftmom
Copy link

I think that the signal was collected correctly. (CF = 5.7965GHz), sometimes I could show the target signal(drone-id burst)

Because The output of drone_id_test.grc (Found burst @ xxxx/xxxx) and I was checked that Burst was detected at regular intervals.

After that, I saved the output file collected by filesink block and ran updated_scrits/process_file.

However, only the output shows that burst is not found. I tried several times, but I couldn't check the result.

I used the "gr-droneid-update" branch.

@proto17
Copy link
Owner

proto17 commented Feb 21, 2023

I'm not sure I quite follow the question. It sounds like you recorded samples with the file sink in GNU Radio and then processed those samples with the process_file.m script. It's quite likely that there are no bursts in the file you recorded. DroneID doesn't appear very often (~ once every 600 milliseconds) and frequency hops which doesn't give you much of a chance of actually recording a burst. If you saved off the exact same samples that you saw burst detections for in GNU Radio then it should work. If you post a screenshot of the recorded file in Baudline then I might be able to tell you if what you have likely contains DroneID bursts that for some reason were not processed properly.

Also, what SDR did you use to collect the samples?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants