PrusaSlicer: "Filament Runout"-Error
 
Notifications
Clear all

PrusaSlicer: "Filament Runout"-Error  

  RSS
Omexlu
(@omexlu)
Active Member
PrusaSlicer: "Filament Runout"-Error

Hello,

I have a strange problem with my Artillery Genius in connection with the PrusaSlicer, as soon as I want to start a print it shows me the error "Filament Runout", but this only happens when I have sliced with the PrusaSlicer (so I assume an error here, or a command that does not fit in the start code).

Attached is the G-Code file that was sliced with PrusaSlicer:

https://easyupload.io/ojbql3?fbclid=IwAR2sn1Xi7Wv354WgANiavz1fJZfGZq7e9Nt8flA1zgAhdsxXZhV3a_UmOCE

PS. Just wanted to try the first print with PrusaSlicer then this error 😛

Posted : 25/06/2021 3:33 pm
karl-herbert
(@karl-herbert)
Illustrious Member
RE: PrusaSlicer: "Filament Runout"-Error
Posted by: @omexlu

Hello,

I have a strange problem with my Artillery Genius in connection with the PrusaSlicer, as soon as I want to start a print it shows me the error "Filament Runout", but this only happens when I have sliced with the PrusaSlicer (so I assume an error here, or a command that does not fit in the start code).

Attached is the G-Code file that was sliced with PrusaSlicer:

https://easyupload.io/ojbql3?fbclid=IwAR2sn1Xi7Wv354WgANiavz1fJZfGZq7e9Nt8flA1zgAhdsxXZhV3a_UmOCE

PS. Just wanted to try the first print with PrusaSlicer then this error 😛

Hello and welcome to the Prusaforum!

Have you selected the correct printer profile in PS? https://3dprintbeginner.com/artillery-genius-profile-for-simplify3d-and-prusa-slicer/#Artillery_Genius_Profile_for_Prusa_Slicer

wbr,

Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 25/06/2021 5:37 pm
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

Hello,

Yes I have loaded the profile that was offered in PrusaSlicer, there is the Artillery Genius listed.

An external file I have not downloaded or imported because I thought that PrusaSlicer supports the so as is offered.

Posted : 25/06/2021 5:59 pm
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

Maybe an option to copy start/end code from cura into pursaslicer, or this a bad idea?🙈

Posted : 26/06/2021 10:31 am
karl-herbert
(@karl-herbert)
Illustrious Member
RE: PrusaSlicer: "Filament Runout"-Error

@omexlu

This should work so far. You only have to pay attention to the syntax if slicer internal variables are used. In any case you can adjust Start and End Gcode in PrusaSlicer as you like.
Just compare the program header /Cura/PrusaSlicer and note the differences. Probably an unknown command will trigger this reaction.

wbr,

Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 26/06/2021 11:57 am
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

Hello,

As far I know cura don't use any variables in start/end-code.

Here is the gcode from pursaslicer;

https://easyupload.io/ojbql3?fbclid=IwAR2sn1Xi7Wv354WgANiavz1fJZfGZq7e9Nt8flA1zgAhdsxXZhV3a_UmOCE

And here from cura:

https://easyupload.io/7k323y

Cura don't have variables in start / end-code, but I would happy to keep the startcode from pursaslicer but there are like you said any command that trigger this reaction and would like to know which one so that I can modify or remove it without replacing all.

Maybe someone can help me to find out the propably failed command.

 

Posted : 26/06/2021 12:04 pm
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

So I tried to take the Gcode from Cura, here the same, so is more generally with some problem with PrusaSlicer and the Genius :/

Posted : 28/06/2021 3:15 am
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

So the error is not in the start/end code but is somewhere in between, when I turn off the filament sensor it goes for a moment without this error message but then the screen freezes.

Posted : 28/06/2021 3:34 am
Neophyl
(@neophyl)
Famed Member
RE: PrusaSlicer: "Filament Runout"-Error

