The two pictures show the same corrupted file. But what's more intriguing... I have found that this corruption only occurs during the print!
I did the following:
- Import the STL file in cura
- Save the gcode to the SD card and copy this file to the PC
- Take the card, insert it again
- Read the gcode, it was OK
- Print the object, then another error occurred
- Stopped the print
- Read the gcode in the PC, it was corrupted!
This is the gcode file view in cura after the print:
This is how the object printed:
Unfortunately I formated the card afterwards without saving the gcode, I should have made a comparison to see exactly what went wrong...
I have tried other SD card, but it doesn't get recognized by the ulticontroller (it's a 16Gb card with a partition of only 2Gb), I don't have any other 2Gb SD card...
Now I'm printing another object with the SD card write protected, I'm at 77% and everything is ok, but you never know until the end...
After this print I will try to replicate the error and see what changed in the file after printing... maybe a firmware bug?
If it's specifically just the file on your SD card, I guess it could be a bad card. It might also be file corruption due to you not properly ejecting the card before you remove it from the machine, maybe?
Is the top picture the 'ok on the pc' one... or are they both from the SD card? In both pictures, something looks wrong aside from the missing bits - there's what looks like a skirt and raft floating over the top of your print... those should be at the bottom.
Perhaps if you can post the 'correct' version of the gcode, I can take a look at it, and see if it makes sense. It's also possible that your model is bad somehow, and is confusing Cura into doing odd things.
Link to post
Share on other sites