Transistor Curve Tracer




I've always wanted a transistor curve tracer. It's the best way of understanding what a device does.Having built and used this one, I finally understand the difference between the various flavours of FET.

It's useful for

  • matching transistors
  • measuring the gain of bipolar transistors
  • measuring the threshold of MOSFETs
  • measuring the cutoff of JFETs
  • measuring the forward voltage of diodes
  • measuring the breakdown voltage of Zeners
  • and so on.

I was very impressed when I bought one of the wonderful LCR-T4 testers by Markus Frejek and others but I wanted it to tell me more about the components so I started to design my own tester.

I began by using the same screen as the LCR-T4 but it doesn't have a high enough resolution so I changed to a 320x240 2.8" LCD. It happens to be a colour touch-screen which is nice. The curve tracer runs on an Arduino Pro Mini 5V Atmega328p 16MHz and is powered by 4 AA cells.

Step 1: How to Use It

When you switch on the curve tracer, the main menu screen is displayed.

Select the kind of device by touching one of "PNP NPN", "MOSFET" or "JFET". You can test diodes in the "PNP NPN" mode.

Put the Device Under Test (DUT) into the ZIF socket. The menu screen shows you which pins to use. PNPs, p-channel MOSFETS and n-channel JFETS go in the left side of the socket. NPNs, n-channel MOSFETS and p-channel JFETS go in the right side of the socket. Close the ZIF socket.

After a second or so, the tester will realise that it has a component and will start to draw the curves.

For a PNP or NPN transistor it plots Vce (the voltage between the collector and emitter) versus the current flowing into the collector. A line is drawn for each different base current - e.g. 0uA, 50uA, 100uA, etc. The gain of the transistor is shown at the top of the screen.

For a MOSFET it plots Vds (the voltage between the drain and source) versus the current flowing into the drain. A line is drawn for each different gate voltage - 0V, 1V, 2V, etc. The turn-on threshold of the FET is shown at the top of the screen.

For a JFET it plots Vds (the voltage between the drain and source) versus the current flowing into the drain. A line is drawn for each different gate voltage - 0V, 1V, 2V, etc. With depletion JFETs, current flows when the gate voltage is equal to the source voltage. As the gate voltage is changed to be further from the drain voltage, the JFET turns off. The cut-off threshold of the FET is shown at the top of the screen.

The most interesting part of a MOSFET or JFET curve is around the turn-on or cut-off voltage plus or minus a few hundred mV. In the main menu, touch the Setup button and the Setup screen will be shown. You can select the minimum and maximum gate voltage: more curves will be drawn in that region.

For a PNP or NPN transistor, the Setup screen allows you to select the minimum and maximum base current

With diodes, you can see the forward voltage and with Zeners, the reverse breakdown voltage. In the image above, I've combined the curves of several diodes.

Step 2: How It Works

Let's consider an NPN transistor. We're going to draw a graph of the voltage between the collector and emitter (x-axis is Vce) versus the current flowing into the collector (y-axis is Ic). We'll draw one line for each different base current (Ib) - e.g. 0uA, 50uA, 100uA, etc.

The emitter of the NPN is connected to 0V and the collector is connected to a 100ohm "load resistor" and then to a voltage that slowly increases. A DAC controlled by the Arduino sweeps that test voltage from 0V to 12V (or until the current through the load resistor reaches 50mA). The Arduino measures the voltage between the collector and emitter and the voltage across the load resistor and draws a graph.

This is repeated for each base current. The base current is generated by a second 0V-to-12V DAC and a 27k resistor. The DAC produces 0V, 1.35V (50uA), 2.7V (100uA), 4.05V (150uA), etc. (Actually, the voltage has to be a little higher because of Vbe - assumed to be 0.7V.)

For a PNP transistor, the emitter is connected to 12V and the collector is connected to a 100ohm load resistor and then to a voltage that slowly decreases from 12V to 0V. The base current DAC steps down from 12V.

