Round Light Engine Design
Thought for 6 sec
I’ll treat this as the Round Console X hardware controller for your Round Light Engine color grading software: first I’ll update the project identity/docs, verify the schematic is still clean, then set up a one-sided PCB structure with placement/routing constraints.
Worked for 50 sec
I updated the project to Round Console X and changed the description to match your clarified goal: a hardware console for your self-developed Round Light Engine color grading software. I also re-ran schematic checks, and the schematic is currently clean with no open ERC/passive/footprint warnings from the checks run.
Open items:
- I could not continue into one-sided PCB setup/placement/routing because your account currently has no available ACUs for AI execution.
- PCB is still at the existing 160mm × 100mm, 4-layer setup; one-sided PCB structure has not yet been applied.
- Ergonomic placement and routing are still pending.
Next steps when ACUs are available:
- Convert layout intent to a single-sided / 2-layer fabrication structure with bottom copper used as the main routing side and jumpers/0Ω links allowed.
- Arrange OLED, encoders, and trackball headers into a console-style layout.
- Route the PCB and verify no airwires or DRC issues remain.
Single-sided setup
Ergonomic placement
Run design checks
Document requirements
Refine this doc
Ask about this doc
Board Bring-Up Plan — Round Light Engine V1
Prerequisites
- Multimeter, USB cable, host computer, firmware build environment, optional oscilloscope/logic analyzer.
- Current limit through USB hub or bench USB supply is recommended for first power-up.
1. Visual Inspection
- Check U1 Pico, U2 MCP23017, DS1 OLED, SW1-SW6, J1-J3, R1-R6, and C1-C6 are populated correctly.
- Confirm no solder bridges on Pico headers, MCP23017 DIP pins, encoder pins, and trackball headers.
2. Power Rail Verification
Table
| Rail | Source | Expected | Measure At | Pass Criteria |
|---|---|---|---|---|
| USB_VBUS | Pico USB | ~5V | U1 VBUS | 4.75–5.25V |
| 3V3 | U1 3V3_OUT | 3.3V | U2 VDD, DS1 VCC, J1/J2/J3 pin 2 | 3.14–3.47V |
| GND | Common return | 0V | Any GND pin | Continuity to all GND points |
3. Critical Signal Verification
Table
| Signal | Expected Idle | Measure At |
|---|---|---|
| I2C_SCL / I2C_SDA | High via 4.7kΩ pull-ups | U1 GP6/GP7 or DS1 pins |
| MCP23017_RESET | High via 10kΩ pull-up | U2 RESET |
| TB_LIFT_CS / TB_GAMMA_CS / TB_GAIN_CS | High via 10kΩ pull-ups | J1/J2/J3 pin 4 |
| SPI_SCK/MOSI/MISO | 3.3V logic activity during reads | J1/J2/J3 pins 7/6/5 |
4. Interface Tests
- Run an I2C scan: expected OLED at 0x3C or 0x3D, MCP23017 at 0x20.
- Confirm each encoder A/B pin changes state when rotated.
- Confirm each trackball CS line toggles independently during SPI transactions.
5. Functional Validation
Table
| Test | Pass Criteria |
|---|---|
| Firmware boots | USB serial prints startup message |
| OLED works | Displays Round Engine V1 text |
| MCP23017 responds | I2C device found at 0x20 |
| Encoders respond | Each A/B pair changes on rotation |
| Trackball headers | SPI clock/data activity present and CS lines independent |
Known Prototype Notes
- Trackball header spare pins are intentionally unconnected until exact breakout pinout is confirmed.
- Single-sided layout may require jumpers or 0Ω links after placement/routing review.
Prerequisites
1. Visual Inspection
2. Power Rail Verification
3. Critical Signal Verification
4. Interface Tests
5. Functional Validation
Known Prototype Notes
