PartSync Devlog #0

The Task

PartSync is a database program that automatically imports order CSV files from DigiKey into a local database — so you always know which parts you actually have at home before starting your next project.

Why

Anyone who orders electronics components regularly knows the problem: you buy parts for one project, some leftovers end up in a bin, and a few months later you have no idea what’s actually in stock. PartSync solves this by turning your DigiKey order history into a searchable local inventory.

How it works (so far)

• Backend: Flask + SQLite- DigiKey API v4 integration with full OAuth2 authentication flow- CSV import pipeline that parses DigiKey order exports and matches them against the DigiKey product API to pull full part details (description, datasheet, footprint, etc.)- Local database stores everything so lookups don’t need to hit the API every time

##Progress

• ✅ OAuth2 token flow (including refresh) working end-to-end
• 🔄 CSV import → product detail matching
• 🔄 Search/BOM frontend

Devlog #1 — PCB Layout Complete

The layout is finished.

What’s on the board

The Yoke runs on an STM32G491VE (LQFP100) — enough pins for the touch display, the button matrix, and FDCAN without fighting over alternate functions. The wheel talks to the base over CAN, using the TCAN332G transceiver.

Stackup

Signal / PWR/ GND/ Signal. Nothing exotic, but the ground plane sits directly over the bottom signal layer, which gives every fast signal a clean return path right beneath it.

That mattered most for two things:

• CANH/CANL — routed as a differential pair, tight and short, transceiver right at the connector.
• USB — the two datalines D+, D- are routed as a differential pair, so they need a clean path to ground.

What’s next

Fabrication. Gerbers are generated, BOM is assembled, and the whole project is under Git now. Then assembly, then the part where I find out what I got wrong.

Devlog #0 — Schematic done!

Wrapped up the schematic for the wheel. Key component choices:

• STM32G491VE — picked for the built-in CAN peripheral and the high GPIO count (needed the pins for buttons, encoders, LEDs, and display).
• TCAN332G — CAN transceiver handling the physical layer to the base unit.
• Touch display — shows live driving data right on the wheel (speed, gear, telemetry over CAN).
• Charge pump — lets me hot-plug the wheel into the base without inrush issues.

Next up: PCB routing.

Finished the schematic

What’s New

• Added the functionality of an oscilloscope
  • using the AD9283 ADC clocked at 50 MHz
• Cancelled the DAC (now only signal generation using the AD9833 for sine, square and triangle)
• Added the functionality to choose the voltage of the ISP programmer in software (with hardware safety)

Next Steps

• Double check the schematic
• Start PCB layout

TRACE Update 1

What’s New

• Defined architecture: two MCUs
  • RP2350 handles logic analyzer, programmers and function generation
  • ESP32-S3 handles WiFi, web UI and AI agent
• Selected key components: ADS1115 for voltage measurement,
  AD9833 for function generator, MCP4922 as DAC
• Started KiCad schematic — analog power section with split ground plane done

Interface

• WiFi: access from any device (phone, PC) via web UI
• USB: direct connection to host for PulseView (logic analyzer)
• AI integration: Claude agent to control the instrument
  • Describe your problem in plain language and Claude automatically
    measures and diagnoses it

Next Steps

• Complete ESP32-S3 and RP2350 schematics
• Start PCB layout