An n-channel enhancement MOSFET is similar to an NPN. The source is connected to 0V, the load resistor is connected to the drain and to a voltage sweeping from 0V to 12V. The DAC that was controlling the base current now controls the gate voltage and steps 0V, 1V, 2V, etc.

A p-channel enhancement MOSFET is similar to an PNP. The source is connected to 12V, the load resistor is connected to the drain and to a voltage sweeping from 12V to 0V. The gate voltage steps 12V, 11V, 10V, etc.

An n-channel depletion JFET is slightly more difficult. You would normally imagine the source connected to 0V, the drain connected to a varying positive voltage and the gate connected to a varying negative voltage. A JFET normally conducts and is turned off by a negative gate voltage.

The curve tracer can't generate negative voltages so the n-JFET drain is connected to 12V, the source is connected to a 100ohm load resistor and then to a voltage that slowly decreases from 12V to 0V. We want Vgs (the gate-source voltage) to step from 0V, -1V, -2V, etc. We want Vgs to remain constant as Vds (the drain-source voltage) varies. So the Arduino sets the voltage at the load resistor then adjusts the gate voltage DAC until Vgs is the required value. It then sets a new voltage at the load resistor and again adjusts the gate voltage, etc.

(The curve tracer can't measure the voltage applied to the gate but it knows what it's told the DAC to do and that's accurate enough. Of course, this only measures the negative-gate part of the JFET response; if you want to see the positive-gate part, treat it as a MOSFET.)

A p-channel depletion JFET is treated similarly but the 0-to-12V values are all inverted.

(The curve tracer does not specifically deal with depletion MOSFETs or enhancement JFETs but you could treat them as depletion JFETs and enhancement MOSFETs.)

Once it has completed the graph the curve tracer calculates the gain, threshold or cut-off of the transistor.

For bipolar transistors, the Arduino looks at the average spacing of the horizontal lines of the curves. As it draws the curve for base current, it notes the collector current when Vce is equal to 2V. The change in collector current is divided by the change in base current to give the gain. The gain of a bipolar is a vague concept. It depends on how you measure it. No two makes of multimeter will give the same answer. Generally, all you're asking is "is the gain high?" or "are these two transistors the same?".

For MOSFETs, the Arduino measures the turn-on threshold. It sets the load voltage to 6V then gradually increases Vgs until the current through the load exceeds 5mA.

For JFETs, the Arduino measures the cut-off voltage. It sets the load voltage to 6V then gradually increases (negative) Vgs until the current through the load is less than 1mA.

Step 3: The Circuit

Here is a brief description of the circuit. A more complete description is in the attached RTF file.

The curve tracer needs three voltages:

  • 5V for the Arduino
  • 3.3V for the LCD
  • 12V for the test circuit

The circuit must convert make these different voltages from the 4 AA cells.

The Arduino is connected to a 2-channel DAC to produce the various test voltages. (I tried using the Arduino PWM as a DAC but it was too noisy.)

The DAC produces voltages in the range 0V to 4.096V. These are converted into 0V to 12V by op-amps. I couldn't find any through-hole rail to rail op-amps that can source/sink 50mA, so I used an LM358. The output of an LM358 op-amp cannot go higher than 1.5V below its supply voltage (i.e. 10.5V). But we need the full range of 0-12V.

So we use an NPN as an open-collector inverter for the output of the op-amp.

The advantage is that this home-made "open-collector op-amp" output can go right up to 12V. Feedback resistors around the op-amp amplify the 0V to 4V from the DAC to 0V to 12V.

The voltages at the Device-Under-Test (DUT) vary between 0V and 12V. The Arduino ADCs are limited to 0V to 5V. Potential dividers do the conversion.

Between the Arduino and the LCD are potential dividers that drop 5V to 3V. The LCD, the touch screen and the DAC are controlled by the SPI bus.

The curve tracer is powered from 4 AA cells which give 6.5V when new and can be used down to around 5.3V.

The 6V from the cells is dropped to 5V with a very low dropout regulator - a HT7550 (if you don't have one then a 5V zener and a 22ohm resistor is not too much worse). The current consumption of the 5V supply is around 26mA.

The 6V from the cells is dropped to 3.3V with a low-dropout regulator - the HT7533. The current consumption of the 3.3V supply is around 42mA. (A standard 78L33 would work but it has a 2V dropout so you'd have to throw away your AA cells sooner.)

The 6V from the cells is boosted to 12V with a SMPS (Switched Mode Power Supply). I simply bought a module from eBay. I had real trouble finding a decent converter. The bottom line is, don't use an XL6009 converter, it's an absolute menace. As the battery goes flat and falls below 4V the XL6009 goes crazy and produces up to 50V which would fry everything. The good one I used is:

It's tiny and is about 80% efficient. Its input current consumption is around 5mA when waiting for a DUT to be inserted and momentarily up to 160mA when drawing the curves.

As the AA cells are discharged the voltages vary, the software compensates by using reference voltages. The Arduino measures the 12V supply. The Arduino ADC uses its "5V" supply as a reference voltage but that "5V" is calibrated accurately against the Arduino's internal 1.1V reference voltage. The DAC has an accurate internal reference voltage.

I like the way the LCR-T4 has a button to turn it on and turns itself off automatically with a timeout. Unfortunately, the circuit introduces a voltage drop which I can't afford when powering from 4 AA cells. Even re-designing the circuit to use a FET wasn't sufficient. So I'm using a simple on/off switch.

Step 4: The Software

The Arduino sketch is attached here. Compile and upload it to the Pro Mini in the usual way. There are lots of descriptions of how to upload programs on the web and in other Instructables.

The sketch starts by drawing the main menu then waits for you to insert a component or touch one of the buttons (or send a command from the PC). It tests for component insertion once a second.

It knows you have inserted a component because, with the base/gate voltage set to half way (DAC = 128) and the load resistor voltage set to 0V or 12V, a current of several mA flows through one or other of the load resistors. It knows when the device is a diode because changing the base/gate voltage does not change the load current.

It then draws the appropriate curves and switches the base and load currents off. It then tests once a second until the component is unplugged. It knows the component is unplugged because the load current falls to zero.

The ILI9341 LCD is driven by my own library called "SimpleILI9341". The library is attached here. It has a standard set of drawing commands very similar to all such libraries. Its advantages over other libraries are that it works (some don't!) and it shares the SPI bus politely with other devices. Some of the "fast" libraries you can download use special timing loops and are upset when other, maye slower, devices are used on the same bus. It's written in plain C and so has smaller overheads than some libraries. A Windows program is attached which allows you to make your own fonts and icons.

Step 5: Serial Comms to PC

The curve tracer can communicate with a PC via a serial link (9600bps, 8-bit, no parity). You will need a suitable USB-to-serial convertor.

The following commands can be sent from the PC to the curve tracer:

  • Command 'N': trace the curves of an NPN transistor.
  • Command 'P': trace the curves of a PNP transistor.
  • Command 'F': trace the curves of an n-MOSFET.
  • Command 'f': trace the curves of a p-MOSFET.
  • Command 'J': trace the curves of an n-JFET.
  • Command 'j': trace the curves of a p-JFET.
  • Command 'D': trace the curves of a diode on the NPN side of the socket.
  • Command 'd': trace the curves of a diode on the PNP side of the socket.
  • Command 'A' nn: set DAC-A to the value nn (nn is a single byte) then return an 'A' to the PC. DAC-A controls the load voltage.
  • Command 'B' nn: set DAC-A to the value nn then return a 'B' to the PC. DAC-B controls the base/gate voltage.
  • Command 'X': continuously send ADC values back to the PC.
  • Command 'M': show the main menu.

When the curves are traced following one of the commands, the results of the curve are transmitted back to the PC. The format is:

  • "n": start a new plot, draw the axes, etc.
  • "m (x),(y),(b)": move the pen to (x),(y).
    • (x) is Vce in integer mV.
    • (y) is Ic in integer hundreds on uA (e.g. 123 means 12.3mA).
    • (b) is the base current in integer uA
    • or (b) is 50 times the gate voltage in integer mV
  • "l (x),(y),(b)": draw a line to pen to (x),(y).
  • "z": the end of this line
  • "g (g)": the end of the scan;
    • (g) is the gain, threshold voltage (x10) or the cut-off voltage (x10)

The values sent to the PC are the raw measured values. The Arduino smooths the values before drawing them by avreraging; you should do the same.

When the PC sends an "X" command, The ADC values are returned as integers:

  • "x (p),(q),(r),(s),(t),(u)"
    • (p) the voltage at the load resistor of the PNP DUT
    • (q) the voltage at the collector of the PNP DUT
    • (r) the voltage at the load resistor of the NPN DUT
    • (s) the voltage at the collector of the NPN DUT
    • (t) the voltage of the "12V" supply
    • (u) the voltage of the "5V" supply in mV

You could write a PC program to test other devices. Set the DACs to test voltages (using 'A' and 'B' commands) then see what the ADCs report.

The curve tracer only sends data to the PC after it has received a command as sending data slows down the scan. It also no longer tests for the presence/absence of a component. The only way to turn off the curve tracer is to send an 'O' command (or to remove the battery).

A Windows program is attached which demonstrates sending commands to the curve tracer.

Step 6: Building the Curve Tracer

Here are the major components that you'll probably need to buy:

  • Arduino Pro Mini 5V 16MHz Atmel328p (£1.30)
  • 14pin Zif Socket (£1)
  • MCP4802 (£2.50)
  • HT7533 (£1)
  • LE33CZ (£1)
  • IL9341 2.8" Display (£6)
  • 5V to 12V boost Power Supply (£1)
  • 4xAA cell battery holder (£0.30)

Search eBay or your favourite supplier. That's a total of around £14.

I got my display here:

And the boost SMPS here:

The remaining components are things you probably have already:

  • BC639 (3 off)
  • 100nF (7 off)
  • 10uF (2 off)
  • 1k (2 off)
  • 2k2 (5 off)
  • 3k3 (5 off)
  • 4k7 (1 off)
  • 10k (7 off)
  • 27k (1 off)
  • 33k (8 off)
  • 47k (5 off)
  • 68k (2 off)
  • 100R (2 off)
  • Slide Switch (1 off)
  • LM358 (1 off)
  • stripboard
  • 28-pin IC socket or SIL header
  • nuts and bolts

You will need the usual electronics tools - soldering iron, cutters, solder, odd pieces of wire, etc. - and a USB-to-serial convertor to program the Arduino.

The curve tracer is built on stripboard. If you're the sort of person who wants a curve tracer, you will already know how to lay out stripboard.

The layout I used is shown above. Cyan lines are copper on the back of the stripboard. Red lines are links on the component side or are the extra-long leads of the component. Curved Red lines are flexible wire. Dark blue circles are breaks in the stripboard.

I built it on two boards, each 3.7" by 3.4". One board contains the display and the tester circuit; the other board has the battery holder and the 3.3V, 5V and 12V supplies. I kept the low-voltage ("5V") and high-voltage ("12V") parts of the tester circuit separate with only high-value resistors crossing the frontier.

The two boards and the display form a triple-decker sandwich held together with M2 screws. I cut lengths of plastic tube to act as spacers or you could use ballpoin pen tubes, etc.

I only connected the Arduino Mini pins that I needed and only the ones on the sides (not at the top and bottom ends of the Mini PCB). I used short lengths of wire rather than the usual row of square pins that Arduinos are supplied with (the pins soldered to the PCB are square in the drawing). I wanted the Arduino to be flush against the stripboard because there's not a lot of height under the display.

The Arduino ProMini pinout is rather variable. The pins on the long edges of the board are fixed but the pins on the short edges differ between suppliers. The layout above assumes a board with the 6 programming pins with Gnd next to the Raw pin and with DTR next to Tx on the long edge. At the other end of the board are a row of 5 pins with 0V next to D9 and A7 next to D10. None of the short-edge pins are soldered into the stripboard so you can use loose wires if your ProMini is different.

Use a SIL header socket to hold the display. Or cut a 28-pin IC socket in half and use the pieces to make a socket for the display. Solder the square pins that are supplied with the display (or came with the Arduino) into the display. They're too fat to plug into a turned-pin socket - choose a socket that has the "spring clip" kind of pins. Some "spring clip" kind of IC sockets can only withstand half a dozen insertions/removals of the LCD so try to find good ones in your component drawer.

The LCD contains a socket for an SD card (which I didn't use). It is connected to 4 pins on the pcb. I used the pins and a piece of SIL header or IC socket to help support the LCD.

Notice that there are some links under the ZIF socket. Solder them in before you fit it.

I added a programming connector with Tx, Rx, Gnd and a reset button. (My USB-to-serial convertor doesn't have a DTR pin so I have to reset the Arduino manually.) I unsoldered the programming connector when the project was finished.

To protect the electronics, I made a cover from polystyrene sheet.

Files for the circuit in EasyPC format are attached.

Step 7: Future Development

It might be nice to produce curves for other components but which? It's not clear to me what extra infomation the curve of a thyristor or triac would tell me beyod what the LCR-T4 tester does. The LCR-T4 tester can even be used with opto-isolators. I've never used a depletion MOSFET or an enhancement JFET or a unijunction transistor and don't own any. I presume the curve tracer could treat an IGBT as a MOSFET.

It would be nice if the curve tracer could recognise a component automatically and say which pin is which. Ideally, it would then go on to produce the curves. Unfortunately, the way the DUT pins are driven and measured, that would require a lot of extra components and complexity.

A simpler solution is to copy the existing LCR-T4 tester circuit (it's open source and very simple) with a second Atmega processor. Extend the ZIF socket to 16-pin to give three extra pins into which the unknown component can be plugged. The new Atmega acts as a slave on the SPI bus and reports to the main Arduino Mini what it sees. (SPI slave sketches are available on the web.) The software of the LCR-T4 tester is available and looks well documented. There's nothing inherently difficult there.

The main Arduino displays the component type and a diagram of how to plug the component in to the curve tracer part of the ZIF socket.

I've attached a surface-mount layout which can be used with an Arduino ProMini or with a naked Atmega328p (in EasyPC format). If there is sufficient demand (and orders with money) I could produce a batch of SM PCBs Could you buy one from me ready built? Well yes, of course, but the price would be silly. The advantage of dealing with China is that so many nifty electronic modules can be bought so cheaply. The disadvantage is that it's not worth developing anything: if it's a success, it will be cloned. Nice as this curve tracer is, I don't see it as a viable business opportunity.



    • Make it Glow Contest 2018

      Make it Glow Contest 2018
    • Plastics Contest

      Plastics Contest
    • Optics Contest

      Optics Contest

    80 Discussions


    2 days ago

    My unit will employ
    Arduino Nano, L2722 and possibly the MCP4822 will be tested (JFETs
    near 0V Vds). Powering exclusively from external PS (no battery power needed) so 3 regulators
    12V, 5V and 3,3V will be used. Is there something which needs my
    special attention? What should be observed first? What the dividers
    47k/33k on A inputs? Now collecting parts (woow it takes time!), in
    the meantime any info will be appreciated!

    3 replies
    Peter Balchok1rr

    Reply 1 day ago

    Let's say you're using the L2722 to control the base of a transistor. According to the data sheet, the output of the L2722 can get to within 100mV of the 0V line which is good (I think that's what the data sheet says). But it can only get to within 0.5V of the 12V line. So if you're testing a germanium PNP then you might not be able to fully turn off the transistor.

    In reality, that might not be important but it's worth testing.

    If it turns out to be a problem then maybe there's some way of setting the emitter of the PNP to 0.5V below the 12V power line - say with a diode. Or maybe you could put a diode in the connection between the output of the L2722 and the base of the PNP so the base is 0.5V above the output of the L2722. The drop across a diode is very non-linear of course so you'd have to have some way of drawing a current through the diode. Or maybe the 0.5V will not be important.

    I was unhappy with my "open collector" op-amp design but it did allow the base voltage of a PNP to get very close to the 12V line.

    > What the dividers 47k/33k on A inputs?

    Just choose whatever gives you the voltage swing you need. The values are specified in the Ardiono sketch.

    Good luck.


    ok1rrPeter Balch

    Reply 1 day ago

    If I understand correctly our main problem is the op amp. A true rail-to-rail device
    with acceptable output current and slew rate would be the solution.
    What about Linear Technology's LT1632? We should pick up the most
    important parameters and select the suitable device. The most
    important is:

    - rail-to-rail (both In to V- and Output)
    - Vs span
    - slew rate
    - output current

    ... what else?

    Greetings from Prague,

    (OK1RR is a ham radio call sign)

    Peter Balchok1rr

    Reply 24 minutes ago

    Slew rate doesn't matter because we're measuring the DC characteristics of the transistor - you wait a few mS for everything to settle befor taking a reading.

    Rail-to-rail output is very convenient as it makes it possible to measure the transistor with Vbe and Vce close to zero. If you don't have rail-to-rail output then you have to find someother way of, say, offsetting the emitter voltage.

    The L1632 says it has "Large Output Drive Current" but the data sheet says 35-40mA. That's OK for small signal transistors but rather low for power transistors.


    Question 8 days ago

    Would be the source code of the .exe program shared? I need a linux application, no Windows here...

    Thank you so much,


    1 more answer
    Peter Balchok1rr

    Answer 7 days ago

    I write all my Windows programs in Delphi so it wouldn't be much use to you. You'd have to re-write it from scratch. It's not particularly well written - I was just hacking something together to test the Arduino s/w.

    Almost all of it is concerned with faking the Arduino screen layouts so I could design and test the screens on a PC (and produce the "screenshots" in the instructable). Any screen I/O is completely different in Windows and Linux so you'd have to rewrite all of that. The Delphi components that handle serial comms are different too and I think that the way Delphi does "multitasking" to interleave serial, mouse and keyboard is different.

    99% of any Windows/Linux/macOS/iOS program is user interface and the way each system handles it is different. I've never invested in any cross-platform development tools as none of my clients has ever asked for it.

    It would be a lot faster for you just to start again. The comms protocol is described in Step 5. Have you tried writing a Linux program to send commands and receive the data back?

    Which parts of my source do you think would help?



    Question 14 days ago

    Peter, would be worth to use the MCP4812 (10 bit) or MCP4822 (12 bit) DAC? Would it improve the accuracy?

    1 more answer
    Peter Balchok1rr

    Answer 13 days ago

    My thought is that for bipolar and MOSFET transistors the answer is no, not really.

    With the curve for collector current vs voltage, you'd get more points on the x-axis but I think it has enough points already.

    When setting the steps for base current, you could have lots more steps or they could be more finely specified but step size isn't a problem.

    The real problem with the graphs is noise - I take several readings and average them. I don't know where the noise comes from. I presume it's digital interference from the power. More bits in the DACs wouldn't help.

    With JFETs, you use the DACs to adjust Vgs and smaller steps might help (i.e. more DAC bits). But once again, the actual problem is noise. With JFETs, noise is particularly bad because noise in Vgs gets amplified by the FET.

    The best way to improve the circuit is to use the TCA0372 as discussed by mausi_mick below.


    Peter BalchDanielS1131

    Answer 5 weeks ago

    Yes. Any Arduino using an ATMEGA328P 16MHz 5Vshould be fine. I've only tried the Pro Mini myself.

    (Some old Arduinos used other chips or ran slower and some Pro Minis run at 3.3V.)


    DanielS1131Peter Balch

    Reply 4 weeks ago

    Thanks for the answer!
    Could it be possible for it to work with the photon particle?

    Peter BalchDanielS1131

    Reply 4 weeks ago

    The Photon Particle has enough (12-bit) ADC pins and digital pins and it has hardware SPI so it should do the job as well as an Arduino does. The software will be different, of course. I think the Photon Particle has only one DAC pin but the curve tracer needs two so you'd still need a separate DAC chip.


    Question 4 weeks ago

    Hi the IL9341 display cant be found in my city and I was checking Amazon and ebay and there is available. Any suggestions for a replaceable display??

    1 more answer
    Peter BalchDanielS1131

    Answer 4 weeks ago

    Search eBay for ILI9341(not IL9341) or for "2.8 LCD TFT". The cheapest I found was £3.70 from Hong Kong.

    If you're thinking of building one, look at mausi_mick's comments below. He reckons the TCA0372 is better than the "open-collector op-amp" design I used.



    Question 2 months ago


    Have you considered to add the Gate-charge curve? that is quite easy to make - but maybe the sample rate of the ADC could be an issue - must be less than 1us i presume... but in principle it is adding a 1mA current sourve on the drain and a switchable 1mA current source on the gate, measure the gate voltage while the gate charges up, each us reading will give the nc charge. :)

    5 more answers
    Peter BalchKasperJ8

    Answer 2 months ago

    I've been looking at high-speed ADC on the Arduino recently. It's possible to get rather poor quality ADC samples at 1Msps. You can get better quality samples at 100ksps - i.e. 10uS per sample - but they're not great.

    If we assume that a big power MOSFET has a gate charge of 100nC and you charge it at 1mA, it will be "full" after 100uS. So, at best, that would be 10 ADC samples - not really enough for a decent graph.

    A more typical MOSFET has a gate charge under 10nC so a Arduino is nowhere near fast enough at 1mA.

    If you could charge the gate at 10uA then it would be OK but I'm not sure how well that would work for the MOSFET. And you've got to worry about the Atmel's input impedance - say 100Mohm and 14pF.

    100Mohm wouldn't have much effect on the 10uA current. Shall we guess a gate capacitance of 5nF? (I know it's non-linear but we can guess an approximate value.) So 14pF is trivial. It looks to me like the ADC could measure the rising gate voltage OK.

    The question is, can you reasonably charge a gate at 10uA - most people discuss switching gates fast not slowly.

    Have you tried looking at it with an oscilloscope?

    Do you think my numbers are reasonable?


    KasperJ8Peter Balch

    Reply 2 months ago

    Hi -

    First i was thinking about some PSOC - it could incorporate all analog signal i presume - but has not that internal ADC in that speed - Then i sav the STM32F7 series, it has 3x2.4Msps and i think they can be combined... But i know it is not a trivial task... The PSOC approch with an external ADC was also a nice solution for less hardware... But the software need a lot of work...

    I think you numbers seems ok - i think it can be an issue to make a stable 10uA current generator... But i think mostly the traces are for comparing different mosfets. Another option i am not sure is present, is a pc interface to get the traces to a PC

    Peter BalchKasperJ8

    Reply 2 months ago

    The section "Step 5: Serial Comms to PC" describes the serial interface and has a Windows EXE that displays the curves. Or do you mean when looking at gate charge vs voltage? The serial interface allows primitive commands to set DAC values and read ADC results. You could use those to draw the gate charge graph. You may need to add other commands to turn the current source on/off.

    KasperJ8Peter Balch

    Reply 2 months ago

    Hi -

    First i was thinking about some PSOC - it could incorporate all analog signal i presume - but has not that internal ADC in that speed - Then i sav the STM32F7 series, it has 3x2.4Msps and i think they can be combined... But i know it is not a trivial task... The PSOC approch with an external ADC was also a nice solution for less hardware... But the software need a lot of work...

    Peter BalchKasperJ8

    Reply 2 months ago

    PSOC as in "Programmable System on a Chip" from Cypress? It's not something I've ever looked at.