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

Unresolved First layer way too thin with cura

Discussion in 'Troubleshooting' started by Aaron Lee, Jun 27, 2015.

  1. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    I was trying to print with cura because I like it better than matter control, but when I start to print, the nozzle is so close to the print bet that the extruder can't push filament. It just grinds so I have to abort the print. How can I adjust the height of the nozzle on the first layer? I'm printing at 0.2mm layer height with initial layer thickness set at 0.3 and initial layer width at 100%.
     
    #1 Aaron Lee, Jun 27, 2015
  2. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,915
    Likes Received:
    7,338
    #2 mark tomlinson, Jun 27, 2015
  3. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    Thanks Mark... I already followed that guide to set up Cura initially.

    I don't want to sound ungrateful, but I'm not sure what I'm missing..
     
    #3 Aaron Lee, Jun 27, 2015
  4. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,915
    Likes Received:
    7,338
    The initial Z offset is probably the issue.
    I don't use Cura so if the guide doesn't help someone else who does can toss out some ideas.

    The Slicer layer heights are all on top of the z offset.

    Pretty sure the Z offset has to go into the startup GCode with Cura.
    As long as you have the correct offset in there you should be good.

    (your offset will likely be different than other peoples, it is a custom setting)
     
    #4 mark tomlinson, Jun 27, 2015
    Last edited: Jun 27, 2015
  5. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    I thought of that. The Z offset in the gcode on matter control is Z0 and it prints pretty well. Tried changing it to M565 Z0 on cura and it didn't seem to have any effect.

    Sent from my SM-G900A using Tapatalk
     
    #5 Aaron Lee, Jun 27, 2015
  6. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,915
    Likes Received:
    7,338
    Z0 is zero offset.
    Try a larger, negative number (more negative -> further from bed).

    That will exhaust my ideas for Cura. @Mike Kelly or someone who uses it will be able to add some value.

    (the zero may have worked in MC if it was doing its own auto-leveling)
     
    #6 mark tomlinson, Jun 27, 2015
  7. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    Crap, I had a very long response written and then remembered that Robo didn't enable writing to EEPROM on their firmware by default.

    Short and sweet, model a small square that is one layer thick make sure that on the advanced tab Initial layer thickness (mm) is thicker than your layer size by some fraction of a mm. Print it. measure it with calipers, if it is bigger than you normal layer size increase your Z_Offset (M565) by making it a larger negative number. If it measures smaller decrease the Z_Offset by using a smaller negative number. Yes I understand this is backwards from the way the whole world treats negative numbers, but apparently Marlin firmware exists in some other reality. Reprint it again, remeasure it. At some point the one layer object will be the same size as your specified layer and you will have squished it by the difference between your normal layer and your Initial layer thickness (mm). At this point place this derived and now tested value of Z_Offset in your startup gcode and don't change it. Make sure all your profiles use the same fractional increase in initial layer height regardless of typical layer height and it will always squish the same amount.
     
    #7 WheresWaldo, Jun 27, 2015
  8. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    Thanks for the replies, both of you. I had to go to work (pffft) but I'll try your suggestion when I get home.

    Sent from my SM-G900A using Tapatalk
     
    #8 Aaron Lee, Jun 27, 2015
  9. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    Okay.. When I try changing M565 it doesn't change anything

    Sent from my SM-G900A using Tapatalk
     
    #9 Aaron Lee, Jun 28, 2015
  10. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    Here's what Cura says when I connect it to the printer:

    < Marlin1.0.0
    < echo: Last Updated: Jun 17 2015 12:21:32 | Author: (RoBo 3D, R1 Single Extruder)
    < Compiled: Jun 17 2015
    < echo: Free Memory: 3771 PlannerBufferBytes: 1232
    < echo:Hardcoded Default Settings Loaded
    < echo:Steps per unit:
    < echo: M92 X80.00 Y80.00 Z2560.00 E723.38
    < echo:Maximum feedrates (mm/s):
    < echo: M203 X500.00 Y500.00 Z5.00 E25.00
    < echo:Maximum Acceleration (mm/s2):
    < echo: M201 X9000 Y9000 Z100 E10000
    < echo:Acceleration: S=acceleration, T=retract acceleration
    < echo: M204 S1300.00 T3000.00
    < echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
    < echo: M205 S0.00 T0.00 B20000 X17.00 Z0.40 E5.00
    < echo:Home offset (mm):
    < echo: M206 X0.00 Y0.00 Z0.00
    < echo:pID settings:
    < echo: M301 P22.20 I1.08 D114.00
    < echo:SD init fail

    this line(< echo: M206 X0.00 Y0.00 Z0.00) shows Z offset as 0 and that doesn't seem to change when I edit the starting GCode. What can I do?
     
    #10 Aaron Lee, Jun 28, 2015
  11. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    So where is the M565 command. What you are showing is what is in EEPROM, because the Robo guys failed to enable EEPROM writing, you need to set M565 every single time the printer is started. If you do a M565 Z-1 at the prompt then do an M565 after it, it should report Z= -1.
     
    #11 WheresWaldo, Jun 28, 2015
    Aaron Lee, Mike Kelly and mark tomlinson like this.
  12. Aaron Lee

    Aaron Lee New Member

    Joined:
    Jun 17, 2015
    Messages:
    16
    Likes Received:
    2
    That's what I needed. I entered the M565 command in the terminal before printing and got results. Changing it in the starting gcode does nothing. At least I got results. Thanks guys. Once I get this calibrated I get the feeling my prints are going to be much better than I've been getting with mattercontrol

    Sent from my SM-G900A using Tapatalk
     
    #12 Aaron Lee, Jun 29, 2015
  13. Mike Kelly

    Mike Kelly Volunteer

    Joined:
    Mar 11, 2013
    Messages:
    6,967
    Likes Received:
    2,277
    If m565 isn't working for you, there's another method using a force defined home definition

    After G28 do this

    Code:
    G1 Z1.0 ; Raise Z axis 1 mm (adjust for your printer) to the true Zero
G92 Z0 ; Force define position as 0
G29 ; Run autolevel routine
     
    #13 Mike Kelly, Jul 6, 2015

Share This Page