How to Draw Schematic & Tips to Improve Schematic - Visual Improvements (Part 1)
HTML-код
- Опубликовано: 26 авг 2024
- Pointing out the things what you may need to be careful about, what to improve in your schematic and why.
Original project can be downloaded from here:
www.fedevel.co...
------------------------------------------------------
Would you like to support me in what I do? It's simple:
- you will help me a LOT, when you sign up for one of our Schematic and PCB Design online courses at www.fedevel.co...
The other ways to support me in what I do are:
- support me through Patreon page / robertferanec
- sign up for my Udemy course, Learn to Design Your Own Boards www.udemy.com/...
- send me an email and/or leave a positive comment
- watch and like the videos :)
- read my Welldone Blog at www.fedevel.co...
- spread a word about FEDEVEL Academy
It is much appreciated. Thank you,
- Robert
Do you recognize yourself in this project? I recognize myself :) These are the things what I was doing when I was starting with hardware design ... and now I do them differently. What do you think about the improvements which I pointed out?
You should've seen mine in the early days...
@@nasserghoseiri4934 :)
@@nasserghoseiri4934 😂 Had the same thought, once you realize your fancy new board does not work due to a screw up in the schematic you start re-thinking how to draw stuff... Frustration is a powerful (and harsh) teaching tool
The point I personally liked the most is the one about the "sense" of the schematic. I did do the same when I was starting (drawing my symbols mimicking the footprint).
I always tell people, ICs are like tiny magic black boxes, things happen on one side the result of the magic comes out the other side on top there's power and on the bottom your reference. Do that and the readability and cleanlyness of your schematics is multiplyed by 100!
Great video, straight to my teaching reference material!
@@leix99 Well the first board I made had no schematics at all. It was in Protel-97, and I just put footprints there and connected the pins manually.
I remember I had made a special QFP-208 footprint for Xilinx Sparta 2 XC2S200, which had a small line beside each pin that was reserved (Power, JTAG, etc.) to remember not to use that specific pin for IO routing.
You can imagine how it would've gone if something didn't work at bring-to-life stage... :)
As always, great video!
We'd love to see PCB part :)
I have done these mistakes initially and now improved over time. Thanks for spreading your knowledge.
Notes for AD beginners like me:
5:35: Create a block diagram for a schematic to explain the functions of the PCB board
11:15: When creating component symbols in your schematic library, always use the 100 Mil grid for pins. Place pins on the 100 Mil grid with lengths of 100, 200, 300 Mils. In the schematic, it’s safe to use 100 and 50 Mil grids.
14:00: Use multiple schematics if necessary (to be simple and clear). Add descriptions properly.
18:55: For chip symbols, place power on top, place ground on the bottom. Place the input on the left. Place the output on the right. We do not have to create symbols that look like their footprints.
22:00: Add net names for important signals, such as power lines and differential pairs.
26:00: Add pin numbers and names together.
Thank you Xinmiao
Very good video that clearly shows the right and wrong ways to draw schematics!
The aesthetic aspect to schematic capture (drawing) that is often overlooked up-ends the traditional, stereotypical view that "engineers" don´t or shouldn´t care about graphic design: good schematics are clear, concise and aesthetically pleasing.
The way you designed that block diagram shown in this video helped me simplify the blockdiagram i made for my own project. Thanks for the video.
Great video Robert and , yes, I would like to see a video about the PCB improvment. I really would like to see all about PCBs, tips, lessons and so on. Thank you very much for sharing. Best regards and you're the man!
Thks! waiting for PCB part
Very helpful video Robert! Please make more. Thanks!
Great and very helpful tips ... looking forward to work on hardware design
Thanks so much! These videos are incredibly useful . This is my new favorite RUclips channel
Thank you Adam.
Very helpful tips there Bob
I l ike the quality of your videos. Thanks for sharing & keep it up
Love it, very helpful. Good design is all in the small details.
Can't wait for the next video for the PCB layout
Thanks for the video. It helped me anticipate working further with Altium. I purchased a T shirt to reward you.
Thank you very much Forrest Erickson
Robert very good tips I am new in designing but what you say about how we should improve the schematics is extremely important since we should not design for ourselves we should also design for other people, several techniques that you use to improve the designs I also use them but with some difficulty but thanks to this video I can improve much more and the truth I am very grateful with what you do and the courses that you teach really appreciate it.
Thank you, this is great content.
Thank you for these kind of helpful tips. We are waiting for PCB Layout tips, also. :)
Perfect! Thanks Robert
So helpful . Thanks !!!
Great video thank you! Might want to put your overlay on the left side lol it was hard to see stuff on your screen sometimes.
When recording this video, big problem was Altium (or the recording software) - for some reason I was not able to see some submenus and I had to actually record this video through Remote Connection - that can influence visibility some of the elements. Maybe that could affect it ... I am not sure why it is happening.
Robert Feranec not sure what you mean I’m referring to the webcam overlay. Was just sayin it probably fits better in the left corner.
@@Daniel-ib5bx Ah, I thought you were speaking about the logo. I try to hide the camera window when I speak about something behind it. Maybe I missed something.
amazing.......!
What do you think about adding a top-level schematic sheet where you connect the input and the two output sheets together using yellow ports. I've learned that this is the proper way of doing a multi-sheet project, but I never seen you do this in your projects. Why should/shouldn't we use ports and a top-level sheet?
In my opinion, top sheets in hierarchical designs are space where additional mistakes and errors may be created (I have seen errors in top sheets). Creating top sheets takes additional work (not only to create them, but also to maintain them and to check them). Also, it is additional step in following signals (makes it harder to read schematic). These are the main reasons why I so not use hierarchical schematics. PS: Sometimes I use TOP Sheet, but without ports and wires, just the green blocks with schematic page names.
hello robert, your video has a great topic. Yet
However, I find it a bit difficult to understand video content when it doesn't support subtitles. Can you add subtitles or closed captions to this video? Thank you.
Thank you so much
I am an embedded design engineer in small company in india .so i have to write firmware , build prototype , schematic pcb design so it's kind of jack of all trade but master of none so this video is holy grail for me.
Great video Robert, I appreciate your work a lot (thumb up)
I want ask if you can sometimes create a full guide (from selecting parts to complete product) of creation some device (somethning with dif.pairs, DDR3, video signals, etc... for ±intermediate difficulty) ando slowly take us this way to tne end with comenting every traps, common mistakes or "things" witch may occur during creation, what I think would be very useful wazch and learn your professional workflow, thanks
PS: oh and of course, best wishes on your name day ;-)
Thank you. Have a look at our courses, they may cover some of the topics you are asking about. However, the courses are not free - it was a lot of work to create them - I mean a lot of work .... hundreds of hours of work. Here is the link: www.fedevel.com/academy/ (Are you Slovak? Best wishes on your name day too :)
enjoy video
Obvious things, but helpful. Pls continue
I would love to have a video about the Board design!
I've learnt so much using your videos!
Right now I'm working on a USB3 Interface (Type-C) on a tiny board, and as a hobbyst it's a nightmare!
I don't have the full space to keep the 3x spacing between the pairs so I had to cheat a bit!
Suggestions?
BTW, I'm adding USB-PD and USB 3.1 to my chromebook :D
I would love to send you my crappy design and see what it's wrong with it!
if you do not mind making a youtube video about your project, you can send it to me (I can not promise that I will make a video about it)
@@RobertFeranec yea, it's a open source design!
I was also making a SBC but in that case the project stopped due to the high cost of the impedance controlled pcb!
@@tuttocrafting ok
If I were u, I would have combined both HDMI symbols by adding a small HDMI Logo(pic) of the first one to ur's in the center, that would be coolest
Shall I always be using 100 mils as snap grid and grid size in schematic symbols and the schematic sheets?
In schematic symbol libraries yes always use 100mils for pins. In schematic, 100mil and 50mil is standard (I only use these in my schematics).
Love it, very helpful.I need the Altium file of HDMI ralated to this video. could you give the link adress for download it?
Thank you. PS: I believe, the file should be here: designhelp.fedevel.com/forum/test/pcb-layout/10466-hdmi-connection
@@RobertFeranec Thanks a lot
@@RobertFeranec Sorry, in this page I haven't any permission to download this file
hi robert, i didnt see all your videos but i think a lot about schematic and pcb design.. i dont recall talking about HDMI it self for example as what is it. (what is the data in the 4 differential pairs).. (how do we program it if we have mcu..) or (memory and external ram) ... things like these i think would be interesting in my opinion thanks. something like schematic design not about schematic drawing.. i would like to see pcb video also.
thank you hasan. normally you do not need to go into protocol / signal levels of interfaces - unless if you would like to generate them by yourself (or something is not working). Most of the time the OS, drivers, right settings in registers and hardware will generate everything correctly by itself.
All sound advice.
Can you please tell me how to implement the two overlapping SMD resistor footprints used to create the "either-or" options.
If I simply overlap two resistor footprints, the DRC rules would complain about the component overlap, even though we know that only one component will ever actually be populated on any given PCB. How should the DRC rules be updated to allow this, (or is it a special library footprint with 3 pads?)
I create a special rule with exception. Have a look at our open source project - you can double check there how it can be done: www.28pins.com/
@@RobertFeranec Thanks, yes I see how you did this now.
For anyone else reading this, the trick used in the 28Pins_Project was to add a new DRC rule under "Placement"->"Component Clearance" called "Power Resistors". In that rule, the scope is set such that when the first object is "R27" and the second object is "R28", the Horizontal and Vertical clearances are set to 0mm, which overrides the default component-to-component clearance rule of 0.2mm. This allows you to overlap the footprints of two resistors thereby creating a very low-cost SMT option jumper with the fool-proof benefit that it is physically impossible to fit both option components simultaneously.
Of course we want more, do you have to ask!? :D