Jump to content

startup: heat up only extruders that are getting used


QuantumKittens

Recommended Posts

Posted · startup: heat up only extruders that are getting used

I've been writing a startup gcode for a custom dual extrusion printer. This is the part of the code that heats up the extruders:

M104 S{material_print_temperature, 0} T0   
M104 S{material_print_temperature, 1} T1
M104 T{adhesion_extruder_nr} S{material_print_temperature_layer_0, adhesion_extruder_nr}

I works fine, but will always heat up both extruders, even if the current print uses only uses one of them. The same issue also happens if one extruder is disabled completely via the enable extruder checkbox, since material_print_temperature will always return something (even for disabled extruders, a bug maybe?).

Does anyone know if there is a way to heat up an extruder only if it is actually going to be used in the current print?

  • Link to post
    Share on other sites

    Posted · startup: heat up only extruders that are getting used

    Update: I found a partial workaround: If I don't include any commands for heating up in my startup gcode then Cura will add its own ones before my code. It appers that this correctly takes into account if an extruder is used (even if it stays enabled).

    However, it might be benefical to run my own code first, to allow the preheat process to occur in a specific location and to set various values. Is there a way to achive this or can I somehow include the code Cura generates as part my own code? Where does Cura take the code it inserts from?

  • Link to post
    Share on other sites

    Posted · startup: heat up only extruders that are getting used

    As you have found out, you can either put your own heatup sequence in the start gcode, or CuraEngine can put it before your start gcode for you.

     

    The pattern replacement you can do in the start gcode snippet is fairly "dumb"; it literally just replaces the {}-pattern with the value of the setting. There is no logic applied whatsoever, only simple replacement. It does not "understand" gcode in any way, so it does not realise you are adding a heatup line that refers to a disabled extruder. There are no "conditional" lines. Just replacing a pattern by a value.

     

    Ofcourse the slicer itself is more intelligent than that. So if you tell it a certain extruder is disabled, it is smart enough to construct a heatup sequence that excludes that extruder.

     

    So the logic is as follows:

    If the user has specified a heatup sequence, just do a dumb pattern replacement on it. No further logic possible.

    If not, created a heatup sequence from all the settings specified by the user, taking into account the number of enabled extruders and which extruder will be used first.

    • Like 2
    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

      • 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
      • Ultimaker Cura 5.6 stable released
        Cura now supports Method series printers!
         
        A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
        • 48 replies
    ×
    ×
    • Create New...