Jump to content

start Gcode is not the same as v15.04.6


Yakie

Recommended Posts

Posted · start Gcode is not the same as v15.04.6

Hi,

I switched from V15.04.6 to V3.2Beta today and copied my gcode to the new curam but instead of starting tho head the bed and directly moving on to the next tasks it first heats the bed and then the nozzle? how can i change this?

Here is my Gcode

M140 S{print_bed_temperature}
M0
G28
G29
M140 S{print_bed_temperature}
M104 S{print_temperature}
M109 S{print_temperature} ; Wait for nozzle temp
M190 S{print_bed_temperature} ; Wait for bed temp
G92 E0
G4 S3
M0

 

  • Link to post
    Share on other sites

    Posted · start Gcode is not the same as v15.04.6

    By the way, the bed usually takes longer than the nozzle so that is kind of desired behavior somewhat as if you leave the filament too hot for too long it can bake into a caramelized gunk.  PLA can usually take it but other materials can't.

  • Link to post
    Share on other sites

    Posted · start Gcode is not the same as v15.04.6
    35 minutes ago, gr5 said:

    By the way, the bed usually takes longer than the nozzle so that is kind of desired behavior somewhat as if you leave the filament too hot for too long it can bake into a caramelized gunk.  PLA can usually take it but other materials can't.

    I'll first let my bed head up and at the same time I'll level the bed after that the nozzle starts to hear but now I'll have to wait untill both nozzle and bed are heated to auto level the bed it takes longer.

    37 minutes ago, gr5 said:

    I think you want this answer here:

     

    Thank you I'll try this in my next print! :)

  • Link to post
    Share on other sites

    Posted · start Gcode is not the same as v15.04.6

    The replacement patterns changed between 15.x and 2.x/3.x. Here's your gcode snippet with the new patterns:

    M140 S{material_bed_temperature}
    M0
    G28
    G29
    M140 S{material_bed_temperature}
    M104 S{material_print_temperature}
    M109 S{material_print_temperature} ; Wait for nozzle temp
    M190 S{material_bed_temperature} ; Wait for bed temp
    G92 E0
    G4 S3
    M0

     

    • Like 1
    Link to post
    Share on other sites

    Posted · start Gcode is not the same as v15.04.6
    1 minute ago, ahoeben said:

    The replacement patterns changed between 15.x and 2.x/3.x. Here's your gcode snippet with the new patterns:

    
    M140 S{material_bed_temperature}
    M0
    G28
    G29
    M140 S{material_bed_temperature}
    M104 S{material_print_temperature}
    M109 S{material_print_temperature} ; Wait for nozzle temp
    M190 S{material_bed_temperature} ; Wait for bed temp
    G92 E0
    G4 S3
    M0

    oh okay! thank you I've already replaced them, thanks alot! :D

     

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