Page 4 of 4

Re: Variable acceleration and Jerk

Posted: Wed Jan 30, 2019 3:27 pm
by S3D-Jake
fael097 wrote:
Tue Jan 29, 2019 1:29 pm
this works apparently.

however is there a code to set specific acceleration and jerk for travel movements?
There isn't a comment in front of travel moves. You could try using a replace command on your retractions to have them be followed up with a new acceleration value.

Re: Variable acceleration and Jerk

Posted: Thu Apr 04, 2019 2:23 pm
by shguevara
Hi, just found this useful thread. I have added the code in the post processing section, my question is: shouldn't I be able to see the g-codes for M204 being executed on my terminal? because I don't see them which makes me think that S3D is not processing the script. By the way I have added the acceleration/jerk script before the send to octoprint script.

Thanks in advance for any help

I have the following:

{REPLACE "; feature outer perimeter\n" "; outer perimeter\nM204 S600\n"}
{REPLACE "; feature inner perimeter\n" "; inner perimeter\nM204 S1200\n"}
{REPLACE "; feature solid layer\n" "; solid layer\nM204 S1000\n"}
{REPLACE "; feature infill\n" "; infill\nM204 S2000\n"}

curl -k -H "X-Api-Key:543AD2E1B2AA48E4868FA6546988E245" -F "select=true" -F "print=true" -F "file=@[output_filepath]" "http://192.168.0.54/api/files/local"

Re: Variable acceleration and Jerk

Posted: Thu Apr 04, 2019 3:01 pm
by S3D-Jake
Check your G-code both locally and on your octoprint's storage. If the replace has been executed successfully the M204 commands should be there.