Hey guys,
This is kind of weird. I was doing my first large print with my new Rostock (Eiffel tower - sliced with Cura, controlling with Repetier). It was getting towards the end, and it just stopped mid-print. Printer not responding to any commands in repetier... can't kill print or anything. So I reboot the printer and am able to connect again. I go to approximately where it died, back a layer or two, and just run that GCODE out to the end of the print. And it stopped at exactly the same spot. This was starting to get suspicious.
I was able to isolate it to layer 1616. Specifically a retraction command (G1 F2400 E3102.34645). However running layer 1616 by itself doesn't cause any problems... it's only when it directly follows a previous layer (so... If I Reboot the printer and just run layer 1616 - no problem. But if I run it again immediately afterward, it breaks)
I am wondering if anyone else can try this GCODE and report back whether it stops your printer or not. Mine Is repetier firmware using the SeeMeCNC code (only changing eeprom settings). I want to know whether it's a bug in my particular controller or if it's overall repetier issue.
(Note: I inserted a G92 E3102 command so that the extruder doesn't try to go from zero to 3102 in one go. Also, make sure your extruder is hot before running this code as there is nothing setting temperatures)
;LAYER:1615
;'Zero' out the extruder position
G92 E3102
G0 X-6.019 Y-6.009 Z323.300
;TYPE:WALL-OUTER
G1 F2400 E3103.99574
G1 F540 X-6.511 Y-5.996 E3104.01621
G1 X-6.490 Y-6.803 E3104.04977
G1 X-6.349 Y-6.800 E3104.05563
G1 X-6.011 Y-6.807 E3104.06969
G1 X-6.019 Y-6.009 E3104.10287
G1 F2400 E3101.60287
G0 F15000 X5.993 Y-6.055
G1 F2400 E3104.10287
G1 F540 X5.997 Y-6.828 E3104.13500
G1 X6.479 Y-6.844 E3104.15505
G1 X6.491 Y-6.122 E3104.18507
G1 X6.482 Y-6.009 E3104.18979
G1 X5.996 Y-6.010 E3104.20999
G1 X5.993 Y-6.055 E3104.21187
G1 F2400 E3101.71187
G0 F15000 X6.026 Y6.000
G1 F2400 E3104.21187
G1 F540 X6.482 Y6.003 E3104.23083
G1 X6.471 Y6.795 E3104.26376
G1 X6.013 Y6.809 E3104.28281
G1 X6.026 Y6.000 E3104.31645
G1 F2400 E3101.81645
G0 F15000 X-6.013 Y6.010
G1 F2400 E3104.31645
G1 F540 X-6.005 Y6.819 E3104.35008
G1 X-6.496 Y6.804 E3104.37051
G1 X-6.485 Y6.016 E3104.40327
G1 X-6.013 Y6.010 E3104.42290
;Small layer, adding delay of 23.734829
G1 F2400 E3101.92290
G0 F15000 X-6.013 Y6.010 Z326.300
G0 X13.987 Y6.010
G4 P5000
;LAYER:1616
G0 X-5.996 Y-5.982 Z323.500
;TYPE:WALL-OUTER
G1 F2400 E3104.42290
G1 F540 X-6.479 Y-5.975 E3104.44298
G1 X-6.466 Y-6.778 E3104.47637
G1 X-6.432 Y-6.777 E3104.47778
G1 X-5.988 Y-6.786 E3104.49624
G1 X-5.996 Y-5.982 E3104.52967
G1 F2400 E3102.02967
G0 F15000 X5.980 Y-5.984
G1 F2400 E3104.52967
G1 F540 X5.984 Y-6.795 E3104.56339
G1 X6.452 Y-6.811 E3104.58286
G1 X6.464 Y-5.982 E3104.61733
G1 X5.980 Y-5.984 E3104.63745
G1 F2400 E3102.13745
G0 F15000 X6.007 Y6.176
G1 F2400 E3104.63745
G1 F540 X6.010 Y5.985 E3104.64539
G1 X6.463 Y5.988 E3104.66423
G1 X6.452 Y6.765 E3104.69653
G1 X6.001 Y6.785 E3104.71530
G1 X6.007 Y6.176 E3104.74062
G1 F2400 E3102.24062
G0 F15000 X-5.989 Y5.984
G1 F2400 E3104.74062
G1 F540 X-5.986 Y6.788 E3104.77405
G1 X-6.470 Y6.772 E3104.79418
G1 X-6.472 Y6.548 E3104.80350
G1 X-6.464 Y5.990 E3104.82670
G1 X-5.989 Y5.984 E3104.84645
;Small layer, adding delay of 23.743482
G1 F2400 E3102.34645
G0 F15000 X-5.989 Y5.984 Z326.500
G0 X14.011 Y5.984
G4 P5000; MatterControl - SeeMeCNC Version 1.4.0 Build 1.4.0.5430 : GCode settings used
This GCODE mysteriously kills my printer mid-print
-
- Noob
- Posts: 4
- Joined: Tue Jan 12, 2016 1:03 am
Re: This GCODE mysteriously kills my printer mid-print
Sorry for the late reply, Please do tell if this has been resolved and how! Have you attempted any other prints? Were they roughly the same size, If you did?
Hey sweetie, Have you checked your thermisistors lately? cause you're hotter than my onyx...
-
- Noob
- Posts: 4
- Joined: Tue Jan 12, 2016 1:03 am
Re: This GCODE mysteriously kills my printer mid-print
This is the only print it has happened with so far. Have not resolved it yet... but i have been meaning to look into it further.
here are a few guesses:
-Printer runs out of memory
-printer divides by zero??
-something weird happening to the USB-Serial chip?
here are a few guesses:
-Printer runs out of memory
-printer divides by zero??
-something weird happening to the USB-Serial chip?