Go Down

Topic: Learning how to read schematic (Read 5478 times) previous topic - next topic

vdiallonort

Hi,
I am looking for some guidance about how to learn to read schematic and translate it in real life circuit. I got a bit confuse sometime, for example in this tutorial here .
I don't get why the jumper that go to the reset pin of the arduino uno have to be connected between the resistor and the Atmega.In my head the line on the breadboard connect everything that is plug into this line so i don't understand why the order matter.
Does there is any good book that could help me understand this kind of thing ( big plus for the electronice on, i order some of them but i live in Australia and take forever to get them ( if i get them at the end)

All the best

Vincent

Koepel

The order does not matter of course.

Here is a video about breadboards : https://www.youtube.com/watch?v=w0c3t0fJhXU

Those are not schematics, but pictures. Some of use (like me) can't get used to the pictures, as I am used to schematics.

Grumpy_Mike

There are no schematics on that page you linked to. There are lots of physical layout diagrams which are shit but no schematics. You can google for lots of videos and pages on how to read schematics.
Once you have a schematic there are many ways to turn that into a physical layout diagram and Fritzing is about the worst one you can choose. Simply do it one component at a time and work your way through the schematic.

vdiallonort

Hi,

Thanks, yep there is no schematic on this tutorial, i insert it just to show that some of these circuit does not make much sense to me.Like why there is a resistor to the reset pin when the atmega support 5v and the VCC is 5V ?
I start electronic by just copy-paste what other peoples are doing with time my interest grow and i like to understand it a  bit deeper.
Thanks for some reason my circuit was not working with the another order ( but should have been about something else ) and it get into my head that order matter.

All the best

Vincent

Hutkikz

#4
Jan 18, 2016, 02:54 am Last Edit: Jan 18, 2016, 03:07 am by Hutkikz
Like why there is a resistor to the reset pin when the atmega support 5v and the VCC is 5V ?
I probably should not stick my nose in here as I am still a noob also and am likely to muck it up.
But I am sure that the reason for that resistor is to limit the current.

 While they are both 5v. The Vcc pin can source 200 mA of current and the reset pin can sink only 50mA so a resistor is required to limit the current to an acceptable range to prevent damage.
 It's the same reason that LED's require resistors or a constant current supply. without them they will draw more current then they or the arduino can handle and then the magic smoke is released. They are not much good after that.

 This is more of a electronic design question than a schematic reading question.

larryd

No technical PMs.
If you are asked a question, please respond with an answer.
If you are asked for more information, please supply it.
If you need clarification, ask for help.

Boardburner2

The resistor is called a pull up resistor.

The maximum current for the chip is i/o is 40 ma per pin although other restrictions apply.

For an input only micro amps are generally needed.

' While they are both 5v. The Vcc pin can source 200 mA of current and the reset pin can sink only 50mA so a resistor is required to limit the current to an acceptable range to prevent damage.'

The current limiting resistor on an led circuit fulfils a similar function.

An output can either be a current source or sink (digitally)
 without a current limiting resistor that can destroy a chip easily.

Understanding circuit diagrams is just a question of time and practice.

Do not waste time trying to understand arduino diagrams.

Learn the basics of transistors and other discrete components first.
arduino specifies source and sink current capabilities for outputs, to understand that properly you need to understand basic transistor operation first.   



outofoptions

You learn to read schematics AS you learn circuits.  Look for good basic sites and it all starts to make sense.  Learning to read schematics is the wrong goal.

sterretje

Learn the basics of transistors and other discrete components first.
arduino specifies source and sink current capabilities for outputs, to understand that properly you need to understand basic transistor operation first.   
One can download the datasheet of a relative simple device like a 74HC00 and have a look at the electrical characteristics for starters. Most relevant are probably Iil (how much current flows out of an input pin when it's pulled low), Iih (how much current flows into an input pin when it's pulled high), Iol (how much current can an output sink when it's low) and Ioh (how much current can an output source (deliver) when it's high) as well as some Vcc related parameters. Ask questions about parameters that one does not understand.

The gained understanding can next be used to understand the electrical characteristics of e.g. the 328 micro controller without drowning in the surplus of information.


Do not waste time trying to understand arduino diagrams.
For me, they are terrible examples of schematics.
If you understand an example, use it.
If you don't understand an example, don't use it.

Electronics engineer by trade, software engineer by profession. Trying to get back into electronics after 15 years absence.

OldSteve

This is more of a electronic design question than a schematic reading question.
Yep. I agree. And as outofoptions says, "You learn to read schematics AS you learn circuits."

It's a matter of getting into studying basic electronics, and as you do so, the various circuit symbols that make up schematics will be presented to you.

Learning to read schematics, without any electronics knowledge, won't work.
Please do not PM me for help. I am not a personal consultant.
And others will benefit as well if you post your question publicly on the forums.

raschemmel

The link in Reply#5 is the only way to learn how to read schematics. Learning the symbols is half of it. The other half is learning to understand why components are connected the way they are. That takes much longer. There is no shortcut. Learn electronics and you will learn how to read schematics at the same time. Try to learn schematics without learning electronics and you will be lost.
Arduino UNOs, Pro-Minis, ATMega328, ATtiny85, LCDs, MCP4162, keypads,<br />DS18B20s,74c922,nRF24L01, RS232, SD card, RC fixed wing, quadcopter


Boardburner2

For me, they are terrible examples of schematics.
It's just not me then.

I get flashes of jelly fish in a bucket when i see them

pwillard

#13
Jan 19, 2016, 03:45 am Last Edit: Jan 19, 2016, 03:47 am by pwillard
You will constantly hear the regulars in the #Arduino IRC channel groan when yet another bad "pictorial" diagram from Fritzing is 1) called a schematic... {because... it's not}  2) posted so someone more knowledgeable can figure why its not working...

And heck  we can't... because all the hookup wires are the same color and crossing each other at crazy angles.  Pictorials are horrible at conveying the INTENT of a design, especially when the tool offers NOTHING in the way of design rules.

I applaud the desire to learn schematics.  It is the common language we should all speak.

larryd

#14
Jan 19, 2016, 04:24 am Last Edit: Jan 19, 2016, 04:26 am by LarryD
Quote
It is the common language we should all speak.
Remember what happened at the Tower of Babel!



  ;)
.
No technical PMs.
If you are asked a question, please respond with an answer.
If you are asked for more information, please supply it.
If you need clarification, ask for help.

Go Up