After my final project is done, I will continue improving it along a few points.
Firstly, I will make the electronics integration better. I will design a new and more secure electronics enclosure, and make cable management better. I will use stronger connectors and get rid of jumper wires.
I will work on integrating stronger stepper motors to the design, since the ones I currently have are not enough to provide the array of movements I want from the head & neck. I will further optimize the wire connections to smooth out the movements. I have to tinker with the code as well, to achieve accelerating simultaneous movements between the motors. After I achieve what I want with two motors, I will move on to integrating new features.
A servo will be integrated to the head to control the mouth movements, for it to open & close it’s beak. Another stepper will be put on the body for hip movement from the leg joints. They will be integrated into the control interface as well.
The last step would be to update the control interface. I can turn it into something more user-friendly or physical, like a joystick. Finally, I can integrate some sensors into the design to make it reactive to the environment, which would make it an exhibition piece.
For IP purposes, this design can either stay as an exhibition piece, or it can be commercialized into a DIY kit like the animatronic raven kit.
As an exhibition piece, it can be part of digital fabrication/ new media exhibitions. If I can make a more robust package and either make it automatic or more easily controllable, it could run for longer times on it’s own.
As a commercial DIY kit, I would have to optimize many parts in the project to reduce costs. Maybe I could transition into servo motors instead of steppers, and use a cheaper microcontroller than a Xiao. I should also streamline the process of building it and assembling it.
CERN OHL is a license that encompasses hardware and product designs and regulations regarding their studying, sharing and distribution. It aims provide a legal basis for the sharing of open-source hardware, and the creation of subsequent iterations over these shared works.
Products of all sorts such as ventilators, cameras, satellites and even beer has been licensed under a form of CERN OHL. Electronics projects such as microcontrollers or integrated circuit designs can also be included within CERN OHL.
My project could be licensed under CERN OHL, since it is a physical product design. Hardware design in this context also covers things like PCB schematics too, for example. Therefore it would be a good fit to license my work as a whole. If it becomes a DIY kit in the future as I said, licensing it under CERN OHL could be especially helpful.
MIT License is mainly used for open-source software projects. It is a relatively accessible FOSS licence, which allows users to do pretty much everything with the code as long as they include the original MIT license in all copies of the end product.
It allows for commercializiation and any developer can use an MIT License in their works if they are familiar with the terms.
Compared to CERN OHL, MIT License does not include hardware or physical products. And it would not be very applicable to my final project, as I mainly used and modified code made by other people and the project is not software-heavy.
Although, if I wanted to, I could licence the project under several different licences. For example, the hardware could be under CERN OHL and the software could be under MIT. As long as I explicitly communicate this, it would be valid.
Creative commons licenses are used for works of media such as videos, photographs, podcasts, stories, datasets, scientific publications etc. They are not recommended to be used for hardware or software. For a creative commons license to be applied to a work, it’s enough to publicly declare it in a way that is comprehensible by the viewer. Once a license is applied, it cannot be revoked.
CC-BY-4.0 is a license that allows for the remix, adaptation, distribution or commercialisation of the work, as long as credit is given to the original author.
CC-BY-4.0 can also be applied to documentation. So if I wanted to apply a license to my Fab Academy documentation page (but for the documentation part only!), this could be a good option.
For this weeks assignment, I chose to license my design under CERN Open Hardware License v2 Permissive.
In order to add this license to my work I followed this guide:
“Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.”
I also added a text in my footer saying “This work is licensed under CERN Open Hardware License v2 Permissive.”
|
|