I'm not sure if this is a problem with Octoprint or Marlin 2.x, but as the problem didn't occur with the original firmware of my Sapphire Pro, I suppose asking here is a reasonable start.
The problem is that the printer never signalizes to the host when I start printing from SD card on the touch display of the printer. Instead it stays in "Operational" mode.
It does receive other messages, e.g. temperatures and "SD printing byte" messages, just not the "File opened" message. When looking at the serial.log, there is no "File opened" message (or errors) either. Just the standard response and temperature/progress messages from the printer.
I've tried to insert a M118 gcode into every gcode file to send a "File opened" message manually. But while it does receive that message and change the state from "Operational" to something else, the print progress doesn't work properly (shows over 100% after a short time), and timelapses don't work at all.
Everything works properly when starting a print through Octoprint, but I prefer starting prints on the display of the printer.
Does anyone have a similar problem with Marlin and Octoprint? It still occurs with Marlin 2.0.4.4.
The problem is that the printer never signalizes to the host when I start printing from SD card on the touch display of the printer. Instead it stays in "Operational" mode.
It does receive other messages, e.g. temperatures and "SD printing byte" messages, just not the "File opened" message. When looking at the serial.log, there is no "File opened" message (or errors) either. Just the standard response and temperature/progress messages from the printer.
I've tried to insert a M118 gcode into every gcode file to send a "File opened" message manually. But while it does receive that message and change the state from "Operational" to something else, the print progress doesn't work properly (shows over 100% after a short time), and timelapses don't work at all.
Everything works properly when starting a print through Octoprint, but I prefer starting prints on the display of the printer.
Does anyone have a similar problem with Marlin and Octoprint? It still occurs with Marlin 2.0.4.4.