RRC[

Rat Rig Community [Unofficial]•13mo ago•

36 replies

Coeus

Print Fail during beacon calibration after update - bug?

I'm running a Vcore 3.1 300 and upgraded from 2.0.2 to 2.1 RC 3 this past week.

@miklschmidt Posted an update 3 days ago to Git.

I updated the RatOS first. I had already been working on some first layer issues with beacon contact, and believed an update may flush out some of the bugs I was hitting. These first layer gcode files were produced and did print after the RatOS updates, where I did encounter some OS issues and notifications in that print via klipper screen, but couldn't catch them on the screen since I was so closely watching the first layer performance and beacon probe sequences. Those didn't occur frequently, and I only had to print about 5 first layer prints before was able to move forward.

The printer begins the full calibration routine, and abruptly, I receive the following message on Klipper Screen

(attached pics of Klipper Screen)

The message in Klipper Screen indicates that the system is "Probing the end of the Prime Location". So the printer is still very deep in the START PRINT and in calibration land of macros.

At this point the printing aborts, but there are no other messages. You can't select 'Cancel' or Pause because the hotend has already cooled down below melt temps. ( I happen to be running PLA on this particular print). But you can back out, and manually set the heater back to the original printing temp, only to be able to select Cancel or Pause, and completely abort the print.

Some of the messages I see in the console on Klipper screen are:
Adaptive Mesh: bicubic interpolation with a probe_count of less than 4 points detected. Forcing lagrange interpolation.

It also seems to stall Mainsail and I do not see any updates in my browser to continue or perform any debug. I was able to SSH to the machine - but I don't see where to find the log files to expose any issues.
I had to reboot my machine to reset Mainsail access.

Suggestions?