Trouble with M201 and M566 settings

Jered

@Norder
Thanks, I will make that change.

Norder

@Norder
Please post a few screenshots of your printer settings in the slicer.
I think the solution is to be found there, why 3000 are reported although 500 are set.

You are now also talking about the SuperSlicer here, previously there was only talk of Simplify3D.
Are you now using Simplify3d and the SuperSlicer?

Please write which slicer you use.
And if you use both slicers, please also write whether both slicers have this error in their slice.

Google Translate
-- Original Text --

Poste doch bitte ein paar Screenshots von Deinen Druckereinstellungen im Slicer.
Ich glaube dort ist die Lösung zu finden warum 3000 gemeldet werden obwohl 500 eingestellt sind.

Du sprichst hier jetzt auch vom SuperSlicer, vorher war nur von Simplify3D die Rede.
Nutzt Du jetzt Simplify3d und den SuperSlicer ?

Bitte schreibe welchen Slicer Du nutzt.
Und wenn Du beide Slicer benutzt, dann schreib bitte auch ob beide Slicer diesen Fehler in ihrem Slice haben.

Norder

Screenshots from Simplify3D, there could be a few.
In order not to make the comment too long, which could damage the overview, you are welcome to show the entire settings page in a video.

That only as a tip.

Jered

@Norder
I will try to get to this. I am using Simplify.

Phaedrux

You could share an example sliced gcode file so we can see what it is doing.

Also share or check your other files that get called when a print starts like homeall.g, start.g, etc. See if there are any stray commands in there.

gloomyandy

@Jered Can I suggest that you do the following....

In the console run the following command: M98 p"config.g" if you get any errors reported these need to be fixed.
Reboot your printer
run M201 check the value of the X and Y accelerations
Home your printer
run M201 check the value of the X and Y accelerations

You basically need to go through all of the steps that you normally go through when starting a print, so if you level the bed using G32 then run that and check M201 again, if you create a mesh with G29 then run that and again check with M201 after is. Basically you are trying to identify any changes to the acceleration setting.

If things look correct at each of the above stages then you need to look closely at your generated gcode....

Jered

@gloomyandy
I didn't even think to check those files. You are right!

The accel was being changed in home x, y, and home all! I have changed them all to match the config and all is well!

Thanks so much for bringing this up. I am so use to the "out of the box" printers that I didn't even think to check those files.

Thanks To All Of You Guys!

It can't be easy dealing with us noobs

engikeneer

@Jered FYI, it might be worth creating a macro called 'motor_settings.g' which contains your default acceleration limits etc. You can then call that in config, and at the and of your homing files etc so you only have one place to change your machine limits. I do this on my printer.
Alternatively you could achieve something similar using global variables but I have not been adventurous enough to try them out yet!