-
Notifications
You must be signed in to change notification settings - Fork 167
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
Klipper config for MKS PWC V3.0? #18
Comments
Same issue here... |
Did find a solution!
This way I get a power printer button in moonsail interface. Pretty easy :)
I found also an idle timeout macro. Still working on it as does not behave as expected :( (not really spent much time on it)
|
Nice! However, i'm using octoprint but, I did find a solution that worked for me on this reddit post. It's quite simple since the octoprint server handles all of the idle timeout stuff. |
Yep, |
Would you explain a little bit better, please? Thank you very much for your help Update. Nevermind, I figured it out. It was PW-DET between the board and the PWC, then the PW-OFF between the PWC and the Raspberry Pi. If anyone needs this info |
Good, could you send us a document for wiring, I don't want to burn anything? |
It worked correctly for me on how many GPIO15, GPIO14 did not communicate. |
MKS-PWC can be used with any board, it would be good to turn off PW-OFF after pressing it, so it turned off the system on the Raspberry Pi and then turned off the entire printer |
Thanks a lot for completing the circle, @conting Now, it's time Makerbase take note of how to give complete functionality to the PWC AGAIN, and give these instructions in their git. Let's see if they read here. |
So, thanks to @gmaranda , we have got a running PWC configuration in klipper. To add more usability and manage it from mainsail and moonraker, I'll change the code: In printer.cfg:
In moonraker.conf:
PD: This is a work-in-progress, as I don't have PWC connected now (I finished using a Tasmota plug to manage the printer power). Please, test it and let comments here. |
Hi! Altough this works it is not fully there yet. When I start my machine I have to hold the button for about 30sec or until you hear the click inside the PWC. After that the machine stays on and if you don't wait long enough the machine shuts down. When the machine is running you get the shutdown button in mainsail (for me) and if you push it this will shut down the machine. Not too bad for now but at least the machine works. I tried to add the PB2, !PA2 as suggested by Marcos (Marc05Arg) above but it would not load properly. At least this is progress but the work continues. |
You're right, @gmaranda ... I would love if @mks-viva or @makerbase-mks follow our work and give lasts steps. |
Hi @ColdBeer72 @gmaranda, as a workaround for this Problem I added this to the printer.cfg file:
So now it looks like this:
After turning on the printer I hear a "click click" and the printer stays on. I know this is just a workaround, buts its better than nothing. If I find a better solution I will post it here. |
Thank you for the idea. Unfortunately for me it does not work. I have put your codes as is and the machine boots etc. but I still have to hold the button and count to about 30 for the machine to stay on. I must be cursed! I left it in the config file since it does not seem to do anything wrong. I am glad it is working for you though. thanks again |
First off, thank you to everyone that's been collectively worked on this project. Below is a quick reference of how I've gotten the MKS PWC V 3.0 to work on a setup using the stock MCU and no Pi. [Specific thanks to @ColdBeer72 @conting @marc05Arg] Printer: FLSUN Q5 MKS PWC Wiring: Klipper Firmware Build: Addition to printer.cfg
Addition to moonraker.cfg
I chose to keep [gcode_macro PW_OFF_PRINTER] disabled is it's a duplicate of the button configured in the moonraker.cfg and only one or the other is really needed. However, it's still useful for those who would like to append the macro to the end of their GCODE files to shutdown after the completion of a print though. I also chose to keep [gcode_button BUTTON_AUTOSHUTDOWN] disabled as I've found a purpose for not allowing it to act as a reset switch. The current config [with no use of a raspberry Pi and only having the onboard MCU setting the PWC] causes the printer to shutdown and turn off anytime a firmware reset command is given. However, if you hold the reset button down while performing the firmware reset, the printer stays on throughout the cycle. So enabling/disabling this portion has it's own benefits. The below screenshot shows the two sections of the DashBoard described above. |
Does anyone have a Klipper config that I could use for the PWC V3.0?
The text was updated successfully, but these errors were encountered: