MMU2S troubles, will not connect and print anymore

Get Help
1

What is the problem?

About a month ago I had a print going that messed up, blob on the print head and during removal, I broke the thermistor wire (it was heated an on to try and melt but I did not wait long enough.

What did you already try to solve it?
I replaced the entire hot end assembly, re calibrated and got back in business, but my octoprint would not connect. SD card prints worked flawlessly.

Mind you I have a MK3s working flawlessly with the same setup with octoprint sitting next to the MMU2s/MK3s unit I can not connect.

Using a laptop and usb cable, I updated to the current firmware ... so USB port seems to work?

Formatted the micro sd card, downloaded latest octopi .17, inserted into the Pi and after a minute or 2 I was in octoprint setting up the profile.

EDIT: setup the profile using 5 extruders and shared nozzle as seen in another post

With the serial port and baud rate set, it would not connect, when i set it to auto it connected and said operational, when I went to send a print, it never asked for filament and after 30 seconds timed out.

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

one clip from the terminal:

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: ['/dev/ttyACM0']
Connecting to: /dev/ttyACM0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0x6a5fa590, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Recv: start
Send: N0 M110 N0125
Changing monitoring state from "Detecting baudrate" to "Operational"
Send: N0 M110 N0125
Recv: Command not found!
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1 M115*39

logs removed because it has more than 2 links in it, will post in reply

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)

About OctoPi

The ready-to-go Raspberry Pi image with OctoPrint

Version 0.17.0, running on Raspberry Pi 3 Model B Rev 1.2

OctoPrint

The snappy web interface for your 3D printer

Version 1.3.12

Really hope its something simple

2

i can't paste the logs because they have links (which to me are local file paths), if there is a way, please let me know and I will post

here is some

2019-11-30 18:00:21,560 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2019-11-30 18:00:21,577 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2019-11-30 18:00:21,583 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-30 18:00:21,586 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-30 18:00:22,614 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-30 18:00:31,338 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Offline"
2019-11-30 18:00:36,026 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-11-30 18:00:36,058 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-11-30 18:00:36,065 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Detecting baudrate"
2019-11-30 18:00:37,076 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-30 18:00:37,103 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting baudrate" to "Operational"
2019-11-30 18:00:37,114 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-30 18:00:46,876 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Terrain NED_-106.82_40.47_tile_1_1_0.2mm_PLA_MK3SMMU2S_2h45m.gcode, owner: pi, user: pi
2019-11-30 18:00:49,836 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2019-11-30 18:00:49,852 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Terrain NED_-106.82_40.47_tile_1_1_0.2mm_PLA_MK3SMMU2S_2h45m.gcode, owner: pi, user: pi
2019-11-30 18:01:07,136 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2019-11-30 18:01:22,226 - octoprint.server.util.flask - INFO - Passively logging in user pi from ::ffff:192.168.5.187
2019-11-30 18:01:27,238 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.5.187
2019-11-30 18:01:27,672 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.5.187
2019-11-30 18:01:27,767 - octoprint.server.util.flask - INFO - Passively logging in user pi from ::ffff:192.168.5.187
2019-11-30 18:01:30,026 - octoprint.server.util.sockjs - INFO - User pi logged in on the socket from client ::ffff:192.168.5.187
2019-11-30 18:01:37,167 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2019-11-30 18:02:07,197 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2019-11-30 18:02:37,227 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2019-11-30 18:03:07,257 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2019-11-30 18:03:37,287 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2019-11-30 18:03:37,317 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Offline (Error: Too many consecutive timeouts, printer still
3

serial log

2019-11-30 17:50:19,913 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-11-30 18:00:18,402 - Enabling serial logging
2019-11-30 18:00:21,544 - Connecting to: /dev/ttyACM0
2019-11-30 18:00:21,560 - Changing monitoring state from "Offline" to "Opening serial port"
2019-11-30 18:00:21,568 - Connected to: Serial<id=0x6c8efb30, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2019-11-30 18:00:21,570 - Changing monitoring state from "Opening serial port" to "Connecting"
2019-11-30 18:00:21,584 - Send: N0 M110 N0*125
2019-11-30 18:00:21,587 - Send: N0 M110 N0*125
2019-11-30 18:00:22,604 - Recv: start
2019-11-30 18:00:22,615 - Send: N0 M110 N0*125
2019-11-30 18:00:31,332 - Connection closed, closing down monitor
2019-11-30 18:00:31,337 - Changing monitoring state from "Connecting" to "Offline"
2019-11-30 18:00:36,018 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-11-30 18:00:36,052 - Serial port list: ['/dev/ttyACM0']
2019-11-30 18:00:36,053 - Connecting to: /dev/ttyACM0
2019-11-30 18:00:36,058 - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-11-30 18:00:36,062 - Connected to: Serial<id=0x6c851570, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2019-11-30 18:00:36,063 - Starting baud rate detection...
2019-11-30 18:00:36,065 - Changing monitoring state from "Opening serial port" to "Detecting baudrate"
2019-11-30 18:00:37,070 - Trying baudrate: 115200
2019-11-30 18:00:37,077 - Send: N0 M110 N0*125
2019-11-30 18:00:37,099 - Recv: start
2019-11-30 18:00:37,102 - Changing monitoring state from "Detecting baudrate" to "Operational"
2019-11-30 18:00:37,115 - Send: N0 M110 N0*125
2019-11-30 18:00:49,835 - Changing monitoring state from "Operational" to "Starting"
2019-11-30 18:01:07,138 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:01:07,147 - Send: N1 M115*39
2019-11-30 18:01:37,168 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:02:07,198 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:02:37,228 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:03:07,258 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:03:37,289 - No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-11-30 18:03:37,316 - Changing monitoring state from "Starting" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2019-11-30 18:03:37,325 - Connection closed, closing down monitor
4

Did you set up your profile for multiple extruders?

5

yup, found that before I posted here but forgot to mention ... I've added up in the initial post

thanks for pointing that out.

-K

6

Do you have something else plugged to the USB ports of your Pi?
Can you operate the printer from the Laptop and Pronterface?

7

I do not, but found out it was RPI Port being set to the ON position that prevented it from working, I am resolved

2 Likes