depends on where you order. If you chose JLC (the part number I just gave you is from JLC), then you have to add that number as well. If you order somewhere else, I can’t help you with that
Updated:
Ah, okay!
@Mineotopia
what do you think might my projekt cost @ JLC fully assembled? i might buy 3 for the first try
In IRLZ34N datasheet the minimum Vgs they specified Rdson is 4V.
When you look at Fig 1 and Fig 2 the first line that looks switching it on almost perfectly is for Vgs=6V.
And the figures are “Typical Characteristics”. As Vgson is between 1V and 2V than rationale is to assume that charts are for transistors with Vgson=1.5V. So for those having Vgson=2V I would expect the same lines for 0.5V higher Vgs voltages. So I would assume to have every piece switched almost perfectly 7.5V would be enough.
And you are using 3V3 * 10/11 = 3V.
No one forces you to get it switched on perfectly but…
Don’t be too focused on Vgson being between 1V and 2V. It is enough for 250uA only drain current. So it is not a voltage when transistor is switched on, but when it starts to switch on.
In past to drive some ST Omni-FETs from 3V3 microcontroller I used AHCT gates to drive it with 5V and not 3V3.
Why not assign a label to every pin and then sort them alphabetically to completely obfuscate the schematic? You alredy did a good job with the label “GND”
Here are a few more comments.
- I believe c_out1 is on the wrong side of the inductor
- I don’t see why three diodes are needed from VBUS to VIN. One should be enough
- You should use 5K1 pulldowns on the CC1/CC2 lines in the usb-c connector for 5V.
- I don’t understand rpd13 + rpd17 where you have a resistor between two gnd?
- You should use the No Connect flag on unused pins
- Shield+gnd are usually connected in the USB connector
- The diodes in the usb-connector should not be schottky diodes but TVS diodes
- For the flash/reset circuit I believe you should use something like:
ESP32 auto reset circuit - MicroPython Forum (Archive) - For the screw terminal/pwm-mosfet repeated circuits I believe there are ways in kicad to repeat the layout using a subsheet. In KiCad 9 there are is a new tool you can use for this:
Post-V8 New Features and Development News - #64 by twl
The 10K on the gate should be there as it accounts for the gate capacitance, discharges it and the 1K was fine. Would work just fine, most people put a resistor to GND on the gate.
Agree.
I can’t be bothered to put all the pieces of the jig-saw puzzle together to understand its purpose. Note: I did not call this a schematic.
Surprisingly KiCad have no problems with it 
There is a difference between drawing for computer and drawing for human.
Wow, I didn’t expect such a useful response in such a short time.
Thank you very much for that! I love learning a lot in a short time – this platform seems to be exactly the right place for me. I only started yesterday morning and downloaded KiCad. I was aware that there would be many mistakes – that’s exactly why I signed up here.
@Piotr Thank you very much for your very constructive input regarding the MOSFET. I only checked whether it was suitable for logic level, and apparently, it might be good for switching low currents. However, the fact that it doesn’t fully switch on – which I could have simply taken from the datasheet – didn’t catch my attention. I will definitely use a converter. I quickly researched what options are available, and besides logic gates, I found a 3.3V to 5V converter. I will look into it in more detail and maybe find even better soultions, which switch 7V. Thanks again for the input – I probably wouldn’t have noticed this until later!
@joob Thank you for your comments! I will work through them step by step and do further research on each point. These are exactly the kind of comments I was looking for. You can probably also tell me why KiCad complains during the ERC check and tells me that some inputs have no connected outputs? Is there perhaps a thread that helps me understand the basic functionality of KiCad regarding the correct structure of a schematic?
It somehow sucks, that new members can only mark 2 people in the same post and are forced to split the reply into multiple messages…
@nickmBy & @jmk Thank you for your input as well. As you have correctly pointed out, I have almost no idea what I’m doing here. Maybe you could also kindly explain exactly what I did wrong, what effects this has, and how I can do it better? I think every forum benefits from constructive contributions rather than scattered Jigsaw puzzle pieces, which, when present in large numbers, only make it harder to find the key in the syringe pile.
You should know that this forum tries to be focused on problems with KiCad use only. With questions about electronic you should expect to be send to other forums (like EEVblog for example).
As it has nothing to do with KiCad I was wondering if someone would write to me that this is not the place for this.
If you know that your schematic is correct… I have never run ERC so no have a problems with its complains.
Read made by @jmk FAQ:
Some people (I think new age school) draw schematic like you just because they think it is the best way of drawing schematic. If you say them that for someone else it is very hard to understand it they don’t care and are often picky when someone draws their attention to it.
In my (and probably others) opinion it’s even rude to draw schematic to be almost impossible to understand and then ask other to help about it (assume you were looking to be such person).
When you see wire ending with label you (except being its author) don’t know where to search for it and even you will find the next end of this connection you don’t know if it is the only one as label can be used many times.
If you use bus (I use it without specifying wires inside - just as only graphic element (it was the only way for buses in earlier KiCad versions)) and end all such wires at bus than seeing one wire going into bus you know that only along that bus you should search for its other end - dramatically reduces the space you have to look through.
I have shown how my schematics looks like (without details). I use only one bus as I don’t have too many wires, but you can logically divide your wires into several buses.
1 Like
Nothing much to add to my above comment that @Piotr has just written.
It may be easy for you to understand what you have drawn for a schematic, but for someone to look for the first time and comment requires much time and effort to hunt down joining labels and decipher their purpose.
If you had drawn the schematic as per Piotr’s example, anyone, at first glance could understand the circuit.
It took me much time (too much) to ensure myself that MOSFETs are driven here from 3V3 and not 5V (V_BUS) to be sure that what I write about IRLZ34N is rationale here. I didn’t bother to think about this schematic any deeper and don’t plan. For me it is absolutely ‘not for human’.
If we were here a set of AIs discussing about it than it would be probably not a problem to any one of us as on finding all labels and generating a netlist from them each of us would spend a time counted in ns. But unfortunately we are human here (unless I don’t know something about you).
I don’t feel very human at the moment. This is our fourth day in a row of over 37° temperature 
Thank you very much for the explanations!
I understand that my circuit is very messy and unprofessional, and I want to change that. My biggest problem is that I don’t know how to use the software properly—I don’t know which label to choose for what, etc. Did I misunderstand something? I thought GND is GND everywhere.
I understand why it might make more sense to connect everything instead of using labels. However, in my opinion, using labels makes things easier (for mee) because it allows me to position components freely and arrange them in a way that makes the most sense visually. But i will try to mix labels and direct wiring instead.
I would like to make some adjustments:
- Implement the MOSFET setup (with resistors, labels, etc.) only once and then duplicate it. Just to clarify—will the labels be automatically numbered? How can I implement this?
- Place each section in a labeled box. Where can I do that?
- Solve the issue with the MOSFETs’ turn-on voltage.
- Add labels to unconnected pins. How can I mark them as not connected?
- Correctly specify the power sources and properly define GND, including differentiating if necessary. I might need an explanation here.
For you, these questions might be obvious, but I struggle to navigate the program, find functions, and fully understand what they do.
I understand if you don’t want to answer all of this. In other areas, I have a lot of expertise and always offer my help, even for absolute beginners. However, what doesn’t work for me is absolute resistance to fact-based advice. I am doing my best to make my circuit easier for you to read, but first, I need to understand how, where, and what… My biggest issue is finding the right buttons—I don’t yet understand the functionality of such software.
I previously tried Eagle, but the program was so buggy that I uninstalled it immediately.
Thats an easy one . . .
Click this and drop an X onto your pin
1 Like
Only because most of the regular people on this forum use Kicad daily, have been using it for 5+ years and have been designing PCBs for 30+ years or more.
Practice makes perfect. The documentation https://docs.kicad.org/ helps. Start with the parts you most need and practice using the functions when you have found them in the Documents. 
And here is the link to the documentation for unconnected pins.
Have you tried to do this?
Highlight all the parts including wires with a diagonal left button down mouse drag (note the difference between L to R and R to L mouse drag), then copy/paste or duplicate (both in right mouse click menu when hovering over highlighted selection) and observe the results. You will find the Refs increase with either function.
If you use KiCad 1 or 2 days than there is nothing unusual that you don’t know it. It is huge software.
I like to learn slower (like I also read slow but very accurate).
In 2017 before installing KiCad for the first time I have printed all KiCad documentation pdfs and then read them all (with marker in my hand). All means all - including for example Drawing Sheet Editor. After reading I decided that I like KiCad. From all what I have marked I have made cheat sheet and thus armed I installed KiCad V4 to find that all pdfs I have read are practically related to KiCad V3 while V5 will be soon. Nowadays documentation is probably more up to date.
When I then joined forum I found that even not using KiCad yet I know the answers for many questions asked here.
My way was that with KiCad V4 I spend time on making my own libraries (I use only my libraries) waiting for V5 to start designing my PCBs with KiCad. The reason for waiting was that it was said that V5 solves the via-stitching problem (in V4 you had to connect with tracks all GND vias connecting top and bottom GND zones). Most PCBs I have done with V5 who reigned for 3 years. From V6 I use KiCad rarely - practically only when one of my PCBs need new revision.
Don’t get too carried away and take some time to review the KiCad documentation.
“Don’t get too carried away” is from Google translator from “Don’t be bathed in hot water”. I hope meaning is as I expect.
We have here about -2°C now, but when I was young at this time of year typical was -10…-20. The coldest I remember (I think it was ±1973) was -35°C. If the air were dry, it wouldn’t be a problem, but it wasn’t. My eyes hurt from the cold. I devised a method of closing my eyes alternately every few seconds.