diff --git a/CAD/belt_axis/belt_axis.f3z b/CAD/belt_axis/belt_axis.f3z new file mode 100644 index 0000000000000000000000000000000000000000..4ca6c5de7fa10246864ee194d966ffbe7a1f518f Binary files /dev/null and b/CAD/belt_axis/belt_axis.f3z differ diff --git a/CAD/belt_axis/belt_axis_kit.stl b/CAD/belt_axis/belt_axis_kit.stl new file mode 100644 index 0000000000000000000000000000000000000000..fc69c94e9e1b2737bbf4fe61cfd583a4a4cd4e19 Binary files /dev/null and b/CAD/belt_axis/belt_axis_kit.stl differ diff --git a/CAD/belt_axis/belt_clip_bod.stl b/CAD/belt_axis/belt_clip_bod.stl new file mode 100644 index 0000000000000000000000000000000000000000..ddae2349fbbb1705ce737efb8b29596ff500ab04 Binary files /dev/null and b/CAD/belt_axis/belt_clip_bod.stl differ diff --git a/CAD/belt_axis/belt_clip_cap.stl b/CAD/belt_axis/belt_clip_cap.stl new file mode 100644 index 0000000000000000000000000000000000000000..8f88909d9ab4d20b6b76977f1bebf1d8b5a5626b Binary files /dev/null and b/CAD/belt_axis/belt_clip_cap.stl differ diff --git a/CAD/belt_axis/belt_idler_body.stl b/CAD/belt_axis/belt_idler_body.stl new file mode 100644 index 0000000000000000000000000000000000000000..fac5798da24184d3073f10db15132d929c892fa5 Binary files /dev/null and b/CAD/belt_axis/belt_idler_body.stl differ diff --git a/CAD/belt_axis/belt_idler_cap.stl b/CAD/belt_axis/belt_idler_cap.stl new file mode 100644 index 0000000000000000000000000000000000000000..1ead3334e03335e57e9a5b7257591d395ecfaf6f Binary files /dev/null and b/CAD/belt_axis/belt_idler_cap.stl differ diff --git a/CAD/belt_axis/belt_motor_mount.stl b/CAD/belt_axis/belt_motor_mount.stl new file mode 100644 index 0000000000000000000000000000000000000000..2ef8dd5b5ac20ca8dcec90e83216788822d2975d Binary files /dev/null and b/CAD/belt_axis/belt_motor_mount.stl differ diff --git a/CAD/leadscrew_axis/leadscrew_axis.f3z b/CAD/leadscrew_axis/leadscrew_axis.f3z new file mode 100644 index 0000000000000000000000000000000000000000..1d4ca9536e19063e0827d85ac365bb5a0e6d40d9 Binary files /dev/null and b/CAD/leadscrew_axis/leadscrew_axis.f3z differ diff --git a/CAD/leadscrew_axis/leadscrew_axis_kit.stl b/CAD/leadscrew_axis/leadscrew_axis_kit.stl new file mode 100644 index 0000000000000000000000000000000000000000..0135d76c86e1d7e064a532d9221cb5d1aef9909e Binary files /dev/null and b/CAD/leadscrew_axis/leadscrew_axis_kit.stl differ diff --git a/CAD/leadscrew_axis/leadscrew_clip.f3d b/CAD/leadscrew_axis/leadscrew_clip.f3d new file mode 100644 index 0000000000000000000000000000000000000000..614c60307bf11cbee714f7909031a3fb715a7972 Binary files /dev/null and b/CAD/leadscrew_axis/leadscrew_clip.f3d differ diff --git a/CAD/leadscrew_axis/leadscrew_clip.stl b/CAD/leadscrew_axis/leadscrew_clip.stl new file mode 100644 index 0000000000000000000000000000000000000000..36262f5aba577f512fe99a1baf9bb73aa08df4f4 Binary files /dev/null and b/CAD/leadscrew_axis/leadscrew_clip.stl differ diff --git a/CAD/leadscrew_axis/leadscrew_motor_mount.stl b/CAD/leadscrew_axis/leadscrew_motor_mount.stl new file mode 100644 index 0000000000000000000000000000000000000000..5df6721669f0d71cfefb0a5f233bede25e98dae8 Binary files /dev/null and b/CAD/leadscrew_axis/leadscrew_motor_mount.stl differ diff --git a/CAD/parts/cart.stl b/CAD/parts/cart.stl new file mode 100644 index 0000000000000000000000000000000000000000..4876e383385d8ad48e014be28b72373a29433097 Binary files /dev/null and b/CAD/parts/cart.stl differ diff --git a/CAD/parts/foot.f3d b/CAD/parts/foot.f3d new file mode 100644 index 0000000000000000000000000000000000000000..060fe48c009c2ffdd7bcbd2c630c927ba377f75d Binary files /dev/null and b/CAD/parts/foot.f3d differ diff --git a/CAD/parts/foot.stl b/CAD/parts/foot.stl new file mode 100644 index 0000000000000000000000000000000000000000..240ca0e5e3e8f77f3dbdf74557b90ad068617518 Binary files /dev/null and b/CAD/parts/foot.stl differ diff --git a/CAD/parts/gusset_T.f3d b/CAD/parts/gusset_T.f3d new file mode 100644 index 0000000000000000000000000000000000000000..8c26375d72c35df64144286ccf781ffb22016eaa Binary files /dev/null and b/CAD/parts/gusset_T.f3d differ diff --git a/CAD/parts/gusset_T.stl b/CAD/parts/gusset_T.stl new file mode 100644 index 0000000000000000000000000000000000000000..c9f9c97c157c19939a5963dc9088f80fa4b8d840 Binary files /dev/null and b/CAD/parts/gusset_T.stl differ diff --git a/CAD/parts/gusset_elbow.f3d b/CAD/parts/gusset_elbow.f3d new file mode 100644 index 0000000000000000000000000000000000000000..807f94b077e2f0879489cfc95771cda3cdadb216 Binary files /dev/null and b/CAD/parts/gusset_elbow.f3d differ diff --git a/CAD/parts/gusset_elbow.stl b/CAD/parts/gusset_elbow.stl new file mode 100644 index 0000000000000000000000000000000000000000..ec4e7624aaa2a8c57a24cdf483e8b3d82955a801 Binary files /dev/null and b/CAD/parts/gusset_elbow.stl differ diff --git a/CAD/parts/leadscrew_motor_mount.f3d b/CAD/parts/leadscrew_motor_mount.f3d new file mode 100644 index 0000000000000000000000000000000000000000..e60bfcdde83b700d5ffcf6bf0a08ebbc23ae8e27 Binary files /dev/null and b/CAD/parts/leadscrew_motor_mount.f3d differ diff --git a/CAD/parts/limit_mount.stl b/CAD/parts/limit_mount.stl new file mode 100644 index 0000000000000000000000000000000000000000..58c23bd0168a1c23d789ade089e4dca7a350e848 Binary files /dev/null and b/CAD/parts/limit_mount.stl differ diff --git a/CAD/rotary_axis/rotary_axis.f3z b/CAD/rotary_axis/rotary_axis.f3z new file mode 100644 index 0000000000000000000000000000000000000000..3486b85199744ddf64d479cf159aac57601d5145 Binary files /dev/null and b/CAD/rotary_axis/rotary_axis.f3z differ diff --git a/CAD/rotary_axis/rotary_axis_kit.stl b/CAD/rotary_axis/rotary_axis_kit.stl new file mode 100644 index 0000000000000000000000000000000000000000..f7f4e849a9b38533876517ecf427e9a2b82cafd8 Binary files /dev/null and b/CAD/rotary_axis/rotary_axis_kit.stl differ diff --git a/CAD/rotary_axis/rotary_barrel_cap.stl b/CAD/rotary_axis/rotary_barrel_cap.stl new file mode 100644 index 0000000000000000000000000000000000000000..5931517d93dc7e9a29f4345b17963579008e7384 Binary files /dev/null and b/CAD/rotary_axis/rotary_barrel_cap.stl differ diff --git a/CAD/rotary_axis/rotary_barrel_toothed.stl b/CAD/rotary_axis/rotary_barrel_toothed.stl new file mode 100644 index 0000000000000000000000000000000000000000..d785ca8eb6ecf3c538b452ad53e8da0e2a02036d Binary files /dev/null and b/CAD/rotary_axis/rotary_barrel_toothed.stl differ diff --git a/CAD/rotary_axis/rotary_body.stl b/CAD/rotary_axis/rotary_body.stl new file mode 100644 index 0000000000000000000000000000000000000000..743823cbbad6f3bb491f105582737cd42bcd1c14 Binary files /dev/null and b/CAD/rotary_axis/rotary_body.stl differ diff --git a/CAD/rotary_axis/rotary_body_cap.stl b/CAD/rotary_axis/rotary_body_cap.stl new file mode 100644 index 0000000000000000000000000000000000000000..d0045bcaf00198b82285e78d521dc9ccfc8936ce Binary files /dev/null and b/CAD/rotary_axis/rotary_body_cap.stl differ diff --git a/README.md b/README.md index d5a0aa5475d925c02f8dcb98ae0e926bbd11390a..e3bdb703ecfe93a9fb08f0858e4d01f971c56b18 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,46 @@ # Simple Machine Kit +> Circa [Machine Week 2023](https://gitlab.cba.mit.edu/jakeread/machineweek-2023) +### Belt Axis [[CAD](CAD/belt_axis/belt_axis.f3z)] -## Getting started +<img src=img/belt_axis.png width=50%><br> -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +Kit [[stl](CAD/belt_axis/belt_axis_kit.stl)] -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +<img src=img/belt_axis_kit.png width=50%><br> -## Add your files +### Leadscrew Axis -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +Assembly [[CAD](CAD/leadscrew_axis/leadscrew_axis.f3z)] -``` -cd existing_repo -git remote add origin https://gitlab.cba.mit.edu/jakeread/simple-machine-kit.git -git branch -M main -git push -uf origin main -``` +<img src=img/leadscrew_axis.png width=50%><br> -## Integrate with your tools +Kit [[stl](CAD/leadscrew_axis/leadscrew_axis_kit.stl)] -- [ ] [Set up project integrations](https://gitlab.cba.mit.edu/jakeread/simple-machine-kit/-/settings/integrations) +<img src=img/leadscrew_axis_kit.png width=50%><br> -## Collaborate with your team +### Rotary Axis -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +Assembly [[CAD](CAD/rotary_axis/rotary_axis.f3z)] [[notes](https://ekswhyzee.com/2019/04/09/gt2-belt-rotary-cad.html)] -## Test and Deploy +<img src=img/rotary_axis.png width=50%><br> -Use the built-in continuous integration in GitLab. +Kit [[stl](CAD/rotary_axis/rotary_axis_kit.stl)] -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) +<img src=img/rotary_axis_kit.png width=50%><br> -*** +### Framing -# Editing this README +T gusset [[CAD](CAD/parts/gusset_T.f3z)][[stl](CAD/parts/gusset_T.stl)] -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. +<img src=img/gusset_T.png width=50%><br> -## Suggestions for a good README +Elbow gusset [[CAD](CAD/parts/gusset_elbow.f3z)][[stl](CAD/parts/gusset_elbow.stl)] -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. +<img src=img/gusset_elbow.png width=50%><br> +--- -## Name -Choose a self-explaining name for your project. +## The Xylophone -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. + \ No newline at end of file