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

Octoprint question

Discussion in 'Mods and Upgrades' started by Jason Hough, May 17, 2016.

  1. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Hey all,

    I've decided to setup my R1+ with Octoprint (on a RasPi 3), and basically everything has been working great so far except the actual printing part.

    Whenever I try to print, either using gcode sliced on Octoprint, or gcode I upload to Octoprint myself from a known good Cura setup on my PC, the same thing happens: The printer does the bed leveling process, and as soon as it finishes the last spot, the print head moves up a bit and then it just stops. The extruder cools down, the bed stays hot, and the printer is unresponsive after that.

    Any thoughts?

    Is there a known good Printer Profile for Octoprint someone could share with me?

    Thanks in advance for any tips.
     
  2. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    You would likely need to see the GCode terminal to sort that out (i.e. what the printer is responding with at that point).
    Not sure that helps since I am not a current Octoprint user, but this:

    http://wiki.fastbot3d.com/octoprint#toc2

    (I did use it for a small period after it first came out.)

    I have seen that same behavior a number of times without Octoprint in the picture and usually the response codes from the printer will sort it out.
     
    #2 mark tomlinson, May 17, 2016
    Last edited: May 17, 2016
  3. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Here's what the gcode terminal says (the first serveral lines are the auto-leveling):

    Send: N11 G29*34
    Recv: Bed x: 15.00 y: 20.00 z: -0.63
    Recv: Bed x: 110.00 y: 20.00 z: 0.03
    Recv: Bed x: 205.00 y: 20.00 z: 0.37
    Recv: Bed x: 205.00 y: 125.00 z: -0.14
    Recv: Bed x: 110.00 y: 125.00 z: -0.25
    Recv: Bed x: 15.00 y: 125.00 z: -0.84
    Recv: Bed x: 15.00 y: 230.00 z: -0.29
    Recv: Bed x: 110.00 y: 230.00 z: 0.18
    Recv: Bed x: 205.00 y: 230.00 z: 0.41
    Recv: Eqn coefficients: a: 0.00 b: 0.00 d: -0.70
    Recv: planeNormal x: -0.00 y: -0.00 z: 1.00
    Recv: ok
    Send: N12 G1 Z15.0 F9000*20
    Recv: echo:endstops hit: Z:0.41
    Recv: ok
    Send: N13 G92 E0*117
    Recv: ok
    Send: N14 M109 S{print_temperature}*41
    Recv: T:162.3 E:0 W:?
    Recv: T:161.2 E:0 W:?
    Recv: T:160.2 E:0 W:?
    Recv: T:159.4 E:0 W:?
    Recv: T:158.4 E:0 W:?
    Recv: T:157.6 E:0 W:?
    Recv: T:156.7 E:0 W:?
    Recv: T:155.7 E:0 W:?
    Recv: T:154.8 E:0 W:?
    Recv: T:154.1 E:0 W:?
    Recv: T:153.1 E:0 W:?
    Recv: T:152.4 E:0 W:?
    Recv: T:151.5 E:0 W:?
    Recv: T:150.6 E:0 W:?
    Recv: T:149.8 E:0 W:?
    Recv: T:149.0 E:0 W:?​

    And it just continues like that. I sent the exact same gcode file via MatterControl and it prints just fine.

    Any thoughts would be appreciated!
     
  4. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Well, no errors (which is good) but this:

    Send: N14 M109 S{print_temperature}*41

    followed by decreasing temperatures is not a good sign :)
    That almost looks like a slicer issue rather than a printer one (again, that is a good thing).

    Hopefully some octoprinters on here can assist.
    In the interim you can try the mailing list/forum:

    https://groups.google.com/forum/#!forum/octoprint

    There are a lot of others for Octoprint (sorry, not sure which one to suggest).
     
  5. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Hmm, I was actually thinking the opposite, given that for this test I used MatterControl to slice the STL file and save the gcode, then simply uploaded that gcode file to Octoprint. I figured it must be the printer config somehow, or a communications problem.
    Plus the same gcode file works if I send it via MatterControl.

    Going to try using Octoprint to print the same gcode file from the printer's own SD card, rather than over USB. And I will check the Octoprint forums, too. Thanks!
     
  6. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    It occurs to me that perhaps we're both right? What's the only gcode octoprint would be bringing to this party? The start/end snippets in the printer profile (which I grabbed from my Cura setup)... and lookee here:

    M104 S{print_temperature}
    M190 S{print_bed_temperature} ;preheat bed and wait
    G21 ;use metric values
    G90 ;use absolute positioning
    M82 ;set extruder to absolute mode
    M107 ;start with fan off
    G28 X0 Y0 ;home X & Y
    G28 Z0 ;home Z
    G1 Z5 F5000 ;lift nozzle 5mm
    M565 Z0.7 ;use 1.0 Z-offset
    G29 ;run autolevel
    G1 Z15.0 F9000 ;raise nozzle 15 mm
    G92 E0 ;zero the extruder
    M109 S{print_temperature} ;wait for nozzle to heat
    M117 Printing... ;print message on LCD

    I think I'll try removing that line, but I wonder if there are "official" Robo3D Cura start/end gcode I should be using? I think I found these on a forum somewhere...
     
  7. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
  8. XEMA

    XEMA New Member

    Joined:
    Mar 7, 2016
    Messages:
    27
    Likes Received:
    12
    I know this doesn't help too much, but I slice my STL's with S3D and upload them/print with no issues at all.

    Yes, remove that line you mentioned "M109 S{print_temperature} ;wait for nozzle to heat" and these two :
    M104 S{print_temperature}
    M190 S{print_bed_temperature} ;preheat bed and wait

    Octoprint doesn't know how to use that, since the temperatures are in the gcode files. I had the same issues when I migrated from mattercontrol.
     
    Jason Hough and mark tomlinson like this.
  9. WZ9V

    WZ9V Active Member

    Joined:
    Apr 9, 2016
    Messages:
    218
    Likes Received:
    64
    I had similar issues using Pronterface and any slicer with the stock firmware. I upgraded to 1.1.0 RC6 and have not seen it since. YMMV, if your not scared off by new firmware I'd try that and did.
     
  10. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Hmm, okay. Thanks! My printer is only a few months old, I haven't even checked to see if new firmware is available.

    As for the problem, I thought I'd update this: it works as long as I take the temperature command out of the start gcode. No idea why!
     
  11. WZ9V

    WZ9V Active Member

    Joined:
    Apr 9, 2016
    Messages:
    218
    Likes Received:
    64
    Keep n mind the firmware update I referenced is not an official release of Marlin yet. It is Release Candidate 6 (RC6) and I expect at the rate they are patching things there will be a few more RC versions before the official 1.1.0. It's been working well for me and better than what came on it out of the box.
     
  12. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Understood! Thanks for the suggestion.
     
  13. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    Thanks for the info. Out of curiosity, are you saying that the temps are baked into the gcode? So if I have a gcode file I sliced a while back, and want to print it again but with a different kind of filament, I need to re-slice it with the correct filament selected?
    I guess that might be a newbie question...
     
  14. WZ9V

    WZ9V Active Member

    Joined:
    Apr 9, 2016
    Messages:
    218
    Likes Received:
    64
    Most slicers will set their own temperature control as long as they don't see it in your start g-code. If they see it in your start g-code they leave it all up to you. If you want to see what your slicer would do behind the scene, empty out your start g-code, slice something, and then view the g-code in your favorite text editor.

    If you think it will help, I can post my start g-code for Cura that has been working well for me. I don't promise it's commented well though. I reverse engineered it from the MatterControl generated g-code and then started messing around.
     
  15. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    If you sliced it with this sort of thing inside:

    M104 S{print_temperature}
    M190 S{print_bed_temperature} ;preheat bed and wait


    The slicer will substitute in the correct values from the profile it uses. So, yes, at that point you have GCode with temperatures in it. If you later changed them then it would not reflect that.
     
  16. Jason Hough

    Jason Hough New Member

    Joined:
    Mar 23, 2016
    Messages:
    25
    Likes Received:
    2
    That'd be great, thanks much. I'm using some I found in a forum, and managed to get a good print yesterday after I removed all the temperature stuff from it. It would still be nice to compare.
     
  17. WZ9V

    WZ9V Active Member

    Joined:
    Apr 9, 2016
    Messages:
    218
    Likes Received:
    64
    My Cura 15.04.5 settings

    --start.gcode
    ;Sliced by Cura 15.04.5 at: {day} {date} {time}
    ;Basic settings: Layer height: {layer_height} Walls: {wall_thickness} Fill: {fill_density}
    ;Print time: {print_time}
    ;Filament used: {filament_amount}m {filament_weight}g
    ;Filament cost: {filament_cost}
    ;Bed temperature: {print_bed_temperature}
    ;Extruder temperature {print_temperature}
    ;Put printing message on LCD screen
    M117 Initializing
    M190 S{print_bed_temperature}
    M109 S{print_temperature}
    G21
    G90
    M82
    M107
    M117 Auto Bed Leveling
    G28
    G29
    G1 Z10 F{travel_speed}
    G92 E0
    G1 F200 E3
    G92 E0
    G1 F{travel_speed}
    M117 Printing

    -- end.gcode
    M107
    M104 S0 ; turn off extruder
    M140 S0 ; turn off bed
    G1 X10 Y200
    M84 ; disable motors
    M117 Done
    ;{profile_string}
     

Share This Page