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

Jerk Limits Using Incorrect Units for RepRapFirmware #1500

Closed
bradvaughan opened this issue Aug 23, 2021 · 7 comments
Closed

Jerk Limits Using Incorrect Units for RepRapFirmware #1500

bradvaughan opened this issue Aug 23, 2021 · 7 comments
Labels
awaiting response Further information is requested fix is live in the last release Please download /build the last release and try to reproduce. problem

Comments

@bradvaughan
Copy link

Version

2.3.56.8

Operating system type + version

Windows 10 Pro

Behavior

The "Jerk limits" in the "Machine limits" section on the "Printer Settings" tab indicates the units are in "mm/s". However, RepRapFirmware uses mm/min for this setting. This is an issue for both the time estimates as well as the "Safeguard" and "limit" options.

The resulting M566 command in the generate G-code simply copies the value from the screen, so it's off by a factor of 60x. Thankfully, this is in the direction of being slower than intended, but a bug nonetheless.

Additionally, this causes issues for the time estimates, because you need to put in the correct mm/min values to get the appropriate G-code, so the time estimates end up artificially low. Again, this isn't a huge issue given jerk's relatively minor impact on overall print time in comparison to feed rates and acceleration.

Is this a new feature request?
No

Project File (.3MF) where problem occurs

N/A. It occurs on all G-Code exports for RepRapFirmware that I've tried.

@supermerill
Copy link
Owner

I though I made it, but maybe I forgot to merge...
#632 #440

@supermerill supermerill added fixed for the next version That means that you should be able to test it in the latest nightly build problem labels Aug 23, 2021
@supermerill
Copy link
Owner

Additionally, this causes issues for the time estimates, because you need to put in the correct mm/min values to get the appropriate G-code, so the time estimates end up artificially low. Again, this isn't a huge issue given jerk's relatively minor impact on overall print time in comparison to feed rates and acceleration.

That shouldn't happens, it's converted from mm/min to mm/sec. Maybe it's the feedrate unit that is creating some problems...
Can you post your project where the time estimate is problematicaly slow ?

@supermerill supermerill added the awaiting response Further information is requested label Aug 23, 2021
@bradvaughan
Copy link
Author

bradvaughan commented Aug 23, 2021 via email

supermerill pushed a commit that referenced this issue Aug 23, 2021
also gcode-viewer now read them even if not marlin
#1500
@bradvaughan
Copy link
Author

bradvaughan commented Aug 24, 2021 via email

@supermerill
Copy link
Owner

supermerill commented Aug 24, 2021

There's a problem? I don't see any image and I can't download your project file.

@bradvaughan
Copy link
Author

bradvaughan commented Aug 24, 2021 via email

@bradvaughan
Copy link
Author

3DBenchy-jerk-test

M566 X1200.00 Y1200.00 Z1200.00 E40.00 ; sets the jerk limits, mm/sec

3DBenchy-jerk-test.zip

supermerill pushed a commit that referenced this issue Aug 27, 2021
also gcode-viewer now read them even if not marlin
#1500
supermerill pushed a commit that referenced this issue Sep 6, 2021
also gcode-viewer now read them even if not marlin
#1500
supermerill pushed a commit that referenced this issue Sep 6, 2021
also gcode-viewer now read them even if not marlin
#1500
@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 Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting response Further information is requested fix is live in the last release Please download /build the last release and try to reproduce. problem
Projects
None yet
Development

No branches or pull requests

2 participants