SBC Case Builder

[hominoid]

This project is about autonomous SBC case creation. It utilizes the SBC Model Framework project to automatically generate cases based on the data for any given SBC contained within the framework. This allows legacy, current and future SBC to have multiple cases available on day one of their inclusion in the framework. There are multiple base case designs(shell, panel, stacked, tray) available and each allows for different styles within the design. New designs and styles will be added in the future as well as accessories.

sbc_case_builder_designs.gif (3.85 MiB) Viewed 3592 times

All case openings are created automatically based on SBC data and, the dimensions of any case design can be expanded in any axis allowing for the creation of larger cases. If you reposition the SBC in a case, you will see i/o openings created or removed appropriately based on it’s proximity to the case geometry. These cases might be useful for prototypes or other in house uses to create standard, specialized and custom SBC cases thru different case designs, styles and accessories.

c4-tray_vu5.gif (7.81 MiB) Viewed 3592 times

The first case “style” to be completed is “vu5” for the case design “tray”, which features screw on sides. It is a fully parametric case which integrates a Vu5 display and uses the Vu Series of cases. There are numerous parameters that can be set to customize the case size, attributes and features.

Code: Select all

view = "model";                         // viewing mode "platter", "model", "debug"

case_design = "tray";                   // "shell", "panel", "stacked", "tray"
case_style = "vu5";                     // style of case_design
                                        // tray: none, vu5

sbc_model = "c4";                       // any sbc from sbc model framework: "c1+","c2","c4","hc4"
                                        // "xu4","xu4q","mc1","hc1","n1","n2","n2+","h2"
                                  
pcb_loc_x = 5;                          // sbc location x axis
pcb_loc_y = 0;                          // sbc location y axis
case_offset_x = 0;                      // additional case x axis size
case_offset_y = 0;                      // additional case y axis size
case_offset_tz = 0;                     // additional case top z axis size
case_offset_bz = 4;                     // additional case bottom z axis size
wallthick = 2;                          // case wall thickness
floorthick = 2;                         // case floor thickness
sidethick = 3;                          // case side thickness
gap = 1.5;                              // distance between pcb and case
indents = true;                         // indentations around io openings
sidewall_support = true;                // enable wall support for standoffs
sbc_top_standoffs = false;              // enable sbc top standoffs
sbc_bottom_standoffs = true;            // enable sbc bottom standoffs
case_ext_standoffs = false;             // enable case extended standoffs
sata_punchout = true;                   // enable sata punchout
gpio_opening = "none";                  // gpio openings "none","vent","open","punchout"
cooling = "fan";                        // "none", "vents", "fan", "custom" using ./dxf/customfan.dxf
exhaust_vents = "vent";                 // exhaust vents "none","vent"
fillet = 0;                             // edge fillets

Even at the minimal size the Odorid-C4 “tray-vu5” case is well balanced and very stable with it’s fixed 15 degree viewing angle. The case does need 4mm extra bottom height for nut holders(case_offset_bz = 4). If a top mounted fan is going to be used, an extra 15mm minimum in the y-axis(case_offset_y) will be required for clearance. Since it’s a tray design, no top standoffs are needed(sbc_top_standoffs = false). One note about the “exhaust_vents = vents” setting, the vent it creates is as wide as the SBC heatsink and it shares it’s location with the gpio opening on most cases. “gpio_opening” takes precedence and requires “gpio_opening = none” to enable “exhaust_vents = vents”. If you want both a vent and future gpio access, There is gpio_opening = "vent" which is a vent the same width as the gpio header which could be easily cut out if needed later.

All cases build correctly with default setting with the exception of the N2’s. The N2 and N2+ SBC need some additional width to accommodate the integrated heatsink. By setting case_offset_x =10 and pcb_loc_x = 5, enough room is created for the correct fit while centering the SBC in the case. Unlike the C4, the N2’s don’t need the extra bottom space either, case_offset_bz = 0;

n2plus-tray_vu5.gif (3.28 MiB) Viewed 3592 times

Here are the SBC Case Builder settings that were used for the N2+ model above, which will also work for the N2. Once the configuration storage and accessory framework is in place, there will be no need to know these details.

Code: Select all

view = "model";                         // viewing mode "platter", "model", "debug"

case_design = "tray";                   // "shell", "panel", "stacked", "tray"
case_style = "vu5";                     // style of case_design
                                        // tray: none, vu5

sbc_model = "n2+";                      // any sbc from sbc model framework: "c1+","c2","c4","hc4"
                                        // "xu4","xu4q","mc1","hc1","n1","n2","n2+","h2"
pcb_loc_x = 5;                          // sbc location x axis
pcb_loc_y = 0;                          // sbc location y axis
case_offset_x = 10;                     // additional case x axis size
case_offset_y = 0;                      // additional case y axis size
case_offset_tz = 0;                     // additional case top z axis size
case_offset_bz = 0;                     // additional case bottom z axis size
wallthick = 2;                          // case wall thickness
floorthick = 2;                         // case floor thickness
sidethick = 3;                          // case side thickness
gap = 1.5;                              // distance between pcb and case
indents = true;                         // indentations around io openings
sidewall_support = false;               // enable wall support for standoffs
sbc_top_standoffs = false;              // enable sbc top standoffs
sbc_bottom_standoffs = false;           // enable sbc bottom standoffs
case_ext_standoffs = false;             // enable case extended standoffs
sata_punchout = true;                   // enable sata punchout
gpio_opening = "none";                  // gpio openings "none","vent","open","punchout"
cooling = "fan";                        // "none", "vents", "fan", "custom" using ./dxf/customfan.dxf
exhaust_vents = "none";                 // exhaust vents "none","vent"
fillet = 3;                             // edge fillets

Accuracy and Utility
In the past there was been no way of validating whether a SBC Model Framework model and it’s components were dimensionaly accurate in their size and placement other then trial and error. Along with producing cases this project provides a much needed model validation tool to assure model accuracy thru the use of test cases. It works on the very simple premise that if the real SBC fits the test case then the virtual model is accurate or otherwise shows were corrections are needed. This will further increased the overall accuracy of models. I have started validation of SBC models in the SBC Model Framework but it will take some time to get thru all of them.

Additionally, template creation and i/o panel layouts in a dxf format can be easily created and integrated into other designs or for hand fabrication by sectioning a case panel for the desired SBC. The case design “panel” will most likely work best. If your new to CAD here is an example of how to section an 3D stl to a 2D dxf format using OpenSCAD (towards the bottom of the post).

SBC Case Builder Goals
SBC Model Framework Validation Tool – complete (model validation in progress)
Autonomous Multi-SBC Multi-Case Generation –complete
Customization Framework – complete

Future Features:
Case configuration storage with pre-defined cases - complete

Additional base case designs
--sliding
--round/cylinder
--snap-together

Additional case styles
--tray-vu5 - complete
--tray-vu7 - complete
--tray-sides - complete

