- Last Week’s Action Items
- [x] Figure out for sure brushed vs brushless
- [x] Update the decision matrix with the decision
- [x] Pick the motor (speak to supplier if needed figure out driver aspect)
- [ ] Pick motor driver (preferably off digikey) Phase 2.2: non-ADCS-related component sourcing
- [x] Look into open source C libraries for the motor we choose (possibly even talk to kiran)
- Probably have to control motors using PWM pins from RM46 ← make our own library in C
- [ ] Finish up board sch by end of this week
- It is tentatively finished
- [ ] Sort out the drivers stuff for the motors
- [ ] @Aryan K to get back on some mentorship for joel on motor control stuff
- [ ] @Shreya Singh to reach out to prof amir for board review stuff
- Overall Progress + Blocks (if any to address)
- Motor picking
- No longer have a height requirement
- Could go with bigger motors to meet the torque requirements within the power constraints
- Starting work on the IMU
- Writing code for the vn-100 and setting it up
Action Items (due by end of this week)
- [ ] To ask CDH regarding sending PWM signals using Halcogen
- [ ] Repick the motors based on the requirements by June 29, 2022
- [x] @Hugh Dawson to confirm height constraint for the motor
- [x] Repick the motor + selecting motor driver
- [ ] @Hugh Dawson to review the final motor picked too
- [ ] Finish sch
- [ ] Continue working on motor driver
- [x] Figure out how to send PWM signals from RM46
- Well I’ve figured out how to generate PWM signals using the HET1 timer Driver on the RM46, but still cant test it because of the error message that I’m getting when I try to load the code (not related to the software).
- Alternatively, there are designated extended PWM modules built into the RM46 that can also be used if needed.
- [ ] Add to orbital git
- [x] Get started with the VN-100 testing
- [x] Starting with technical manuals + documentation
- [x] Getting their software running
- [x] Possibly getting some readings working
- See VN-100 intial readings