FLSun-QQ-S doesn't read temperature

What is the problem? OctoPi monitor reports no change in temperature of bed or hotend when starting a print. After a little bit, it reports thermistor failure and disables printing for safety. So the thermistors are broken, the communication is screwed up, or OctoPi is seeking temperature reports from the wrong place.

What did you already try to solve it?

  • Power down Pi and printer. Boot Pi, then printer. No change.

  • closed browser window and re-connected to server

  • Verified Pi is using stock 5.1V / 3A supply

  • Disconnect printer USB cable and print from micro-SD in the printer's slot. Temperatures ramp up as normal, then printing begins.

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

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

  • Terminal is MacBook Air running Windows 10 / 64bit
  • Wireless: TP-link Deco mesh system @5GHz and 2.4GHz
  • About 30 other devices on my home network
  • ISP (Charter) download speed always >50mbps
  • Raspberry Pi 4b 4gig
  • built boot image from Octoprint.org website: octopi-buster-lite-0.17.0.zip downloaded 20Mar2020
  • Upgraded to Octopi 1.4.0 stable

Terminal text grab

From PuTTY session:

Linux octopi 4.19.75-v7l+ #1270 SMP
OctoPrint version : 1.4.0
OctoPi version : 0.17.0

Other shell info pluTerminal Tab Text:

From PuTTY session:

Linux octopi 4.19.75-v7l+ #1270 SMP
OctoPrint version : 1.4.0
OctoPi version : 0.17.0

Terminal Text:

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: [u'/dev/ttyUSB0']
Connecting to: /dev/ttyUSB0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0xaa515b90, open=True>(port='/dev/ttyUSB0', 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
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from "Detecting baudrate" to "Operational"
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Recv: ok 1
Recv: FIRMWARE_NAME:Robin
Send: M21
Recv: Printed filament:200.21m Printing time:2 days 17 hours 30 min
Recv: PrinterMode:FFF
Recv: ok 1
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Send: M105
Recv: ok 1
Recv: T:25.00 /0 B:36.33 /0 B@:0 @:0
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Send: M104 S210
Recv: ok 1
Recv: TargetExtr0:210
Recv: wait
Send: M140 S60
Recv: ok 1
Recv: TargetBed:60
Recv: wait
Recv: wait
Send: M105
Recv: ok 1
Recv: T:24.17 /210 B:35.60 /60 B@:255 @:255
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Recv: wait
Changing monitoring state from "Operational" to "Starting"
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from "Starting" to "Printing"
Send: N1 M2100 T2512*97
Recv: ok 1
Recv: Unknown command:N1 M2100 T208
Send: N2 M82*27
Recv: ok 2
Send: N3 G21*25
Recv: ok 3
Send: N4 G90*20
Recv: ok 4
Send: N5 M82*28
Recv: ok 5
Send: N6 M107 T0*103
Recv: ok 6
Send: N7 M190 S60*89
Recv: ok 7
Recv: busy:heating
Send: N8 M109 S210 T0*39
**Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly**
Recv: T:24.03 /210 B:34.95 /60 B@:255 @:255
Recv: busy:heating
Recv: T:24.03 /210 B:34.95 /60 B@:255 @:255
Recv: T:24.03 /210 B:34.86 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.86 /60 B@:255 @:255
Recv: T:24.03 /210 B:34.95 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.86 /60 B@:255 @:255
Recv: T:24.03 /210 B:34.86 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.77 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.86 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.86 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.77 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.77 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.77 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.68 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.59 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.59 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.59 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.59 /60 B@:255 @:255
Recv: T:24.03 /210 B:34.59 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.50 /60 B@:255 @:255
Recv: T:23.75 /210 B:34.50 /60 B@:255 @:255
Recv: busy:heating
Recv: T:24.89 /210 B:34.50 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.50 /60 B@:255 @:255
Recv: busy:heating
Recv: T:23.89 /210 B:34.50 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.50 /60 B@:255 @:255
Recv: busy:heating
Recv: T:24.89 /210 B:34.40 /60 B@:255 @:255
Recv: T:23.89 /210 B:34.40 /60 B@:255 @:255
Recv: DebugLevel:14
Recv: Error:One heater seems decoupled from thermistor - disabling all for safety!
Changing monitoring state from "Printing" to "Error: One heater seems decoupled from thermistor - disabling all for safety!"
Send: M112
Send: N9 M112*40
Send: N10 M104 T0 S0*16
Send: N11 M140 S0*85
Changing monitoring state from "Error: One heater seems decoupled from thermistor - disabling all for safety!" to "Offline (Error: One heater seems decoupled from thermistor - disabling all for safety!)"
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: []
Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
Failed to autodetect serial port, please set it manually.

Hello @ecp!

Have you seen this:?

Another reason can be, that there is no energy for heating up the hotend and the bed. Check the connectors on the printer board.
Curious is, that the print from SD card seem to work.
BTW: What printer are you using?

o rly?

I'm guessing that you're running something like Apple Boot Camp (perhaps). This is probably something like Docker in that a virtual machine is created and then spun up so that Windows could be installed to it. But if the device tree isn't the exact same or the serial devices aren't handed over to the virtual machine then "you're gonna have a bad time".

You might try going to a standard macOS Terminal. You can then run commands like ls -l /dev to find out what device the printer should be and ssh to remote over to the Pi. You could use Safari to talk to the web interface.

The issue here isn't the terminal software, it's the firmware on the printer. See https://community.octoprint.org/t/i-cannot-successfully-print-on-my-printer-running-a-firmware-identifying-itself-only-as-cbd-make-it-or-zwlf-make-it/17481 for another recent case.

The FLSun-QQ-S printer has some funky firmware that calls itself "Robin"

Send: M105
Recv: ok 1
Recv: T:25.00 /0 B:36.33 /0 B@:0 @:0

is close but not what OctoPrint is expecting. It should be:

Send: M105
Recv: ok T:25.00 /0 B:36.33 /0 B@:0 @:0

This may be "fixable" with a plugin (as was the bastard firmware in the thread posted above) but someone has to write the plugin. Please follow @foosel's advice and complain loudly to the printer manufacturer.

In the mean time, search the internet for FLSun-QQ-S and Marlin and see if you can find someone who has created a decent version of firmware for this printer.

Actually, OctoPrint should still read that just fine (it's a Repetier style format).

No idea what funky kind of firmware "Robin" is supposed to be though.

The bigger issue here really is that thermistor/heater error. That needs to be fixed. Firmware- or hardwareside, OctoPrint can't do ANYTHING about that. The reason there's no change in temperature being shown is that it is not being measured which then also leads to that error being reported by the firmware.

Sorry if I confused the issue. I learn something new every day!

No worries, just thought I'd mention it :slight_smile:

Repetier puts the ok before any command output (so that it gets received as fast as possible). Looks like "Robin" does as well. Judging by the log that firmware on first look also seems to be fairly well behaved. I mean, it even has thermal runaway protection or it wouldn't throw that error.

Thanks for the suggestion. When a weird one comes up, I often end up with a Mac/Boot Camp/ Win10 issue. Unfortunately, running under MacOS, chrome, safari, PuTTY, ssh, no difference.

Hi @Ewald_Ikemann! It's a FLSun QQ-S (not the Pro).

Hi @b-morgan -

Installed the CBD Make It plug-in, did system restart (printer and Pi), same outcome. I'll take your advice and try to track down "Robin"

That plugin is for a completely different printer (set). Uninstall it because it may cause more problems.

Yikes!! Thanks!