Runout unklicky

[waytotheweb]

• [x ] The mod, firmware configuration or slicer profile is in the correct category folder. Printable mods go to printer_mods/, firmware configurations go to firmware_configurations/, slicer profiles go to slicer_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] Folder and file naming:
  • Folders and filenames shouldn't contain spaces. Only letters a-zA-Z, numbers 0-9, underscores _, hyphens - and periods .
  • Primary color: part_xyz.stl
  • Accent color: [a]_part_xyz.stl
  • Opaque color (Blocks light): [o]_part_xyz.stl
  • Clear/transparent color (Allows light): [c]_part_xyz.stl
  • Quantity, if more than one is needed: part_xyz_x4.stl
• [x ] For each mod, add a small README.md file 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.md of 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 .STEP or .SCAD file
• [x ] Submitted firmware configs or slicer profiles contain no sensitive data (e.g. API keys).

Which mods/configurations/profiles are added by this PR?

chirpy/RunoutUnklicky

How was it tested?

Printed, installed and running on my Trident, V0.1 and other users on Discord

Any background context you want to provide?

This was made to utilise the Unklicky principle and to offer different mounting and PTFE tube retention options

Screenshots (if appropriate)

Provided in the repo

Further notes

[maz0r]

I'm wondering if this better suits a PR into klicky/klickyprobe or majarspeed/unklicky as a usermod/ alternate variant rather than a dedicated Voron mod?

I say this as those mods are rather agnostic with variants for multiple other printers already. A filament runout sensor is also pretty universal,

Not opposed just throwing my 2¢ out there to see what peoples thoughts are :), obviously mod discovery / visibility is potentially a factor to consider.

[waytotheweb]

I didn't see this as a derivative of unklicky, more a development of the filament runout sensor for those that find it hard to source reliable microswitches. It'd be a shame for me for it to disappear in the unklicky mod where it would likely get lost from people finding it, whereas it would be more useful to find here. I do understand it's getting quite cluttered at the top level, but it seems the nature of the beast hosting the mods on github.