https://talkativeturtles.club/ Wed, 05 Aug 2026 13:53:24 +0000 MyBB https://talkativeturtles.club/showthread.php?tid=125 Tue, 07 Jul 2026 08:35:25 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=125
Mistakes:

• Power trace width. Routed my 2A power traces at the default 0.25mm. Use a trace width calculator. Rule of thumb: 0.5mm per amp is conservative but safe.
  
• Decoupling caps too far from the IC. Put them at the edge of the board to keep things tidy. They need to be as close to the VCC pin as possible.
  
• No test points. Trying to probe a QFN package without test points is miserable.
  
• Silkscreen on pads. Solder does not stick properly where silkscreen overlaps pads. KiCad will warn you in DRC but I ignored it.
  

What worked:

• Via stitching around the ground plane looks great
  
• Component placement was decent - watched a lot of Phil Lab videos first
  
• JLCPCB quality on a $5 board is genuinely impressive
  

If you are doing your first board: run DRC until it is clean, double-check your footprints against the actual components, and add test points everywhere.]]>
Mistakes:

• Power trace width. Routed my 2A power traces at the default 0.25mm. Use a trace width calculator. Rule of thumb: 0.5mm per amp is conservative but safe.
  
• Decoupling caps too far from the IC. Put them at the edge of the board to keep things tidy. They need to be as close to the VCC pin as possible.
  
• No test points. Trying to probe a QFN package without test points is miserable.
  
• Silkscreen on pads. Solder does not stick properly where silkscreen overlaps pads. KiCad will warn you in DRC but I ignored it.
  

What worked:

• Via stitching around the ground plane looks great
  
• Component placement was decent - watched a lot of Phil Lab videos first
  
• JLCPCB quality on a $5 board is genuinely impressive
  

If you are doing your first board: run DRC until it is clean, double-check your footprints against the actual components, and add test points everywhere.]]> https://talkativeturtles.club/showthread.php?tid=135 Sun, 05 Jul 2026 20:52:08 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=135
Pick ESP32 when:

• You need WiFi or Bluetooth. The ESP32 has both built in at a price the Pico cannot match without add-ons.
  
• You are building an IoT device that needs to talk to the internet.
  
• Power consumption matters but not critically - the ESP32 can sleep to ~10 microamps.
  
• You want more GPIO and more peripherals on one chip.
  

Pick Raspberry Pi Pico when:

• You need precise timing - the PIO (Programmable I/O) state machines are genuinely unique and handle timing-critical protocols in ways most microcontrollers cannot.
  
• You want MicroPython and a simpler mental model for beginners.
  
• USB HID device - the Pico is excellent as a custom keyboard, game controller, etc.
  
• Pure compute tasks without wireless.
  

The Pico W exists now and closes some of the gap. WiFi-capable, same pinout as the original Pico, similar price to the ESP32.

For most first projects I point people to the Pico - the documentation and getting-started experience is more polished. For anything network-connected I go ESP32 without thinking about it.]]>
Pick ESP32 when:

• You need WiFi or Bluetooth. The ESP32 has both built in at a price the Pico cannot match without add-ons.
  
• You are building an IoT device that needs to talk to the internet.
  
• Power consumption matters but not critically - the ESP32 can sleep to ~10 microamps.
  
• You want more GPIO and more peripherals on one chip.
  

Pick Raspberry Pi Pico when:

• You need precise timing - the PIO (Programmable I/O) state machines are genuinely unique and handle timing-critical protocols in ways most microcontrollers cannot.
  
• You want MicroPython and a simpler mental model for beginners.
  
• USB HID device - the Pico is excellent as a custom keyboard, game controller, etc.
  
• Pure compute tasks without wireless.
  

The Pico W exists now and closes some of the gap. WiFi-capable, same pinout as the original Pico, similar price to the ESP32.

For most first projects I point people to the Pico - the documentation and getting-started experience is more polished. For anything network-connected I go ESP32 without thinking about it.]]> https://talkativeturtles.club/showthread.php?tid=80 Mon, 22 Jun 2026 12:32:07 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=80
The most common mistake: not enough heat, too long
Beginners often use too-low iron temperature and compensate by holding the iron on the joint for too long. This damages components and gives cold joints. Better: use adequate temperature (350-380°C for leaded, 380-400°C for lead-free), heat the joint for 2-3 seconds, flow solder, remove.

You're heating the joint, not the solder
Touch the iron to the pad AND the component leg simultaneously. Let the joint heat up, then bring solder to the joint (not to the iron). The solder should flow toward the heat.

A good solder joint:

• Shiny (not dull or grainy - dull = cold joint)
  
• Concave fillet shape, like a volcano
  
• Not balled up (too much solder) or flat and sparse (too little)
  

