search

prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.79k stars 1.94k forks source link

wrong gcode uploaded to Connect from PrusaSlicer #13526

Open m10d opened 1 month ago

m10d commented 1 month ago

Description of the bug

I opened a new PrusaSlicer window to create a quick flow cal box for my mk4s, recently upgraded & possibly having issues. image

Logged in via Slicer, Send to Connect resulted in in this in my connect mk4 page; the gcode is named correctly ("Shape-Box..."), but is clearly the time & preview glyph of a 23hour helmet I had previously sent to my XL.
image

Further, I had clicked in Slicer "skip queue and set ready", but while the printer WAS apparently set to ready, no print started. Going to send it again, I now see the Mk4 is at ready (previously it was stopped) image

I believe this is a Slicer but, NOT a connect bug, because when I re-send from the same window, it's sending the 30+MB helmet file (which was never opened in this slicer window; I do have it open in another window) image image

Project file & How to reproduce

see descr.

Checklist of files included above

Version of PrusaSlicer

2.8.1 flatpak

Operating system

ubuntu 22.04

Printer model

mk4, and xl5t

kocikdav commented 1 month ago

Hello, thank you for reporting this issue. Please help us reproduce the issue by answering these questions.

  1. The original helmet gcode - it was sliced in different PrusaSlicer window? Was this window still opened while slicing the cube?
  2. Can you reproduce this issue again?
  3. If yes, when you export the second gcode to a local folder, is it correct gcode or also wrong?

Thank you.

m10d commented 1 month ago

  1. Correct, I had two PrusaSlicer windows open; the gcode it uploaded was another model I had sliced in the other window. I can't guarantee it was the exact most recent one, but it was my model and I had recently sliced it and sent it to my other printer.

  2. I reproduced this state multiple times at the time of report, but do not believe I have seen it since.

  3. I answered No obviously, but note for this question in the original reproduction it would seem high-confidence the gcode it actually uploaded was indeed wrong based on (A) stated size & preview image, (B) time to upload and (C) reported size on the printer - because the gcode I asked it uploade from the current window was ~10% of the size.

On 10/29/24 12:07, David Kocik wrote:

Hello, thank you for reporting this issue. Please help us reproduce the issue by answering these questions.

  • The original helmet gcode - it was sliced in different PrusaSlicer window? Was this window still opened while slicing the cube?
  • Can you reproduce this issue again?
  • If yes, when you export the second gcode to a local folder, is it correct gcode or also wrong?

Thank you.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>