DragonOS Focal DJI DroneID Capture w/ Gr-DroneID + Gr-Fosphor (b205mini, Nvidia, GR 3.8) part 1

Summary

In this field recording, the operator is testing the GR drone and its ID functionality after updates. Despite facing some technical challenges and the drone's signal jumping intermittently, they persist in trying to capture the ID successfully. The session is marked by a sense of urgency as they race against an impending rainstorm, resulting in a mix of frustration and determination as they work through the process to capture the drone's ID at the right moment.

Takeaways

• 😀 The speaker needs to act quickly due to impending rain.
• 😀 The focus of the session is on a B205 mini device after updates.
• 😀 The GR drone ID appears every 600 milliseconds, which the speaker is tracking.
• 😀 The speaker is trying to find the correct moment in the data stream for recording.
• 😀 The GR drone ID value is fluctuating, making it harder to capture a consistent reading.
• 😀 The speaker believes they found the correct drone ID value at '2429'.
• 😀 There are attempts to start and stop recording multiple times due to the large file size.
• 😀 The speaker keeps trying to locate the right data to capture, sometimes unsure if it's the correct moment.
• 😀 The speaker experiences a brief frustration with the process, leading to multiple overwriting attempts.
• 😀 After multiple attempts, the speaker is confident that they have captured the correct data point.

Q & A

What is the GR drone ID mentioned in the script?

The GR drone ID appears to be an identifier or code that the system uses to track or log data at regular intervals, possibly related to the operation of the drone, occurring approximately every 600 milliseconds.

What is the purpose of the B205 mini mentioned in the transcript?

The B205 mini is a device connected to the system, and its role in this context seems to be related to processing or updating some data for the drone operations.

What does the speaker mention about updates?

The speaker notes that the drone system is being tested or observed after some updates, although the exact nature of the updates isn't detailed in the transcript.

What is the issue the speaker is facing while trying to record data?

The speaker faces difficulties with recording the data, as the system is generating large files quickly, and the process of overwriting or capturing the data is somewhat erratic.

Why does the speaker mention 'rain' at the beginning?

The speaker indicates that the task needs to be completed quickly because rain is imminent, possibly to avoid interference with the recording or operation of the drone.

What does the speaker mean by the drone ID jumping around?

The drone ID seems to fluctuate or change at regular intervals, which could be part of the system's behavior to log or update the ID every 600 milliseconds or so.

How does the speaker try to capture the data effectively?

The speaker attempts to find the right moment to record by testing different intervals and trying to pinpoint the best time to capture the necessary data, sometimes overwriting previous attempts.

What seems to be the desired outcome of this operation?

The goal appears to be to successfully record or capture a specific data point related to the GR drone ID, likely for further analysis or processing.

What does the speaker mean when they say, 'That was probably it'?

The speaker suggests that they have likely captured the correct data, as they identify a moment where the drone ID is likely aligned with the intended point of interest.

What does the speaker hope to achieve by 'getting something better'?

The speaker is trying to improve the quality or accuracy of the data by testing and adjusting their approach, hoping to capture a better result.