Control 3D Printer with Klipper & Tasmota_plug & Fluidd

[GadgetAngel]

trafficstars

• [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] 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.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?

printer_mods

How was it tested?

Yes, on my 3D printer. These are a set if instructions that I pulled together from 20 different sources. This will allow others to do the same without having to take the time to read 20 different pieces of information to do the same job.

Any background context you want to provide?

Screenshots (if appropriate)

Further notes

[newphreak]

I would really like to see off_when_shutdown: True mentioned as a double safety here. With that enabled moonraker is able to kill the power if the mosfet blows closed on the hotend for example. Seem like a missed opportunity for free added "safety". "" because it relies on many things going right. But if it stops one voron from melting down I'm happy.

[cbc02009]

This is awesome, but I really feel like this belongs in a community docs guide and not in usermods, since there's not STLs or PCBs with it. let me discuss with the rest of the crew.

[GadgetAngel]

This is awesome, but I really feel like this belongs in a community docs guide and not in usermods, since there's not STLs or PCBs with it. let me discuss with the rest of the crew.

Right now I have over 56 PR documents waiting to get approved for community docs (https://github.com/VoronDesign/Voron-Documentation/pulls?q=is%3Aopen+author%3AGadgetAngel+). Some of the 56 should be added immediately but because they have "GadgetAngel" on the PR none get approved and they have been sitting there for over two months.

I want this added to usermods because it is information that people can use NOW. I can added it the community docs after the other previous 56 PR are added.

@newphreak The reason I did not add off_when_shutdown: True is because I want the Raspberry Pi to stay up and NOT shutdown when the MCU connections is lost. If I set the off_when_shutdown: True option then when the motherboard shuts down and the connection is lost to the MCU and the Raspberry Pi will then be placed in a shutdown state.

I have the Raspberry Pi acting as the MQTT broker and placing the Raspberry Pi in shutdown will cause the MQTT communication to other devices to stop working.

Remember I want the Raspberry Pi (Klipper) to stay up and running at all times, and only shutdown the PSU for the 3D printer's motherboard and the 3D printer's motherboard when the print ends. If the 3D printer's motherboard and 3D printer's PSU is shutdown then the 3D printer's heaters will all be shutdown and their is no risk of fire.

The Klipper's Raspberry Pi being allowed to stay up and running should cause no risk to the user.

[FHeilmann]

Hi,

I want to thank you for your submission and want to personally apologize that your submission has not gotten the review it deserves. We are in the process to restructure the repo to streamline reviews and hopefully solve this issue in the future.

Unfortunately, this means that we will require you to resubmit the mod under the new system.

Please check here for details and instructions on how to proceed. If you have any questions, please reach out in the #voronuser_mods channel on the VoronDesign discord. If you have since moved on from this mod and don't want to resubmit, no further action is necessary from your side.

Bests,

Florian a.k.a. Haribro