VoronUsers
VoronUsers copied to clipboard
Slitte mods
- [x] The mod, firmware configuration or slicer profile is in the correct category
folder. Printable mods go to
printer_mods/, firmware configurations go tofirmware_configurations/, slicer profiles go toslicer_profiles/. Create a subfolder with your name, and place the mods in a subfolder with a descriptive name within that folder, e.g.:/printer_mods/FHeilmann/flux_capacitor - [x] Folders names MUST NOT contain spaces. If possible, make sure file names also do not contain any spaces.
- [x] For each mod, add a small
README.mdfile to its folder with a short description of what the mod accomplishes. This readme can be used to add pictures, give assembly instructions or specify a bill of materials if the mod requires additional hardware. - [x] The PR modifies the top-level
README.mdof the category folder adding the contribution to the table. Read the top part of the file for instructions on how to do this. Please preserve the alphabetical ordering while adding new rows. Make sure to fill out the compatibility matrix to indicate which versions of the Voron printer the submission is compatible with. - [x] The mod/configuration/profile has been tested by the person submitting the mod and/or other Voron users. Make sure to add information about how the mod was tested below.
- [x] The mod is not merely a slight modification of an official Voron part, configuration or profile (i.e. an official Voron part with a few mm added or removed or a slicer profile which only modifies a few values). (When in doubt, contact one of the admins in the Voron discord before submitting the PR)
- [x] Submitted STLs are printable without support. (If the mod does not meet this criterion join the Voron discord and ask the other users for advice on how to modify the mod such that it does not require supports)
- [x] Submitted STL files are not corrupt. (This can be tested by opening the STL in PrusaSlicer and checking if mesh errors are reported.)
- [x] Submitted STL files are oriented and scaled properly for printing.
- [x] Submission includes a CAD file in the form of a
.STEPor.SCADfile - [x] Submitted firmware configs or slicer profiles contain no sensitive data (e.g. API keys).
Which mods/configurations/profiles are added by this PR?
PCB_Probe ssd_bracket
How was it tested?
tested both on my v2.4 (see images folder)
Any background context you want to provide?
Screenshots (if appropriate)
Further notes
Sliced and reviewed ssd_bracket.stl, no printability changes required.
deleted the licence files
This contains a bunch of unnecessary readme.md files. They should be removed unless there's some more information to be added to them.
printer_mods/slitte/PCB_Probe/Gerber/readme.md
printer_mods/slitte/PCB_Probe/KiCad/readme.md
printer_mods/slitte/PCB_Probe/images/readme.md
printer_mods/slitte/ssd_bracket/STEP/readme.md
printer_mods/slitte/ssd_bracket/STL/readme.md
printer_mods/slitte/ssd_bracket/images/readme.md
This contains a bunch of unnecessary readme.md files. They should be removed unless there's some more information to be added to them.
printer_mods/slitte/PCB_Probe/Gerber/readme.md printer_mods/slitte/PCB_Probe/KiCad/readme.md printer_mods/slitte/PCB_Probe/images/readme.md printer_mods/slitte/ssd_bracket/STEP/readme.md printer_mods/slitte/ssd_bracket/STL/readme.md printer_mods/slitte/ssd_bracket/images/readme.md
Deleted unnecassary readme.md files
@slitte looks like the CI failed. there's an issue with one of the STLs:
Validating STL printer_mods/slitte/ssd_bracket/STL/ssd_bracket.STL
!! Detected "Edges fixed" value of 166
Error occurred while validating STLs.
Error: Process completed with exit code 255.
@slitte looks like the CI failed. there's an issue with one of the STLs:
Validating STL printer_mods/slitte/ssd_bracket/STL/ssd_bracket.STL !! Detected "Edges fixed" value of 166 Error occurred while validating STLs. Error: Process completed with exit code 255.
new export of the stl file, testet with superslicer, no errors found. reuploaded new stl file. hope it's fine now
do i have something else to do with this pr? @cbc02009