OctoPrint issues and tips  

Re: OctoPrint issues and tips

I was initially pretty jazzed by the idea of moving from outboard Pi to onboard Pi Zero W via the Einsy's headers. Then I realized my USB Logitech HD Cam wasn't going to make that journey as well and held off. I'm still using my RPi 3 from my MK2/S on the new MK3 via USB until I finish weighing the pros and cons of deeper integration. The RPi3 performance is certainly snappier than I got with the RPi2 (which is a closer match to the Pi Zero resource-wise).

I would say that if the Pi Zero soldered to the Einsy opened the door to faster access to things like the MK3's SD card, I'd be more inclined (it's seemingly bound by the same serial over USB baud rates that are fine for driving the printer realtime but suck for large data exchanges). But even that has less appeal to me once OctoPrint starts to have intelligent responses to MK3-unique features (which I assume is coming from the partnership that seems to be growing there).

On a side note, I've been a Patreon contributor to the OctoPrint author for a good long while now and adore her work. Seeing these two products I use possibly more tightly coupled and the chance that it provides her yet more financial support for her endeavors (even if just by attracting more supporters coming to 3D printing via Prusa printers) would be well deserved. Always like seeing people who contribute so much freely to the open source community getting support from said community in a meaningful way.

Some last side notes since I'm already somewhat off topic to the thread: if you're a Slack user, the OctoSlack plug-in is super handy. I get great status updates and still images from my prints pushed to my devices via Slack. Also have a TPLink driver for powering my printer on and off remotely via a smart plug - something I like as an option in an emergency, plus insights in the electrical draw and, by extension, cost of running the printer. These being functions on an outboard Pi also gives me some confidence they will function even if the serial connectivity to the printer is offline. I assume the Einsy-mounted Pi would still be accessible as long as it had power regardless of the mental state of the printer firmware... but also uncharted territory for me in my pro/con weighing.

Re: OctoPrint issues and tips

Hello everyone,

Just wanted to post my findings. I got the MK3 Kit (with RC5 b150 out of the box).
Printed some of the model from the attached SD card. All of them except Adalinda printed ok. Adalinda printed fine in stealth mode - in normal mode I've got layer shifting.

After some hardware/software setup I'm now runing OctoPrint on Odroid XU4 and my MK3 is connected to one of the USB3.0 ports. I'm getting crashes from time to time - sometimes they end up fine but sometimes it's layer shifting (g-codes generated using unchanged Slic3r profiles - since I've just read about the changes that need to be made).

Re: OctoPrint issues and tips

Please read .... NO Kit. I need StepbyStep for the assembled MK3 !!
...not using the accessory port... what do you mean by that ? How should I connect the PI? He is still connected via the external USB-B port?

octoprint has nothing to do with kit vs pre-assembled.

if you're using the usb port, the setup is incredibly simple.
if you're using the accessory/einsy port (whatever you want to call it) then good luck, seems like a lot of work for basically no benefit.

Re: OctoPrint issues and tips

...seems like a lot of work for basically no benefit.

What do you mean ? Are there no benefits of using the internal port instead of USB ?

Re: OctoPrint issues and tips

Biggest advantage, it gets its power from the EInsy board, Takes less space, is better organised. Biggest disadvantage, tbh a Pi Zero is underpowered and struggles when you want it to record video/timelapse . I have both a Pi3b and a Pi zero W, so I will test both. Runing another make of printer at the moment, and quite happy with the Pi3 based control

Re: OctoPrint issues and tips

Biggest advantage, it gets its power from the EInsy board, Takes less space, is better organised. Biggest disadvantage, tbh a Pi Zero is underpowered and struggles when you want it to record video/timelapse . I have both a Pi3b and a Pi zero W, so I will test both. Runing another make of printer at the moment, and quite happy with the Pi3 based control

Much less power that I know of. What are the advantages ? Is the transfer rate even faster than via USB2serial ? That was the only thing that I was hoping for. If not than I'm staying with USB.

Re: OctoPrint issues and tips

Biggest advantage, it gets its power from the EInsy board, Takes less space, is better organised. Biggest disadvantage, tbh a Pi Zero is underpowered and struggles when you want it to record video/timelapse . I have both a Pi3b and a Pi zero W, so I will test both. Runing another make of printer at the moment, and quite happy with the Pi3 based control

