2024-05-17 EFS Director Sync

Begin developing for CAN architecture now?

• help with IC selection

  • all CAN boards share the same STM and the same CAN transceiver circuit

  • EE should approve STM32L431KCU6

• see project priority order in 2024-05-16 Electrical Director Sync

• these boards will very small cant run a LFQP144

• https://www.st.com/content/st_com/en/stm32-mcu-product-selector.html

• Projects

  • Servo Module Improvements micro and CAN is on our custom PCBA

  • ESC CAN Adapter our custom PCB solders onto the COTS PCBA

  • Sensor Cluster we implement sensor drivers and micro and CAN is on our custom PCBA

    • imu and gyro live in pixhawk and not on this board, i left comments

  • Custom CAN Hub outline for a “generalized” CAN board

    • this is more generalized but the STM and CAN transceiver will be custom on all

    • we wanna do specific ones EE wise so the connector to the endpoint is able to be 1:1

    • this has options for MCU selection

    • Implementation summary for EE is given by Custom CAN Hub | Plan for Implementation very nicely!!

How is team taking the shift?

• team is ok with it

• senior members seem interested in new directions

Plans for ZP tests?

• EE Side of ZP

  • end of next week Ryan is looking to finish interface board

  • will need EFS to help test functionality

  • ask for help with system diagram and intended hardware

• Mech side ZP

  • foam plane again, will need help engineering this to house ZP

  • 2024-05-10 Mechanical Director Sync

  • mech wants to help ensure we have a good plane

• M2

  • pushing for end of June to cross the finish line on this, before midterms hopefully

  • AM has most the work remaining, need to figure out what's happening

  • SD Card SD card is almost done

  • TM needs some written

• M3

  • concern is we might not make M3

    • will send experienced people to the new stuff and will lose people on ZP

      • there’s a while before we actually get our CAN hardware in there

      • once we get microcontroller locked in then development is able to start on EFS side for CAN boards

  • most work is in AM

    • anni was carrying, but left

    • we want to run the PID through simulator first

  • rough target is more than next term

New Project Ideas

• Wifi network we’ve talked about

  • requires more architecture though

  • main stuff is with tracking antenna so we don’t have to run wires to everything

    • we may still need mavproxy to pipe mavlink messages around everywhere

    • if we dont need bidirectional we dont need mavproxy?

  • low power low interference

• tracking ant improvements

  • https://discord.com/channels/776618956638388305/1174564563270774854/1239987255901425734

    • “If we use the ardupilot antenna tracker software we could use a minipix and the vectornav”

    • “It would be cool if you could use sensors in addition to the external ahrs, though that's more of a drone thing. Right now if you have external ahrs you can't use optical flow for example”

  • mech input

    • should make it clear to mech we need a way to mount GPS antenna and compass devices far above the rest of the components

    • antennas go below

    • maintain spacing between video receiver and ELRS receiver

    • mounting for gemini and minipix (or whatever custom controller we make to run ardu)?

What should Roni work on?

• Continue on tracking antenna stuff for now bc most important

  • fixing compass and imu stuff

    • compass is hard one for calibration

  • starting work on hotspot/wifi sutff

    • we need to do architecture here

  • ardu support imu?

    • no calibration for imu

• would prefer to put him on CAN development over ZP stuff

• CAN development

  • entails assigning a senior member of a lead to look into how products implement

  • should be able to find open source examples online

  • dont wanna put Roni on it bc we dont have implementation details