Accessories framework
geometry additions and subtractions
--circle - complete
--rectangle - complete
--slot - complete
--text - complete
--art(dxf or svg) - complete
--punchout - complete
--fans - complete
--vents - complete
--standoffs - complete
--rtc battery holder - complete
--uart holder - complete
--drive mount - complete
--oled holder - complete
--case access panels - complete
--H2 network card - complete
--buttons – complete
--cable holders/strain relief
--sdcard holders

There is still considerable work to be done to reach all of the goals of this project. The initial basic autonomous case creation is complete and can produce standard cases. More case designs and styles will be developed with the intent to keep all case designs fully parametric. The customization framework, when complete, will come with predefined cases that will serve as examples. With 10’s of cases available from the first release, not every case and SBC combinations can be tested so any report of problems will be appreciated and receive priority. Have an idea for a case design, style, or an accessory I haven’t mentioned, let me know and I will try to incorporate it into SBC Case Builder.

Notes:
All libraries are included and with ongoing development may be newer than posted release.
Due to the number of possibilities, no pre-compiled stl’s are included.
This is a work in progress.

February 2, 2022 - initial release
sbc_case_builder-v1.0.zip

February 6, 2022 - added try-vu7 style and various fixes
sbc_case_builder-v1.0.1.zip

February 12, 2022 Version 1.1.0
implemented sbc_case_builder.cfg configuration file, sbc_case_builder_library.scad and basic accessory framework. Adjusted tray-vu7 tabs, adjusted tray-vu7 model alignment. Minor fixes and other maintenance.
sbc_case_builder-v1.1.0.zip

February 20, 2022 Version 1.1.1
accessory placement additions and fixes, added .cfg commands add1,add2,suball,model,platter, schema changes, extended standoff fixes, hd mounting accessories
sbc_case_builder-v1.1.1.zip

February 27, 2022 Version 1.1.2
added sbc_off setting, fixed hdmi bottom placement, schema change, extended standoff detection, hd vertical mount, oled holder, access port, access cover, case feet and other fixes
sbc_case_builder-v1.1.2.zip

March 6, 2022 Version 1.1.3
added h2_netcard, buttons, parametric access_port, other fixes and maintenance

March 12, 2022 Version 1.2.0
added fillet array, button cutout style, hk_lcd35, other fixes and maintenance
sbc_case_builder-v1.2.0.zip

March 20, 2022 Version 1.2.1
hk_boom bonnet model and accessories, hk_uart model, fixed uart opening, enabled pcb_z, added tabs and fixed tray case top, other fixes and maintenance

April 6, 2022 Version 1.2.2
vu7c, vu8m and weatherboard2 models, other additions, fixes and maintenance

May 15, 2022 Version 1.2.3
standardized and fully enabled autonomous case openings, new top for tray design, new tray style "sides", several new cases for odroid-m1 and other sbc.
additional library modules, updated SBC Model Framework.

SBC_Case_Builder-1.2.3.zip

(3.81 MiB) Downloaded 5 times

sbc_case_builder.scad
sbc_case_builder_library.scad
sbc_case_builder.cfg
tolerance_check.scad
./dxf
./lib
./stl

[hominoid]

Case Designs and Styles
The case naming convention for standard cases in the configuration file follow the basic form of “sbc”_”design”_”style” e.g. c4_shell or c4_tray_vu5. As new designs and styles are added this graphic will be kept up to date as a visual reference for all available cases.

SBC_Case_Builder-110_Cases.gif (1.32 MiB) Viewed 234 times

Current Case Count 110
Odorid-C1+ cases - 12 : c1+_shell,c1+_panel,c1+_panel_lcd3.5,c1+_desktop_lcd3.5,c1+_stacked,c1+_tray,c1+_tray_sides,c1+_tray_vu5,
c1+_tray_vu7,c1+_shell_boombox,c1+_panel_boombox,c1+_tray_boombox
Odorid-C2 cases - 13 : c2_shell,c2_panel,c2_panel_lcd3.5,c2_desktop_lcd3.5,c2_stacked,c2_tray,c2_tray_sides,c2_tray_vu5,
c2_tray_vu7,c2_shell_boombox,c2_panel_boombox,c2_deskboom_lcd3.5,c2_tray_boombox,
Odorid-C4 cases - 13 : c4_shell,c4_panel,c4_panel_lcd3.5,c4_desktop_lcd3.5,c4_stacked,c4_tray,c4_tray_sides,c4_tray_vu5,
c4_tray_vu7,c4_shell_boombox,c4_panel_boombox,c4_deskboom_lcd3.5,c4_tray_boombox
Odorid-HC4 cases - 11 : hc4_shell,hc4_shell_drivebox2.5,hc4_shell_drivebox2.5v,hc4_shell_drivebox3.5,hc4_panel,hc4_stacked
,hc4_tray,hc4_tray_sides,hc4_tray_vu5,hc4_tray_vu7,hc4_tray_drivebox2.5
Odorid-N1 cases - 7 : n1_shell,n1_panel,n1_stacked,n1_tray,n1_tray_sides,n1_tray_vu5,n1_tray_vu7
Odorid-N2 cases - 5 : n2_panel,n2_tray,n2_tray_sides,n2_tray_vu5,n2_tray_vu7
Odorid-N2+ cases - 5 :n2+_panel,n2+_tray,n2+_tray_sides,n2+_tray_vu5,n2+_tray_vu7
Odorid-XU4 cases - 7 : xu4_shell,xu4_panel,xu4_stacked,xu4_tray,xu4_tray_sides,xu4_tray_vu5,xu4_tray_vu7
Odorid-XU4Q cases - 7 : xu4q_shell,xu4q_panel,xu4q_stacked,xu4q_tray,xu4q_tray_sides,xu4q_tray_vu5,xu4q_tray_vu7
Odroid-MC1 cases - 0
Odroid-HC1 cases - 0
Odroid-HC2 cases - 0
Odroid-H2 cases - 13 : h2_shell,h2_lowboy,h2_lowboy_router,h2_shell_router,h2_shell_routerssd,h2_panel,h2_stacked,h2_tray,h2_tray_sides,
h2_tray_vu5,h2_tray_vu7,h2_tray_router,h2_router_station
Odroid-Show2 cases - 1 : show2_shell
Other cases - 10 : jetsonnano_shell,jetsonnano_panel,jetsonnano_stacked,jetsonnano_tray,jetsonnano_tray_sides,
rockpro64_shell,rockpro64_panel,rockpro64_stacked,rockpro64_tray,rockpro64_tray_sides

Case and Accessory Schema
The schema for case configuration and accessories is documented in the beginning of the file sbc_case_builder.cfg. It has not been finalized and may be subject to changes in the near future as development in these areas is ongoing. Here is a review of the current schema which will be updated as needed for each release. The schema is divided into two areas, case and accessories. There are 30 fixed entries that describe any given case followed by an unlimited number of accessory entries each containing 14 entries.

schema:

