I think figuring out how to precisely affix the polygon in an entirely repeatable fashion should be your next step. I can't help but think the polygon should be cut to accommodate a fastener of some sort. When you have a dead center fastener then you can built it as starting point for making your own polygon motor. Eventually, it may be possible to put all components on a single PCB which would reduce things like alignment issues as well as the overall size.
I made a blog on the current motor pcb. I have a technique for fixing the prism now which is quite okay. It takes minutes, making the electronic boards and wiring is the most time consuming step. This can take hours if you do it by hand. I think most import for developers is that the technology is robust and the software is refactored enough so new components can be added. The last days I tried to improve deployment using poetry, https://python-poetry.org/ , and the like.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
I think figuring out how to precisely affix the polygon in an entirely repeatable fashion should be your next step. I can't help but think the polygon should be cut to accommodate a fastener of some sort. When you have a dead center fastener then you can built it as starting point for making your own polygon motor. Eventually, it may be possible to put all components on a single PCB which would reduce things like alignment issues as well as the overall size.
Are you sure? yes | no
I made a blog on the current motor pcb. I have a technique for fixing the prism now which is quite okay. It takes minutes, making the electronic boards and wiring is the most time consuming step. This can take hours if you do it by hand.
I think most import for developers is that the technology is robust and the software is refactored enough so new components can be added. The last days I tried to improve deployment using poetry, https://python-poetry.org/ , and the like.
Are you sure? yes | no