Jump to content

Jerk / Motion control


DivideByZero

Recommended Posts

Posted · Jerk / Motion control

Hi,

 

In Cura 3.6 I switched off Jerk control via the tick box. I would have assumed that this should then let the printer use its defaults.

 

Though something strange happened, after printing, I did an M503 and it returned a jerk of 20. I double checked my FW and it was set to 8 when I flashed it.

 

I rebooted my printer and a M503 then reported the 8 I was expecting.

 

Any suggestions what I should do to test what is causing this please? Any ideeas what I can look for in the GCODE to check if something is changing it?

 

Ultimately, what I want is to be able to control the print speed itself in Cura, but accelleration and jerk should be done by the printer firmware defaults.

 

FYI. Printer is a CR-10S running Marlin 1.1.8.

 

Thanks

  • Link to post
    Share on other sites

    Posted · Jerk / Motion control
    1 hour ago, DivideByZero said:

    Any suggestions what I should do to test what is causing this please? Any ideeas what I can look for in the GCODE to check if something is changing it?

     

    Be aware that Marlin uses "sticky" parameters. All settings stay at the last value until the next reboot (or M501).

    If you want to be sure that every print starts with the stored values, add M501 at the beginning of the start script.

     

    If you want to check the generated gcode: jerk can be changed with M205, acceleration with M204.

    (follow the links for details).

     

    • Like 1
    • Thanks 1
    Link to post
    Share on other sites

    Posted · Jerk / Motion control
    58 minutes ago, fergazz said:

    Did you save it in EEPROM? 

     

    Yeah, when I updated the FW I saved it. Something had changed the max_x_jerk etc. from 12 to 20 (just double checked). Reboot and it was back to normal.

     

    21 minutes ago, tinkergnome said:

     

    Be aware that Marlin uses "sticky" parameters. All settings stay at the last value until the next reboot (or M501).

    If you want to be sure that every print starts with the stored values, add M501 at the beginning of the start script.

     

    If you want to check the generated gcode: jerk can be changed with M205, acceleration with M204.

    (follow the links for details).

     

     

    Thanks - good info.

    Definitely happening in Cura. I even have M204 + M205 setup in my startup code for the correct values... but then after that, I get this:

     

    ;LAYER_COUNT:50
    ;LAYER:0
    M107
    M204 S5000
    M205 X30 Y30
    G0 F3600 X130.766 Y130.38 Z0.2
    M204 S500
    M205 X20 Y20
    ;TYPE:SKIRT

     

    Above we can see  X20 Y20 - which is what it ends up.

     

    Just to double check... I don't have "Enable Acceleration Control" or "Enable Jerk Control" on, that's all I need to switch off right?

     

    Let me reset my profile again and see if I still get that. At least I can find out without having to print now. Thanks

     

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