You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered: