Mk4 intermittently detecting what seems like a non-existent collision, how to address?
 
Notifications
Clear all

Mk4 intermittently detecting what seems like a non-existent collision, how to address?  

  RSS
jbroggio
(@jbroggio)
Eminent Member
Mk4 intermittently detecting what seems like a non-existent collision, how to address?

Hello all,

This doesn't seem to happen often, but it DOES happen sometimes, so I am curious what I can do to remediate it. 

Occasionally when starting up a new print, right around the nozzle cleaning stage of things, the printer detects a collision. It then seems to self-repair this, retaps, recleans nozzle, and then prints normally with no intervention really needed.

I calibrated (or at least tested, really) the Z axis and the loadcell etc, and it all seemed fine.

What can I do to prevent this behavior?

Thanks!

Posted : 07/11/2024 7:45 am
efvee
(@efvee)
Trusted Member
RE:

I found this also, in particular with TPU filament from the standard top spool holder and guide and the printer moving from parking pose to nozzle cleaning pose, so fast movement away from the guide. TPU filament then easily gets resistance in the guide, jerks the Nextruder and the printer sees this as a collision.  

Giving some slack on the filament may help. 

This post was modified 2 weeks ago by efvee
Posted : 07/11/2024 8:50 pm
jbroggio
(@jbroggio)
Eminent Member
Topic starter answered:
RE: Mk4 intermittently detecting what seems like a non-existent collision, how to address?

I'm not using TPU, for what it's worth. The TPU situation you described makes sense but I am using exclusively PLA. 

Posted : 08/11/2024 8:07 pm
efvee
(@efvee)
Trusted Member
RE: Mk4 intermittently detecting what seems like a non-existent collision, how to address?

Irrespective of the material, is there, in your setup a reason an rapid 'jerk' of filament could lead to increased resistance?  

Posted : 09/11/2024 10:45 am
Share: