#Octoprint zits, switch to Mainsail but...

77 messages · Page 1 of 1 (latest)

zinc edge
#

Hi All,

Using Octoprint since many time and printing essentially technical straight part, well I never noticed zits or blobs on my print.

I'm now trying to print a part that have cylinders and get a lot of zits/blobs.
My researches inform me that Octoprint is not able in particular cases, where there is a lot of information for a "high definition" circle for exemple, to send data fast enough.

I'm on SKR 1.4 turbo mother board.
RPi 3 B+.
50cm nice USB cable.

I was thinking that using a most "Klipper dedicated OS" can solve my problem, so I just switched to Mainsail.
I setup the "virtual SD card" by adding :

[virtual_sdcard]
path: ~/printer_data/gcodes

In "printer.cfg" file and it's the same path in the "mainsail.cfg" file.

But I still have the zits/blobs... (red cylinder)

How to reach the SD Card print quality from a RPi ???

novel lance
#

I am not sure what you expect but I explain you the difference:

  • Octoprint is a gcode streamer, in that scenario Klipper works as pure firmware and Octoprint sends the gcode line by line. That’s results in that the head sometimes pause if it can not send the gcodes fast enough. And yes worst case here are circles as that are many small moves.
  • virtual SD card print (btw also posible using Octoprint), in that scenario the UI (Mainsail, Octoprint whatever) tells Klipper only to print the gcode file. Klipper will open it and take care of the rest (reading the file from the card …)

Both have nothing to do with the artifacts you seeing in your print. For me that looks more like an old wet filament.

zinc edge
#

Look on the black part, the "big circle" at the center is perfectly printed.
That doesn't come from filament.

novel lance
#

I am talking about your red cylinder

#

As said I do not understand your technical question, if your where at Klipper and switched only between Octo and Virtual SD nothing changed.

#

What do you exempt from us, currently for me it looks more like a question for #print-quality

zinc edge
#

My "question" was about the data transfert speed between Octoprint and Mainsail.
The zits I get come from the capability to send the information to Klipper.
In Cura, I can reduce the resolution and I have less zits.

But how to get ride of it...?

novel lance
#

As I tried to explain, Octoprint send the gcode commands line by line to klipper ( done via a virtual console) in that that case you can see that the heads stand still for a second or longer and than continuing to print. A print imitated via virtual scarf means that Klipper reads the file direct and can plan ahead better and therefor you will not see the head pausing even if you print much faster.

#

So first question do you see that phenomenon that the head pauses in the middle of the print and continue a second or 2 later

zinc edge
#

That's what I try to do setting Virtual SD card, but there is no difference...

zinc edge
novel lance
#

Is that gone if you use the virtual sd card? Mainsail has nothing to do with it. In case using Mainsail you can compare it with mainsail is sitting on the backseat and watching Klipper driving

zinc edge
#

That's what I'm trying to do !

May you please confirm that the "only thing" to do is to add :

[virtual_sdcard]
path: ~/printer_data/gcodes

In "printer.cfg" ?

#

The same path is in "mainsail.cfg"

novel lance
#

If you have [include mainsail.cfg] already in your printer.cfg you do not need to add it a second time

zinc edge
#

You right, I remove it from printer.cfg right now.

novel lance
#

But it will not harm and yes if you have that block in and start a print in Mainsail it will request Klipper to print the file xyz and from that point in time only monitor Klipper

#

Klipper does the rest, that means Klipper reads the file direct from the sd card and does everything internally.

zinc edge
#

Well. So I don't know what to do.

novel lance
#

That’s why I said your question is more likely something for #print-quality

zinc edge
#

Last question about the RPi.

#

A RPi 3 B+ of powerful enough ?

novel lance
#

That depends on the printer and also what else is running in parallel, but in general a 3B is powerful enough

#

I see that bend corners also on the big black circle so it might be a combination of mechanics, speed and resolution

zinc edge
#

A Sunlu S8 with SKR 1.4 Turbo board.
I have a 3D touch and a webcam 720p/15fps

novel lance
#

And all others

#

I would try to print a cylinder in vase mode with the diameter of that part

zinc edge
#

Yes, that's the overextrusion caused by the head micro pause...

zinc edge
#

give me 15min

zinc edge
#

I still have random pauses.

#

Only in the same area

#

I can see the head briefly slow down and restart

#

The other side is perfectly printed

novel lance
#

Minimum layer time active?

#

What happens if you reduce speed?

zinc edge
#

I have made that mistake first, that's why it took me so long.
Minimum layer time is setted now at 1sec.
I launch a print at 50mm/s, I'm currently at 100mm/s

#

Still have the same "head pause/lag"

#

I can see the lag during print

#

same behavior than using Octoprint, Klipper seems to wait the next information.

#

It's always in the same area, there is a bottleneck.
But were ?

zinc edge
#

Well, no problem with Prusa Slicer (I was using Cura since ages)

willow zinc
#

do you print with octoprint or mainsail now? is octoprint also on the same system installed? i cannot read this information in this conversation...

#

ans pls upload a gcode file + klipper log for more informations + a video from the print, when it stops

zinc edge
#

Hi, Thanks, problem is totally solved using Prusa Slicer !

#

I'm now on Mainsail

#

may you please confirm that is the only thing to add in "moonraker.cfg" to get a "auto power off" once printing is finished :

[power SunluS8]
type: gpio
pin: gpio2
locked_while_printing: True
on_when_job_queued: True
restart_klipper_when_powered: True
restart_delay: 2
bound_service: klipper
off_when_shutdown: True
off_when_shutdown_delay: 180

willow zinc
#

ok. maybe a "settings issue" with cura...

zinc edge
#

I guess too

willow zinc
zinc edge
#

Noticed and thanks you.
What is the command to add (and then I close the post)?

willow zinc
#

but remember that you are simply taking the power away from your pi!

zinc edge
willow zinc
zinc edge
#

Why that doesn't work ?

[power SunluS8]
type: gpio
pin: gpio2
locked_while_printing: True
on_when_job_queued: True
restart_klipper_when_powered: True
restart_delay: 2
bound_service: klipper
off_when_shutdown: True
off_when_shutdown_delay: 180

willow zinc
#

is your klippy state "shutdown"?

#

(this would be a thermal runaway or some other klipper errors)

zinc edge
#

I have to add end-gcode "shutdown" ?

#

(sorry it was a plugin in Cura...)

#

It's the last thing I miss !

#

It's seems to only miss a M80 in my end-gcode

willow zinc
#

but i think you have to do it as a delayed macro. otherwise you will see all jobs as "canceled" in your history, when you poweroff your printer "during" a job

zinc edge
#

I see, but there is no link with GPIO2 in your link

willow zinc
#

this doesnt matter...

zinc edge
#

ok, thanks

willow zinc
#

just the name have to match

zinc edge
#

The name of my printer ?

willow zinc
#

power device

#

pls read the description below... there are all informations about this script

zinc edge
#

I'm on it, OK, we was rightly talking about [power SunluS8] in my case.

willow zinc
#

SunluS8 in your case