Can anyone recommend any web site or book with a good basic tutorial on reading schematics, US symbols preferred to European? I have a colleague who is an experienced embedded programmer, but she never had any formal electronics training and she has asked me to try to find a resource. All suggestions appreciated. -- Jack Klein Home: http://JK-Technology.Com FAQs for comp.lang.c http://c-faq.com/ comp.lang.c++ http://www.parashift.com/c++-faq-lite/ alt.comp.lang.learn.c-c++ http://www.contrib.andrew.cmu.edu/~ajo/docs/FAQ-acllc.html
Looking for recommendations: schematic reading turotial
Started by ●March 18, 2007
Reply by ●March 19, 20072007-03-19
Jack Klein wrote:> > Can anyone recommend any web site or book with a good basic tutorial > on reading schematics, US symbols preferred to European? > > I have a colleague who is an experienced embedded programmer, but she > never had any formal electronics training and she has asked me to try > to find a resource. > > All suggestions appreciated.This may be obsolete, but how about the ARRL handbook? -- <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt> <http://www.securityfocus.com/columnists/423> "A man who is right every time is not likely to do very much." -- Francis Crick, co-discover of DNA "There is nothing more amazing than stupidity in action." -- Thomas Matthews -- Posted via a free Usenet account from http://www.teranews.com
Reply by ●March 19, 20072007-03-19
Jack Klein wrote:>Can anyone recommend any web site or book >with a good basic tutorial on reading schematics, >US symbols preferred to European?Symbols: http://www.ibiblio.org/obp/electricCircuits/Ref/REF_9.html http://homepage.ntlworld.com/g.knott/elect91.htm I guess this is as good a page as you will find: (Uses Cadsoft EAGLE for artwork, so symbols are Yurpeen) http://66.102.9.104/search?q=cache:6rL03uKDGK8J:www.best-microcontroller-projects.com/how-to-read-schematics.html+Horowitz.and.Hill+bible+The-Art-of-Electronics The original link for Google's spider: http://www.best-microcontroller-projects.com/how-to-read-schematics.html Other starter pages: http://arts.ucsc.edu/EMS/Music/tech_background/schematics/ReadSchem.html http://66.102.9.104/search?q=cache:_OCkLUlbiGUJ:doctord.dyndns.org:8000/courses/Topics/Electronics/Mark_Sokos/How_to_read_schematics.htm More pages here (of lesser quality) if you want them. http://ww.google.com/search?q=intitle:reading+OR+intitle:read+intitle:schematic+OR+intitle:schematics
Reply by ●March 20, 20072007-03-20
CBFalconer wrote:> Jack Klein wrote: > >>Can anyone recommend any web site or book with a good basic tutorial >>on reading schematics, US symbols preferred to European? >> >>I have a colleague who is an experienced embedded programmer, but she >>never had any formal electronics training and she has asked me to try >>to find a resource. >> >>All suggestions appreciated. > > > This may be obsolete, but how about the ARRL handbook? >Excellent suggestion; I also suggest collecting at least one Handbook per decade from 1960 onwards. Regards, Michael
Reply by ●March 20, 20072007-03-20
On Mar 18, 9:21 pm, Jack Klein <jackkl...@spamcop.net> wrote:> I have a colleague who is an experienced embedded programmer, but she > never had any formal electronics training and she has asked me to tryThis sounds really weird. How can someone be an "experienced embedded programmer" without being able to read schematics?
Reply by ●March 21, 20072007-03-21
Adrian escribi�:> On Mar 18, 9:21 pm, Jack Klein <jackkl...@spamcop.net> wrote: >> I have a colleague who is an experienced embedded programmer, but she >> never had any formal electronics training and she has asked me to try > > This sounds really weird. How can someone be an "experienced embedded > programmer" without being able to read schematics? >By concentrating his/her efforts in the application part and leaving the "low level details" to real men/women of the same team? -- A real man.
Reply by ●March 21, 20072007-03-21
On Mar 21, 9:47 am, "Ignacio G.T." <igtorque.rem...@evomer.yahoo.es> wrote:> > By concentrating his/her efforts in the application part and leaving the > "low level details" to real men/women of the same team? >Then he/she is not "experienced"!
Reply by ●March 21, 20072007-03-21
On Mar 21, 11:50 am, "Adrian" <adrianb...@yahoo.com> wrote:> On Mar 21, 9:47 am, "Ignacio G.T." <igtorque.rem...@evomer.yahoo.es> > wrote: > > > > > By concentrating his/her efforts in the application part and leaving the > > "low level details" to real men/women of the same team? > > Then he/she is not "experienced"!Depends on the type of embedded system. Not all embedded applications are memory constrained, hardware controller, no OS programs. Running ontop of a realtime OS the higher application might only have to worry about their realtime deadlines, not hardware registers. Ed
Reply by ●March 21, 20072007-03-21
On 21 Mar 2007 11:15:51 -0700, "Ed Prochak" <edprochak@gmail.com> wrote:>On Mar 21, 11:50 am, "Adrian" <adrianb...@yahoo.com> wrote: >> On Mar 21, 9:47 am, "Ignacio G.T." <igtorque.rem...@evomer.yahoo.es> >> wrote: >> >> > By concentrating his/her efforts in the application part and leaving the >> > "low level details" to real men/women of the same team? >> >> Then he/she is not "experienced"! > >Depends on the type of embedded system. Not all embedded applications >are memory constrained, hardware controller, no OS programs. Running >ontop of a realtime OS the higher application might only have to worry >about their realtime deadlines, not hardware registers.Yes, but then what is the difference from that and any general programmer writing applications on general purpose computing platforms? To me, what makes you more (or less) an embedded programmer is the degree to which you require skills outside of those required by programmers working on general purpose computing systems. Do you need to understand linker details and influence the linking process? Do you need to write assembly? Do you directly control hardware or interact with electronic components you need to understand? Do you need to concern yourself with Harvard achitecture variances from the C system model? Do you need to delve into the generated code sometimes? Are you cycle-counting because you need to have alternate paths of code branches take exactly the same number of CPU cycles? Are you wriing what amounts to a BIOS or O/S? Do you need to understand numerical methods well and analyze error propagation and control it? Do you find many of your projects requiring you to understand signal processing basics? Do you need to read schematics and influence their design? Do you need to understand sensor and transducer physics? Do you find many of your projects requiring you to be fluent in linear algebra, ordinary differential equations, group theory, kalman or other optimal filtering theories, fourier and laplace, compiler parsing theory, dynamical catastrophe theory, etc? If you find more of your work merrily assuming a general operating system and BIOS you can rely upon for detailed control of hardware, if you find more of your work allowing you to just write C or C++ code and never really needing to expand your vistas beyond that space, if you find your programming life and programming concerns and problems little different from those who actually _do_ program on general purpose computing platforms then to that degree you are not an embedded programmer. It's the differences from general programming, those general programming skills usually taught in basic undergrad courses, that make one more experienced as an embedded programmer. Jon
Reply by ●March 21, 20072007-03-21
On 21 Mar 2007 08:50:29 -0700, "Adrian" <adrianbica@yahoo.com> wrote:>On Mar 21, 9:47 am, "Ignacio G.T." <igtorque.rem...@evomer.yahoo.es> >wrote: >> >> By concentrating his/her efforts in the application part and leaving the >> "low level details" to real men/women of the same team? >> > >Then he/she is not "experienced"!Embedded systems are quite often tested using a row of switches to simulate binary inputs, potentiometers to simulate analog transducer signals and LEDs for monitoring digital outputs. In order to test an embedded software using these tools, very little knowledge of electronics is needed, but still you may have to write device drivers etc. The software designer in a team does not usually have to worry about galvanic isolation, input protection and EMC filtering, which are done specialised HW people. Still it helps if the software designer is able to look at the circuit diagram, e.g. to determine if the buffer stage between the processor pin and the external (say 20 mA) circuit is inverting or not, in order to write the correct polarity into the output register. Paul
