BIGTREETECH-TouchScreenFirmware TFT35 throws M14 E unknown command

Description

When I print something I get error unknown command M14 E

Steps to reproduce

Start printing over octoprint and get this error

Print withouth errors

Hardware Variant

TFT35 V3

TFT Firmware Version & Main Board Firmware details

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.

Oct 16 '24 07:10 Blisk

This is an error thrown by the motherboard host software, the display just reports it. I'm not sure what host software you are running, but Marlin doesn't understand M14, so it would report the error you got. (https://marlinfw.org/docs/gcode/M010-M011.html)

Make sure to select the correct gcode dialect when slicing.

Oct 21 '24 07:10 rondlh

it is also Marlin 2.1.X on SKR mini 3.0

Oct 21 '24 08:10 Blisk

This error is usually caused by electromagnetic interference on the serial port. SKR mini V3 boards suffer a lot from this

Oct 26 '24 17:10 radek8

This error is usually caused by electromagnetic interference on the serial port. SKR mini V3 boards suffer a lot from this

I have now shielded sreial cable

Oct 26 '24 17:10 Blisk

It doesn't always help. It looks like a bad design of the board, maybe the interference from the stepper motor controller is oscillating to the serial port. Put the cables as far away from the stepper motor controller as possible.

Oct 26 '24 17:10 radek8

It doesn't always help. It looks like a bad design of the board, maybe the interference from the stepper motor controller is oscillating to the serial port. Put the cables as far away from the stepper motor controller as possible.

OK I will do that also.

Oct 26 '24 17:10 Blisk

A lot of people here complain about this problem and 90% of them have one thing in common - SKR mini V3.0

Oct 26 '24 19:10 radek8

@Blisk Do you always get the "M14 E" error, or did it just happen once? If it only happened once then, like @radek8 mentioned, it could be a serial communication reliability issue. In that case lower your serial baud rate to 115200 baud, shorten your serial cable as much as possible and keep the serial cable away from the stepper cables.

Nov 01 '24 06:11 rondlh

@Blisk Do you always get the "M14 E" error, or did it just happen once? If it only happened once then, like @radek8 mentioned, it could be a serial communication reliability issue. In that case lower your serial baud rate to 115200 baud, shorten your serial cable as much as possible and keep the serial cable away from the stepper cables.

yes that error happend many times and I have shielded serial cable.

Nov 01 '24 07:11 Blisk

Is the error code still the same, or is it changing and is different each time? (text in quotation marks)

Nov 01 '24 10:11 radek8

code is mostly the same

Dec 12 '24 21:12 Blisk

Hi

I checked your FW but you only have TFT28 firmware i use TFT35 display.

What I need to do here?

From: Kiss Lorand @.> Sent: Sunday, January 5, 2025 12:41 AM To: bigtreetech/BIGTREETECH-TouchScreenFirmware @.> Cc: Blisk @.>; Mention @.> Subject: Re: [bigtreetech/BIGTREETECH-TouchScreenFirmware] TFT35 throws M14 E unknown command (Issue #2960)

@Blisk https://github.com/Blisk

Test the FW from my repo https://github.com/kisslorand/BTT-TFT-FW . Some monkey loitering around @.*** https://github.com/rondlh ) might tell you to beware because that FW might burn your house, empty your bank accounts, break your printer or any other stupidity he comes up with but you should be smart enough to think for yourself. Other people did the switch and never looked back.

— Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/2960#issuecomment-2571440926 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVFAORSHL4U26U3KW3DSVD2JBWRPAVCNFSM6AAAAABQAY3EQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGQ2DAOJSGY . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AAVFAOU5H3IQFGYG6T6CUJL2JBWRPA5CNFSM6AAAAABQAY3EQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUZIUJR4.gif Message ID: @.*** @.***> >

Jan 05 '25 11:01 Blisk

@Blisk that unknown command messages are probably fixed by PR #2970. Increase the value for new param tx_delay (you can change it also at runtime from the Feature menu) until the issue is no more present.

Feb 07 '25 10:02 digant73

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.

Jul 29 '25 14:07 github-actions[bot]