Re: OctoPrint on MK3?
Perhaps the printer firmware doesn't yet have the Pi connectivity part coded?
Yes, that's what I'm wondering too but there's nothing in any of the documents to suggest it doesn't work. I've sent a message to Prusa asking for clarification.
Re: OctoPrint on MK3?
If the Prusa firmware is like Marlin you don't need any special "code" to get it working, you only have to tell the firmware on witch uart / serialport the octopi / host is connected... probably in the config file...
Re: OctoPrint on MK3?
If the Prusa firmware is like Marlin you don't need any special "code" to get it working, you only have to tell the firmware on witch uart / serialport the octopi / host is connected... probably in the config file...
Looks like the current version of the firmware is actually able to communicate on either serial port without needing to reconfigure.
Re: OctoPrint on MK3?
Hey guys. First time posting here.
I'm having a strange issue that I can't figure out. I can't get my prints to go using OctoPrint on 3.1.1 b122 RC1.
I can connect to OctoPrint and connect to the printer, upload the gcode directly using my browser and using Slic3r, set the temperature and move the extruder around through the browser.
However, when I start a print using OctoPrint, my MK3 will go through the bed levelling process, draw the horizontal line at 0, -3, then stop. The temperature stays at print temperature, but I can't get it to do anything beyond that. If I take the same gcode file and put it on the SD card, it will print no problem.
I've tried this with 2 Pi Zero Ws and 2 Pi 3s and get the same result. I would even load up 2 new installs of OctoPrint and put 1 on my MK2S (3.1.0) and 1 on my MK3. The MK2S would print just fine, the MK3 would stop after it draws the line. I would then reinstall OctoPi on both and switch the Pis between the printers and same thing.
Any help is appreciated. Thanks guys.
Re: OctoPrint on MK3?
If you look in the octoprint console, does it look like octoprint is sending any commands?
Re: OctoPrint on MK3?
It seems to get hung up on one part. I would guess it's the checksum part, but I don't know how to fix it.
Send: N24 M900 K{if printer_preset=="Original Prusa i3 MK2 MultiMaterial"}200{elsif printer_preset=="Original Prusa i3 MK2 MM Single Mode"}200{else}30{endif}*10
Recv: Error:No Line Number with checksum, Last Line: 23
Recv: Error:Line Number is not Last Line Number+1, Last Line: 23
Recv: Resend: 24
Recv: ok
I'm using drivers 2.0.0 if that makes a difference.
It looks like if I slice using the MK3 profile, I get this line in the gcode
M900 K{if printer_preset=="Original Prusa i3 MK2 MultiMaterial"}200{elsif printer_preset=="Original Prusa i3 MK2 MM Single Mode"}200{else}30{endif}; Filament gcode
If I use the MK2 profile to slice, that line is simply
G92 E0.0
M900 K30 ; Filament gcode
If I replace that line in the MK3 gcode then upload it to Octoprint, then it prints fine. I guess this would be an issue to do with Slic3r rather than octoprint.
Re: OctoPrint on MK3?
If the Prusa firmware is like Marlin you don't need any special "code" to get it working, you only have to tell the firmware on witch uart / serialport the octopi / host is connected... probably in the config file...
Looks like the current version of the firmware is actually able to communicate on either serial port without needing to reconfigure.
Thanks. Yes, it looks like there's a new option which will show up in settings to enable the second serial port. However, that code is not yet in the current release. It was added to the Github repository on Dec 7. (Latest published build is B122 which is dated Dec 12, but is actually from Dec 5). I guess I need to be patient! 🙂
In the meanwhile I got Repetier Server working on an external Raspberry Pi connected through the USB port in the normal way. (OctoPrint still had problems, even when run externally. Looks like yulong.1 in the post immediately above this one found the same problem.)
Re: OctoPrint on MK3?
I'm trying to figure out this issue as well. Sliced gcode from Slic3r printed using octoprint USB printing does the bed leveling, the purge line, and stops. The same exact file printed from the SD card works fine. Could be worth a try on your setup to see if we both observe the same. Similarly, I sliced the same model with simplify3D using a profile I was trying to work up for the MK3 and saw different bad behavior during USB printing but normal printing via SD card with the same file.
Re: OctoPrint on MK3?
I'm trying to figure out this issue as well. Sliced gcode from Slic3r printed using octoprint USB printing does the bed leveling, the purge line, and stops. The same exact file printed from the SD card works fine. Could be worth a try on your setup to see if we both observe the same. Similarly, I sliced the same model with simplify3D using a profile I was trying to work up for the MK3 and saw different bad behavior during USB printing but normal printing via SD card with the same file.
Yes, exact same issue with OctoPrint, stops after purge line. I think that yulong.1 has it right, it's the if/else statement in the Gcode which is causing the problem. FWIW Repetier-Server has no problem with it.
I believe this linear advance code in the Slic3r MK3 Filament Settings
is irrelevant for the MK3, as it only refers to the MK2 so will always fail and can be replaced with:
Re: OctoPrint on MK3?
I'm trying to figure out this issue as well. Sliced gcode from Slic3r printed using octoprint USB printing does the bed leveling, the purge line, and stops. The same exact file printed from the SD card works fine. Could be worth a try on your setup to see if we both observe the same. Similarly, I sliced the same model with simplify3D using a profile I was trying to work up for the MK3 and saw different bad behavior during USB printing but normal printing via SD card with the same file.
Yes, exact same issue with OctoPrint, stops after purge line. I think that yulong.1 has it right, it's the if/else statement in the Gcode which is causing the problem. FWIW Repetier-Server has no problem with it.
I believe this code in the Slic3r MK3 Filament Settings
is irrelevant for the MK3, as it only refers to the MK2 so will always fail and can be replaced with:
Ok, I can confirm in my case, replacing the statement in the line with just the following fixes the problem when printing via USB on octoprint.
M900 K30; Filament gcode
Edit: confirmed this has nothing to do with what I was seeing while trying to set up an S3D profile. Will start another thread on that if necessary, but it doesn't like changing the cooling fan speed, even when using the same gcode as slic3r does.
Re: OctoPrint on MK3?
M900 - thats the linear advance command, right?
It looks like slic3r isn't parsing the if-statement-macro correctly. Presumably it sends M900 K200 if you are using a MK2 multimaterial and M900 K30 otherwise? Is the K parameter something to do with bowden tubes?
Re: OctoPrint on MK3?
That fixed it for me. Thanks guys!
Re: OctoPrint on MK3?
M900 - thats the linear advance command, right?
It looks like slic3r isn't parsing the if-statement-macro correctly. Presumably it sends M900 K200 if you are using a MK2 multimaterial and M900 K30 otherwise? Is the K parameter something to do with bowden tubes?
Right to both. Conditional GCode is a brand new Slic3r feature. I suspect it's not yet in the customized Prusa branch of the code.
Re: OctoPrint on MK3?
Currently is not possible connect and control MK3 with Rpi Zero through UART (GPIO) 😥 Tested with Repetier Server and Octoprint. Booth can connect to the printer with UART, but there is no communication between printer and Rpi. Raised ticket on OctoPrint and Prusa git. Waiting for response...
Re: OctoPrint on MK3?
If you're printing from octoprint I recommend keeping the filament sensor disabled for now. Seems like Octoprint is not able to deal with the M600 which is sent when it triggers.
Re: OctoPrint on MK3?
Regarding the ability to interface octoprint via the serial port on the einsy headers: it appears PR297 was only recently committed into the firmware which appears to enable the extra serial port simultaneously. This will only be present in firmware 3.1.1 build 130 or later which is not yet released. You would have to build it yourself, and since it still looks like a lot of things are in flux it might be better to wait than to live on the edge for this one.
Re: OctoPrint on MK3?
Regarding the ability to interface octoprint via the serial port on the einsy headers: it appears PR297 was only recently committed into the firmware which appears to enable the extra serial port simultaneously. This will only be present in firmware 3.1.1 build 130 or later which is not yet released. You would have to build it yourself, and since it still looks like a lot of things are in flux it might be better to wait than to live on the edge for this one.
Yes, I'd come to the same conclusion, so I tried building the current code from GitHub. It worked, and the internal Pi Zero W is now working as it should. 🙂 However, I 100% agree with you that this is not necessarily the smartest/safest thing to do as lots of things are changing right now. I'll likely revert to the current release.
Re: OctoPrint on MK3?
Did you reconfigured you Rpi before (disabling bluetooth or swaping port)? Or you are connecting now to /dev/ttyS0?
Re: OctoPrint on MK3?
I had swapped ports, but I reflashed the Pi so it's back to defaults and connecting through /dev/ttyS0
Re: OctoPrint on MK3?
Thx 😉 ttyS0 is not good option, better to swap or disable bluetooth completly 😉