Acceleratu

Hardware

Designing a solar e-paper station with Codex

I gave Codex a list of parts and access to Fusion. Three prompts later, I had an editable PCB design and files to print its enclosure.

Explore the hardware

Loading design…
Browser
Original Fusion view
Exploded Fusion model showing the display, circuit board, battery and enclosure on the desk stand
Exploded view of the weather station in Autodesk Fusion.

How I set it up

I wanted to see how far I could get with a list of parts and almost no PCB experience. I told ChatGPT what I needed in plain language and asked it to write a prompt for Codex. I then ran that prompt as a Codex goal, with GPT-6 Astra at maximum reasoning effort, access to the computer, the internet and Autodesk Fusion through MCP. The agent could look up a part, draw it, open the drawing and change its mind.

I asked for a two-layer, 1 mm board with every component on top and at most 4.1 mm above the board. The brief called for a weather sensor, radio, solar charging, USB-C and a 4.2-inch e-paper display. I left the dimensions and exact orderable parts to the agent. Eight subagents helped with the board, including separate layout, firmware and review work.

Power, radio and the board

The solar panel is rated at 5 V and 230 mA at its maximum power point. It feeds an SPV1050 energy harvester. A TPS2116 selects solar or USB, giving USB priority. Both go through the same BQ24074 charger to a protected 250 mAh LiPo. The battery temperature circuit can inhibit charging. USB-C supplies power only. Seven pogo contacts provide access for programming and debugging.

The source changeover looked straightforward on the schematic. The simulation used TI’s model of the TPS2116. With solar power available, the USB input fell from 5.25 V to 3.55 V in 200 µs. In all three runs, the switch output dipped to about 3.88 V, below the charger’s input regulation threshold. The simulation covered the switch alone. The bench plan therefore calls for watching the charger and battery rails during an actual switchover. Starting on solar alone is another open test.

The PCB layout measures 112 × 84 mm. The nRF54L15-QFAA sits inside an Ebyte E73-2G4M08S1F radio module with its own crystals and antenna. Checking the module drawing moved four ground pads by 0.30 mm. In the display circuit, the stencil opening for inductor L301 was only 0.025 mm from the nominal outline of transistor Q301. Moving L301 by 0.35 mm gave its second pad 0.375 mm of clearance from Q301 at nominal dimensions, or 0.305 mm with the largest specified transistor body.

Copper tracks and pads on the top side
Top copper, reopened from the manufacturing files. The antenna keepout lies along the board edge.

Waking a display that forgets

The picture stays on the glass when power is removed, but the SSD1683 controller loses its working memory. A partial update needs both the old and the new image. The firmware stores the last confirmed scene in the microcontroller’s nonvolatile RRAM. When a partial refresh is possible after wake-up, the firmware rebuilds the old and new 400 × 300 monochrome frames and sends 15,000 bytes for each. If power failed midway through a refresh, it requests a full redraw.

The PCF85063A clock runs on the always-on supply while the main rail is off. The design uses its quarter-hour alarm, the TPL5111 and the RT6160 regulator to power the 3.3 V rail for a BME280 reading. The first choice of clock was out of stock. The selected part is PCF85063AT/AY. The 24-pin display connector also needed checking against the exact black-and-white V2 panel. Pins 1 and 4 stay open and pin 5 is VSH2.

Tests on a computer checked the next alarm for every possible starting second of the day (86,400 cases) and simulated power loss while saving display state. Three clean firmware builds produced byte-for-byte identical HEX files. The room-temperature energy model gives 0.707 mAh per day including assumed self-discharge, for 16 full and 80 partial updates. At +5 °C with the battery at 3.35 V, charging inhibited and all 96 updates using a full refresh, the model gives 7.886 mAh per day including self-discharge. Actual current, ghosting and legibility need a meter and a real panel.

The enclosure I forgot to ask for

My first prompt stopped at the board. In the second I asked for a printable enclosure and a visual inspection. The case body measures 134 × 196 × 24 mm in CAD, or 25.10 mm thick including the rear buttons at rest. The stand tilts it 12° from vertical. The display and solar panel share the front. Three keys operate from the back, and five openings let air reach the sensor. I spotted the board through the USB-C opening in the model, so we adjusted the case.

Assembled weather station on its desk stand
The enclosure on its desk stand. The readings on the display are sample data.

Opening the back also moves the battery cable. The service guide says to lift the cover parallel to the board by at most 12 mm before disconnecting the battery. The board and display glass then move together through 20 mm of travel, with the flex cable still connected. The print set contains 11 STL parts. For the complete set, the slicer estimated 10 h 48 min 08 s and 239.17 g of PETG. I haven’t printed or assembled it.

What passed, and what needs a bench

The design has 92 electrical nets, 210 vias and 214 drilled holes. The manufacturing check matched the holes against the reopened drill files. Copper, mask, paste, assembly placement, antenna clearance and access to the test pads were checked separately. The final design passed all 36 automated manufacturing checks and all 35 mechanical checks on the CAD model.

Fusion’s board design-rule check reported zero findings. KiCad found no violations or unconnected items on the imported board. Fusion’s schematic check reported 35 power-pin naming warnings (ERC 104). The review traces all 35 from the symbol pin to the PCB pad and its net. Six deliberately damaged design variants tested the checks themselves, including a mirrored module, crossed battery pins and a trace on an inner layer of the two-layer board. The verifier rejected all six.

The prototype has yet to be built. All 15 tests on the bench worksheet are marked “Not run”. First power-up, changeover under load, charging across temperature, sleep current, radio range, visible partial refresh and USB fit all still need bench work. The qualification plan gives the setup and acceptance thresholds. If you review the files, I’d especially like to hear which part you would put on the bench first.

Time and token costs

Codex recorded the elapsed time from the start of each prompt to its final response. The total excludes the gaps between prompts and counts parallel work by subagents only once.

I ran this on a $200/month subscription. The three prompts used about half my weekly allowance by my estimate. For an API comparison, I counted each recorded model response once, including the subagents. At the standard Astra rates recorded on November 15, 2026, a million tokens cost $10 for new input, $1 for cached input and $50 for output. The reasoning tokens are already included in output.

StageElapsed timeCallsNew inputCache readsOutputUSD
Board1 h 46 min 36 s2,4523,873,137370,936,448994,702459.40
Enclosure1 h 06 min 50 s1,4952,080,431221,413,632702,439277.34
Enclosure revision2 h 00 min 37 s2,6973,257,702419,919,1041,090,795507.04
Total4 h 54 min 03 s6,6449,211,2701,012,269,1842,787,9361,243.78

How the work unfolded

Longest stage37 min 04 sOblique views and board tolerances
Highest estimated cost$164.51Plug clearance and the cover seam
Compare stages by

0 – 40 min0 – 200 USD

1. Circuit board1 h 46 min 36 s · $459.40

Parts, display memory and radio19 min 46 s$106.18
0:00:00 – 0:19:46

Checked stock, changed the RTC, chose the radio module and corrected missing component labels in the first schematic export.

First routing pass and firmware build16 min 59 s$105.76
0:19:46 – 0:36:44

Fusion revealed tracks as narrow as 0.09 mm. In parallel, three clean builds produced byte-for-byte identical HEX files.

Track widths, pins and ground copper20 min 12 s$99.58
0:36:44 – 0:56:56

Reworked routing and checked the pin assignments against firmware. An independent Gerber inspection found isolated ground copper.

Ground connections and 3D assembly14 min 17 s$63.05
0:56:56 – 1:11:13

Reworked the ground connections and reopened the populated board in STEP. At maximum package size, transistor Q301 could overlap the stencil opening for inductor L301.

Final layout and manufacturing checks15 min 37 s$64.45
1:11:13 – 1:26:50

Adjusted component spacing, reran Fusion DRC and reconstructed all 92 nets from the exported copper.

