Skip to content

hashgraph-online/awesome-codex-plugins / plugins/aklofas/kicad-happy/skills/emc

EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, shielding, and magnetic leakage from switching inductors. Produces severity-ranked risk report with pre-compliance test plan. Supports FCC Part 15, CISPR 32, CISPR 25 (automotive), MIL-STD-461G. SPICE-enhanced when available. Use when the user asks about EMC, EMI, radiated/conducted emissions, FCC compliance, CE marking, CISPR, ground plane issues, decoupling strategy, clock routing EMC, switching noise, differential pair skew, or whether their board will pass EMC testing. Also for "will this pass FCC?", "check my EMC", "is my ground plane okay?", "check my decoupling", or "generate an EMC test plan".

EMC Pre-Compliance Skill

Automated EMC risk analysis for KiCad PCB designs. Identifies the most common causes of EMC test failures using geometric rule checks, analytical emission formulas, and optional SPICE simulation.

This is a risk analyzer, not a compliance predictor. It catches ~70% of common EMC design mistakes before fabrication. It cannot guarantee FCC/CISPR compliance — only a calibrated measurement in an accredited lab can do that. But it can reduce the first-spin failure rate from ~50% toward ~20-30%, potentially saving $5K-$50K per avoided board respin.

Related Skills

SkillPurpose
kicadSchematic/PCB analysis — produces the analyzer JSON this skill consumes
kicad (thermal)Thermal hotspot analysis — MLCC derating and ferrite/inductor overheating findings can amplify EMC decoupling and filter issues (an over-stressed MLCC degrades; a hot ferrite drifts impedance). Worth cross-checking when EMC flags DC-001/DC-002 or EF-001/EF-002.
spiceSPICE simulation — provides simulator backend for SPICE-enhanced PDN checks

Handoff guidance: Run the kicad skill's analyze_schematic.py and analyze_pcb.py --schematic first — this skill consumes their JSON output. Use --full on the PCB analyzer for best results (enables per-track coordinates for ground plane crossing, edge proximity, and return path checks). During a design review, run EMC analysis after the schematic/PCB analyzers, SPICE simulation, and thermal analysis, then incorporate EMC findings into the report.

Requirements

  • Python 3.10+ — stdlib only, no pip dependencies
  • Schematic analyzer JSON — from analyze_schematic.py --output
  • PCB analyzer JSON — from analyze_pcb.py --full --schematic <sch> --output (recommended with --full)
  • SPICE simulator (optional) — ngspice, LTspice, or Xyce for SPICE-enhanced PDN checks. Auto-detected. Without one, analytical models run unchanged.

Workflow

Step 1: Run the analyzers

python3 <kicad-skill-path>/scripts/analyze_schematic.py design.kicad_sch --analysis-dir analysis/
python3 <kicad-skill-path>/scripts/analyze_pcb.py design.kicad_pcb --full --schematic analysis/<run_id>/schematic.json --analysis-dir analysis/

Step 2: Run EMC analysis

Pass --analysis-dir analysis/ — the script auto-resolves schematic.json and pcb.json from the manifest's current run, and writes emc.json into the same folder so the manifest tracks it.

# Recommended: auto-resolve inputs from the current run
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/

# Equivalent — explicit paths still accepted (and required if you want to
# point at a non-current run or override one input)
python3 <skill-path>/scripts/analyze_emc.py \
    --schematic analysis/<run_id>/schematic.json \
    --pcb analysis/<run_id>/pcb.json \
    --analysis-dir analysis/

# One-off JSON (bypasses the cache)
python3 <skill-path>/scripts/analyze_emc.py --schematic schematic.json --pcb pcb.json --output emc.json

# SPICE-enhanced (improved PDN accuracy)
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/ --spice-enhanced

# Select target standard
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/ --standard cispr-class-b

# Select target market (sets all applicable standards)
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/ --market eu

# Filter by severity (high = error findings only)
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/ --severity high

# Human-readable text output
python3 <skill-path>/scripts/analyze_emc.py --analysis-dir analysis/ --text

Optional: Screen supplied harmonic lines against supplied limits

For spectral lines that are already expressed as RMS dBµV, dBµV/m, or dBµA, use the standalone screen. Levels must be RMS: subtract 3.01 dB from peak-amplitude spectra first. This skill's harmonic_spectrum() gives switch-node source amplitudes, not emission levels, so it is not a valid input without a coupling/path model.

Limit values must come from the user. Build a limit profile only from limit values the user provides, together with their source (for example a standard's edition and table or clause, where applicable), and record that source in source.citation. Never write limit tables from memory or fill in missing bands, detectors, or units; if the user has not supplied limits, ask for them instead of running the screen.

python3 <skill-path>/scripts/analyze_harmonic_limits.py \
  --spectrum harmonic-lines.json \
  --limits limit-profile.json \
  --limit-column peak \
  --output harmonic-limit-screen.json

This command is separate from analyze_emc.py. It does not calculate a spectrum, add an EMC finding, change the risk score, write emc.json, or determine compliance. See Harmonic-Limit Screening for the input schemas and interpretation boundary.

Step 3: Interpret results

Read the JSON report and incorporate findings into the design review. Each finding has a severity, rule ID, description, and actionable recommendation. See "Interpreting Results" below.

What Gets Checked

44 rule IDs across 18 categories. Each rule has a specific threshold, rationale, and source citation — see references/pcb-emc-rules.md for full details.

CategoryRulesWhat it detects
Ground planeGP-001 to GP-005Signal crossing voids or plane splits, zone fragmentation, missing ground planes, low fill ratio, multiple ground domains
DecouplingDC-001 to DC-003Cap too far from IC, IC with no decoupling cap, cap too far from via
I/O filteringIO-001, IO-002Connector without filtering, insufficient ground pins
Switching EMCSW-001 to SW-003Harmonic overlap, switching node copper area, input cap loop area
Clock routingCK-001 to CK-004Clock on outer layer, long trace, clock near connector, no ground pour near a crystal
Via stitchingVS-001Ground via spacing exceeds λ/20 at highest frequency
StackupSU-001 to SU-003Adjacent signal layers, signal far from reference plane, thin interplane capacitance
Diff pairDP-001 to DP-004Intra-pair skew vs protocol limits, CM radiation, reference plane change, outer layer routing
Board edgeBE-001 to BE-003Signal near edge, incomplete ground pour ring, connector area stitching
PDN impedancePD-001 to PD-004Anti-resonance peaks, distributed rail impedance at IC load points, cross-rail coupling from downstream switching regulators
Return pathRP-001Layer transition via without nearby ground stitching via
CrosstalkXT-0013H spacing violation, aggressor-victim pairs
EMI filterEF-001, EF-002Filter cutoff too close to switching frequency (analytical)
ESD pathES-001, ES-002TVS too far from connector, insufficient ground vias near TVS
Thermal-EMCTH-001, TH-002MLCC DC bias derating (SRF shift), ferrite near heat source
ShieldingSH-001Connector aperture slot resonance near emission source
Emission estimatesEE-001, EE-002Board cavity resonance, switching harmonic envelope
Inductor leakageML-001Unshielded or unknown-shielding switching inductor within 15 mm of an ADC, op-amp, crystal or RF part

Advisory outputs (not findings):

  • Pre-compliance test plan — frequency band prioritization, interface risk ranking, near-field probe points
  • Regulatory coverage — market-to-standards mapping, coverage matrix (what the tool checks vs what requires lab testing)

Output Format

{
  "summary": {
    "total_findings": 27, "categories_checked": 12,
    "active": 27, "suppressed": 0,
    "by_severity": {"error": 2, "warning": 10, "info": 15},
    "emc_risk_score": 73
  },
  "target_standard": "fcc-class-b",
  "findings": [
    {
      "category": "ground_plane",
      "severity": "error",
      "rule_id": "GP-001",
      "summary": "Signal crosses ground plane void",
      "description": "Net SPI_CLK crosses a 3.2mm gap in GND on In1.Cu",
      "components": ["U3", "U7"],
      "nets": ["SPI_CLK"],
      "recommendation": "Route around the gap, or fill the void"
    }
  ],
  "per_net_scores": [
    {"net": "SPI_CLK", "score": 79, "finding_count": 3, "rules": ["GP-001", "CK-001", "BE-001"]}
  ],
  "test_plan": {
    "frequency_bands": [{"band": "30-88 MHz", "risk_level": "high", "source_count": 12}],
    "interface_risks": [{"connector": "J1", "protocol": "USB", "risk_score": 8}],
    "probe_points": [{"ref": "L1", "x": 45.2, "y": 32.1, "reason": "switching inductor"}]
  },
  "regulatory_coverage": {
    "market": "us",
    "applicable_standards": ["FCC Part 15 Class B"],
    "coverage_matrix": [{"standard": "...", "coverage": "partial", "note": "..."}]
  }
}

Severity Levels

SeverityMeaningAction
errorLikely to cause an EMC failureFix before fabrication
warningMay cause issues depending on specificsReview and assess
infoInformational — frequencies, estimates, good practiceUseful for lab prep

--severity takes error, warning or info, or the older five-level names: critical and high keep error findings, medium keeps error and warning, low and all keep everything.

Risk Score

Each rule ID contributes at most 3 findings to the score (worst severity first). This prevents per-net rules like GP-001 from saturating the score on 2-layer boards. All findings are still reported — only the score is capped.

penalty = sum(severity weight × confidence weight, worst 3 per rule), score = max(0, min(100, 100 - penalty)); weights error 12, warning 3, info 0; heuristic findings count half. 0 is worst and 100 best, and the score can be fractional. It covers every unsuppressed finding; --severity only filters the emitted list. Scores below 50 indicate significant EMC risk.

Interpreting Results

Ground plane findings — Any error finding (signal crossing a void) is almost always a real problem. Fix unconditionally.

Decoupling findings — Distance-based findings have moderate false positive rates. A cap at 6mm may be fine for a low-speed IC but problematic for a 100MHz clock buffer. Use frequency context to prioritize.

I/O filtering — Highly relevant for cable-connected products. For board-to-board connections inside an enclosure, the risk is lower.

Diff pair findings — Protocol-specific skew limits are well-defined. USB HS (25ps, when the part is known to be high-speed; other USB pairs get the full-speed budget), PCIe (5ps), Ethernet (50ps). Findings exceeding these limits are real issues.

PDN findings — Anti-resonance peaks are real and cause voltage droop. SPICE-verified findings are more accurate than analytical. If a peak is flagged, add a capacitor with SRF near the peak frequency.

Emission estimates — Order-of-magnitude estimates (±10-20 dB). Use them to prioritize frequency bands for pre-compliance testing, not to predict pass/fail.

EMC Standards

StandardFlagUse Case
FCC Part 15 Class Bfcc-class-bUS residential (default)
FCC Part 15 Class Afcc-class-aUS commercial/industrial
CISPR 32 Class Bcispr-class-bInternational (EU CE marking)
CISPR 32 Class Acispr-class-aInternational commercial
CISPR 25 Class 5cispr-25Automotive (strictest)
MIL-STD-461G RE102mil-std-461Military/defense

The --market flag maps markets to all applicable standards: us, eu, automotive, medical, military.

Limitations

  • Cannot predict absolute emission levels better than ±10-20 dB
  • Cannot account for enclosure effects (shielding, apertures, seams)
  • Cannot predict cable radiation without knowing external cable routing
  • Cannot replace full-wave simulation for complex geometries
  • Cannot guarantee compliance — only accredited lab measurement can
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexUnverifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexUnverifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexUnverifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall