Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] M204 P0 T0 in RepRapFirmware #4048

Closed
timschneider opened this issue Jan 4, 2024 · 4 comments
Closed

[BUG] M204 P0 T0 in RepRapFirmware #4048

timschneider opened this issue Jan 4, 2024 · 4 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@timschneider
Copy link

What happened?

The slicer will output M204 P0 T0 in G-Code causing the printjob to fail.

Project file & How to reproduce

Change default acceleration under print settings -> speed -> Default acceleration to a value != 0 -> slice -> change it back to 0 -> slice again -> M204 appears with P0 T0

dfd970b7-2746-4052-a49d-26d50d9735ee.mp4

Shape-Box.zip

Version

2.5.59.6

Operating system

Windows 11

Printer model

Meltingplot MBL 136

@vknvkz
Copy link

vknvkz commented Jan 8, 2024

I have the same problem but with Gcode Flavor = Marlin 2.
This problem appeared in version 2.5.59.5

@vknvkz
Copy link

vknvkz commented Jan 8, 2024

I found a solution, all acceleration values in Print Settings -> Speed -> Acceleration control (advanced) must be 0.
Even the grayed-out cells.

@timschneider
Copy link
Author

I found a solution, all acceleration values in Print Settings -> Speed -> Acceleration control (advanced) must be 0. Even the grayed-out cells.

I would call it a work around :)
If the values are greyed out, they should be ignored by the software and/or set to a value that does not cause any damage.

@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels Jan 10, 2024
@supermerill
Copy link
Owner

thanks for he report.
I made 2 errors:
. forgot to initialize the travel acceleration to 0 at startup
. I had a safeguard for 0 travel accel, but not yet for 0 printing accel.

supermerill added a commit that referenced this issue Jan 10, 2024
supermerill added a commit to NematX/NematXSlicer that referenced this issue Jan 11, 2024
supermerill added a commit that referenced this issue Jan 15, 2024
supermerill added a commit to NematX/NematXSlicer that referenced this issue Jan 17, 2024
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

3 participants