[Gelöst] Octoprint with FW 5.1.0 alpha 2  

RE: Octoprint with FW 5.1.0 alpha 2

I just installed 5.1.0 alpha 2 on my Mini today, and restarted octoprint, and it connected and worked right away.  I have the latest (1.9.3) version of octoprint, so maybe that has something to do with it.  I didn't know it wasn't supposed to work until I saw this post.  I can help with details if you need, but I don't think anything on my end is special.  Everything is pretty stock and octoprint doesn't have any plugins installed that I would think would help it work.

RE: Octoprint with FW 5.1.0 alpha 2

You are absolutely right - maybe it’s the alpha 2 but it just works.  Thanks for posting I wouldn’t have bothered trying again if you didn’t till I saw something in the release notes 

back to hassle free uploads yay!!!

RE: Octoprint with FW 5.1.0 alpha 2

Nope spoke too soon - I got a print to start which I cancelled (was surprised it worked and don’t want the print) 

but now Octto will connect - I send a print and it changes the status to starting and that’s it - doesn’t start heating 

I’ve tried rebooting mini but same

RE: Octoprint with FW 5.1.0 alpha 2

I have seen it take a minute or two to start heating with octoprint on this firmware.  I haven't figured out why this happens yet, but so far it has always eventually started for me.

RE: Octoprint with FW 5.1.0 alpha 2

Here's what I mean.  There was roughly a minute between when it completed uploading from prusa slicer (behind on right) to when it actually started changing temps in octoprint (in front on left).    I've seen it take as long as 3 mins so far.

RE: Octoprint with FW 5.1.0 alpha 2

Interesting - I did notice the delay between sending and starting the job but was not a massive delay - thats the bit Im kinda basing it on is the temp changes - I may not have waited 3 minutes.  Im running Octoprint on an i5 NUC so its been the quickest of my fleet of octoprints for file transfers but perhaps this is different.  What are your connection settings?

I will try something else and leave it a good while to test some more.

Is it youve just placed your screen in a neat way or are you running octoprint inside of prusaslicer?

RE: Octoprint with FW 5.1.0 alpha 2

No luck - I really dont know what the difference from the first time it worked to now: 

Im goping to start playing with settings

I get this log

Trying port /dev/ttyACM0, baudrate 115200
Connecting to port /dev/ttyACM0, baudrate 115200
Handshake attempt #1 with timeout 12.0s
Connected to: Serial<id=0x7f45f47361d0, open="True">(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=12.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Recv: echo:Unknown command: "echo: G21 "
Recv: ok
Changing monitoring state from "Detecting serial connection" to "Operational"
Recv: ok
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Changing monitoring state from "Operational" to "Starting"
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N2 M21*18
Recv: FIRMWARE_NAME:Prusa-Firmware-Buddy 5.1.0-alpha2+13126 (Github) SOURCE_CODE_URL: https://github.com/prusa3d/Prusa-Firmware-Buddy PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa-mini EXTRUDER_COUNT:1 UUIok
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Starting" to "Offline after error"
Connection closed, closing down monitor</id=0x7f45f47361d0,>