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

G-Code flavor RepRap produces wrong M204 commands #450

Closed
toskium opened this issue Sep 5, 2020 · 2 comments
Closed

G-Code flavor RepRap produces wrong M204 commands #450

toskium opened this issue Sep 5, 2020 · 2 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

@toskium
Copy link

toskium commented Sep 5, 2020

Version

Superslicer 2.2.53

Operating system type + version

Windows 10 pro

3D printer brand / version + firmware version (if known)

DIY Delta printer
Reprap Firmware 3.1.1

Behavior

  • gcode flavor is set to "RepRap"
  • acceleration control is used to define different acceleration values
  • model is sliced, gcode is produced
  • acceleration values according to slicer are ignored

When looking up the relevant lines of gcode you will find:

M204 Sxxxx

According to the documentation over at RRF:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M204_Set_printing_and_travel_accelerations

The proper M204 command looks like:

M204 Pxxx

It seems to be a bug originally coming from the PrusaSlicer code since I can reproduce that behaviour on PrusaSlicer as well.

@supermerill
Copy link
Owner

I have

M204 P500 T1500 ; sets acceleration (P, T), mm/sec^2

please post your project file for me to test.

@toskium
Copy link
Author

toskium commented Sep 5, 2020

Here you go:
testprint.zip

@supermerill supermerill added bug Something isn't working as intended and removed could not reproduce labels Sep 5, 2020
supermerill added a commit that referenced this issue Sep 5, 2020
@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Sep 5, 2020
supermerill added a commit that referenced this issue Sep 6, 2020
@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 Oct 5, 2020
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

2 participants