OctoPi, OctoPrint and MK2  

Re: OctoPi, OctoPrint and MK2

I had seen that, but thought it was just a -per file- statistic. Do you use it? Do the totals include files that have been deleted off the Pi after they have been printed? I don't imagine I'll keep all my GCode out there forever.

Yes, I use it. It keeps the statistics for each file printed, with a total at the bottom, and doesn't remove those from the total if you delete the G-Code. It only deletes the stats for a file if you go into the stat list and delete it there. The only real problem that I have with it is that it doesn't seem to include any totals for failed prints. It puts them in the list but with no time or filament usage.

Re: OctoPi, OctoPrint and MK2

The only real problem that I have with it is that it doesn't seem to include any totals for failed prints. It puts them in the list but with no time or filament usage.

Thanks for the additional information. It would be a nice enhancement to see the time and filament added for the failed prints.

John

Re: OctoPi, OctoPrint and MK2

I am using OctoPrint (as OctoPi image) for two years now and was very happy with it.

With the MK2 and the latest OctoPrint version 1.2.16 - running on a Raspberry Pi 3, installed a few days ago - I encounter massive connection and communication problems. Jobs stop in mid-print, timeout issues (also having set them all up a large amount) and weird filename cutoffs like in 1990 on a DOS machine.
Haven't had this issues before. No idea, if my OctoPrint installation is broken somehow, or if there is an incompatibility issue with the current version.

So I am currently printing directly from the MK2 screen / SD card. Not too convenient...

Best Regards,
Martin

Re: OctoPi, OctoPrint and MK2

With the MK2 and the latest OctoPrint version 1.2.16 - running on a Raspberry Pi 3, installed a few days ago - I encounter massive connection and communication problems. Jobs stop in mid-print, timeout issues (also having set them all up a large amount) and weird filename cutoffs like in 1990 on a DOS machine.

What connection speed are you using? The fastest speed where I can get a reliable connection is 115200.

If you are already using that speed, I would suggest unplugging and replugging your USB cable. Either that, or try a different one. I purchased a very short cable to connect between my Raspberry Pi 3 and my MK2.

Also - if you look at the terminal window, are you seeing any error messages, or odd symbols? The only time I see odd symbols is when I am initiating the connection.

The files I upload to the Raspberry Pi (via OctoPrint) show the full file name. The files on the MK2 SD card show up as old style DOS 8.3 file names. I agree that seems an odd limitation, considering that the MK2 itself can display the full filename.

I have not had any communication errors, but also I have not tried to print anything longer than 2 hours via OctoPrint.

John

Re: OctoPi, OctoPrint and MK2

What connection speed are you using? The fastest speed where I can get a reliable connection is 115200.

String based serial communication, like Marlin uses, requires a specific baud rate to encode the sent character symbols. So 115200 is mandatory, especially because the MK2 uses a Mini-Rambo i.e. an 8bit processor with very limited specs and a fixed communication speed. Boards like e.g. Smoothieboard have advanced serial communication setups and can negotiate the baut rate during connection. So, yeah, I am using 115200, because every other speed produced encoding errors, thus a connection error.

If you are already using that speed, I would suggest unplugging and replugging your USB cable. Either that, or try a different one. I purchased a very short cable to connect between my Raspberry Pi 3 and my MK2.

Yeah, the cable could be really a problem. USB is prone to interferences. Funny enough, it is the genuine USB cable that came with the Prusa i3 MK2 kit.
This is another reason why I hope to see more 32bit boards in the future with Ethernet on board. But the best board is nothing without a reliable firmware, right? So I think we are well served with Prusa's Marlin version.

Also - if you look at the terminal window, are you seeing any error messages, or odd symbols? The only time I see odd symbols is when I am initiating the connection.

I think the biggest problem are the many automatisation routines found inside the MK2, being the bad mesh leveling, or the ColorPrint material exchange. They produce either a high calculation demand on the cpu and firmware so that there is no time left to report the status back to OctoPrint, or there is simply no feedback loop implemented during the routine execution. This causes OctoPrint to think the printer is gone, which results in a timeout. But I don't understand why this also happens during ordinary printing?!

The files I upload to the Raspberry Pi (via OctoPrint) show the full file name. The files on the MK2 SD card show up as old style DOS 8.3 file names. I agree that seems an odd limitation, considering that the MK2 itself can display the full filename.

There is definitely something wrong with the communication of the filenames. Either Marlin reports them as DOS 8.3, or OctoPrint is interpreting it this weird way. I also encountered a firmware crash, if I did the SD card swapping (to load new files on it) and file system navigation several times. The printer does not display the file-tree anymore and freezes. Restart of the printer is required. This has nothing to do with OctoPrint in this case.

