Notifications
Clear all

Another "File Incomplete" Thread  

  RSS
WillGIam
(@willgiam)
New Member
Another "File Incomplete" Thread

Hey guys,

Since yesterday Im very frustrated with my prusa Mk3S+ with MMU2S. I got the "File Incomplete" error for the first time. First I tried the hardware - different SD card, reformatting old SD card, etc... nothing worked with this gcode.

I tried different file name, different, model, changed to standard filament settings, standard printer settings and standard print settings. At the moment I cant slice a MMU print with the standard profiles - I really dont get why.

I found out, that the error is connected to the MK3S+ MMU2S profile. When Im choosing the "single" version I can print and dont get the error. 

Does anybody has an idea what could cause the error here? 

 

Best regards 
William

Posted : 18/12/2023 9:50 am
Thejiral
(@thejiral)
Noble Member
RE:

That sounds like something in the start or rather end-g-code was changed. It is the kind of error you get when you delete the end-g-code in the slicer altogether for example (or something is missing that the Prusa deems essential). 
You should have a look how those g-codes look like in fresh default settings. 

Can you click that error away and start the print nonetheless afterwards?

This post was modified 4 months ago 2 times by Thejiral

Mk3s MMU2s, Voron 0.1, Voron 2.4

Posted : 18/12/2023 12:32 pm
WillGIam
(@willgiam)
New Member
Topic starter answered:
RE: Another "File Incomplete" Thread

Hi, 

Thanks for your reply. I compared both profiles and checked the start and end gcodes. Even with fresh default settings there is no way for the non single MMU Profile. 
This is the endcode of the standard single profile:

{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+1, max_print_height)} F720 ; Move print head up{endif}
G1 X0 Y210 F7200 ; park
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+49, max_print_height)} F720 ; Move print head further up{endif}
G1 E2 F5000
G1 E2 F5500
G1 E2 F6000
G1 E-15 F5800
G1 E-20 F5500
G1 E10 F3000
G1 E-10 F3100
G1 E10 F3150
G1 E-10 F3250
G1 E10 F3300

M140 S0 ; turn off heatbed
M107 ; turn off fan
M702 C
G4 ; wait
M221 S100 ; reset flow
M900 K0 ; reset LA
{if print_settings_id=~/.*(DETAIL @MK3|QUALITY @MK3|@0.25 nozzle MK3).*/}M907 E538 ; reset extruder motor current{endif}
M104 S0 ; turn off temperature
M84 ; disable motors
; max_layer_z = [max_layer_z]

And here we got the MMU profile:

{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+1, max_print_height)} F720 ; Move print head up{endif}
G1 X0 Y210 F7200 ; park
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+49, max_print_height)} F720 ; Move print head further up{endif}
{if has_wipe_tower}
G1 E-15 F3000
{else}
G1 E2 F5000
G1 E2 F5500
G1 E2 F6000
G1 E-15 F5800
G1 E-20 F5500
G1 E10 F3000
G1 E-10 F3100
G1 E10 F3150
G1 E-10 F3250
G1 E10 F3300
{endif}

M140 S0 ; turn off heatbed
M107 ; turn off fan

; Unload filament
M702 C

G4 ; wait
M221 S100 ; reset flow
M900 K0 ; reset LA
{if print_settings_id=~/.*(DETAIL @MK3|QUALITY @MK3|SOLUBLE|@0.25 nozzle MK3).*/}M907 E538 ; reset extruder motor current{endif}
M104 S0 ; turn off temperature
M84 ; disable motors
; max_layer_z = [max_layer_z]

Maybe you can check if its the same for you? 

When clicking to proceed and start the print everything is fine. I only tried it once, but the print was like expected.

Have a nice day

William

Posted : 18/12/2023 12:38 pm
Thejiral
(@thejiral)
Noble Member
RE: Another "File Incomplete" Thread

I can have a look in the evening. Can you also post the start-gcode?

