If you LIKE this, please HIT the LIKE 👍👍 button, subscribe, and hit the Bell 🔔🔔 👇 SUBSCRIBE TO CMTEQ CHANNEL NOW 👇 ua-cam.com/users/CMTEQ Buy me a cup of coffee: www.buymeacoffee.com/cmteq Donate on Paypal: www.paypal.com/donate/?hosted_button_id=GJH7BWNSJAV7N Become a Patreon: www.patreon.com/cmteq
Can't we just supply Vgs and use multimeter resistance measurement mode to measure Rds(on)? Can we use boost converter to increase Vgs to reduce the Rds?
Yes, You can but it won't be very accurate due to the Multi meter internal reistance, also measuring it while there's no current flowing will some important details of the power dissipation. Yes, if you are able to boost your VGS you can do so to reduce the power loss by reducing Rds(ON).
Thank-you very much for this helpfull description. My question is the value of current when making this test , where in datasheet we notice the RDS value @10v and 10A . If we got 2 transistor which are identical in ID & Vgs but with different Amp. noted in RDS test 10v@10A = 0.15 mohm 10v@100mA = 0.15 mohm.
I can't find anything on google with the part you supplied. To answer your question, if you want to replace a transistor with another one, just make sure that the voltage rating and drain current is high enough for your circuit. Same RDS is also great, but you can still use it even if RDS ON is higher, all you need is some form of a heat dissipation heatsink or anything.
I am planning on designing/making a simple cheap hobbyist targeted(open source if working good enough) mosfet tester. the idea is that it would test the mosfet. but with more goals: goal 1: testing the mosfet rds(on) for most general mosfets and displaying it on a screen, or through usb or serial. goal 2: testing the mosfet allowing to set the voltage for opening the gate. goal 3: testing the mosfet and outputting it to a libreofice calc dataset/graph so you can also make those curves you see in a datasheet, this is for both voltage on the gate, and for temperature as those affect it's performance heavily and are important, next to that unlike normal component testers which can test capacitance and such pretty relyable, as for making such graphs, the cheap options cost thousands of €'s) goal 4: also adding the other one of goal 3 whichever one wasn't chosen to add first. goal 5: making sure all is modular(this will be added in from the beginning of the development probably) goal 6: preventing the mosfet from being powered whenever it is being tested. goal 7: higher resolution and ccuracy goal 8: more and free open source use.(open source will be added more early as long as it works well enough and is cheap enough and there are no better options(which is why I am looking at options now, as if there are options it is better to just use or improve those, otherwise I make it, and try to make it good enough for free open source, making this tool just to counter the huge amount of fakes on the current day market, and to be be able to better use whatever parts I have)) and then perhaps some others later on. most of those mentioned above are easy actually, mostly just want to try to do them for cheap and autocontrolled by the controller
This is a brilliant idea, myself I have been thinking of developing a similar tool for myself. I made something similar without a display, not very fancy, mostly just for RDS ON and Testing if it's defective. Let me know if you need some collaboration on this open-source project.
@@CMTEQ sounds great, since with a project like this, base functionality should be super simple to reach(ofcource I already figured out how I would do it before even searching online and then checked online to see if there where better, more easy, or already done methods.(as in how I would do it for my use)), but it are things later on which really benefit from more people and reach. as for a screen, I mostly only planned on adding that for a opensource version so people can make cheap standalone tools. originally for myself I planned to just use serial or simulated usb keyboard input to read the values. main function is essentially to just have a simple cheap tool which can be used to see if mosfets are real or likely to be fake. and when doing that already it becomes quite easy to also add some other functions the normal budged mosfet testers don't have. ofcource for many things there are good cheap tools already, but most of them are inaccurate surrounding Rds(on) and also obviously can't trace such graphs as often they are meant as handy multi purpose component testers and not speciffically for things like mosfets or transistors. so would be great to work together. also what did you make for doing such tests? as in that perhaps that method might be quite usable already. I shall also explain roughly what I planned to do now. I planned to base it primarily upon the ESP32-C3 or RP2040(pi pico), however using arduino code primarily to make it easy to use other boards instead. I selected those 2 boards primarily because both have 12bit(4096) ADC resolution and multiple ADC pins. the pi pico is faster with 500ksps where the esp32-c3 only reaches 100ksps, both should be plenty of fast enough however. the pi pico also is faster and has PIO which might be usable, next to that it is super popular thus many people would already have them. the esp32-C3 however has wifi and bluetooth in it, this allows to do things like wireless terminal or interface to the module which can be very nice. I planned to just use a powerresistor and measure the voltage drop on the resistor to calculate current (optional) and the voltage drop on the mosfet to calculate the Rds(on). the mosfet will be pulsed on for a while and measurements taken. for the temperature measurements a heat sensor can be screwed to the mosfet and temperatures measured and mapped like that. as for the pulses, if the ADC proves fast enough for the used mosfets reaction time then it is possible to take multiple measurements when turning it on, even though that might be harder as for most mosfets they will probably both be to slow for measuring that. as for screen and interface and such. all such things which aren't the bare functionality would be in a way so that they can be easily added modular. either as their own files or copied in the main code by the user, some basic functions can perhaps be added by default and just enabled or disabled with a variable. as for calling the methods in a loop to make it easy, it is probably most easy to give them tiers and already add sections for them using comments, either tiers to abstract it and allow more options, or just things like input, processing and output. for example a screen function would be called after the calculations, and those would be called after the measurements. measurements however should first enable the mosfet, then wait a very short time before measuring and turn it off after measuring. I didn't properly design it out or to far yet however, so this is just how I currently plan on doing it. it uses microcontrollers instead of dedicated or analog hardware because microcontrollers are cheap and do not require as much manual soldering often(as you can get full development boards). less different parts makes it more easy to make and less easy to accidentally make a mistake.
Thanks for sharing your detailed approach-sounds like you're setting up a solid foundation! For my part, I’ve prototyped a basic MOSFET tester on a breadboard. It uses a resistor network to turn the MOSFET on and measure RDS(ON). Nothing fancy yet, as I haven’t integrated a microcontroller into it. What you’re doing is fantastic! I’d recommend using the ESP32 over the Pi Pico for its additional features like WiFi and Bluetooth, which can open up possibilities for a wireless interface or remote logging. While the Pico is great for raw speed and its PIO capabilities, the ESP32’s flexibility might serve your project better in the long run, especially for sharing data or controlling the device remotely. Once you’ve got the basics working, it’ll be straightforward to add a user interface, whether it’s a screen or wireless control. Also, consider adding a dedicated ADC chip with 16-bit resolution to improve measurement precision when interfacing with the ESP32. That might be a valuable enhancement for ensuring accurate RDS(ON) measurements, especially if precision becomes a bottleneck with the onboard ADCs. Looking forward to hearing how it evolves!
@@CMTEQ yes a dedicated ADC would indeed be usefull for greatly increased resolution. but first it should be working for as simple and cheap as possible, so all can use it. adding modular dedicated ADC support should be easy and can be usefull. as for the microcontroller, I will be using general C++ with arduino(altered C++) code. with that it should work with any microcontroller which is aduino compatible. as for the test, it is quite similar to the basic resistor test but then instead of using a dedicated volt meter it uses the microprocessor and automatically does the calculations and could do some special methods. in my case, the soldering is the main issue right now, not the design, but soldering properly also a connector for the mosfet with low losses, I guess in the end I will just use one of those general connectors like on a arduino, as for soldering, while I can solder it is winter now and as I solder outside most often when I have time either someone else is working there or it is already dark outside. perhaps I should start on a breadboard as well, avoided that for now fearing it might overheat.
for the TK100E08N1 you might pretty likely have a fake. as the datasheet mentions it should be on at around 4V, normally this means it is relatively close to the stated Rds on. however you got a value over 5 times higher. I didn't see a Rds(on) graph comparing it to voltage in the datasheet however, but a difference of 5.176 times at a point reffered to in the datasheet as being above the activation voltage and over half the max efficiency voltage is quite a lot. it is still possible it is a real one, especially if the datasheet is just being weird. I have seen such behaviours in some mosfets. but I recommend running it at a higher voltage then to test it.
@@CMTEQ yeah such test conditions can differ a lot. mostly since the datasheet mentions it being on from around 2 to 4 volts, so despite the Rds on being at 10v logic would assume they are either close or that there should be some some kind of linear like curve atleast(transistor) but for mosfets generally it turns on very rapidly from a certain point and then very slowly increase after that until the Rds point and then go down again. but different behaviour happens normally as well in some cases. just worth checking if it is real as there are many fakes these days(even though less famous chips are less often targeted). but next to that the chip doesn't have a Rds on to gate voltage graph. so might also be normal behaviour indeed. for that it is usefull to test that curve yourself since if that is normal then it means that it reacts very heavily to the gate voltage and that lowering it to 5v reduces the load it can handle by over 5 times.
If you LIKE this, please HIT the LIKE 👍👍 button, subscribe, and hit the Bell 🔔🔔
👇 SUBSCRIBE TO CMTEQ CHANNEL NOW 👇
ua-cam.com/users/CMTEQ
Buy me a cup of coffee: www.buymeacoffee.com/cmteq
Donate on Paypal: www.paypal.com/donate/?hosted_button_id=GJH7BWNSJAV7N
Become a Patreon: www.patreon.com/cmteq
Great video Sir really appreciate you sharing very helpful information 👍🏽🙏🏽
Wonderful, Thank you for the feedback. I'm Glad it was helpful!
Can't we just supply Vgs and use multimeter resistance measurement mode to measure Rds(on)?
Can we use boost converter to increase Vgs to reduce the Rds?
Yes, You can but it won't be very accurate due to the Multi meter internal reistance, also measuring it while there's no current flowing will some important details of the power dissipation.
Yes, if you are able to boost your VGS you can do so to reduce the power loss by reducing Rds(ON).
Thank-you very much for this helpfull description.
My question is the value of current when making this test , where in datasheet we notice the RDS value @10v and 10A .
If we got 2 transistor which are identical in ID & Vgs but with different Amp. noted in RDS test
10v@10A = 0.15 mohm
10v@100mA = 0.15 mohm.
Which MOSFET are you using? Please clarify your question a bit.
@@CMTEQ
ATP5015PVR & 5015PVFR
can any of them be used instead of the other .?
Note vaue of IDrain in Rds test .
Thank-you in advance .
I can't find anything on google with the part you supplied. To answer your question, if you want to replace a transistor with another one, just make sure that the voltage rating and drain current is high enough for your circuit.
Same RDS is also great, but you can still use it even if RDS ON is higher, all you need is some form of a heat dissipation heatsink or anything.
Really you are very kind and .
Excuse me the correct mosfet nos. are
APT5015PVR & APT5015PVFR.
I am planning on designing/making a simple cheap hobbyist targeted(open source if working good enough) mosfet tester.
the idea is that it would test the mosfet.
but with more goals:
goal 1: testing the mosfet rds(on) for most general mosfets and displaying it on a screen, or through usb or serial.
goal 2: testing the mosfet allowing to set the voltage for opening the gate.
goal 3: testing the mosfet and outputting it to a libreofice calc dataset/graph so you can also make those curves you see in a datasheet, this is for both voltage on the gate, and for temperature as those affect it's performance heavily and are important, next to that unlike normal component testers which can test capacitance and such pretty relyable, as for making such graphs, the cheap options cost thousands of €'s)
goal 4: also adding the other one of goal 3 whichever one wasn't chosen to add first.
goal 5: making sure all is modular(this will be added in from the beginning of the development probably)
goal 6: preventing the mosfet from being powered whenever it is being tested.
goal 7: higher resolution and ccuracy
goal 8: more and free open source use.(open source will be added more early as long as it works well enough and is cheap enough and there are no better options(which is why I am looking at options now, as if there are options it is better to just use or improve those, otherwise I make it, and try to make it good enough for free open source, making this tool just to counter the huge amount of fakes on the current day market, and to be be able to better use whatever parts I have))
and then perhaps some others later on.
most of those mentioned above are easy actually, mostly just want to try to do them for cheap and autocontrolled by the controller
This is a brilliant idea, myself I have been thinking of developing a similar tool for myself.
I made something similar without a display, not very fancy, mostly just for RDS ON and Testing if it's defective.
Let me know if you need some collaboration on this open-source project.
@@CMTEQ sounds great, since with a project like this, base functionality should be super simple to reach(ofcource I already figured out how I would do it before even searching online and then checked online to see if there where better, more easy, or already done methods.(as in how I would do it for my use)), but it are things later on which really benefit from more people and reach.
as for a screen, I mostly only planned on adding that for a opensource version so people can make cheap standalone tools.
originally for myself I planned to just use serial or simulated usb keyboard input to read the values.
main function is essentially to just have a simple cheap tool which can be used to see if mosfets are real or likely to be fake. and when doing that already it becomes quite easy to also add some other functions the normal budged mosfet testers don't have.
ofcource for many things there are good cheap tools already, but most of them are inaccurate surrounding Rds(on) and also obviously can't trace such graphs as often they are meant as handy multi purpose component testers and not speciffically for things like mosfets or transistors.
so would be great to work together.
also what did you make for doing such tests?
as in that perhaps that method might be quite usable already.
I shall also explain roughly what I planned to do now.
I planned to base it primarily upon the ESP32-C3 or RP2040(pi pico), however using arduino code primarily to make it easy to use other boards instead.
I selected those 2 boards primarily because both have 12bit(4096) ADC resolution and multiple ADC pins. the pi pico is faster with 500ksps where the esp32-c3 only reaches 100ksps, both should be plenty of fast enough however. the pi pico also is faster and has PIO which might be usable, next to that it is super popular thus many people would already have them.
the esp32-C3 however has wifi and bluetooth in it, this allows to do things like wireless terminal or interface to the module which can be very nice.
I planned to just use a powerresistor and measure the voltage drop on the resistor to calculate current (optional) and the voltage drop on the mosfet to calculate the Rds(on).
the mosfet will be pulsed on for a while and measurements taken.
for the temperature measurements a heat sensor can be screwed to the mosfet and temperatures measured and mapped like that.
as for the pulses, if the ADC proves fast enough for the used mosfets reaction time then it is possible to take multiple measurements when turning it on, even though that might be harder as for most mosfets they will probably both be to slow for measuring that.
as for screen and interface and such. all such things which aren't the bare functionality would be in a way so that they can be easily added modular.
either as their own files or copied in the main code by the user, some basic functions can perhaps be added by default and just enabled or disabled with a variable.
as for calling the methods in a loop to make it easy, it is probably most easy to give them tiers and already add sections for them using comments, either tiers to abstract it and allow more options, or just things like input, processing and output.
for example a screen function would be called after the calculations, and those would be called after the measurements.
measurements however should first enable the mosfet, then wait a very short time before measuring and turn it off after measuring.
I didn't properly design it out or to far yet however, so this is just how I currently plan on doing it.
it uses microcontrollers instead of dedicated or analog hardware because microcontrollers are cheap and do not require as much manual soldering often(as you can get full development boards). less different parts makes it more easy to make and less easy to accidentally make a mistake.
Thanks for sharing your detailed approach-sounds like you're setting up a solid foundation!
For my part, I’ve prototyped a basic MOSFET tester on a breadboard. It uses a resistor network to turn the MOSFET on and measure RDS(ON). Nothing fancy yet, as I haven’t integrated a microcontroller into it.
What you’re doing is fantastic! I’d recommend using the ESP32 over the Pi Pico for its additional features like WiFi and Bluetooth, which can open up possibilities for a wireless interface or remote logging. While the Pico is great for raw speed and its PIO capabilities, the ESP32’s flexibility might serve your project better in the long run, especially for sharing data or controlling the device remotely.
Once you’ve got the basics working, it’ll be straightforward to add a user interface, whether it’s a screen or wireless control. Also, consider adding a dedicated ADC chip with 16-bit resolution to improve measurement precision when interfacing with the ESP32. That might be a valuable enhancement for ensuring accurate RDS(ON) measurements, especially if precision becomes a bottleneck with the onboard ADCs.
Looking forward to hearing how it evolves!
@@CMTEQ yes a dedicated ADC would indeed be usefull for greatly increased resolution.
but first it should be working for as simple and cheap as possible, so all can use it.
adding modular dedicated ADC support should be easy and can be usefull.
as for the microcontroller, I will be using general C++ with arduino(altered C++) code. with that it should work with any microcontroller which is aduino compatible.
as for the test, it is quite similar to the basic resistor test but then instead of using a dedicated volt meter it uses the microprocessor and automatically does the calculations and could do some special methods.
in my case, the soldering is the main issue right now, not the design, but soldering properly also a connector for the mosfet with low losses, I guess in the end I will just use one of those general connectors like on a arduino, as for soldering, while I can solder it is winter now and as I solder outside most often when I have time either someone else is working there or it is already dark outside.
perhaps I should start on a breadboard as well, avoided that for now fearing it might overheat.
for the TK100E08N1 you might pretty likely have a fake.
as the datasheet mentions it should be on at around 4V, normally this means it is relatively close to the stated Rds on.
however you got a value over 5 times higher. I didn't see a Rds(on) graph comparing it to voltage in the datasheet however, but a difference of 5.176 times at a point reffered to in the datasheet as being above the activation voltage and over half the max efficiency voltage is quite a lot.
it is still possible it is a real one, especially if the datasheet is just being weird. I have seen such behaviours in some mosfets.
but I recommend running it at a higher voltage then to test it.
Thank you for picking it up, I will revisit it and double-check.
It could just be that the test conditions were not fully met as per the datasheet.
@@CMTEQ yeah such test conditions can differ a lot. mostly since the datasheet mentions it being on from around 2 to 4 volts, so despite the Rds on being at 10v logic would assume they are either close or that there should be some some kind of linear like curve atleast(transistor) but for mosfets generally it turns on very rapidly from a certain point and then very slowly increase after that until the Rds point and then go down again.
but different behaviour happens normally as well in some cases.
just worth checking if it is real as there are many fakes these days(even though less famous chips are less often targeted).
but next to that the chip doesn't have a Rds on to gate voltage graph.
so might also be normal behaviour indeed.
for that it is usefull to test that curve yourself since if that is normal then it means that it reacts very heavily to the gate voltage and that lowering it to 5v reduces the load it can handle by over 5 times.