GCode Corruption keeps happening
Can someone help me figure out why I keep having GCode fail? It's getting very frustrating. It's happened a few times now on a few different prints.
Once I had it happen on the same print where the GCode was re-compiled and reprinted.
This one here is the only example I have that I can provide. This print just failed at 98% with 1 minute to go after 2 hours. Fortunately, the part can still be used, but I am still perturbed.
I included the GCode if that helps. Also, the STL file. And some screen shots of the print, but I don't have the error message. Sorry.
What I don't understand is why Prusa Slicer is making GCode the Core One cannot interpret. Do I need to turn off error checking? Is it a USB thing? If it IS a UBS thing, why do the prints that I have keep failing at 97-98% Because 3 of the 4 did. I think one failed at 83% or thereabouts.
RE:
And it happened again! On a different print.
See the attached files.
This time it failed at 97%. I re-opened the .3mf file and made a fresh GCODE. I did not run it, I gave up on the print for now (because I am too irritated)
I compared the .3mf file I just created with the one on the USB stick using Beyond Compare software. I am not sure how helpful it is, but there were differences.
I thought I saw somewhere that heat was affecting the USB sticks and might be corrupting them. If that's the case, that sounds like a huge design flaw. Perhaps I need an extension cable...
If it matters, I am running the printer in my garage. And it is rather hot out.
Also, I included the .3mf file from the first crash, because I forgot it.
RE:
While I don't have the time to check your attached files yet:
I also had errors and it seems that the USB stick of the Core One isn't the best.. Hopefully just a bad batch and not a "too cheap" usb stick.. Any issue with the storage is amplified due to the Core One not using any internal storage. So the G-Code isn't read once and copied into the internal storage, but instead it's continuously read from the usb storage. One bad sector and the print fails.
However, I wanted to be sure and bought a SanDisk "Max Endurance" micro-SD and the tiny usb adapter from SanDisk.
Max Endurance cards are the most recommended for car dash cams, which is a very tough situation with the sun heating everything up, vibrations, road bumps and constant write cycles.
I didn't have any errors with my dash cam in two years, so for me, these cards work as promised.
I also tried to use a few different other SD cards, that I use in my action cam without issues, but the dash cam didn't like any of them. Always some corrupted videos or 10-40 seconds of error-beeping at random times, while driving.
Make sure to get the max Endurance and not the high endurance though! Big difference between these two.
RE:
I look into a Max Endurance card. It looks like it's not the kind of thing I can just go buy at my local store, but will have to order.
That really sucks. I was working on a project I really want to finish this weekend, and this uncertainty is upsetting.
I will be doing some tests on my files I try to print today. I am going to verify the code is identical pre-print and in the instance of a failure. I do believe it is the printer itself that is corrupting the files, be it heat or some other issue.
RE:
I also think it's just the USB stick causing issues.
If you have a decent USB stick available to format, use that instead. It's sadly "normal" for cheaper storage devices to have some little errors every now and then. PC programs can usually take it and stay stable, while either correcting the errors or reading the faulty sector again.
But the Core One doesn't seem to like any errors.. Any decent USB stick or SD card + reader should work without errors though!
The SanDisk Max Endurance is a total overkill, but since you won't go broke by paying 30€ for it, after buying a Core One, it's a no-brainer for me to buy that card.
_________________
About the card, since you don't really find any real information about this stuff: there are different ways to use the storage cells of SD cards and SSD drives. You have two voltages, "high" and "low", "1" and "0".
But you can split that voltage into more ranges. For SSDs, there are "SLC", "TLC" and "QLC" nowadays.
Single, Triple, Quadruple.
When using the same amount of storage cells, QLC will have about 4x the storage space vs SLC, but it's a lot slower and more prone to errors. Usually, writing is done as SLC mode for speed and then the SSD controller moves the data into QLC mode in the background, when there's little activity.
The "Max Endurance" cards are basically just SLC storage with components for rough environments like cold, heat, humidity, vibrations.
For a 32 GB card, the amount of storage cells is probably about the same as a normal 128 GB card. Making them a lot more expensive.
The "High Endurance" cards are not SLC and only use similar tough environment components, as the "Max Endurance" cards.
RE:
I went to the store this morning and could not find an appropriate SD card. So I will order one when I have a chance.
In the mean time, I have a 3 foot USB extension cable. I am using that to get my USB stick a little farther from the machine. Hopefully that will take vibration and heat out of the equation. At least for heat coming from that little 0.5" distance between USB and printer. Garage heat just is what it is, I am afraid.
I have pulled the stick off after prints and it was rather warm. I am currently using one of these: https://emtec-international.com/en/drives/3.0/b110-click-easy-32
RE: GCode Corruption keeps happening
I've used Prusa drives just fine, and I've had very expensive high end brand usb drives that failed quickly. I've become very negative on USB drives in general and wish Prusa had some on board storage. And I can't escape the feeling--like the USB--that some read/write operations of the printer may be responsible for some of the issues but really no way to prove this conclusively.
Formerly known on this forum as @fuchsr -- https://foxrun3d.com/