SKR1.4 turbo connection to Octoprint

Get Help
1

What is the problem?
Got my self a new SKR1.4 turbo for my ender 5 plus. Octoprint is running on a Pi 4. When connecting to the usb port I get Operational and then once i send a stl file it immediately disconnects and then i cant reconnect.

What did you already try to solve it?
I have reinstalled firmware multiple times. Disconnected the LCD and ran with just octopi and the new board. Disabled addons. Restarted multiple times.

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

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

OctoPrint 1.3.12 running on OctoPi 0.17.0
Ender-5 Plus
Marlin-2.0.x-SKR-V1.4-Turbo

2

Hello @Syndrogo!

Already tried in safemode?
There are some errors referring to astroprint.

3

I have tried safe mode and same result. I can try turning Astro print off again and get another log.

4

Here the log from save mode

2020-02-03 19:59:14,658 - octoprint.environment - INFO - Detected environment is Python 2.7.16 under Linux (linux2). Details:
|  hardware:
|    cores: 4
|    freq: 1500.0
|    ram: 1979641856
|  os:
|    id: linux
|    platform: linux2
|  plugins:
|    pi_support:
|      model: Raspberry Pi 4 Model B Rev 1.1
|      octopi_version: 0.17.0
|  python:
|    pip: 19.3.1
|    version: 2.7.16
|    virtualenv: /home/pi/oprint
2020-02-03 19:59:14,665 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets...
2020-02-03 19:59:14,679 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache...
2020-02-03 19:59:15,036 - octoprint.server - INFO - Shutting down intermediary server...
2020-02-03 19:59:15,437 - octoprint.server - INFO - Intermediary server shut down
2020-02-03 19:59:15,439 - octoprint.events - INFO - Processing startup event, this is our first event
2020-02-03 19:59:15,439 - octoprint.events - INFO - Adding 1 events to queue that were held back before startup event
2020-02-03 19:59:15,442 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue...
2020-02-03 19:59:15,470 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2020-02-03 19:59:15,542 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue
2020-02-03 19:59:15,735 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid
2020-02-03 19:59:15,916 - octoprint.server.util.watchdog - INFO - Running initial scan on watched folder...
2020-02-03 19:59:15,921 - octoprint.server.util.watchdog - INFO - ... initial scan done.
2020-02-03 19:59:15,928 - octoprint.plugins.discovery - INFO - Registered 'OctoPrint instance on octopi' for _http._tcp
2020-02-03 19:59:15,935 - octoprint.plugins.discovery - INFO - Registered 'OctoPrint instance on octopi' for _octoprint._tcp
2020-02-03 19:59:15,936 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-03 19:59:15,945 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on octopi for SSDP
2020-02-03 19:59:15,952 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2020
5

Hmmm.

Can you also share the serial.log? (Have a look that it's activated)

6 
2020-02-03 20:00:12,922 - Connecting to: /dev/ttyACM0
2020-02-03 20:00:12,943 - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-03 20:00:12,947 - Connected to: Serial<id=0xb0d72350, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2020-02-03 20:00:12,948 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-02-03 20:00:42,992 - There was a timeout while trying to connect to the printer
2020-02-03 20:00:43,008 - Changing monitoring state from "Connecting" to "Offline"
2020-02-03 20:00:43,018 - Connection closed, closing down monitor
2020-02-03 20:02:24,953 - Connecting to: /dev/ttyACM0
2020-02-03 20:02:24,982 - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-03 20:02:24,991 - Connected to: Serial<id=0xa7ea1e10, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2020-02-03 20:02:24,992 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-02-03 20:02:55,027 - There was a timeout while trying to connect to the printer
2020-02-03 20:02:55,042 - Changing monitoring state from "Connecting" to "Offline"
2020-02-03 20:02:55,049 - Connection closed, closing down monitor
2020-02-03 20:04:29,834 - Connecting to: /dev/ttyACM0
2020-02-03 20:04:29,854 - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-03 20:04:29,855 - Connected to: Serial<id=0xa7dee6b0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2020-02-03 20:04:29,857 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-02-03 20:04:59,899 - There was a timeout while trying to connect to the printer
2020-02-03 20:04:59,909 - Changing monitoring state from "Connecting" to "Offline"
2020-02-03 20:04:59,920 - Connection closed, closing down monitor
7

Already tried another baudrate?

8

So i got it connected to the USB 2.0 insteed of the 3.0 and got it connected again and then it failed when i sent the print.serial (1).log (8.3 KB) octoprint.log (381.2 KB)

9

I've stumbled over this line

2020-02-03 20:35:38,591 - Send: N9 M104 S195 ?T0*26

The ? is quite weird. I did not find anything about this on the Marlin site. This may confuse the printer's firmware.

You may check the gcode start code of the slicer.

1 Like
10

Fixed it (was a tone i send on my creality board) still getting disconnected. octoprint (1).log (446.4 KB) serial (2).log (4.6 KB)

11

So you get a timeout when sending M105.

2020-02-03 20:56:49,175 - Recv:  T:19.53 /0.00 B:-15.00 /0.00 @:0 B@:0

But why is the bed at -15°C and the hotend at 19.53°C?
Do you get the same on the printer display?
If yes, you may check the cables of the heatbed thermistor and the thermistor itself.

13

After taking a look it looks like the thermistor on both bed and hot end was suppose to be flipped. They are now working 100%

1 Like
14

Small issue - huge problem. Great you found it :+1:

1 Like