2022 - 01 -11 (jan 11)

First meeting of the term!

 

Meeting plan:

  1. Icebreakers

  2. Interesting facts

  3. Goal for this term

  • Asana task updates

  • How we’re going to conduct ourselves

 

attendance:

introduction of team leads!

few new members! Ice breakers :D

Icebreakers

Aidan

  • systems design

  • just finished 2b (4th co-op)

  • varsity curling team! !

  • want to learn how to use STM Microcontrollers.

Andre V

  • biomedical engineering

  • currentyl 1b

  • play volleyball

  • Further code in c++

Anthony

  • Robust plane in the air

Chris

  • finished 2a mechatronics, doing co-op right now

  • Likes to juggle

  • gain some more experience with STM’s

Dhruv

  • finished 2a, on co-op right now.

  • gliders license before could drive.

  • build a drone that’s robust, modular. hopefully we learn.

Gordon

  • just finished 2b (co-op)

  • like playing cello ?!

  • do something cool!

Neha

  • finished 2a tron.

  • do something cool and learn something.

Nixon

  • tron 2a

  • work on diff things and learn as much as you can.

Tony Bertnyk

  • 2a tron

  • Can fence

  • Want to see code fly

Yashraj

  • 2a tron (on co-op)

  • speedcubing/yoyoing

  • gain firmware experience

Manav

  • 2a tron (co-op)

  • like watching anime !

  • learn about firmware!

Shrinjay

  • team lead of warg

  • was cv teach lead

  • likes going to ghost towns to take

Aadi

  • 2a tron (on co-op)

  • drone not falling out of the sky.

 

Goals to hit this term

  • robust code

  • mentorship

  • try to learn from each other.

    • methods of assigning tasks and running meetings.

    • pairing old + new members.

    • standups by team members.

      • when making PR, give a quick presentation to the team (or give a quick status update on what your code does and what you have learned).

      • include documentation.

  • -

 

Status updates

  • 2-3 week hiatus over winter?

  • restarting now.

  • if you worked on something, please give a quick update. If new member, don’t say anything.

 

  • aadi

    • before took break had test programs written for sending data through xbees

    • code has been accumulated.

    • meeting with CV have as little clue as we do for data firmware wise.

    • Gordon has list from previous comp (confluence outdated).

    • Develop requirements from comp reqs.

    • Meeting with Jeffrey (CV Co-op) and all leads.

      • thing for groundstation is looking at data or sending commands

  • Aidan

    • had done nothing over exam period?

    • looking at doing PID tuning.

    • Hover to Waypoint Manager

    • no new task

  • Gordon

    • firmware bootcamp revamp done now? Being implemented. Chris tested it out → first person through

    • ready for another task

  • Neha

    • IMU Driver has been merged into github

  • Nixon

    • got nucleo from dhruv.

    • tried to run driver on it.

    • getting some errors on the SD card.

    • same error on devboard.

      • error with sdcard not having spi enabled

      • try to get sdcard with spi enabled.

    • can flash on board

  • Tony

    • last explicit task was wrapped up (PID LOOP MODE state)

    • helped out a bit with cmake integration and getting safety rtogether

    • nothing specific being worked on

  • Dhruv

    • AM rearchitect (Tony and Dhruv working on moving it from autopilot to safety).

    • State machine being redone.

    • Controls drone orientation in space.

  • Yashraj

    • firmware-cv comms

    • finished uart driver, pr in. waiting for review.

    • data formatting defined before starting.

    • how to put that into telemetry manager

  • Kaveet

    • ghosted the team for 2.5 months. (xd)

    • no task.

  • Manav

    • Last thing was failsafe implementation

    • ready for new task.

Overview of Available tasks

→ all up on Asana (https://app.asana.com/0/187002107997407/list)

  • giving idea of tasks available, you can see them on asana.

  • Based on open tasks, we will be send out a google form and you’ll put in preferences and how you plan to implement them. (hopefully nobody fighting on tasks)

General comments

  • documentation for the documentation

    • need styles for documentation

  • Integrate confluence with documentation && github pull request.

  • Â