Cancelobject - halts printer completely - Cura 5.3.1

Plugins
1

First time caller, longtime listener...love the show

I recently installed the cancel objects and have hit a wall. Once i select an object to cancel the printer continues its script until it gets to the cancelled object and stops. Print head and bed remain on with the nozzle resting on the cancelled object. I have added ";MESH:ENDGCODE" to the beginning of the endcode in Cura. Combing is off. I have also noticed that the printer will not accept commands after it stops. Have to reboot everything to get it working again.

I'll admit I am not supper good and breaking down the G-Code

Thank you in advance for any ideas or guidance

2

Hi Jeremy,

can you please provide more information on the printer you have, firmware info where possible and the logs from your octoprint/ocopi system.

Click on system followed by Download Systeminfo Bundle and attach the file with the upload button on the forum.

We can then compare responses from your system to my own and see what the differences are.

3

octoprint-systeminfo-20230523234222.zip (1.4 MB)

@jattie thank you so much for getting back to me so quickly. I've attached the requested system bundle

As for the printer, is an SV01 Pro running Marlin 2.0.9.2 Firmware 1.2.0

4

Hi Jeremy,

my cancel objects seems to work just fine, however there seems to be a lot of conditions to be met in order for it to work.

I checked the logging and the octoprint log does'nt log anything and you have to enable logging for the plugin explicitly to get something logged.

image
image915×200 4.45 KB

Make sure to click save after you added the option

==> /home/octo/.octoprint/logs/plugin_cancelobject_cancelobject.log <==
2023-05-24 10:30:39,770 Object puzzle_1.stl cancelled
2023-05-24 10:31:06,809 Object puzzle_3.stl cancelled
2023-05-24 10:31:09,981 Object puzzle_4.stl cancelled
2023-05-24 10:31:14,067 Hit a cancelled object, puzzle_1.stl
2023-05-24 10:31:14,080 Hit a cancelled object, puzzle_3.stl
2023-05-24 10:31:14,093 Hit a cancelled object, puzzle_4.stl
2023-05-24 10:31:14,102 Took 0.008040666580200195 to skip block
2023-05-24 10:33:07,062 Hit a cancelled object, puzzle_1.stl
2023-05-24 10:33:07,074 Hit a cancelled object, puzzle_3.stl
2023-05-24 10:33:07,086 Hit a cancelled object, puzzle_4.stl
2023-05-24 10:33:07,096 Took 0.010609865188598633 to skip block
2023-05-24 10:33:27,624 Object puzzle_5.stl cancelled
2023-05-24 10:33:27,647 Took 20.560871839523315 to skip block
2023-05-24 10:34:54,906 Hit a cancelled object, puzzle_1.stl
2023-05-24 10:34:54,918 Hit a cancelled object, puzzle_3.stl
2023-05-24 10:34:54,931 Hit a cancelled object, puzzle_4.stl
2023-05-24 10:34:54,939 Hit a cancelled object, puzzle_5.stl
2023-05-24 10:34:54,948 Took 0.008770227432250977 to skip block
2023-05-24 10:36:15,346 Hit a cancelled object, puzzle_1.stl
2023-05-24 10:36:15,354 Hit a cancelled object, puzzle_3.stl
2023-05-24 10:36:15,368 Hit a cancelled object, puzzle_4.stl
2023-05-24 10:36:15,376 Hit a cancelled object, puzzle_5.stl
2023-05-24 10:36:15,384 Took 0.008281230926513672 to skip block
2023-05-24 10:36:51,363 Object puzzle_2.stl cancelled
2023-05-24 10:36:51,482 Took 36.105923652648926 to skip block
2023-05-24 10:37:17,212 Hit a cancelled object, puzzle_1.stl
2023-05-24 10:37:17,215 Hit a cancelled object, puzzle_3.stl
2023-05-24 10:37:17,220 Hit a cancelled object, puzzle_4.stl
2023-05-24 10:37:17,223 Hit a cancelled object, puzzle_5.stl
2023-05-24 10:37:17,228 Took 0.004570960998535156 to skip block
2023-05-24 10:37:29,346 Hit a cancelled object, puzzle_2.stl
2023-05-24 10:37:29,352 Took 0.005515575408935547 to skip block

Try to enable this and see if there appears meaningful error message in there.

1 Like
5

Please provide your gcode file that gives you this problem.

6

Here is the G-code of the most recent failed cancel print in a .txt format. Thank you for taking a look

(Gcode-cancelobject-fail.txt - Google Drive)

7

That isn't the gcode file, but the terminal output.
Regardless, it seems the issue happens after your printer is sent a Dwell command (G4 P1). It is possible there is a firmware issue that is causing the printer to report that it is busy.