Prusa link, uploading gcode does not transfer to printer after.
This is happening sporadically and sometimes I cant get it to work at all.
I have 5 mks3+ on the prusa link system.
I choose Upload and print, it goes through the motion of uploading success but the second dialog bar does not initiate.
If I go to look at the files in storage it shows it but no icon representing the file is there and if I go to try to print from it it does nothing.
However I CAN download the gcode and manually transfer it to the printer sd card and start print and It works and shows the icon(image of stl)
RE: Prusa link, uploading gcode does not transfer to printer after.
Hello,
I have the same problem that I have just discovered this morning on one of my 15 printers, not always easy to see because we often print the same file of our list, on the other hand it misses for a printer the part of load
attached photo
RE: Prusa link, uploading gcode does not transfer to printer after.
Ya I gavc up and went back to octoprint.. had no choice. got zero support here
RE: Prusa link, uploading gcode does not transfer to printer after.
Hi, sorry, this one slipped my attention. I posted it to slack, an attempt to fix this has been merged three weeks ago, asked if and when was it deployed. Bit I didn't get back to the thread, sorry.
I am very confused about which upload are you talking about. I assume it is an upload using PrusaConnect. Since the upload through PrusaLink straight from the slicer does not have the second part.
Sorry about it being broken, I'll make sure to ask about it again.
RE: Prusa link, uploading gcode does not transfer to printer after.
Thanks but I am not converting back again.
There is the part where it uploads the main file to the repository I assume.. and then from there it does a slower transfer to the actual printer. (This second part never kicks in)
RE: Prusa link, uploading gcode does not transfer to printer after.
It works again
RE: Prusa link, uploading gcode does not transfer to printer after.
Yes, it's intermittent, the SEND_INFO command fixes it. But I'm in the dark as to why, sorry. If I forget to get back to here again. If it's still broken after a few weeks, please ping me.