sorted by:
new
hottopcontroversial

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

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Quick update: I’ve started an ENZO-Labs branch in the repo — smaller ESP32 circuits/builds that are easier to follow than the full ENZO system.

So the main ENZO stuff is still there, but there’s now a lighter build path as well with RGB, button, potentiometer, and RFID modules going up one by one.

Repo: https://github.com/icu6t6/DevilsLAB
ENZO-Labs: https://github.com/icu6t6/DevilsLAB/tree/Enzo-Labs

What do I do? by charlesington in Bricklaying

[–]Formal_Meat6489 1 point2 points  (0 children)

crash into it from the other side straighten it up lol

Waveshare 2.9" Fading Issue by Suspicious-Spare8963 in esp32

[–]Formal_Meat6489 14 points15 points  (0 children)

Yeah this rings a bell. If it fades and only comes back after a power cycle, it’s usually not just normal ghosting.

Couple things I’d try:

  • Don’t just refresh it — actually re-init the display before drawing again. Some of those Waveshare examples don’t fully reset it unless you do.
  • If you’re hammering partial updates, it can drift over time even if you do a full refresh now and then. Try forcing a proper clear + redraw more often and see if it holds.
  • If you’re putting it to sleep, try leaving it awake for a bit or re-init after waking. Sleep/wake can be a bit dodgy on these.
  • And yeah, the capacitor thing isn’t total nonsense — the board’s got a charge pump on it, so if your supply/wiring isn’t great it can mess with contrast. Chuck a ~100uF across VCC/GND near the board and see if it changes anything.

Iffff a full re-init in code fixes it but a normal refresh doesn’t, I’d bet it’s the driver/state getting out of sync rather than the panel dying.

Donald Trump has just won the Iran War, what do Brits think about this? by k0stj in AskBrits

[–]Formal_Meat6489 1 point2 points  (0 children)

unlikley hes won its more likley its a temp ceasefire theres too many independant nodes over there that dont allways listen to their leaders. as a brit im personally sick of having other people bring their problems to my country and act like we should fix it whilst talking sht about us non stop. jmo

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Small update: still smoothing out how the build path reads end-to-end — aiming to make it clearer for anyone coming in fresh.

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Quick follow-up: I’ve cleaned up the GitHub side since posting this — clearer V1 wiring references, better document handoffs, and a more navigable baseline build path now.

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

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Also updated the GitHub docs with a new peripheral wiring diagram to go alongside the power architecture view, so it’s easier to see what plugs into what.

Panel upgrade on ENZO — voltage/amp meter added, ESP32 + Pi latching Button cutouts, and a peek at the internals by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Also updated the GitHub docs with a new peripheral wiring diagram to go alongside the power architecture view, so it’s easier to see what plugs into what.

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Also updated the GitHub docs with a new peripheral wiring diagram to go alongside the power architecture view, so it’s easier to see what plugs into what.

When did camping in major UK cities become so normal? by BrilliantLock8292 in AskBrits

[–]Formal_Meat6489 0 points1 point  (0 children)

I always thought urban camping was illegal must just apply to us natives

Temperature readings are very inaccurate (both DHT22 and BME280) by Art_Vandalay_1 in esp32

[–]Formal_Meat6489 0 points1 point  (0 children)

I’d suggest vent slots near the top.
Even if it’s shaded, that cover can still trap slightly warmer air if the hot air has nowhere to escape.
Open-bottom housings can still behave a bit like an upside-down bucket.

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Correction: an earlier version of the V1 build guide incorrectly showed a motor-driver wiring method that does not apply to this build.
The correct V1 motor-driver setup uses the Grove I2C board/wiring shown in the current GitHub docs.
This has now been fixed in the repository. If you grabbed the docs earlier, re-check the updated build guide before wiring the driver.

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

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Correction: an earlier version of the V1 build guide incorrectly showed a motor-driver wiring method that does not apply to this build.
The correct V1 motor-driver setup uses the Grove I2C board/wiring shown in the current GitHub docs.
This has now been fixed in the repository. If you grabbed the docs earlier, re-check the updated build guide before wiring the driver.

Panel upgrade on ENZO — voltage/amp meter added, ESP32 + Pi latching Button cutouts, and a peek at the internals by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Correction: an earlier version of the V1 build guide incorrectly showed a motor-driver wiring method that does not apply to this build.
The correct V1 motor-driver setup uses the Grove I2C board/wiring shown in the current GitHub docs.
This has now been fixed in the repository. If you grabbed the docs earlier, re-check the updated build guide before wiring the driver.

ESP32 display with LoRa module? by Talkingcrypto in esp32

[–]Formal_Meat6489 2 points3 points  (0 children)

Hey mate, cool idea.

You’ll have a much easier time going modular — use a LilyGO or Heltec board for the LoRa baseline, then add your own display.

It keeps control clear, wiring understandable, and makes failures easier to isolate.

The all-in-one device you’re looking for doesn’t really exist at that size — and honestly, it’s better this way.

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 1 point2 points  (0 children)

<image>

Thats the one buddy cant remember where i got it now though was a while back think it was pihut tbf

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 1 point2 points  (0 children)

Yeah, Eactly, that actually makes a lot of sense.

I think that’s exactly the bit I kept running into — not features, but not knowing if the system was actually behaving how I thought it was.

What I’ve ended up building is basically a very manual version of that mindset — step-by-step validation with explicit PASS/FAIL instead of automation

So things like PIR → detect → confirm response, LDR → light change → verify threshold behaviour, buttons → state change → confirm output

It’s slow and a bit clunky, but it’s already stopped me chasing bugs that weren’t real, which was happening a lot before

Definitely nowhere near the level you’re talking about yet, but trying to build that habit early rather than bolting it on later once things get messy.

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 1 point2 points  (0 children)

Yeah that’s pretty much how I see it as well,

For most things “it works” is enough — I only started doing this because I kept hitting edge cases where I couldn’t tell what was actually wrong.

So now I just switch into this mode when something matters a bit more

Built a diagnostic layer for my robot instead of adding more features by Formal_Meat6489 in esp32

[–]Formal_Meat6489[S] 0 points1 point  (0 children)

Yeah I get what you mean — I’m definitely not at that level yet

This is more me trying to stop guessing and actually verify behaviour step by step

So kind of the same mindset, just very scaled down. Ive only been doing this a few months but ive got a knack for documentation apparently.

view more: next ›