UAS/Design/Software: Difference between revisions
Jump to navigation
Jump to search
en>Jmussemann No edit summary |
m (4 revisions imported) |
||
(One intermediate revision by one other user not shown) | |||
Line 19: | Line 19: | ||
*Position Control | *Position Control | ||
*Telemetry & Datalogging | *Telemetry & Datalogging | ||
sensor the first three items will be run all the time, and the last will only be executed if there is enough time. We will put in ,some kind of check to ensure that telemetry is going out sometime, even if the timers are being overrun. |
Latest revision as of 20:30, 30 March 2024
Software Design should be layout out here.
Should have an initial design that outlines the major components, and how they inter communicate.
In order to fully describe a motion status of an object, 6 variables are needed, 3 linear coordinate: x, y, z, and 3 angular coordinate α, β, γ. accelerometer can measure the x y z and gyro can measure the α, β, γ, so 6 variables are all measured by the 2 elements, you get the exact status.
Implementation Considerations
- code will be implemented in c++
- application will be single threaded, design may or mayn't take this into consideration.
Main Loop
- Sensor Reading
- Sensor combing
- Position Control
- Telemetry & Datalogging
sensor the first three items will be run all the time, and the last will only be executed if there is enough time. We will put in ,some kind of check to ensure that telemetry is going out sometime, even if the timers are being overrun.