ubitux/shimonbox

Semi-automatically generated 3D printable cases for development boards using OpenSCAD

ShimonBox

ShimonBox is an OpenSCAD project aiming at providing semi-automatically generated 3D printable cases for development boards.

See pkh.me introduction blog post for more information.

Supported boards

Board name	Preview
BeagleBone Black
Cubieboard
Hikey (LeMaker)
NanoPi Neo 2
Orange Pi Zero
Raspberry Pi 3

Corresponding cases

Board name	Preview	Status
BeagleBone Black		VERIFIED:
Cubieboard		VERIFIED:
Hikey (LeMaker)		VERIFIED:
NanoPi Neo 2		VERIFIED:
Orange Pi Zero		VERIFIED:
Raspberry Pi 3		VERIFIED:

Usage

To make all the .stl files, run make. The resulting files will be found in the cases/ directory.

If you're looking at building individual parts, you can use make cases/<board>-<part>.stl where <board> is the board name and <part> is the part you want to build (bottom, top, or button).

shimonbox's Issues

Add Pine A64 board support

I am working on adding the specs for the pine a64 board.

Add little notch/groove between bottom/top lid?

My first print in #1 fits pretty tightly, since the bottom case flexes a tiny little bit because my PCB holes were ~0.2mm off (fixed in my current branch).

But generally, the top part is just 'resting' on the bottom part. What do you think about adding a little groove around the lip that would click into the bottom part?

I would give it a try to modify the case.scad and use a 0.5mm cylinder + a cut on the bottom side that makes the two halves clip together. Any thoughts on this?

Reduce redudancy when defining boards

Hey there,

currently adding one or two more boards. While doing this, I also thought about writing a little doc about how to add new boards.

I noticed that I had to put the board name at several places… like defining the base plate it needs an individual name. Then again I also need to add the board to the top-level file boards.scad.

I did not yet read through all the files completely, thus I do not fully understand why it needs to be defined at so many places. Maybe OpenSCAD has some functions to redcuce the redundancy at some points, thus making it easier to add new ones. When I find more specifig things, I will report back to this issue. :-)

Add CONTRIBUTING.md

Issue to track progress on writing a CONTRIBUTING.md :-)
A rough, initial plan has been written by ubitux already in #2 which was:

Here is a quick & dirty howto:

• create boards/.scad following other .scad files in the same directory. This .scad is directly open-able with openscad.
• if necessary, add the electronic components in electronics/.scad. The .scad files are directly open-able with openscad.
• register the board in boards.scad (include of boards/.scad, mapping array to the info function, and the 2 modules entries)
• create cases/.scad following other .scad files in the same directory (this one should be pretty simple). This .scad is directly open-able with openscad.
• if your board has button pushers, you want to register it in cases/Makefile (BOARDS_WITH_BUTTON_PUSHERS)
• make -j$(nproc) gif will generate the gif (it may take some time)
• edit the .md files to add the necessary entries (board, cases, electronics).
  This step could be automatized, but it lacks a description to extract from somewhere. Maybe a // @desc or whatever in the .scad files or whatever could do the trick (extracted with a grep or whatever).