Finally the fun starts =) - Page 1
Forum section: electronics / beginners

author: SuperMiguel
author_rank: Regular Contributor
timestamp: March 18, 2011, 01:24:57 am
content: So finally ima start my true electronics studies at school i finish my calcs, my physics and all the prerequisites to get into the EE program.. So i have play with arduino from turning on an LED on to building a small robot. Also i done a bit of straight AVR but not much, so my C programming is not that great also the only analog electronics i have done is playing with the 555 and few basic things...So should i go ahead and start working on my C programming or finally read "The art of electronics" and learn analog?Thanks

author: Mechatrommer
author_rank: Super Contributor
timestamp: March 18, 2011, 02:56:58 pm
content: congrats. do it all, if you can, analog, programing digital etc etc.

author: SuperMiguel
author_rank: Regular Contributor
timestamp: March 18, 2011, 03:56:00 pm
content: Quote from: Mechatrommer on March 18, 2011, 02:56:58 pmany recommendation on which one to do first?

author: Mechatrommer
author_rank: Super Contributor
timestamp: March 18, 2011, 08:20:36 pm
content: ok, since you ask me. first programming, then digital, and then analog. i'm sure alot of people will answer backward. but thats just me

author: NiHaoMike
author_rank: Super Contributor
timestamp: March 18, 2011, 10:29:28 pm
content: Start with whatever interests you most or whatever you think is most important to you.I personally started with analog, then digital and finally software. I mostly work with power electronics which is mostly analog with some digital and sometimes a little bit of software. On the other hand, my friend Tiffany Yep, a digital communications engineer (and a model), specializes in software and only needs to know the basics of digital and analog circuits.

author: Simon
author_rank: Unknown
timestamp: March 18, 2011, 10:36:54 pm
content: we were taught digital first in "school" and I found it well wierd, you still need the fundamentals of electronics to understand digital, software is not electronics, it's software. Programming a computer (MCU) is just programming although with MCU's you will be designing the whole system of software and electronics so things start to "meld".For a general approach I'd say make sure you have the analogue fundamentals, at least enough to understand the physics of digital circuitry (not much point in trying to interface logic gates to control power loads until you know at least the basics of transistors) then do as you please. Developing both analogue and digital may be a good idea, both are huge so take what you need from either. most designs are both, or rather they are MCU's and analogue interface circuitry, but understanding digital helps with MCU's I guess

author: Mechatrommer
author_rank: Super Contributor
timestamp: March 18, 2011, 11:39:14 pm
content: o well, at least i have something in common with Tiffany Yep. but not all.

author: SuperMiguel
author_rank: Regular Contributor
timestamp: March 19, 2011, 02:39:06 am
content: not sure if it matters but im really interested in robotics, not sure if that changes the order of the factors

author: Simon
author_rank: Unknown
timestamp: March 19, 2011, 08:19:44 am
content: yea, you need to study all areas as you will be dealing with software control through digital interfacing into the real (analogue) world by means of actuators and transducers. Not having the analogue skills to interface an MCU to the rral world will cost in the long run. I made a real hash of a project once because I didn't understand my opamp properly. It worked in the end but that was opure luck and due to software tinkering to compensatwe for my mistake

author: Trigger
author_rank: Regular Contributor
timestamp: March 20, 2011, 09:45:11 pm
content: I was a CS major then I switched over to CE which gave me a solid background in programming. It made my life a whole lot easier when it came to projects. Once you have to program in binary, then op codes, assembly, and finally C. My impression of microcontroller assembly was 'wow this is simple'. You should learn assembly for debugging purposes but don't torture yourself with writing programs in it unless you have to and that's why inline assembly exists. You can do a lot of creative outside of the box things with a microcontroller to solve problems but that all depends on your ability to tell it what to do.