/
2025-01-27 EFS Meeting

2025-01-27 EFS Meeting

 

 

 

 

 

  • Please fill out the leadership interest form if you would like to become a lead starting S25:

  • Microsoft Forms

 

 

 

 

  • Lots of people interested in EFS social (16). Need to find location big enough.

 

 

 

 

 

 

 

 

  • Firmware Jobs & Interview Workshop this Tuesday (tmrw) 8-9:30pm in E7 4417 and online

 

M1 Drivers @Ethan Leung

  • Message Queue @Dami Peng

    • Header done

    • Starting the implementation

 

 

  • Motor Channel (PWM) @Bill Lu

    • Met issue when trying to control the servo

    • Mostly there

 

 

 

 

  • RC Receiver @Chandise Anderson

    • Finished code, going to submit PR

 

 

 

 

  • Watchdog @Ronald You

    • New abstraction done. PR pending approval.

 

  • SD Card @Ari Van Cruyningen

    • Submitted PR, just need to test it

 

 

M2/3/4 Drivers

  • RFD900 @Aditya Bang

    • Configured and connected, having trouble sending messages

 

 

 

 

  • IMU + AHRS @Liam Suter @Kelvin Feng @Richard Dong

    • Accelerometer looks fine

    • Gyroscope oscillating, might have been causing getting yaw data

    • Trying to mitigate oscillation

    • Then working on implementing filter

 

  • GPS @Ria Prakash @Ronak Patel

    • Been reading through the data sheet

    • The output given by the module looks good

    • Will be implementing later this week

 

 

  • CRSF @Uzayr Hussaini

    • Check on progress, might move to another task as we might not use CRSF driver

 

 

Attitude Manager @Ayoung Eun

  • 1-to-1 Motor Output @Ayoung Eun

    • Made tweaks based on your comments left on Ayush’s commit. However, I do have some questions.

 

 

 

  • Failsafe @Raiyan Samin

    • Waiting on PR

 

 

 

 

  • Arm / Disarm @Raiyan Samin

    • Waiting on PR

 

 

 

 

 

System Manager @Manasva Katyal

  • RC Passthrough @Sreya Roy Chowdhury

    • Took a look, open to continue though the PR, comments to be reviewed

    • Changing to push to AM queue instead of SM queue

 

 

 

 

  • Kick Watchdog @Sreya Roy Chowdhury

    • To be done but easy

 

 

 

 

 

Infrastructure @Thuvaragan Prathifkumar

  • Meeting with Derek today

 

 

 

 

 

ZP Board Validation @Ari Van Cruyningen

  • Started communicating with the ZP board

  • IO and PWM timer pins done

  • SPI, UART, I2C next

  • Putting together a validation image

 

 

LED Board @Nick Armstrong@Tochi Okoro @Billy Karantzoulis

  • Worked on implementing the central node election algorithm

  • Billy joined the team and is taking a look at writing Ardupilot-side scripts in Lua to generate CAN messages with info like altitude, speed, etc

  • Tochi and I are still looking into what she wants to work on

 

 

 

Servo @Hardy Yu @Allan Su @Ethan Leung

  • Onboarded both Allan and Ethan on this project

  • Not much has been done so far, we are a little blocked by the hardware

    • single servo drive pcbs are missing plz let us know if anyone has seen it

    • 6s servo module rev2 is currently undergoing its assembly

    • maybe we could use 6s servo module rev1 for now or just focus on the software

 

 

 

 

6s Power Module @Bryan Ma@Aditya Sharma @Andrew Wang

 

 

 

 

 

Baud Rate Auto Sensing @Teighan Miller

  • Code to test and detect common Baud Rates is written.

  • Next steps are to test the code on a board to see if it's working properly.

  • Working on learning how the CAN Bus connects to the Nucleo Board

 

 

 

 

 

Sensor Cluster

  • Barometer

    • On pause until EE gets board

  • IMU

    • Paused until ZP driver

  • Lidar @Aidan Fisher

    •  

  • Magnetometer @Henry Wu

    • getting CAN transaction to and from ArduPilot

    • code refactoring and pushing code to Github

    • turning magnetometer in ArduPilot (Magfit?)

  • PixArt OFS

    • Paused until EE board

  • Radar @Henry Wu

    • driver doesn’t look too difficult to setup

    • look at example code

 

 

Tracking Antenna @Larry Pan @Jackie Yi

  • We were trying to parse the bytes that were dumped from last semester, but pymavlink is not parsing properly.

  • Probably because the bytes were in decimal and not hex

  • Just got hex data from simulation, will work to get hex from the drone soon.

 

 

 

Related content