Jump to content

Cura 15.01 release. Oddity with other slicers?


chrisr

Recommended Posts

Posted · Cura 15.01 release. Oddity with other slicers?

I've recently been using Simpify3D for slicing with this default Gcode for startup

G28 ; home all axes

G1 X20 Y20 F3000 ; bring extruder to the front

G92 E0 ; zero the extruded length

G1 Z0.3 ; lower

G1 X35 E30 F225 ; purge nozzle with 30mm of filament

G1 X45 Y20 F2100

G92 E0 ; zero the extruded length again

When first turning my UM2 on and starting a print, this code will try and home the bed (it already is)

That's all fine. The bed will then raise (once everythings up to temperature) and the print will begin.

But subsequent prints (with my UM2 remaining switched on) cause the bed to re-home twice before

printing. i.e the bed will raise up, lower and then raise back up again before the print begins.

It's not particulary problematic, just unnecessary and I'm wondering what's the cause of it?

The ending Gcode is this:

G28 X0 ; home the X-axis

M104 S0 ; turn off heaters

M140 S0 ; turn off bed

M84 ; disable motors

 

Any pointers? :-)

 

Daid?

 

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    The root for this "might" also be in the firmware.

    When I start a new print after having finished one before, my z-stage will stutter when rising. I always have to switch the machine (UMO) off and back on before I can make a new print...

     

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    ...

    It's not particulary problematic, just unnecessary and I'm wondering what's the cause of it?

    ...

     

     

    The root for this "might" also be in the firmware.

    ...

     

    Yep. It is...

    After selecting the file from sd-card the buildplate is raised up to the priming height (20mm) before it even starts reading the gcode.

    This behavior is not related to the GCode-flavor - although priming takes place only for UltiGCode.

    The fact that this will not happen directly after turning on - is more or less "by accident"...

    The firmware has just no clue about the current position of the z-axis before the first "homing"... and runs into the "soft-endstop control".

    Conclusion: i think this has to be fixed in the firmware.

     

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    After selecting the file from sd-card the buildplate is raised up to the priming height (20mm) before it even starts reading the gcode.

    This behavior is not related to the GCode-flavor - although priming takes place only for UltiGCode.

     

    Ah! That's the reason then... I wonder if modifying the start Gcode to "G28 (just_the_head_please_and_not_the_bed)"

    would fix it... I'm tempted to try but I'm wondering what then controls raising the bed to the nozzle to start the print? Is that the firmware again?

     

    Conclusion: i think this has to be fixed in the firmware.

     

    That would be ideal, I guess the Gcode which controlled that raising/priming sequence could always be added to the generated prints Gcode by Cura instead of having it in the UM2's firmware.... or am I missing something very fundamental? :smile: (which is very possible!)

    (Edited for a bit more clarity)

     

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    ...

    That would be ideal, I guess the Gcode which controlled that raising/priming sequence could always be added to the generated prints Gcode by Cura instead of having it in the UM2's firmware.... or am I missing something very fundamental? :smile: (which is very possible!)

    ...

     

    Nothing fundamental.... only a penny:

    The "firmware priming" (and heatup - using UltiGcode) uses the target temperatures of the current material preset. IMHO this is the major (respectively the only...) benefit of UltiGcode - one can print the same gcode file with different materials. This is very convenient (in my opinion) - i frequently switch between PLA and XT for example.

    With those start code generated into the gcode - you would have to reslice for every material (or at least: edit the temperature settings in the file)...

     

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?
    Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    You are awesome :-) You know that right?

     

  • Link to post
    Share on other sites

    Posted · Cura 15.01 release. Oddity with other slicers?

    You are awesome :smile: You know that right?

    Oh no, i didn't want to scare you... (are you always online...?)

    I just had opened the related file already... :grin:

    ...but... wait a minute - this is a praise in any case, isn't it?

    ...first, i want to forward this to my wife... :cool:

     

     

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