Code: Select all

    "case_name","sbc_model","case_design","case_style",
    pcb_loc_x,pcb_loc_y,pcb_loc_z,case_offset_x,case_offset_y,case_offset_tz,case_offset_bz,
    wallthick,floorthick,sidethick,gap,fillet,
    indents,sidewall_support,sbc_top_standoffs,sbc_bottom_standoffs,case_ext_standoffs,mode
    sata_punchout,"gpio_opening","cooling","exhaust_vents",
    top_standoff[    6.75,     // diameter
                       18,     // height (top_height)
                      2.5,     // holesize
                       10,     // supportsize
                        4,     // supportheight
                        4,     // 0=none, 1=countersink, 2=recessed hole, 3=nut holder, 4=blind hole
                        0,     // standoff style 0=hex, 1=cylinder
                        1,     // enable reverse standoff
                        0,     // enable insert at top of standoff
                      4.5,     // insert hole dia. mm
                      5.1],    // insert depth mm
    bottom_standoff[ 6.75,     // diameter
                        5,     // height (bottom_height-pcb_z)
                      3.6,     // holesize
                       10,     // supportsize
                        4,     // supportheight
                        1,     // 0=none, 1=countersink, 2=recessed hole, 3=nut holder, 4=blind hole
                        0,     // standoff style 0=hex, 1=cylinder
                        0,     // enable reverse standoff
                        0,     // enable insert at top of standoff
                      4.5,     // insert hole dia. mm
                      5.1],    // insert depth mm
    top_ext_standoff[    6.75, // diameter
                       18,     // height (top_height)
                      2.5,     // holesize
                       10,     // supportsize
                        4,     // supportheight
                        4,     // 0=none, 1=countersink, 2=recessed hole, 3=nut holder, 4=blind hole
                        0,     // standoff style 0=hex, 1=cylinder
                        1,     // enable reverse standoff
                        0,     // enable insert at top of standoff
                      4.5,     // insert hole dia. mm
                      5.1],    // insert depth mm
    bottom_ext_standoff[ 6.75, // diameter
                        5,     // height (bottom_height-pcb_z)
                      3.6,     // holesize
                       10,     // supportsize
                        4,     // supportheight
                        1,     // 0=none, 1=countersink, 2=recessed hole, 3=nut holder, 4=blind hole
                        0,     // standoff style 0=hex, 1=cylinder
                        0,     // enable reverse standoff
                        0,     // enable insert at top of standoff
                      4.5,     // insert hole dia. mm
                      5.1],    // insert depth mm

    "class","type",loc_x,loc_y,loc_z,face,rotation[],size_x,size_y,size_z,data_1,data_2,"data_3",data_4[]

Fixed Schema Entries
The 30 fixed schema entries are self-evident based on their name.

• case_name = “case_name”
  sbc_model = any sbc from sbc model framework: "c1+","c2","c4","hc4","xu4","xu4q","mc1","hc1","n1","n2","n2+","h2"
  case_design = "shell", "panel", "stacked", "tray"
  case_style = “style” of case_design (tray: none, vu5, vu7)
  pcb_loc_x = sbc location x axis
  pcb_loc_y = sbc location y axis
  pcb_loc_z = sbc location z axis
  case_offset_x = additional case x axis size
  case_offset_y = additional case y axis size
  case_offset_tz = additional case top z axis size
  case_offset_bz = additional case bottom z axis size
  wallthick = case wall thickness
  floorthick = case floor thickness
  sidethick = case side thickness
  gap = distance between pcb and case
  fillet = edge fillets
  indents = enable indentations around io openings (true or false)
  sidewall_support = enable wall support for standoffs (true or false)
  sbc_top_standoffs = enable sbc top standoffs (true or false)
  sbc_bottom_standoffs = enable sbc bottom standoffs (true or false)
  case_ext_standoffs = enable case extended standoffs (true or false)
  sata_punchout = enable sata punchout (true or false)
  gpio_opening = gpio openings "none","vent","open","punchout"
  cooling = "none", "vents", "fan", "custom" using ./dxf/customfan.dxf
  exhaust_vents = exhaust vents "none","vent"
  top_standoff[] = top pcb standoffs
  bottom_standoff[] = bottom pcb standoffs
  top_ext_standoff[] = top extended standoffs
  bottom_ext_standoff[] = bottom extended standoffs
  mode = special mode "net_card"

Accessories Configuration Entries
The accessories entries need more explanation because of their input variability. For accessories there are 6 classes, “add1”,“sub”,”suball”,”add2”,”model”,”platter” and all use the same command format for various “type”.

"class","type",loc_x,loc_y,loc_z,size_x,size_y,size_z,"face",rotation[],data_1,data_2,"data_3",data_4[]

Code: Select all

"sub","rectangle",3,78,-.1,8,8,5,"bottom",[0,0,0,],0,0,"",[1,1,1,1],

Every type, regardless of it’s class, uses a basic set of variables(loc_x,loc_y,loc_z,”face”,rotation[]) but each type doesn’t necessarily use all available data fields(size_x,size_y,size_z,data_1,data_2,”data_3”,data_4[]). “add1” and “add2” are used to add geometry to the case. The difference is when the addition occurs. “add1” happens at the beginning when the core case geometry is created and add2 happens after all subtractions have occurred. “suball” is used to affect all faces of a case, not just “face”. The “face” is the case piece that will be effected by the addition or subtraction. The "model" type is for placing supporting accessories in the model view. e.g. hard drives, fans. The "platter" type is for adding supporting accessories to the print platter.

classes: add1, sub, suball, add2, model, platter

additive type: circle, rectangle, slot, text, art, standoff, batt_holder, uart_holder, hd_holder, hd_holes, hd_vertright_holes, hc4_oled_holder, access_port, button, pcb_holder, boom_grill, boom_speaker_holder
subtractive type: circle, rectangle, slot, text, art, punchout, vent, fan, hd_holes, hd_vertleft_holes, hd_vertright_holes
model type: uart_strap, fan_cover, hd25, hd35, hc4_oled, feet, access_cover, net_card, hk35_lcd, hk_boom, boom_speaker, boom_vring, hk_uart
platter type: uart_strap, fan_cover, access_cover, button_top, boom_vring

Shared add and sub “type” commands
-circle
description: circlular geometry.
uses: size_x=dia, size_z=height
-rectangle
description: rectangular geometry with individual defined corner fillets. Radius1 is lower left corner then moves clockwise.
uses: size_x, size_y, size_z, data_4=[radius1, radius2, radius3, radius4]
-slot
description: slot geometry.
uses: size_x=diameter, size_y=length, size_z=height
-text
description: raised or sunk text
uses: data_1=size, data_3="text"
-art
description: art work in dxf or svg format
uses: data_1=scale, data_2=height, data_3=file

Add class only “types”
-uart_holder
description: console uart holder
uses: none
-batt_holder
description: rtc battery holder
uses: none
-standoff
description: user defined standoff
uses: data_4=

• [ 6.75, // radius
  5, // height
  3.6, // holesize
  10, // supportsize
  4, // supportheight
  1, // 0=none, 1=countersink, 2=recessed hole, 3=nut holder, 4=blind hole
  0, // standoff style 0=hex, 1=cylinder
  0, // enable reverse standoff
  0, // enable insert at top of standoff
  4.5, // insert hole dia. mm
  5.1] // insert depth mm

