Response time out. Attempting to Force Continue.

[theboz1419]

Lately I have been doing some long prints 40+ hours and this morning, while I went to work, I was printing a job that had been going great for 30+ hours.

I went to check up on it, via Octoprint, and found that it had stopped printing and I could not communicate with Octoprint either. So, I arrived home and could not find the issue except I still could not communicate with my RPi, so I rebooted it and I also could not find the issue on any of the logs.

To remove any issues with Octoprint, I decied to use my computer and Simplify3d to restart the print and see how it goes.

It started up fine and on the first layer it stopped and it looked like it had printing in the same spot a few times and then stopped. I noticed the error message" Response timeout. Attempting to force continue" but it would then try to continue. But the print head was stuck going over the same spot, as you can see in the picture.

I restarted it again and again it had repeated the same thing basically at the same spot of the print. Just prior to stopping I could see I was getting the same fault over and over

I'm not sure of what I can do to troubleshoot this. I'm thinking it's the main board of the printer, but I'm not sure

[theboz1419]

I'm currently printing another .stl and it seems to be going better. Although, I can't believe it was the .stl that was causing the issue, as I tried two different files of the samething and both had stopped in the same place. The file I'm printing atm, has made it past the same point and doing OK, so far.

[theboz1419]

I spoke to soon, as I am seeing the fault Attempting to force continue again

[theboz1419]

I purchased a new USB A to B cable. We'll that didn't help one bit. I guess I will be getting a new Rambo board in the near future. I will try Octoprint with the new cable first to atleast eliminate a computer.

[jferguson]

I apologize if this isn't clear, but I found that Octoprint has a max time-out setting such that if it doesn't get a new command for say 30 seconds it assumes print is over and shutsdown. I'd never had this problem in a few years of printing with it, until I did a model which required very long very slow passes andwith timing I think stallked the enxt command for over 230 seconds which was enough. If you look through the configuration, you'll find a place where you can increase the acceptable time out.

also google this problem because that's how I found out what to do.

I'm away from my system so cannot be sure my advice is entirely accurate, but your peroblem could be same as mine.

john