Raspberry Pi LiDAR Scanner HAT

flux

0:00

I confirmed the board is still 65mm × 56mm on a 2-layer stackup, with 68 airwires and 49 overlapping-copper findings. I’m first tightening placement to remove footprint/copper conflicts and open routing corridors while preserving the required connector edge locations.
2 days

Placed components

5:33

Placed 40 component(s): TP4, TP2, C7, TP1, R5, D2, TP3, R11, R2, TP5, R1, R15, LED1, U3, R12, J4, C12, D1, J6, R10, F1, R9, R13, TP6, C9, C14, R7, R3, TP7, C13, U1, U2, TP8, C10, R8, LED2, R14, C11, C8, R6

2 days

flux

0:04

Work done
  • Reviewed the PCB DRC state for airwires, overlapping copper, floating copper, and missing footprints.
  • Preserved the required 65 mm × 56 mm, 2-layer board constraints and ran a placement cleanup pass to improve routing corridors while keeping the functional connector grouping.
  • Documented the verified status in Routing Cleanup Status.
Success criteria review
  • ✅ Board size and 2-layer stackup preserved.
  • ✅ Connector/functional grouping intent preserved during placement cleanup.
  • ✅ Missing footprints are not blocking.
  • ❌ Airwires are not cleared: 68 remain.
  • ❌ Overlapping copper is not cleared: 52 remain.
  • ❌ Floating copper is not cleared: 1 via-related issue remains.
Next steps
Use the PCB editor routing workflow to route the remaining nets with the existing width rules (MOTOR 1.0 mm, POWER 0.5 mm, SIGNAL 0.25 mm), then rework/delete the floating via/route conflict and rerun DRC before Gerber release.
Show overlap locations
List remaining airwires
Find floating via
Check critical nets
Export DRC report
2 days
Sign up to send

Refine this doc
Ask about this doc
Raspberry Pi LiDAR Scanner HAT Validation Punch List
Summary
Validation and implementation work was performed for the Raspberry Pi 4/5 LiDAR scanner HAT. Schematic connectivity, component metadata, UART separation, board setup, layout rules, and manufacturing checks were updated and reviewed.
1. Schematic corrections completed
  1. Separated UART assignments:
    • TFmini-Plus LiDAR is on Raspberry Pi UART0:
      • UART0_TX_GPIO14 from J1:GPIO 14 through R8 to LIDAR_RX / J2:4.
      • UART0_RX_GPIO15 from J1:GPIO 15 through R7 from LIDAR_TX / J2:3.
    • TMC2209 is on a separate dedicated UART pair:
      • TMC_UART1_TX_GPIO12 from J1:GPIO 12 to R2:P1.
      • TMC_UART1_PDN_RX_GPIO13 joins R2:P2, J1:GPIO 13, and U1:PDN_UART.
  2. Confirmed TMC2209 single-wire UART topology with R2=1kΩ series resistor between Pi TX and PDN_UART; RX is connected directly to the single-wire node.
  3. Cleaned debug header naming:
    • DEBUG_TX_FROM_UART0 is the post-R9 debug TX stub to J6:1.
    • DEBUG_RX_TO_UART0 is the post-R10 debug RX stub from J6:2.
  4. MPU-6050 IMU wiring verified:
    • I2C_SDA: J1:GPIO2, R5, U2:SDA.
    • I2C_SCL: J1:GPIO3, R6, U2:SCL.
    • IMU_INT: U2:INT to J1:GPIO25.
    • U2:VIN on 3V3, U2:GND on GND.
  5. Power rails verified:
    • USB-C 5V path to fuse/protection and AMS1117 VIN.
    • LIDAR_5V_PROTECTED to TFmini connector J2:2 via fuse output.
    • VM 12V motor input rail to TMC2209 VM pins and bulk capacitance.
    • 3V3 rail from AMS1117 output to logic, Pi 3V3 header, IMU, and TMC2209 VCC_IO.