-hd_holder
description: double stacked holder for 2.5 and 3.5 drives
uses: data_1=2.5 or 3.5, data_3=”portrait” or “landscape”
-hd_vertleft_holder
description: vertical left side holder for 2.5 and 3.5 drives
uses: data_1=2.5 or 3.5, data_3=”portrait” or “landscape”
-hd_vertright_holder
description: vertical right side holder for 2.5 and 3.5 drives
uses: data_1=2.5 or 3.5, data_3=”portrait” or “landscape”
-hc4_oled_holder
description: hc4 oled holder
uses: size_z=floorthick
-access_port
description: bottom access for sd and emmc
uses: size_z=floorthick, data_3=”portrait” or “landscape”
-button
description: button top and plunger
uses: size_x=diameter,size_z=height, data_3=”reccess”
-pcb_holder
description: pcb bottom edge holder
uses: size_x=pcb_x,size_y=pcb_y,size_z=pcb_z, data_1=wall_thick
-boom_grill
description: hk boom bonnet grill covers
uses: data_3="flat", "dome", "frame"
-boom_speaker_holder
description: hk boom bonnet speaker friction holder
uses: data_1=tolorence

Sub class only “types”
-punchout
description: punchout in rectangle, round or slot shape
uses: size_x=width, size_y=depth, data_1=gap, size_z=thick, data_2=fillet, data_3="rectangle","round" or "slot"
-vent
description: horizontal or vertical vent openings
uses: size_x=open_width, size_y=open_length, size_z=thick, data_4=gap, data_1=rows, data_3=columns, data_3=orientation("vertical","horizontal")
-fan
description: fan opening
uses: size_x=size, size_z=thick, date_1=style(1=open,2=fan)
-hd_holes
description: bottom hole pattern for 2.5 or 3.5 drives
uses: data_1=2.5 or 3.5, data_2=thick, data_3=”portrait” or “landscape”
-hd_vertleft_holes
description: bottom hole pattern for 2.5 or 3.5 drives
uses: data_1=2.5 or 3.5, data_2=thick, data_3=”portrait” or “landscape”
-hd_vertright_holes
description: bottom hole pattern for 2.5 or 3.5 drives
uses: data_1=2.5 or 3.5, data_2=thick, data_3=”portrait” or “landscape”-component mask(incomplete)

Model class “types”
-uart_strap
description: console uart holder strap
uses: none
-fan_cover
description: cover for fan hole opening
uses: size_x=40 or 80, size_z=thick
-hd25
description: 2.5 hard drive
uses: data_1=height
-hd35
description: 3.5 hard drive
uses: none
-hc4_oled
description: hc4_oled model
uses: none
-feet
description: case feet
uses: size_x=diameter, size_z=height
-access_cover
description: bottom access cover for sd and emmc
uses: size_z=floorthick, data_3=”portrait” or “landscape”
-button_top
description: button top and plunger
uses: size_x=diameter,size_z=height, data_3=”reccess”
-h2_netcard
description: h2 network card model
uses: none
-hk_lcd35
description: hk 3.5 inch lcd model
uses: none
-hk_boom
description: hk stereo boom bonnet model
uses: data_1=speakers(true or false), data_3=”front” or "rear"
-boom_speaker
description: hk stereo boom bonnet speaker
uses: data_1=pcb(true or false), data_3=”left” or "right"
-hk_speaker
description: hk speaker model
uses: none
-boom_vring
description: hk stereo boom bonnet volume wheel extention
uses: data_1=tolerence
-hk_uart
description: hk console uart model
uses: none

Platter class “types”
-uart_strap
description: console uart holder strap
uses: none
-fan_cover
description: cover for fan hole opening
uses: size_x=40 or 80, size_z=thick
-access_cover
description: bottom access cover for sd and emmc
uses: size_z=floorthick, data_3=”portrait” or “landscape”
-button_top
description: button top and plunger
uses: size_x=diameter,size_z=height, data_3=”reccess”
-boom_vring
description: hk stereo boom bonnet volume wheel extention
uses: data_1=tolerence

[rooted]

Subscribing of course.

[hominoid]

The “tray-vu7” style case is complete and the test print looks good. There was one minor issue I found with the side rails, which act as a stop to prevent the top sliding to far forward. This was caused by an earlier change and should now be correct for both the “tray-vu5” and “tray-vu7”. The Odroid C series of SBC’s will need a little extra width(case_offset_x) to accommodate the vesa 100 mount and like the vu5 style with active cooling, needs 15mm(case_offset_y) more space for fan clearance and 4mm(case_offset_bz) extra bottom height for the side nut holders.

c4-tray_vu7.gif (2.46 MiB) Viewed 3540 times

I was thinking that for cases that are larger than the minimal size and were other electronics are not being installed, the space could be used for covered storage. Maybe have a emmc or sdcard holder as an accessory option that fits inside the case,with the slide and lift top it’s easy access. If the case is large enough it could even be used for other storage. One could even enlarge the y-axis more and have enough room for a battery and charging pcb.

I personally will be using this case with a c4 as a portable media player and streaming device. I believe it makes for a good freestanding all-in-one unit that is small, low power and portable, while being capable of running on a battery bank for use during power outages or wireless mobility if needed.

Updated file SBC_Case_Builder-v1.0.1.zip in op.

[mad_ady]

Your posts make me crave a 3d printer

[hominoid]

Your posts make me crave a 3d printer

Build one, it's a great project for the kids/family and can be done fairly inexpensively. Better yet, make an Odroid Edition and claim serial #3. You already have the first part.

[mad_ady]

Your posts make me crave a 3d printer

Build one, it's a great project for the kids/family and can be done fairly inexpensively. Better yet, make an Odroid Edition and claim serial #3. You already have the first part.

Step one: make room for it in the house... Step two - 3d print larger house. Step three: profit!

Yes, when the time comes, I think I will go the diy route!

[rooted]

It's hard to DIY a printer without a printer.

[brad]

Very nice project, I'm building a CNC machine and wonder how well some of these designs would work cutting from aluminum rather than printing

[hominoid]

It's hard to DIY a printer without a printer.

The RepRap and Voron communities, as well as others, have provided the means to obtain starter sets and I have also seen sets on ebay and others places. Going old school, one could bootstrap a starter machine from scratch but that really isn’t necessary anymore.
Voron even has a dedicated web server – Print It Forward

[hominoid]

Very nice project, I'm building a CNC machine and wonder how well some of these designs would work cutting from aluminum rather than printing

I believe most if not all of them can be cut on a 3-axis CNC, maybe even on a 2 ½ axis CNC. The flat ones are doable and the others might need multiple setups but should also work, imo. I’m somewhat limited in my design because they are being produced for a 3D printer so having a mill should expand what you could do and open up better aesthetic design choices too, imo.

[hominoid]

Some more progress has been made on this project with the core implementation of the case configuration file, accessory framework and a new dedicated library. There are 56 usable cases in the configuration file and all of them are included in the image album in the second post. I’ve also started documenting the schema for case configuration and accessories there.

No new cases or cases using accessories have been added and won’t be until the accessory code is nearer to completion. The focus right now is on figuring out the best way to handle multi-surface placement of accessories and then things will be in a better position to finalize and lock down the schema. Once the schema is finalized then new cases and styles will be created.

