Welcome to the SeeMeCNC Community

When I select Pause Print from the LCD, my machine takes off away from the print then comes back and crashes the part immediately. Is there a script that runs on pause from the LCD? I am printing from SD card when this happens.

Well nevermind. I was looking through the SDCard.cpp file and see the problem. I went to Github to look at the firmware there and it looks like there was a fix 7 days ago. There was indeed an issue with the pause code. If you are having this problem update your firmware.

Well I'm still having issues. I replaced the SDCard.cpp file but now it seems to be doing something else. When I pause it goes all the way home and then comes back down to a z position and inch or so above the layer it stopped at.

Then on resume, it homes again and comes all the way down. Not sure if it is coming back to the exact position, but I definitely don't want it going home first. Very odd. Hopefully someone at SeeMeCNC will chime in here.

Because these machines use stepper motors, and don not have encoders, they have to no way of knowing where they are at unless they go home first.

Absolutely true. However they don't need to home when you pause. The motors never turn off and the machine still knows where it is. This is a bug.

thats exactly what it is, me and john fixed the "shoot off to the side" part of pause, and I got it to go up to home (not a full home, does not hit endstops).. but its more of a random that it shoots back down when you pause. 9 times out of 10 I was able to pause, it goes up, stops... then sits till continue, and goes back where it was and keeps printing. This is so you can change filament if you want to change color or are running out of filament and want to replace the spool... but randomly when you pause, it goes up like it should, but then shoots back down for some reason. We have tried adding delays, changing the way it goes up, but have not been able to find what causes that bug that shoots it back down randomly when you pause. So its about a 90% effective pause, but not 100%...

Guanu

Thanks for the feedback. I'll try work on it a bit too. I thought I was hitting end stops but now I'm not certain. I'll verify. When it shoots down and you hit continue it goes back up and then comes down again. Very odd. Also I noticed when you hit pause on the way up there a a few very brief stops. It doesn't go up in one smooth move. I wonder if that has something to do with the 200ms pause?

the brief stops you are seeing is it doing three commands at once, its doing the z max move, and while its going to z max, it does x and y 0 since you cant just issue a home all command, as this resets the memory location, and would remove the last location and you would not be able to resume. So you will have the two pauses there, (not manually inserted pauses, its just the way its handling the command) the problem with resuming when it does the fast shoot down, is that when it does that, it skips steps, so you no longer have an accurate location. if it was able to do that shoot down without skipping, you would be able to resume no problem.

Guanu

My ROSTOCK MAX V2 Fails to PAUSE correctly 9 times out of ten. Regardless of the success rate, results are unpredictable when trying to use the PAUSE function provided in the SD CARD MENU. My experience has been that when using the Repeater Host PAUSE function things work fine. How much different is the process used by Repeater Host and that of the MAX V2 firmware?

xr750 wrote:My ROSTOCK MAX V2 Fails to PAUSE correctly 9 times out of ten. Regardless of the success rate, results are unpredictable when trying to use the PAUSE function provided in the SD CARD MENU. My experience has been that when using the Repeater Host PAUSE function things work fine. How much different is the process used by Repeater Host and that of the MAX V2 firmware?

Looking at it they behave exactly the same.
Pushing pause in the host software inserts a command into the queue, which when it's interpreted by the firmware calls the sd.pausePrint function.
Selecting it from the UI just directly calls the same function.

I have the same issue. No fix yet? i just lost an 36 hour print because of the pause button..