Reimport and handover19 min 47 s$20.38
1:26:50 – 1:46:36

Reimported the F3Z archive in Fusion, checked the schematic, PCB and 3D links, then verified the delivery files.

2. Enclosure1 h 6 min 50 s · $277.34

Measure the display and lay out the front5 min 15 s$21.43
0:00:00 – 0:05:15

Checked the manufacturer’s drawing, reserved the full 36.7 mm width of the display flex and positioned the solar panel below the screen.

Model and slice the enclosure13 min 40 s$55.03
0:05:15 – 0:18:55

Built the first 11 printable parts, including the stand and keys. The slicer revealed unsupported areas, so the cover guides became ramps.

Glass clearance, stand and assembly order19 min 25 s$90.92
0:18:55 – 0:38:20

Moved a screw post away from the glass, lengthened the enclosure by 2 mm, checked insertion into the stand and worked out when to connect the display flex.

Tolerances and solar wiring14 min 24 s$63.48
0:38:20 – 0:52:43

Checked the glass and flex through their 20 mm assembly travel, then checked where the wire insulation ended relative to the solder pad.

Print files and assembly guide14 min 06 s$46.48
0:52:43 – 1:06:50

Checked the exports used for printing and assembly and packaged the models and illustrated guide.

3. Enclosure revision2 h 0 min 37 s · $507.04

Reproduce the issue and reshape the opening15 min 12 s$72.19
0:00:00 – 0:15:12

Found the socket nearly 10 mm behind the wall. The revised recess hid the board from the angle in my screenshot.

Plug clearance and the cover seam30 min 56 s$164.51
0:15:12 – 0:46:08

Checked full insertion of a 13 × 7 mm plug in CAD, sliced the front again and added an internal rib where an oblique view exposed the solar panel.

Oblique views and board tolerances37 min 04 s$156.65
0:46:08 – 1:23:12

Narrowed the sides of the recess and tested the board at its mounting limits. The revised wall blocked all 41 previously identified sight lines.

Print paths and mask alignment25 min 57 s$89.38
1:23:12 – 1:49:09

Checked the wall in the slicer, plug travel in the CAD assembly with the stand fitted, and how far the mask could shift. Added an inspection template and sliced all 11 parts.

Final checks and delivery11 min 28 s$24.30
1:49:09 – 2:00:37

Collected the Fusion views, geometric checks and updated assembly kit. The final report covers 277 viewing directions on the model.

Each prompt starts at 0:00:00. The checkpoints come from the project log. Each stage names the main activity in that interval. Its cost includes every recorded response, including parallel work by subagents. Durations and timestamps are each rounded to the nearest second. Dollar amounts are API estimates rounded to the nearest cent.

The prompts

Translated from Romanian.

