Skip to main content

Set Up Your Drone Hardware with an AI Assistant

You can let an AI assistant — ChatGPT, Claude, Gemini or similar — walk you through setting up your MicoAir or Robofusion hardware. The assistant plans the steps and the parameter changes; you do the physical work (plugging in USB or a battery, wiring, holding BOOT) and enter the settings in your ground station. This page gives you one prompt to copy and explains how to get reliable answers.

How it works — you set the goal and do the physical steps, your AI reads the Robofusion docs and plans the changes, you apply them to the flight controller with propellers off

Why point the AI at our docs?

Asked cold, AI assistants answer from memory and web search. For small drone boards that goes wrong in predictable ways: they mix up boards with near-identical names (an H743 V1 manual offered for the V2), and they use parameter names from older firmware — ArduPilot 4.7 renamed many parameters and changed several units from centimetres to metres. Our reference file for AI assistants, docs.robofusion.net/ai/start.md, lists every board's firmware target and board ID, the 4.7 renames, and a link to the verified manual for each product.

Quick start: paste this into your AI​

Fill in the three bracketed parts and paste the whole block into a new chat:

Use https://docs.robofusion.net/ai/start.md as the reference for my hardware,
and open the pages it links for my exact products before answering.

My hardware: [e.g. MicoAir H743 V2 flight controller + LR900-F telemetry radio]
Firmware and version: [e.g. ArduPilot Copter 4.7.1 — if I don't know, tell me where to find it]
What I want to do: [e.g. set up telemetry to Mission Planner on my laptop]

Rules:
- Don't guess product-specific values; if the docs don't cover something, say so.
- Give me one physical step at a time and wait for me to confirm.
- Propellers stay off until you say the setup is complete.
- Show parameter changes as a table (parameter, current value, new value, reboot needed, why)
  for me to enter myself, then help me verify the result.
- Never disable arming checks or failsafes as a fix.

That's all most people need. The rest of this page covers the details that make the difference.

How do I find my exact model and firmware version?​

The model. Use the full product name from your order or the box. Several boards have near-identical names — MicoAir H743 V2, H743 V2 AIO 45A and H743 AIO 35A all need different settings. If you are unsure and the board runs ArduPilot, connect it to Mission Planner: the Messages tab shows the firmware target name as soon as it connects, followed by the board's serial number — for example MicoAir743v2 0031002A 33335110 35353936. Give the assistant that line. (The serial number itself is explained in Flight Controller ID.)

The firmware and version. Mission Planner prints it at the top of the Messages tab as soon as it connects — for example ArduCopter V4.7.1. Other ground stations show it on their vehicle-information or firmware page. The version matters: a setting written for ArduPilot 4.6 can mean something different on 4.7.

Which AI assistants work?​

AssistantWhat to do
ChatGPT (free or paid)Paste the prompt. If it answers without opening the link, reply "Open the link first and read it."
Claude (free or paid)Paste the prompt. Claude opens links you give it and the links inside the page it reads.
GeminiPaste the prompt.
An assistant without web access (some offline or local models)Open the product's manual, add .md to the end of its address (for example docs.robofusion.net/flight-controllers/h743-v2-user-manual.md), save the file and attach it to the chat together with the prompt.
Coding assistants (Claude Code, Cursor and similar)Point them at docs.robofusion.net/llms.txt, which indexes the whole hub.

Every page on this site has a plain Markdown version at the same address plus .md. It holds the same content without the website around it, which is easier for an assistant to read in full.

What the AI can and cannot do​

It can read the manuals and guides, tell you which wires go where, work out the parameter changes for your exact board and firmware version, explain what each setting does, and help you read error messages and pre-arm failures.

It cannot connect to your flight controller. Web and phone assistants run in the provider's cloud; they cannot see a board plugged into your computer, and they cannot see or touch your aircraft. You stay in control of everything that actually changes: you enter the parameters, you plug things in, you decide when to fly.

What a good session looks like​

Here is the shape of a telemetry setup on an H743 V2 with ArduPilot 4.7.1:

  1. The assistant confirms your board and firmware version, then asks you to remove the propellers and connect the flight controller to your computer over USB.

  2. It asks you to read the current settings of the port the radio will use and report them.

  3. It gives you a table like this to enter yourself:

    ParameterCurrentNewRebootWhy
    SERIAL1_PROTOCOL(what you read)2yesMAVLink 2 on the TELEM port
    SERIAL1_BAUD(what you read)57yes57600 baud, the radio's default

  4. It walks you through the wiring (radio TX to the flight controller's RX and RX to TX), one step at a time.

  5. It tells you what success looks like — both radios' LEDs solid, Mission Planner connecting over the radio's COM port — and what to check if it doesn't.

The values in a real session come from the manuals for your hardware; the table above only shows the format.

Safety rules the AI should follow​

  • Propellers off for wiring, configuration, motor tests and the first power-up.
  • Save your current parameters to a file first, so every change can be undone.
  • One change at a time, verified before the next one.
  • No switching off arming checks or failsafes to get past an error. A pre-arm message names the problem — fix the problem.
  • No copied PID or filter values. Tuning is done with AutoTune and the firmware's own tuning guide.
  • Check connector voltages. Some connectors carry 9 V or 12 V (for example the HD video connector). Never connect a 5 V device there.

If an assistant suggests something that breaks one of these rules, stop and ask it why. If you are unsure, ask us.

What if the AI gets something wrong?​

Assistants make mistakes, even with good sources. Two habits catch most of them:

  • Ask for the source. "Which page says that? Quote the line." A value that cannot be traced to a page is a guess.
  • Check the firmware version in the answer. If the assistant uses a parameter your ground station cannot find, it may be using a name from another version. The ArduPilot 4.7 rename table in our reference file covers the common ones.

If you find a mistake in our documentation itself, tell us at support@robofusion.net and we'll correct it.

Written and maintained by the Robofusion engineering team.

Last updated on