PrusaConnect - problems with interpreting BGCODE
I like the bgcode in Prusaslicer 2.70 and MK4 on 5.1.0 firmware. However i am noticing couple of issues in PrusaConnect since using bgcode.
1) preview works fine on printer but it frequently doesnt show up on PrusaConnect. At least not at start, they show up later but cant confirm what triggers suddenly show them. Maybe random, maybe shows after i print the file for first time. Not sure. Sometimes shows instantly after upload, sometimes days later. Dont see any pattern.
2) it often cant get print details from the bgcode, such as print time. As example when putting files in queue, it tells me "print time is unknown" and then wont show the timeline
RE: PrusaConnect - problems with interpreting BGCODE
Came here to post this exact issue. It's quite annoying and worst of all it seems random. Some files work, some don't. Sometimes, a file that didn't work will work at another time and vice-versa. It also doesn't seem to matter whether the file was copied directly to the USB from the computer or sent over via PrusaLink to the printer. Surely we can't be the only ones experiencing this. I see your post was a few weeks ago. Have you figured anything out since then?
RE:
Hi, I think I've forwarded this to the team. We do not have the parsing ready yet, sorry for that. It will get added in the future. As for the bgcode prints not working, please describe that in as much detail as possible. Ideally start a new issue or look for a simmilar one in the github prusa3d Prusa-Firmware-Buddy repo. Thanks
RE: PrusaConnect - problems with interpreting BGCODE
The failure for me is more to do to the print time missing. I'm using the "Print Queue" for schedule management and the missing time results in a 12 hour block and missing any job past that point. Once it starts printing it will correct itself and print without issue, but a repeat print of the same file still shows the same problem in the schedule. I've tried re-slicing and file naming defaults, no differences. It seems random as my jobs at the moment use the same parameters in slicer, just different parts. Naming of the files use consistent naming, like starting with beam A, beam B, beam C... beam C has the problem and nothing I do seems to correct it. BTW Slicer 2.7.1, MK4 5.1.2
RE: PrusaConnect - problems with interpreting BGCODE
Correction, reprints of the same file do show the correct times. I can share a file if you'd like.
RE: PrusaConnect - problems with interpreting BGCODE
I'm also seeing this - starting today, interestingly. Certain files are displaying this message "The printing time of the last job is unknown, the following jobs will not be displayed".
RE: PrusaConnect - problems with interpreting BGCODE
I have the same issue. When stacking up a bunch of prints, apparently random prints in the queue will not have their duration appear in the timeline, and every job after them in the queue won't show up on the timeline. Deleting the file from the queue, reslicing and reuploading with identical settings solves the issue.
RE: PrusaConnect - problems with interpreting BGCODE
Yep, same. A bit frustrating when you're trying to build a print schedule.
RE: PrusaConnect - problems with interpreting BGCODE
Hi, thank you for the report, I am pretty sure where at least some of the trouble originates from. Will work on this soon
RE: PrusaConnect - problems with interpreting BGCODE
I'm having the same issues with the queue, but I'm also having an issue with no information being displayed for the current print. The times are displayed on the MK4 LCD, but nothing is displayed in Prusa Connect until the print is finished. It only tells me a percentage.
RE: PrusaConnect - problems with interpreting BGCODE
I have a temporary workaround for one of the issues. When you move the file from connect to the printer, make sure the printer and the file are in the SAME team. Hope this helps at least some of you. It seems like we have multiple issues mixing in here now.