What I asked ChatGPT
https://www.anthropic.com/research/claude-electronics-design https://dantudose.github.io/articles/solar-e-ink-board-with-an-ai/ I want to use GPT-6 Astra Max in Codex to reproduce the experiment. I’ll use Fusion and the Fusion MCP. The model can use my computer whenever it wants, with full access to my PC and the internet. No restrictions. I want you to write the prompt for me. I’d like to try doing the whole thing with one prompt, so we’ll use /goal. Tell it to keep going until it’s checked everything visually and run every test it thinks it needs, including the manufacturing checks (I think they’re called DOM). If it spots a problem while testing, it should fix it itself. Tell it to think things through and make the best decisions it can. It can use any tool it wants in Fusion or on my PC, and install whatever it needs. Have it research PCB and schematic design best practices thoroughly online. I just want a prompt that fits within the 4,000-character limit for /goal. I don’t want any extra Markdown files. Let Astra do the reasoning. Just give me the initial prompt. Leave out the sources and include only the requirements. I don’t want it to copy the original experiment or see what went wrong the first time.
1. ChatGPT’s reply and my first prompt for Codex
Design a solar-powered e-ink weather station board from scratch in Autodesk Fusion Electronics. Deliver a complete prototype manufacturing and test package. Use an nRF54L15 in a QFN package, a 2.4 GHz radio and antenna, a 4.2-inch Waveshare e-paper display with a 24-pin FPC connector and its full drive circuitry, a BME280 sensor, an SPV1050 energy harvester and a 5 V, 230 mA solar panel. Use a protected 250 mAh LiPo that can charge from both solar and USB-C, an RT6160 regulator, a TPL5111 timer, an RTC with an alarm, three buttons and battery measurement circuitry. Provide programming and debugging via SWD pogo contacts or a viable USB solution. Keep power consumption low. Support wake-up and partial refresh after main power is switched off. Retain the required state and verify display controller support. Use a two-layer PCB, 1 mm thick, with all components on top and a maximum component height of 4.1 mm above the PCB. Choose the dimensions, parts and unspecified details yourself. Check current JLCPCB assembly stock and use available parts, with 0402 passives where possible. You may use the Fusion MCP, all Fusion features, the terminal, scripts, simulators, other apps and the internet. Use computer control whenever helpful and install any tools or dependencies you need. Make full use of your reasoning, subagents and independent reviews. Make technical decisions without routine confirmation. If an approach fails, diagnose the problem and try another. Keep the final design editable and verify it in Fusion. Research the design thoroughly using datasheets, errata, application notes, reference designs and official guides to schematics, PCB design, RF, power and manufacturing. Develop your own solution without consulting accounts or results of other AI hardware design experiments. Set measurable acceptance criteria and justify key decisions with calculations and documentation. Go beyond checking the design files for consistency: independently verify that the architecture works. Produce a readable schematic, accurate libraries, a fully placed and routed PCB and a 3D model. Check pinouts, symbols, footprints, polarities, connectors, decoupling, return paths, RF design and impedance, power integrity, thermal behaviour and access for programming and testing. Analyse the energy budget, tolerances, corner cases, startup, sleep and wake, all power-source combinations and transitions, charging and protection. Run relevant simulations with valid models. Use independent checks where available. Run ERC and DRC in Fusion. Check the design for manufacturing, assembly and test (DFM, DFA and DFT) against the manufacturer’s actual rules. Cover clearances, trace widths, holes and vias, annular rings, solder mask and paste, silkscreen, edge clearances, tolerances, assembly and testability. Never relax rules or hide errors to get a pass. Open the project in Fusion. Visually inspect every schematic sheet, every PCB layer, both sides of the board and the 3D model. Inspect critical details and check for collisions and access issues. Reopen the Gerber and drill files in an independent viewer and compare them with the design. Save screenshots and test results. Design, verify, inspect, correct and retest. Redesign blocks or reroute as needed. Repeat affected checks after each change, then rerun all relevant checks on the exact revision you deliver. Don’t stop at a plan, a partly routed board or clean ERC and DRC reports. Deliver the native project files, schematic PDF, Gerber and drill files, BOM with manufacturer part numbers and JLCPCB codes, pick-and-place file, 3D model, compiled minimal bring-up firmware and verification reports. Finish only after running every available check and fixing the issues you find. Back every test claim with evidence. Run physical tests if you have the hardware and equipment. Otherwise, mark them as not run and provide procedures and acceptance thresholds. Distinguish simulation from physical validation.
2. The enclosure
I’d like you to make a 3D enclosure for it too. Keep going until you’ve done a full visual check and everything looks right and works.
3. Final enclosure adjustment
Here’s a problem. I want to get the enclosure just right. Change the PCB if you need to, or anything else you think needs changing. The finished design has to pass all your checks. Please fix the USB opening so that only the port itself is exposed.

Project files

The full download contains the editable board and schematic, library, STEP assemblies, firmware source and HEX, manufacturing exports, workshop files and test records. The case models use STEP and the included CAD generator. The Markdown documents are available in English and Romanian. The illustrated workshop guide is in Romanian.

Project documentation
Documentation RO Download .md