Jump to content

Question regarding start scripts


MTG

Recommended Posts

Posted (edited) · Question regarding start scripts

Hey,

I'm using Cura 4.1 and Octoprint, so I have to use the start script function of Cura. With only one Material it wasn't a problem, but I have modiefied my UM 2+ Extended for dual printing. So I made a startup script for dual extrusion. It's basically just:

 


T0

//Extrude T1, Wipe and do stuff

T1

//Extrude T1, Wipe and do stuff

T0

As you See, I make sure that I have T0 selected, extrude and wipe, change to T1, do the same and back again to T0. Then I'm ready to start with T0.

 

So, when my part starts with T0, no problem here, everything is working normally. But when my part starts with T1, I mess up because my startup script ends with T0 and the Cura-generated toolchange is before the user startup script:

 

// How it is:

T1 //<- This is the Cura generated toolchange

//cura generated stuff like heating etc

; Start user startup script dual ---------------------------------------------------

T0 //My toolchange

//Extrude, wipe and stuff

T1 //My toolchange

//Extrude, wipe and stuff

T0 //My toolchange

As you see, it starts with T0 when it should actually start with T1. Now, I have to modify every gcode file by hand, if it starts with T1.

Why is it not like the following (or how can I make this work):

 

// How it should be:

//cura generated stuff like heating etc

; Start user startup script dual ---------------------------------------------------

T0 //My toolchange

//Extrude, wipe and stuff

T1 //My toolchange

//Extrude, wipe and stuff

T0 //My toolchange

; End user startup script dual ---------------------------------------------------

T1 //<- Here should be the the Cura generated toolchange

Wouldn't that be more logical for the final toolchange before the part starts?

I hope it's understandable what I mean

 

 

 

 

Edited by MTG
  • Link to post
    Share on other sites

    Posted · Question regarding start scripts

    Use

    T{initial_extruder_nr}

    instead of the final

    T0

     

    Cura will fill in the extruder number of the first used extruder for the {initial_extruder_nr} part.

    • Thanks 1
    Link to post
    Share on other sites

    Posted · Question regarding start scripts

    Oh, nice, I knew I couldnt be the only one facing this problem.

     

    Is there a way to only perform one part of the start script if only one Extruder is used, by the way?

  • Link to post
    Share on other sites

    Posted · Question regarding start scripts
    35 minutes ago, MTG said:

    Is there a way to only perform one part of the start script if only one Extruder is used, by the way? 

     

    No, there is not.

    • Like 1
    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
        • 16 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.
        • 0 replies
    ×
    ×
    • Create New...