This problem just started after several months of no issues. The printer warms up does bed leveling then does the first print line. After that it moves up then to the front corner and just starts retracting and extruding a ton at super fast speeds. Not a great video and I killed the power to prevent jam. https://youtu.be/8Hh38NkpBfY
What did you already try to solve it?
Tried different cable. tried different gcode's. Same Gcoode's prints fine from SD card. Removed G34 from script since the problem started around the same time i started using it.
I tried in safe mode and got the same result. Here are the logs but seem to be pretty much the same. I will try the m502 and m500 after a current print gets done. Thanks for helping. Would posting my marlin configs help at all? octoprint.log (404.2 KB) serial.log.2021-02-09_18-21-06.log (54.4 KB)
Wouldn't this be an issue when printing from the sd card as well? Same gcode works fine from SD. I also posted the gcode in the first post. It does extrude the initial line.
Edit: I will try a gcode from Cura and see if it does the same just to rule this out. My normal is S3D
I tried a cura gcode with same results. I let the printer run for about 5 seconds after it moved to the corner to try and see the info. Got a little info about it moving to the corner. Still not sure why it does though.
I built it from scratch. It's a cartesian style built with all 2020 and 2040 extrusion. Build size is roughly 315x315x320. 24v with skr e3 mini v2, BMG extruder, E3d v6 hotend, 12 inch mains powered heat bed. I'm not sure what info you want from the printer profile? Lower left origin, rectangle, size set to what i put above, nothing in the scripts.
That seems firmware related.
The printer performs such a move on pause or filament change.
Some things do not happen during SD card print but on serial print.
Ok so you've jogged my memory and i started going line through line of my marlin. I had been making firmware changes to install a filament runout sensor. I do believe now the firmware is setup for filament runout but i haven't installed the sensor yet. I'm guessing that is the issue. I made a change on my carriage so i re-flashed the firmware with the new settings and forgot i made those filament runout changes.
Hmm hooked up the filament runout sensor and getting the same thing. It is definitely moving to the park position and doing it's thing. I can't figure out why it would do this through octoprint but not from SD? I guess i will turn off all the filament runout stuff in marlin and reflash and see if that fixes. Unless someone has something to try?
Got it solved. Runout state had to be changed to HIGH. Apparently marlin doesn't care if the print starts with the runout sensor open and just prints. Octoprint must check for that state? or something because it would fail every time.