I'll start by saying I have zero experience/knowledge on how to do any circuit hardware design nor software programming skills. If it ain't GUI driven or WYSIWYG, then I lose interest real quick.
However I've had idea's in my head on cool shit i'd like to have made for years, but being niche products or low volume sales potential, it's never been worth pursuing. So with a abundance of time & money to potentially burn & having lots of success on the programming code side of things I thought i'd give Claude the job of making me some PCB boards.
Software wise I'm using Claude Desktop, Kicad 10.0, OpenScad.
Project 1:
First board to get made was what i call the "Mini Expander Board".
It was effectively a test case to add an ESP32 device & analog break out signals by plugging into the Riverdi's 40 pin, 1.27mm expansion header & breaking them out to 2.5mm pins along with using a 20 pin FFC, both ports provide SPI interfaces to relevant sub modules & work as a pass through of power & can signals via molex connector to the displays original Picoblade connectors (tiny bastards!).## What the board does
A daughterboard for a Riverdi 7″ STM32H7 display, plugging onto the **P8** header and the **RiBUS** FFC.
it adds an **8-channel 16-bit ADC** for vehicle analog inputs and dry contacts, a **copper-only vehicle-CAN pass-through**, and keeps the ESP32-C3 WiFi module (on SPI1 over RiBUS) with native USB-C flashing. Powered from the car's 12 V via the display.
JLCPCB was used to manufacture all the boards & there was luckily a failed attempt on the first job i sent to get manufactured that Tazzi picked up immediatly, so i managed to cancel the order to address the issue on the next round. It was a few weeks ago now & i can't remember what the specific issue was but it would of cost me $400 worth of failed parts.
Cue some 3 weeks later after getting the board made, delivered & me getting home from work, i was looking forward to testing out my new board.. cue suspenseful music..
So i start by plugging it into my laptop usb port to attempt to load the esp32 firmware up & nothing.. no comm port, no sound of a usb connected device.. ah shit. ah well try the next one... same, then the next.. all 5 boards have the same problem. completely dead, this is not good. Spent the day talking to claude on testing points, checking voltages, resistance, continuity & nada. I end up removing the ESP32 chip on 1 board looking for a short or issue before i set them aside in disappointment.
Cost of Boards: $397.20
Result & known issues: Dead, no power
FFC pinout is ass about to what the display uses, so it needs an A type FFC & flip the cable over. Basically Pin 1 on a normal FFC connector is on the left, but Riverdi made pin 1 on the right of the board.
I also purchased some premade 6 pin pico blade cables, these should have been pinned 1:1, but i found pin 1 goes to 6,2 to 5 & so on. Not good when mixing 12v & gnd for the power pass-through.
Luckily i had the smarts to check this before i plugged it in, but the display does have reverse voltage protection, but not keen to pop a display board either.
Next board i ordered was the "Track Expander Board". Again another board for the Riverdi display, this is the cheapest expansion boards im going to offer for sale with my displays. The displays themselves can be used in pretty much anything, not user configurable to the max like a powertune or haltech, but it doesn't take a week to boot up. Since it's firmware based & not running a linux kernel it's basically ready to go in under 2 seconds from power on.
back to the board:
Cost of Boards: $505.58## What the board does
*The motorsport tier: a **brainless, display-driven** daughterboard for the Commander 7 display (Riverdi H7 module, mated over the P8 hub). It gives the display **8 channels of protected 16-bit analog input**
(any of which can be a **dry-contact switch input**), **4 protected high-side outputs**, an **ESP32-C3 for WiFi/BLE**, a **GPS/BDS receiver**, and **CAN pass-through** — all from a single 12 V vehicle feed,
reverse- and surge-protected. There is **no local MCU**: the display's H7 drives the ADC and outputs directly over the P8 hub, and the ESP over the RiBUS flex.
Problems:
Same deal as the Mini board, plug it into my laptop to flash the firmware & were dead too. FARKKK.... spend another day talking to claude on what the issue could be, 2 different style board with the same problem, this is clearly not a board build issue, but a placement one.. End result find that 3 of the power diodes were placed back to front. Claude had assigned the wrong pin numbers to components & since the track board was based off the mini, it carried over the same fault. So from the learnings on this one i was able to recover the mini boards by unsoldering the diodes, rotating them 180, solder again & the sweet sound of a device detected on the USB port started chiming away.
GPS works, comms to ESP works, Analog signal inputs also worked to a Display Project ive configured for our Haltech fitted budget race car. Large feeling of relief that i haven't blown close to $1000 bucks for zero results.
Next board is a Dual PWM fuel pump controller V1 (i'm at like V3.1 design now, coz i keep adding features, lol).
It has ESP32, can twai. PWM 2 x 30amp TI/Walbro 525 pumps or fans, 3rd output control for reverse lights or relay. Basically you can configure it to turn on the output based on any canbus signal condition.
Watch CAN data gauges over the wifi link on laptop/phone (i even built a custom firmware to a cheap 7" waveshare dash to configure the device/access the gauges etc) Cost of Boards: $525.58
Problems: Plugged it into program the esp & luckily when i was holding it i felt something get hot with my finger real quick, disconnected it before the smoke got let out, whether that would happen or not im not sure, but i erred of the side of caution & unplugged it. Again spent some more time diagnosing with claude, during some voltage checks found that the 3.3v supply to the esp was being pulled down to 1.4v. Again the cause of this was a pinout issue to a component, luckily it was auxillary signal over voltage protection related for ESP ADC pins, but was redundant because we were already clamping via TVS clamps. So easy solution was to just de-solder the 3 components off each board.
I've also been getting claude to do a bunch of 3d design work so i could print out case mounts & other parts/projects im working on too. I feed it measurements, suggestions etc & it gets it right 70% of the time, but it's still quicker then me learning the CAD software. I have however gotten more confidence/knowledge on circuit design, running trace lines, via's etc on the PCB side. Sometimes it's quick for me to do stuff then let claude attempt to do it headless, purely because of software limitations.
Over all, It's pretty exciting stuff. The display boards will just be used for development use & the current issues have already been rectified for new board orders with some other placement tweaks etc.