I have not had any communication errors, but also I have not tried to print anything longer than 2 hours via OctoPrint.

I had communication drops after a few minutes.

Re: OctoPi, OctoPrint and MK2

Also - if you look at the terminal window, are you seeing any error messages, or odd symbols? The only time I see odd symbols is when I am initiating the connection.

I think the biggest problem are the many automatisation routines found inside the MK2, being the bad mesh leveling, or the ColorPrint material exchange. They produce either a high calculation demand on the cpu and firmware so that there is no time left to report the status back to OctoPrint, or there is simply no feedback loop implemented during the routine execution. This causes OctoPrint to think the printer is gone, which results in a timeout. But I don't understand why this also happens during ordinary printing?!

I wonder if a possible solution is to re-compile a special "Mk2" version of octopi that has a longer timeout?

Re: OctoPi, OctoPrint and MK2

It would be enough to use Google first. 😉
https://github.com/foosel/OctoPrint/wiki/FAQ#i-see-a-lot-of-communication-timeout-messages-in-the-log
http://docs.octoprint.org/en/master/configuration/config_yaml.html#serial see longRunningCommands

Re: OctoPi, OctoPrint and MK2

It would be enough to use Google first. 😉
https://github.com/foosel/OctoPrint/wiki/FAQ#i-see-a-lot-of-communication-timeout-messages-in-the-log
http://docs.octoprint.org/en/master/configuration/config_yaml.html#serial see longRunningCommands

Pfft. You and your "simplicity". 😉

Re: OctoPi, OctoPrint and MK2

Pfft. You and your "simplicity". 😉

He learned that from me 😉

Peter

Re: OctoPi, OctoPrint and MK2

Hi,

Just wondering, for the people having timeout during print from OctoPi, does it happens at the same time, is it on a specific portion of the gcode ?

Re: OctoPi, OctoPrint and MK2

Christophe

Its for commands like M600, G80 etc.

Simply a matter of adding such commands to the "Long Running Commands" list and maybe increasing timeout values.

Peter

Re: OctoPi, OctoPrint and MK2

It would be enough to use Google first. 😉
https://github.com/foosel/OctoPrint/wiki/FAQ#i-see-a-lot-of-communication-timeout-messages-in-the-log
http://docs.octoprint.org/en/master/configuration/config_yaml.html#serial see longRunningCommands

I have set this already to 240s. Four minutes should be enough one might think. But as it turns out I still have the same issues. I will try AstroPrint next week. Also a new RC of OctoPrint came out yesterday. Maybe it contains already the necessary fixes? I am "still" on the stable branch...

Re: OctoPi, OctoPrint and MK2

Here is my list of "long running commands": G4, G28, G29, G30, G32, M80, M400, M226

Re: OctoPi, OctoPrint and MK2

Aaron

I think your M80 should be G80 (mesh probing rather than turn on PSU) and you should add M600 (filament change).

Peter

Re: OctoPi, OctoPrint and MK2

Wow Peter, (pjr) Your knowledge of CNC machine G codes and M codes is good. I have a crib sheet that I use too. You cannot help yourself Peter (pjr) 🙂 Over 2000 replies Peter (pjr) well done you. Do you live here on the forums Peter? And lurk?

I run Octoprint and OctopPi across all my 3D printers. I have 6 different printers. Its not Rocket science except if you have the Astro Pi Rapsberry Pi Hat lol 🙂 A project I have run.

I run a networked steerable Daylight and Night camera to monitor my printers. I never go to bed with a 3D printer running. Hence I am up late
sometimes 🙂

I own 10 Raspberry Pi's of various models.

Re: OctoPi, OctoPrint and MK2

Would you mind sharing all the changes you made to the Octoprint config files for the MK2?

Re: OctoPi, OctoPrint and MK2

X2 - can you please post. I am about to set this up and need to know what to change if possible.

Re: OctoPi, OctoPrint and MK2

There really is very little to change; OctoPrint is simply a tool which feeds the GCode to the printer.

You just have to define a few basic parameters (USB port, baud rate etc) upload the GCode file and print.

Peter

Re: OctoPi, OctoPrint and MK2

It was mentioned that some of the GCodes for the MK2 (mesh level?) will time out on OctoPrint. So just need to modify one file (config.yaml) using SSH, correct?

Re: OctoPi, OctoPrint and MK2

No; simply go to settings/serial connection/advanced settings and add them to the list of "long running commands":

M600, G4, G28, G29, G30, G32, M400, M226, G80

You could also increase the comms & connection timeout values, should you so desire...

Peter