What does negative voltage mean for MOSFET?

Click For Summary
SUMMARY

The discussion centers on the use of a P-channel MOSFET, specifically the ZVP3306A, with a Raspberry Pi for controlling a PWM signal to a servo. The consensus is that this MOSFET is unsuitable due to its negative gate-source threshold voltage of -1.5V, which prevents proper operation with the Raspberry Pi's GPIO pins. Instead, participants recommend using an N-channel MOSFET with a low threshold voltage or a multiplexer to manage the PWM signals effectively.

PREREQUISITES
  • Understanding of MOSFET operation, particularly P-channel and N-channel types.
  • Familiarity with Raspberry Pi GPIO pin functionality and voltage levels.
  • Knowledge of PWM signal generation and control.
  • Basic circuit design principles, including the use of multiplexers.
NEXT STEPS
  • Research N-channel MOSFETs suitable for low-voltage logic applications.
  • Learn about using multiplexers for PWM signal management in circuits.
  • Explore the specifications and applications of the CD4016 and CD4066 analog switches.
  • Investigate the TI SN54AHC157 multiplexer for integrating multiple PWM sources.
USEFUL FOR

Electronics hobbyists, Raspberry Pi developers, and engineers designing circuits that require PWM control for servos or similar devices.

andrew700andrew
Messages
11
Reaction score
0
Hi, I'm planning on using a mosfet with my raspberry pi to controll a circuit, using the GPIO pins which can be set to +3.3V or GND but I'm having problems with choosing the type of MOSFET I will need. I've found the data sheet for a possibility here
http://www.diodes.com/datasheets/ZVP3306A.pdf
But I'm confused as to why all of the figures are negative. E.g. The Gate-Source threshold voltage is -1.5V. Does this mean I cannot use it wih my raspberry pi? What does negative voltage even mean in this case? I'm not sure how you can have a negative because doesn't that just mean the circuit is connected In reverse? So as you can see I'm rather confused and would really appreciate it if someone could explain what the negative values for voltage (and current) mean practically.
Thanks.
 
Last edited:
Engineering news on Phys.org
No you cannot use this MOSFET. This MOSFET is a P- channel one. And you need a N- channel type one with very low threshold voltage (logic level). Or use a BJT (NPN) that will drive the MOSFET.
 
Jony130 said:
No you cannot use this MOSFET. This MOSFET is a P- channel one. And you need a N- channel type one with very low threshold voltage (logic level). Or use a BJT (NPN) that will drive the MOSFET.

I need to use a P channel because the MOSFET will be controlling a PWM data line connected to a servo, so the load will always be on the GND side of the MOSFET. Is it only this specific one I cannot use, or P channels in general? Also, could you explain why this one is not going to work? Thanks for replying!
 
andrew700andrew said:
I need to use a P channel because the MOSFET will be controlling a PWM data line connected to a servo, so the load will always be on the GND side of the MOSFET. Is it only this specific one I cannot use, or P channels in general? Also, could you explain why this one is not going to work? Thanks for replying!
Can you provide a sketch of the circuit (with voltage levels) that you have in mind?
 
NascentOxygen said:
Can you provide a sketch of the circuit (with voltage levels) that you have in mind?

http://imgur.com/UwkOqvX

The 300k ohm resistor represents the servo and the two "raspberry pi GPIO" on the side are the pins I will use to controll which device can send PWM signals to the servo. This will either be the RX (radio reciever) which will continuously transmit a PWM signal or the raspberry pi which will only sometimes send a PWM signal, but when it does it will use the other two GPIO ports to disconnect the RX, then connect it's self to the servo data line and take over controll. At all other times the RX should have control of the servo. Also, I don't think the RX always uses a set max voltage for the PWM (depends on the voltage supply to the RX) so that's why I've written between "3.3 and 5v".
 
I guess what I'm also asking is are there an alternatives to create a circuit which allows me to use two PWM signals to drive one servo with a way to select which source I use, if the MOSFET idea is bad.
 
The MOSFET idea is not necessarily ruled out, it just hasn't been considered sufficiently thoroughly (speaking only for myself!). Do you have IC sockets you can solder to? There are available plenty of MOSFETs-on-chips and already fabricated data switches, I'll be surprised if something can't be found to do the job; the CD4016 or CD4066, for example. http://www.jaycar.com.au/products_uploaded/ZC4066.pdf
 
Last edited by a moderator:
andrew700andrew said:
I guess what I'm also asking is are there an alternatives to create a circuit which allows me to use two PWM signals to drive one servo with a way to select which source I use, if the MOSFET idea is bad.
Look into using a 2 input multiplexer to drive the gate of your FET.
 
