Jump to content

The slicer flow rate settings are often ignored / notr in gcode


CBX_Micha
Go to solution Solved by Slashee_the_Cow,

Recommended Posts

Posted · The slicer flow rate settings are often ignored / notr in gcode

Hello community,

 

if I specify flow rates other than 100% in CURA 5.6.0 (often 97% for the first layer, then 95%; depending on the material), this flow rate "M221 Sxxx" is mostly not adopted into the created gcode (searching with np++) so the used print server (Repetier) and so also the printer (Marlin 2) don't know about.
Strangely enough, sometimes it works, but despite intensive searching, I just can't figure out under what circumstances it works and when it doesn't.



Is that just me?

  • Link to post
    Share on other sites

    Posted (edited) · The slicer flow rate settings are often ignored / notr in gcode

    You don't have to use the M221 command to set flow rate - you just calculate it the extruder position.

     

    Try making some gcode with flow rate changes, and then one that's 100%, and see what the E value is in the last G1 move on the first layer.

     

    All that M221 does is do those calculations for you.

    Edited by Slashee_the_Cow
  • Link to post
    Share on other sites

    Posted · The slicer flow rate settings are often ignored / notr in gcode

    Hmmm... Ok.
    This means that the flow rate setting in CURA is converted to the extrusion rate and does not appear as M221 in the gcode... Did I understand that correctly?
    This also means that the print server doesn't notice anything and the flow rate set in the print server of, for example, 100% represents the flow rate of, for example, 90% converted into CURA... Correct?

  • Link to post
    Share on other sites

    • Solution
    Posted · The slicer flow rate settings are often ignored / notr in gcode

    A print server won't notice the difference, it's just sending the code Cura creates. If your server is set to 100% flow rate then it shouldn't touch the values Cura has calculated, so if you had 100% on the server and 90% in Cura, it will go at 90%.

  • Link to post
    Share on other sites

    Posted · The slicer flow rate settings are often ignored / notr in gcode

    Are there any settings/circumstances in CURA that still allow an M221 to be integrated into the gcode? Because occasionally when the gcode is transferred from CURA to the server, the previously set 100% on the server is changed. I just haven't been able to figure out in what context and why...

  • Link to post
    Share on other sites

    Posted · The slicer flow rate settings are often ignored / notr in gcode
    50 minutes ago, CBX_Micha said:

    Are there any settings/circumstances in CURA that still allow an M221 to be integrated into the gcode?

    It could be changed by a post-processing script, and often startup gcode will contain "M221 S100" to make sure the flow rate is set to 100%, but I just searched literally all my gcode files (gotta love Notepad++) and those are the only instances of M221, never in anything generated by Cura itself.

     

    Unfortunately I'm not familiar with your server software so I wouldn't know of any other reasons why it could do that.

  • Link to post
    Share on other sites

    Posted (edited) · The slicer flow rate settings are often ignored / notr in gcode

    The flow as entered in the materials category of the settings is never put in the gcode as a M221 command by Cura. Instead this setting is used to calculate the E steps in extruding moves.

     

    The "Tweak at Z" post processing script may be used to insert M221 commands in the gcode at certain heights/layers. This command acts as a "multiplier" on top of the flow as entered in the materials category.

    Edited by ahoeben
  • 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...