# Dev-Kit Documentation

**URL:** https://dao.arrowair.com/t/dev-kit-documentation/143
**Category:** Engineering
**Tags:** draft, discussion
**Created:** [December 3, 2025, 3:51pm UTC](https://dao.arrowair.com/t/dev-kit-documentation/143 "2025-12-03T15:51:02Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![errrks.eth](https://yyz2.discourse-cdn.com/flex004/user_avatar/dao.arrowair.com/errrks.eth/32/11_2.png) [@errrks.eth](https://dao.arrowair.com/u/errrks.eth)
#### Post date: [December 3, 2025, 3:51pm UTC](https://dao.arrowair.com/t/dev-kit-documentation/143/1 "2025-12-03T15:51:02Z")

</div>

I am starting this forum post to begin collecting ideas on feedback for the multiple documents that will accompany the dev kit launch. I have a loose structure in mind but we can add or remove to this list. Please let me know your thoughts and I will update the post with any suggestions!

# Engineering Report

- System architecture

- Mechanical design

- Propulsion and Power

- Avionics & sensors

- Performance metrics

- Reliability

# Manufacturing Guide

- General assembly guide

- PCB assembly

- Wiring

- Structural Assembly

- Enclosure printing

- Final integration

- Tools required

- Links to CAD files

- recommended suppliers

- Master BOM

# Pilot’s Guide

- safety & compliance

- system setup

- Power up procedure

- Emergency procedures

- Pre flight check list

- Post flight check list

- Flight tracking platform

# Developer guide

- Attachment interface

- Communication protocols

- RPI 5 SDK

- clarify power budget for 12V and 5V

# Maintenance Guide

- instruction on how to clean and store

- inspecting propellers

- torque check on critical screws after x hours of operation

- how to spot deformations

---

<div class="post-metadata">

### Author: ![Alexander\_Dada](https://yyz2.discourse-cdn.com/flex004/user_avatar/dao.arrowair.com/alexander_dada/32/7_2.png) [@Alexander\_Dada](https://dao.arrowair.com/u/Alexander_Dada)
#### Post date: [December 16, 2025, 5:05pm UTC](https://dao.arrowair.com/t/dev-kit-documentation/143/2 "2025-12-16T17:05:49Z")

</div>

Could add in Systems Requirements, Networking (Ethernet, CAN, and 5G network configurations), and Regulatory Compliance (Targets) Sections to the Engineering report.

---

<div class="post-metadata">

### Author: ![ZeynepB](https://yyz2.discourse-cdn.com/flex004/user_avatar/dao.arrowair.com/zeynepb/32/257_2.png) [@ZeynepB](https://dao.arrowair.com/u/ZeynepB)
#### Post date: [December 22, 2025, 4:48pm UTC](https://dao.arrowair.com/t/dev-kit-documentation/143/3 "2025-12-22T16:48:15Z")

</div>

We can add some software related parts to the guide for a more comprehensive approach. Some headlines may already cover these but I wanted to add these explicitly so that we won’t forget:

- I don’t think we need to add all the control system related stuff in Ardupilot but a simple overview with relevant parameters can be helpful. Also we need to add links to our firmware version on Github, changelog and the latest version information.
- We will ship the drone calibrated but a re-calibration might be necessary from time to time. We can add a calibration procedure for this (or at least link to the related part on Ardupilot documentation)
- Some info on enabling RTK (and the user’s options on this) can be helpful.
- Remote ID module setup would be necessary.
- A troubleshooting part for the operator would be great for the common problems. Also some information on how to recover if pixhawk stuck in a reboot cycle or something like that.
- We may need to add some limitations on payload design for safety (not only weight but also size, inertia etc.)
