... for beginners who are new to RF like me, and even the cheapest RF power Meters cost hundreds of RMB. For electronics enthusiasts who follow the principle of "spend when you should, save when you can", DIYing an RF power Meter is a great alternative. The first step WAs to define the functions and design the hardware circuit. To test RF power, a chip called a detector is required. I had not found a suitable option for a long time as it WAs my first time working with an RF detector, until I saw the power detection module on the E25-C test baseboard, which use ...

Definetly not, Dont switch to amps or move the red lead to the A/10A jack while your probes are on a live circuit. In A mode the Meter is basically a short; flipping to it or probing voltage with the lead in A can blow the fuse, make an arc, or worse. Set the Meter and leads with power off, break the circuit, insert the Meter in series, then power up. For mains, use a clamp Meter; for 12 V high-current systems be extra cautious or use a clamp/shunt. And always move the red lead back to V when you’re done to avoid the classic “next-time short.”

Not quite—a 6000-count Meter doesn’t extend the 2V range to 5.999V. The range is fixed by the multimeter, not the count. In the 2V range, both 2000- and 6000-count Meters typically max out at 1.999V. A 6000-count Meter would show up to 5.999V only if it's on a 6V range, not 2V. So, a higher count means better resolution, but the voltage range itself stays the same unless the Meter has a higher range setting.

This usually happens due to the high sensitivity of the multimeter’s continuity mode. Some Meters are designed to beep even with very low resistance, which means slight contact, moisture, or even nearby conductive surfaces can trigger a false beep. However, that's not the only cause. Sometimes, while testing components like Semiconductors or capacitors, residual charge or leakage paths within the component can also cause the Meter to falsely detect continuity. In such cases, the beep doesn't necessarily indicate a true short—it could just be the Meter reacting to a small voltage or current still present in the circuit.

@ankunegi The answer is on point but I think there's a mistake in your calculation. To calculate the duty cycle, we have to divide it by 255(the maximum value) and not 256(The total no. of steps). For example: A 2-bit PWM signal has 4 possible steps: 0,1,2 and 3 corresponding to 0%, 33.33%, 66.67% and 100% duty cycle. You get this by dividing by 3, not 4. If you divide it by 4, you will get 25%. Which means 0%, 25%, 50% and 75%. See, you are not getting 100% duty cycle in this case.

Hey, Note: UNO R3 supports 8-bit PWM resolution, not 10. Higher resolution means the PWM output can be more finely tuned, resulting in a smoother signal. This is particularly important in applications like motor control, LED dimming, and audio signal generation. 8-bit resolution means there are 256 possible duty cycle values (from 0 to 255). That's why the analogWrite(PWM pin, PWM value) takes values bw 0 and 255. In this case, increasing the duty cycle step by step corresponds to a change of approximately 0.4% (1/256) of the full-scale value. Whereas the 16-bit resolution means there are 65,536 possible duty cycle values (from 0 to 65,535).Each step in the duty cycle corresponds to a change of approximately 0.0015% (1/65,536) of the full-scale value. As much as the resolution is important, so does the frequency of the PWM signal. The increase in PWM resolution decreases the maximum PWM frequency possible for the same clock frequency. if UNO and ESP32 have the same clock frequency i.e., 16 MHZ. The maximum possible PWM frequency(16-bit) for ESP32 will only be 244 Hz. Whereas for UNO(8-bit), it is 62.5 KHz. For example, 16 MHz / 256 and 16 MHz / 65,536. EDIT: Hey everyone! Let’s clear up the confusion regarding PWM resolution and the difference between dividing by 2^n versus 2^n - 1 The Hardware Timer Perspective In fast PWM mode, the timer counts from 0 up to a “TOP” value and then overflows back to 0. For 8-bit PWM, TOP = 255. This gives you a counter range of 0–255 = 256 distinct counts. For 2-bit PWM, TOP = 3. This gives you a counter range of 0–3 = 4 distinct counts. Thus, in terms of raw timer ticks, there are 2^n counts per cycle. The Duty Cycle Perspective When calculating duty cycle, we typically use: Duty Cycle (%)= (Compare Register Value/TOP) ×100. For 8-bit PWM, you divide by 255 (TOP = 255), so the highest compare value 255 yields 100 % duty cycle. For 2-bit PWM, you divide by 3 (TOP = 3), so a compare value of 3 yields 100 % duty cycle. If you were to divide by 2^n directly (e.g., 256 for 8-bit), the maximum compare value (255) would give (255/256)x 100 =~ 99.6% which technically matches clock ticks but doesn’t align with the usual definition of 100 % on hardware PWM outputs. Why It Matters 0 % duty cycle: Compare Register = 0. 100 % duty cycle: Compare Register = TOP (which is 2^n - 1). Users generally expect that the maximum compare setting translates to the output being fully ON (i.e., 100 %). Summary The timer truly counts 2^n steps (from 0 to 2^n−1). However, to get a duty cycle percentage from 0 % to 100 %, you divide the compare value by 2^n - 1. That’s why for 8-bit PWM, you’ll see many references to dividing by 255, not 256.

