Basic Information:
Printer Model: Anycubic Kobra Go
MCU / Printerboard: Trigorilla
klippy.log
Attached
klippy.zip (1.3 MB)
Fill out above information and in all cases attach your klippy.log
file (use zip to compress it, if too big). Pasting your printer.cfg
is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
When starting a print or start of bed mesh leveling, I run into an issue where the stepper makes a beeeep noise because its being driven to hard, which causes the Z to skip steps.
I’ve noticed it right after X hits the 0 spot which is 10mm from the endstop and then it happens to Z, sometimes multiple times. Doesn’t seem to matter how slow I set all the axis in both Klipper and the slicer, but it also happens during a bed mesh so I don’t think the slicer has much to do with it. I think it’s trying to apply my X Y velocity & or acceleration to the Z…
The reason I say that is because there seems to be another weird fault that uses the Z homing speed as X Y at specific times. Here’s an easy to test example, set center of bed as home with probe. Set X Y speeds to 120mm/s with 40mm/s bump, then set Z to 8mm/s with 1mm/s bump. After the endstops are hit and bumped, the X & Y will move at turtle speed, even slower than the X Y bump speed, to the center of the bed. I noticed this even without probe for Z and using the center as home but its not as pronounced because its only between Homing and start of Gcode. I can set the X Y to 300mm/s with 200mm/s bunp and it will still crawl after it completes the bump, and it will still use (what i think) my Z speed after the bump and onto whatever move is next until its told otherwise by Gcode or a command sent from Klipper.
Same Gcode works fine on Marlin with even faster speeds. The homing process works fine, its just when the print starts if the gantry is something like 10mm or higher above bed, It wants to slam down really fast when starting the very first part of your start Gcode and I can’t understand why, or why its ignoring the speeds set, where this mystery speed is coming from and so on.
If I turn the velocity down to like 40 it doesn’t happen, but that changes the velocity for everything.
My Z is a 4mm w/ non-captive stepper, you cannot hit it will full speed right away, honestly I’m shocked the default 8mm lead on the Kobra Go did it most of the time, but now I know why I had random start heights here and there. That is also the reason I changed my Z endstop to use the probe. Needless to say, my bed is wrecked crao happens, we move on.
I have tried Simplify 3D, Cura and Anycubic’s Slic3r. Different profiles and start Gcode in each.
I normally have my accel around 30, on S3D my Jerk is set to 1 with a speed of 10 for the Z. Lowered it from 14, but again this happens during a bed mesh as well which has nothing to do with the slicer.
XY were 1500 and Jerk of 7. I usually try to stay around those numbers.