Flux is not optional
Flux cleans oxidation and helps solder flow. Most solder wire has flux core but it burns off quickly. For rework or anything that's being a pain, add extra flux paste. It's what makes the difference between a joint that works first time and one that takes ten attempts.

Gear worth having:

• A temperature-controlled iron (Pinecil is excellent at £25, Hakko FX-888D if you want pro)
  
• Flux paste
  
• Solder wick for removing excess
  
• A solder sucker (desoldering pump) for through-hole work
  
• Good lighting and magnification - you'd be surprised what you can't see with the naked eye
  

What are you currently soldering?]]>
The most common mistake: not enough heat, too long
Beginners often use too-low iron temperature and compensate by holding the iron on the joint for too long. This damages components and gives cold joints. Better: use adequate temperature (350-380°C for leaded, 380-400°C for lead-free), heat the joint for 2-3 seconds, flow solder, remove.

You're heating the joint, not the solder
Touch the iron to the pad AND the component leg simultaneously. Let the joint heat up, then bring solder to the joint (not to the iron). The solder should flow toward the heat.

A good solder joint:

• Shiny (not dull or grainy - dull = cold joint)
  
• Concave fillet shape, like a volcano
  
• Not balled up (too much solder) or flat and sparse (too little)
  

Flux is not optional
Flux cleans oxidation and helps solder flow. Most solder wire has flux core but it burns off quickly. For rework or anything that's being a pain, add extra flux paste. It's what makes the difference between a joint that works first time and one that takes ten attempts.

Gear worth having:

• A temperature-controlled iron (Pinecil is excellent at £25, Hakko FX-888D if you want pro)
  
• Flux paste
  
• Solder wick for removing excess
  
• A solder sucker (desoldering pump) for through-hole work
  
• Good lighting and magnification - you'd be surprised what you can't see with the naked eye
  

What are you currently soldering?]]> https://talkativeturtles.club/showthread.php?tid=79 Mon, 22 Jun 2026 12:24:14 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=79
Use an ESP32 when:

• You need WiFi or Bluetooth connectivity and low power consumption
  
• The project runs from battery or a small power supply
  
• You don't need to run a full OS - just read sensors, control outputs, talk to a service
  
• You want something small and cheap (£3-8 for a dev board)
  
• Real-time constraints matter - the ESP32 runs FreeRTOS and has deterministic timing
  

Use a Raspberry Pi when:

• You need to run Linux - web server, database, media server, Python with heavy libraries
  
• You need USB peripherals, a desktop environment, or complex I/O
  
• Processing power matters more than power efficiency
  
• You're running something that needs to be always-on and plugged in
  

Common mistake: Using a Pi for something that just reads a sensor and sends data somewhere. That's an ESP32 job - lower cost, lower power, runs for months on a battery.

Common mistake #2: Using an ESP32 for something that needs to parse JSON from a complex API, do image processing, or run a web framework. That's a Pi job.

The middle ground: An ESP32 talking to a Pi over MQTT. ESP32s do the sensing and actuation at the edge, Pi does the aggregation, logging, and web interface. Works very well for home automation setups.

What are you using for your current project and why?]]>
Use an ESP32 when:

• You need WiFi or Bluetooth connectivity and low power consumption
  
• The project runs from battery or a small power supply
  
• You don't need to run a full OS - just read sensors, control outputs, talk to a service
  
• You want something small and cheap (£3-8 for a dev board)
  
• Real-time constraints matter - the ESP32 runs FreeRTOS and has deterministic timing
  

Use a Raspberry Pi when:

• You need to run Linux - web server, database, media server, Python with heavy libraries
  
• You need USB peripherals, a desktop environment, or complex I/O
  
• Processing power matters more than power efficiency
  
• You're running something that needs to be always-on and plugged in
  

Common mistake: Using a Pi for something that just reads a sensor and sends data somewhere. That's an ESP32 job - lower cost, lower power, runs for months on a battery.

Common mistake #2: Using an ESP32 for something that needs to parse JSON from a complex API, do image processing, or run a web framework. That's a Pi job.

The middle ground: An ESP32 talking to a Pi over MQTT. ESP32s do the sensing and actuation at the edge, Pi does the aggregation, logging, and web interface. Works very well for home automation setups.

What are you using for your current project and why?]]> https://talkativeturtles.club/showthread.php?tid=33 Sun, 21 Jun 2026 09:42:20 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=33
I've been building a soil moisture monitoring system for a small greenhouse. ESP32 with a capacitive soil sensor (resistive ones corrode too fast), reading every 15 minutes and pushing data to a small SQLite database on a Pi Zero over MQTT. Simple web dashboard with Chart.js to plot trends over time.