case_builder_acc.jpg (109.59 KiB) Viewed 3396 times

There is a case called “test” that I have been using to develop the accessory framework. It shows the current working accessories, for anyone with an interest. I use debug mode to view only the bottom of a c4-tray, the pcb standoffs are disabled for more working room. The naming convention for other standard cases in the configuration file follow the basic form of “sbc”_”design”_”style” e.g. c4_shell or c4_tray_vu5.

[rooted]

The accessories are looking really nice, I'm not usually one to add things for aesthetics but I love that logo.

[hominoid]

It can be any dxf or svg file and is scalable. There are a few dxf files I have used in the past that are included in the release.

[hominoid]

A new release has been posted in the op and the accessory placement is coming along well enough that I started to test directly with a real case example. I have been working with 2.5 and 3.5 drive mounts and still need to finish the oled holder and button access before this is complete, but it does test the things I need and might be useful afterwards. Shown with twin 15mm drives.

hc4_shell_drivebox2.5.gif (1.41 MiB) Viewed 3204 times

New classes have been added for accessories: add1, sub, suball, add2, model, platter. When the fundamental case geometry is to be modified, it needs to happen before subtractions. On the other hand, there are times when additions need to take place after subtractions. There are now two different times to add geometry, when the core case is first created(add1), then subtractions happen(sub,suball) and then the second geometry additions(add2) take place. The class suball is used to effect all “faces” of a case, for example when an opening splits the top and bottom faces.

Another area addressed in this release is model and platter accessory management. Accessories that are not manifold to the case can be included in the model view or included on the print platter on a per case basis as part of the accessory framework. For example, this includes hard drives, fans, access covers, etc in the model view and being able to include the uart strap, access covers or other related components on the print platter.

FYI, to interactively use sbc_case_builder, the sbc_case_builder.cfg file can be edited with any ascii editor and if automatic reload and preview is turned on in OpenSCAD(Design Menu->Automatic Reload and Preview), anytime the configuration file is saved the case model will update. A quick way to create a new case is to copy an existing design that is closest to your use in sbc_case_builder.cfg, rename it and save the configuration file. Select the case name in sbc_case_builder.scad and your set to make modifications. There is also now a highlight(true or false) feature so it’s easier to place subtractive geometry.

sbc_case_builder-v1.1.1 updated in op.

[rooted]

Great stuff, I'm excited that you continue to work on this already awesome project.

Is the case in your turntable animation around 200x150mm? It's not that large is it?

[hominoid]

The size right now is: width = 197.6, depth = 146, top = 27, bottom = 27, so printable on a 200mm platter. I think it can get smaller but I haven’t finished the automatic collision detection for the extended corner standoffs. Once that is done the sbc can be pushed into the corner to gain another 10mm. The height can be reduced more as well. I have it setup to have the soc fan inside the case. If it’s passive that 10mm or more of space can be reclaimed too.

The 3.5 version is the tough one to get under 200mm but the tray case design might work better. The shell version is: width = 227.6, depth = 186, top = 27, bottom = 27. Still developing so I haven’t been doing test prints or worrying to much about the finish details yet.

drivebox3.5-shell.png (30.21 KiB) Viewed 3178 times

[rooted]

Oh it's not too large, it just doesn't seem like the HC4 with a drive beside it would be that size.

[hominoid]

The hd mounts have been completed with the addition of a vertical mount for 2.5 drives. The vertical holder comes in several orientations to ease integration and both the side and bottom screw holes can be used. It can be called in portrait or landscape as well as left and right drive mount. This can be used in opposing mounts so screw holes are accessible as illustrated in the case hc4_shell_drivebox2.5v. This case is 145mm x 145mm x 76mm and uses two 3mm holes for access to the outside mount screws. Shown with twin 15mm 2.5" drives

hc4_shell_drivebox2.5v.gif (1.32 MiB) Viewed 2993 times

The bottom drive mount holes are a separate call and also come in several configurations to match the associated horizontal, vertical, left and right mounts. The bottom holes are registered to the mount so the same coordinates are used for positioning both. There are several actions and geometry that are registered to specific accessories.

A new hc4-oled mount also has it’s opening and the oled model registered to the mount location and the hc4 oled screen opening is created automatically. The extended standoffs, when enabled, have collision detection using a 10mm buffer around each one. All standoffs have the appropriate head opening created automatically as well. These features and others should make using the application easier and faster well still allowing flexibility. The work for access panels has started and they also register related components and create all appropriate openings automatically, but this accessory group is not yet finished.

access-port.jpg (50.03 KiB) Viewed 2993 times

In order to aid design there are two more operational settings now, sbc_off and raise_top, to disable the sbc model or raise the case top in model view(mm or < 0 = off), as well as the subtractive highlight enable.

Code: Select all

highlight = false;                                  // enable highlight for subtractive geometry (true or false)
raise_top = -1;                                     // raises top mm in model view or < 0 = off
sbc_off = true;                                     // sbc off in model view (true or false)

c4_shell_drivebox2.5, hc4_shell_drivebox2.5v and hc4_shell_drivebox3.5 have been updated and are very close to being ready but they need to be tested printed. The oled opening may need to be tweaked to get a perfect fit. Anyone attempting to use them should also verify the the type of standoffs to use. The current settings use inserts in the blind top standoffs with a recessed head for the bottom. They can be changed in their respective standoff data array in sbc_case_build.cfg.

sbc_case_builder-v1.1.2 and documentation updated in the op.

[hominoid]

Test prints have just gotten underway for the previous hc4 cases. The oled holder needed some attention and hopefully they will be in good shape soon. In the meantime work went ahead with the network card model and it’s case integration. Several new router cases in various configurations have been created which included test prints for the h2_shell_router (117x117x65mm) and h2_lowboy_router(117x117x44mm). Other cases include the h2_shell_router-ssd and h2_router_station.

h2-routers.jpg (64.48 KiB) Viewed 2855 times

They feature a cmos battery holder and a large bottom access port to the memory modules and the m2 socket. They also have recessed buttons for power and reset, accessible at the top of the case.

inside.jpg (82.7 KiB) Viewed 2855 times

The network card was added as an accessory instead of a case style as was originally planned. One of the reasons was, as an accessory, it could be combined with any case design or style which would not have been possible if it where itself a style. This allows for more combinations like the h2_router_station.

h2_router_station.png (38.12 KiB) Viewed 2855 times

For those doing their own design there is an accurate model of the HK netcard in the library now. The pcb and hole pattern is a direct extrusion of the hk dxf file on the wiki.

h2_netcard.png (11.66 KiB) Viewed 2855 times

Files and documentation updated to version 1.1.3 in the op.

[mctom]

And all that made in OpenSCAD. Brilliant!
Do you use any plugins worth recommending?

[hominoid]

And all that made in OpenSCAD. Brilliant!
Do you use any plugins worth recommending?

Over the years I have not found many libraries at all. The one's mentioned at the OpenSCAD web site and those available at thingiverse are about it. For that reason everything I use is self developed with the exception of the fillet library that I have used for years. It's under ./lib in the op files if your interested.