2. Component and datasheet validation completed
  1. TMC2209:
    • Single-wire UART support implemented with 1kΩ series TX resistor (R2).
  2. Sense resistors:
    • R3 and R15 set to 0.11Ω, 1%, 0.5W, package metadata SMD_0805_2012Metric.
    • Selected MPN: YAGEO PE0805FRF7T0R11L.
    • LCSC part number: C7326940.
  3. TFmini-Plus connector:
    • J2 is JST SM04B-GHS-TB(LF)(SN), LCSC C189895.
    • Intended pin order documented as: 1=GND, 2=5V/LIDAR_PWR, 3=LiDAR TX to Pi UART0 RX, 4=LiDAR RX from Pi UART0 TX.
    • Connector current rating metadata is 1A, adequate for TFmini-Plus 5V load.
  4. AMS1117-3.3 decoupling:
    • C10=100uF, C11=10uF, and C12=100nF are connected from 3V3 to GND.
  5. BOM metadata:
    • J1 assigned Adafruit MPN 2222.
    • TP1 through TP8 assigned Keystone Electronics MPN 5019.
3. PCB layout configuration completed
  1. Board size configured as 65mm x 56mm.
  2. Stackup configured as Standard 2 Layer:
    • Top copper: 0.035mm copper.
    • Bottom copper: 0.035mm copper.
    • Total thickness: 1.50mm.
    • This corresponds to standard 1oz copper on a 2-layer PCB.
  3. Net width rules applied:
    • MOTOR nets: 1.0mm trace width.
    • POWER nets: 0.5mm trace width.
    • SIGNAL nets: 0.25mm trace width.
  4. Ground fill setup:
    • GND net configured for all connected layers with fill stitching density set to 10mm.
  5. Placement pass completed and then re-optimized:
    • Connectors placed on board edges.
    • U1/TMC2209 support parts grouped nearby.
    • Decoupling/bulk caps constrained near associated power pins where possible.
    • Follow-up placement reduced physical crowding and improved component spacing while keeping all components on the top layer.
4. Review results
  1. ERC status: PASS for selected categories:
    • Driver conflicts: pass.
    • Floating pins: pass.
    • Missing power: pass.
    • Single-pin nets: pass.
    • Undriven nets: pass.
  2. Footprints: PASS for missing-footprint check.
  3. Manufacturing metadata:
    • Previously missing MPNs for J1 and TP1-TP8 were filled.
  4. DRC status: NOT CLEAN.
    • Remaining overlapping copper errors: 49.
    • Remaining airwire/unrouted errors: 68.
    • These must be resolved before fabrication.
5. Remaining blockers before fabrication
  1. Complete routing until all 68 airwires are cleared.
  2. Resolve 49 overlapping-copper DRC errors.
  3. Re-run full DRC after routing and copper cleanup.
  4. Visually verify the JST-GH keyed connector orientation and cable pin order before ordering; schematic intent is documented but keyed cable direction should be checked against the exact harness.
  5. Re-export Gerbers only after DRC is clean; the current generated Gerber archive is for inspection only, not release.
6. Gerber export notes
A Gerber ZIP was generated for inspection. Required 2-layer fabrication outputs should include:
  1. Top copper .GTL.
  2. Bottom copper .GBL.
  3. Top solder mask .GTS.
  4. Bottom solder mask .GBS.
  5. Top silkscreen .GTO.
  6. Bottom silkscreen .GBO if bottom markings exist.
  7. Board outline / edge cuts .GKO or .GM1.
  8. Excellon drill files for PTH/NPTH holes.
Because DRC still reports overlapping copper and airwires, the exported package must not be treated as manufacturer-ready until these errors are resolved.

    Summary

    1. Schematic corrections completed

    2. Component and datasheet validation completed

    3. PCB layout configuration completed

    4. Review results

    5. Remaining blockers before fabrication

    6. Gerber export notes

Documents

    Raspberry Pi LiDAR Scanner HAT Validation Punch List

    Routing Cleanup Status

    Scary Aquamarine Scramble Suit — Raspberry Pi LiDAR Scanner HAT

Assets

No assets added.

Scary Aquamarine Scramble Suit 3580

Scary Aquamarine Scramble Suit 3580 thumbnail
Scary Aquamarine Scramble Suit — Raspberry Pi LiDAR Scanner HAT with TFmini-Plus UART, TMC2209 stepper drive, MPU-6050 IMU, USB-C 5V input, 12V motor input, debug header, LEDs, and test points for indoor 360° obstacle mapping.

Properties

Properties describe core aspects of the project.

Pricing & Availability

Distributor

Qty 1

Arrow

$4.74–$74.84

Digi-Key

$4.64–$179.75

LCSC

$8.03–$8.79

Mouser

$12.54–$132.15

TME

$1.36

Verical

$2.09–$29.27

Controls