Slicer is overwriting my acceleration values
Weird one today. I have an Ender 5 Plus that's been pretty hopped up. It runs at 2000 acceleration and a speed of 150mm/sec. I mostly use Cura for it and Prusaslicer for my two MK3S.
I tried a file today on Prusaslicer and it seemed to be printing much slower on the 5 plus. I found out it was overwriting my acceleration value of 2000 to 500 and saving it to eeprom. Then the max value I could change in then menus after that was to 1000. I have to reset the Ender's eeprom to get the ability to change it from the Marlin screen.
I'll admit, prusaslicer for me is import and slice. It's all calibrated for the two Prusas so I'm not quite sure what is happening here when it comes to slicing/overwriting eeprom on an Ender 5 Plus with an SKR mini E3 V2 and Marlin 2.1.2
RE: Slicer is overwriting my acceleration values
Have you set your preferred values in the 'Mackine Limits' table which are an Advanced Mode Option in Printer settings?
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Slicer is overwriting my acceleration values
Joan, always a pleasure to see your replies. Yes, I have tried "apply limits" to ignore and emit to g-code. Ignore works for me but emit to g-code should not overwrite my eeprom correct? Doesn't require an M500 command in the g-code?
RE: Slicer is overwriting my acceleration values
Sorry Jason,
I have never actually used this feature. Prusa profiles work OK for me...
I can understand non prusa profiles being less optimised...
if it were my ender, I would create a gcode file, and search it with Notepad++ looking for M500
Regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Slicer is overwriting my acceleration values
The emit to gcode option is the one that includes them and then over rides the ones set in your machine. However it does not do a M500 to save them. So rebooting the machine should restore what was saved to eeprom.
However what your machine actually does with any values sent is determined by its firmware. It’s quite possible that creality is storing them without an explicit M500. Who knows as they modify firmware and don’t post the changes as they are required to by the open source license.
If the menu on the printer won’t go above 1000 then there will be a max value defined in the firmware menu’s for that, if the original eeprom is set above that by creality then it’s just another example of sub par firmware modification, they should have increased the max limit on the menu values to match what they are putting in as base values.
You should use the ignore option in the slicer machine limits page to not send them.
RE: Slicer is overwriting my acceleration values
I have it set to ignore and it still injects an M204 into the g-code. It populates the number from Acceleration Control (Advanced) "Default" (500).
This field is still overwriting the machine with ignore set. It's an odd choice to force acceleration on a printer by default. My other slicers do not do this. This shouldn't have to be disabled, it should have to be enabled.
Since it is a limit, it should fall under the ignore option. My acceleration is set to 3000 and this has been frustrating me all day. My printer would "break" after using Prusaslicer and slow right down. I never expected the slicer to be modifying my printer.
RE: Slicer is overwriting my acceleration values
could you go to prusa slicer git hub, and raise this as an issue please?
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Slicer is overwriting my acceleration values
Will do Joan. I didn't think this was a bug, just thought it was an odd choice in behaviour. I'll see what the response is there.
RE: Slicer is overwriting my acceleration values
Thanks Jason
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Slicer is overwriting my acceleration values
As I expected, I got told to get stuffed. I've had to go through all my profiles and just change it to 3000 and save the new profile. It shouldn't do this.
RE: Slicer is overwriting my acceleration values
I ran across this the other day. Order of operations.
1. Start gCode
2. Filament gCode
3. Advanced acceleration
you MUST set the default value to 0 otherwise it injects that value after both 1 and 2.
filament settings > Speed > Acceleration Controll > Default > Set to 0
RE: Slicer is overwriting my acceleration values
Using ver 2.6.0 alpha6
DIY Delta printer Duet wifi controller
Got the same problem. Superslicer works ok.
Using NotePad++ Found no instance of M500, M201, M203, M204 or M566 unless I enable 'Emit to G-code'. Goint to try and set configuration to machine settings. We will see!