Much less power that I know of. What are the advantages ? Is the transfer rate even faster than via USB2serial ? That was the only thing that I was hoping for. If not than I'm staying with USB.

apparently its not, but usb speed wasn't even the issue in the first place. "better organized" is a mayyybe, since you have to print a new enclosure for header access, or run a jumper.

I have a pi3 case that bolts into the factory mounting holes directly above the einsy case, so best of both worlds. better organized and more powerful.

Re: OctoPrint issues and tips

I'll be making an enclosure with a 10" touchscreen and electronics bay under the printer so the organization isn't a thing for me. Just waiting for the MMU for my printer to start to design the enclosure.

Re: OctoPrint issues and tips

Just wanted to report my experience. Not too long ago I received my MK3 and have been printing via SD for a while now on Firmware RC5. Pretty good success on small short prints, but long prints I seem to always get a layer shift of some kind and reported collisions in the logs. The prints from SD always finish though. I decided to try my hand at OctoPrint and after reading the concerns of the PiZero and the limited resources I ended up implementing a Pi3B instead. I initially started printing from the Pi using the USB and was able to successfully do some short prints from the Pi. I then decided to build a cable to the accessory port on the einsey to some day use the maybe coming features that will be used with GPIO 22, and 23. I followed all the instructions for disabling the BT and etc. and am able to connect through Pi UART0 but I have to say it is anything but reliable. I failed 100% of the prints from the Pi to the MK3 accessory port. I tried all the reported troubleshooting but to no avail. I then just tried to use the Pi to start a print directly from the SD and monitor its success via the serial connection to the Einsey accessory port. The problem with this option is that when the serial connection has problems it halts the print until the serial is connected again and successful even though the print is coming directly from the SD. I also noticed that by watching the terminal in OctoPrint that when the corruption happens the log reports a disconnect and the MK3s display has corrupted characters all over the display. I am now going to try some longer prints on the Pi3B USB connection and see if it is more reliable. So far it sounds like it is and that the Pi Port on the Einsey sucks....

Re: OctoPrint issues and tips

Hello, any improvements / deteriorations with the new FW 3.1.1?

Re: OctoPrint issues and tips

After using Octoprint successfully for months, I have recently been experiencing random disconnects from my MK2. Today I noticed that the hot end tether pushes on the USB cable when during x axis movements. I suspect that this may be causing the USB to disconnect.

I ordered a USB cable with a right angle connector that should keep the cable clear of the MK2 tether. Will report again once that part arrives.

Re: OctoPrint issues and tips

Last night I upgraded to the latest fw release and re-attempted to use the RPI-Port from Einsey to OctoPrint. I think the overall reliability may be improved. One thing I did notice is that in the new FW the filament sensor still false triggers on my Black PETG. It false triggered while using Octoprint to monitor a SD originated print and when the filament was restarted the print failed to print a full parameter around the print. This is the same problem I saw when the serial connection would randomly disconnect to the Pi. It seems that if you use OctoPrint in any way to either monitor a print from SD or print directly from OctoPrint that if there is any hiccup in the serial connection including a filament sensor event the print will fail in some way. I guess this limitation being known it is what it is and the new features of MK3 will not be available while using OctoPrint.

Re: OctoPrint issues and tips

Hi,
I just installed Octoprint (The Prusa version) on a RPi Zero and would like to connect it to my MK3.

Some questions:
1) Is there any functionality/performance/reliability difference between connecting thru USB or the Serial pins?
I know that USB requires an external Power Supply and the 2 GPIO (Power loss? and filament detection?) won't be available but for just remote monitoring doesn't seems a big difference.

2) Kind of same question between printing from SD card or directly from Octoprint. Any functionality/performance/reliability difference?

3) Did some preliminary tests with a camera connected to RPi Z and the system seems to crawl... Any one using a RPI1/2/3/3B/etc?

Thanks!
Jose

Re: OctoPrint issues and tips

