search

Jyers / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. | Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
http://marlinfw.org
GNU General Public License v3.0
2.14k stars 386 forks source link

M112 error on connect from Octoprint #1600

Open plucker opened 2 years ago

plucker commented 2 years ago

Description

I can't connect to my Ender 3v2 with octoprint. I reverted back to the 1.3.5 build and all is fine

Steps to Reproduce

  1. Power up printer
  2. connect to printer with Octoprint connect button

Expected behavior: Oct print successfully connects to the printer

Actual behavior: Octoprint reports an immediate disconnect with attached messages in the log

Additional Information from Octoprint terminal

Trying port /dev/ttyUSB0, baudrate 115200 Connecting to port /dev/ttyUSB0, baudrate 115200 Handshake attempt #1 with timeout 2.0s Connected to: Serial(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Send: N0 M110 N0125 Recv: \x0b\x9aÑ\x85ÑÕÍ\x81mismatch Recv: Error:Serial status mismatch Changing monitoring state from "Detecting serial connection" to "Error" Send: M112 Send: N1 M11232 Send: N2 M104 T0 S035 Send: N3 M140 S0102 Changing monitoring state from "Error" to "Offline after error" Connection closed, closing down monitor

plucker commented 2 years ago

I did look at that page and have all those settings correct and I have some insulating tape on the pin of the usb cable to prevent 5V coming in. Not sure why this would be different for the new version - it's always worked fine with 1.3.5.

plucker commented 2 years ago

That’s correct. I tried installing it twice, same result both times

plucker commented 2 years ago

I tried that and the machine was OK with the Meatpack line commented out. I'm just going to rebuild with it back in again to prove that that is the issue.

plucker commented 2 years ago

Nope I uncommented it still works fine, so I put the downloaded release build back on and that works fine as well. I don't understand, maybe I disturbed the tape on the 5V wire. I'll close this anyway as all appears well.

plucker commented 2 years ago

OK, re-opening it as it appears to be an intermittent issue.

ozonejunkieau commented 2 years ago

For what it's worth, I am also having this issue with the exact same hardware. I did just identify then that powering up the printer with the OctoPi host disconnected and then plugging it in worked to "reconnect". I'm not sure how often this will work, but figured I'd let someone know that it may be related to the serial startup sequence?

bushybluejeans commented 2 years ago

Glad it's not just me. Getting the same M112 error on Ender 3V2 with Octoprint on power up. (5V pin was masked).

Update: I removed a number of plugins from Octoprint, reverting to a more basic operating system and then used the settings here and restarted Octoprint. Everything okay so far on the last three prints.

nike12000 commented 2 years ago

I have also been having this same issue and it also seems to be erratic and intermittent. It’s hard to prove but if I home all before I connect it “seems” like it does not happen as often.

BlueWings172 commented 2 years ago

I have the same problem ever since I upgraded to 2.01 firmware. I have these Octoprint settings already.

Anyone figured a solution other than downgrading ?

bushybluejeans commented 2 years ago

I have the same problem ever since I upgraded to 2.01 firmware. I have these Octoprint settings already.

Anyone figured a solution other than downgrading ?

I was having this issue recently. The steps I took to rectify it were:

1) I removed any unused and unwanted plugins from Octoprint. 2) I then Formatted the SD card and flashed the new firmware to the printer. 3) I then systematically did a Reset to Default, followed by a Store Settings and followed by a Restore Settings to correctly initialise the EEProm. 4) I also flashed the DWIN firmware to the display. Then followed the process in step 3.

pc-bastler commented 2 years ago

I had the same issue with the 2.0.1 JyersUI... After 6-7 retries Octoprint connected to the printer.

Since I swapped out the display unit with a Creality touchscreen, I had to swap to the Creality-provided Firmware (also based on Marlin 2.0.1) and Octoprint is working as expected again.