Notifications
Clear all

Prusalink vs Octoprint for the MK4  

Stránka 2 / 2
  RSS
Steve
(@steve-4)
Estimable Member
Topic starter answered:
RE: Prusalink vs Octoprint for the MK4

ArcWelder causes my MK3/S to lock up.  Took it out of Octoprint, and everything worked fine.

Senior Life member of IEEE.

Napsal : 24/10/2023 5:07 pm
Walter Layher
(@walter-layher)
Prominent Member
RE: Prusalink vs Octoprint for the MK4

What kind of Pi are you using? I have had no problem with the Arc-Welder plugin and I have been using it for years on my MK3S+ and also for months on my MK4. I am using it on Pi4s, on slower Pis it probably takes a while to finish processing the file. The plugin should not block anything during printing because the arc conversion process runs after you send the gcode file over from PrusaSlicer and you can start the print job only after the conversion process is finished. Then it is just like printing any other gcode file (it just ends in *aw.gcode) and the plugin is not active on the Pi while the print job is running. It is just a much smaller file that gets sent to the printer.

Did you see a high rate of "resends" in the top left part of the OctoPrint interface? This indicates a communication problem between the Pi and the printer. Normally this value is 0 or very close to 0.

Or did you select "Upload and Print" in PrusaSlicer? This could cause the unprocessed gcode file to be printed and the processing of the Plugin happens anyway and slows everything down, although the arc-welded file will not be printed. As I understand it, you should select just "Upload" and then wait until the Arc-Welder processing is finished before you start the print job of the processed file from the OctoPrint interface. At least that is the way I have been using it, never tried the other way. So I just assume that is what happens if you select "Upload and Print". 🙂

Napsal : 24/10/2023 5:31 pm
ScottW se líbí
PAUL HODARA
(@paul-hodara)
Trusted Member
RE: Prusalink vs Octoprint for the MK4

I have also used ArcWelder and MeatPacker for many months on an Rpi 3B without any problems. It may be a conflict between ArcWelder and another plugin.

Napsal : 24/10/2023 6:01 pm
eagleeye
(@eagleeye)
Active Member
RE: Prusalink vs Octoprint for the MK4

I currently stopped using octoprint, I got to strange issues. It looks like the head is moving slower then it should, but the extruder  extrudes as it moves faster.

So I have many strange walls, but it is not 100% repeatable.

I'm waiting for the new firmware for the MK4

Napsal : 24/10/2023 7:17 pm
Steve
(@steve-4)
Estimable Member
Topic starter answered:
RE: Prusalink vs Octoprint for the MK4

I finally connected my MK4 to Octoprint.  It works fine except the printer status is not displayed on the LCD.  I submitted a bug report on Github about this.

Senior Life member of IEEE.

Napsal : 27/10/2023 1:30 pm
James Kirk
(@james-kirk)
Trusted Member
RE: Prusalink vs Octoprint for the MK4

This is already known. Octoprint is not fully supported yet, also the filament (runout) sensor does not work with octoprint.

Posted by: @steve-4

I finally connected my MK4 to Octoprint.  It works fine except the printer status is not displayed on the LCD.  I submitted a bug report on Github about this.

 

Napsal : 27/10/2023 1:47 pm
Stránka 2 / 2
Share: