1. Got a question or need help troubleshooting? Post to the troubleshooting forum or Search the forums!

Unresolved Robo R1+ Z gantry diving into print

Discussion in 'Troubleshooting' started by Hal Reed, Aug 8, 2019.

  1. Hal Reed

    Hal Reed New Member

    Joined:
    Aug 8, 2019
    Messages:
    3
    Likes Received:
    0
    I setup my octoprint, to NOT have gcode scripts to run post print. I use S3D to slice and upload to Octoprint to run the printer.
    My Gcode at the slicer at the end of print is the following:
    M104 S0 ; turn off extruder

    M140 S0 ; turn off bed

    G1 X0 ;

    M84 ; disable motors

    The Printer sends command gcode (logged on octoprint) that the z axis should be G1 Z10;
    No where in my settings calls this. Even after reslicing with the verified setup script, it still dives to Z10
    Whats up there......
     
    #1 Hal Reed, Aug 8, 2019
  2. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Have you looked at the generated Gcode (what the slicer outputs) to be certain that the slicer is not tagging that in there?
    Double check. If it is NOT generated by the slicer then OctoPrint is sending it.
     
    #2 mark tomlinson, Aug 8, 2019
  3. Hal Reed

    Hal Reed New Member

    Joined:
    Aug 8, 2019
    Messages:
    3
    Likes Received:
    0
    Yes... I checked both the Octoprint scripts and cleared each window completely, and removed any script, and went into Simplify 3d and made sure of the scripting there. I also sliced using Slic3r and it did the same thing. I did the slice and exported the file to SD card and it did the same thing from SD print. No Octoprint or USB print hookup. Its weird I just started this not too long ago.
     
    #3 Hal Reed, Aug 8, 2019
  4. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    I meant check the generated Gcode itself.
    It is just a text file you can read it :)
    Look at (or near) the end of it and see if it has a G1 Z10; in there.
    If not you can be certain that it is OctoPrint (or maybe an odd hardware failure of some sort)

    If it does it from the SD card then that rules out OctoPrint -- rule out the slicer too
     
    #4 mark tomlinson, Aug 8, 2019
  5. Hal Reed

    Hal Reed New Member

    Joined:
    Aug 8, 2019
    Messages:
    3
    Likes Received:
    0

    Nope... its has the right control command...
    G92 E0.0000
    G1 X107.493 Y124.453 E0.0102 F1003
    G1 X108.059 Y124.453 E0.0271
    G1 X107.467 Y123.861 E0.0522
    G1 X107.473 Y123.852 E0.0525
    G1 X107.719 Y123.547 E0.0642
    G1 X108.625 Y124.453 E0.1026
    G1 X108.978 Y124.453 E0.1132
    G1 X109.066 Y124.329 E0.1177
    G1 X107.972 Y123.235 E0.1640
    G1 X108.021 Y123.173 E0.1664
    G1 X108.254 Y122.951 E0.1760
    G1 X109.301 Y123.998 E0.2204
    G1 X109.536 Y123.667 E0.2325
    G1 X108.543 Y122.675 E0.2745
    G1 X108.647 Y122.575 E0.2788
    G1 X108.857 Y122.422 E0.2866
    G1 X109.780 Y123.346 E0.3257
    G1 X110.090 Y123.090 E0.3377
    G1 X109.183 Y122.183 E0.3761
    G1 X109.335 Y122.072 E0.3817
    G1 X109.533 Y121.967 E0.3884
    G1 X110.399 Y122.834 E0.4251
    G1 X110.709 Y122.577 E0.4371
    G1 X109.902 Y121.771 E0.4713
    G1 X110.177 Y121.624 E0.4806
    G1 X110.282 Y121.585 E0.4840
    G1 X111.070 Y122.373 E0.5173
    G1 X111.081 Y122.367 E0.5177
    G1 X111.081 Y121.818 E0.5341
    G1 X110.695 Y121.433 E0.5504
    G92 E0.0000
    G1 E-1.5000 F1800
    ; layer end
    M104 S0 ; turn off extruder
    M140 S0 ; turn off bed
    G1 X0 ;
    M84 ; disable motors
    ; Build Summary
    ; Build time: 5 hours 24 minutes
    ; Filament length: 21908.2 mm (21.91 m)
    ; Plastic volume: 52695.50 mm^3 (52.70 cc)
    ; Plastic weight: 65.87 g (0.15 lb)
    ; Material cost: 3.03
     
    #5 Hal Reed, Aug 8, 2019
  6. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Well, that answers that :)
    While I have no specific advice to what causes this ... the only thing to look at is hardware.
    Do you have the LCD installed? Is there anything loaded into the configuration for it?

    Failing that ... it becomes a real head-scratcher because the Arduino is the only other thing in the picture that would be processing that input and while I have seem the Mega fail -- I have never seen it fail like that. Rather when it fails it is usually NOT subtle :)
     
    #6 mark tomlinson, Aug 8, 2019
  7. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    also if you were seeing the G1 Z10; in the terminal -- that is almost certainly something actually sending it.
     
    #7 mark tomlinson, Aug 8, 2019

Share This Page