-
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
Zc sequence identify #34
Comments
The brute forcing code that currently exists is unlikely to work for the downlink since there are almost certainly a different number of occupied carriers. My guess is that you'll need to do the following:
I'm not certain this will work, but it might. It's likely that the downlink also follows the LTE spec in its number of occupied carriers. If true then you're likely to see one of: 600, 900, 1200, 1800, or 2400 [1] occupied carriers. I have no idea if they use all of the occupied carriers for the ZC sequence as I haven't had a look. You can probably look at the spectrogram (waterfall) view in a tool like Baudline to see if they are all being used. Good luck! [1] https://faculty.coe.drexel.edu/jwalsh/Gwanmo-Nov11-2.pdf <-- See slide 4. Use the bandwidth of the signal to tell how many occupied carriers it should have |
Appreciate for your reply,which gives me an new inspiration. |
Hi, I m interesting about your brute testing to get the root for drone ID zc. Have you tried that on the DJI downlink signal?
My test for downlink zc got a wired result, which has only one root answer for 1022 (I suppose there are two type of zc in one frame). There must be some errors I missed.
The text was updated successfully, but these errors were encountered: