# Getting Started

## Drone Hardware Stack

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2Fs8CJrrg3RuHFlKxEgZ0n%2FStillRender_02_v01.png?alt=media&#x26;token=84107efc-756d-43b9-b5e1-b8592b3a234e" alt=""><figcaption><p>F-11</p></figcaption></figure>

The F-11 brings the power of Nvidia GPUs to the sky, enabling a full machine learning stack in flight. The onboard Jetson is capable of lightning fast computation for large workloads, paving the way for [large-scale machine learning aerial applications.](https://docs.flybydev.com/quickstart/capabilities#large-scale-object-detection)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2FxBlhgZwc92tDwHdbtHpD%2Fwaldo.png?alt=media&#x26;token=733c60ff-d92e-42a6-a812-d3d9c598ae45" alt="" width="563"><figcaption><p><a href="https://github.com/stephansturges/WALDO">https://github.com/stephansturges/WALDO</a></p></figcaption></figure>

The main hardware components that are packaged with the drone are the onboard computer, the flight controller, the radio, and the drone controller. In the F-11, these components are as follows:

* Nvidia Orin NX onboard computer (F-11 H/D/S)(Sinlge by default, dual Orin on custom order)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2FG4Qd7FMXCDpDygfIif31%2Forin%20nx.jpeg?alt=media&#x26;token=773b8821-dbcd-4761-8fb6-cb4a922548be" alt=""><figcaption><p><a href="https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-orin/">https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-orin/</a></p></figcaption></figure>

* A CubePilot Cube flight controller (F-11 H/D/S)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2FygEcWYOhDf9Ygy2x84OQ%2Fcubepilot_cube_orangeplus_standard_set.CHEoULJg.jpg?alt=media&#x26;token=479e0400-8fb4-453a-a40c-31385a78fef0" alt="" width="375"><figcaption><p><a href="https://docs.px4.io/main/en/flight_controller/cubepilot_cube_orangeplus.html">https://docs.px4.io/main/en/flight_controller/cubepilot_cube_orangeplus.html</a></p></figcaption></figure>

* Herelink Airunit radio (F-11 H)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2FRternc82NvLtHSCqHGCA%2Fairunit.webp?alt=media&#x26;token=91aff617-56e8-453f-a582-f9e0de5c48c7" alt="" width="375"><figcaption><p><a href="https://irlock.com/products/herelink-blue-air-unit-v1-1">https://irlock.com/products/herelink-blue-air-unit-v1-1</a></p></figcaption></figure>

* Herelink radio controller (F-11 H)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2Ft8LCBFSg9hzZYYhCVohG%2Fradio%20controller.webp?alt=media&#x26;token=c668fbef-3bca-49a1-88b6-156b9be6a584" alt="" width="525"><figcaption><p><a href="https://nwblue.com/products/herelink-blue-v1-1">https://nwblue.com/products/herelink-blue-v1-1</a></p></figcaption></figure>

* Doodlelabs radio (F-11 D)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2F0d5SLfujaZ4CzuQSUcE6%2Fdoodlelabs.png?alt=media&#x26;token=8f694861-0f78-4e1f-98f6-8d4e9f7f3188" alt="" width="372"><figcaption><p><a href="https://doodlelabs.com/aerial-systems/">https://doodlelabs.com/aerial-systems/</a></p></figcaption></figure>

* Silvus 5200 EW-jam resistant radio (F-11 S)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2FYSBRvLAcIzKfdMUze2BD%2FSilvus_Technologies_StreamCaster_LITE_5200.jpg?alt=media&#x26;token=874c2ea7-3db7-433d-bd03-bc4f1a939696" alt="" width="338"><figcaption></figcaption></figure>

* UXV SRoC (F-11 D/S)

<figure><img src="https://4058622452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKvWvYXOlsubeGgyxYP6E%2Fuploads%2Favyn7gdaQBiDypU1KOa1%2FSRoC.webp?alt=media&#x26;token=18f2bb8a-85cc-462c-9bb1-4f73afc64f7e" alt=""><figcaption><p><a href="https://www.uxvtechnologies.com/ground-control-stations/sroc">https://www.uxvtechnologies.com/ground-control-stations/</a>sroc</p></figcaption></figure>

## Booting Up

The drone batteries should be between 39.6V and 50.4V, and should be monitored periodically during use. The drone may take some time to boot up all of its components, which occur at various times depending on the payload. When booting up, the flight controller is likely to boot up first, and should be reflected in the drone controller showing a connected status. The FPV camera should boot up relatively quickly after, and should start displaying its feed on the drone controller, all within the first minute from turning on. If there are other cameras connected, they should display their stream on the controller as soon as they finish loading.

When developing on the drone and/or accessing the drone, be sure to kill the motors if the propellers are attached.&#x20;

## Accessing the Onboard Jetson

The onboard computer can be accessed via SSH. The default IP is `192.168.35.1` with a default user `flyby` and password `flyby`. Refer to [network](https://docs.flybydev.com/quickstart/network "mention") for more information. The access point for this conection is the ethernet port at the top of the drone, as shown in the [top drone diagram](https://docs.flybydev.com/quickstart/hardware-connectivity#external-peripherals).