Mk3s MMU2s, Voron 0.1, Voron 2.4

Posted : 18/12/2023 1:21 pm
WillGIam
(@willgiam)
New Member
Topic starter answered:
RE: Another "File Incomplete" Thread

 

Hi,

Sure.

For MMU:

M862.3 P "[printer_model]" ; printer model check
M862.1 P[nozzle_diameter] ; nozzle diameter check
M115 U3.13.2 ; tell printer latest fw version
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S[first_layer_temperature] ; set extruder temp
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
M109 S[first_layer_temperature] ; wait for extruder temp
G28 W ; home all without mesh bed level
G80 X{first_layer_print_min[0]} Y{first_layer_print_min[1]} W{(first_layer_print_max[0]) - (first_layer_print_min[0])} H{(first_layer_print_max[1]) - (first_layer_print_min[1])} ; mesh bed levelling

; Send the filament type to the MMU unit.
; E stands for extruder number, F stands for filament type (0: default; 1:flex; 2: PVA)
M403 E0 F{"" + ((filament_type[0]=="FLEX") ? 1 : ((filament_type[0]=="PVA") ? 2 : 0))}
M403 E1 F{"" + ((filament_type[1]=="FLEX") ? 1 : ((filament_type[1]=="PVA") ? 2 : 0))}
M403 E2 F{"" + ((filament_type[2]=="FLEX") ? 1 : ((filament_type[2]=="PVA") ? 2 : 0))}
M403 E3 F{"" + ((filament_type[3]=="FLEX") ? 1 : ((filament_type[3]=="PVA") ? 2 : 0))}
M403 E4 F{"" + ((filament_type[4]=="FLEX") ? 1 : ((filament_type[4]=="PVA") ? 2 : 0))}

{if not has_single_extruder_multi_material_priming}
;go outside print area
G1 Y-3 F1000
G1 Z0.4 F1000
; select extruder
T[initial_tool]
; initial load
G1 X55 E29 F1073
G1 X5 E29 F1800
G1 X55 E8 F2000
G1 Z0.3 F1000
G92 E0
G1 X240 E25 F2200
G1 Y-2 F1000
G1 X55 E25 F1400
G1 Z0.2 F1000
G1 X5 E4 F1000
G92 E0
{endif}

M221 S{if layer_height<0.075}100{else}95{endif}
G92 E0

; Don't change E values below. Excessive value can damage the printer.
{if print_settings_id=~/.*(DETAIL @MK3|QUALITY @MK3|SOLUBLE).*/}M907 E430 ; set extruder motor current{endif}
{if print_settings_id=~/.*(SPEED @MK3|DRAFT @MK3).*/}M907 E538 ; set extruder motor current{endif}

And for the single:

M862.3 P "[printer_model]" ; printer model check
M862.1 P[nozzle_diameter] ; nozzle diameter check
M115 U3.13.2 ; tell printer latest fw version
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S[first_layer_temperature] ; set extruder temp
M140 S[first_layer_bed_temperature] ; set bed temp
Tx
M190 S[first_layer_bed_temperature] ; wait for bed temp
M109 S[first_layer_temperature] ; wait for extruder temp
G28 W ; home all without mesh bed level
G80 X{first_layer_print_min[0]} Y{first_layer_print_min[1]} W{(first_layer_print_max[0]) - (first_layer_print_min[0])} H{(first_layer_print_max[1]) - (first_layer_print_min[1])} ; mesh bed levelling

;go outside print area
G1 Y-3 F1000
G1 Z0.4 F1000
; select extruder
Tc
; purge line
G1 X55 F2000
G1 Z0.3 F1000
G92 E0
G1 X240 E25 F2200
G1 Y-2 F1000
G1 X55 E25 F1400
G1 Z0.2 F1000
G1 X5 E4 F1000

M221 S{if layer_height<0.075}100{else}95{endif}
G92 E0