Yes, the 0.6 V drop you’re seeing is the Meter’s burden voltage, which is the voltage lost across the DMM when it measures current. In mA mode, the Meter places a small internal shunt resistor (and often a fuse or protection components) in series with your circuit to sense current, and this resistance causes a voltage drop equal to V=I×Rmeter​. For example, a 0.6 V drop at 60 mA means the Meter adds about 10 Ω in series, which can significantly affect low-voltage circuits by reducing the actual voltage reaching your load. To minimize this, you can use an external low-value shunt resistor and measure the voltage across it with the DMM in voltage mode, then calculate current using I=V/RI = V/RI=V/R. Alternatively, use a dedicated low-burden current sense amplifier or sensor such as the INA219, a DC clamp probe that measures current without inserting resistance, or the Meter’s 10 A input (which usually has much lower internal resistance) if the current is within safe limits. These methods help keep the measurement accurate without disturbing the circuit’s operating voltage.

Hi everyone, While checking continuity with my multimeter, I sometimes get beeping sounds even when the probes aren’t actually touching the wires.It seems like a false reading.Could this be due to stray capacitance, interference, or a faulty Meter?

... of wire—it has very low resistance. If you try to connect it across a live circuit (like you would for voltage), you're basically shorting the power source, and that can result in Blown fuse in the Meter (if you're lucky), Arcs or sparks. So, If you dont WAnt that Always power off the circuit before measuring current. Break the circuit and insert the Meter in series, making sure the probes are in the correct ports—especially the high current port if you're measuring above ~200mA. Once everything's connected, power on the circuit, take your reading, and t ...

Decoupling capacitors are essential for stabilizing the power supply and suppressing noise in microcontroller and digital circuits. A common starting point is placing a 100 nF ceramic capacitor (X7R Type recommended) close to the Vcc and GND pins of each IC to handle high-frequency transients. To support sudden current demands and filter lower-frequency noise, it's also good practice to add a bulk capacitor—typically 1 µF to 10 µF—near the microcontroller or groups of ICs. The exact values depend on several factors, including the switching speed of the ICs, current consumption, and the quality of the PCB layout. Faster ICs may require additional smaller capacitors like 10 nF or 1 nF in parallel with the 100 nF to cover a broader frequency range. High-current circuits may benefit from larger bulk capacitors up to 47 µF. Proper placement is critical—capacitors should be located as close as possible to the power pins, with short, direct traces. Using a mix of capacitor values in parallel helps improve overall decoupling performance. While 100 nF is a solid default, evaluating layout and load conditions can help you fine-tune your choices for a more robust and reliable design.

Thermistors cost much less than the LM35 temperature sensor but require calibration due to their non-linear nature. At the same time, a thermistor is more accurate and precise(down to +/- 0.1°C) than an LM35(around +/- 0.5°C). LM35: Very easy to integrate with Arduino. You can read the output voltage directly using an analog pin, and with simple conversion (multiply by 100 to convert from mV to °C), you get the temperature. Thermistors: While they can be integrated, they often require additional components (like a resistor for a voltage divider) and more complex calculations to convert resistance to temperature. This can make them slightly more challenging to set up. Main Differences Feature LM35 Temperature Sensor Thermistor Type Integrated circuit (analog voltage output) Resistor (typically NTC or PTC) Output Outputs a linear voltage (10 mV/°C) Resistance changes non-linearly with temperature Temperature Range Typically -55 to +150 °C Varies, but generally -40 to +125 °C Accuracy Typically ±0.5 °C or better Can be very accurate, but depends on the Type and calibration Response Time Fast response time Generally fast but varies by design Ease of Use Simple to interface with Arduino (analog input) Requires more complex calculations for linearization Calibration Usually factory calibrated Often requires calibration and look-up tables for accuracy For most projects requiring precise temperature monitoring with reliable readings and ease of integration with Arduino, the LM35 is likely the best option. However, if you need the highest accuracy and can manage the additional complexity, consider using a thermistor P.S.: LM358 is an OP-AMP IC. LM35 is a temperature sensor.

I’ve seen WArnings about using the current (amp) setting on a multimeter, and I WAnt to be cautious. I understand that to measure current, the Meter has to be placed in series with the load. But I’m unsure about the risks involved when doing this on a live circuit, especially with higher voltages like AC mains or even 12V DC systems with decent current. Is it safe to switch to the amp mode while the circuit is powered?

... gives inaccurate results. 2. Discharge the capacitor safely: 3. Use a resistor (e.g., 1kΩ, 1W) across the leads. 4. Avoid shorting large electrolytics directly — they can spark or get damaged. 5. Set your multimeter to capacitance mode (⏀). 6. Connect the probes to the capacitor leads. Polarity doesn't matter for film or ceramic caps; for electrolytics, follow Meter instructions. 7. WAit a few seconds for the reading to stabilize — especially for high-value caps. Hope this helps!

Yes, definitely discharge the capacitor first — especially if it's a high-voltage one. A charged cap can damage your multimeter or give you completely wrong readings. To discharge it, you can short the leads using a resistor (like 1kΩ or 10kΩ), or a screwdriver with an insulated handle if it's a small electrolytic (nothing high voltage though — not safe). Also, for accurate readings: Take the capacitor out of the circuit if you can. In-circuit measurements are often wrong because of parallel components. Let the multimeter settle for a few seconds, especially with large caps. Make sure your test leads are making good contact. If your Meter has a "zero" or "rel" mode, use that to cancel out stray capacitance from the probes. And keep in mind, these DMM readings are just a ballpark — they won’t tell you if the cap has high ESR or leakage. For that, you'd need an ESR Meter.