Occasionally the printer receives the M1 command even though it is blocked in the configuration
Reeinstalei o octoprint. Verifiquei que o M1 e M0 está bloqueado
No! don't think that's could help
No!
You can download this in OctoPrint's System Information dialog ... no bundle, no support! ) octoprint-systeminfo-20240112204415.zip (172.1 KB)
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Firmware Name: Marlin bugfix-2.1.x (Dec 18 2023 20:59:35)Extruder Count : 1Machine Type : Ender-3 PROProtocol Version : 1.0
*OctoPrint 1.9.3OctoPi 1.0.0 (build 2023.10.09.151442)
iduarte:
Did running in safe mode solve the problem?
No!
consider trying in safe mode to rule out a plugin issue.
if the issue persists you probably need to enable serial logging in the settings to troubleshoot further.
Thanks for the quick response.
Found an workaround here. Seems to be an old issue.
opened 05:35PM - 08 Feb 22 UTC
closed 07:19PM - 12 Feb 22 UTC
### Description
I have successfully operated an SKR Mini E3 V2.0 with a TFT E3 … V3.0 on an Ender 3 with BL Touch for months.
After converting to an SKR Mini E3 V3.0, I tried flashing the preconfigured firmware from Github. The BL Touch is plugged into the probe slot. When that particular firmware didn't work, I plugged the BL Touch's two wires into the Z endstop and flashed the other firmware that was specifically made for it. Again no success. Unfortunately, a quick test was not possible.
So I configured and flashed the firmware myself. Now everything works as it should be. On this occasion I flashed the current firmware for the TFT display and I was happy that everything went well and is up to date.
The joy didn't last long. During a longer print I came to the printer and noticed that the print was paused with an M1 stop and the display asked me to press the button to continue. The nozzle had melted into the component and the print was ruined. The print was made from the SD card slot on the TFT display. The error does not appear when printing from the SD card slot on the board.
I then did a little research and came across indications that machine codes that begin with M1.. (e.g. M117) may not arrive completely at the printer and only an M1 is evaluated.
I helped myself in this regard by deactivating M0 & M1 in the Marlin firmware. Even if an M0 or M1 is sent to the printer by mistake, it is not evaluated and a "Command unknown" message appears on the TFT display.
However, this is only a temporary solution and should not remain so in the long term.
Is this problem generally known or does it only appear on a few devices?
Soon I want to flash an older firmware on the TFT display and try out whether the cause is the update to the display or whether the board tends to errors when receiving serial data.
Does anyone have a final solution?
### Steps to reproduce
randomly during print
### Additional Information
config & binary at : https://github.com/Seelenkind/Ender-3-SKR-Mini-E3-V3-Marlin-Firmware
1 Like
system
April 12, 2024, 5:11pm
5
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.