; Don't change E values below. Excessive value can damage the printer.
{if print_settings_id=~/.*(DETAIL @MK3|QUALITY @MK3).*/}M907 E430 ; set extruder motor current{endif}
{if print_settings_id=~/.*(SPEED @MK3|DRAFT @MK3).*/}M907 E538 ; set extruder motor current{endif}

Thanks a lot,

William

Posted : 18/12/2023 2:31 pm
Thejiral
(@thejiral)
Noble Member
RE: Another "File Incomplete" Thread

Hm, the only difference to my settings I could find is that in my start gcode the G80 is not dynamic but that has probably something to do with the older version. Seems like it is not that G-code. At least I can't see anything.

Have you tried installing a new default MMU Profile on the slicer and is the problem persisting in that case?

Mk3s MMU2s, Voron 0.1, Voron 2.4

Posted : 18/12/2023 5:21 pm
WillGIam
(@willgiam)
New Member
Topic starter answered:
RE: Another "File Incomplete" Thread

Hi,

I´m sorry for my late reply. I wanted to make sure Ive tried everything. Today I deinstalled Prusa Slicer and deleted all user profiles from my pc. After that I reinstalled everything. 

 

I´m still getting the same result. The MMU Profile is seen as incomplete... I really don´t know what to do.

 

William

Posted : 20/12/2023 3:38 pm
Thejiral
(@thejiral)
Noble Member
RE: Another "File Incomplete" Thread

Have you contacted Prusa Live chat? It is mysterious to me as well, can't be the Slicer then, can it. The only thing I could think of, as you tried already other SD-cards, is to downgrade the MMU firmware, given the reports about some issues with newer firmware versions in general. That's a blind shot though. 

Mk3s MMU2s, Voron 0.1, Voron 2.4

Posted : 21/12/2023 10:05 am
Peter_B
(@peter_b)
Member
RE: Another "File Incomplete" Thread

Hi, as per this support page https://help.prusa3d.com/article/file-incomplete-continue-anyway_1847 it is a known bug. It should be corrected in fw 3.14, hopefully soon, as it renders MMU unusable. 

Posted : 21/12/2023 4:19 pm
toy4x4 liked
G Bell
(@g-bell)
Eminent Member
RE: Another "File Incomplete" Thread

I get this error with the MMU3 when there is a color that isn't used after some z-level.  It doesn't seem to be a huge problem as for "Continue anyway?" I just select "Yes" and it appears the print is perfect.  Maybe it has something to do with the wipe tower?

Posted : 28/12/2023 9:10 pm
G Bell
(@g-bell)
Eminent Member
RE: Another "File Incomplete" Thread

After further investigation, my models that give this error all use 2 colors, and one color is not used above a certain z-level.  Thus, the wipe tower is not needed at this z-level. Perhaps the wipe tower is not terminated correctly?

Posted : 28/12/2023 10:14 pm
delwilson6241@gmail.com
(@delwilson6241gmail-com)
Active Member
RE: Another "File Incomplete" Thread

I'm seeing this too.  I suspect the slicer settings for the printer type are not always aligned with the printer firmware.  I ignore the warning and it seems to print fine. 

Posted : 01/01/2024 11:30 pm
Mark
 Mark
(@mark-19)
Member
RE: Another "File Incomplete" Thread

I am getting this error as well, but on my prints, it just doesn't print the 2nd color (of my 2 color print).  The two extruders show up in the slicer, but I can't get it to print the other color...

Posted : 10/01/2024 6:30 am
Komet_82
(@komet_82)
Eminent Member
RE: Another "File Incomplete" Thread

I have the exact same error here using MK3S & MMU2S

Posted : 12/01/2024 3:48 pm
Peter_B
(@peter_b)
Member
RE:

Here is the cause and solution https://github.com/prusa3d/Prusa-Firmware/pull/4507

Posted : 13/01/2024 7:27 am
Share: