SMD MOSFET to power down my SMD H-Bridge

PS - don't forget to add some good decoupling capacitors between the source terminal of the P-channel mosfet and the ground connection of the H-bridge.

Alternatively, pick a mosfet with a higher Vgs rating but designed for 5V gate drive, such as TSM2313CX.

...still looking for something at Digikey. I can't get the one you mentioned at Digikey, and at Mouser it's a non stocked item which you've gotta order 15000 of…
Digikey's filtering system doesn't have the criteria of Vgs, so I'm having trouble selecting one. Once I find something I'll post my updated schematic.

Perhaps PMV48XP then?

dc42:
Perhaps PMV48XP then?

Thanks! Here's what I came up with...
Is R1 needed? I usually put something like that to make sure the motor is off while the Arduino boots up.
So nothing is needed between the Arduino pin and the gate of the BS1338?
Sure appritiate all the help!

I'll be glad to go this route rather than just a relay.

R1 is worth including. Its purpose is to ensure the mosfet is kept off when the system is powered up but the Arduino pin has not yet been configured as an output. It isn't needed if the pin feeds a BJT, but then you need a series resistor instead.

Looks OK to me. The Vgs rating of that P-channel mosfet is only 8V, uncomfortablly close to the 6V drive it is getting, so it is probably better to spit the 2K2 resistor into 2 x 1K and drive the gate from the junction of the two. Alternatively, pick a mosfet with a higher Vgs rating but designed for 5V gate drive, such as TSM2313CX.

I have changed from a 6 volt motor supply to a 9 volt supply, (and tapping off 4.5v for the 328 chip), but I don't understand this Vgs thing, so will this schematic still work to turn on/off Vcc to my motor driver chip?
Will I still need to have the 2k2 resister split into 2 1k resistors? I don't understand thus part.
Thanks.

Running from 9V, you definitely need R1, R2 to be 2 x 1K. However, your schematic is wrong. They need to be in series, not in parallel, and the gate drive to the P-channel mosfet needs to be taken from the junction of the two.

I would connect the 100nF capacitor to the source terminal of the P-channel mosfet instead of the drain terminal, and put a much larger electrolytic capacitor (e.g. 1000uF) in parallel with it. Position the P-channel mosfet and capacitors close to the 9986, and keep the traces connecting these 4 components short.

OK! I think I've got it. I made the schematic on eagle, trying to make it all clear so I could get a second opinion on it. If you could note that it looks okay, and that the mosfet are connected to the correct gates. I've included datasheets for the components...
thanks again,

BSS138W N Channel Mosfet:
http://www.diodes.com/datasheets/ds30206.pdf

PMV48XP P Channel Moseft:
http://www.nxp.com/documents/data_sheet/PMV48XP.pdf

Si9986 H-Bridge
http://www.vishay.com/docs/70007/si9986.pdf

As I tried to make clear in my previous reply, I think you should omit C3. Otherwise, every time you turn on the P-channel mosfet, there will be a large surge of current through the mosfet as C1 charges. If you do decide to keep C3, then you can omit C1 but I think you should also deliberately slow down the turn-on speed of the P-channel mosfet by connecting a capacitor of about 10nF in parallel with R2.

You will need to make sure that the 2 input signals to the 9986 are low before you turn off the P-channel mosfet, and remain low until after you have turned it on.

I will just omit C3. I didn't realize it was a problem. I added C1 thinking that was what you meant to do. C3 is just what I put next to all chips I use as a decoupling cap. I didn't know it was interfering with the P channel MOSFET. Thanks for explaining that. I kinda understand it now.
I'll be sure to turn the h bridge signals off before turning off the P channel.
Thanks!

On the same project, I need to turn off the Vcc to the DS3234 RTC chip. If I should start a new thread for that let me know.
The 3 chips in my project are:
Atmega328P-AU (first time to boot load the SMD variant)
si9986 H-Bridge
DS3234 RTC

Vcc for the Atmega328 & DS3234 is 4.5v (3 C cells)
...trying to last a year on batteries, I will power down the Atmega328P, and have the alarm from the DS3234 interrupt wake it up. But if the DS3234 has Vcc it uses a lot of current. If I turn Vcc off, it uses only 1-2 uA from Vbatt (a coin cell battery).
So I need to "disconnect" Vcc from the DS3234. Would this same technique I used on the si9986 work?

SouthernAtHeart:
I will just omit C3. I didn't realize it was a problem. I added C1 thinking that was what you meant to do. C3 is just what I put next to all chips I use as a decoupling cap. I didn't know it was interfering with the P channel MOSFET. Thanks for explaining that. I kinda understand it now.
I'll be sure to turn the h bridge signals off before turning off the P channel.
Thanks!

