Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Using a start script from CURA and passing Variables?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    4
    473
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Reefwarriorundefined
      Reefwarrior
      last edited by

      Hi

      I am using CURA as slicer. I would like to eg. have my printer do all levelling, etc. before it commences heating of the hotend - eg heat the bed to XXXC, head to XXXC, do the levelling, and only then heat up to what is required in the file.

      Is there perhaps a way to easily do this? Or am I thinking too complicated?

      Rgds
      Tinus

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        You can use a macro file called start.g to do whatever you want at the start of a print BEFORE the slicer gcode is executed. So you could specify that it heats up and does the homing/leveling/etc and when it's all done that, pases over to the sliced gcode file for final temp setting and starting the print.

        Z-Bot CoreXY Build | Thingiverse Profile

        Nuramoriundefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by

          @reefwarrior in RRF 3.3 you can pass parameters when invoking a macro with M98.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          1 Reply Last reply Reply Quote 0
          • Nuramoriundefined
            Nuramori @Phaedrux
            last edited by

            @phaedrux said in Using a start script from CURA and passing Variables?:

            You can use a macro file called start.g to do whatever you want at the start of a print BEFORE the slicer gcode is executed. So you could specify that it heats up and does the homing/leveling/etc and when it's all done that, pases over to the sliced gcode file for final temp setting and starting the print.

            I do something similar (as a cura user), and call a “wipe.g” file at a certain point once the extruder has primed. A similar approach is easily done to accomplish what the OP is outlining by putting the desired commands prior to printing in a similar “g” file that then is called in the startup code in cura.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA