bigtreetech / BIGTREETECH-TouchScreenFirmware

support TFT35 V1.0/V1.1/V1.2/V2.0/V3.0, TFT28, TFT24 V1.1, TFT43, TFT50, TFT70
GNU General Public License v3.0
1.3k stars 1.65k forks source link

[BUG] PrusaSlicer: "Filament Runout"-Error #2027

Closed omexlu closed 3 years ago

omexlu commented 3 years ago

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. Don't know if it has something to do with the TFT Firmware, but possible. If i slice with Cura i don't have this issue.

EDIT: Maybe there are some wrong codes in the generated file :/

oldman4U commented 3 years ago

Slice the same object in the two slicers and compare the gcode.

This repository is about possible bugs and feature requests related to the TFT firmware.

omexlu commented 3 years ago

I have done it and compared not a big difference, another user tell me that he has this problem with cura, so very strange behavior, I can be a possible big in TFT firmware.

Normally the slicer should not do any big difference but here it's the case, it should be investigated.

omexlu commented 3 years ago

Here is the same objects sliced with cura: https://easyupload.io/7k323y

576e229e-ac8a-4150-b38b-7e3613ce5914

oldman4U commented 3 years ago

The TFT sends the commands written in the gcode file to Marlin.

Do you have a filament sensor?

omexlu commented 3 years ago

Yes, of course, otherwise it would be obvious where the problem lies.

But the error message comes right at the beginning and also only with prusaslicer at Cura not.

radek8 commented 3 years ago

Is it the same problem if you print from Marlins?

omexlu commented 3 years ago

Dont havent try this i only peints Form screen over TFT screen,but only happends with prusaslicer.

oldman4U commented 3 years ago

I have been testing both gcode files and they printed just fine without any problem.

Sorry that I ask, but the sensor is connected to the TFT?

omexlu commented 3 years ago

Yes it's connected to TFT, unfortantly with me I get this weird error and dont know why it only happens with prusaslicer :/

Maybe @kisslorand has a solution for that, he was able to find out my last problem with filament error, maybe its somehow related :)

I forgot to mention that after "OK" confirmation of this error message, the display also hangs and I have to restart the printer, also indicates a bit of a firmware problem.

omexlu commented 3 years ago

I tried with the settings from cura (start / endcode) same result,disabling the filament sensor works for a few seconds then the screen freeze,there must be either a bug in the tft firmware or in prusaslicer (profio for genius).

oldman4U commented 3 years ago

I can not reproduce the issue so I can not help.

Sorry

omexlu commented 3 years ago

Thanks anyway, also do not know what this is :/

omexlu commented 3 years ago

Check out my thread here, they are also assuming a firmware issue related to PrusaSlicer: https://forum.prusaprinters.org/forum/prusaslicer/prusaslicer-filament-runout-error/#post-464743

oldman4U commented 3 years ago

See #2040 maybe related

omexlu commented 3 years ago

Yes seems so that its related, i cant use prusaslicer because this errors. Cura Works fine so i purged/deleted prusaslicer.

oldman4U commented 3 years ago

Please close this ticket in case you are not looking for a solution anymore.

Happy printing

github-actions[bot] commented 6 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.