You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When printing a (very) large G-Code file from the SD card with a Raspberry Pi 3b, OctoDash displays "Can't retrieve job status" continuously, OctoPrint correctly displays the job in progress.
Steps to reproduce the behavior:
I grabbed the moon-lamp-thingi_1m.stl from https://www.prusaprinters.org/prints/23859-designer-lithophane-moon-lamp/files, sliced it at .15mm and got a resulting 207MB G-Code file. Stored it on the Prusa SD card, then had the Prusa print it. OctoPrint correctly displayed the resulting file, print status, time remaining, filename, etc - but OctoDash is continuously displaying "Can't retrieve job status".
I am on the latest version of firmware, slicer software, and OctoPrint (having just upgraded everything earlier in the day). I just switched to OctoDash yesterday though, so I can't say if this issue was present in earlier versions of anything or not. I do have an MMU, though this print is for a single material, so I don't expect that to play into the equation.
The text was updated successfully, but these errors were encountered:
When printing a (very) large G-Code file from the SD card with a Raspberry Pi 3b, OctoDash displays "Can't retrieve job status" continuously, OctoPrint correctly displays the job in progress.
Steps to reproduce the behavior:
I grabbed the moon-lamp-thingi_1m.stl from https://www.prusaprinters.org/prints/23859-designer-lithophane-moon-lamp/files, sliced it at .15mm and got a resulting 207MB G-Code file. Stored it on the Prusa SD card, then had the Prusa print it. OctoPrint correctly displayed the resulting file, print status, time remaining, filename, etc - but OctoDash is continuously displaying "Can't retrieve job status".
I am on the latest version of firmware, slicer software, and OctoPrint (having just upgraded everything earlier in the day). I just switched to OctoDash yesterday though, so I can't say if this issue was present in earlier versions of anything or not. I do have an MMU, though this print is for a single material, so I don't expect that to play into the equation.
The text was updated successfully, but these errors were encountered: