I have an ESP32 running a TV backlight on a 10A power supply. I split the power line to try to siphon off approx 2A to power a small usb c that can be used for a separate Led lamp or even another small LED strip.

The TV LED still turns on but no sign of life in the USBc connector. I've plugged in a C6 mini just to test for a power LED.

How do I trouble shoot this? I've reseated the wires a few times but hasn't done anything.

The connector between the USB c piece and the larger power cable could be a point of failure.

Or have I just misunderstood how to connect a usb c to a set up like this and there is something missing?

Please help!

Seems too good to be true:

• 4" IPS with capacitive touch
• Built in esp32 s3
• SD card slot
• Mic and speaker and battery ports

And it cost less than $20:??

What's the catch? The only thing that popped was that there's no mention of PSRAM (msged the seller, let's see what they say). But I can't find any reviews on it which makes me worries.

They market it for use with AI chat bot, but I don't care. Seems like a good deal if you don't need the extra GPIOs or stereo sound.

Anyone has it and can share their experience?

Since launching the NM-CYD-C5 (the ESP32-C5 based CYD variant with dual-band WiFi 6), the single most common piece of feedback has been:

"Could you make a 1u variant that I could connect an antenna to?"

"Does it have external antenna connector"

"Will an external antenna be supported this time, or is a DIY solution again required to attach an external antenna?"

Fair point. 5GHz attenuates much faster than 2.4GHz, and a small PCB trace antenna surrounded by a display and ground planes has its limits.

So: the NM-CYD-C5-Colorful-Ant is coming.

• IPEX-1 connector + bundled dual-band 2.4G/5G antenna • External antenna only — no onboard PCB antenna on this version • Same ESP32-C5 (dual-band WiFi 6, BLE 5.3, Zigbee/Thread), same 16MB Flash + 8MB PSRAM, same CYD-compatible footprint • Still works with Bruce / Marauder / ESPHome, etc as before

The default External Antenna Parameters

• Frequency range: 2400-2500MHz / 5000-5800MHz
• VSWR: 2400-2500 ≤ 2.5, 5000-5800 ≤ 2.5
• Efficiency %: 2400-2500: 83.3 AVG; 5000-5800: 73.8 AVG
• Peak Gain (dBi): 2400-2500: 3.2 AVG; 5000-5800: 3.7 AVG
• Radiation Properties: Omni-directional
• Polarization: Linear

The 3D printed shells (see from the picture) will be released on GitHub repository soon.

https://github.com/RockBase-iot/NM-CYD-C5

Guys I have built a DIY 1.8 inch TFT Display ST7735 Module With Only 50Rs/0.5$ The PCB Is Totally Hand Made Using Toner Transfer Paper And Working Quite Well The All Source Header Files For different ESP Boards are in the github repository with schematics diagrams, Pinout Of the module, Proper documentation has been in the video and github repository please follow it, it use TFT_eSPI Library

Github Repo:-https://github.com/samiralam5755/DIY-1.8-TFT-Display

Full Video:-https://youtu.be/EqtmMCGdx98

Dead TWS earbuds still have a working Bluetooth receiver + amp — only the battery, buttons, or mic usually fail. So I tapped the analog speaker output and built a 3-tone FSK modem to send data over it.

Signal path:

Phone/PC → Bluetooth A2DP → TWS earbud → analog speaker out → MCU ADC → Goertzel FSK demod → packet + CRC

Key details: TWS output is BTL/differential — do NOT ground the second speaker terminal, it'll short the amp (as did) .

ADC sample rate assumption (8kHz) was wrong. Measured actual rate was 5.8kHz. 3 sparse tones (700/1100/1700 Hz) survive the earbud's bad frequency response better than GGWave's multi-tone scheme, which failed to decode payloads reliably on this path. Built a small packet protocol: preamble, length, payload, CRC-8, end marker. Keeping the A2DP stream open, instead of closing/reopening it, fixed intermittent decode failures.

Results: 95%+ packet success in integration testing. 4/4 packets decoded clean with valid CRC in controlled tests.

~3.2–4.5 bit/s effective payload rate. Not competitive with SPP or a real wireless modem — that's not the point. The point is turning e-waste into a $0 Bluetooth-to-MCU bridge.

Next: testing this with a Bluetooth-less MCU (CH32V003) as the actual receiver. Source: https://github.com/Ishu1519/TWS-A2DP-Mode

Curious if anyone's got a better modulation scheme that survives A2DP codec distortion at a higher bitrate.

Hi r/esp32,

I’m the developer of OmniPulse, a project that uses ESP32 boards as external Wi-Fi survey sensors for native clients on iPhone, iPad and Mac, with a companion Apple Watch app.

The engineering problem I was trying to solve is that iOS applications do not receive unrestricted information about surrounding Wi-Fi networks. Instead of attempting to bypass the operating system restrictions, I built firmware that lets authorized ESP32 sensors collect standard Wi-Fi scan results and send the observations to the Apple device.

I found several general BLE debugging applications and ESP32 Wi-Fi scanning examples, but I wanted a workflow capable of combining measurements from multiple sensors, reviewing them before importing, and associating them with locations or floor plans.

### Try OmniPulse

- Source code and ESP firmware:
  https://github.com/tiburonns/OmniPulse

- AltStore source:
  https://raw.githubusercontent.com/tiburonns/OmniPulse/main/source.json

- Latest release — OmniPulse 1.0.1:
  https://github.com/tiburonns/OmniPulse/releases/tag/v1.0.1

In AltStore, open **Sources → +** and paste the AltStore source URL.

ESP32 implementation

The current design works as follows:

1. An ESP32 performs a standard Wi-Fi scan.
2. The firmware converts the observations into measurement batches.
3. The batches are transferred to the client through a custom BLE GATT protocol.
4. The client reviews and imports the observations.
5. The measurements can then be used for channel analysis, maps, floor plans, PDF reports and CSV exports.

The application can maintain simultaneous connections with up to eight ESP32 sensors. The firmware also includes BLE OTA support and a 4 MB OTA partition layout.

Current PlatformIO environments cover:

• ESP32
• ESP32-S3
• ESP32-C5
• ESP32-CAM
• XIAO ESP32S3 / Sense

There is also a separate local HTTP implementation for ESP8266 and Wemos/LOLIN D1 mini boards.

No custom PCB is required; the current implementation runs on off-the-shelf development boards.

Safety and privacy boundaries

This is intended only for surveying networks and locations the user owns or is explicitly authorized to analyze.

The firmware does not:

• Deauthenticate clients
• Jam or disrupt radio communications
• Inject packets
• Attempt to decrypt networks
• Capture network payload traffic
• Transmit observed MAC addresses in clear text

BLE identifiers stored by the application are converted into session-specific pseudonyms.

Source and documentation

Main repository:
https://github.com/tiburonns/OmniPulse

ESP32 firmware:
https://github.com/tiburonns/OmniPulse/tree/main/firmware/esp32-omnipulse

Firmware source:
https://github.com/tiburonns/OmniPulse/tree/main/firmware/esp32-omnipulse/src

BLE protocol specification:
https://github.com/tiburonns/OmniPulse/blob/main/docs/ESP32_PROTOCOL.md

Architecture documentation:
https://github.com/tiburonns/OmniPulse/blob/main/docs/ARCHITECTURE.md

The project is free and source-available for inspection. There is no subscription or paid plan.

I would appreciate feedback specifically on these engineering decisions:

1. Is BLE GATT a reasonable transport for batches of Wi-Fi observations, or would you choose HTTP, MQTT or ESP-NOW?
2. Is the protocol documentation sufficient for someone to implement a compatible sensor independently?
3. Which ESP32 variant would you prioritize for reliability and power-consumption testing?
4. Are there additional scan measurements that would be useful without crossing into packet capture or disruptive behavior?

I’ll monitor the comments and would appreciate honest technical criticism. Thanks!

My handheld device is limited to 2 tactile switches, one of which is used to wake the device up from deep sleep & the other one I want to use to enter download mode.

After looking into the datasheet, I found that logic level high & low voltages are 0.75 * VDD & 0.25 * VDD respectively (2.475V & 0.825V).

I came up with the following circuit where after toggling the button, RST goes "HIGH" (above 2.475V) at ~16 ms and after that, IO0 stays "LOW" (below 0.825V) for about ~24 ms.

Here's the falstad circuitjs link if anyone wants to try: https://www.falstad.com/s.php?s=XXFnBH

I want to know if there's any issue with this circuit or if there's a better alternative?

This device will be updated OTA for most of the time, but this is a fallback mechanism to ensure the device isn't bricked in an bad update.

Edit: The MCU is ESP32-S3

Hi folks,

I finally got around to finishing the documentation for my hexapod robot dog, The hardest part to figure out was powering the servos directly from buck converters and setting up the common ground bus to PCA boards, I believe this might be a pain in the neck for many first timers so I am sharing the full wiring diagram here for anyone to benefit.

I also put together a detailed documentation for the robot itself. I contains information about the parts I used for the robot and how the joint servos are wired across the two PCA board pins.

You can download the diagram, documentation and the design file form the links below if you are interested in building one yourself or would like to use it as reference for a similar project.

Documentation and Diagram:

https://www.patreon.com/PrintedRobotics/posts/hexadog-zbd-and-167021077

https://app.cirkitdesigner.com/project/0a1ee9f8-8495-4f33-9e41-12ed67207672

CAD and 3D printing files:

https://makerworld.com/en/models/3181404-hexadog-zbd

https://www.patreon.com/PrintedRobotics/posts/hexadog-zbd-and-165170615

ESP32 Scripts and Android Controller app APK:

https://github.com/serdarselimys/HexaDogZBD-ESP32Scripts

https://github.com/serdarselimys/HexaDogZBD-AndroidControllerApp

I do have a question for you all, should I design and build a mini version of the robot with SG92R servos? If I can manage to keep the weight down enough it might be even more agile and cost under 100 bucks? has anyone tried building robot dogs or hexapod robots with SG92R? how was your experience with them??

I also share simulation tutorials along with my robot's other videos on my youtube channel youtube.com/@printedrobotics check it out if you are interested in simulation side of robotics, I share all my scripts for free so you can download them and experiment on your own.

As always, your comments and suggestions for my robot are most appreciated.

What this basically is is a PID controlled PWM Solenoid driver, running on a C3 SuperMini. Designed my first PCB for this (with some mistakes ofc) and decided to use a TC4422 mosfet driver. Also included a 5V supply to be able to plug it into my cars 12v system. Code was mostly written by an LLM, including the Webserver which this is running for setting Target and PID parameters. (I'm a real newbie with all of this) I'm already working on rev2 which I'm gonna post on GitHub solving all my issues with this one. (https://github.com/ziraw).

I've tested the perfboard prototype on my car already (1989 200SX CA18DET) with a BMW N75 Boost Valve strapped to my waste gate and it seems to work perfectly, just not getting enough air through the OEM Airbox though atm, hitting a ceiling of 0.9bar. Gonna install this soon and see what it does. I/O: 12v,5v,sensor(i/o), valve.

The only thing this doesn't include ATM is a pressure sensor, I'm grabbing it off of my boost gauge. But the IO has a 5V supply for any type of sensor to be hooked up directly, the code might need adjusting through. It's currently Ov=-1 / 5V=+4 bar (Scaled to 3.3V and divided by 1.1 since that seems to reflect what my gauge is saying more accurately).

I don't specifically know why I made this, just thought it couldnt be that hard and I haven't seen anything like this, besides what maybe Speeduino and rusEFI are doing. If this already exists I'd love the be informed :-)

Cheers

(disclaimer: might blow up your engine)

Hello,
I wanted to share my project that I've been working on that is aimed for debugging and flashing everything around the esp chip from the browser only without anything to install. I got frustrated with the current tech that for a lot of basic things esp-idf is needed while I don't have my regular device at hand. There are couple of other projects allowing to flash the board from browser or open a terminal but most of them are very basic and not sufficient to do something more advanced. I got into the internals and realised the tech is ready (Webserial api, webassembly and browser support) and exists but there is no tool to leverage it so I built the ESP Swiss knife tool.

All of this runs in a browser as a static website with no installation (browser must support Webserial, recommended choice is chrome/edge)

Here is a quick rundown of features:

• flash and chip identification
• read and write memory (in bootloader mode) interactive terminal
• inspect security status of efuses and configuration (secure boot) read and browser partition table flash any partition or whole chip, verify on flash, sanity check for alignment and compatibility, dump chip/partition or edit any flash data via builtin hexviewer
• inspect bootloader details
• edit otadata status, reflash apps and change their ota status
• browse and modify NVS keys in nvs partition
• browse and modify with full file browser for supported FS partition types (littlefs, spiffs, fat32) read and decode coredumps directly in browser

The tool is available for free at https://esp.sourcecode.ai . Please share any feedback or ideas for improvements. Thank you guys for trying and I hope this helps you in debugging as much as it does me on daily basis!

For years, I've been stupid and soldering using my "helping hands" thing. 🤦‍♂️

This made is so much quicker and easier. Literally 30 seconds to do both sides! Hopefully one person doomscrolling sees this and it helps them.

This is my first hardware project: a voice AI device connected to a local server running Agora Conversational AI. I’m new to hardware and don’t have any soldering experience yet, so I’m starting with a breadboard prototype based on this idea.
I’ve decided to learn soldering and PCB design, with the goal of eventually turning this into a real product. Any advice?

I made a PWM fan hub/controller for my passive cooling gpu. Support DS18B20, NTC, manual as temperature source, Curve-based controller, scheduling,... Temporarily closed-source for development, open-source soon.

For PWM, I'm using an NPN open-collector driver, combined with a tachometer level-shifter/divider which I found from here