I'm sorry but I'm not clicking on some unknown download site just to check out some gcode.  You can zip up both gcode files into a zip file and attach it to the forum.  Much safer for those who have an interest in helping.

Posted : 28/06/2021 7:45 am
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

Sure here the zipped files.

 

Attachment removed
Posted : 28/06/2021 7:59 am
Neophyl
(@neophyl)
Famed Member
RE: PrusaSlicer: "Filament Runout"-Error

You have some dubious ordering on your PS start gcode.  However there is notrhing in the gcode that can or would trigger a filament runout.  That has to be related to your firmware.  Its firmware that triggers that and puts a message up on the screen, its a run time message and not something that the slicer knows anything about or thats included in the gcode.

You have 2 totally different start up routines.

Your Cura startup does this :-

M140 S60 <-starts heating the bed
M105
M190 S60 <- waits for bed to get to full temperature
M104 S200 <- starts heating the nozzle
M105
M109 S200 <- Waits for the nozzle to get to printing temperaturte
M82 ;absolute extrusion mode <-sets absolute extrusion mode
G28 ; home all axes
M420 S1 ; take MBL-settings
M117 Purge extruder
G92 E0 ; reset extruder

;This is a basic purge/prime line
G1 Z1.0 F3000 ; move z up little to prevent scratching of surface
G1 X2 Y20 Z0.3 F5000.0 ; move to start-line position
G1 X2 Y200.0 Z0.3 F1500.0 E15 ; draw 1st line
G1 X2 Y200.0 Z0.4 F5000.0 ; move to side a little
G1 X2 Y20 Z0.4 F1500.0 E30 ; draw 2nd line
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little to prevent scratching of surface

It then goes on to print the skirt and the rest of the print.

Your Prusa Slicer start up though follows the following process

M201 X1000 Y1000 Z1000 E5000 ; sets maximum accelerations, mm/sec^2
M203 X200 Y200 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1250 R1250 T1250 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X8.00 Y8.00 Z0.40 E1.50 ; sets the jerk limits, mm/sec
M205 S0 T0 ; sets the minimum extruding and travel feed rate, mm/sec
This sets and over rides any hardware settings from your firmware. If these do not match the firmware settings this CAN cause problems. Make absolutely sure these values are correct for your machine. If you aren't sure then change the option in PS to only use for time estimate in Printer Settings>Machine Limits.  

M107 ; disable fan
;TYPE:Custom
; Initial setups
G90 ; use absolute coordinates
M83 ; extruder relative mode <- your Cura settings are using absolute. Should be ok but its a difference to be aware of and depending on the firmware of your printer it might not like it.
M220 S100 ; reset speed factor to 100%
M221 S100 ; reset extrusion rate to 100%

; Set the heating
M190 S65 ; wait for bed to heat up
M104 S210 ; start nozzle heating but don't wait <- this is different, in Cura you are waiting for your nozzle to be heated up first.

; Home
G1 Z3 F3000 ; move z up little to prevent scratching of surface <-this is dangerous as you are telling it to move when your Home position has NOT been established.
G28 ; home all axes
M420 S1 ; take MBL-settings
G1 X3 Y3 F5000 ; move to corner of the bed to avoid ooze over centre

; Wait for final heating
M109 S210 ; wait for the nozzle to heat up
M190 S65 ; wait for the bed to heat up <- you have already waited for the bed to heat up, this line is pointless.

; Return to prime position, Prime line routine
G92 E0 ; Reset Extruder
G1 Z3 F3000 ; move z up little to prevent scratching of surface
G1 X10 Y.5 Z0.25 F5000.0 ; Move to start position
G1 X100 Y.5 Z0.25 F1500.0 E15 ; Draw the first line
G1 X100 Y.2 Z0.25 F5000.0 ; Move to side a little
G1 X10 Y.2 Z0.25 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
M221 S95

These lines should be at the start and not down here. As well as the M83 and G90 is duplicated.
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion

