Marlin 2.1 M112 issued when using ESP3D/ESP8266

[rickjs]

Marlin 2.1.2.1 on SKR 1.4 board, M112 is issued(some error is causing this) when running, hotend 250c and bed 60c, print idle thru ESP3D/ESP8266 but not when running Octoprint thru USB.

[luc-github]

What do you mean by M112 error?
M112 is emmergency stop GCODE command not an error

[rickjs]

Either way, ESP3D or ESP8266 is causing it?

[rickjs]

Octoprint has a plugin called Netprint which uses socket, ESP3D supports socket. This is not the issue here because ESP3D webui talks directly to the ESP8266 I guess, so this eliminates wifi.

[luc-github]

what parameters do you use on this plugin use to communicate with esp3d by network ? to understand what is using

[rickjs]

Not sure I follow, "I suggest you to send The commands to heat using and close immediatly communication with esp3d as well as octoprint it will tell you if issue comme from esp8266 sending something when nothing is connected to it" Think I controlled hotend from ESP3D webui directly, even disconnecting Octoprint.

[luc-github]

esp3d does not control anything it just forward commands coming from esp3d- webui or your net plugging

[luc-github]

so I suggest you to send the heat command and disconnect octo print and webui if open
to see if you reproduce issue

[rickjs]

I don't have the printer with me but the socket connection is shown on ESP3D ui, that's pasted in the Octoprint's additonal serial port list. But as I said, I tested not using Octoprint, just using the ESP3D webui, same problem.

[rickjs]

I won't be at printer location until Sat. so won't do further testing until then. Thanks

[luc-github]

Any update ?

[rickjs]

Yes, at first just seemed to be with wifi, then I got it with usb. Changing settings on Octoprint to not cancel was able to get thru most of print. Running into extruded pieces let behind might be creating a problem with the sensorless drivers, sensing collisions. Printing PETG is a problem, readjusting extruder settings in Prusaslicer.

[luc-github]

Sorry you wrote before you have issue without octoprint - is that correct ? if that the case you should not search on octprint setting but on EMI noise on your board
As someone wrote 🤓 :
As Sherlock Holmes once said, "If you eliminate the impossible whatever remains, however improbable, must be the truth",

[luc-github]

I close issue as not esp3d related

[rickjs]

I thought it may have been related to wifi but it happened with usb also