Re: OctoPrint issues and tips
1) When setting up OctoPrint should I just steal the printbed and speed settings from PrusaPrint?
2) Do I need a cura profile or can I just ignore that?
3) Is it worth using the Slic3r plugin and is there a guide on how to get it up and running somewhere?
Re: OctoPrint issues and tips
I'm curious as to what advantages/disadvantages there are between the Prusa fork of OctoPi vs the main Guysoft?
Re: OctoPrint issues and tips
Hey guys, I have a quick question, can I use your guide for Octoprint in Prusa i3 mk3 covering Raspberry Pi 0, while I bought Pi 3 B+ ? I am aware about that it needs external power to run, but would it be possible with this model - to power it by a Ethernet cable if I would have needed one for that?
https://manual.prusa3d.com/Guide/0.+Preparing+necessary+components/585?lang=en
ALSO,
I'm curious as to what advantages/disadvantages there are between the Prusa fork of OctoPi vs the main Guysoft?
Could you say some more, I never heard about any other software like Octoprint
Re: OctoPrint issues and tips
I'm curious as to what advantages/disadvantages there are between the Prusa fork of OctoPi vs the main Guysoft?
Could you say some more, I never heard about any other software like Octoprint
Both are called OctoPi -- Prusa 'forked' from GuySoft (made a custom version):
GuySoft: https://github.com/guysoft/OctoPi
Re: OctoPrint issues and tips
Hi Guys, Just setting up a new MK3. I have added a Pi Zero W. attached to the board as recommended. I can access the octopi web interface , but cannot connect to the printer. I have tried various baud rates. But no success. the pi port is turned on in the settings. I have tried 2 pi zeros.
Any help would be awesome thanks.
Also the ip address never comes up on the screen
Crash detection on
Filament sensor on
Firmware 3.2.1. 576
Thanks Matt
Re: OctoPrint issues and tips
@matt.o2: Did you do as described HERE?
BTW... guys, how do you "power off" your printers Raspberry onboard? Do you just turn power switch to "off" or do you "shutdown octoprint" via web page every time? Is it octoprint (or raspbian, for that matter) made such way that it allows shut down through power cut without longterm damage?
Re: OctoPrint issues and tips
Yeah I followed that post. The only thing I haven't tried is to do a build from an octopi image vs Prusa Build. But that doesn't really make sense why that should work over a custom version from Prusa.
Re: OctoPrint issues and tips
Protoncek,
Using OctoPrint you can shutdown OctoPrint (the service) and leave the RPi running or you can also shutdown the RPi completely.
If you want to shutdown the printer via OctoPrint you can use PSU Control or TP-Link-Smartplug plugins.
Quick advertisement: There is a new free and open source iOS app for controlling OctoPrint and the printer from any iOS device. App name is OctoPod. Link to App Store: https://itunes.apple.com/us/app/octopod-for-octoprint/id1412557625?mt=8 . Link to the repo in case you want to contribute code or ideas or requests: https://github.com/gdombiak/OctoPod
Re: OctoPrint issues and tips
Tried using the octopint image today and still the same result. I beginning to think in may be a faulty board as no one else are having this issue.
@matt.o2: Did you do as described HERE?
BTW... guys, how do you "power off" your printers Raspberry onboard? Do you just turn power switch to "off" or do you "shutdown octoprint" via web page every time? Is it octoprint (or raspbian, for that matter) made such way that it allows shut down through power cut without longterm damage?
Re: OctoPrint issues and tips
Protoncek,
Using OctoPrint you can shutdown OctoPrint (the service) and leave the RPi running or you can also shutdown the RPi completely.
True, but if i choose "power down system" via octoprint chromium still tells me every boot that it shut down improperly. Only option is to close chromium and shut down system through "legal" command. (i have installed desktop and 7 inch LCD on my octopi).
I think i'll just let RPI to run 24/7 and select blank as screensaver. (too bad that RPi supposely can't turn off LCD backlight...) Even so i have one "minor problem": each time i will power-on printer i'll have to manually "connect" to octopi 🙄
Re: OctoPrint issues and tips
each time i will power-on printer i'll have to manually "connect" to octopi 🙄
I added Octoprint to my i3 to make thigs easier. And now I have to click on it manually to connect? And perform a clean shutdown by logging into the interface again? No, thanks. I don't see any point why Prusa Research would give an option to connect Pi such a nice way and ruin the idea by adding another manual stuff you have to do every time you want to print something. No button to shutdown, no ATX PSU ...
todo:
- autoconnect on boot (probably delay start of Octoprint)
- touch the WebUI after Octoprint is loaded (using curl or wget) - the WebUI will be loaded immediately after that
I'll respond when I have it ready 😛
Re: OctoPrint issues and tips
todo:
- autoconnect on boot (probably delay start of Octoprint)
well, the problem is , at least in my case (since i don't have zero but Pi 3) since for now i have Pi always on, so when i turn off printer octopi looses connection and it doesn't try again. So when i power-on printer again connection is lost, so that's why i have to connect manually. So, i guess one option is for octoprint to constantly checks for connection...
When i've had zero onboard printer octopi connected automatically (at least most of the times), but it tool ages... shortage of processing power in zero, i guess. But, i changed with Pi3 because i want to have LCD connected (among others)...
Re: OctoPrint issues and tips
todo:
- autoconnect on boot (probably delay start of Octoprint)
well, the problem is , at least in my case (since i don't have zero but Pi 3) since for now i have Pi always on, so when i turn off printer octopi looses connection and it doesn't try again. So when i power-on printer again connection is lost, so that's why i have to connect manually. So, i guess one option is for octoprint to constantly checks for connection...
When i've had zero onboard printer octopi connected automatically (at least most of the times), but it tool ages... shortage of processing power in zero, i guess. But, i changed with Pi3 because i want to have LCD connected (among others)...
A cron job for checking the existence of a serial port and restarting octoprint could do it
Re: OctoPrint issues and tips
OK.... now all we need is someone with knowledge to write it... (i'm definitely not that much into linux...)
Re: OctoPrint issues and tips
Same problem here. 🙁 🙁 🙁 New MK3, new RPi zero W (original), I can access the web interface but i cannot connect printer. When I click the connect button, the state changes to "Connecting" for a while, than back to "Offline" (after about a minute). Could be an issue with latest firmware? Maybe someone from PrusaResearch can chech with latest version?
Additional info: PINs are long more than enaugh, RPi port enabled, default settings (prusaimage), firmware 3.3.1-845, Octoprint updated to latest stable.
Tried using the octopint image today and still the same result. I beginning to think in may be a faulty board as no one else are having this issue.
Re: OctoPrint issues and tips
OK.... now all we need is someone with knowledge to write it... (i'm definitely not that much into linux...)
I'll see what I can do
Re: OctoPrint issues and tips
jakub.g7, what is the printer doing when you click connect? Do you see the fan starting to spin? Any changed on the LCD? If nothing happens then I would check that you have the correct Baudrate. Use 115200.
Re: OctoPrint issues and tips
OK.... now all we need is someone with knowledge to write it... (i'm definitely not that much into linux...)
I wrote a small python script to:
- check if the serial port exists
- check if the printer is connected. in case not, it asks the API to connect and check for status for next 10 seconds. if connected, it will exit with a message that it was successful.
- touches the IP for Octoprint to reload everything so the webpage is loaded quickly even when first using.
all you need is to give the Pi a bit of time, this script runs every second minute. It's not professional work, but it's worth testing. Also the CPU usage is worth monitoring, we don't want this script to pause the printjob every two minutes. Like said, it works but it can have negative impact on the performance and there could be a better way to do it.
before saving the .py file please:
- change the API key in headers_post and headers_get
- check if the payload_connect part contains correct things, like serial port name and so on.
try this, put the code below into a file and save it in /home/pi/restartOP.py
then run crontab -e and put this line to the end as new line
*/2 * * * * python /home/pi/atest.py
script here:
import requests
import json
import sys
import os
import time
url = "http://127.0.0.1/api/connection"
url_refresh="http://127.0.0.1"
headers_post = {
"Content-Type":"application/json",
"X-Api-Key":"2333F4CD454B491BA409B20A1CDA6A06"
}
headers_get={
"X-Api-Key":"2333F4CD454B491BA409B20A1CDA6A06"
}
payload_connect = {
"port":"/dev/ttyAMA0",
"baudrate":115200,
"printerProfile":"_default",
"autoconnect":"true",
"save":"true",
"command":"connect"
}
#we'll assume the process is running
if os.path.exists("/dev/ttyAMA0"):
print("Serial port does exist")
r = requests.get(url , headers=headers_get)
current_state=(r.json()['current']['state'])
if current_state.lower()=="closed":
print("Connection is closed. Reconnecting ...")
r = requests.post(url, data=json.dumps(payload_connect), headers=headers_post)
for x in range(10):
rc=requests.get(url , headers=headers_get)
cstate=(rc.json()['current']['state']).lower()
print("Result: port is "+cstate)
if cstate=="operational":
break
time.sleep(1)
if cstate=="operational":
print "Connection established OK"
else:
print("Connection is already established, nothing to do")
else:
print("Serial port does not exist, exiting")
#now just touch the WebUI to get it loaded quicker when needed
print("Touching the WebUI")
rc=requests.get(url, headers=headers_get)
Re: OctoPrint issues and tips
I am having this recurring issue with Octoprint where it will mess up my MK3 calibration settings if I stop the print remotely. This has happened on 3 occasions within the last 8 or so prints through Octoprint.
I was watching the print remotely when I saw that the model got unstuck from the bed and started to make a mess, so I hit cancel on Octoprint and left the printer on to cool down. When I got home and cleaned up the excess plastic, I tried to start a different print and noticed that the printer was homing in to a location on the X-axis about 1/3 the length of the printer, nowhere near the origin. It then tries to do the mesh bed leveling and fails since the probe does not end up in the correct location. The only fix is to redo the XYZ calibration from the beginning and try to manually line up the PINDA probe so it lines up with the first calibration point.
I've noticed that if the print finishes perfectly then there is no issue. However, if I cancel the print remotely, the printer gets confused and sets its current location as the new home point, which messes up the calibration.
Has anyone else had this issue? Or does anyone know if there's a fix?
Regards
Re: OctoPrint issues and tips
Printer does nothing. No change at all. I double checked the soldering and everything looks fine, but I am unable to connect the printer. Baudrate is correct (115200). I have another printer with RPi 3 connected via USB and it works also fine with this printer. However RPi Zero via serial pins is not connecting. I may have to buy another RPi Zero and check if this one is not defective.
jakub.g7, what is the printer doing when you click connect? Do you see the fan starting to spin? Any changed on the LCD? If nothing happens then I would check that you have the correct Baudrate. Use 115200.