Notifications
Clear all

File incomplete - gcode issue??  

  RSS
3DALHEMIJA
(@3dalhemija)
Estimable Member
File incomplete - gcode issue??

Just got message - File incomplete from my SD card....

what is cause, and more important what is solution for this?
PS. i m pretty new user of MK3

Posted : 30/01/2019 6:38 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
Re: File incomplete - gcode issue??

What slicer are you using?

If it's not Slic3r....
Try making

M84

the last instruction in the custom end gcode....

Regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Posted : 30/01/2019 7:35 pm
gnat
 gnat
(@gnat)
Noble Member
Re: File incomplete - gcode issue??

Could be as simple as how you removed the SD card from your computer. Computer writes are typically buffered, so if you remove a drive (the SD card in this case) before it has flushed the buffers you could end up with corrupted files.

Always make sure that you eject/unmount the card and wait for the light on your SD card adapter to stop flashing before removing the card.

Try a different card as it could simply be the card itself has issues. I bought a pack of 4 8GB cards and one simply refuses to be recognized at all.

Also don't cheap out on SD cards, stick to the major brands (e.g. SanDisk). Not all SD cards are created equally and some interfaces are more finicky than others. We have a Cannon camera that is extremely picky about what it will read. Even the major brand cards can have issues though, but my experience is that is much rarer.

MMU tips and troubleshooting
Posted : 30/01/2019 9:44 pm
markus.g3
(@markus-g3)
Active Member
Re: File incomplete - gcode issue??

HI all

Just want to inform, that I have the same issue, using "Slic3r Prusa Edition 1.41.2+win64" with MK2S MM with Firmware 3.1.0 ( I know that this is the MK3 board, but the error seems to be the same). I would upload my small gcode file for review, but it seems uploading does not work. If anyone wants to have a look at it, drop me a note and I will send it by PM.

When loading the gcode file from my SD, the error message apears. If I print anyway, everything seems to be OK. However, I fear that once I have a larger file, that there might be a complication at a certain time (think about a 30 hour print... 😯 ).

Same settings in an older slicer-version did not lead to this error. Unfortunately I do not have this older version anymore (because I had to rebuild my computer) and it is not longer available as a download, even in the older versions-section (I remember it was 1.37.2). maybe I can getr this version from anywhere else?

In any case I'd prefer, if this "bug" would be fixed sooner or later...

BR Markus

Posted : 09/02/2019 1:38 pm
cwbullet
(@cwbullet)
Member
Re: File incomplete - gcode issue??

I have had the same issue - usually from Octoprint, but have had it without. I have had it most often from Simplify 3D but also Slic3D.

I have figured out a correlation. I will try M84.

--------------------
Chuck H
3D Printer Review Blog

Posted : 09/02/2019 2:19 pm
markus.g3
(@markus-g3)
Active Member
Re: File incomplete - gcode issue??

I now found some older slic3r-versions at the prusa download-site.

I figured out, that also Version 1.37.5 (included in driver package "prusa3d_win_2_1_0" from 2018-04-11 18:59) leads to the same error "incomplete file".

So I re-installed version 1.37.2 (from driver package "prusa3d_win_1_9_2"from 2018-04-11 18:15). At least this version works fine, wthout erors when loading the gcode from SD-card.

(All tested with firmware 3.1.0 at MK2S MM)

BR Markus

Posted : 09/02/2019 2:45 pm
markus.g3
(@markus-g3)
Active Member
Re: File incomplete - gcode issue??

update:
just tested version 1.41.3 from Feb. 12:

Same issues (file incomplete). However, the result of a test-print was quite OK.
At the end of the print, the heatbed and nozzle turned off, so I still don't know what the problem if the "incomplete file" is.

Maybe someone of the Prusa-team is able to analyze my gcode, to find out whats going on there. Just driop me a note and I can send you the file (It's a small one)...

BR
Markus

Posted : 18/02/2019 8:13 pm
dclaar
(@dclaar)
Eminent Member
Re: File incomplete - gcode issue??

The MK3S firmware is corrupting the file.

Just set up my MK3S, updated firmware to 3.6.0-2069 (Mar 1 2019), installed slic3r 1.41.3+win64.
Opened 3DBenchy in slic3r, hit Export G-code, waited until it finished.
Verified file was complete:
; default_filament_profile = "Prusament PLA"
; compatible_printers_condition_cummulative = "printer_notes=~/.*PRINTER_VENDOR_PRUSA3D.*/ and printer_notes=~/.*PRINTER_MODEL_MK3.*/ and nozzle_diameter[0]==0.4";"! (printer_notes=~/.*PRINTER_VENDOR_PRUSA3D.*/ and printer_notes=~/.*PRINTER_MODEL_MK(2.5|3).*/ and single_extruder_multi_material)"

Safely ejected the SD card.
Inserted SD card into MK3S.
File incomplete.

Removed card, brought it back to PC. File is now corrupted: Everything past 0xffff has been trashed!
The last part of the file is:
0000ffc0: 2e30 3037 3832 0a47 3120 5831 3134 2e36 .00782.G1 X114.6
0000ffd0: 3537 2059 3130 332e 3637 3920 4530 2e30 57 Y103.679 E0.0
0000ffe0: 3132 3930 0a47 3120 5831 3134 2e35 3638 1290.G1 X114.568
0000fff0: 2059 3130 342e 3030 3820 4530 2e30 3038 Y104.008 E0.008
00010000: ffff ffff ffff ffff ffff ffff ffff ffff ................

0047b860: ffff ffff ffff ffff ffff 0a ...........

That's 0x46B86A (4634730) bytes of badness.

Posted : 31/03/2019 1:19 am
dclaar
(@dclaar)
Eminent Member
Re: File incomplete - gcode issue??

I realized that what I wrote didn't make sense, so I took the Prusa out of the loop. I still get corrupted files. I tried a different PC.
I tried a different adapter. Tried a different TF card, but it had a bad block. So finally tried a full size SD card, and it seems to have worked fine.

Windows doesn't think that the original TF card is bad, but reformatting it seems to have made the problem go away. ¯\_(ツ)_/¯

Posted : 31/03/2019 4:02 am
Share: