Advice for Future 218ers
- Keep designs simple from the start. Once you've met the bare expectations, then scale up. Preferably start simple and simplify more as you go.
- Use Adafruit PermaProto breadboards (or an equivalent). This will save you time.
- If you can buy a part to do something and it isn't too expensive, buy it. Time saved on mechanical implementation is worth it.
- Buy power terminals and route all your power lines back to the main power source (i.e. batteries)
- Think about noise reduction early in the design process. Design it in from the beginning.
- Buy spare parts.
- Always have fall back plans that allow you to simplify for anything you are not positive on how to do.
- Keep an up to date change log of the robot and design decisions made. This can avoid unneeded or duplicate work.
- If you realize that something is not working but you don't really need it, cut that feature and add it in only if you have time.
- Don't assume you need closed loop control. Many systems work quite well open loop. If you find you need feedback, think about how simple you can make it.
- Be aware that printing to terminal takes time; adding a print that wasn't there or removing a print that was can both change code execution. Once you get it working, don't change anything.
- Build and test components and modules until they are rock-solid, then integrate. Debugging integrated subsystems that have not been tested is asking for trouble.
- Push hard to stay ahead of checkoffs. This gives you more time for debugging, gives you more time on the field to test, and will leave you much less stressed the night before grading.
- Use Adafruit PermaProto breadboards (or an equivalent). This will save you time.
- If you can buy a part to do something and it isn't too expensive, buy it. Time saved on mechanical implementation is worth it.
- Buy power terminals and route all your power lines back to the main power source (i.e. batteries)
- Think about noise reduction early in the design process. Design it in from the beginning.
- Buy spare parts.
- Always have fall back plans that allow you to simplify for anything you are not positive on how to do.
- Keep an up to date change log of the robot and design decisions made. This can avoid unneeded or duplicate work.
- If you realize that something is not working but you don't really need it, cut that feature and add it in only if you have time.
- Don't assume you need closed loop control. Many systems work quite well open loop. If you find you need feedback, think about how simple you can make it.
- Be aware that printing to terminal takes time; adding a print that wasn't there or removing a print that was can both change code execution. Once you get it working, don't change anything.
- Build and test components and modules until they are rock-solid, then integrate. Debugging integrated subsystems that have not been tested is asking for trouble.
- Push hard to stay ahead of checkoffs. This gives you more time for debugging, gives you more time on the field to test, and will leave you much less stressed the night before grading.