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
My current setup uses USRP B-205 mini connected to a 2.4/5.8 GHz antenna for the RX2 to decode DJI Mavic 2 which uses Ocusync 2.0 protocol. I tried running the code both in indoor and outdoor environment and encounter the same issue, which it still stuck at the endless loop of trying to find the center frequency.
As I read through the code, I noticed that the list of frequencies are hard coded, is there a way to obtain the drone's actual frequency that it is communicating so that it can lock to it.
Furthermore, I have tried setting the 'Legacy = True' and still obtain the same problem.
The text was updated successfully, but these errors were encountered:
Hi, sorry that this is a bit unrelated, but were you able to get decoded payloads using the offline receiver? I'm currently trying to do it with a different SDR but have had no luck
@BryanCastorius
Ok, good to know. I assume you ran the offline receiver in legacy mode since you're using the Mavic 2 Pro? I get the following error when I run it in legacy mode, so I was wondering if you made any changes to the original code. It seems to be locating the packet correctly based on the spectrum but I'm stuck here...
Dear @mrlnc,
My current setup uses USRP B-205 mini connected to a 2.4/5.8 GHz antenna for the RX2 to decode DJI Mavic 2 which uses Ocusync 2.0 protocol. I tried running the code both in indoor and outdoor environment and encounter the same issue, which it still stuck at the endless loop of trying to find the center frequency.
As I read through the code, I noticed that the list of frequencies are hard coded, is there a way to obtain the drone's actual frequency that it is communicating so that it can lock to it.
Furthermore, I have tried setting the 'Legacy = True' and still obtain the same problem.
The text was updated successfully, but these errors were encountered: