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

Change Encoder Steps to Float #343

Closed
wants to merge 1 commit into from
Closed

Change Encoder Steps to Float #343

wants to merge 1 commit into from

Conversation

reecej
Copy link
Contributor

@reecej reecej commented Dec 15, 2017

The encoderSteps and zEncoderSteps variables were changed from int to float, and the changeEncoderResolution function updated accordingly.

Full discussion at: https://forums.maslowcnc.com/t/what-is-correct-chain-pitch/1430/

The encoderSteps and zEncoderSteps variables were changed from int to float, and the changeEncoderResolution function updated accordingly.
@reecej
Copy link
Contributor Author

reecej commented Dec 15, 2017

I see that changes were made to a few of the files I modified here recently and I did not merge soon enough. The CNC_Functions.h changes should now go to System.cpp.

@krkeegan
Copy link
Collaborator

We should also remove the extraneous lines from Axis::write() as well.

@krkeegan
Copy link
Collaborator

Also nice work @reecej, good find. I haven't had a chance to test it this solves all of it

@reecej
Copy link
Contributor Author

reecej commented Dec 15, 2017

@krkeegan, are you talking about removing the steps*2, round, and /2? If so, I can include that as well.

Also, if you could test at some point and see if it works, that would be very much appreciated. I don't have my Maslow kit yet so I can't validate that this fixes the error.

@krkeegan
Copy link
Collaborator

I made PR #344 which fixes the conflict so that @BarbourSmith doesn't have to figure it out.

I still need to test that this solves all of the problems, but I am pretty sure it does.

Nice work!

@BarbourSmith
Copy link
Member

Great! I will close this pull request and wait on merging #344 until we have confirmed that it fixes the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants