A small Discord for log questions

The Discord is where logs get a second pair of eyes, including from people who disagree with the tool. It is deliberately small. There is no bot that posts your analysis, and no automated sharing.

Open the Discord invite

What to post with a question

The header of the log, or the firmware version and PID/filter values.
A short clip of the manoeuvre you are asking about, or the time range in the log.
The symptom: what the quad does, when, and what you already changed.
The report JSON if you have one, minus anything you consider private. It contains no key and no email.

What not to post

A full log with your name, home field or other personal detail visible in the filename.
A licence key, an email address in a screenshot, or a checkout receipt.
“Is this tune good?” without the log. A tune is a hypothesis about one aircraft; without the measurement there is nothing to check.
Complete CLI dumps for someone else's airframe. Paste targets are how a good tune becomes a bad crash.

Rules

Be specific and be kind. “It oscillates at 0 throttle after a hard stop” gets help; “it flies bad” does not.
No self-promotion or affiliate links outside a dedicated thread.
No medical, legal or safety-critical advice. This is a hobby tool for multirotors.
Disagreement about a measurement is welcome and should include the log section that shows it.

Support questions that need a reply from the maintainer go to easyquadtune@outlook.com; Discord is peer help and may be slower.

Easyquadtune is not affiliated with Betaflight. Published 2026-10-21. Measurements come from the maintainer's own flight logs; an example is illustrative of the method, not a tune for your aircraft.