I agree with Rtyr from your thread on github, you should NOT be using the M420 UNTIL you actually have the bed sensor actually fitted.  It should not be on in the firmware or even plugged in.  You should have printed the brackets and everything  else needed when you had it stock and only after fitting everything correctly then enabling it in your printers firmware.  The firmware will have checks you can do from the lcd to make sure its all working.  Once you know that for certain, only then would you modify your start gcode to include the use of it.  At the moment its an unknown.  The first rule of debugging is to reduce the number of unknown factors and do and test 1 thing at a time.  Make a single change then test it.  Then make the next, test.  Only that way can you be sure.

Posted : 28/06/2021 9:28 am
Omexlu liked
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

As mentioned the Cura and Prusa settings are all default, here I have not changed anything except "M420 S1 ; take MBL-settings" added, which loads my mesh data (which is stored in the EEPROM). This has nothing to do with the BLT but that it loads the mesh leveling that is currently already stored in the EEPROM.

I also copied the settings (start/end code) from Cura completely, but again the same result or the TFT hangs.

Therefore I assume that this part may cause the problem:
M201 X1000 Y1000 Z1000 E5000 ; sets maximum accelerations, mm/sec^2
M203 X200 Y200 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1250 R1250 T1250 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X8.00 Y8.00 Z0.40 E1.50 ; sets the jerk limits, mm/sec
M205 S0 T0 ; sets the minimum extruding and travel feed rate, mm/sec

But I can't find this part in the start/end code, so how can I remove the above parts in PrusaSlicer?

Maybe this is causing the problems?

Thanks in advance.

Posted : 28/06/2021 10:00 am
Neophyl
(@neophyl)
Famed Member
RE: PrusaSlicer: "Filament Runout"-Error

I already pointed you to where those are.  Printer Settings> Machine Limits.  There is a dropdown in that section with choices for Emit to gcode, Use for time estimates and Ignore.  With Emit to gcode it adds them in to the gcode output.  With use for time estimates it just uses them for the time estimates and ignore it does nothing with them.  

As Rtyr already pointed out the included prusa profile is for a completely stock machine.  That doesn't have any mesh leveling and is for the stock firmware.  As soon as you start customising any part of that then its all bets off and you are responsible for getting it working.  

The BLT will be the device that is creating your mesh level data that is stored, so how can it have any to be recalled if the blt is not fully fitted ?  Its even worse if you have it enabled and plugged in but not actually fitted above the bed.  As that way it will be recording mesh data but it will be completely incorrect mesh data.  Do you have a different device to the blt already fitted that is creating mesh data ?  If you do then why do you need a blt ?

Posted : 28/06/2021 10:57 am
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

I will try it, mesh is loaded by MBL not by ABL.

These are two different things but loaded with the same Gcode.

Posted : 28/06/2021 11:00 am
Neophyl
(@neophyl)
Famed Member
RE: PrusaSlicer: "Filament Runout"-Error

If they are loaded by the same gcode command then they are the same thing.  Question for you then, whats the difference between ABL and MBL ?

Mesh Bed leveling is generating a mesh map of the irregularities in your bed surface to adjust them out in software.  Where theres a low spot it adjusts the mesh to account for it.  ABL is just an automated process to assist in leveling the bed.  Both need a sensor to gather that data.  On a prusa printer it uses the PINDA probe.  On your Artillery it sounds like you are fitting a BLT to do the same job.  The thing is, without it actually fitted its not going to produce any valid data.  So until it is. there's no point saving or recalling mesh data.  

Get your firmware into a known good working condition with the hardware you have fitted before adding it to the profile.  Its like trying to jump before you can even walk.

Posted : 28/06/2021 12:43 pm
Omexlu
(@omexlu)
Active Member
Topic starter answered:
RE: PrusaSlicer: "Filament Runout"-Error

I do the MBL by hand (via display) and then data is very well available.

Posted : 28/06/2021 12:59 pm
Share: