Page Comparison

• `Roni Kant Will be promoted as the new EFS Lead starting next term! Congrats to Roni 🎉

• Sahil will be holding a bootloader workshop with the Orbital team @ 8:30 tonight

Drivers

• IMU driver - Kelvin Feng

  • PR received approvals and ready to be merged

• Sensor Fusion - Polly Liu & Liam Suter

  • prototyping with bmx160

  • Code tested and functioning on arduino

    • Need to calibrate the sensor as it’s not giving reasonable data currently

    • Starting code for the IMU on the STM32 in the meantime

• GPS

  • new task opening?

• Fail-Safe Fix - Uzayr Hussaini Andrew Wang

  • no update, Hardy Yu will follow up

  • pr is up with merge conflicts?

Attitude Manager Anthony Luo

• Same as last week. Waiting on sensor fusion and IMU

System Manager Hardy Yu

• no update

Telemetry Manager Yarema Dzulynsky

• Created proposal to simplify remote TM development

Path Manager Ayoung Eun

• Ideation Code Currently working to determine the required altitude and were wondering if we have a fixed wing specification available still (When we test it, would we still use that foam plane?). This would help us figure out the optimal altitude and speed for takeoff and landing.

• Just to double check, sensor fusion still works right? I know it’s in ZP 3.5 but just to double check if it still functions properly.

Infrastructure

Core Dump Kabir Verma

• I wanted to download the testing rig and kinda stuck on the versioning and ideal setup so wanted some help there.

ZP Validation Image Ethan Leung

• Fake Arduinos arrived and they are working. Running into some troubles during testing but not blocked

• Worked on the ADC tests cases.

ZP3.5 M2 Bring-Up Sherry Lai

• Was able to properly build ZP3.5 on laptop

Drivers Ethan Leung

• Message Queue Dami Peng

  • Finished interface and pushed onto message_queue branch

• Motor Channel (PWM) Bill Lu

  • After our sync/help session Bill has started on writing his interface and some function definitions.

• RC Receiver Chandise Anderson

  • I’ve started to work on the driver, but starting to run into issues with writing the interface. I will ask about it

• Watchdog Ronald You

  • Ronald is pretty much done and is working out some final details for his driver.

Attitude Manager Sam Zhang

• No updates, just waiting for the finalized interface between drivers for the PWM motor function and the queue.

System Manager Manasva Katyal

• Wrote out SM interface and scaffolding for the implementation

• PR has been made, awaiting approval

• Will be meeting with the team to delegate the function bodies before next meeting

ESC (Jeffery Zhen)

• continuing to work on the CAN component

• need to test DShot by plugging in a motor

Servo Tharun Ganeshram Fion Lin Herman Gahra

• Larry Pan Modifying code to handle interrupts LIFO instead of FIFO

Sensor Cluster Roni Kant

• Tochi Okoro finished code, will be testing in the bay in a few days with dev board

• Henry Wu Yutong Zhu Getting good results from sensors and different config options also seem to be working, working on getting DMA set up

• Aidan Fisher Most of the driver is written, working on implementing a specific mode for getting data from the rangefinder

• Ria Prakash Porting to cpp pretty much finished now, looking into different configuration options for the sensor and adding some more config options to the driver

• Roni Kant General update: Decided to use FreeRTOS with each sensor on a thread. Also going to implement the CAN driver hopefully this week when porting the CAN driver to L4 is done.

LED Board Folarin Fatola (Unlicensed)

• Worked on debugging the CAN integration code

• TODO: Enable one lighting board node to act as a master for the rest of the lighting boards

6s Power Module Bryan Ma Harry Chen

• The doc for the CAN interface has definitely helped a bit in understanding the CAN architecture, and how it’s used in conjunction with DroneCAN

• We will still need to learn more about DroneCAN and Nucleo L5’s CAN connectivity in general, before we know how to receive a message from the FC.

• After that we’ll continue learning/doing from there