Had a fun bug where the ESP was deep sleeping between readings, which I expected to save power - but the capacitive sensor needs a warm-up period after power-on or the readings are way off. Added a 500ms delay after enabling the sensor power pin and it became rock solid.

What are you building?]]>
I've been building a soil moisture monitoring system for a small greenhouse. ESP32 with a capacitive soil sensor (resistive ones corrode too fast), reading every 15 minutes and pushing data to a small SQLite database on a Pi Zero over MQTT. Simple web dashboard with Chart.js to plot trends over time.

Had a fun bug where the ESP was deep sleeping between readings, which I expected to save power - but the capacitive sensor needs a warm-up period after power-on or the readings are way off. Added a 500ms delay after enabling the sensor power pin and it became rock solid.

What are you building?]]> https://talkativeturtles.club/showthread.php?tid=32 Sun, 21 Jun 2026 09:42:20 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=32
Arduino

• arduino.cc/en/Tutorial/HomePage - Official tutorials, genuinely good
  
• Elegoo starter kits - affordable, come with a components guide
  
• "Arduino Cookbook" by Michael Margolis - solid reference
  

ESP32 / ESP8266

• randomnerdtutorials.com - One of the best ESP resource sites
  
• docs.espressif.com - Official Espressif docs
  
• PlatformIO (platformio.org) - Much better than Arduino IDE for real projects
  

Raspberry Pi

• raspberrypi.com/documentation - Official docs
  
• pimylifeup.com - Project guides and tutorials
  
• Jeff Geerling's YouTube & blog (jeffgeerling.com) - Best Pi content on the internet
  

Electronics Fundamentals

• "The Art of Electronics" - Horowitz & Hill (the bible)
  
• All About Circuits (allaboutcircuits.com) - Free textbook
  
• EEVblog YouTube - Dave Jones explains concepts excellently
  

Where to buy components

• DigiKey, Mouser - Professional grade, wide selection
  
• AliExpress - Cheap modules for prototyping (variable quality, slow shipping)
  
• Pimoroni (UK), Adafruit (US) - Curated maker-focused stock
  

]]>
Arduino

• arduino.cc/en/Tutorial/HomePage - Official tutorials, genuinely good
  
• Elegoo starter kits - affordable, come with a components guide
  
• "Arduino Cookbook" by Michael Margolis - solid reference
  

ESP32 / ESP8266

• randomnerdtutorials.com - One of the best ESP resource sites
  
• docs.espressif.com - Official Espressif docs
  
• PlatformIO (platformio.org) - Much better than Arduino IDE for real projects
  

Raspberry Pi

• raspberrypi.com/documentation - Official docs
  
• pimylifeup.com - Project guides and tutorials
  
• Jeff Geerling's YouTube & blog (jeffgeerling.com) - Best Pi content on the internet
  

Electronics Fundamentals

• "The Art of Electronics" - Horowitz & Hill (the bible)
  
• All About Circuits (allaboutcircuits.com) - Free textbook
  
• EEVblog YouTube - Dave Jones explains concepts excellently
  

Where to buy components

• DigiKey, Mouser - Professional grade, wide selection
  
• AliExpress - Cheap modules for prototyping (variable quality, slow shipping)
  
• Pimoroni (UK), Adafruit (US) - Curated maker-focused stock
  

]]> https://talkativeturtles.club/showthread.php?tid=6 Sun, 21 Jun 2026 09:34:07 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=6 Microcontrollers & Electronics covers Arduino, ESP32, Raspberry Pi, circuit design, soldering, sensors, and embedded systems.

Posting Rules:

• Specify your hardware. Include microcontroller model, voltage levels, and any shields/modules involved.
  
• Use [code] tags for firmware/code snippets.
  
• Post schematics or wiring diagrams when asking about circuit issues. A photo of your breadboard is also helpful.
  
• State what you have measured. Include oscilloscope traces, multimeter readings, or serial output when debugging.
  
• Safety first. Do not encourage or share designs that violate electrical safety standards. Mains voltage projects require appropriate warnings.
  
• Share your results when your problem is solved - it helps the next person.
  

]]> Microcontrollers & Electronics covers Arduino, ESP32, Raspberry Pi, circuit design, soldering, sensors, and embedded systems.

Posting Rules:

• Specify your hardware. Include microcontroller model, voltage levels, and any shields/modules involved.
  
• Use [code] tags for firmware/code snippets.
  
• Post schematics or wiring diagrams when asking about circuit issues. A photo of your breadboard is also helpful.
  
• State what you have measured. Include oscilloscope traces, multimeter readings, or serial output when debugging.
  
• Safety first. Do not encourage or share designs that violate electrical safety standards. Mains voltage projects require appropriate warnings.
  
• Share your results when your problem is solved - it helps the next person.
  

]]>