My last project didn't work at first, so I learned what happens if I leave a CMOS input floating, a signal has too long rise time and why would I need to connect capacitors across rectifier diodes in a FWB if I wanted to use the 50Hz signal from the power transformer (because otherwise I would get a spike and the signal would be detected as 100Hz).
Funnily just after I saw this, my next project didnt work! It was fine on a breadboard, but having digital sensors on the end of 50m of telephone cable meant I got nothing back. The datasheet calls for pullup resisitors between 5v and the data line and I had done this on the circuit board. To fix it, I found I had to add some high value (33kohm) pullups on the end of the 50m data line.
when i made the second prototype for my 8 digit display, i'd shifted to using a tristate output shift reg for addressing the display registers and i found all the display registers were changing and showing the same outputs, as im using the OE pin on the tristate register it makes the strobe lines on the display registers OC and with noise it was strobing the display registers, putting on some pulldown resistors helped with that
I once had some serious problems with an Atmel flash IC in a no-lead package that was not fully solderded onto my board. So one (or possibly many) pins were only coupled by capacitance. It drove me freeking nuts finding this fault, as you could not measure the signals at the leads. The flash's basic functions like reading and writing larger data blocks seemed to work without problems but more specific stuff like reading a config register failed. After re-soldering the chip it finally worked.
love your debug story. nice to know the pros go through the similar bug hunts as us amateurs do, allbeit, your bug hunt involve non-amateur components.
Electrical Engineering branches off to many disciplines that include, Hardware (PCB/Amplifier Design etc), Software (Application, Embedded firmware ) or even sales, and research.
@BusterBlader910 I'm an ex-electronics engineer - these days I write software. But when I started I designed analogue RF transceivers (private mobile radio systems), then went on to low-power digital RF communications, some consumer electronics design (wireless burglar alarms), then one-off electronics display systems for exhibitions and education, but then drifted into software. If you understand the theory, can build stuff that works in practice, you can do what you like.
Great advice regarding dual purpose I/O. I always put a series resistor (a few hundred ohms) between any two pins that could potentially clash. The firmware still has to be right, but the current limiting resistor can save hours of debugging because it reduces unexpected brownout resets, code excursions, IC damage, etc.
My last project didn't work at first, so I learned what happens if I leave a CMOS input floating, a signal has too long rise time and why would I need to connect capacitors across rectifier diodes in a FWB if I wanted to use the 50Hz signal from the power transformer (because otherwise I would get a spike and the signal would be detected as 100Hz).
Pentium100MHz 3 weeks ago
@Pentium100MHz Good work. Next try floating the power pin and see what happens!
EEVblog 3 weeks ago
Funnily just after I saw this, my next project didnt work! It was fine on a breadboard, but having digital sensors on the end of 50m of telephone cable meant I got nothing back. The datasheet calls for pullup resisitors between 5v and the data line and I had done this on the circuit board. To fix it, I found I had to add some high value (33kohm) pullups on the end of the 50m data line.
etalon3141 2 months ago
when i made the second prototype for my 8 digit display, i'd shifted to using a tristate output shift reg for addressing the display registers and i found all the display registers were changing and showing the same outputs, as im using the OE pin on the tristate register it makes the strobe lines on the display registers OC and with noise it was strobing the display registers, putting on some pulldown resistors helped with that
williefleete 4 months ago
Oh man... i don't know why I've heard findtubes instead of findchips, maybe it's your accent. Don't go to what I mentioned, it's nsfw...
Everything's ok in the end.
mariushmedias 6 months ago
6:15 = a face on the whiteboard. Wonderful.
prenvo 7 months ago
Is anything a trap for old players?
heroineworshipper 11 months ago
I once had some serious problems with an Atmel flash IC in a no-lead package that was not fully solderded onto my board. So one (or possibly many) pins were only coupled by capacitance. It drove me freeking nuts finding this fault, as you could not measure the signals at the leads. The flash's basic functions like reading and writing larger data blocks seemed to work without problems but more specific stuff like reading a config register failed. After re-soldering the chip it finally worked.
gishidenki 1 year ago
love your debug story. nice to know the pros go through the similar bug hunts as us amateurs do, allbeit, your bug hunt involve non-amateur components.
averagemale2000 1 year ago
Man, I got screwed over for like 3 days with Microchip's Analog/Digital purpose pins!
vex123 1 year ago
Why didn't you use the screenshot feature of the osc? I'm assuming it has it.
good videos btw
chromebeats 2 years ago
thanks! another great video.
kchididdy 2 years ago
I want to become an electronics engineer
but I'm not very sure what they really do. Do they play a role in making the next gen ipods or make circuit boards.Both maybe idk.
ps I'm freshmen in high school
pss awesome video
BusterBlader910 2 years ago
I'm a freshmen in high school. I've been doing digital electronics for about 3 years and AVR electronics for about 4months.,
davidbball13 2 years ago
@BusterBlader910
Hi there,
Electrical Engineering branches off to many disciplines that include, Hardware (PCB/Amplifier Design etc), Software (Application, Embedded firmware ) or even sales, and research.
Best of luck!
vex123 1 year ago
@BusterBlader910 I'm an ex-electronics engineer - these days I write software. But when I started I designed analogue RF transceivers (private mobile radio systems), then went on to low-power digital RF communications, some consumer electronics design (wireless burglar alarms), then one-off electronics display systems for exhibitions and education, but then drifted into software. If you understand the theory, can build stuff that works in practice, you can do what you like.
GRAHAMAUS 1 year ago
Great advice regarding dual purpose I/O. I always put a series resistor (a few hundred ohms) between any two pins that could potentially clash. The firmware still has to be right, but the current limiting resistor can save hours of debugging because it reduces unexpected brownout resets, code excursions, IC damage, etc.
codeprose 2 years ago