Filament runout not working

[Neme77]

Description

the filament sensor is correctly detected I checked its status with m119, during printing if active the sensor by setting smart or on in TFT mode the printing stops even if the filament is present and the message filament finished appears on the display.
In lcd emulation mode printing starts and after a few seconds the m600 command is performed.

Install a smart filament detector

Hardware Variant

TFT35 V3_0

BIGTREE_TFT35_V3.0.26 & Trigorilla 14 and Marlin 2.0.5.3 Bugfix

Additional Information

• Include a ZIP file containing your Configuration.h or use Pastebin and paste a link in this issue.
• Provide pictures or links to videos that clearly demonstrate the issue.

[poumsoon]

I also have the same problem.
When printing through MKS MINI 12864, the filament sensor works well, but it does not work when connected to TFT28 or TFT35 V2.
Testing with the May 26 firmware has the same problem.

[poumsoon]

I also have the same problem.
When printing through MKS MINI 12864, the filament sensor works well, but it does not work when connected to TFT28 or TFT35 V2.
Testing with the May 26 firmware has the same problem.

I knew the cause of the problem. In the case of touch LCD, the filament sensor must be connected to the port of the LCD. Refer to the TFT LCD manual.
  I didn't expect anything at all, and I think I've been looking for this and that for three days.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[oldman4U]

kisslorand recommends to do the following:
Send M75 to Marlin when print begins. Marlin doesn't know that the print is started so no filament runout warnings. It's not a bug.
You can put M75 in your Start-Gcode and you're set. That's what I did.

Please let us know if this solves your problem

Thank you

[github-actions]

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.