Bug report: object cancellation causes ugly things to happen

[gnydick]

@oliof the latter, since when you emit the code, it will immediately do the skip.

[mballin]

@gnydick Any update on this, i want to use the object cancel plug in, i tried it, and now it really messes up the print, and changes the axis for what the printer is calibrated to.

[dc42]

@gnydick is this still an issue with 3.5.3 and/or 3.6.0-beta.1 ?

[gnydick]

@dc42 Don't know, I'm not doing it because it nearly caused my printer to self destruct.

[dc42]

@gnydick have you checked that the maximum speeds you have set using M203 aren't higher than your printer can manage?

[Tinchus]

@dc42 I think not on 3.5.3, wich I have. I have cancelled objects and it works ok (duet3, 3.5.3, SBC mode)

[gnydick]

@dc42 definitely. My printer never loses steps when used normally.

[dc42]

@gnydick is that the case even if you request very high speeds, e.g. G1 X150 Y150 F100000 ? I think RRF uses the maximum speed you have configured in M203 when doing moves to skip objects.

[gnydick]

@dc42 yes, it is the case. I've used cancellation in the past without issue so I think this is a regression.

[gnydick]

@gnydick Any update here? This is still happening. I'm running even gentle prints with lower accel and speeds.

Duet 3 MB6HC	MB6HC	3.5.3
Duet 3 Expansion EXP3HC 	EXP3HC	3.5.3
Duet 3 Expansion TOOL1LC 	TOOL1LC	3.5.3
Duet 3 Expansion TOOL1LC 	TOOL1LC	3.5.3
Duet 3 Expansion TOOL1LC 	TOOL1LC	3.5.3
Duet 3 Expansion TOOL1LC 	TOOL1LC	3.5.3
Duet Software Framework	DSF	3.5.3
Duet Web Control	DWC	3.5.3

[dc42]

@gnydick I've asked @droftarts to see of he can reproduce this.

[droftarts]

@gnydick I've tested object cancellation, seems to work fine for me on 3.6.0-rc.2.

I created a job with 7 small items on the bed, widely spaced out, and cancelled a couple of them during the print. Travel speed between the normal objects and skipped objects seems the same, at 150mm/s. Cancelled objects with M486 P4 and M486 C. It does seem to travel to the cancelled object, and then on to the next one, rather than direct from the previous active object to the next active one.

I haven't tested on 3.5.x, will do tomorrow morning.

Ian

[droftarts]

@gnydick I've tested on 3.5.4, same file, same result when objects are cancel: seems to work correctly, no sudden motor movements. What slicer are you using? Maybe it is not tagging each object correctly. If you can post a simple gcode file that exhibits the problem, then we can take a look. I sliced with Orcaslice, which puts in M486 S# commands in seemingly sane places.

Ian

[gnydick]

@droftarts I'm using PrusaSlicer. I'll slice up a little print and upload it.

[gnydick]

@droftarts amp coin v18 - PLA.gcode

[droftarts]

@gnydick said in Bug report: object cancellation causes ugly things to happen:

@droftarts amp coin v18 - PLA.gcode

I hadn't looked at the file you sent until now, as I was waiting until RRF 3.6.0-rc.3 was released before further testing. I have updated my test machine with this, and ran my test of object cancellation (cancelling with M486 C and M486 P#, uncancelling with M486 U#), without issue.

I looked at the file you sent, but it seems to only have one object?

I've attached my test gcode, in case you want to try it. It has a centre origin, currently sliced for PETG, 0.2mm layer height with 0.4mm nozzle.

Belt anchor_PETG_9m33s.gcode

Ian