Changing monitoring state from "Operational" to "Starting"
Send: N10 M117 0% | -*113
Recv: ok
Send: N0 M110 N0*125
Recv: ok
Send: N1 G90*17
Recv: ok
Changing monitoring state from "Starting" to "Printing"
Send: N2 G21*24
Recv: ok
Send: N3 G90*19
Recv: ok
Send: N4 M42 P3 S1*16
Recv: ok
Send: N5 M117 0% | 09:49*86
Recv: ok
Send: N6 G90*22
Recv: ok
Send: N7 G0 X0 Y0 F1500*77
Recv: ok
Changing monitoring state from "Printing" to "Finishing"
Send: N8 M400*47
Recv: ok
Changing monitoring state from "Finishing" to "Operational"
I've moved your topic into the Get Help sub forum because this is actually the better place.
Alas, because you opened it in General you failed to fill out the template, so please do so now:
<!-- ~~~~~ Filling this out properly makes it WAY more likely to get help quickly ~~~~~ -->
### What is the problem?
WRITE HERE
### What did you already try to solve it?
WRITE HERE
### Have you tried running in safe mode?
WRITE HERE
### Did running in safe mode solve the problem?
WRITE HERE
### Systeminfo Bundle
<small>You can download this in OctoPrint's System Information dialog ... **no bundle, no support!**)</small>
WRITE HERE
### Additional information about your setup
<small>OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... **as much data as possible**</small>
WRITE HERE
What I can tell you is that I just ran your GCODE through OctoPrint's virtual printer and I didn't see any weirdness, so I'd strongly suggest you try safe mode.
I use Octo for some years and I was in 1.6 and I update to 1.7.2, and I have exactly the same problem , but not with all Gcode, nealy uploaded on Octo refuse to print, olders prints.
On the terminal, I can send some gcode, like G28, M140, G92, but G0 and G1 are not sended.
After many test, I couldn't not identify what made Octo to refuse G0 and G1, but once restarted I can send this Gs for a short time.
Please help, I have lost all my SD card, I can't print.
There's a ton of errors in there from the dashboard plugin, so you really should first test in safe mode if the issue persists. If it does, please enable serial.log, reproduce the problem and then create another systeminfo bundle.
edit On closer look, this is most definitely the dashboard plugin as it crashes with a division by zero whenever a command is to be sent to the printer.
Dashboard plugin removed, also, it's not the same problem but I never succeed to made layerdisplay work. I tested patterns on the web site and they were ok.
As soon my printer finish its job I'll test without the plugin
Yep, at least the log of @Joachim is littered with:
2021-11-11 15:08:01,790 - octoprint.util.comm - ERROR - Error while processing hook dashboard for phase sending and command G1 X86.208 Y70.466 E0.0407:
Traceback (most recent call last):
File "/home/pi/OctoPrint/venv/lib/python3.6/site-packages/octoprint/util/comm.py", line 4611, in _process_command_phase
tags=tags,
File "/home/pi/OctoPrint/venv/lib/python3.6/site-packages/octoprint/util/__init__.py", line 1737, in wrapper
return f(*args, **kwargs)
File "/home/pi/OctoPrint/venv/lib/python3.6/site-packages/octoprint_dashboard/__init__.py", line 792, in process_gcode
current_layer_progress = int((self.layer_moves / self.layer_move_array[self.current_layer]) * 100)
ZeroDivisionError: division by zero
This is btw why we always want y'all to test if a problem persists in safe mode first. Safe mode disables all third party plugins, and believe it or not, a third party plugin is surprisingly often the culprit.
Yep, best open a ticket on the plugin's issue tracker. I don't know if they are active on this forum here and I for one cannot solve this, that's for the plugin author to do.
What I have however just added to my TODO list is to make OctoPrint more resilient in this particular part of the code against issues like this one, in 1.8.0.
My point was that the reporting template explicitly asks to test in safe mode because that will already unveil if it is an issue caused by a third party plugin. Sadly a lot of people don't (or - even worse - say they tested in safe mode but actually didn't) and that costs their time and ours and frankly is a bit frustrating when it happens so often. Be kind, test in safe mode
