Contact

Send a message

Reporting a false positive

Every rule is a heuristic, and real designs do clever things. If a finding is wrong for your board, the fastest way to get the rule fixed is a report with:

• The rule id shown under "About this check" (for example esp32.strapping). The "Report a false positive" link under each finding fills it in for you.
• The parts involved as the finding lists them, and the part numbers (for example "U3, an AP2112K-3.3").
• What the circuit is meant to do, and why the finding does not apply.

Please do not paste confidential design data. The checker never sends your file, and you do not need to send it either; a short description is usually enough. If an excerpt would help, you will be asked for it and can decide then.

Before you write: three quick checks

• Did you export the KiCad format? The XML and OrcadPCB2 netlists are different files; the checker explains which one it received.
• Did you drop every sheet? For hierarchical schematics, select all .kicad_sch files together, or export a netlist from the root sheet.
• Is the design annotated? References like R? make findings hard to act on. Annotate, export again and re-run.

A file that will not load

Tell us the KiCad version that saved the file, whether it is a netlist (.net) or a schematic (.kicad_sch), and the exact message the checker showed. For schematics, mention whether the project uses hierarchical sheets or buses. Exporting a netlist (File > Export > Netlist, KiCad format) usually works around schematic-reading problems while we fix them - see how to export a netlist.

Rule ideas

The best rule requests describe a mistake that actually cost someone a board spin, which parts it affects and where the requirement is documented (a datasheet section, an application note, a hardware design guideline). Rules need a primary source and a way to detect the problem from a netlist without too many false alarms.

Human reviews

To request a review, use the form on the pricing page - it asks for the details needed to quote. Use this form for questions before you decide.

Corrections to the guides

The guides summarise vendor documents, and vendors revise them. If you spot a value or recommendation that disagrees with the current datasheet or application note, send the document name, revision and section. Corrections are checked against the source and fixed quickly, and the rule that depends on them is updated too.

Security issues

If you find a way for this site to leak data or run untrusted code - for example a crafted KiCad file that injects markup into the results - please report it here with steps to reproduce. The checker treats every string from your file as plain text, and reports like this are taken seriously.

What happens to your message

Messages are read by a person, not a bot. Your email address is used only to reply; it is not added to a newsletter or shared. If you want a past message deleted, say so and it will be removed.

Response times

Messages are usually answered within two business days. Review requests get a reply with a payment link and a delivery date within 24 hours.