RE: When will we have Octoprint support?
Axes
- X - 180mm/min
- Y - 180mm/min
- Z - 180mm/m
- E - 80mm/min
FWIW you're mixing units. PrusaSlicer lists maximum feedrates in mm/second - not 180mm/min. Have to multiply by 60 sec/min for the Octoprint expected units of mm/min.
That would make the info to feed into the Axes tab:
- X: 10800 mm/min
- Y: 10800 mm/min
- Z: 720 mm/min
- E: 4800 mm/min
Based on the maximum feedrates of 180, 180, 12, and 80 from the "Machine limits" menu under "Printer settings" in the latest PrusaSlicer.
RE: When will we have Octoprint support?
I also has some problems to connect my Prusa mini to Octopi (R'pi 3B+)
Tried several cables and all gave errors in the dmesg like these:
[ 199.744702] usb 1-1.1.3: new full-speed USB device number 9 using dwc_otg
[ 199.890670] usb 1-1.1.3: New USB device found, idVendor=2c99, idProduct=000c, bcdDevice= 2.00
[ 199.890686] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 199.890695] usb 1-1.1.3: Product: Original Prusa MINI
[ 199.890704] usb 1-1.1.3: Manufacturer: Prusa Research (prusa3d.com)
[ 199.890714] usb 1-1.1.3: SerialNumber: CZPX1620X017XC06512
[ 199.942453] cdc_acm 1-1.1.3:1.0: ttyACM0: USB ACM device
[ 199.944889] usbcore: registered new interface driver cdc_acm
[ 199.944902] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 224.366714] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 224.367553] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 224.368382] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 238.411856] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 3
[ 242.433359] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 5
[ 247.471827] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 0
[ 249.484607] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 1
[ 250.489355] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 0
[ 252.504239] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 6
[ 257.460842] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 264.303266] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 264.307900] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 264.311919] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 304.389780] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 311.262523] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 311.265021] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 311.272105] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 351.345074] cdc_acm 1-1.1.3:1.0: failed to set dtr/rts
[ 408.343707] usb 1-1.1.3: USB disconnect, device number 9
But as I did see something, I searched through all my USB cables and finally found one that had a longer tip.
This one has not jet given any disconnect message and also Octopi immediately found the printer.
So maybe the printed enclosure does have some margins which may work for some and don't work for others.
Please try using an USB cable with a longer tip.
RE: When will we have Octoprint support?
I flashed my Mini with 4.1.0 and it now has the Disconnect feature (which is a great feature). Maybe I missed it, but is there a a Reconnect feature? It seems like a big miss to add Disconnect without the foresite to include Reconnect in the latest update. I'm having to resort to rebooting my machine.
RE: When will we have Octoprint support?
@naturalhoosier
Before, even disconnected from the Octoprint interface didn’t change the menu on the Mini’s display back to the normal interface. You had to reboot the printer to get back. Now you can disconnect from the printer to return to the normal menus. If you want to reconnect you can do it from the Octoprint interface like before.
I believe it might be intentional to not allow the use of the Mini to connect to Octoprint but not sure.
RE: When will we have Octoprint support?
@bradmcgonigle
Appreciated. The Octoprint web-based interface wouldn't reconnect, but it worked like a charm from the Octopod app. I'm a newbie and learning! 🙂
RE: When will we have Octoprint support?
Can someone answer this for me, I don't have a raspberry pi to test it. If I connected via the micro USB slot to the Mini, does that also power the pi? Or can I power the pi form the spare USB slot on the Mini?
aka do I need to buy a power cable for the pi?
RE: When will we have Octoprint support?
@malcmcm
A separate power cable is the way to go. The PI needs 2.5-3 amp and the mini has a 5 amp power supply I believe. So that said, you would be under powered.
RE: When will we have Octoprint support?
@malcmcm
I doubt it. I think it's a USB 2 capable device, which I think only puts out 500 mA. The Raspberry Pi's all need at least 700 mA, and the rPI 4 much more. https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md#:~:text=hardware%20%3E%20raspberrypi%20%3E%20power-,Power%20Supply,uses%20a%20USB%2DC%20connector.
RE: When will we have Octoprint support?
Ok thanks, I'll buy the power cable too, cheers.
RE: When will we have Octoprint support?
@joo
I pasted your /dev info in as an additional serial port but it still only shows AUTO in the pull down. Any ideas?
RE: When will we have Octoprint support?
My only question is, why have an ethernet port on the prusa mini and then have to use a PI with micro usb to talk to octoprint. Seems like the prusa mini should have the ability to install octoprint or some form of it so we can just use the built in ethernet.
Prusa Connect
The built in ethernet is for Prusa Connect:
https://help.prusa3d.com/en/article/prusa-connect-local-mini_133279/
I think it's a little too hopeful to expect a 3D printer to have the power to support Octoprint. It needs a Pi 3 at least.