Prusa Connect fails to upload to the MK4 - some file not all
I am running Prusa Connect on a new MK4. Using Prusaslicer 2.6 GA version and now on v5.0 alpha 2. Alpha 2 seems to have fixed the wifi dropping issue by the way. The issue I am having and had even before the alpha release is that when I send a print job from the slicer to the printer via connect it sends it to connect and connect sees it but it does not going into the print queue although you can see the file there but there is no way to force it to the printer. I have tried deleting all the files in the queue and resending but it seems to happen a lot. The printer is online as I can control other functions. I have searched this forum and will check the filenames to make sure there are no bad characters in the filename.
Anyone have a similar issue.
TLDR, some files sent to the printer vie Prusa Connect show in queue but will not load to the printer.
RE: Prusa Connect fails to upload to the MK4 - some file not all
I have the exact same issue, most files upload flawlessly, but some files upload to connect but get stuck sending it to the printer...
When a transfer fails it just keep waiting without an error and its always the same files sent from prusa sllicer, doesn't matter if i delete them and upload again it keeps failing
Uploading it through web instaid prusaslicer throws the same result
I've changed the file name to something shorter and it has uploaded just fine, could it be too long even when it didnt throw an error??
Original name was: Protector_tapa_olla_0.4n_0.3mm_FLEX_Fillamentum Flexfill 98A @MK4_MK4_1.19137grs_15infill_5m.gcode
Modified Name: Protector_tapa_olla_0.4n_0.3mm_FLEX_MK4_1.19137grs_15infill_5m.gcode
RE: Prusa Connect fails to upload to the MK4 - some file not all
I was also having issues uploading some files into my MK4 printer via the Prusa Connect web interface. The file would transfer into the Prusa Connect system without any issues; however, the file would not transfer into the printer. There were no errors or messages displayed. I deleted the file from Prusa Connect, logged into PrusaLink, attempted to transfer the file directly into the printer, and immediately received an error message - "File name too long". I'm thinking that Prusa Connect will accept just about anything for a filename because the filename and its data are being stored into a database and perhaps there is little validation being made on the filename submitted. Then, when the system attempts to transfer the file from Prusa Connect into the printer, it fails but no messages are being returned to the Prusa Connect user. I, too, shortened the filename and the file transferred as expected. I've also learned that there are some characters accepted by my computer's file system that are not allowed by Prusa Connect and this results in the file not being accepted with no error reporting. For example, my Mac's file system accepts a "+" character within a filename but Prusa Connect did not seem to like the filename and rejected the file. I removed the "+" character, resubmitted the file, and it worked as expected.
I am a new Prusa user without much experience yet but perhaps this information might be useful.
RE: Prusa Connect fails to upload to the MK4 - some file not all
Hi, yes, this is confirmed broken. The printer rejects the file and connect just re-sends the request. This keeps happening in an endless cycle. Will fix. Thanks for the report
RE: Prusa Connect fails to upload to the MK4 - some file not all
It is a file naming issue. Prusa Connect rejects sending duplicate file names. Do you know if this is a PC or a Firmware issue.
RE: Prusa Connect fails to upload to the MK4 - some file not all
You cannot exactly have two files named the same on the printer in the same folder. And also there is a rather short path (as in "/my/special/folder/duck.gcode") under 80 chars or something like that. It shold be communicated to the user as fast as possible instead of just timing out or spinning in an endless circle. But it is unlikely the underlying limitation would get mitigated as is that we would automatically rename the file to fit and be named uniquely. A replace / cancel modal box might be nice the. But not anytime soon I think
RE: Prusa Connect fails to upload to the MK4 - some file not all
Prusa slicer should not send filenames that are too long to the printer. Period. Its a stupid bug.
RE: Prusa Connect fails to upload to the MK4 - some file not all
Just a quick reply while troubleshooting my XL file upload using connect.
Opening TCP 443 works for the WEBGUI (management). File transfers (at least firmware) seem to use HTTP.... To you need to open TCP 80 to Prusa Servers to be able to upload (firmware) files.
Don't forget to check out rnldnkp.com 😀
RE: Prusa Connect fails to upload to the MK4 - some file not all
I can confirm that this is still happening. I recently upgraded a 3S to a 3.5 and was able to send a couple files and successfully print. Cancelled a print, moved the printer and then tried to resend. Failed to go from PrusaConnect to the printer. Tried redoing all the network connectivity from the ground up. Turns out, simply adding a "b" to the file name fixed it. Seems silly.
RE:
Just ran into the same issue; duplicate filenames prevent Prusa Connect from printing.
(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.
RE: Prusa Connect fails to upload to the MK4 - some file not all
I can confirm the same issue here.
Something seems broke.
I am printing multiple versions that're are slightly tweaked. Same name.
Seems silly you have to remove the file after printing
RE: Prusa Connect fails to upload to the MK4 - some file not all
You cannot exactly have two files named the same on the printer in the same folder. And also there is a rather short path (as in "/my/special/folder/duck.gcode") under 80 chars or something like that. It shold be communicated to the user as fast as possible instead of just timing out or spinning in an endless circle. But it is unlikely the underlying limitation would get mitigated as is that we would automatically rename the file to fit and be named uniquely. A replace / cancel modal box might be nice the. But not anytime soon I think
it's now a year later, and people - including me - keep having the issue.
Even after cleaning up the root folder of the USB stick, still print jobs are stuck.
It's especially conrfusing and makes new users feels helpless as the Connect UI does not offer any advice or possible solutions.
it would be extremely helpful to have a button "try re-uploading" or an info "try renaming the project file"
RISPONDI: Prusa Connect fails to upload to the MK4 - some file not all
it happens when you upload a file with the exact same name to the printer,
when you fix a small thing and the new printing time is not changed it will try to reuplad that with the exact same name
easy fix is to go to my printer files and delete the old file that have the same name
please Prussa, you can simply check that and trough an error or add +1 at the end of the name
RE: Prusa Connect fails to upload to the MK4 - some file not all
This is still an issue. Is there any way to get rid of the current transfers that won't complete due to conflicting file names?
RE: Prusa Connect fails to upload to the MK4 - some file not all
Hello,
It is happening to my XL and MK4 all the time, I need to attempt sending files several times, sometimes 4 attempts are not successful. I tried to restart the printer, sometimes it works, sometimes not. The error says that the network connection was reset.
I saw some people saying on the forum that we should not reuse the same name when uploading a new file, but using the same name should actually overwrite the existing file.
Printers are connected via cable as initially I thought that my wifi has issues.
@Prusa: Please fix this, it is very annoying. Thank you.
RE:
This also happens with my MINI+ (running firmware 6.2.1+8833, printing from PrusaSlicer 2.9.1 Beta1, but also previous versions at least back to 2.9.1 Alpha).
Sometimes I "Send to Connect", the printer is marked ready, etc, and the print is at the head of the queue. The file says it has been uploaded to Connect, but the stage where it then is uploaded to the Printer simply never starts. I've not been able to find any combination of restarting the printer or prusaslicer that will trigger the upload to actually start.
I'm assuming that either the printer needs to check for uploads, or Connect needs to push out to the printer, but neither of those things is something one can manually retrigger.
EDIT: I am also fairly certain this happens when there would be no filename collisions. I am usually able to print by "deleting" the print from the queue, and simply doing all the same steps again (and this time the sliced gcode _is_ uploaded to the printer)
RE: Prusa Connect fails to upload to the MK4 - some file not all
Hello,
FWIW: From my perspective there seem to be multiple issues affecting the transfer of files from a web interface to PrusaLink and PrusaConnect. I tend to create GCODE files with long names. I first encountered a limit of 80 characters from web interface to PrusaLink last year and that seems to have now changed to a limit around 100 characters. Web interface to PrusaConnect appears to have a different character limit, something less than the PrusaLink limit. If a file transfer truncates the file extension, I'll get a "Not a GCODE file" error message. If more than the file extension is truncated, a uniquely named file can be thought to have a duplicate file name if only the last character(s) are what makes the filename unique. I have yet to see a file with a lengthy filename, directly copied to the USB stick, that cannot be handled by the printer (I am using both a MK4 and an XL). I'm thinking that whatever the filename limit is in the printer operating system needs to be replicated out to both PrusaLink and PrusaConnect so that files traveling between all these systems do not have their filenames truncated. I've given up on PrusaConnect (too many failures) and am using PrusaLink. If a PrusaLink transfer fails, I just do a direct copy to the USB stick.
This afternoon, I tried copying a file to the XL using PrusaLink. The filename is 102 characters. The file transfer failed ("not a GCODE file") so I copied the file to the USB stick and the file is currently printing. It is also interesting that both PrusaConnect and PrusaLink currently display the correct, lengthy filename even though they would not accept the file.
Considering that GCODE filenames originate with whatever operating system PrusaSlicer is running on, I'm thinking the filename limit from start to finish should be at least 256 characters -- a length that Linux/Mac/Windows might easily create. It would also be helpful for PrusaConnect/PrusaLink, upon receiving a file that they do not like, display the full name of the file they see as part of an error message so the person submitting the file can compare their filename with the filename the receiving system has rejected.