Just bear in mind that C1 is effectively the decoupling cap for the H-bridge, so it should be close to the chip and the traces between it, the chip and the P-channel mosfet should be kept short. If you are making a PCB, then I suggest you make a space for C1 anyway (and a capacitor in parallel with R2), just in case there are any problems with noise pickup when the mosfet is off.

SouthernAtHeart:
On the same project, I need to turn off the Vcc to the DS3234 RTC chip. If I should start a new thread for that let me know.
The 3 chips in my project are:
Atmega328P-AU (first time to boot load the SMD variant)
si9986 H-Bridge
DS3234 RTC

Vcc for the Atmega328 & DS3234 is 4.5v (3 C cells)
...trying to last a year on batteries, I will power down the Atmega328P, and have the alarm from the DS3234 interrupt wake it up. But if the DS3234 has Vcc it uses a lot of current. If I turn Vcc off, it uses only 1-2 uA from Vbatt (a coin cell battery).
So I need to "disconnect" Vcc from the DS3234. Would this same technique I used on the si9986 work?

The DS3234 takes less than 1mA. Power it from an Arduino output pin (possibly the same one that is controlling the power to the H-bridge), through a 150 ohm resistor, and put a decoupling capacitor between its Vcc and ground. Make sure you drive the 3 SPI control signals to it LOW before you power it off.

Thanks! I should've known that. In all the details of powering down the H bridge. I forgot.
I'll post my complete schematic here in a few days.
Trying to check anything that might draw current I thought about the 10K pull-up resistor on pin 1 of the Arduino. 5v through a 10K resistor = 500 uA. But maybe there's a lot more resistance in the Arduino chip when I put it to sleep?

The pullup on the reset pin won't draw any current, unless something else pulls the pin low.

Ok, thanks.

Adding a 16x2 LCD in low quiescent mode

I got the RTC DS3234 added into my schematic. One more thing I'm going to need is an LCD screen to enable the user to set the date/time.
For all the more it'll be used (probably once in 10 years if the coin cell last as long as they say they do), I won't even bother with the back light. And data sheets I've looked at are showing Vcc for LCDs to only be 1-2 mA, so I can power that from a digital pin, too. Would a 150 ohm resistor be good between the I/O pin and the Vcc on the LCD?

What about the 6 I/O pins controlling the LCD? I know they're a kind of communication lines, but I just use a liquid crystal library to control them. I'll likely be losing some current through them? After the user is done setting the time, I could disconnect the LCD, only I don't see a LCD.end() function only the LCD.begin(). Will the be any power consumption from this connection?
thanks.
PS. I've read some threads about powering off the backlight, but what I need to do is power off the whole LCD.

SouthernAtHeart:
One more thing I'm going to need is an LCD screen to enable the user to set the date/time.
For all the more it'll be used (probably once in 10 years if the coin cell last as long as they say they do), I won't even bother with the back light.

Then get a reflective mode LCD display, otherwise you may find the LCD display very hard to read without the backlight.

SouthernAtHeart:
And data sheets I've looked at are showing Vcc for LCDs to only be 1-2 mA, so I can power that from a digital pin, too. Would a 150 ohm resistor be good between the I/O pin and the Vcc on the LCD?

Yes, that's what I do.

SouthernAtHeart:
What about the 6 I/O pins controlling the LCD? I know they're a kind of communication lines, but I just use a liquid crystal library to control them. I'll likely be losing some current through them? After the user is done setting the time, I could disconnect the LCD, only I don't see a LCD.end() function only the LCD.begin(). Will the be any power consumption from this connection?

You need to drive all the pins connected to the LCD low before turning off its power, then they won't draw any current.

You need to drive all the pins connected to the LCD low before turning off its power, then they won't draw any current.

They will already be set from the LCD.begin() function. What will I need to do to turn them low, just digitalWrite(pin, LOW)?
Or will I first need to use pinMode(pin, OUTPUT)?
thanks.

SouthernAtHeart:
What will I need to do to turn them low, just digitalWrite(pin, LOW)?

Yes. BTW there is a problem with the LiquidCrystal library: it makes a call to the begin() function in the LiquidCrystal constructor (a very silly thing to do IMO, and completely unnecessary because you should call begin() in setup). So you should preferably patch the LiquidCrystal library source file to remove this call, to avoid feeding power through the I/O connections before you power up the LCD.