WarDragon Remote Drone ID Detection Update w/ Node-Red Map Plotting (Sniffle, DragonTooth)
Вставка
- Опубліковано 27 сер 2024
- In this video, I'll guide you through the setup of a modified Sniffle repository designed to decode FAA Remote ID from drones, focusing specifically on Bluetooth 5 Long Range Extended types. I'm using DragonOS, specifically on a WarDragon configured with all the necessary equipment. Let's dive into the details!
Key Highlights:
- Repository Setup on DragonOS: Step-by-step instructions to set up the modified Sniffle repository on DragonOS, tailored for FAA Remote ID decoding.
- Bluetooth 5 Long Range Extended: In-depth focus on capturing and decoding signals using Bluetooth 5 Long Range Extended.
- Troubleshooting Node-Red: Tips and tricks for resolving common issues with a Node-Red Docker setup. Mostly my fault.
- Sniffle with ZMQ Server: How to start up the Sniffle Python code with ZeroMQ server support.
- Node-Red Flow Configuration: Configuring a Node-Red flow to connect to the Sniffle ZMQ server and process the decoded drone information.
- Plotting on a World Map: Displaying decoded drone information, including latitude and longitude, on a world map.
Understanding Remote ID and Regulations:
The FAA (Federal Aviation Administration) in the United States and equivalent regulatory bodies in Europe require drones to broadcast their identification and location for safety and security purposes. Remote ID acts as a digital license plate for drones, providing crucial information to law enforcement and other agencies to enhance airspace safety.
Why Tracking Drones is Helpful:
Tracking drones can significantly enhance safety and security by providing real-time information about drone activities. This is particularly important for preventing unauthorized drone operations in sensitive areas, assisting in the coordination of drone traffic, and ensuring compliance with aviation regulations.
Ethical Use and Testing:
It's important to note that the modified Sniffle repository includes the ability to transmit Remote ID packets for testing purposes. This feature is intended solely for educational and development purposes. I strongly discourage any misuse of this capability and urge viewers to use this feature responsibly and ethically.
By the end of this video, you'll have a fully functional setup capable of decoding FAA Remote ID signals from drones using Bluetooth 5 Long Range Extended and visualizing the data on a world map using Node-Red.
Links to the Repository:
Modified Fork github.com/bke...
Original github.com/ncc...
FlightViewGui (mentioned in the video) github.com/alp...
WarDragon available here (when in stock):
cemaxecuter.co...
Don't miss out on staying connected:
Catch updates on Twitter: / cemaxecuter
Supporting the channel:
If you appreciate the value this content brings, I invite you to consider extending your support through Patreon: / cemaxecuter
Very cool, been messing with the DroneRemoteIDSniffer project, some European kids wrote it and it's pretty buggy to get running with a variety of WiFi dongles.
Would love to see this ported to use with a HackRF or BladeRF one day to go it over 2.4 and 5.0/5.8 ISM bands beyond the BLE implementation
The person that did the fork is actively working on an SDR port. That’ll be super handy too!
Flightviewgui? Docker? Nodered? This video makes me feel like such a smooth brain. At least I got the dongle flashed and running so I can type the gps cords into Google maps 😂
Any chance all this comes to FocalX soon?
I probably overly complicated the video, essentially if you do the following
git clone github.com/alphafox02/flightview_gui
Follow the guide in the readme to install docker
then just
docker compose -f docker-compose-node-red.yml up
It should start up node red. You’ll also notice I put the example flow json in the directory. You should be able to piece it together.
I’m honestly trying to work out a way easier method asap!
@@cemaxecuter7783Wow I got it, thank you! I see the new subscriber on Sniffle and NodeRed map is open. Now to wait for a drone to fly by...
I still needed to remove the docker image and retry it, even though it was a fresh install, so glad you left that in there.
@ericks1979 was this on a WarDragon? I only ask cause I emailed out a new base image. If you’ve restored to that image it should’ve had the new node red and everything setup. Just curious.
@@cemaxecuter7783 no just FocalX R36 on a Toughpad
@@cemaxecuter7783 no just FocalX R36 on a Toughpad
Very nice!
man what a pain! I have pulled apart many droneID units and sensors a lot use a ESP32 of some kind
I'm trying to follow, but what software is drawing the map?
Hey there! Amazing work on the Dragon Kit project. I've followed your progress on X since the beginning, and you've come a long way. Quick question: do you have a LinkedIn account where I could message you privately? Also, will you be attending Defcon this year? also i want to order the kit i been the site so let me know how i can go about that as well.
Shoot me an email sometime. It’s up under the UA-cam about section. I try to monitor it. I do plan on being there! If your outside the US I will have to coordinate some kind of shipping arrangement, but if your in the US you can grab it from the cemaxecuter.com site. I have a bunch of the full kits I’m working on now.
🎉🎉🎉
Can this work with a RTL SDR dongler?
In the repo is not mentioned but works on the same frecuencies
Bt5 operates in 2.4ghz well outside range of the rtlsdr. However, the developer of the modified repo is working on porting things to an SDR (would need the freq range of course).
@@cemaxecuter7783 Oh I didn't know it was 2.4GHz, hopefully the developer you mention finish it soon for HackRF or BladeRf , thanks for the reply btw
@314Show no problem, I think the sniffle original developer is also pursuing a SDR version, so I think we will see some great stuff soon!
i tried installing dragon os pi version and i'm using a 4inch lcd screen and when i tried to install the lcd drivers i get a github error i can't get it to work. do u know the work around for this? i updated everything but couldn't get it Thanks
Can you shoot me the details on the screen? I never did get around to trying out screens besides a normal monitor but some people in the source forge discussion/ticket section got a few working. This also reminds me, I really need to get a chunk of time and update the DragonOS Pi image.
What is the use of the remote ID ? They can only be tracked a relatively short distance and there is no "Drone ATC" that tracks them all in the airspace so what use are they ? I'm hoping someone here can illuminate to me their usefulness beyond being a potential revenue source for the FAA via fines...I watched part of the RDQ invasion of privacy lawsuit unfold and it appeared the judges were fed up with the FAA until the FAA lawyers finally threw out the old "National Security" mantra against our toys being flown in parks..weak..🙄
I’ve managed so far to detect the remote ID over 1km away when it’s the Bt5 Long Range type and that’s with only an 8db small Omni antenna. I suspect it can be received much much further making it likely more relevant.
Like you said though, it’s probably to have something in order to detect if a drone or drones are in unauthorized areas, but only if there’s some device locally there set up to receive. I just think I can extend that range way out for more of a protective measure of sorts.
Sorry for so many split replies. The last thing I was gonna say was I have a spot picked out that’s several miles line of sight which I was going to attempt having a directional antenna and see if I could pick up the remote ID.
@@cemaxecuter7783 More relevant to who and why is the question. If there is no ATC for drones why track them in such a limited fashion? . not a fan...will never comply as I fly alone quite often and have been doing so safely for 40 years now..I don't want local thieves or karens to even know I'm anywhere near them because they used a phone app to track me....All this has done so far is leave the big park I fly at that had 20 flyers at times empty...seems most took up the few available spots at the traitorous AMA clubs ...others flying in different places because they fear being fined for flying toys in such a large venue or given up the hobby altogether..I reckon the field was too crowded anyway..good job FAA/ AMA.. 👎🏼