Jump to content

Cura not detecting first layer above support as bottom


breexly

Recommended Posts

Posted · Cura not detecting first layer above support as bottom

I would like to chime in on this, for ages I've been looking for a way or explanation why Cura doesn't interpret the layers above the support / support interface (after the z gap) as bottom layers, since I like to set the flow on the layer(s) directly (after the z gap) over the support/support interface.

 

 

Regards

Ksanto

  • Link to post
    Share on other sites

    Posted (edited) · Cura not detecting first layer above support as bottom

    "the layer above the support gets recognized as walls". 

    @breexly It depends on the gap you set between the support and the model.  The default is 1 layer height.  If that is the case in your setup then the layer above the interface has been left empty of support and it IS only walls.  The skin doesn't start until above the gap.

     

    @Ksanto it should be a "bottom" skin.

    Here I've set the "Bottom Layers" to 0.

    image.thumb.png.9d0dd7ae51ff476d7259a5013b4ad0b5.png

     

    And here they have been set to 1

    image.thumb.png.24adb72626c14479e321f021ab3c5787.png

     

    There really isn't a way to set the flow on the "First layer above support".  You would need to set the flow of "All Skins" with the "Material / Top Bottom Flow" setting.  

    In the case of my example model it's easy to do because the only ";TYPE:SKIN" on layer 176 happens to be that area over the support.  That won't always be true.  It would still require going into the gcode and manually adding an M221 S??? at the start of the "SKIN" and then M221 S100 at the end of that gcode section.

     

    Edited by GregValiant
  • Link to post
    Share on other sites

    Posted · Cura not detecting first layer above support as bottom

    Will look into that tomorrow, I did never see any difference in flow over support when bumping up the flow only for bottom layers. Thank you for confirmation.

     

    Regards

    Ksanto

  • Link to post
    Share on other sites

    Posted · Cura not detecting first layer above support as bottom

    When you adjust the "Flow" in Cura it goes right into the calculation of the E numbers so it isn't really possible to see a flow change when checking the gcode.  That is especially true with the variable line width.  There are no "M221" lines to jump out at you.

     

    Adjusting the flow (or speed or fan) of the "first skin above support" can't really be done perfectly in post process either.  The "first skin above support" might not be the only "skin" on a particular layer and there is no way to tell the skin that you don't care about from the skin that you want to change a setting for.  You can only do that by manually making a flow change provided you know the XY of the "area of interest" on a particular layer.

     

    What you could do in post process is list the layers that are involved.  All skins on those layers could have their flow/fan/print speed adjusted while walls and infill and such would not.  Not a perfect solution but it would at least be doable and provide some automation.

     

  • Link to post
    Share on other sites

    Posted · Cura not detecting first layer above support as bottom

    Thank you for the additonal Information.

     

    When I sad that I "did never see any difference in flow" I meant in Curas Flow Color Scheme. I do not have the Matrix sighte/eye/vision as you have. (A Yellow, A Brown and a Red Benchy)  😄

     

    Suddenly it works, so as Slashee_the_Cow said :

    On 10/5/2023 at 12:30 PM, Slashee_the_Cow said:

    Computer problem diagnostic step #2: Attempt to show someone else the problem, and it fixes itself so you look a bit silly to whoever you just tried to show it to.

     

    I think I expect to see the change from the sides, but did not realise the the walls surrounding the rise bottom layer still not belonging to them and keep there values and so also there color indipendently.

     

     

    Regards

    Ksanto

     

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 20 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...