Jerky communication between MatterControl on a Windows 10 PC and a Rostock Max II printer
ryan.lutz last edited by
Interesting coincidence, but I think that's all it is.
We look forward to your results.
I just sent the terminal log and the line numbers where the printer paused to firstname.lastname@example.org. Both lists are in the attached excel workbook.
This time I printed the calibration cube and instead of 35 lines there were 32 to 34 lines between pauses. It almost seems like a buffer/serial communication/driver/firmware issue.
I used yesterday's 1.6 Alpha build for my test that I ran this morning.
Thanks for helping,
I took this video while trying to print the calibration box. The terminal log that I submitted for analysis was created while capturing this video.
Here are the terminal log the numbers where the printer paused while printing the calibration cube.
Line Numbers with Pauses Number of lines between Pauses 2279 2312 33 2345 33 2378 33 2411 33 2445 34 2478 33 2511 33 2545 34 2577 32 2610 33 2643 33
I found the solution to my problem. I guess my database must have been corrupt. I closed MatterControl, renamed the MatterControl folder (C:\Users\$USERNAME$\AppData\Local\MatterControl) and restarted MatterControl. After that the printer worked without any jerking or stuttering.
Lochemage last edited by
I'm glad that you found the problem. I know this might sound like a stupid question, but when was the last time you rebooted MatterControl or your laptop? I only say this because I have had experience with communication being jerky like this, and it was because my PC was running out of memory. It turns out that MatterControl's memory usage goes up and rarely goes back down (every time I view a 3D model, or it's g-code, memory goes up, even if I view the same model repeatedly), eventually I need to reload it or even reboot my whole machine before I get smoothness again.
ryan.lutz last edited by
I think @Lochemage may be on to something. The jerky behavior has been hypothesized to be related to memory problems, so closing MatterControl might just reset any affected memory and dissipate the symptoms temporarily. I'd expect the behavior to return after memory issues show themselves again.
Thanks guys for your feedback.
Hey tellingmacine, thanks for all the hard work looking at this bug. We were able to figure out exactly what it is and it will be fixed in MatterControl 1.6.
Actually, it is already fixed! Try the alpha. :
the Alpha is already installed and printing PokeBall bottoms. I am liking all the new features!!!!
Thanks again for your great support!!!!