does not completely finish the last layer of the print 3.5.0-b4

Arminas

@dc42 Downgraded to 3.4.6 again, no issues. Input Shaper activated, same speed. I don't know if something is wrong with my setup/config, but 3.5.0 rc1 does not work for me

Threepwood

@Arminas You seem to have had the same problem as I am having.

I noticed when I looked over the print, the blobs were caused by the printhead stopping for a fraction of a second, so residual pressure in the hotend was extruding plastic on the one area, causing the blob.

https://forum.duet3d.com/topic/33692/input-shaper-causing-stutters-and-blobs-on-curves-rrf3-5-0-rc-1/1

Diamondback

@Arminas said in does not completely finish the last layer of the print 3.5.0-b4:

@dc42 Most of the time, after the printing process, DWC shows that printing is paused and I have to press cancel the print, although it's finished, but heaters are turned off.

Today it happen again, and even worse. I was looking at the last layer being finished, and couple of seconds before the end, print bed moved up very fast and crashed into the part, melting the hole into the part with hot nozzle.... Luckily, I was standing next to the printer and turned it off as fast as I could.

@dc42 i just had this very issue with 3.5rc1. (also had similar issues with the beta versions before, but was blaiming bad settings or something since it didn't always happen) I had to turn the printer off immediately to prevent any further damage after the nozzle crashed into the print.

Arminas

@Threepwood This might be a different issue now. To sum up, during my last RRF upgrades to 3.5.0. Beta and 3.5.0 RC, I had several issues (maybe all are related):

Printer did not finish the last few lines, but there was no printhead crashing into the part.
In the middle of the print, extruder used to extrude backwards for a couple of seconds, but there was no printhead crashing into the part.
Everything was good, but at the very last lines printhead crashed into the part.

Well, all issues are related with the unwanted movement of the printhead/extruder.

Arminas

@Diamondback same here. Now I am using 3.4.6 latest firmware with input shaper results, no issues.

Diamondback

Any news on any of this? I have a hunch the crashing part is related to whether or not I paused the print at some point... I don't really want to test this idea though, the stuff is too expensive to keep destroying Revo nozzles from crashes...

Arminas

@Diamondback I went back to RRF 3.4.6 and don't have any problems now. I just know that I had extruder crashes with RRF 3.5.0-b, I had blobs on the corners with RRF 3.5.0-rc1 and now I have zero issues with RRF 3.4.6. I would be glad to search what causes these issues with new firmware, but I am trying to run a 3d printing business and don't really have time for this. Also, I am afraid to brake some parts of extruder...

dc42

@Diamondback you could try the new build at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0. I wasn't able to replicate your issue exactly, but I did replicate and fix another, possibly related, issue with print jobs not quite completing.

Diamondback

@dc42 said in does not completely finish the last layer of the print 3.5.0-b4:

@Diamondback you could try the new build at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0. I wasn't able to replicate your issue exactly, but I did replicate and fix another, possibly related, issue with print jobs not quite completing.

Will do. Does this also include the fix for the not quite finished print?
( https://forum.duet3d.com/post/325940 )

dc42

@Diamondback that's what I want to know. It may have had the same cause as the issue I was able to reproduce and fix.

Diamondback

Ah, sorry, wrong thread I meant to post in the filament monitor one...

Diamondback

@dc42 Can you elaborate what sort of condition lead to the SD print not finishing properly? Can you tell what it would do "instead"?
Would it just ignore all the rest of the file? Or just parts of it? What I can imagine given the behavior I saw is that RRF ignored the last few lines of actual extrusion but then executed all the management stuff afterwards (tool deselection, toolhead parking etc)
In that case the headcrash would happen due to the nozzle still being in the middle of the print and Z not being lifted...
Is that something that seems plausible?

I really want to understand this issue and help debug it but I'm not really fond of destroying another Revo nozzle...

Diamondback

@dc42 More info on this from my side. What I have been seeing appears to be the combination of two issues.

Not finishing of the extrusion bit of the print file
Some weird crashing/stalling movement issues after pausing and unpausing the print

The first issue seems to be new with RC1, but the second issue also just happened to me on beta 4. I will try to actually replicate what it's doing, maybe without a tool or without a nozzle or something. It's kinda scary, but I don't fully understand what exactly is happening. The printer makes very loud nosies as if it's stalling/crashing into something, but ultimately it somehow ends up moving in the right places. I haven't been able to actually see what it's doing, I only heard it a couple of times and saw the end result. I will try to film it or something and then make a new thread about that.

Arminas

@Diamondback A little bit of info from my case:

Not finishing of the extrusion bit of the print file - I had this problem with 3.5 beta versions too, it was solved with RC1.

2.Some weird crashing/stalling movement issues after pausing and unpausing the print - I had crashes for no reason at the very end of the print, with beta versions (there was no pause).

dc42

@Diamondback have you tried the new firmware at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0 yet?

Diamondback

@dc42 So far no issues with not finishing the print with this build.

dc42

@Diamondback thanks for reporting back.

Diamondback

@dc42 Some more prints done, nothing new to report, all working fine.

dc42

@Diamondback thanks, I'll flag this as solved.