-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Make Buttons for 530 kit without labels #498
Comments
If you ever want to make an inkscape file with the labeling I'd be down to include this in the project files! |
Actually, I meant the STL button, not a label file. Literally, your tall and short buttons have text on them for the 530 kit, I'm saying leave them as plain buttons. RE: See your Button_tall.stl etc. |
For sure! I've just exported the STLs (I just performed a cut in Bambu Slicer), if you have an SVG file to send to a cutter I think that could be helpful for people? If that's something you want to make it could be super dope! but if not I can do it sometime :) |
Only if you'd already do it or if you want to though! |
I see them! That was quick. Buttons_Flipper The Flopper.stl Above need that magic too, when free time exist. I note you went the slicer route, but that is not always gonna work (all the time), especially if the item like "flipper the flopper" has text below the highest point. I really wish I had the SVG file, but i used https://cessna172sim.allanglen.com/docs/avionics/garmin-gns-530/ when I built mine 2 years back. His SVG worked without issue. Link to SVG files on Git: parts/avionics/garmin-gns-530 |
For kit buyers, 80% (or more) will benefit from labels (OBS, VNAV, FPL etc) embossed on the button itself, as you have done. However, for those of us with Lasers (CNC) it would be cool to have no raised labels on buttons. Please consider this a VERY low priority item (but you can apply the logic to all buttons in all kits).
I print in white, spray paint black, then let the laser do the magic of removing the .3mm of black paint to reveal detailed text.
The text was updated successfully, but these errors were encountered: