Please ignore -- problem unrelated to Cura

[jhirschman 6]

My printheads seem to be drastically off right now -- you can see that most easily in the priming tower (upper right) where the circles are off in both the X and Y directions. Running a calibration shows the same sort of offset, although I haven't tried enter the "17s" and "18s" it would take to straighten this out.

 

This happened after my upgrade to Cura 4.12.1. My prints over the last few weeks have been single head prints, so it's possible this happened before, but it seems like quite a coincidence.

 

I also did 3 straight cold pull cleanings on printhead 2 (The first 2 tries the filament broke. Third was a hard pull, but I've done many cold pulls in the past without seeing this kind of offset problem) before this print.

 

 

 

Is anyone else seeing this? Any suggestions other than trying the crazy offsets?

Edited December 16, 2021 by jhirschman
I discovered the problem was not related to the Cura upgrade

[jhirschman 6]

Ugh. Please ignore this. After debugging (unimportant details, below), it turns out there was something wrong with Printcore 1, unrelated to either the Cura update or the cold pull. Super embarrassing, and I wish I knew how to delete the initial post.

 

Debugging steps:

1. Changed out Printcore 2 (thinking I damaged/displaced it with the cold pull). No change.
2. Downgraded to 4.11. No change.
3. Changed out Printcore 1. Everything is lined up again!!!

Apologies to anyone who spent more than a few seconds reading this post.

[RudydG 62]

3 hours ago, jhirschman said:

Ugh. Please ignore this. After debugging (unimportant details, below), it turns out there was something wrong with Printcore 1, unrelated to either the Cura update or the cold pull. Super embarrassing, and I wish I knew how to delete the initial post.

 

Debugging steps:

1. Changed out Printcore 2 (thinking I damaged/displaced it with the cold pull). No change.
2. Downgraded to 4.11. No change.
3. Changed out Printcore 1. Everything is lined up again!!!

Apologies to anyone who spent more than a few seconds reading this post.

Thanks for updating with the solution, can happen to everyone, so it is a valuable post!

Edited December 16, 2021 by RudydG