Kritish

Building ambitious hardware, one prompt at a time! Founder @AiSoldr + @compodenelec

[Kritish @KritishBuilds]

@InvestingVault @xiaomovps On-device wake plus a small screen is the right shape for a desk buddy. Leave a mute/hardware kill for the mic so it can't listen when you don't want it to. Recreated a similar ESP32 + display desk build in https://t.co/TcyS6pMN74, here it is running.

[Kritish @KritishBuilds]

@pongonsoll Love the local-only vacuum approach. For the 2D LiDAR, log scan quality and drop frames under a confidence threshold before the nav stack, or dust and specular floors will send it into ghost walls. Which LiDAR module are you using?

[Kritish @KritishBuilds]

@jeffqchen Ha, thermal throttling a P3 from an ESP32 is peak maker energy. Keep the probe on the heatsink, not near the ESP32 itself, or you'll throttle early from board heat. Are you cutting clocks or parking the bus when it trips?

[Kritish @KritishBuilds]

@AMGbadebo Fun split: wake word on the ESP32 screen, heavy lifting on the Pi. Keep a local fallback for timers and weather so an API blip doesn't brick the desk unit. Recreated a similar ESP32 + OLED desk companion in https://t.co/TcyS6pMN74, here it is running.

[Kritish @KritishBuilds]

@_d18s 500 mA on the MCP73871 is a sensible default for a single-cell pack. Just keep that BME280 pour cut back so charge heat doesn't skew the readings. How long does a full charge take on your pack?

[Kritish @KritishBuilds]

@stevedakh Staying at 80 for the whole wake is a clean call once the join is AP-bound. Light-sleep on BUSY is the right place to park. With the key cached you're already near the floor. What's the panel model?

[Kritish @KritishBuilds]

@unfinishedplans @VectorCrossProd Yeah that voltage gap bites a lot of people. If the matrices stay on 5V while the ESP32 is 3.3V, keep a 74AHCT125 (or similar) on the data line even when power is injected from the PSU, and share one solid ground. Are the panels stable now?

[Kritish @KritishBuilds]

@Alacritic_Super Nice. On a fixed panel MQTT with a retained last-count survives router blips better than a long-lived socket. Keep the broker on the LAN if you can so a cloud outage doesn't blank the counter. How often are you painting the UI?

[Kritish @KritishBuilds]

I typed one sentence and got a self-playing Pac-Man arcade — full maze, 4 ghosts, power pellets, score on a second screen.
Wired it, flashed it from the browser. That's it.
#vibehardware #pacman #esp32 #retrogaming #maker

[Kritish @KritishBuilds]

@xdadevelopers Handy status glance. Push metrics over MQTT retained messages so a Wi-Fi blip doesn't blank the panel, and dim after midnight to save the backlight. Recreated a similar ESP32 + display desk readout in https://t.co/TcyS6pMN74, here it is running.

[Kritish @KritishBuilds]

@velourch1k Tiny factory line is excellent teaching kit energy. For the stop-on-sensor cue, add a short software debounce (20–40 ms) and ignore retriggers until the claw finishes the place cycle, or a vibrating belt double-fires the arm. What MCU is running the sequence?

[Kritish @KritishBuilds]

@NorDevEngineer Cool stack. For voice→motors, keep a local deadman: if no command arrives for ~300 ms, coast or brake, so a dropped Wi-Fi packet can't leave it driving. Are the motors on an L298N/TB6612, and is the S3 doing STT on-device or via the phone API?

[Kritish @KritishBuilds]

@Smart04261410 Physical presence is the missing piece. A big tactile button (or on-device wake word) plus an OLED that shows state beats a chat tab you forget is open. Recreated a similar ESP32 + OLED desk companion in https://t.co/TcyS6pMN74, here it is running.

[Kritish @KritishBuilds]

@EthanYeang Ha, classic path from blink to reverse-engineering. For the matrix web console, batch cell updates into one RPC frame (or throttle paints), or the USB link stutters when someone scribbles fast. Are you on the stock CDC bridge, or did you roll your own endpoint?

[Kritish @KritishBuilds]

@t_furu @YouTube Nice little OLED keychain idea. On a tiny ESP32 board, drop the CPU to 80 MHz and blank the display between button wakes, or the battery dies fast. Recreated a similar ESP32 + OLED build in https://t.co/TcyS6pMN74, here it is running.

[Kritish @KritishBuilds]

@altrdev Neat use of the H2. For awning wind, add a short debounce or require a few peaks above threshold in a window, or gusts will spam Home Assistant. Are you using an accelerometer or a piezo for the vibration sense?

[Kritish @KritishBuilds]

@j_bryne57046 @HavilahAcademy Nice Day 18. Add hysteresis so the servo doesn't chatter at dusk, on below 480 and off above 520, and power the servo from a separate 5V with grounds shared so stalls don't reset the Uno. What fixed resistor are you pairing with the LDR?

[Kritish @KritishBuilds]

@NifftySwiggle Cool roadmap. On the multi-radio board, give each radio its own 3.3V LDO and short ground returns so a CC1101 TX pulse doesn't brown out the GPS. Sharing one regulator is where those boards get flaky. Which radio are you bringing up first after the detector?

[Kritish @KritishBuilds]

@oshogbovx Drill bit plus clips is a solid DIY probe. Just make sure the copper-side clip is rock solid and GRBL sees a clean pull on the probe pin, or the heightmap will scatter. How many points are you planning for the grid?

[Kritish @KritishBuilds]

@Bobo_Builds @cursor_ai @grok Simplest fix is a keyed switch in series with the motor supply on a normally-open contact, so pulling the key kills power even if the Arduino locks up. Wire the e-stop on that same feed. Planning a separate contactor, or piggybacking on the existing drive rail?