Pulse Induction Metal Detector PCB Design
Proceed with final stabilization of the PCB design:
- Grounding and validation:
- Fix all grounding issues and enforce a strict single star-ground topology at the 12V input only
- Ensure complete separation of analog, digital, and power return paths with no unintended coupling
- Rerun full ERC and DRC after grounding corrections and resolve all remaining violations
- Component placement:
- Place the Arduino Nano centrally between the analog front-end (TL072 + LM393) and the power driver section (TC4420 + IRF3205 + coil)
- Maintain clear physical separation between analog and power domains to minimize electromagnetic coupling
- Power integrity:
- Add bulk capacitors for each power domain:
- Analog domain: 10µF–47µF low-noise capacitor
- Digital domain: 10µF–47µF capacitor near Arduino Nano
- Power domain: 100µF–470µF near coil driver input
- Ensure each bulk capacitor is placed close to its respective power entry point
- Final review:
- Re-check decoupling placement (100nF at every IC power pin)
- Verify no routing crosses between analog and power zones
- Confirm coil driver loop remains minimal and isolated
Only proceed to final Gerber, BOM, and Pick-and-Place generation after all checks pass successfully.
Thought for 59 sec
I've made a plan, and started work on it.
Fix grounding and checks
Place MCU between domains
Add bulk capacitors
No schematic yet
Talk to Flux to get started.
Refine this doc
Ask about this doc
PCB Improvement Requirements Capture Plan
Objective
Capture and formalize the requested PCB improvement requirements for the current Pulse Induction Metal Detector project before any schematic or layout changes are made.
Requested Changes to Capture
- Add 12V reverse-polarity protection at the input.
- Add a 2A input fuse at the power entry.
- Increase PCB size to 120 mm × 80 mm.
- Require a minimum 3 mm trace width for coil-current and power-switching paths.
- Enforce strict physical and routing isolation between the analog section and the power-switching section.
- Maintain separate analog and power grounds, joined only at a single defined star point.
High-Level Execution Plan
1. Baseline review and scope confirmation
- Confirm the current project revision and identify which existing power-entry, coil-drive, analog front-end, and grounding structures are already present.
- Define the exact scope of this update as a PCB improvement pass, not a functional redesign unless new constraints are discovered.
- Record any assumptions that must be validated before changes proceed.
2. Power-entry protection requirements capture
- Define the input power-entry requirement set around 12V operation.
- Record the need for reverse-polarity protection at the board input.
- Record the requirement for a 2A input fuse and clarify whether it is intended as system protection, wiring protection, or both.
- Capture any acceptance criteria for normal operation, fault handling, and serviceability at the input stage.
3. Board envelope and mechanical requirements capture
- Record the new target board size as 120 mm × 80 mm.
- Confirm whether this is a hard maximum, nominal target, or fixed final outline.
- Capture any implications for mounting, connector placement, coil interface location, enclosure fit, and keepout areas that may be affected by the larger board.
4. High-current path requirements capture
- Identify all nets that belong to coil current and power-switching paths.
- Record the minimum trace-width requirement of 3 mm for those paths.
- Capture whether this rule applies universally to the full current path or only to specific trunk segments.
- Record any related current, pulse, thermal, copper-weight, or allowable voltage-drop constraints that determine whether 3 mm is sufficient.
5. Analog/power partitioning requirements capture
- Define which circuits belong to the analog section and which belong to the power-switching section.
- Record the requirement that these sections remain strictly isolated in placement and routing intent.
- Capture any required separation goals for noisy nodes, switching loops, sense paths, and sensitive analog measurement paths.
- Record the need to preserve signal integrity and noise immunity as the main purpose of this partitioning.
6. Grounding architecture requirements capture
- Define the analog ground domain and the power ground domain explicitly.
- Record the requirement that these grounds remain separated throughout the layout except at one intentional star-point connection.
- Capture where that star-point should be defined from a system perspective (for example, around the measurement reference or input return strategy) without yet choosing an implementation.
- Record any review criteria needed to verify that no unintended secondary ground ties are introduced.
7. Review and sign-off criteria capture
- Convert the above requests into formal, reviewable PCB requirements.
- Identify open questions that must be resolved before implementation begins.
- Establish a requirement-review checkpoint so the user can approve the captured constraints before schematic or PCB edits are made.
Deliverable from This Planning Step
A reviewed requirements set that clearly defines:
- input protection expectations,
- the new board size,
- high-current trace-width constraints,
- analog versus power-switching partition boundaries, and
- the single-point grounding strategy.
Open Questions to Resolve During Requirements Capture
- Is 12V the nominal input, maximum input, or both?
- Should the 2A fuse be fast-blow, slow-blow, resettable, or left open for later selection?
- Which exact nets count as coil-current and power-switching paths?
- Is 120 mm × 80 mm a fixed outline or a maximum allowed size?
- Which circuits are explicitly classified as analog versus power-switching in this design?
- Where should the star-ground reference be defined at the system level?
Objective
Requested Changes to Capture
High-Level Execution Plan
1. Baseline review and scope confirmation
2. Power-entry protection requirements capture
3. Board envelope and mechanical requirements capture
4. High-current path requirements capture
5. Analog/power partitioning requirements capture
6. Grounding architecture requirements capture
7. Review and sign-off criteria capture
Deliverable from This Planning Step
Open Questions to Resolve During Requirements Capture
