Hello @mungbean,
Thank you for the explanations. I did not upgrade the motherboard of my CR-10S, I only updated the firmware (TH3D U1.R1.8i) yes me baudrate is at 115200. hard to say for the changes of layers.
I have a gcode file that with octoprint creates breaks of more than 3 seconds (https://ufile.io/vx0xj)
https://www.thingiverse.com/thing:686111
i add a video with my problem (play with sound) : pb octoprint.zip (446.3 KB)
I had this issue with my Pi3+. I rebuilt the SDcard with a new Octopi Image and the problem went way.
Hello,
I tried running the previous Gcode directly from the new instance of octoprint (windows) and I have the same problem.
for my previous test I had a difference with my raspberry (octoprint) and windows (octoprint), now after having optimized my plugin configuration of octoprint it's the same.
but i still have lag, much less, but still on some gcode files
First, I am a real novice with the Raspberry Pi unit. However, I did have a problem with mine that was solved by powering it with a wall wart with more output. You should have a 5 volt supply with at least 2 amps, preferably 2.5 amps. The unit may be starving for current and waiting for small periods of time unit the power supply can catch up with the output. Just a guess, but you problem sounds like hardware, not software.
ALan
Hello ALan,
Thank you for your feedback.
I do not think this is a power problem, because I reproduce the same problem with an installation on windows octoprint.
in addition I removed the power of my USB cable between the octoprint and the printer (to avoid that it powers the printer when it is off)
It might be worth trying to disable Bluetooth on the Raspberry as well as turning off the console's ability to connect via serial.
This is technical but it goes like this:
If the "cheap UART" is doing your communication to the printer, it could manifest itself in serial-related problems like pausing (perhaps).
Docs See "Disabling Linux's use of console UART"
OK bluetooth turn off :
add : dtoverlay = pi3-disable-bt into /boot/config.txt
remove : console=serial0,115200 into /boot/cmdline.txt
test in progress
Did you ever try the Spiralize Outer Contour feature of Cura?
@OutsourcedGuru yes I tried but it makes my model hollow (just the outer shell without filling),
it's not really what I'm looking for 90% of my print
Are you sure you're not confusing that with Special Modes -> Surface Mode that's right above it?
But maybe I'm mistaken. Does it remove the insides?
During my tests, I activated this option.
I would do another test to be sure.
but when I read the description, this part: "this feature turns a solid model into a single wall print" that makes me think that I did not make a mistake
People swear by it. I don't think they'd be so enthusiastic if it created a hollow part. I'll try it myself later but I'm writing some code at the moment.
Hi!
I had the exact same issue some time ago.
I made a complete new reinstall with a fresh OctoPi image onto a new SD card.
Reinstalled all the Plugins I need.
And now everything is fine.
What is really odd and the nail in the coffin so to speak is that the same issue is happening on a windows PC. Try making a new profile in your slicer with some pretty rudimentary but satisfactory settings and re-slice your gcode.
On the same page that speaks of disabling Bluetooth, there is an entry telling you how to check for throttling.
Hey guys. I have exactly the same problem with my Tevo Tarantula. These lags occurs randomly. It only happens printing from octopi, not from SD Card. IĀ“ve disable all the installed plugins, and no changes. Was monitoring pi using top to see if it was resource related, but it was using just 1/4 of processing power, and very low memory usage. IĀ“ll be away from home this week, but as soon as I come back I will try a fresh install to see if it getĀ“s better.
Just to give a feedback. Reinstalled and problem solved. But itĀ“s too much effort, to reinstall all plugins back.
If you have your OctoPrint running as you like, you can make an SD card image of your own to have a complete backup.
It's entirely possible that one or more of your plugins was causing this. Anything that hooks into the serial stream adds the possibility of slower execution.
