Temperature return code is not supported on connect to Duet 3

Get Help Electronics
1

What is the problem?
When connecting from Octoprint to a Duet 3 board Octoprint can't parse the temperature returned.

What did you already try to solve it?

  • Set the Duet to Marlin compatibility with M555 P2 in config.g
  • Switched off firmware auto-detection (didn't work)

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, what kind of hardware precisely, ...)

Octoprint 1.4.2
Pi 4B/4GB also running Duet Software Framework / Duet Web Control
RepRap FIRMWARE_VERSION: 3.1.1
ELECTRONICS: Duet 3 MB6HC 1.0

2020-08-16 23:17:01,546 - Connecting to: /dev/ttyACM0
2020-08-16 23:17:01,564 - Changing monitoring state from "Offline" to "Opening serial port"
2020-08-16 23:17:01,567 - Connected to: Serial<id=0xaaa43510, 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-08-16 23:17:01,569 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-08-16 23:17:01,577 - Send: N0 M110 N0125
2020-08-16 23:17:01,583 - Send: N0 M110 N0125
2020-08-16 23:17:01,585 - Recv: ok
2020-08-16 23:17:01,597 - Changing monitoring state from "Connecting" to "Operational"
2020-08-16 23:17:01,624 - Send: N0 M110 N0125
2020-08-16 23:17:01,626 - Recv: ok
2020-08-16 23:17:01,628 - Send: N1 M11539
2020-08-16 23:17:01,629 - Recv: ok
2020-08-16 23:17:01,631 - Send: N2 M2118
2020-08-16 23:17:01,644 - Recv: FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2
2020-08-16 23:17:01,654 - Recv: ok
2020-08-16 23:17:06,591 - Send: M105
2020-08-16 23:17:06,600 - Recv: Error: Code is not supportedok T0:-273.1 /0.0 B:-273.1 /0.0
2020-08-16 23:17:06,602 - Changing monitoring state from "Operational" to "Error: Code is not supportedok T0:-273.1 /0.0 B:-273.1 /0.0"
2020-08-16 23:17:06,608 - Send: M112
2020-08-16 23:17:06,610 - Send: N3 M11234
2020-08-16 23:17:06,612 - Send: N4 M104 T0 S037
2020-08-16 23:17:06,613 - Send: N5 M140 S096
2020-08-16 23:17:06,638 - Changing monitoring state from "Error: Code is not supportedok T0:-273.1 /0.0 B:-273.1 /0.0" to "Offline (Error: Code is not supportedok T0:-273.1 /0.0 B:-273.1 /0.0)"
2020-08-16 23:17:06,752 - Connection closed, closing down monitor

2

It looks like OctoPrint is not expecting/accepting negative temperatures (below freezing) in temperature updates. For some reason, your printer is reporting the absolute zero temperature of -273.1 degrees Celcius for both your bed and extruder. I don't think you have your temperature sensors configured or wired correctly.

1 Like
3

Ah, yes, that makes sense. This is a lab setup. The rest of the printer has not arrived yet! Thanks!

4

Ok, the temp sensors are not sufficient. I've got some connected now but the return still fails.

The non-response for M21 is also worrying. Note there is no SD card in the board. The Duet Web Control uses a virtual SD card with the data stored on the PI.

Here's the log:

Send: N1 M115*39
Recv: FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2
Recv: ok
Send: M21
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: M105
Recv: Error: Code is not supportedok T0:26.7 /0.0 B:26.7 /0.0
Changing monitoring state from "Operational" to "Error: Code is not supportedok T0:26.7 /0.0 B:26.7 /0.0"