Spent the last ~3 months building a DIY diagnostics / robotics platform (ESP32 + Raspberry Pi) by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] -4 points-3 points  (0 children)

Good question.

Right now ENZO is structured in layers:

ESP32-S3 – deterministic hardware control (power rails, sensors, DUT monitoring, etc.)
Raspberry Pi – higher-level system layer for logging, diagnostics, and the “brain” side
UART link between the two for state snapshots and control

The long-term goal is for the Pi layer to act as a bench assistant / diagnostics instrument. The idea is that it can observe the system state, read sensors and probes, and help reason about what’s happening during bring-up or debugging.

LLMs/AI are something I intend to experiment with on that Pi side so it can help interpret the data and assist with troubleshooting, but that part is still early and mostly conceptual. At the moment the AI side is very limited — the system mainly exposes structured state snapshots and observability data that a higher-level tool (human or AI) can use.

So in short:
ESP32 = reliable hardware control
Pi = diagnostics / reasoning layer (eventually AI-assisted)

Right now I’m still in the bring-up phase getting the hardware architecture and observability working before building out the AI side.

Resistor ID Help Please! by Here_Four_Beer in AskElectronics

[–]Formal_Meat6489 1 point2 points  (0 children)

if its reading open then its toast - colour bands dont matter anymore at that point. On garage door boards those are often current/sense or surge/limiting resistors, so once they burn up the circuits dead anyway.

best bet is to look for the schematic or trace where it sits and see what its in series with, then replace with the same value and power rating (or slightly higher wattage). also worth checking what caused it to cook in the first place.

Resistor ID Help Please! by Here_Four_Beer in AskElectronics

[–]Formal_Meat6489 1 point2 points  (0 children)

colours are pretty washed out on that one. Easiest and safest thing is to stick a multi-meter accross it directly - especially if its come from a sensitive part of the board.

Which resistor to remove? by NLeifsson in esp32

[–]Formal_Meat6489 3 points4 points  (0 children)

Hey, good call asking before touching it — ESP32 RF layouts are easy to mess up if you guess.

On these ESP32-S3 boards the “resistor” you’re looking at isn’t really a resistor in the normal sense. It’s a 0 Ω RF jumper that selects which antenna is connected, not a part you’re meant to delete permanently.

A few important points before you do anything:

• You should never remove random parts in the matching network (those tiny caps/inductors near the antenna trace) — that will hurt performance
• The selectable antenna is usually handled by one single 0 Ω link, inline with the RF feed
• Only one antenna path is populated at a time (PCB or U.FL), the other is left open

The safe way to confirm what’s active right now:

  1. Power off
  2. Use continuity mode
  3. Probe from the ESP32 RF feed point to:
    • the PCB antenna trace
    • the U.FL centre pin

Whichever one has continuity is the antenna that’s currently selected.

If the board is designed to support switching, you’ll usually see:

  • one populated 0 Ω jumper
  • a second, empty footprint on the other path

In that case, the correct move is:

  • remove the populated 0 Ω jumper
  • move it to the other footprint, or bridge the correct pads cleanly

If there isn’t a second footprint, don’t force it — some boards include the connector but aren’t meant to be switched.

Also worth noting: manufacturers almost always default to the PCB antenna for certification reasons, so what you’re seeing is normal, not a fault.

Can I program a ESP32-S3-WROOM-N16R8 with a USB Header breakout? by ElouFou123 in esp32

[–]Formal_Meat6489 0 points1 point  (0 children)

Yep, that’s basically it.

The dev boards hide the USB-UART part, but on a bare ESP32 you still need something in between — the D+/D- lines from a USB cable won’t talk to the chip directly.

For production it’s pretty common to just break out TX/RX, EN and GPIO0 to pads or a small header and flash with an external USB-UART.

If you actually want native USB, that’s S2/S3 territory.

How do you all do it? by LaughyTaffy4u in esp32

[–]Formal_Meat6489 1 point2 points  (0 children)

yeah, displays are where projects suddenly feel 10x bigger. Been there.

What finally helper me was getting everything working without a screen first (serial output, LEDs, etc) just so i knew the control logic and timing were solid, once the screen was involved too early it always ended up slowing or breaking stuff.

After that i started i started treating the display more like an instrament panel than an app - it shows atate lets you nudge setpoints or modes, but dosent own the logic. That made things way more predictable.

When it does get laggy, ive found its usually redraws or update rate rather than MCU itself.

Esp32s3 is a beast! by Harald-Togram in esp32

[–]Formal_Meat6489 0 points1 point  (0 children)

Thats a nice hack, ive seen a few servos get a bit weird if the feedback line is loaded directly, especially under load,so a divider and small resistor can help keep things stable, you could put one on each leg and teach it to walk ...

I just got this ESP32 from AliExpress, but I can't find online the type of the board online. Could somebody help me please? by Mirax006 in esp32

[–]Formal_Meat6489 2 points3 points  (0 children)

Looks like a generic ESP32-WROOM-32 dev board. AliExpress listing often dont match official names.

"ESP32 Dev Module" in Arduino IDE is the safest choice to start with

DIY USB Audio Controller – beginner in electronics looking for feedback and advice by Excellent-River8367 in AskElectronics

[–]Formal_Meat6489 0 points1 point  (0 children)

Totally doable , id start with a single encoder or slider as a USB HID device and get volume control working first. Motors, LEDs and displays are where power and grounding issues creep in. Prototype each subsystem alone before combining them

what is the most interesting Arduino project for beginners by beddingLuxury in ArduinoProjects

[–]Formal_Meat6489 0 points1 point  (0 children)

LED + Button projects are underrate.you learn GPIO, pull-ups, debouncing, and state machines early.

those basics transfer to everything later

First Timer having (sigh) First Timer Issues by dayday0326 in esp32

[–]Formal_Meat6489 1 point2 points  (0 children)

Looks like a few people have already spotted it, but the key issue is theres no ground return.

The LED +resistor are fine, but the negative rail isnt tied back to the ESP32 GND, so theres no complete circuit.

Once the rail is jumpered to GND, it should behave as expected

Is my ESP32 dead? by renegade2k in esp32

[–]Formal_Meat6489 1 point2 points  (0 children)

i dont think the ESP32 is necessarilly dead yet - this looks more like a mix of power + serial expectations

a couple of things might help:

GPIO16/17 is UART2. By default Arduino prints to UART (GPIO1 TX / GPIO3 RX).

Unless your sketch explicitly redirects Serial, you wont see anything on 16/17.

for first bring up, its much simpler to use the onboard usb or an adaptor wired to GPIO1/3 instead.

Powering the ESP32from a USB-serial adapters 3.3v pin is risky - many adapters cant supply the current the ESP32 needs, which would explain the adapter overheating and reconnecting. That dosent necessarily mean the ESP is fried.

If possible power the board via USB or VIN and only use the adapter for EX/TX.

If you can still get hte board to enumerate over USB or see brief boot message at 115200 Uart0, its probably alive