Skip to content
Snippets Groups Projects
Select Git revision
  • 32f580a174b8464a1d209748d0091ed5b7fca239
  • main default protected
2 results

TODO.md

Blame
  • Forked from Jake Read / machineweek-2023
    8 commits ahead of the upstream repository.
    user avatar
    Jake Read authored
    32f580a1
    History

    Machine Week TODO

    • check in about TA input / meetings every day ... !

    Demo Building

    • assemble, photograph and doc (exports) the linear dof
    • assemble, photograph and doc (exports) the rotary dof
    • ... one-dof code (!)
    • finish xylo update with the router
      • x unfk the shite cable routing
        • consider... this could be example w/ new linear axis...
        • also included: limit switches !
      • write HAL (w/ homing) for quentin
    • the little guy
      • x assemble the little guy
      • program the little guy (using new drivers?)
      • put the little guy in a repo / get a demo video ?

    Kit Assembly

    • they need extra hardware and probably zip ties
    • should get some rotary blades ee-wise - roland drop-ins
    • finalize router, hbridge, deadbugger, stepper firmwares and load / test them all
    • finish one complete kit and grab a photo
      • need 2 finish firmwares for hbridge, deadbugger, and stepper so that we can load finals on
      • need 2 test 'em all
      • (maybe get a better one) pic of controller kit as well, w/ router, two motors, one of each deadbugger (wired to servo, in-case) and h-bridge (wired to solenoid, in-case)

    Repo / Docs

    • the little guy, the xylophone
      • standalone repos I think, w/ all hardware / software / circuits ?
      • ... consider doing the same for simple linear axes, since we re-use those occasionally as well ? IDK - consult w/ quentin
    • them little wire management things
    • notes on making ribbon cables
    • for controllers: CAD for mounts
    • mount patterns for other things: extrusion sizes, linear axes dimensions (and bolt patterns) ?

    Other Odds / Ends / Thoughts for Later

    • raspberry pi's on the demo machines ?
    • firmware programming ... how will they do it ?
      • should/could we promote the anything-as-a-python-object codes ?
    • how to rename devices, besides just uploading new firmwares ?
    • limit switch boards, or some other way to Reduce Limit Switch Suffering (or fk it, focus on code)
    • a backpack-to-whatever circuit / it's reciprocal ?
      • jlcpcb rush assy ?
    • should demo projects get rolled into standalone repositories ?
    • the handbook ?
    • the mega compound plotter ?