diff --git a/README.md b/README.md index b40fff2a6fc729bb51ac120431f35848c4f8fcc7..ccc9838540cf8b2c7b65e0ce8891b18535ddf2cd 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,98 @@ # Metallic Kusudama +<img src="img/tdgarden2.png" width=700px center=left> -## Getting started +<img src="img/cbalogo.png" width=700px center=left> -To make it easy for you to get started with GitLab, here's a list of recommended next steps. -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)! +## Introduction -## Add your files +**Kusudama is a form of modular Origam that, by assemblying same-shape cells, generates an enclosed volume shape (sphere like, but the structure is based on classic polyhedron.)** -- [ ] [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: +Some time ago, since I got the last book of Ekaterina Lukasheva [Modern Kusudama Origami](https://kusudama.me/), I had in mind to build edge-unit polyhedra but maybe, one order of magnitude bigger than conventional modular folds... -``` -cd existing_repo -git remote add origin https://gitlab.cba.mit.edu/alfonso/metallic-kusudama.git -git branch -M main -git push -uf origin main -``` +Modular Origami heavily relies on octahedron, cubes, icosahedron and dodecahedron. I decided to design my own Kusudama and to do so, I revisited a type of polyhedra that I consider incredibly interesting, the family of [fleible polyhedra](https://en.wikipedia.org/wiki/Flexible_polyhedron). These shapes have DOFs that change the form of the polyhedra without alter the facets. -## Integrate with your tools +Doing so, I could have a geometrical structure in the form of edge-Kusudama but with a degree of freedom. I choosed a [Jeesen's Icosahedron](https://en.wikipedia.org/wiki/Jessen%27s_icosahedron), discovered by the french mathematician [Adrien Douady](https://en.wikipedia.org/wiki/Adrien_Douady). It has an interesting chiral deformation that will be shown later in the documentation. -- [ ] [Set up project integrations](https://gitlab.cba.mit.edu/alfonso/metallic-kusudama/-/settings/integrations) +<img src="img/jessens.png" width=600px center=left> -## Collaborate with your team +As my research is pointing more and more towards folding metals, I decided to make a huge shiny aluminum Kusudama, something I have not seen yet before and I was very excited to see. I have some ideas for next iterations with the material looking. -- [ ] [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/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +A month ago, friends from [Infra](https://www.infrabos.com/) contacted me to make an installation for the Boston Boiler Room and I decided to go with this! Jurgis Ruza and I have worked last week in the nights to make this happen. -## Test and Deploy -Use the built-in continuous integration in GitLab. -- [ ] [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) -*** +## Structural Design -# Editing this README +As I have some spare sheets of Hylite, a 3M aluminum composite with 1.2mm thickness and PP core, I decided this is the best fit material to build the structure out of. I would double face mill the peaks and valleys and join modules with M3 bolts. -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!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. +As the Icosahedron is non regular, but still resembles the node counts as a regular one, I just detail designed one node, and then, spatially alocate this design 12 times to get the full model. -## Suggestions for a good README -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/node.png" width=600px center=left> -## Name -Choose a self-explaining name for your project. +<img src="img/complete.png" width=600px center=left> -## 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. +Each node is a folded sheet that holds 5 beams. It uses 36 screws and hosts in the tip a translicent peak that will host a PCB with LEDs to make the nodes to shine! -## 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. +<img src="img/bolts.png" width=600px center=left> -## 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. +All models can be downloaded from the CAD folder. -## 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. +I also designed a base to host the power and controll of the structure and to be hanged from the cealing. -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. +<img src="img/CADbase.png" width=600px center=left> -## 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. +## Electronic Design -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. +Two PCBs were degidned, one to host the LEDs on the nodes and other to transfer to each of them data and power. The Node board, host very bright LEDs and 360nm wavelength UV leds. Those operates at different volts and are controlled through PWM. To take logic levels to it desired values (5V and 12V), I installed two N-mosfets to each of the LEDs. The schematics and board layouts can be downloaded from CAD. -## License -For open source projects, say how it is licensed. +<img src="img/nodePCB.png" width=600px center=left> -## 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. + +An external 12V power supply will feed the microcontroller and the LEDs through a second PCB called the distribution board. + +<img src="img/distributionPCB.png" width=600px center=left> + +Then, I just had to manufacture 1 of the power and 12 of the distribution boards. I added aluminum tape in the back of the PCBs so they are almost invisible when installed in the nodes of the structure! + +<img src="img/pcbmanuf.gif" width=400px center=left> + +<img src="img/pcblayout.png" width=600px center=left> + + +## Manufacturing + +<img src="img/flat.png" width=600px center=left> + +With everything cutted in the Zund, is time to assembly and put hose 36 * 12 bolts to make this! + +<img src="img/manuf1.gif" width=600px center=left> + +<img src="img/manuf2.gif" width=400px center=left> + +The structure is done, and circuits are integrated, is blinking and working very well : + +<img src="img/blink.gif" width=600px center=left> + +## Boiler Room + +Now its time to transport the structure to Big Night Live, at the TD Garden. Its was pretty ridiculous to insert that on a pickup. + +<img src="img/pickup.png" width=600px center=left> + +<img src="img/tdgarden.png" width=700px center=left> + +And the party was a blast. + +<img src="img/boiler.png" width=700px center=left> + +<img src="img/boiler2.jpg" width=700px center=left> + +(thanks to infra for this pic) \ No newline at end of file diff --git a/img/CADbase.png b/img/CADbase.png new file mode 100644 index 0000000000000000000000000000000000000000..9495ceb038b9cb1474a97cd65327f7741b0f0a4d Binary files /dev/null and b/img/CADbase.png differ diff --git a/img/Translucent_Jessen_icosahedron.svg b/img/Translucent_Jessen_icosahedron.svg new file mode 100644 index 0000000000000000000000000000000000000000..454828a502b95380fdcabc4ce702da0f73ffd537 --- /dev/null +++ b/img/Translucent_Jessen_icosahedron.svg @@ -0,0 +1 @@ +<svg viewBox="-0.5 -0.5 1 1" width="512" height="512" xmlns="http://www.w3.org/2000/svg"><g fill="#D8F0FF" fill-opacity=".9" stroke="#000" stroke-linejoin="round" stroke-width=".005"><path d="M-.344.137l.38-.255.069.457z"/><path d="M.037-.118L.11-.46l-.006.8z"/><path d="M.111-.46l-.074.342-.392-.141zm.274.394L.111-.46l-.006.8zm-.729.203L-.44.075l.476-.193z"/><path d="M.105.34l.28-.058-.73-.145z"/><path d="M.385.282l-.28.057.28-.405zm-.74-.542l-.084.335.476-.193z"/><path d="M-.115.474l.5-.192-.73-.145zm.513-.632L.111-.46l.274.394z"/><path d="M-.439.075l.095.062.23.337zm.55-.535l.287.302-.753-.101z"/><path d="M-.122-.397l.52.24-.753-.102z"/><path d="M-.122-.397L-.44.075l.084-.334zm.507.679L-.047.15l.432-.216z"/><path d="M.398-.158L-.047.15l.432-.216zm-.837.233l.317-.472.007.871zm.392.075l.432.132-.5.192z"/><path d="M-.047.15l-.075-.547.007.871z"/><path d="M.398-.158L-.047.15l-.075-.547z"/></g></svg> \ No newline at end of file diff --git a/img/base.jpeg b/img/base.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..99e5698e5f0db1af3abd68dda730a8fc12ac60a8 Binary files /dev/null and b/img/base.jpeg differ diff --git a/img/blink.gif b/img/blink.gif new file mode 100644 index 0000000000000000000000000000000000000000..9d167ff409269e59b17b2cf1bb4823a063146f42 Binary files /dev/null and b/img/blink.gif differ diff --git a/img/boiler.jpeg b/img/boiler.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..839ddaa72dc14e0e85cf97846d7021e5654151ac Binary files /dev/null and b/img/boiler.jpeg differ diff --git a/img/boiler2.jpg b/img/boiler2.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dc183b351e8dca043f668797476a4201e224095 Binary files /dev/null and b/img/boiler2.jpg differ diff --git a/img/bolts.png b/img/bolts.png new file mode 100644 index 0000000000000000000000000000000000000000..cbff731787d3083afe9158c0b6d5ce0752c27a77 Binary files /dev/null and b/img/bolts.png differ diff --git a/img/cbalogo.jpeg b/img/cbalogo.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..7d841035f29c36a9512dc7850f00a78e9953402f Binary files /dev/null and b/img/cbalogo.jpeg differ diff --git a/img/complete.png b/img/complete.png new file mode 100644 index 0000000000000000000000000000000000000000..c6e8cc00227751b916dcf31764c935b7e92729eb Binary files /dev/null and b/img/complete.png differ diff --git a/img/distributionPCB.png b/img/distributionPCB.png new file mode 100644 index 0000000000000000000000000000000000000000..5b5774431f51d96f0c261f02a89cc87c95cd778b Binary files /dev/null and b/img/distributionPCB.png differ diff --git a/img/ekaterina.png b/img/ekaterina.png new file mode 100644 index 0000000000000000000000000000000000000000..321f45196d13e87262d2cb0ae300ebb161f838a2 Binary files /dev/null and b/img/ekaterina.png differ diff --git a/img/flat.jpeg b/img/flat.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..cecba8be19e7fcb52b23bfdd7a378a516af37612 Binary files /dev/null and b/img/flat.jpeg differ diff --git a/img/jessens.png b/img/jessens.png new file mode 100644 index 0000000000000000000000000000000000000000..7509da16f5fb6d8557d57833de73ad98033bfc11 Binary files /dev/null and b/img/jessens.png differ diff --git a/img/manuf1.gif b/img/manuf1.gif new file mode 100644 index 0000000000000000000000000000000000000000..886beda08bed146a6812f2b3b4dc90d0e4691d88 Binary files /dev/null and b/img/manuf1.gif differ diff --git a/img/manuf2.gif b/img/manuf2.gif new file mode 100644 index 0000000000000000000000000000000000000000..52642000b29919f5a73efd2389bf93272d04be54 Binary files /dev/null and b/img/manuf2.gif differ diff --git a/img/node.png b/img/node.png new file mode 100644 index 0000000000000000000000000000000000000000..8328c795a90795f4d461bc04cd719a28990fe565 Binary files /dev/null and b/img/node.png differ diff --git a/img/nodePCB.png b/img/nodePCB.png new file mode 100644 index 0000000000000000000000000000000000000000..b7bab23bcf671672802868aafa6365a326839d7f Binary files /dev/null and b/img/nodePCB.png differ diff --git a/img/pcblayout.png b/img/pcblayout.png new file mode 100644 index 0000000000000000000000000000000000000000..d0b1186ee84bf593d88eca2af319110fdc2b3926 Binary files /dev/null and b/img/pcblayout.png differ diff --git a/img/pcbmanuf.gif b/img/pcbmanuf.gif new file mode 100644 index 0000000000000000000000000000000000000000..7d6900b5703e805f66ae2b8091e1e44219efad13 Binary files /dev/null and b/img/pcbmanuf.gif differ diff --git a/img/pickup.jpeg b/img/pickup.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..7616e7e187a826b585159d4d9295549c21c5e1fe Binary files /dev/null and b/img/pickup.jpeg differ diff --git a/img/tdgarden.png b/img/tdgarden.png new file mode 100644 index 0000000000000000000000000000000000000000..b2c0027ab71f7aa6ce4453fa7b680bc5c9e3d030 Binary files /dev/null and b/img/tdgarden.png differ diff --git a/img/tdgarden2.png b/img/tdgarden2.png new file mode 100644 index 0000000000000000000000000000000000000000..f9fd1a8b058a22fcba0fc2368334780b310d2365 Binary files /dev/null and b/img/tdgarden2.png differ