Print won't start if uploading file with the same name as an existing file in history
PrusaLink type: Raspberry Pi 3
PrusaLink version: 0.8.1
Printer type: MK3s
Printer UUID (you can find it in Printer detail page - address line): bb04469e-b0bf-420b-a64a-66fe3762a850
Printer firmware version: 3.14.0-8066
PrusaSlicer version (if applicable): 2.8.0
Description of the bug, including steps to reproduce (if possible):
Upload and print a gcode file.
Upload and try to print another gcode file with the same name as the previous one.
The second one is stuck with the message "File not uploaded to printer".
If I manually ssh into the raspberry pi and remove the old file from the prusa files folder, the second file can be printed.
RE:
Same issue for me as well.
Pi zero 2.
I have yet to confirm by deleting the file with the same same.
RE: Print won't start if uploading file with the same name as an existing file in history
Just ran into the same issue, though not using a rpi.
(MK4 @ 6.0.4+14924. PrusaSlicer 2.8.0+MacOS-arm64)
It doesn't give a proper warning, and keeps filling the queue with items marked "The file is not uploaded to the printer". Renaming the file (or deleting the original) solves it.This seems like a rather silly bug, just check for duplicates and add a suffix. I can image that throwing the error to the user isn't easy as it takes a round trip to the printer.
A much nicer way to solve it could be to calculate the sha (on pc or cloud) and automatically add it as a suffix.If the sha is not different, no need to upload it again, just print it. That would also prevent from filling up the usb with duplicates.