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

OctoPrint & Cura - Printhead too high on prints....

Discussion in 'Software' started by CDitty, Dec 29, 2016.

  1. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    As you can see from the my recent forum posts, I've been playing with OctoPrint and various slicers. Somehow, during all that messing around, I seem to have messed something up. Anything I try and print now prints about 1/4" off the print bed.

    I've gone through my OctoPrint setup and the Cura setup and they look fine, atleast to me. I will include my gcode startup code and config settings incase someone wants to see them.

    OctoPrint
    - Before Print
    Code:
    G28 X0 Y0 Z0 ; home all axes
    G1 Z5 F5000 ; lift nozzle
    M109 S210 ; set the extruder temp and wait
    M140 S60 ; set the hotbed temp and wait
    G28 X0 Y0 Z0 ; Home Z again in case there was filament on nozzle
    G29 ; probe the bed
    - After Print Completes
    Code:
    M104 S0 ; turn off temperature
    M140 S0
    G1 X10 Y200
    M84     ; disable motors
    Cura
    - Start code
    Code:
    G28 X0 Y0 Z0 ; home all axes
    G1 Z5 F5000 ; lift nozzle
    M109 S210 ; set the extruder temp and wait
    M140 S60 ; set the hotbed temp and wait
    - End Code
    Code:
    M104 S0 ; turn off temperature
    G1 X10 Y200
    M84 ; disable motors
    Cura profile - Just remove the .txt from the ext.
     

    Attached Files:

  2. Geof

    Geof Volunteer Moderator
    Staff Member

    Joined:
    Nov 9, 2015
    Messages:
    6,757
    Likes Received:
    2,339
    theres no z offset in any of your start up scripts? Never used Octo but I'd imagine you would need a z offset. also may want to check your z endstops to make sure they arnt out of whack.
     
  3. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    It's the same code as what was in MC. The only diff is the [temperature] and the M140 line for the hotbed.

    Code:
    G28 X0 Y0 Z0 ; home all axes
    G1 Z5 F5000 ; lift nozzle
    M109 S[temperature] ; set the extruder temp and wait
    G28 X0 Y0 Z0 ; Home Z again in case there was filament on nozzle
    G29 ; probe the bed
     
  4. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    As I mentioned to you before get rid of all scripting in OctoPrint the 7 sections in OctoPrint >> Settings >> GCODE Scripts should all be blank. You should take care of any scripting needs all within Cura. Because of the way you have this set up there are commands that work at cross purposes.

    Here is what is happening when you start a print.
    1. OctoPrint homes all axis (also unless you are homing a specific axis just use G28 and not G28 X0 Y0 Z0)
    2. OctoPrint lifts the nozzle 5 mm
    3. OctoPrint sets extruder temp to 210°C then bed temp to 60°C
    4. Octoprint homes again
    5. OctoPrint performs the auto-leveling routine
    6. Cura homes all axis a third time (do you really need to home three times)
    7. Cura lifts the nozzle 5 mm
    8. Cura sets the temperature of extruder and bed to 210°C and 60°C respectively
    9. Your actual print starts.
    Can you see the issue here?
     
    Geof likes this.
  5. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    I must have missed the gcode part.

    It does make sense and I was thinking that it had to be the code somewhere. But since the G1 Z5 F5000 was in MC, I figured it needed to be elsewhere too.

    I'll test it all in about an hr when I get home.

    Thanks. I'll report in later and update.
     
  6. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    In Cura your start up code is included in every single model you slice with Cura. So there is no need to 'Initialize' anything in OctoPrint.

    Cura Start code should probably look something like this:
    Code:
    G90    ; movement absolute values
    M82    ; extruder absolute values
    G28    ; home all axes
    G29    ; auto-level
    M565 Z-1.0    ; Z-Offset, adjust as necessary
    M190 S{print bed temperature}    ;set bed temp and heat
    M109 S{print temperature}    ;set extruder temp and wait until heated
    M117 Printing...    ;put a message on the LCD status line
    Honestly you are making it way more complicated than necessary. Remember the simplest processes are usually the best ones.

    In your Cura end code don't forget to turn off the bed temperature also, add a M140 S0 in there somewhere
     
    #6 WheresWaldo, Dec 29, 2016
    Last edited: Dec 29, 2016
  7. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    Thanks. I have a tendency to over think/complicate things from time to time.
     
  8. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    @CDitty if you are interested I could upload my version of Raspian Jessie with OctoPrint installed. It is still configured for DHCP. I actually configure my entire network for DHCP and use MAC filtering at the DHCP server to divvy out Static Leases to machines that need to be in permanent locations (media server running PLEX, network laser printer, print servers like OctoPrint). Also it is not configured for Bonjour since I only use Windows and a tiny amount of Linux and Apple abandoned Bonjour for Windows ages ago. HAProxy does not have authentication set up, but since you configured yours for outside access already you likely know how to get that done. I have a rPi camera module so mjpeg-streamer is set up and configured properly. On a 4GB microSD you will have approximately 50% free space after you expand the file system (on 2GB there is about 14KB left).

    I tried to build it so there is nothing extra/unnecessary. OctoPrint has Display Status and Printer Statistics and that is all the additional plugins.
     
  9. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    Sure. Can't hurt to try. Which rPi did you build it on? Last time I built some on the rPis, it was Pi specific. Something for a 2 wouldn't work on a 3.

    I think I'm going to have to redo my Octo this weekend anyway. I bought a rPi camera and the damn little plastic piece on the pie camera port broke. Can't get it to work now. Luckily I have a few rPis just lying around begging to be used.

    Btw...did you update your octo to 1.3?
     
  10. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    I have a 2 and a 3 and it works on both, I used OctoPrint 1.4 devel

    Here is the hardware I used
    rPi2, Waveshare 3.5" A (SPI, 320 x 480, TFT) the drivers are loaded for all their screens, I hardwire so no WiFi dongle, rPi camera module v2 (8mp).
    rPi3, Waveshare 4" (HDMI, 800 x 480, IPS)
     
    #10 WheresWaldo, Dec 30, 2016
    Last edited: Dec 30, 2016
  11. CDitty

    CDitty Member

    Joined:
    Dec 8, 2016
    Messages:
    67
    Likes Received:
    7
    Awesome. What method do you want to try and transfer it?
     
  12. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    I think it's too big to just post here, PM me you email address and I will send it to you later today.

    I also think the move to Jessie eliminated a lot of the specific rPi2 v. rPi3 stuff.
     
  13. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    Robo posted a few Cura 15.04.6 profiles on their Github just a few days ago, these could be used for an OctoPrint setup by putting them on the rPi in the appropriate directory. https://github.com/Robo3D/Slicing-Profiles
     

Share This Page