The second issue could be a software issue and the first could be a driver issue, so I’d start by reinstalling Windows and installing the latest driver for your specific GPU
The drains in the 8205 MOSFET are connected together internally. In a DW01 circuit, they are not connected to anything else.
One MOSFET stops the battery from charging and the other stops it from discharging.
Yes that I found as well but have/had trouble understanding why it would be built like this. Also why a MOSFET would be designed internally like this. If you want more power capability you’d get a bigger MOSFET rather than two tiny ones in parallel right?
It’s related to the internal body diode of the N channel mosfet, so two of them are in series but reversed. When one MOSFET is activated, current may flow easily in one direction but be reduced by the body diode of the other. When both are activated, current may flow easily in either direction.
It seems they don’t really prevent discharging or charging separately due to the body diodes but they can cut off the battery alltogether.
The MOSFETs are in series, but in opposite polarities. Two MOSFETs are needed to block current in both directions.
The DW01 uses the voltage drop across the MOSFETS to measure the current. The overcurrent threshold voltage is fixed at 150mV. Using a larger MOSFET that has a lower RDS(on) will increase the current limit.
While 60/40 is a joy to work with, I gave SAC305 a shot and it’s been totally fine for my uses with hobby electronic projects. You need to run your soldering iron hotter so it’ll be rougher on your iron’s tips, but I haven’t noticed much difference in ware, etc.
As a hobbyist, contributing to junk with lead in the world is something that’s been bugging me for some time. Additionally, it feels silly but there’s also a certain relief in not having to worry as much about contamination between my workbench and the rest of my environment.
If you haven’t already I’d also suggest getting some good flux. The Amtech NC-559-ASM has been working great for me.
That makes sense! In my case I actually needed to turn down my iron temps for the lead-free solder, previously had it ridiculously high from when I was trying to work with the cheap no-name solder.
This new lead free stuff is great, it comes with a price tag but it’s eons better than the no-name stuff IMO.
I have flux (syringe type) but I have no idea if I’m using it correctly, or if it’s just not that great. Haven’t noticed too much of a difference when soldering with it, apart from needing to brush off the circuit board with some contact cleaner to remove the residue
The navy gave me a spool like 5+ years ago. It has no label. They were going to trash it. I have no idea whatsoever what its composition is. It’s rosin core and that’s about all I know. I also have a few different gauges of safety wire and shear wire.
As long as it fully saturates i thiink it’s fine, i’ve personally only had issues with too slow switching when i switch the mosfet many times a second, or when i didn’t give a high enough voltage to fully saturate it, both of which usually led to a smoky mosfet
I finally bought some flux last year and was angry at myself for all the wasted years, proper solder is next on the list but I still have some cheap but usable solder that I want to use up first
You might want to check out OpenMV Cam which does some cool machine vision stuff and runs MicroPython.
I would probably start looking at OpenCV software for RasPi if you need more processing power.
I’ve been playing with ESP32 lately. I’m frankly kind of shocked at how well documented the API is and how well it all works. And it’s mostly open. I haven’t done anything with ESP32 Cams I bought, yet. No idea what is possible there or where to start.
Hopefully that helps.
Meanwhile I’m over here trying to wrap up a simple Bluetooth-enabled amp project for the last couple months lol. I should do more with machine vision.
I’ve noticed that outside of the fixed use cases and their combination, it is surprisingly difficult to make ESP32 do something. For example, i wanted to crop and apply simple filters on videos being streamed from an ESP32 Cam. Should be doable for a setup that can do facial recognition and AI stuff, right? Clearly not without writing your own libraries.
PS: to me RPi is overkill for all but the most intense compute requirements. So is the esp32 to a lesser degree. Don’t always need 240MHz dual core RISC with FreeRTOS and 2.4G radio…
I default to Arduino, usually attiny devices for simple, low power stuff. I am really liking the new TinyAVR line. Quicker programming, way more functionality, etc.
This is by far the best option for awkward connectors. You could even remove the pins and put the new cables in by opening the crimp and soldering the new ones without any splice.
From a conceptual perspective, very low quiescent current (aka idle/standby current) when unactivated is entirely achievable. What your design will need to do is assess how much each component will draw at idle, and if it’s too high, then you may need to have gates which turn off those high-draw components when idling.
From a cursory Google Search, the DFPlayer Mini datasheet shows a standby power of 20 mA, which far too high. A forum post shows that if the sleep mode is enabled using the serial interface, current drops to 0.4 uA. This is much better.
For the 555 itself, you mention an astable oscillating configuration, although I’m wondering what your intention for the 555 is. Ostensibly, the DFPlayer either needs a brief pulse to start playing (roughly “edge triggered”) or needs to be kept active for as long as the music should be playing (roughly “level triggered”). In either case, a 555 in a one-shot configuration would make sense, since an astable oscillator would imply the music would restart on its own every so often.
If you’re insisting on the 555, then you may not be able to access the sleep mode in the DFPlayer Mini. So your option might be to gate the DFPlayer so that it only gets Vcc power when the 555 supplies it, probably using a MOSFET. Alternatively, using a cheap microcontroller would let you control the DFPlayer Mini via serial. Your microcontroller could then also receive the signal from the vibration switch and come out of deep sleep to issue commands to the DDPlayer.
The ATTiny uC and MSP430 uC families can draw as low as microamps or even nanoamps in some low-power modes. So that neatly addresses the standby current.
What you’ll also have to assess is the active current, or how much the music player draws when it runs for however long. This should give you an idea of the total lifetime for your application on a single battery charge.
I haven’t done a course in electromagnetism yet, but as far as I understand, the ferrite core is just a piece of metal with no magnetic field, so moving it doesn’t induce a voltage
I think it would, however, change the inductance, just like the iron core in a transformer does
Depending on the power consumption, you may consider not using thermal relief while connecting thermal vias for the chip (component 57) to ground layers. But this may make soldering harder so do it only if needed. Thermal vias are so close that they form 3 long dents in 3v3 plane. It is good practice to put vias a little far apart so that planes can go through between vias. This can be important since sometimes lowest impedance can be obtained when current is flowing between those vias. If you don’t need to fit 15 vias there, you may consider reducing the number and separating them a bit. You can also check the design rules for minimum copper width and minimum via clearance for your manufacturer and enter them in your CAD tool.
The idea is to have an 8-channel power amplifier in one box …
I still have to source the right trafo, but one large one would be both lighter and cheaper (new) than, say 4 small ones. An argument to use multiple would potentially be that peaks on individual channels might have less impact on the other channels. Still working on it …
There will be loss in the process so you should go a little above. You also need to account for the efficiency curve of your power supply: is it best efficient at 80% load? 90% load? Can it handle 120% momentarily in case of a spike?
CV power supplies are the standard: constant voltage. It outputs say 12V, and trips when overcurrent. A CC supply would limit current to say, 20A. It does so by dynamically adjusting the voltage output to match that target. That’s a lot less common and usually used for battery charging or testing/troubleshooting. So, I guess, don’t plug it on a battery charger.
It should come with specs as to what input it can take. Follow the recommendations. If it says DC give it DC unless you’re absolutely sure of the circuit in there. The presence of a rectifier and caps doesn’t tell you much given it’s an amplifier, it could be part of the amp circuit for the MOSFETs and not its power supply.
Well, it says to use a toroidal transformer between 12V to 32V output, and looking at pictures of other people who bought it, it seems to work on AC directly, so I have high confidence that that’s what it is.
I’m slightly confused by your question. Are you trying to power two thingies off a twofer adapter, or are you trying to multiplex something?
It sounds like you’re just trying to do power so:
See how much each strip draws (either via data sheet of amps per meter times 0.69, or measure it) and if that amount exceeds the capacity of the adapters you want to use, it’ll either not work or shorten the life of the gizmos (or if it’s really cheap crap or you’ve gone way the heck over the capacity of any component it might catch fire a bit).
Note the current on the datasheet wont be linear per length, but for 27” chonks if should be close enough.
Edit: I see now your LEDs are 3V. Personally I’d recommend replacing them with 12 or 24V, or at least 5V to run properly on the 5V thing you’re plugging them into. Why did you go with 3V product?
I am assuming the LEDs are white (blue with yellow phosphor), which always have a roughly 3V voltage drop, this is just a physical fact. Some chips like those in LED bulbs have several LEDs in series for a voltage drop of 6/9/12/15/18 V but this is not the case here.
The vast majority of 5V strips have no step-down switching power supply (aka constant current buck converter) to reduce 5 V from the power rails to 3 V, instead just driving the LEDs with a resistor in series – it drops 2 V and if it’s a 100Ω resistor (usually labeled “101”), it lets 20 mA to the LED as per Ohm’s law. In practice, multiple LEDs are often in parallel to one resistor to save cost, in which case the current divides among them.
The strip may be RGB, in which case the LED voltages are 🔴1.8 V 🟢2.4-3.0 V 🔵3 V and pretty much the same applies. There may be an external controller but it usually just uses PWM to pulse the 5V rail of each color rather than adjusting the current. Individually cntrollable LED strips have a chip driving each LED, and there is just one power rail and serial data line between them.
Wow awesome, thank you for the info and resources! I have to follow the links later but I really appreciate the reply.
I don’t think OP’s strips have pixel control since in my experience you wouldn’t have a separate USB power line that bypasses the controller like OP is describing, but now am curious and hope they follow up.
askelectronics
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.