Cant start a print with octoprint even though i can print from printer sd card with no issues. i can control the printer in octoprint web ui though.
so when i load and print gcode, the bed will reach target temp no problem, but when the hotend tries to reach target temp, the print freezes and i get a communication timeout in the terminal. also i noticed when reaching target hotend temp, it defaults to 170degrees. very Odd.
also my printer is constantly trying to do a filament change but i have not seen any m600 command in the gcode.
pls help. thanks.
What did you already try to solve it?
i reflashed and used other sd cards to rule out bad sd card. i also replaced usb cable with a new cable that has ferrite chokes on both ends.
Have you tried running in safe mode?
yes
Did running in safe mode solve the problem?
no success either
Complete Logs
octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)
OctoPrint version 1.5.2, OctoPi version 0.18.0, printer= artillery sidewinder x1, firmware= marlin 2.0.7 (self compiled but not sure if perfect/ prints from printer's sd card with no issues), browser= chrome, operating system= windows 10,
One request: Either attach your logs as file or please use the </> in the editors menu bar for logs etc. (You may have to enable the serial.log before.)
Things get lost.
Like here:
I'm missing the line where the hotend is set to 170°C
im not sure if i compiled the firmware right because i cant get the filament runout sensor to work and filament change feature to work. but when i compiled marlin in vscode, it was a sucsess..
After reading that issue it explains the M113 but it looks to me like we need to know what the Settings, Serial Connection, Intervals & timeouts page looks like.
Also, when I send an M113 S2 to my LulzBot TAZ 6 it responds with ok:
Send: M113 S2
Recv: ok P15 B4
So I'm still confused by the contents of the serial.log.
I'm going to take a guess, could be completely out but if there is a filament sensor active, then this would make sense:
Start print
Filament is out, so heat the hotend for a filament change
Waiting for user to press button on LCD creates a timeout
Usually, Marlin should have busy protocol enabled and should not timeout. However, I have seen a number of bugs reported (to OctoPrint) that the 2.0.7.2 release (and probably others) have issues with timeouts on filament change. Reportedly using the latest bugfix branch has these issues fixed.
Again, a bit of a shot in the dark but it is the feeling I am getting. Based as well on the mention of the filament sensor somewhere.
i had a rash of communication errors that usually happened a few minutes after print started - cure for mine was replacing the USB cable between PI and Printer with one that was shielded better.
Bruce
About this...
Have you tried to leave the printer in the 'preheat'-menu?
If I don't, after a while - like you describe - I loose connection to the printer while printing from for example Octoprint (also other programs).
But I leave it in that submenu it works just fine.
I have had this problem with multible sidewinders by the way and it seems to be in combination with the original touchscreen on the printer.
When I disconnect the touchscreen, the problem is also solved.
Well, not a problem anymore since I leave the printer in it's submenu for the preheat after starting that and I can print for days without any issue.
I remember that this issue was listed in the problem-list at artillery when I was still active in those groups to do problem-solving.