Jump to content

Starting G-code before temperature setting


Recommended Posts

Posted · Starting G-code before temperature setting

I am using Cura 2.3.99 from an Ubuntu PPA, and I have run into a problem: the start G-code I provide appears after the heater commands Cura automatically generates. This is a problem because I use an ATX power supply, which needs to be turned on before the heaters will work. This is easy - just run M80 before heating - but is there any way to make it happen in Cura?

I'm perfectly happy using variables - I assume using python's .format {} syntax - and writing the heater commands myself. in fact I'd prefer it, because the Cura default waits for the bed to reach temperature before starting the hot end heater, and I'd rather heat both at once. But there are two problems: I have no idea what the variables for print temperature and bed temperature are called, and even if I put those commands in the start G-code, Cura still prepends its own heater commands. Is there a way around this? Is there any documentation on the heater commands? I tried exporting the material definition file, and the XML contains variables "print temperature" and "heated bed temperature", but these don't get interpolated with {} either as is or with underscores replacing the spaces.

  • Link to post
    Share on other sites

    Posted · Starting G-code before temperature setting

    The correct variables for your startcode:



    And about the heater commands Cura prepends:

    I can't remember exactly but it depends on some settings, this was discussed here not long ago ...

  • Link to post
    Share on other sites

    Posted · Starting G-code before temperature setting

    Thank you. Are these all listed anywhere? Or visible within the source code?

    The extra heater commands are the bigger problem, though, since they force me to manually run M80 before I can print anything, and they are slower than necessary. They would also be an obstacle to people who need to do autoprobing cold.

  • 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...