and... Welcome!
Happy to hear about your new printer, not that you’re having problems of course.
-
1
and... Welcome!
Happy to hear about your new printer, not that you’re having problems of course.
Actually, since making my post I think it is caused by my micro SD card getting corrupted. I don't know if it is caused by Cura?
I have been saving the G-code file directly from Cura to my microSD, then ejecting in cura from the little popup at the bottom of the screen. I noticed after doing so, then reinserting my MicroSD and trying to access the files in Windows, it would freeze up and crash windows explorer. This was repeatable. This might explain the strange behavior of my printer.
If I save the G-code file to my hard drive then copy the file to the microSD, and eject from the windows tray icon, it seems to work fine. I just started an 8 hour print and so far so good, but we'll see.
When I get octoprint set up I don't think I will have to worry about this.
I think you’re on to something, if your SD crashes explorer it seems likely it would cause problems with the printer.
I wish you the best of luck
Well my SD card seems to be working fine now.
But my print I started last night failed. I'm guessing about 1.5 hours in it froze. When I check on it this morning it was just sitting in one spot.
Maybe an wiring issue.
12 hours ago, TMicke said:
Have you tried to run the same gcode again, and just restart the printer?
Well I just tried the same G code again. It failed in the exact same place. Crap!
I guess it's a slicing issue?
That would be my guess as well, unfortunately I’m not the one to help you with that.
/Micke
I have been printing from octoprint today with no issues.
I'm attempting my longer print that failed last night again. Hopefully it works this time!
Edited by Overkill777For the pausing issue, check that your Z-Speed limit is set to something other than zero:
This should have been fixed in 4.2, but it could certainly cause problems.
The other thing to check for the area where it pauses, is whether there are a huge number of tiny moves--possibly caused by too much complexity in the model.
Recommended Posts
TMicke 23
Have you tried to run the same gcode again, and just restart the printer?
Link to post
Share on other sites