\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
Framework Requirements to overtake Simulink
...
Able to integrate C code (ZP3)
Able to simulate wind/imu/noise
Visualize simulation, (able to import CAD model for later models, not important right now)
Able to reitarate models easily
Accurate dynamic/physic model
Manual inputs / Real-time inputs?
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
8pm | Revalidating previous architecture proposal | See Simulator | |
8:15pm | State requirements |
| |
8:20pm | ZP3 Integration | ||
8:35pm | IMACS Integration | ||
8:45pm | FreeRTOS Integration | ||
8:55pm | ZP3 submodule/Repo structure |
PID Tuning for Attitude Manager? (Need accurate model to have accurate PID values)
Big challenge; finding parameters
Milestones
Revalidate framework, 1 week, MS#1
Researching on fixed-wing dynamics, 1 week, MS#2
Verifying flowchart / architecture (scope), 1-2 weeks, MS#3
What ZP3 code to integrate
What functions, what they do, inputs/outputs, what data types
Simulink model
Pretty decent fixed-wing simulator model, 2-3 months, MS#4
Very simple model working (then reiterate with bit more complex model), MS#4a
Develop physics model of fixed-wing
Manual (vector user input) and controller MS#4b
Integrating ZP3/C code (motor outputs, sensor fusion), MS#4c
Decent quad simulator, hard to estimate timeframe (more complex dynamics) MS#5
Branch off from fixed-wing model when basics are established (different people work simultaneously)
Tuning the model, hard to estimate timeframe MS#6a
Flight data (analyzing geometry, aerodynamic flow)
Determintion of coefficents and aerodynamic derivatives
Refit simulator to competition drone, MS#7
...
2. 1 on simulink model, 1 integrating ZP3 code into matlab