Troubleshooting Brian Kidney Engr. 6808 September 22, 2003.
-
Upload
abraham-wells -
Category
Documents
-
view
214 -
download
0
Transcript of Troubleshooting Brian Kidney Engr. 6808 September 22, 2003.
Troubleshooting
Brian KidneyEngr. 6808September 22, 2003
What? Problems? Never!
You WILL experience problemsBoth with hardware and software
Planning can limit delays Incremental buildingUnit testingRevision Control
Incremental Building
Practice KISSKeep It Simple Stupid
Build components in small steps Fully test each component before moving
on Integrate in steps as well
Unit Testing
Concept comes from softwareJUnit, CPPUnit, and many others
Main idea is to design test firstBased on the functionality of the component,
not the implementation Test after first implementation and every
change
Revision Control
If it works, Keep It! Always keep copies of old software that
worksDate files, use CVS, Source Safe, …
Try to add to hardware rather than redesignDocument all circuits in stages
Noise!!!
Shows up everywhereVideo, sensors, circuits, motors,…
Difference between labs and “real world” Need to filter out noise
Can be done with simple RLC circuitsCan be done in software
Tips to find your problems
Never rule out anything Start with simplest components, then complex Even wires break
Use datasheets Example circuits may give clues
Have others look at you work If at first you don’t succeed, take a break Document your mistakes