probatio / probatio-docs

Other
1 stars 0 forks source link

Improve the documentation of the 3d printing files. #3

Open jtragtenberg opened 4 years ago

jtragtenberg commented 4 years ago

I felt the naming of the stl files helped a lot to know what I needed to print to make the bases and blocks I wanted, but it could improve a lot with a well illustrated guide. A wiki showing what are the final forms of all the bases and blocks, showing which stl was which part of the model. I got specially confused with the base internal margin, which I didn't have a clue of its purpose, neither could understand what each support was meant for. There could be together with the guide a brief explanation of what some of the parts are intended for. It would also help to describe which parts can or have to be manually modified after printing. My block didn't fit in the 1x3 base hole, can I cut it until it passes through it? The side pogo-pins got stuck in it, should that happen? What about the base_margins? It didn't fit perfectly. Is that normal? can I cut any part of it out? I got elephant footing in some of my prints, is it tolerable? In which models? How do I make the connections between the 1x3 base and top strong? Do I have to glue them together? Which glue should I use? Can I use some clamps to hold the together for gluing? How should the pcbs fit in the base? Can I cut the internal margins for them to fit loosely? Should the fit be perfect to hold them by pressure? Do they need to be glued to the base? How?

jtragtenberg commented 4 years ago

It would also help to have a description of the electronic components I need to make each block. I didn't know if the joystick would be good to make a joystick block. Some amazon, digikey, aliexpress links to the components or some datasheets would help for me to make sure I got them right. I don't want to print a model to find out it doesn't fit my component in.

jtragtenberg commented 4 years ago

I liked the redundancy between some models with different file-names which were the same model, but it would help to have in the documentation something reaffirming that.