donpacino said:
In your diagram you show the raspberry pi PWM on the source of the FET. That is wrong. the pwm signal should come through the gate of the FET. The same should occur with the signal from the receiver. You do NOT want to pull power from your pi or receiver.

In which case, will something like this work?
http://imgur.com/vmcR53y
The diodes will prevent the current shorting to ground at the GPIO. The problem is still this negative voltage thing and also, in the simulation I'm only getting 2.8V over the servo resistance even when is is really high. Is this due to the diodes? Also, I'll check out the other devices later.
 
  • #10
andrew700andrew said:
In which case, will something like this work?
http://imgur.com/vmcR53y
The diodes will prevent the current shorting to ground at the GPIO. The problem is still this negative voltage thing and also, in the simulation I'm only getting 2.8V over the servo resistance even when is is really high. Is this due to the diodes? Also, I'll check out the other devices later.
Do you know how a mosfet works?
 
  • #11
I recommend using nascent's solution, as it is a one package version of my solution, but you really shouldn't be doing this if you don't have a grasp on how fets work.
 
  • #12
I recommend using nascent's solution, as it is a one package version of my solution, but you really shouldn't be doing this if you don't have a grasp on how fets work.
 
  • #13
donpacino said:
In your diagram you show the raspberry pi PWM on the source of the FET. That is wrong. the pwm signal should come through the gate of the FET. The same should occur with the signal from the receiver. You do NOT want to pull power from your pi or receiver.
I don't see the problem. The control signal goes to the gate, the controlled signal is fed S to D.

But you multiplexer idea is good, using a half dozen NAND gates to make a basic multiplexer would be a fruitful exercise and is all that's needed.
 
  • #14
you should NEVER power a servo through the raspberry pi, it should come directly from the power source. in addition it is not a good design practice to have the gate of a ptype fet at a higher potential than the source
 
  • #15
donpacino said:
you should NEVER power a servo through the raspberry pi, it should come directly from the power source. in addition it is not a good design practice to have the gate of a ptype fet at a higher potential than the source
The servo input is 300kΩ, he's not powering the servo.
 
  • #16
donpacino said:
you should NEVER power a servo through the raspberry pi, it should come directly from the power source. in addition it is not a good design practice to have the gate of a ptype fet at a higher potential than the source

Ok, The 2 input multiplexer looks right, well at least the truth table on them seems to do what I'm looking for.

And the Raspberry pi won't be 'powering' the servo, the servo has 3 leads, one for +5V other GND and the third is the PWM control which is fine at 3.3V and can be controlled by the Pi, as I have already made it work.
 
  • #17
ohhh if that's the case then you don't need a fet at all. just the mux should do it
 
  • #18
I've found this http://www.ti.com/lit/ds/symlink/sn54ahc157.pdf to use as a MUX.

However, I'm confused about a few details:
1) What is the "Input clamp current" because I'm worried about the negative current there.
2) Do I need some sort of resistor on the Vcc to limit the current through the MUX. It says the continuous current though Vcc or GND is +-50mA, is this what I need to aim for (in which case I also need to know the resistance of the MUX itself through Vcc to calculate a current limiting resistor value) or is this what the current will be if I connect the MUX directly to a 3.3V supply and GND (i.e. no resistor is required)
3) Also, what are the (Ioh) High-level output current and (Iol) Low-level output current values mean? The High level is -4mA and the Low-level is +4mA, yet earlier in the datasheet it says that the Continuous output current is +-25mA?

Thanks.
 
  • #19
1. that is in the absolute maximum rating table. that means with vi<0 the input current will clamp at 20 mA
2. no you do not. like i said that is the max current draw without damaging the part will be +-50 mA. you should be able to calculate your current draw from the load to see if you lie within that range.
3. like i said the above table is absolute maximums for the part. The below is recommended maximums for specific operating conditions.
 

Similar threads

  • · Replies 5 ·
Replies
5
Views
2K
  • · Replies 42 ·
2
Replies
42
Views
5K
  • · Replies 6 ·
Replies
6
Views
2K
  • · Replies 6 ·
Replies
6
Views
2K
Replies
2
Views
2K
  • · Replies 28 ·
Replies
28
Views
6K
  • · Replies 10 ·
Replies
10
Views
6K
  • · Replies 5 ·
Replies
5
Views
4K
  • · Replies 6 ·
Replies
6
Views
2K
Replies
2
Views
2K