AT219 Remote ID Fact Check (Lab 1)

 Michael Holland


Introduction

Remote ID is a technology that broadcasts the drone's location, altitude, and identity. This allows other people to see where the drone is. There are three methods for complying. The first method is Standard Remote ID, which is where the Remote ID is broadcast as a part of the drone's hardware and software. In other words, it is "built-in". The second method of compliance if you have a drone without Standard RID is to buy a separate module that you can attach to the drone. This is called a "broadcast module". The third method is for drones without Remote ID. You can operate one of these drones in an FAA- Recognized Identification Area, which is an area exempt from the Remote ID requirements.


Verify DJI Mavic 2 Pro is RID Compliant

The FAA has a Declaration of Compliance page with a list of all Remote ID aircraft that have been officially approved by the FAA. This list contained the Mavic 2 Pro which means the FAA has verified that it is in compliance with the Remote ID requirements.


This aircraft is in compliance with the Remote ID requirements using standard Remote ID because it is built into the firmware and is not an external broadcaster.

According to 14 CFR 89.305, the standard remote ID must broadcast the identity including serial number, session ID, latitude and longitude of control station, geometric altitude of control station, latitude and longitude of unmanned aircraft, geometric altitude of unmanned aircraft, velocity of unmanned aircraft, time mark of position source output, and an indication of emergency status of aircraft.

The aircraft firmware is 1.00.0797 which is the most up-to-date version. The Remote ID was implemented in version 1.00.0796.

The first drone we connected to was not showing a Remote ID status check, so we connected another DJI Mavic 2 Pro, and in the overall status section, it told us that the Remote ID was functional.


Test the M2P RID

To test the Remote ID of the drone, we downloaded the Drone Scanner app. We took our DJI Mavic 2 Pro outside and started the motors. We were able to see the drone on the app, meaning that the remote ID was working. 

There was a caveat though. The Drone Scanner app would only work if it was on an Android device. This does not work on Apple devices since IOS, their software, is only compatible with Bluetooth and not Wi-Fi. Since remote ID functions off of a Wi-Fi broadcast, the IOS software cannot see it.


Flying the M2P

To test the remote ID, we conducted a simulated flight. This meant we started the motors without the propellers attached and held the drone in the air so that it would broadcast its remote ID. There were no Temporary Flight Restrictions in the area, and the Lafayette Airport METAR included:

-KLAF 081654Z 13005KT 10SM CLR 03/M02 A3025 RMK AO2 SLP249 T00281017

-KLAF is the airport

-081654Z means it was the 8th day of the month at 1654 UTC time

-The wind was out of the southeast at 5 knots

-Visibility was 10 statue miles

-The sky was clear

-The temperature at the airport was 3 degrees Celcius and the dewpoint was negative 2 Celcius

-The air pressure was 30.25 inches of mercury at sea level, which was 249 millibars.


The following screenshots show the remote ID data from our "flight". This data was displayed on the Drone Scanner App.











Comments

Post a Comment

Popular posts from this blog

UAS Teardown: 3D printed Motor Mount Final Product

Image
 After taking apart the drone, we needed to build a new motor arm for one of the motor mounts that had snapped. To do this we took measurements of hole sizes and locations, and distances for the motor, and then created a hand sketch of a motor arm. After completing the hand sketches we created a CAD drawing on NX. We used this CAD drawing, got peer feedback, and revised it.  After we were sure the CAD drawing would turn out well, well we sent it to a software called CURA. CURA is a splicing software that would help us 3D print our part. We 3D printed our part using PLA material and tested it on our arm, which turned out very well. Pictures of the finished product are included below. The only thing that didn't work out well with our design was that the mounting screws on the arm could not go all the way through the arm and out the other side due to a lack of holes on the bottom. The screw was still able to hold on the mount firmly, but if it were subject to vibrations, the scre...
Read more

Criminal Location Search (AT309 Week 11)

Image
In this lab, our lab groups met at the Boys and Girls Club in Lafayette to conduct a hostage mission. By the time my group was scheduled to arrive, we had moved our operation outside. The purpose of this lab is to test the capabilities of completing search and rescue work with a drone. We had one person flying the drone trying to locate hostages in high visibility vests, and the other partner would follow the drone, being a visual observer. We found this activity to be relatively unsuccessful because it was time-consuming and the visual observation would spot the participants hiding well before the drone could. It was also taking place in a very confined area. By the time my group was conducting the mission, we had started hanging the vests up in the trees and we had to take a picture when we found them. Figure 1 shows an example of finding the vest in the trees. Figure 1- Vest Location
Read more

AT209 Lab 5 Wind Speed vs Battery Life Measurement

Image
In this lab, we used Mavic 2 Pro drones at different altitudes to conduct measurements on wind speed by comparing battery life of the drones hovering in place. Methods: The first step in this lab was to gather our supplies. The class members in lab got partners, and each partner group got a Mavic 2 Pro drone, landing pad, and two or more fully charged batteries from the Purdue Dispatch Center. We then headed to coordinates 40.44364180047488, -87.03272783607103. We set up the drones with landing pads in a row, spaced 5 meters apart. We each had different assigned altitudes so we lined up in order of increasing altitude, south to north. The altitudes for all of the partner groups were 3m, 25m, 50m, 75m, 100m, and 121m. My partner and I flew at 75m AGL. We set up and pre-flighted the drones on one battery, and when everyone was ready, we switched the batteries to a new fully charged one and started up at the same time. We then all took off and flew to our assigned altitudes while facing t...
Read more