Prusa connect issue slow speed
Hello. Today it is 12.11.2013.
I have kinda problem taht prusa connect is not usable because of how it is working. I mean the page is verry verry slow. And when I uploaded file to to my printer it is sending it with speed 800bit/s - 2kb/s So it is not usable and i must to play with usb sticks to print anything. The file to prusa connect was sended in 1-2 seconds. But now even file 2-4mb gcode is transimted to printer in 3-4 hours
RE: Prusa connect issue slow speed
Hi, please try ethernet, we are making a better firmware that should alleviate this problem. It's weird that you get less than a hundredth of the speed we normally get - still slow, but not THIS much. Sorry for the inconvenience :/
RE: Prusa connect issue slow speed
I have both printers connected via ethernet. Sending via prusalink is okay with speeds. But the issue was with site. The page of prussa connect was loading aprox 5-10 minutes. And the sending from prussa connect site was verry slow end often the page froze for dozen of minutes. Like there was problem with routing from Poland to your prusa connect servers. ATM it is working like it should everything is loading in few seconds. I was checking from 2-3 other ISP and the issue was the same yesterday.
RE: Prusa connect issue slow speed
Prusa MK4S, printing a file using Connect. Failes 2 times ("gCode transfer too slow, check connection or USB" - something like so). WiFi connection was ok, printer connected. Pressed "resume", but failed to resume. USB drive was in, but I assume that the printer "knows" the original source of the file. My print is lost.
The printer heats up, then goes to the last printed position to continue, then touches the print and fails to continue with message "Chyba disku nebo souboru, připojte disk znovu". This happened already two times.
Design • Code • Make
RE: Prusa connect issue slow speed
I just got my Mk4s and have been trying to use PrusaConnect to send files and print remotely. I'm having the same issue as petr-vacek with prints failing due to slow gcode transfer.
Additionally, I can't even just send a file to the printer. I get an error saying that the file upload failed. This is not just for Gcode but a firmware update as well.
The only way I can use my Mk4s is via the USB stick. I'd love to have this issue resolved so that I can actually make use of PrusaConnect.
RE: Prusa connect issue slow speed
This is still a problem. Does anyone know how to fix it? Happening on a new Core One
RE: Prusa connect issue slow speed
This is also happening on my factory built core one.
both the core one and the computer are connected by wire to the same modem.
This is still a problem. Does anyone know how to fix it? Happening on a new Core One
RE: Prusa connect issue slow speed
This is also now occurring on my MK4S.
any solution from Prusa for this 2+ year old problem?
RE: Prusa connect issue slow speed
Have you taken a look at this: https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v6.2.6-alpha ?
RE: Prusa connect issue slow speed
Unfortunately it still occurs on the latest Alpha build, both on wired or wireless.
Oddly, I will have greater success of the file fully transferring correctly (once Connect service is live) by transferring the file to the printer and then starting the print from its screen.
RE: Prusa connect issue slow speed
This is terrible, it takes 3-5 minutes to move a tiny 12 meg file. Is it going UP to Prusa cloud and back down? I am all hardwired Ethernet. Optoprint moves files in a few seconds, AT MOST, while I researched this problem and typed this in, and I am still waiting on Prusa Connect to my new Core One. Unusable.
RE: Prusa connect issue slow speed
Two things that can help are minimizing your printers latency and an overkill flash drive.
As far as I know, this is a limitation of the Buddy platform. It can hold only a tiny block of data in RAM before writing it to the USB drive. The block is smaller than the block size of the flash drive making it retrieve, modify and rewrite the same block of flash multiple times instead of a single time if the block in RAM was larger. This is slow and it stresses the USB drive.
The firmware and slicer teams did everything in their power to make this not a problem. The files got compressed, so less data has to be transmitted and the print can be started while the file is still downloading eliminating the wait almost completely.
That said just managing files on the flash drive through cloud is not going to be swift. Until a new platform comes along, we're stuck with these speeds.
Octoprint is fast because single board computers are fast with usually multiple gigabytes of RAM. Our printers use a micro-controller with 256 kilobytes of it. Feel free to search for STM32F427ZIT6 specs. That's the main chip. It prints, runs the local web interface, the UI, the Connect integration, the downloads.
RE: Prusa connect issue slow speed
The problem is if i I try to stream and start then i get the g code is running slow and it crashes my print. So that doesn’t seem to be an option either… if the g code running slow wasn’t a problem I would not have know about this absurdly slow transfer. This is a design decision flaw. Can the g code issue be fixed instead?
RE: Prusa connect issue slow speed
In that case, I would contact support.
I don't know of anything beyond verifying you are running the latest FW, using bgcode, minimizing network latency and upgrading the USB drive. Maybe the support guys will know more.
And yes, the files uploaded through the Connect interface go up to Connect, then down to your printer. Which adds some delay, depending on the latency and packet loss from the cloud servers to your printer, it might be cutting speeds significantly. You can verify with an upload through your local printer web interface (PrusaLink). It might end up being much faster.
RE: Prusa connect issue slow speed
Those are good points. I don’t know about a local prusalink interface, will check that out. And will see about enabling bcode (my mk3 doesn’t accept bcode so maybe I can do bcode for the core and keep scode for the older printer. Thanks!
RE: Prusa connect issue slow speed: Tojik had good advice!
While I was updating to the 6.4 so it will auto close or open the vent, I took his advice. I switched to bcode to reduce the file size (my old MK3 will still work with gcode, and Prusa Slicer knows to do bcode only for the Core. It seems to help with the file going quicker, since I am now trying streaming again using the smaller bcode file. We will see! Now if I can get my material to match the name on the custom value on the printer, so I don't get those "wrong filament" warnings (Printer says "3D-PCTG" and my saved Filament on the slicer is "3D-PCTG". Seems the same to me.