Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Updated PrusaLink to 0.7.0 RC1. When using gcodes from other slicers (Cura, Simplify3d) the percentage completion is always at 0% throughout the print. This is a chnage from 0.6.1. The printers themselves will still display a percentage as the file progresses, but this is not carried through to PrusaLink (and therefore PrusaConnect).
I know the percentages from other slicers are nowwhere near as accurate as the ones generated by PrusaSlicer, but they are still usful to know approximately how far through the print is.
RE: Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Hi, this was not a deliberate change, it would be helpful if you could provide a gcode that breaks it. Thank you
RE:
GCode attached.
I did some further testing this afternoon and I can only reproduce this if I print from SD card. If I upload the file to PrusaLink it will display the percentages ok. Hopefully that helps narrow it down?
RE: Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Frankly, I cannot see the file, could you try packing it into a zip?
RE: Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Must not have uploaded right. I'll try again here.
RE: Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Okay, I think this could never have worked. I was operating under the assumption that I can get the printer thought up progress by calling M73 without any parameters. That doesn't work - returns every value equal to -1. I'll add this to my to-do list. Sorry I missed it. Don't expect it soon tho. Cameras are a huge priority right now.
RE: Print percentage always stays at 0% when using 0.7.0 RC1 with gcodes generated from other slicers
Thanks for looking at it. I'd definately take camera support over obscure "other" slicer percentages issues in certain use cases! If I spot a bug I just like to have it logged that all 😉
RE:
Never mind, it is a bug. I had that functionality. It's just been so long, thank you