File upload Prusa -> OctoPrint -> don't connect

[Herbert-Testmann]

I upload a file from Prusa Slicer to Octoprint.
The file is in file list in octoprint.
Octoprint don't connect to printer.

If the printer is already connected and I do in Prusa "upload and print" then the print starts.
I don't know if this information is helpful.

(is it possible to talk here in german?)

[Maxinger15]

Hi, ja wir können gerne deutsch reden.
Falls du das Problem noch hast lade mal die Octoprint Logdatei hoch, nachdem das drucken nicht geklappt hat.
Ich wüsste auf anhieb nicht woran es liegen könnte.

[SebastianOsinski]

Hi! I would like to follow up on this issue as I seem to have the same problem. I have both Connect & Print and PSU Control installed. When I upload the file through Prusa Slicer, printer gets turned on, but there is no connection made to the printer. The print does not start of course. It only starts if I click Connect in OctoPrint within 2 minutes of uploading.

Here is my log:

2023-11-26 19:31:58,532 - octoprint.plugins.dashboard - INFO - GcodePreProcessor started processing.
2023-11-26 19:31:59,006 - octoprint.filemanager.analysis - INFO - Starting analysis of local:Christmas+Present+Bow+v3+-+Stronger+Peg_0.4n_0.2mm_PLA_MINIIS_21m.gcode
2023-11-26 19:31:59,026 - octoprint.plugins.connectandprint - INFO - Uploaded file to print detected, connecting and printing...
2023-11-26 19:31:59,037 - octoprint.plugins.connectandprint - DEBUG - PSU-Status: False
2023-11-26 19:31:59,038 - octoprint.plugins.connectandprint - DEBUG - Trying to turn PSU on
2023-11-26 19:31:59,038 - octoprint.plugins.psucontrol - INFO - Switching PSU On
2023-11-26 19:31:59,839 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2023-11-26 19:31:59,859 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 0 port/baudrate candidates: 
2023-11-26 19:31:59,859 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Error"
2023-11-26 19:31:59,867 - octoprint.util.comm - INFO - Changing monitoring state from "Error" to "Offline after error"
2023-11-26 19:32:00,020 - octoprint.filemanager.analysis - INFO - Analysis of entry local:Christmas+Present+Bow+v3+-+Stronger+Peg_0.4n_0.2mm_PLA_MINIIS_21m.gcode finished, needed 1.01s
2023-11-26 19:32:00,310 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2023-11-26 19:32:00,313 - octoprint.plugins.connectandprint - INFO - Waiting for printer to connect...
2023-11-26 19:32:00,332 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 0 port/baudrate candidates: 
2023-11-26 19:32:00,333 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Error"
2023-11-26 19:32:00,337 - octoprint.util.comm - INFO - Changing monitoring state from "Error" to "Offline after error"
2023-11-26 19:32:09,315 - octoprint.server - INFO - Serial port list was updated, refreshing the port list in the frontend

Here is my PSU Control config:

The printer in question is Prusa Mini

[Maxinger15]

@SebastianOsinski according to your logs it looks like my plugin does what it is supposed to do. The connection fail is a error from Octoprint and there is nothing really I can do because I just call the function octoprint provides.

I have the same workflow (PrusaSlicer -> Octoprint -> Prusa Mini) and it works fine (with Firmware 5.1.0-alpha2 and 5.1.0 of the Prusa Mini)

[SebastianOsinski]

Thank you for such quick response! So I guess the problem might be with my configuration. Could you share how your PSU Control is configured or other settings which might influence the serial connection?

This is how my Serial Connection config looks like (nothing special I guess)

[SebastianOsinski]

Ok, I found the issue 🤦. The problem was with PSU Control -> Power On Options -> Post On Delay setting. I had it set to 0 seconds. I increased it to 10s and now it connects correctly after powering on the printer.

[Maxinger15]

I´m glad you fixed it. @Herbert-Testmann can you try if it fixes the error for you?