Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prusa Connect randomly does not display previews sent by Prusa Slicer #12847

Closed
2 tasks done
zbkingCZ opened this issue Jun 17, 2024 · 7 comments
Closed
2 tasks done

Prusa Connect randomly does not display previews sent by Prusa Slicer #12847

zbkingCZ opened this issue Jun 17, 2024 · 7 comments
Labels
connect Cloud-based platform for remote printer management, sending G-code files, monitoring print status

Comments

@zbkingCZ
Copy link

Description of the bug

Hello,

Well, I don't know if it's a PrusaSlicer problem or Prusa Connect. After sending a file from PrusaSlicer to Prusa Connect, previews with printed objects are not displayed randomly. If the preview of the printed object is not displayed, the printing plate is also not displayed and therefore the "Cancel Object" function cannot be used. The "Cancel Object" function can only be used manually on the printer.
Screenshot 2024-06-17 at 17-20-50 67% PERSEUS historie tisku - Prusa Connect

Best regards

Zbyněk Král

Project file & How to reproduce

Tesla Label V01_0.4n_0.2mm_PLA_MK4IS_1h56m.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.7.4+win64, PrusaSlicer-2.7.4+win64-202404050928

Operating system

Windows 10 (sestavení 19045), 64bitová edice, Total RAM size [MB]: 8,510MB

Printer model

Original Prusa MK4, Firmware 6.0.2+14873

@zbkingCZ
Copy link
Author

Um, just a little note. If I send a print file from Prusa Slicer to Prusa Connect in .bgcode format, everything seems to be fine.

Screenshot 2024-06-17 at 20-37-40 0% PERSEUS historie tisku - Prusa Connect

@kubispe1 kubispe1 added the connect Cloud-based platform for remote printer management, sending G-code files, monitoring print status label Jun 19, 2024
@kubispe1
Copy link
Collaborator

Hi,
Thanks for reporting this issue. It's most likely a problem on Connect's side. I'm forwarding it to the team for investigation.

  • In the meantime, I can confirm that I've observed this issue as well. Several gcode files aren't displaying thumbnails correctly. However, it's good to know that bgcode files are working as expected.

@dunkmann00
Copy link

I've not used PrusaConnect, but have experienced something that might be similar to what you're describing with PrusaLink. In particular, the fact that it only happens with text gcode and not binary gcode.

If this is the same thing these might be related:

@zbkingCZ
Copy link
Author

Thank you for answer. I switched the slicer to .bgcode format because the "Cancel Object" feature in Connect is more important and by the way it's just brilliant 👍.
However, on the other hand, I really miss the direct editing of this format in text mode. Sometimes it is necessary for me to directly modify the source code for the printer.

@Printer606
Copy link

I am also experiencing these issues, except I can't get them to show up at all.

@kukulin
Copy link

kukulin commented Jun 26, 2024

I observe the same behavior in the version 2.8.0-RC1 win64
Just to update - problem solved in slicer 2.8.0 released tonight (27/06/2024)

@kubispe1
Copy link
Collaborator

If I remember correctly, there was a tiny issue with cookies on our side, which we fixed in one of the recent releases. It should be much better now, but I noticed some missing thumbnails. I assume it is an issue with the communication between Connect and Fw, as I see the same problem in the slicer webview and in common browsers (previously, this only occurred in Slicer).

I am closing the issue as resolved on our side. I have also forwarded the remaining issue to the Connect team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
connect Cloud-based platform for remote printer management, sending G-code files, monitoring print status
Projects
None yet
Development

No branches or pull requests

5 participants