Error after Z-Tilt Calibration When Printing: No trigger on probe after full movement
------------------ Issue Summary ------------------
When starting a print, everything successfully homes. Z-tilt also functions correctly. However, after z-tilt calibration (when adaptive mesh runs and toolhead moves to print the prime blob), it seems like the toolhead crashes.
This results in the toolhead not arriving at the specified location for the prime blob. Instead, the toolhead goes to the same position (as seen in the video where the probe is off the bed) and crashes the nozzle into the bed plate.
There is no resistance in the system (belts aren't too tight, cables aren't catching on anything, etc). I had a print work just fine before this starting happening but now it is consistently failing. I would love some help figuring this out!
------------------ Technical Details ------------------
Machine: Rat Rig V-Core 3
RatOS Version: v2.1.0-RC3-29-g6f87a747
Gcode: attached
printer.cfg: https://gist.github.com/andrew-manger/fe1917aca6e63c5a084fe2db92bfad44
Debug Zip: https://drive.google.com/drive/folders/1wtubo_pa70HFHotzsdm6dtbGkA25i9Q2?usp=sharing
Logs: https://gist.github.com/andrew-manger/3ef8df4f37b60995bac00b77d1c09a51
Videos: https://drive.google.com/drive/folders/1J3UBRki_YggkIMQwkz-PHCm_39cMuAAy?usp=sharing (suspected cause of error occurs at 45 second of IMG_4430.mov. The sound you hear when the print head moves from the back to front right is just from the cable wrap scratching against the corner of the acrylic panel in the back.)
24 Replies
Seems like your acceleration/speed is too high at that point and the motor/physics can't keep up
Thanks @TheTik, where would you recommend limiting the acceleration? The machine setting on the dashboard or in a config file?
Honestly not sure, try the easiest first, the dashboard. I'm not 100% sure where the speed is set for the macro
Gotcha, I’ll play around with it, thanks!
oh! Are you in "performance mode" yet? Might be an appropriate speed if you're at the correct motor amperage
I wasn't. I did just try enabling performance mode, but it crashed the printer with stepper overheating warnings. I also tried decreasing the acceleration from 3000mm/s to 1000mm/s, but I'm still getting that weird skip right around adaptive meshing.
Here is another video of the issue without the cable scratching noise
What was the exact error message?
I don't get an error message when the skiiping happens, just afterwards when I get "No trigger on probe after full movement" because the printhead is in the wrong place
Sorry, this bit. "crashed the printer with stepper overheating warnings"
Ahh, gotcha, I first get:
And then I get one more OT warning (I'd have to run it on performance mode again to get the error) before the firmware shutsdown to protect the steppers. They are not actively cooled and I think they need to be when turning on performance mode, as it says in the configurator.
not the steppers, but the stepper drivers need actively cooled
yes, exactly, I'm not actively coolig them, just heatsinks
as the guide says, need to cool them to enable performance mode. Non performance mode is for early setup, to not crash into anything so hard. You've got the motion and homing working, so it's time to cool and enable 🙂
But should I be able to run it and print in non performance mode? Seems odd that you have to cool and use performance mode to print
you should, if you slow it down
It seems like you're running at performance mode speeds at non-performance amperage
Is 1500 for acceleration too fast?
I'm not good with the numbers, but try lowering it and see what happens
It skipped a little less, but is still skipping
I just found that when the error occurs, the reported machine settings change too. Typically, the velocity shows 300 mm/s but at the moment of failure, the velocity jumps to 18000 mm/s even though it is limited to 300 in my printer.cfg
I wish i knew how the limits actually worked, cause I've seen similar. It's like whatever is in the gcode overrides. @blacksmithforlife Do you know of a guide that says what trumps what?
I didn't read the whole thread so I might be missing context - but I always thought that what you sliced was what you asked of the printer, and the config would limit it. However, others say the slicer will override what is set in the config.
so for example, I thought that if you asked for 5000 acceleration, but had the config set to 2000, you would only get 2000
But others have pointed out to me this isn't how it works, and I think Andrew's experience shows this is true. So, the slicer is overriding
Slicer shouldn't override the machine limits set in the config. I've also set the limits in the slicer but it didn't help. Do one of you have a gcode file I can test?
