Octoprint (1.8.2) Timeout with Einsy RAMBo 1.2e & MK3 Firmware 3.11.0

What is the problem?

Long story, while calibrating one of my MK3 (Einsy RAMBo 1.1b) the power went out, which caused some board failure (could not read some language file, on some chip.. etc) and would no longer drive the Y axis. So I ordered 2 replacement boards which are version 1.2e and had the MK3S Firmware loaded.

Installed the new board, performed a factory reset (all data); flashed the MK3 3.11.0 FW, and performed a full calibration.

The printer seems to work otherwise with the MK3 on board SD card, but Octoprint can't complete a connection with this software version.

What did you already try to solve it?

  1. Tried several USB Cables.
  2. Many changes to configuration in both OP and MK3.
  3. Flashed MK3 FW 3.10.0 - Regained Communication, but something was causing OP to loose communication during a print.
  4. Flashed MK3 FW 3.9.3 - Regained Communication and printing fine.
  5. Tried the same above with the 2nd new board with the same exact results.

What is interesting about this, my second MK3 with board 1.1b has no problem communicating with OP with MK3 FW 3.11.0. So there seems to be something different with the 1.2e boards?

Have you tried running in safe mode?

Yes, made no difference

Did running in safe mode solve the problem?

No

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

NOTE: This is with the MK3 FW 3.09.0

octoprint-systeminfo-20220823130632.zip (66.9 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

OP 1.8.2
MK3 (Non S)
Octopi 0.18.0
Raspberry Pi 3 Model B Rev 1.2

2022-08-21 16:41:37,927 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2022-08-21 16:45:44,880 - Enabling serial logging
2022-08-21 16:45:55,300 - Changing monitoring state from "Offline" to "Opening serial connection"
2022-08-21 16:45:55,311 - Connecting to port /dev/ttyACM0, baudrate 115200
2022-08-21 16:45:55,618 - Changing monitoring state from "Opening serial connection" to "Connecting"
2022-08-21 16:45:55,621 - Connected to: Serial<id=0x67dfcff0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2022-08-21 16:45:55,641 - Send: N0 M110 N0*125
2022-08-21 16:46:07,762 - Recv: start
2022-08-21 16:46:07,776 - Send: N0 M110 N0*125
2022-08-21 16:46:07,832 - Recv: ;S
2022-08-21 16:46:07,882 - Recv: ;S
2022-08-21 16:46:07,934 - Recv: ;S
2022-08-21 16:46:07,988 - Recv: ;S
2022-08-21 16:46:08,038 - Recv: ;S
2022-08-21 16:46:08,045 - Recv: SN update failed
2022-08-21 16:46:08,052 - Recv: echo: 3.11.1-RC1-4987
2022-08-21 16:46:08,059 - Recv: echo: Last Updated: Jun 13 2022 17:21:41 | Author: (none, default config)
2022-08-21 16:46:08,066 - Recv: Compiled: Jun 13 2022
2022-08-21 16:46:08,073 - Recv: echo: Free Memory: 2034  PlannerBufferBytes: 1760
2022-08-21 16:46:08,080 - Recv: echo:Hardcoded Default Settings Loaded
2022-08-21 16:46:08,087 - Recv: adc_init
2022-08-21 16:46:08,442 - Recv: CrashDetect DISABLED
2022-08-21 16:46:08,806 - Recv: PAT9125_RES_X=0
2022-08-21 16:46:08,814 - Recv: PAT9125_RES_Y=240
2022-08-21 16:46:08,821 - Recv: PAT9125_init:1
2022-08-21 16:46:08,829 - Recv: PAT9125_RES_X=0
2022-08-21 16:46:08,834 - Recv: PAT9125_RES_Y=240
2022-08-21 16:46:08,838 - Recv: PAT9125_init:1
2022-08-21 16:46:08,842 - Recv: FSensor ENABLED
2022-08-21 16:46:08,847 - Recv: Sending 0xFF
2022-08-21 16:46:08,851 - Recv: echo:SD card ok
2022-08-21 16:46:09,216 - Recv: LCD status changed
2022-08-21 16:46:09,260 - Recv: fsensor_autoload_check_start - autoload ENABLED
2022-08-21 16:46:11,240 - Recv: RX timeout
2022-08-21 16:46:37,652 - Recv: MMU not responding - DISABLED
2022-08-21 16:47:07,689 - There was a timeout while trying to connect to the printer
2022-08-21 16:47:07,702 - Changing monitoring state from "Connecting" to "Offline"
2022-08-21 16:47:07,730 - Connection closed, closing down monitor

Have you set the RPi port to off?

Thanks Ewald,
Indeed, it was off. I actually think the serial logs shows a different set of errors when RPi port is on.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.