-
Notifications
You must be signed in to change notification settings - Fork 0
Software
The purpose of software is to make the robot actually do things. A body without a brain is lame.
The software team must consider the following:
How much code do I actually have to write?
What does the pseudocode look like for the robot? What does the flow look like for the code?
What tasks does the robot need feedback to do? What does it not need feedback for?
What sensors can be used for each task? Are there alternatives?
How do I minimise lag between the sensor reading a value and actually doing something?
What actuators are the mechanical team putting on the robot?
What electrical components to control those actuators?
Are there drivers written for the components already?
What programming language is the software team using?
Can you get away with a less feature-heavy equivalent? (Arduino Uno instead of an Arduino Mega, etc)
How do I best use interrupts in my code?
Copyright Nam Tran, 2018