i have the pi0w running. and it works perfect. (new FW and the new prusa iso).
No Problems at all. (ok took a while to find out that the rpi don't support chanel 12/13 Wlan 🙄 because it did not connect to router..)

now i would like to connect a logitech 720 Webcam. did anyone try this?

I printed the case with the door for rpi. but there ist litte to no space to get a usb plug in there.
what cable and plugs did you use?

I think i would solder a smal micro usb plug to the webcam, but i haven't found a cable with a smal plug yet.

Re: OctoPrint issues and tips

. (new FW and the new prusa iso).

Is there a new Octopi image from Prusa?

Re: OctoPrint issues and tips

After upgrading to the latest firmware I was able to successfully monitor and print from Pi3B using the USB. I decided to make another attempt to run my Pi3B to the accessory port on the back of the Einsey to see if the new firmware made this more reliable to the Pi3B UART0 interface. I again was able to establish an initial connection and did start an SD Print. It was about 1 min in and then it crashed just like before but maybe even sooner than before on RC5.

Below is the last report of disconnect from the serial corrupted connection. Accessory Port still seems to be unreliable.

Recv: echo:Unknown command: ""(2)
Recv: ok
Send: M105
Recv: ok T:229.4 /230.0 B:85.1 /85.0 T0:229.4 /230.0 @:42 B@:27 P:35.2 A:31.4
Send: M105
Recv: ok T:229.5 /230.0 B:85.0 /85.0 T0:229.5 /230.0 @:40 B@:36 P:34.9 A:31.5
Send: M105
Recv: ok T:230.2 /230.0 B:85.1 /85.0 T0:230.2 /230.0 @:29 B@:29 P:34.9 A:31.5
Send: M105
Recv: ok T:230.3 /230.0 B:85.2 /85.0 T0:230.3 /230.0 @:29 B@:18 P:34.8 A:31.3
Send: M105
Recv: ok T:230.7 /230.0 B:85.1 /85.0 T0:230.7 /230.0 @:23 B@:38 P:34.9 A:31.2
Send: M105
Recv: ok T:230.5 /230.0 B:85.1 /85.0 T0:230.5 /230.0 @:26 B@:48 P:34.9 A:31.5
Send: M105
Recv: ok T:230.5 /230.0 B:85.1 /85.0 T0:230.5 /230.0 @:27 B@:38 P:35.0 A:31.6
Send: M105
Recv: echo:SD card ok
Recv: ok T:229.9 /230.0 B:85.1 /85.0 T0:229.9 /230.0 @:36 B@:47 P:35.0 A:31.6
Send: M105
Recv: ok T:229.3 /230.0 B:85.1 /85.0 T0:229.3 /230.0 @:46 B@:46 P:34.9 A:31.0
Send: M105
Recv: ok T:229.1 /230.0 B:85.0 /85.0 T0:229.1 /230.0 @:47 B@:60 P:35.0 A:31.5
Send: M105
Recv: ok T:229.7 /230.0 B:84.9 /85.0 T0:229.7 /230.0 @:37 B@:68 P:35.0 A:31.5
Send: M105
Recv: ok T:230.3 /230.0 B:84.9 /85.0 T0:230.3 /230.0 @:27 B@:62 P:35.1 A:31.7
Send: M105
Recv: ok T:230.2 /230.0 B:84.9 /85.0 T0:230.2 /230.0 @:29 B@:73 P:35.1 A:31.4
Send: M105
Recv: ok T:230.1 /230.0 B:84.9 /85.0 T0:230.1 /230.0 @:33 B@:68 P:35.1 A:31.6
Send: M105
Recv: ok T:230.6 /230.0 B:84.8 /85.0 T0:230.6 /230.0 @:24 B@:78 P:35.1 A:31.6
Send: M20
Recv: Begin file list
Recv: End file list
Recv: ok
Send: M105
Recv: ok T:230.2 /230.0 B:84.9 /85.0 T0:230.2 /230.0 @:31 B@:56 P:35.1 A:31.1
Send: M105
Recv: ok T:230.4 /230.0 B:84.9 /85.0 T0:230.4 /230.0 @:29 B@:52 P:35.1 A:31.8
Send: M105
Recv: ok T:230.1 /230.0 B:85.0 /85.0 T0:230.1 /230.0 @:33 B@:47 P:35.1 A:31.2
Changing monitoring state from 'Operational' to 'Offline'
Connecting to: /dev/ttyAMA0
Changing monitoring state from 'Offline' to 'Opening serial port'
Connected to: Serial<id=0x6dd2b5f0, open=True>(port='/dev/ttyAMA0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection
Changing monitoring state from 'Opening serial port' to 'Detecting baudrate'
Trying baudrate: 115200
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from 'Detecting baudrate' to 'Operational'
Send: N0 M110 N0*125
Connection closed, closing down monitor
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin V1.0.2; Sprinter/grbl mashup for gen6 FIRMWARE_URL: https://github.com/prusa3d/Prusa-i3-Plus/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa i3 MK3 EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
Recv: ok
Send: M21
Recv: echo:SD card ok
Recv: ok
Send: M20
Recv: Begin file list
Recv: End file list
Recv: ok
Send: M105
Recv: ok T:229.6 /230.0 B:85.1 /85.0 T0:229.6 /230.0 @:39 B@:32 P:35.3 A:31.5
Send: M20
Recv: Begin file list
Recv: End file list
Recv: ok
Send: M105
Recv: ok T:230.6 /230.0 B:85.1 /85.0 T0:230.6 /230.0 @:24 B@:44 P:35.3 A:31.8
Send: M105
Recv: ok T:231.0 /230.0 B:85.0 /85.0 T0:231.0 /230.0 @:18 B@:51 P:35.3 A:31.6
Send: M105
Recv: ok T:230.7 /230.0 B:85.0 /85.0 T0:230.7 /230.0 @:23 B@:53 P:35.3 A:31.2
Send: M105
Recv: echo:SD card ok
Recv: ok T:230.2 /230.0 B:85.0 /85.0 T0:230.2 /230.0 @:32 B@:63 P:35.4 A:31.8
Send: M105
Recv: ok T:230.0 /230.0 B:84.9 /85.0 T0:230.0 /230.0 @:34 B@:70 P:35.4 A:31.6
Send: M105
Recv: ok T:229.9 /230.0 B:85.0 /85.0 T0:229.9 /230.0 @:34 B@:51 P:35.3 A:31.5
Send: M105
Recv: ok T:229.8 /230.0 B:85.0 /85.0 T0:229.8 /230.0 @:36 B@:51 P:35.4 A:31.7

Re: OctoPrint issues and tips

After some hardware/software setup I'm now runing OctoPrint on Odroid XU4 and my MK3 is connected to one of the USB3.0 ports. I'm getting crashes from time to time - sometimes they end up fine but sometimes it's layer shifting (g-codes generated using unchanged Slic3r profiles - since I've just read about the changes that need to be made).

That's interesting, because I've still got an Odroid X2+ lying around and I thought of turning it into an OctoPrint server. What Linux distro are you using? I was thinking of running ArchLinux on it, as there's an OctoPrint package in their repository as well.

Re: OctoPrint issues and tips

. (new FW and the new prusa iso).

Is there a new Octopi image from Prusa?

look here: https://shop.prusa3d.com/forum/original-prusa-i3-mk3-f30/octoprint-for-original-prusa-i3-mk3-t14156.html

Re: OctoPrint issues and tips

look here: https://shop.prusa3d.com/forum/original-prusa-i3-mk3-f30/octoprint-for-original-prusa-i3-mk3-t14156.html

Cheers.. Found it in the end (Now V2).. Direct link incase it helps anyone else

https://www.prusa3d.com/download-prusaprint#_ga=2.231223455.1650856160.1517823596-749811373.1499169512

Re: OctoPrint issues and tips

After some hardware/software setup I'm now runing OctoPrint on Odroid XU4 and my MK3 is connected to one of the USB3.0 ports. I'm getting crashes from time to time - sometimes they end up fine but sometimes it's layer shifting (g-codes generated using unchanged Slic3r profiles - since I've just read about the changes that need to be made).

That's interesting, because I've still got an Odroid X2+ lying around and I thought of turning it into an OctoPrint server. What Linux distro are you using? I was thinking of running ArchLinux on it, as there's an OctoPrint package in their repository as well.

Ubuntu MATE and installed OP with dependencies from command line (info on the manual install is on the OP wiki)