The reason for this imo is that it takes longer to do things in OpenSCAD then a traditional mouse and graphic ui, plus I believe it requires more math( and programming) skills which deters some people. Then there are the companies that make web portals available for "free" (we'll keep your data, license it the way we want and maybe share it with you, and if we shutdown...to bad). That's all ok and doesn't matter to me because one of my goals is to support the FOSS community and make my designs available for free..the real meaning of free.

[rooted]

And you do that hominoid, amazing designs.

That filament you're using seems to provide a matte finish, what is it?

[mctom]

And all that made in OpenSCAD. Brilliant!
Do you use any plugins worth recommending?

Over the years I have not found many libraries at all. The one's mentioned at the OpenSCAD web site and those available at thingiverse are about it. For that reason everything I use is self developed with the exception of the fillet library that I have used for years. It's under ./lib in the op files if your interested.

The reason for this imo is that it takes longer to do things in OpenSCAD then a traditional mouse and graphic ui, plus I believe it requires more math( and programming) skills which deters some people. Then there are the companies that make web portals available for "free" (we'll keep your data, license it the way we want and maybe share it with you, and if we shutdown...to bad). That's all ok and doesn't matter to me because one of my goals is to support the FOSS community and make my designs available for free..the real meaning of free.

Very well said and I agree. As you were writing this response, I just programmed a mockup of radiator, to see how badly my new bed will fit to my room.
That's the beauty of drawing in this software, pretty much like programming a microcontroller in Assembly - the hard way. Slowly, but precisely from ground up.

I'll probably dive into your resources sooner or later, but currently I'm busy designing furniture, so that's not the same scale we're operating on.

I was curious about collision detection that I believe you mentioned somewhere earlier, and I assumed you had a plugin for that. Is that a built in functionality?

[hominoid]

The concept of plugin's doesn't really apply with OpenSCAD, it's a language and doesn't offer any plugin tools like traditional CAD packages. So some basic collision detection is written into SBC Case Builder so that the extended standoffs are turned off if the sbc is within 10mm of it. Nothing complicated or fancy needed to accomplish that task, just some nested if's. I think I'm at about 3000 lines of code between the main program and it's library, not counting SBC Model Framework, so you might find some interesting things in there when you have the time. Have fun with your Furniture project.

[hominoid]

And you do that hominoid, amazing designs.

That filament you're using seems to provide a matte finish, what is it?

It is translucent black by WYZ Works. It does have a flat look to it and the hue changes depending on the thickness. It is indeed translucent but not as much as other colors. I had never heard of translucent black before so I had to try some. I thought it might work well with my solid black cases were I want to see leds, use an IR sensor or go for a different look on one of more panels. We'll see how it works out.

EDIT: The WYZ Works translucent black is terrible. I had all kinds of problems with it.

[hominoid]

The hk 3.5” lcd model and cases for the C1+, C2 and C4 are now complete. New cases include c1+_panel_lcd3.5(122mm x 63mm x 30mm), c1+_desktop_lcd3.5, c2_panel_lcd3.5(122mm x 63mm x 30mm), c2_desktop_lcd3.5, c4_panel_lcd3.5(122mm x 63mm x 31mm), c4_desktop_lcd3.5. The test prints look good and C2 and C4 variants were built out. Extra time was spent making sure the display openings are accurate and the buttons work well.

c series-lcd35.jpg (57.5 KiB) Viewed 2710 times

The C2 and C4 desktop version is set up 30 degrees from horizontal for easier access and viewing on a flat surface. This is done by adding two lines for each side to the configuration entry. one adds a rectangle at the viewing angle aligned with the existing left or right pieces by using the location and size of the rectangle. The second is a subtraction using a cylinder to form the opening of the legs.

Code: Select all

"add1","rectangle",-3.5,11.25,-31,"left",[30,0,0],2,58.15,33.5,0,0,"vertical",[.1,.1,.1,.1],    // add rectangle            
"sub","round",-3.75,46,-34,"left",[0,90,0],60,0,3,0,0,"vertical",0,                             // sub round            
"add1","rectangle",116.5,11.25,-31,"right",[30,0,0],2,58.15,33.5,0,0,"vertical",[.1,.1,.1,.1],  // add rectangle            
"sub","round",116.4,46,-34,"right",[0,90,0],60,0,3,0,0,"vertical",0,                            // sub round            

The c1+ is the same but set to 20 degrees to show other view angles are possible. Simply copy the entries for the C2 or C4 to change it to 30 degrees if desired. The sides for the panel and desktop versions can also be quickly interchanged without disturbing the rest of the case. A similar affect can be accomplished using dxf or svg files for infinite variety.

c4_desktop_lcd3.5.gif (592.84 KiB) Viewed 2710 times

Since top standoffs cannot be used with the 3.5” lcd, only the panel or tray designs are possible and the tray design doesn’t make sense for this application. The eventual inclusion of other designs will allow for additional case choices for the 3.5” lcd.

A new button style called cutout has been added to the framework to accommodate these cases and the previous hc4 case's oled holder is in good shape now and ready for use. The ability to move or turn off each case face in model mode individually has been added for easier use of SBC Case Builder. This also allows for the creation of exploded views.

Code: Select all

case_name = "c4_desktop_lcd3.5";                    // case_name to load from sbc_case_builder.cfg
view = "model";                                     // viewing mode "platter", "model", "debug"

highlight = false;                                  // enable highlight for subtarctive geometry (true or false)
sbc_off = false;                                    // sbc off in model view (true or false)
raise_top = 0;                                      // raises top mm in model view or < 0 = off
lower_bottom = 0;                                   // lowers bottom mm in model view or < 0 = off
move_leftside = 0;                                  // move left side mm in model view or < 0 = off
move_rightside = 0;                                 // move right side mm in model view or < 0 = off
move_front = 0;                                     // move front mm in model view or < 0 = off
move_rear = 0;                                      // move rear mm in model view or < 0 = off

The current case count is now 72. Files, flip album and documentation updated to version 1.2.0 in op.

hk_lcd35.png (9.39 KiB) Viewed 2710 times

[rooted]

That case is awesome, the clear plastic one I have is broken so it's good to have this option in your library.

[mad_ady]

Kudos for the cool case! My original one chipped in a couple of places after a couple dismantlings.

[Trilom]

Hello hominoid, this lib looks great!

Very interested in contributing to VU7C if I can. I wanted to first check if you had any work/progress towards this if not I wanted to start looking at it.

Thank you!

[hominoid]

Hello hominoid, this lib looks great!

Very interested in contributing to VU7C if I can. I wanted to first check if you had any work/progress towards this if not I wanted to start looking at it.

Thank you!

Hi @Trilom
Thank you for the kind words and the offer to help. I am working on the Vu7c for this project. There are two designs I’m considering and don’t know if both will be included. Likewise, @tobetter has done a really nice design as well. So, I don’t want to discourage you but it is late in the game for this particular project as I’m nearing completion with only the Vu7c and maybe an additional base design or two as I mentioned in the op. If you do decide to design a Vu7c case with or without this project, please share your work in the forum. I and others would be interested in seeing your work. If you use this project and your design is unique, I’ll certainly be willing to included it with appropriate credits. Thanks again for your interest!

[Trilom]

I have only used OpenSCAD once recently, and AutoCAD over a decade ago so will let you handle it, but it has been a great example I added to component libraries for things I am working with. It lead me to other resources that I have learned from.

Might ask if you have a repository link for it it might be helpful for future contributions/sharing/releasing, at least from my perspective.

I'm excited to see these cases. I have a N2+ and C4 (H2+ w and w/o netcard as well if needed) both with these displays I am very willing to print out a case to test at any point. I am also using the speakers as well so interested in work with the boom bonnet.

I dug into @tobetter's case but have not printed, landed on this based on my interest to learn OpenSCAD.

[hominoid]

When I learned, I read the OpenSCAD documentation and then studied other peoples work, so your approach should work well for you. I don't have any git or other repos for this work, I keep the latest release in this thread. FYI, there is other OpenSCAD work posted in the forum you can query as examples as well.

[EDIT]
I had been working on the boom bonnet model, it will be in the next release.

hk_boom.png (21.86 KiB) Viewed 2643 times

[mctom]

I tried the OpenSCAD hands-on tutorial, but it had a dead slow pace, so I got bored after one or two modules and went on with my own designs.
It's easy assuming you know the basics of any programming language and keep your syntax tidy.

Here's one tip though: OpenSCAD has an option of automatically polling file changes. That means you can use any text editor for your work, not that built-in thing. I use vim. Every time you save a file, changes will appear in OpenSCAD window.

No sweet model on topic I could show off.

[hominoid]

The boom bonnet model is complete along with supporting accessories and cases implementing different deployments of the boom bonnet in a horizontal and vertical application. Cases for the C1+, C2 and C4 have been created: c1+_shell_boombox, c1+_panel_boombox, c1+_tray_boombox, c2_shell_boombox, c2_panel_boombox, c2_deskboom_lcd3.5, c2_tray_boombox, c4_shell_boombox, c4_panel_boombox, c4_deskboom_lcd3.5, c4_tray_boombox.

c4_shell_boombox.gif (1.71 MiB) Viewed 2482 times

Since the boom bonnet is modular, the model was setup likewise to call individual parts to facilitate maximum flexibility for different layouts. The volume wheel reside below the edge of the boom bonnet's PCB which makes it inaccessible in most case applications. A volume ring has been designed to extend the volume wheel above the PCB board. With an additional 6mm of diameter the wheel projects 3mm taller which is enough to expose the knob to the outside of most cases.

hk_boom.jpg (109.13 KiB) Viewed 2482 times

The PCB can be called as a complete unit or without the speakers. Speakers can be called with or without the mounting PCB and a friction fit speaker holder is available that doesn’t require any additional components. Both flat and domed grills make up the finishing touches for boom bonnet applications. The domed grill is designed so it can be printed on a vertical wall without support.

c4_tray_boombox.gif (1.68 MiB) Viewed 2482 times

Other work completed for this release include a hk uart model, tray design top work and implementation of independent pcb_z settings along with other improvements and fixes. In previous releases the pcb_z was calculated and the entry in the schema was not used. Now the PCB height can be set independently which opens up more design choices. Likewise, in the previous release the case corner fillets were changed to be set independently as well. They were originally set to the sbc fillet size. A regression was found and fixed for the top for the tray design. I really like the tray case but I’m not happy with how the top works. I have added some tabs to try and better hold it but I’m no more satisfied with how it’s working so expect some more changes in the future.

c4_tray_boombox.jpg (58.17 KiB) Viewed 2482 times

There is now a OpenSCAD file included called tolerance_check.scad which can be used to check the tolerance of the three current friction fit parts: batt_holder(tolerance), boom_speaker_holder(tolerance) and boom_vring(tolerance). The current settings were derived from test prints but depending on your printer and the shrinkage of the material your using, they could need adjustment. Any tolerance adjustment can be added to data_1 for each effected entry in the sbc_case_builder.cfg.

c4_deskboom_lcd3.5.gif (615.16 KiB) Viewed 2482 times

Test prints were done for the c4_shell_boombox, c4_panel_boombox and c4_tray_boombox.
The current case count is now 83. Files, flip album and documentation updated to version 1.2.1 in op.

[mad_ady]

Awesome design for the boom bonnet! I'm looking at mine, covered with dust with wires sticking out and feel envious!

[hominoid]

...covered with dust with wires sticking out...

Ah, the classic hacker look. Some of mine still look that way.

[mctom]

You really make me consider buing a 3D printer..

[hominoid]

You really make me consider buing a 3D printer..

As I have evangelized before, anyone who builds, repairs or re-purposes things will significantly benefit from having a 3D printer. I have saved a lot of money by being able to repair or re-purpose things that wouldn’t have been possible otherwise. It has definitely paid for itself. Even if your doing CNC work, being able to do check prints before committing to the much more expensive and time intensive machining process, not to speak of the increased material costs and dedicated space needed, just makes sense imo.

For many if not most visiting this site, I would recommend that they seriously consider building one. It’s not that hard and there might be the opportunity to learn new skills along the way. The cheap printers are just that and anyone who is serious or becomes serious starts to demand more then they can sometimes deliver. Imo, it’s much easier to start with a basic build and improve on it over time then to start with a poor design, substandard construction or materials and have limited ways to improve it. If an assembled printer is still desired then take a look at Prusa’s Mini+.
Thinking of building one?
reprap.org
Voron Designs

On the down side, one area of concern I have always had is the environmental cost of using plastic. It’s half-life is quite long as we know. I have collected and saved all the scrap plastic I have used over the years, surprisingly it is only a few medium size box divided by color and material type. Almost all of it is ABS and black, so my plan is to build a grinder-extruder in the future. Even if I never do, by using care I haven’t created a large amount of scrap and what I have created is accounted for and not floating in the ocean or buried in a land fill. Maybe I’ll use it to print a casket and take it with me when it’s time.

[mctom]

I wish we could grab some beers and hold longer discussion about that and everything else. I like where your head's at.
I don't think I can afford a 3D printer, at least space-wise - I'm currently trying to create more storage just to have more room for ourselves.
So before I get a second hand Prusa, which can be obtained for some $200 in a good shape, I'll outsource the production for now and see if I'm any good at designing 3D prints in the first place.
JLC PCB has a 3D printing service now, and I'm tempted to try it once and see if it's any good.

But thanks anyway for sharing your thoughts, you made a lot of good points there.

Fun fact: Prusa Mini+ costs more than my car.

[Trilom]

You really make me consider buing a 3D printer..

As I have evangelized before, anyone who builds, repairs or re-purposes things will significantly benefit from having a 3D printer. I have saved a lot of money by being able to repair or re-purpose things that wouldn’t have been possible otherwise. It has definitely paid for itself. Even if your doing CNC work, being able to do check prints before committing to the much more expensive and time intensive machining process, not to speak of the increased material costs and dedicated space needed, just makes sense imo.

For many if not most visiting this site, I would recommend that they seriously consider building one. It’s not that hard and there might be the opportunity to learn new skills along the way. The cheap printers are just that and anyone who is serious or becomes serious starts to demand more then they can sometimes deliver. Imo, it’s much easier to start with a basic build and improve on it over time then to start with a poor design, substandard construction or materials and have limited ways to improve it. If an assembled printer is still desired then take a look at Prusa’s Mini+.
Thinking of building one?
reprap.org
Voron Designs

On the down side, one area of concern I have always had is the environmental cost of using plastic. It’s half-life is quite long as we know. I have collected and saved all the scrap plastic I have used over the years, surprisingly it is only a few medium size box divided by color and material type. Almost all of it is ABS and black, so my plan is to build a grinder-extruder in the future. Even if I never do, by using care I haven’t created a large amount of scrap and what I have created is accounted for and not floating in the ocean or buried in a land fill. Maybe I’ll use it to print a casket and take it with me when it’s time.

I couldn't agree more, I have resisted for years because I knew it would be consuming because I would love it and I was right. If you buy these computers then in some way you need one. What sold me was needing a fan bracket for my h2+'s and being tired of compromising on something that costs more than my complete happiness. It's like no longer do you have to buy size 7 or 8 shoe, you buy 7.314.

Your point with scrap is something I have been incredibly mindful of as well, my partner has been using my scrap plastic for art and I use it for spot "welding" when I need to.

Ultimately as I was researching one I realized a lot of "building your own" comes down to needing a printer to print parts so committing to an egg to make a Rhode Island red should be considered. I am elated with my Ender, but excited to use it to birth something better.

Thank you for the update on the case builder project!!

[hominoid]

This release includes models for the new HK Vu7c and Vu8m displays in the sbc_case_builder_library. Thanks to @mctom for the modeling work on the Vu8m and allowing it's inclusion into the library.

Vu7c-Vu8m.gif (1.62 MiB) Viewed 2127 times

It also contains many fixes and a few improvements that include a better Boom Bonnet speaker model that is much more detailed. An improved Boom Bonnet friction speaker holder that has incorporated a stop to create a setback distance to assure proper speaker operation and a new clamp style speaker holder.

acc.png (23.81 KiB) Viewed 2127 times

There are no new cases in this release and there will be a short temporary pause on this project in order to complete the Odorid-M1 model and associated peripherals. Files updated to version 1.2.2 in op.

[hominoid]

Might ask if you have a repository link for it it might be helpful for future contributions/sharing/releasing, at least from my perspective.

Due to multiple requests I have decide to move into the late 20th century and posted this work and others in a public git for anyone interested.
https://github.com/hominoids/SBC_Case_Builder
I'll still be posting releases here as they become available.

[mad_ady]

yay!

[hominoid]

I'm working on selling the horse and getting a Model-T...baby steps.

[fkpwolf]

that is what I want for my h2 router!
I like the h2_lowboy_router model but looks it has some small component which I am not sure can be handled by a common 3D printer. Is it easily be broken?

[hominoid]

that is what I want for my h2 router!
I like the h2_lowboy_router model but looks it has some small component which I am not sure can be handled by a common 3D printer. Is it easily be broken?

I didn't have any problem on a homemade Prusa i3 and I think most, if not all printers, would be fine. The ones for other models and cases like the C4 or C2 are even thinner and those can be a little fragile. But, I handle them with care and if I do brake them a little glue works to repair them. Just to make a point, the test prints in the photos below were printed at 200mm/s and I would imagine your printing slower, so less of a problem. I did use a brim for the print and it's important that your printer is reasonably tuned. I see some designs that don't even bother to fill in between components and that is another alternative. IMO, I think you'll be fine.

h2-lowboy-router-1.jpg (155.87 KiB) Viewed 1655 times

h2-lowboy-router-2.jpg (177.33 KiB) Viewed 1655 times

[hominoid]

A new release is available and there has been good progress made for version 1.2.3. There is a new top design for the tray case with the original design now a new style called “sides”. Several Odroid-M1 cases have been added as well(m1_panel,m1_tray,m1_tray_drive,m1_tray_sides,m1_tray_vu5,m1_tray_vu7).
The m1_tray case is 117mm x 131mm x 35mm, has 2.5mm thick walls, a recessed external button and uses the new tray top design.

m1_tray.gif (1.87 MiB) Viewed 233 times

The case design m1_tray_drive can incorporate a 2.5” SSD mounted upside down on the inside of the top with 8mm added height. The dominate factor for the correct case height is the SATA connection at the M1. An angled end is best used for this design, otherwise adjust the height of the case according to the height of the SATA cable connectors being used. It is a snug fit and every mm counts for this configuration. The drive could be mounted in other orientations by adding to the case size. The goal with m1_tray_drive was to see if a 2.5” drive could fit in the minimum M1 case size. From a modeling view it appears it does and even though I didn't do a test print, I wanted to give an approximation using the photos below for those who are interested in this configuration. They are of the standard m1_tray case, which doesn't have the additional 8mm height, but shows the proximity of connectors and surrounding components. The model rendering is of the actual m1_tray_drive case with 8mm additional height.

m1_tray_drive.gif (208.22 KiB) Viewed 233 times

The internal mask code for creating openings in cases has been standardized across all sbc components and is now fully enabled. Each component entry for a SBC in sbc_model_framework is parsed and a SBC specific mask set is automatically generated. The mask starts 2mm behind the face of each component, in case of a pcb overhang, and projects 6mm beyond the face of the component. This allows for a standardized working range of 6mm for the pcb gap and wall thickness of any case. Another noteworthy change is to the punchout() routine, it has been updated to make printer friendly knockouts for vertical walls that don’t require print support.

mask-set_knockout.jpg (53.64 KiB) Viewed 233 times

The Show2 model has been in the library for a while but hasn’t been verified and I don’t have one. It was created on request from a photo with measurements. A test case show2_shell has been added with the hope that someone will give it a try and provide some input as to the accuracy of the show2 model itself. Once the model has been verified or corrected then other cases can be created and maybe even with integrated buttons.

show2_shell.gif (2.09 MiB) Viewed 233 times

With this release things are starting to look good with the core functionality and accessories of this application. This should allow time to focus on new base case designs and the expansion of existing case offerings moving forward. There has already been a couple of other sbc contributed to the SBC Model Framework, for which cases have been created, bring the total case count to 110.

Files updated for version 1.2.3 in op.

[rooted]

Sorry about not verifying the Show 2 case, I certainly meant to but life got in the way and I forgot.

All my filament is packed away but when I find it I will try to remember and verify, the work is appreciated regardless.

[hominoid]

Sorry about not verifying the Show 2 case, I certainly meant to but life got in the way and I forgot.

All my filament is packed away but when I find it I will try to remember and verify, the work is appreciated regardless.

No need to apologize, there wasn't really a way to verify models when it was created and there was never a discussion about providing feedback. I brought it up only because I was surprised in the recent past when I noticed it had been download over 80 times(88 now). With such interest I thought it might make sense to add a case for it in sbc case builder but wanted to warn people that it's accuracy was unknown and solicit some feedback.