-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] 10-Inch Mini Rack #4
Comments
This has been requested by a couple of people already. I'll look into when I get the time. (I don't think it'll be a lot of work, but I'm probably going to eat those words later.) Thank you for your interest! |
Hi there, I just found your project and it looks amazing! I’m interested in printing a 10” version of this too and was wondering if either of you had got any further with the required changes? Thanks! |
I'm new to networking racks and openSCAD, but am I correct that items 2-4 in the OP are only needed if you're trying to make the printed rack compatible with standard 10" mini racks? In other words, if I was going to stick to the rackstack ecosystem and print my own mounts for switches, routers, etc., would I only need the first item?
Thanks! |
That's right, you would only need to increase the width to 10" from the outing of each rail or ~9.312" from the inside. Then you could use Rackstack's uniform hole spacing and M3 hardware. |
That's the only thing that i have to do, how to get the 10 inch mounting in the front, the squares? |
any progress on this? printed out the whole thing and figured out later it is not really 10' :D |
Hey Jazwa!
I saw your post on r/homelab and this seems like a super cool project!
I'd be down to print rackstack in a 10-inch mini rack form factor. I tried to do this myself but couldn't figure out how to do so in OpenSCAD :(
The changes that would have to be made are:
rackFrame.scad
)mainRail.scad
width and depth to accommodate larger M6 hardwareThanks for your project, and if you're able to do this I'd 100% be down to test a prototype!
The text was updated successfully, but these errors were encountered: