search

prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.76k stars 1.93k forks source link

Crashing Printer When No Infill #13297

Open AdamS1187 opened 2 months ago

AdamS1187 commented 2 months ago

Description of the bug

Just updated to version PrusaSlicer 2.8.0. I was tuning my printer, Elegoo Neptune 4 Plus, and everything was going fine until I tried printing in vase mode. Every time I would upload the gcode to the printer the printer would restart. I went back and tried printing with normal settings and the print would start fine. I tested each setting individually and figured out it was the infill that was causing the problem. I then tried printing in vase mode in Cura and had no issues.

Thanks Adam

Project file & How to reproduce

Shape-Box.zip

Checklist of files included above

Version of PrusaSlicer

2.8.0

Operating system

Windows 10

Printer model

Elegoo Neptune 4 Plus

gaellafond commented 2 months ago

Did you disable "Binary GCode"? Not all printer supports that feature.

Preferences > Other > Use binary G-code when the printer supports it

You can also disable it for your printer

Printers > General > Advanced > Supports binary G-code

AdamS1187 commented 2 months ago

I disabled binary code but the problem is still there. Right after the printer homes I get a flash from the led lights and the printer goes into a reboot. If I turn on infill the print starts normally.Sent from Samsung Galaxy smartphone. -------- Original message --------From: Gael Lafond @.> Date: 8/27/24 9:05 PM (GMT-06:00) To: prusa3d/PrusaSlicer @.> Cc: AdamS1187 @.>, Author @.> Subject: Re: [prusa3d/PrusaSlicer] Crashing Printer When No Infill (Issue

13297)

Did you disable "Binary GCode"? Not all printer supports that feature.

Preferences > Other > Use binary G-code when the printer supports it

You can also disable it for your printer

Printers > General > Advanced > Supports binary G-code

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Jan-Soustruznik commented 2 months ago

Hello, @AdamS1187 , I dont know if we can help you... Did you try to flash FW on Printer or check the start g-code?

gaellafond commented 2 months ago

That sounds like a problem with the printer. Maybe there is not enough power going to the printer. That could be an issue with the power supply. Did you try to contact Elegoo?

AdamS1187 commented 2 months ago

It's funny that it only started after updating prusaslicer and only with no infill. Printer works fine with cura. I will open a ticket with elegoo.Sent from Samsung Galaxy smartphone. -------- Original message --------From: Gael Lafond @.> Date: 9/3/24 7:12 PM (GMT-06:00) To: prusa3d/PrusaSlicer @.> Cc: AdamS1187 @.>, Mention @.> Subject: Re: [prusa3d/PrusaSlicer] Crashing Printer When No Infill (Issue

13297)

That sounds like a problem with the printer. Maybe there is not enough power going to the printer. That could be an issue with the power supply. Did you try to contact Elegoo?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

AdamS1187 commented 2 months ago

The printer has the most current firmware.I will have to compare the start code with what's in cura since the printer prints normally with cura.Sent from Samsung Galaxy smartphone. -------- Original message --------From: Jan Soustružník @.> Date: 9/3/24 8:16 AM (GMT-06:00) To: prusa3d/PrusaSlicer @.> Cc: AdamS1187 @.>, Mention @.> Subject: Re: [prusa3d/PrusaSlicer] Crashing Printer When No Infill (Issue

13297)

Hello, @AdamS1187 , I dont know if we can help you... Did you try to flash FW on Printer or check the start g-code?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Jan-Soustruznik commented 2 months ago

Hello, @AdamS1187 , did you find some differences?

gaellafond commented 2 months ago

It's funny that it only started after updating prusaslicer and only with no infill.

I have a feeling that's unrelated. The sequence of command might just be tipping the printer over its limit. It's just a coincidence that it happens with those settings.

Maybe the printer is struggling with all the comments at the beginning of the file? You can edit the GCode file and remove every lines that starts with a semi-colon ";". It's possible that the printer is trying to interpret them and it's just a bit too much for its processor...

Jan-Soustruznik commented 2 months ago

@gaellafond I dont know If we can get some solution. I suggest to ask printer manufacturer for some solution ...

gaellafond commented 2 months ago

@gaellafond I dont know If we can get some solution. I suggest to ask printer manufacturer for some solution ...

You are probably right, but it's worth diagnosing the issue. It would be much easier for Elegoo to fix the issue if we can say "that sequence of gocde crash the printer" rather than "my printer crash when slicing that part with those settings with this slicer...". Also, if we can isolate the bug, it might be possible to find a workaround to prevent it from happening again, until Elegoo fix it in firmware (assuming it's a bug in the firmware).