PID Profiles are something I was specifically looking for on my Trident build. XOL and Dual Auxiliary fans means that speed runs will almost certainly require entirely different Tunes than just everyday printing. Will be fun to play with tuning each use case and filament. Love that options exist!
I've been running DK for a number of months, and it was a 5 minute conversion (switch git repo over and restart). The DK devs are amazing, are actually willing to implement new features that make sense. I lurk in their discord and try to help test out and provide feedback on new features/git issues under review that seem cool (i e. adding customizable Z-Hop to firmware retraction!!) Highly recommend everyone look at making the switch!!
One of the first things I do, is determin the pins that need to be forced high or low to stop stepper motors, enable fans, and disable heaters; to add to GPIO on Startup in Firmware make screen. This forces those pins to be set, A) between powerup and Klipper taking control, and B) emergency shutdown can leave the hotend HOT and the Heatbreak Fan OFF, So I add the fan pin so it will be forced on during both. One of the best Safety Features Klipper has!!
Great video! Honestly, I'm really excited for the stuff their folks have been working on like porting Model Predictive Control to DK for incredibly fast hotends (and odd ones with large thermal masses) with Velocity PID. Keep it up :)
what a great video, so many of these things this plugin fixes are gripes i have with klipper. ive never even heard of this before.. have a good weekend !
"danger klipper - its klipper but better" i find most of the stuff is *less* dangerous since its enabled by default and just lets me do what people want. MPC is *way* less dangerous for successful prints, etc.
Danger Klipper will (at some point) support full coreXYUV kinematics (ie. 2 coreXY gantries stacked on top of each other). This could lead into some cool IDEX printers and WEDM machines (for which this kinematics is being developed)
Thanks for the video! I’m considering building a kit/open source printer for the first time, but the software implementations seem the most daunting to me. I bought my first printer earlier this year and I really want to make something a little more custom, play around with settings, and maybe even design a reliable printer that’s inexpensive. :)
about time you did a DK video lol (I mean that as a joke), I run bleeding-edge-v2, The different accel's are called coreXY limited or cartesian limited BTW, another person also mentioned MPC that has been ported over from Marlin which works very well in DK IMHO, also with their bleeding-edge-v2 you can get "High precision stepping and new stepcompress protocol" and also "Smooth Input Shapers" it adds smooth versions of the protocols like smooth_mzv & smooth_ei and more, which I and another are working on a macro to change input shaping during a print, still has a few bugs but works.
There’s a couple ways to do this already. There’s an option to turn on that enables it, but I forget how to move it afterwards. The other way is to send a gcode that tells an axis it is now at whatever position you give it, so it thinks it’s homed. Then it will move as normal.
But I don't want PID profiles, I want klipper to finally support the M301 gcode command. Imagine finally being able to initially tune, and then dynamically set PID depending on print speed and layer time, no more glossy/matte discoloration on prints.
any chance you'll make a video on the "TMC autotune" plugin? and maybe compare it to the "chopper-resonance-tuner" one? for me the chopper-resonance-tuner gave me much better results but it's definitely not a fast process, plus I'm using cheap unsupported motors so I might've gotten some values for "TMC autotune" wrong
Been wanting to try danger klipper for a while, but getting my SB2040 CAN board working with normal klipper was hard enough, so I’m worried working with the danger klipper repo is gonna complicate things beyond my ability to flail my way to success…
should basically just work, there is very little divergence in the firmware so provided your Klipper installe/ FW is recent you may not even need to change firmware.
I may give this a try on my V0. Too many times I've had the USB Display disconnect because I bumped its cable and such and the print failed. Currently I don't have the screen enabled due to it loosing connection so it would be nice not to have to worry about the printer freaking out if the screen disconnects,
It would be nice if they could add option to set different values for z tilt points and leveling points. I want my z til to measure height once on each point, and i want double points on each bed mesh, but I cant seem to do that with Klipper.
Ah.... A klipper fork where the dev doesn't refuse all requests for change/features just because HE things it's not important. (Such a proper implementation of the S and R parameters in the set set and wait for temperature commands.
A comment you made that is misleading... Danger Klipper IS NOT dangerous just because "you can do something to damage your printer." You can do that with regular Klipper as well. Danger Klipper is dangerous because you can Completely Disable SERIOUS SAFETY CHECKS that can lead to FIRES! This SHOULD NOT be downplayed in the slightest and you SHOULD NOT play around with DK on a whim, you NEED TO KNOW what you are doing! The reason DK has a lot of these "features" you won't find in mainline Klipper is because it is used as a test bed and it is easier to get features implemented in it than it is in mainline Klipper. If you want you printer to be reliable DO NOT run a test firmware on it! Now if you're wanting to tinker and play around and you know exactly how all options in Klipper work then have fun! But if there are features in DK you really want, such as retract on sensorless homing, then insist they get merged to Mainline.
Some do, however Kevin doesn't like just adding new features or making huge changes. Klipper runs on alot of big business gear and changing things can cause issues for them etc so things get implemented or changed ALOT slower on klipper compared to dangerklipper which is much more for hobbiests.
i mean, danger klipper makes it sound like all hell will break lose and everything that can go wrong, will go wrong but if they had called it klipper without training wheels? it might of been categorized has the “for professionals only” 😂
DangerKlipper: Klipper with devs that aren't seemingly actively hostile to opensource development (COUGH Dev response to klipper GH issue #6711 COUGH) and are happy to add a feature even if the main dev wont personally be using it...
Make sure to read through the discourse thread on the GH issue you're referencing and you'll see that it is no longer as black or white as it looked in the beginning.
@@SvenLankes I specifically take issue with how the devs reacted to an an *extraordinarily* well-made issue... being made on the Thing Specifically Made to Track Issues instead of their discussion forum. Not the bug itself.
@@SvenLankes It's pretty black and white (the bug, not the cause or the fix), i have it all reproduced on a single stepper + endstop setup. It's very broken.
The bug report I wrote up multiple times after going through dozens of rebuilds against different patches to narrow down to the exact patch and finding the exact lines of change in that patch that caused the failure were completely dismissed and blamed on the hardware, when the hardware worked fine before that patch. The original author of that bit of code put a chip reset in before the first access for a reason (but that person never responded to the thread) and someone else removed that code, causing the bug. The workaround given was to change from hardware to software SPI (which means resoldering the assembly too) and the case was closed. The reason for the code removal was never explained, and since it literally only runs once (on first access), it's not like it was a performance optimization or anything. That one left me baffled.
Wait why doesn't it use the accelerometer in real time all the time?? This is really useful to look for issues? Every smart phone does this for no reason... and tracks you and you don't even want it to. Yet here it has a reason to collect real time movement data and nobody takes advantage of it? Not even this "advanced" software?
@@ModBotArmy I just spent all day getting my printer config to work restarted the printer and the printer config file was just null over and over I guess I'm really not ready.
It's a nice tutorial, but imho a bit useless. If you can't find it and install it you don't actually need it, and probably should not even consider to mess with it 😂
Do you like to solve unnecessary problems every now and then (worst case scenario) and "rubber duck programming"? then Klipper. Do you like to have something key in hand which you send a print and even forget it was goin because your high ass didn't notice it was 3 and a half days with 4kg of filament? MARLIN UH-AH AH!
DK: because if I want to start my printer on fire, I should be able to set it on fire
Thermistor: Disabled
Hotend fan: disabled
Thermal runaway: Disabled
can do this just with my own negligence anyway. bought a smoke alarm.
PID Profiles are something I was specifically looking for on my Trident build. XOL and Dual Auxiliary fans means that speed runs will almost certainly require entirely different Tunes than just everyday printing. Will be fun to play with tuning each use case and filament. Love that options exist!
I've been running DK for a number of months, and it was a 5 minute conversion (switch git repo over and restart).
The DK devs are amazing, are actually willing to implement new features that make sense. I lurk in their discord and try to help test out and provide feedback on new features/git issues under review that seem cool (i e. adding customizable Z-Hop to firmware retraction!!)
Highly recommend everyone look at making the switch!!
One of the first things I do, is determin the pins that need to be forced high or low to stop stepper motors, enable fans, and disable heaters; to add to GPIO on Startup in Firmware make screen. This forces those pins to be set, A) between powerup and Klipper taking control, and B) emergency shutdown can leave the hotend HOT and the Heatbreak Fan OFF, So I add the fan pin so it will be forced on during both. One of the best Safety Features Klipper has!!
Great video! Honestly, I'm really excited for the stuff their folks have been working on like porting Model Predictive Control to DK for incredibly fast hotends (and odd ones with large thermal masses) with Velocity PID.
Keep it up :)
Oh my God thank you! I've been pushing klipper to its limits and creating lots of work around for features that I could have done easily with this.
Always like you stuff. It’s a klippier klipper for klippier people
what a great video, so many of these things this plugin fixes are gripes i have with klipper. ive never even heard of this before.. have a good weekend !
Awesome! If you give it a shot let me know how it goes 😊
"danger klipper - its klipper but better" i find most of the stuff is *less* dangerous since its enabled by default and just lets me do what people want. MPC is *way* less dangerous for successful prints, etc.
I have heard about this but didn't see a proper video, thanks!
Danger Klipper will (at some point) support full coreXYUV kinematics (ie. 2 coreXY gantries stacked on top of each other). This could lead into some cool IDEX printers and WEDM machines (for which this kinematics is being developed)
This is why i like your channel you talk about the things that matter.
homing current sounds like something worthy of main line. Sensorless homing is not really thar be dragons anymore and is used in a few kits.
Thanks for the video! I’m considering building a kit/open source printer for the first time, but the software implementations seem the most daunting to me. I bought my first printer earlier this year and I really want to make something a little more custom, play around with settings, and maybe even design a reliable printer that’s inexpensive. :)
me who has never installed klipper in any way: huh neat
Nice, thanks for the summary. looks very interesting
Don't understand why easy things like the PID for dirfferent materials is not a standard klipper thing.
about time you did a DK video lol (I mean that as a joke), I run bleeding-edge-v2, The different accel's are called coreXY limited or cartesian limited BTW, another person also mentioned MPC that has been ported over from Marlin which works very well in DK IMHO, also with their bleeding-edge-v2 you can get "High precision stepping and new stepcompress protocol" and also "Smooth Input Shapers" it adds smooth versions of the protocols like smooth_mzv & smooth_ei and more, which I and another are working on a macro to change input shaping during a print, still has a few bugs but works.
6:04 personal access token should not be public man
Will delete and recreate 👍
i love watching these videos even though i use a bambu, the video is really interesting by itself
We got Advanced Klipper before GTA 6
installin this to my heavily modded v0 :D
thx for the vid and info
Neat! I'm sure DangerKlipper allows you to also move any axis manually without always homing them first? That's been annoying for me in stock Klipper.
There’s a couple ways to do this already. There’s an option to turn on that enables it, but I forget how to move it afterwards. The other way is to send a gcode that tells an axis it is now at whatever position you give it, so it thinks it’s homed. Then it will move as normal.
Not sure where the whole 'danger' thing comes in, other than it's just the non-standard version of klipper 🤔
very useful, thanks!
But I don't want PID profiles, I want klipper to finally support the M301 gcode command. Imagine finally being able to initially tune, and then dynamically set PID depending on print speed and layer time, no more glossy/matte discoloration on prints.
any chance you'll make a video on the "TMC autotune" plugin? and maybe compare it to the "chopper-resonance-tuner" one?
for me the chopper-resonance-tuner gave me much better results but it's definitely not a fast process, plus I'm using cheap unsupported motors so I might've gotten some values for "TMC autotune" wrong
@@danandrei96 I still have super limited experience with it. It’s definitely something I’ll consider.
I would also love to see a video on this topic 👍🇦🇺😊
Mostly I needed a modified heater algorithm. That’s why I DK.
Danger Klipper had a Bed Mesh surface scan ?
I didn't found this option in DOC.
Been wanting to try danger klipper for a while, but getting my SB2040 CAN board working with normal klipper was hard enough, so I’m worried working with the danger klipper repo is gonna complicate things beyond my ability to flail my way to success…
should basically just work, there is very little divergence in the firmware so provided your Klipper installe/ FW is recent you may not even need to change firmware.
I may give this a try on my V0. Too many times I've had the USB Display disconnect because I bumped its cable and such and the print failed. Currently I don't have the screen enabled due to it loosing connection so it would be nice not to have to worry about the printer freaking out if the screen disconnects,
Man I have a couple flashforges, un-converted and a couple klippers. That object exclude is a very much missed feature on my other printers.
It would be nice if they could add option to set different values for z tilt points and leveling points. I want my z til to measure height once on each point, and i want double points on each bed mesh, but I cant seem to do that with Klipper.
Ah.... A klipper fork where the dev doesn't refuse all requests for change/features just because HE things it's not important.
(Such a proper implementation of the S and R parameters in the set set and wait for temperature commands.
Hi!
RATS! Ember Prototypes doesn't have the build plate in my size (235x235). Can you say Ender 3 Enderwire?
A comment you made that is misleading...
Danger Klipper IS NOT dangerous just because "you can do something to damage your printer." You can do that with regular Klipper as well.
Danger Klipper is dangerous because you can Completely Disable SERIOUS SAFETY CHECKS that can lead to FIRES!
This SHOULD NOT be downplayed in the slightest and you SHOULD NOT play around with DK on a whim, you NEED TO KNOW what you are doing!
The reason DK has a lot of these "features" you won't find in mainline Klipper is because it is used as a test bed and it is easier to get features implemented in it than it is in mainline Klipper. If you want you printer to be reliable DO NOT run a test firmware on it!
Now if you're wanting to tinker and play around and you know exactly how all options in Klipper work then have fun! But if there are features in DK you really want, such as retract on sensorless homing, then insist they get merged to Mainline.
What tmc auto tune macro are you using ?
Why don't some of these features just get integrated into mainline klipper?
Some do, however Kevin doesn't like just adding new features or making huge changes. Klipper runs on alot of big business gear and changing things can cause issues for them etc so things get implemented or changed ALOT slower on klipper compared to dangerklipper which is much more for hobbiests.
What is SSHing ? Many like me aren't familiar with all the acronyms. Please an honestly dummies guide when it comes to software
Print area? No, DANGER ZONE. 😂
skr mini e3 v3 has jumpers on board for sensorless homing, is it better than software solution?
The jumpers are _required_ for sensorless homing. Danger-klipper allows for easier _configuration_ of sensorless homing.
I mean it is firmware forCNC machine not a daycare so anything going bad is on you not the program.
The per axis acceleration is not perfect. I returned to normal because I was getting little benefits and quality seemed worse
i mean, danger klipper makes it sound like all hell will break lose and everything that can go wrong, will go wrong but if they had called it klipper without training wheels? it might of been categorized has the “for professionals only” 😂
DangerKlipper: Klipper with devs that aren't seemingly actively hostile to opensource development (COUGH Dev response to klipper GH issue #6711 COUGH) and are happy to add a feature even if the main dev wont personally be using it...
Make sure to read through the discourse thread on the GH issue you're referencing and you'll see that it is no longer as black or white as it looked in the beginning.
@@SvenLankes I specifically take issue with how the devs reacted to an an *extraordinarily* well-made issue... being made on the Thing Specifically Made to Track Issues instead of their discussion forum. Not the bug itself.
@@SvenLankes It's pretty black and white (the bug, not the cause or the fix), i have it all reproduced on a single stepper + endstop setup. It's very broken.
@@SvenLankesUnfortunately those discussions on discourse aren't related to the bug i reported.
The bug report I wrote up multiple times after going through dozens of rebuilds against different patches to narrow down to the exact patch and finding the exact lines of change in that patch that caused the failure were completely dismissed and blamed on the hardware, when the hardware worked fine before that patch. The original author of that bit of code put a chip reset in before the first access for a reason (but that person never responded to the thread) and someone else removed that code, causing the bug. The workaround given was to change from hardware to software SPI (which means resoldering the assembly too) and the case was closed. The reason for the code removal was never explained, and since it literally only runs once (on first access), it's not like it was a performance optimization or anything. That one left me baffled.
Danger Klipper, hahahaha, try RRF. No holding hand, no limits, no boundaries and a good community that helps me to get my RooKRRF running.
Wait why doesn't it use the accelerometer in real time all the time?? This is really useful to look for issues?
Every smart phone does this for no reason... and tracks you and you don't even want it to.
Yet here it has a reason to collect real time movement data and nobody takes advantage of it? Not even this "advanced" software?
I need the training wheels
Haha nothing wrong with that at all.
@@ModBotArmy I just spent all day getting my printer config to work restarted the printer and the printer config file was just null over and over I guess I'm really not ready.
@@paintballercali That sounds like a corrupted microSD card. Never power off your Pi without a proper shutdown.
@@glabifrons yeah I didn't remember that there was a shutdown option. I have it basically going now
It's a nice tutorial, but imho a bit useless. If you can't find it and install it you don't actually need it, and probably should not even consider to mess with it 😂
Do you like to solve unnecessary problems every now and then (worst case scenario) and "rubber duck programming"? then Klipper.
Do you like to have something key in hand which you send a print and even forget it was goin because your high ass didn't notice it was 3 and a half days with 4kg of filament? MARLIN UH-AH AH!