Skip to content

Tools & Reference

4 Topics 4 Posts

Component guides, equipment manuals, sourcing tips, and reading lists.

This category can be followed from the open social web via the handle tools-reference@forum.grapesiot.com

Subcategories


  • Pinouts, wiring guides, datasheet links for common components

    1 1
    1 Topics
    1 Posts
    A
    This category is our shared parts shelf: pinouts, wiring notes, and gotchas for components we all use. Copy this format for every new entry so the database stays searchable: Part: name + common module variant Supply: voltage range the module wants Interface: I2C / SPI / UART / 1-Wire / analog / proprietary ESP32 wiring: which pins, pull-ups needed, level shifting needed? Gotcha: the thing that wastes everyone's afternoon Datasheet: manufacturer link Seeded entries (add yours below) DHT22 (AM2302) — temp + humidity Supply 3.3–5V · proprietary single-wire protocol · any GPIO, 10k pull-up to VCC on the data line. Gotcha: max ~0.5 Hz sampling — poll it every 2 seconds minimum. Faster polling returns stale or checksum-failed reads, and the sensor's physics is minutes-scale anyway; don't chase transients with it. DS18B20 — temperature, 1-Wire Supply 3.0–5.5V · 1-Wire bus (many sensors, one pin) · 4.7k pull-up to VCC on the data line, mandatory. Gotcha: every sensor has a unique 64-bit address — scan the bus and hardcode addresses per unit. Parasite-power mode works but a dedicated VCC wire is far more reliable in the field. MPU6050 — accelerometer + gyro module Supply 3.3V (most modules include a regulator; do NOT feed 5V into VCC if the module is 3.3V-logic) · I2C, address 0x68 (AD0 low) or 0x69 (AD0 high) · SDA/SCL with 4.7k pull-ups to 3.3V. Gotcha: two of these on one bus need different AD0 levels. Raw readings need calibration offsets — sample at rest and subtract bias before trusting angles. HC-SR04 — ultrasonic distance Supply 5V · trigger (input) + echo (output) GPIO · echo idles low and pulses 5V — divide it down (e.g. 1k/2k) before it reaches a 3.3V ESP32 pin. Gotcha: minimum range ~2–3 cm, wide beam picks up nearby objects, and soft surfaces absorb the ping. Time out your pulse measurement or one missed echo hangs the loop. Reply with new parts in the format above. Corrections welcome — a wrong entry here costs someone a board.
  • Using test equipment for embedded debugging

    1 1
    1 Topics
    1 Posts
    A
    Two instruments solve the overwhelming majority of hardware mysteries. You don't need a lab — a basic multimeter and the cheapest scope (or logic analyser) you can borrow will do. Here's the 20% worth learning first. Multimeter: measure, don't guess Continuity beep finds broken wires, cold solder joints, and short circuits. Power off first — beeping a live circuit lies to you and risks the meter. DC volts on the rail, under load. A 3.3V rail that reads 3.28V idle and 2.9V when WiFi transmits is your random-reset culprit. Always measure while the device is doing the thing that fails. Current in series. Break the supply line and put the meter in the middle (correct jack, correct range, start high). Compare against expectations: tens of mA sleeping, hundreds transmitting. Way off in either direction is a clue. Resistance unpowered. Verify pull-ups are actually pulling, dividers divide, and nothing is shorted to ground. Never measure resistance on a powered board. Scope: see the signal in time Probe on ×10, compensated, ground clip short. A long ground lead turns every fast edge into ringing that isn't really there. Compensate the probe on the scope's test output once, then trust what you see. Trigger deliberately. Free-running waveforms are soup. Trigger on the edge you care about — the UART start bit, the PWM rising edge, the droop when the motor kicks — and the picture stabilises. UART debugging: set the timebase to see individual bits, measure one bit width, invert to get the baud (1 ÷ width). If transmit and receive disagree by even a few percent at high baud, you get framing garbage. PWM check: duty cycle and frequency straight off the scope, in seconds. "The motor hums but doesn't turn" is usually 0% or 100% duty, or a frequency the driver can't follow. What to capture when asking for help One screenshot per mystery: the rail during the failure (is it power?), the signal in question with trigger point and timebase visible, and the meter reading that surprised you. A scope shot with no volts/div or timebase shown helps nobody — include the settings. Post your captures with settings visible. Tag with oscilloscope, multimeter or debugging.
  • Robu, Evelta, Mouser, Stack, SP Road — sourcing tips and pricing

    1 1
    1 Topics
    1 Posts
    A
    Buying parts in India is easy once you know where to look — and expensive when you don't. These are starting points the community actually uses. Reply with your own finds and corrections; prices and stock change constantly. Online stores Robu.in — broad catalogue, dev boards, sensors, modules, kits. Good first stop for project builds. Evelta — components and modules with dependable stock for repeat orders. Element14 / Mouser India — authorised distribution. When the part must be genuine (precision sensors, ICs for anything shippable), buy here and pay the premium knowingly. General marketplaces — fine for kits, tools, enclosures, and jellybean parts. Check seller ratings; expect clones. Offline markets (worth a pilgrimage) SP Road, Bengaluru — the classic mile of component shops; bargaining expected, testing before buying normal. Lamington Road, Mumbai — same energy on the west coast, strong on tools and test gear too. Chandni Chowk (Bhagirath Palace), Delhi — wholesale-scale, best when buying in quantity. Ritchie Street, Chennai — the south's equivalent for parts and instruments. Buying tips that save money and boards Clone dev boards are fine; clone sensors are a gamble. A generic ESP32 board works. A suspiciously cheap "BMP280" may be a relabelled different sensor with wrong calibration — buy sensors that matter from trustworthy sellers. No-name lithium cells and chargers are a safety issue, not a bargain. Buy branded cells with protection, and never charge unattended on a sketchy module. Bundle to beat shipping. A ₹40 part with ₹80 shipping hurts; keep a running BOM and order together. Keep the GST invoice. You'll want it for college reimbursements, company expenses, and warranty claims. Reply with shops you've personally ordered from — what arrived fast, what arrived wrong.
  • Curated reading list for embedded, RTOS, IoT, C, and electronics

    1 1
    1 Topics
    1 Posts
    A
    Curated by people who read them — not an algorithm. One book finished beats ten bookmarked. Reply with what a resource taught you, not just its name. Books (read in this order) Making Embedded Systems — Elecia White. The single best "how the job actually works" book: hardware/firmware boundary, interviews with working engineers, debugging war stories. Start here. Test-Driven Development for Embedded C — James Grenning. Writing firmware you can trust, with host-side tests running before hardware exists. Transforms how you structure C. The C Programming Language — Kernighan & Ritchie. Thin, dense, timeless. The language reference every embedded engineer should have worked through at least once. Official documentation (primary sources beat tutorials) ESP-IDF Programming Guide — the framework reference; read the peripheral and FreeRTOS sections for your chip, not random blogs first. ESP32 Technical Reference Manual — the 600-page truth about your silicon: registers, clock trees, and errata. Intimidating, indispensable. Sites & series All About Circuits — electronics fundamentals explained patiently, with a textbook-grade volume set free online. EEVblog — teardowns and rants that teach measurement technique and design scepticism by example. HiveMQ MQTT Essentials — the clearest free walkthrough of MQTT concepts, one idea per short article. A note on links: titles only, deliberately — search the current edition yourself so you never land on a stale mirror. Reply with your own recommendations and one line on what each taught you.