After uploading g-code "it rotates" and takes forever (not ready to print)
Hi there,
when I am uploading an about 1 MB big gcode file (which is generated from Repetierhost with Slic3r), the upload time is normal and then the little rotating "working" icon apears and stays - the CPU is about 50% used from Repetier-Server. I wait for about 5 minutes - nothing happens it is rotating and not going to be ready to print. The CPU stays loaded at about 50 %. When I delete the file the CPU usage goes down. I tried it with several g-code files but only realy small and uncomplicated files are working and let me start with the print.
My g-code files are all in good condition and all printable with the normal Repetier-Host without any problems.
My machine is a Intel DualCore with 1.8 GHz rating, Running Windows 8.1 with about 2 GB Ram - until now it was fast enough for everything I've done in 3D printing.
Any ideas?
when I am uploading an about 1 MB big gcode file (which is generated from Repetierhost with Slic3r), the upload time is normal and then the little rotating "working" icon apears and stays - the CPU is about 50% used from Repetier-Server. I wait for about 5 minutes - nothing happens it is rotating and not going to be ready to print. The CPU stays loaded at about 50 %. When I delete the file the CPU usage goes down. I tried it with several g-code files but only realy small and uncomplicated files are working and let me start with the print.
My g-code files are all in good condition and all printable with the normal Repetier-Host without any problems.
My machine is a Intel DualCore with 1.8 GHz rating, Running Windows 8.1 with about 2 GB Ram - until now it was fast enough for everything I've done in 3D printing.
Any ideas?
Comments
I tried the version you sent to me. Nothing changed - but I found a solution for that issue: the problems are special characters in the filename like German-Umlaute and SZ-Signs...
After renaming the files everything is fine. It would be very kind to fix that bug in later versions...
Xserver would start chrome using up much memory and pi 1 does not have so much (512MB I think) so it might be that it gets really slow by swapping memory to sd card when you upload. Also I would expect more memory usage after upload when it starts rendering the image.
Also a full sd card could be a problem.