OctoPrint commands not obeyed by printer

Get Help
1

What is the problem?

None of the commands I sent through Octoprint are obeyed by my printer. The only commands that the print follows are the return home. Fans do not work. The hot end and bed do not heat up.

What did you already try to solve it?

Ran it in safe mode. Tried rewiring some things. All connections are secured. Tried safe mode and resetting through the terminal. Tested different hardware, including the fans. Replaced nozzle.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

Log files are attached

Additional information about your setup

Version 1.9.3, MEWron, Chrome, MacOs
Build 2023.10.09.151442 with "webcamd", based on OctoPi 1.0.0, running on Raspberry Pi 4 Model B Rev 1.5
auth.log (196 Bytes)
octoprint.log (42.9 KB)
plugin_softwareupdate_console.log (4.2 KB)
serial (1).log (148 Bytes)
tornado.log (32.5 KB)

2

Hello @starfish !

There is no need to send the log files as single files. The systeminfo bundle is zipped and loads up faster.

You did not mention what printer you use.

The constant first error you get is:

| Send: G0 X10 F6000
| Recv: !! Must home axis first: 10.000 0.000 0.000 [0.000]

After turning on the printer, you have to home (usually with G28)
The same applies when you turned off the motors.

The next issue is:

| Send: G0 Z-100 F200
| Recv: !! Move out of range: 60.000 110.000 -95.000 [0.000]

At last, the printer is homed. But you can't move 95 mm below the print bed.

So, the printer does what you want. But what you want makes no sense, so the printer throws out an error message.

3

Thank you so much for your response. I am new to this if you couldn’t tell!

I’ll keep the zipped file in mind next time I ask for help. My printer is the open-source Voron 0.1 printer.

I see what you’re saying. However, even when I was moving the z axis by an interval of 1, the bed still would not move. This also does not explain why my hot end and bed do not heat up. Any ideas? Thank you again.

4

Heating up does not appear in the logs.

Can you try that and then attach the systeminfo bundle to your next post?

BTW: Here is a good information source on Gcode commands

https://reprap.org/wiki/G-code

6

octoprint-systeminfo-20240416132124.zip (35.1 KB)

Here are the system info files. After looking at this log files, I have this error message when trying to use the heaters.

Heater extruder not heating at expected rate
| Recv: // See the 'verify_heater' section in docs/Config_Reference.md
| Recv: // for the parameters that control this check.
| Recv: //
| Recv: // Once the underlying issue is corrected, use the
| Recv: // "FIRMWARE_RESTART" command to reset the firmware, reload the
| Recv: // config, and restart the host software.

Not sure where to find docs/Config_Reference.md.

7

Neither bed nor hotend are heating at all.

2024-04-16 12:59:36,348 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Heater extruder not heating at expected rate
| Last lines in terminal:
| Send: M105
| Recv: ok B:24.2 /100.0 T0:24.3 /210.0
| Send: M105
| Recv: ok B:24.2 /100.0 T0:24.3 /210.0
| Send: M105
| Recv: ok B:24.2 /100.0 T0:24.3 /210.0
| Send: M105
| Recv: ok B:24.2 /100.0 T0:24.3 /210.0
| Send: M105
| Recv: ok B:24.2 /100.0 T0:24.3 /210.0
| Send: M106 S255
| Recv: // Heater extruder not heating at expected rate
| Recv: // See the 'verify_heater' section in docs/Config_Reference.md
| Recv: // for the parameters that control this check.
| Recv: //
| Recv: // Once the underlying issue is corrected, use the
| Recv: // "FIRMWARE_RESTART" command to reset the firmware, reload the
| Recv: // config, and restart the host software.
| Recv: // Printer is shutdown
| Recv: !! Heater extruder not heating at expected rate

I assume the printer is properly powered?

Did you built it yourself or have you got it assembled?

8

Another person built it from scratch. It is an open source printer that has worked before. The printer is powered properly. The command G28 works.

9

Then something with the powering of bed and hotend is not working.
A blown fuse (depends on the printer board), a loose cable, ...
You may have to check.

10

How do I access docs/Config_Reference.md?

11

This is Klipper stuff.

You may consult the Klipper forum.

12

octoprint-systeminfo-20240422160124.zip (12.5 KB)

Last week, I went ahead and replaced all of the hardware that I thought could have been the issue. Now it cannot connect. Any thoughts?

mcu 'mcu': Unable to connect

13

As I said: This is Klipper stuff.

This is the OctoPrint support forum.

For Klipper issues please consult the Klipper support forum.

14

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