Let’s Design pib Together!
Motivation: How, what, why?
Wir alle wollen pib weiterentwickeln. Jeder von uns bringt hier tolle Ideen ein, und hätte die am liebsten sofort umgesetzt. Aber welche Ideen nehmen wir auf, welche nicht, und wie entscheiden wir das?
Damit wir gemeinsam mit Spaß an pib arbeiten können brauchen wir ein gemeinsames Verständnis, was pib ausmacht und wo die Reise hingehen soll. Der Designguide soll euch dabei mit der Weiterentwicklung eurer Ideen und in euren Entscheidungen unterstützen.
Hier erklären wir alles, was es für die Weiterentwicklung von pib zu beachten gilt. Wenn ihr Fragen habt, könnt ihr euch natürlich gerne jederzeit an uns wenden.
Great Minds Work Alike
Let's get the best out of pib together! Do you have questions, suggestions or concrete ideas for the further development of pib? In the forum we are looking forward to your ideas!
Principles: This is important to us
|Humanoid||The pib.rocks team believes in the future of humanoid robots. Our environment and our tools are chosen for us as people. Instead of having individual specialized robots for each task, pib naturally becomes a part of our familiar world.|
|3D printable||Good ideas are feasible. All parts of pib must be able to be created as easily and realiably as possible with standard printers.|
|Open||pib is and will remain open. That holds true for the hardware as well as software and also for the development process we are using.|
|Maintainable – aka “no glue!”||pib’s parts must be easily exchangable and updatable. Even if it is tempting to quickly glue some parts together – we are conscioulsy doing without that! We are putting a lot of effort into the easy maintainability of pib.|
|Great user experience||pib is intuitively buildable because the parts explain themselves and follow a central theme which is this design guide.|
|Great community, documentation and support||We – the pib community – have a shared vision that we want to work on together. We are excited about each new member! For an appreciative cooperation we value but also demand the principles of our code of conduct.|
|Accessible||Gaining access to pib should be as simple as possible. Even though there may be plenty of great building parts that could optimize pib, we are trying to focus on non-printable parts that are as widely available and as affordable as possible.|
Name conventions for parts
The names of the building parts consist of English identifiers connected by underscores and follow the convention:
<Body part>_<Function>_<Specification 1..N>
The body part begins with a capital letter, the other elements are either in lowercase letters or, if compound, in camelCase notation.
The body part corresponds to the part studio in which the part is being developed (Arm, Body, Hand, Leg, …) and enables us to quickly find the correct position in the CAD document. Especially since we reuse some parts in different places this is helpful for the navigation. This indication is mandatory.
The function describes what the building part is being used for with pib. Ideally, an anatomic indication is being used which of course is not always possible. A few examples are:
- for the attachement of the joint which enables the lifting of the arm (“abduction”), the description is “abductionMount”
- for the carrying shell it’s “shell”
- for the mount of the motors “motorMount”
Connections are made with M3 screws with Allen screw. The corresponding hexagon nuts have a height of 2.5 mm.
Simple drill holes for the M3 screws have a diameter of 3.2 mm. For countersunk bolts the following modulations are used:
For the nuts, hexagonal recesses are being set. In Onshape, you will use a hexagon with an inner diameter of 2.85 mm.