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

PFW-1055: M350 for all axis - MK3 #2057

Merged
merged 2 commits into from
Nov 8, 2019
Merged

PFW-1055: M350 for all axis - MK3 #2057

merged 2 commits into from
Nov 8, 2019

Conversation

leptun
Copy link
Collaborator

@leptun leptun commented Jul 29, 2019

Closes #2024

@vintagepc
Copy link
Contributor

I've applied this to a local build and it does indeed work as expected.

@leptun
Copy link
Collaborator Author

leptun commented Nov 4, 2019

Testing: Try setting a different resolution for X or Y (eg 32) and see if everything still works. Also test saving the values to eeprom

uint16_t res = tmc2130_get_res(i);
tmc2130_set_res(i, res_new);
cs.axis_ustep_resolution[i] = res_new;
uint16_t fac;
Copy link
Collaborator

@DRracer DRracer Nov 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even though extracting this var away from the if-else subtree may look like correct programming paradigm, however it may also prevent optimization

@DRracer DRracer merged commit 4cf2f05 into prusa3d:MK3 Nov 8, 2019
@DRracer DRracer changed the title M350 for all axis - MK3 PFW-1055: M350 for all axis - MK3 Nov 15, 2019
@leptun leptun deleted the MK3_fix_M350 branch January 9, 2020 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

M350 non-functional for X/Y/Z
3 participants