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

x cross slide questions #1

Closed
pantonvich opened this issue Feb 5, 2022 · 7 comments
Closed

x cross slide questions #1

pantonvich opened this issue Feb 5, 2022 · 7 comments

Comments

@pantonvich
Copy link
Contributor

pantonvich commented Feb 5, 2022

question on tables.html - and in general - on my x axis how do I account for the gear ratio from the x-stepper to cross slide screw pitch.
From your thingverse cross slide - it looks like you have a 3x - 54/18 but I'm not seeing that in the digital_feed_7e2 or tables.html code that you have posted. I have a 1mm cross slide but an odd 77/13. I started my els about a year ago and just started working on it again last month. I found your github in the last two weeks - so thanks for posting what you have. I'm not that good with github - so not sure how to correctly tag this

@gerritv
Copy link

gerritv commented Feb 5, 2022

You need to calculate the number of steps to revolve the leadscrew one revolution. The motor is usally 200 steps/rev, add in the 77/13 ratio (5.923) to get 1184.6 steps per rev?

@pantonvich
Copy link
Contributor Author

thats what I was thinking so I tried setting MOTOR_X_STEP_PER_REV to 1185. I also tried setting the SCREW_X to 17 with motor 200 - but got an error - see below - looks like if I set the MxStep_X to 1 it's not an issue - so I'll try that.

Digital_Feed_7e2:55: error: static assertion failed: Ð?еверно задано значение MAX_FEED
static_assert(f > 1, "Ð?еверно задано значение MAX_FEED");

@kachurovskiy
Copy link
Owner

I prefer changing the leadscrew pitch - using 1:3 reduction on cross-slide with 1.25mm screw I've entered 42 as SCREW_X. That gives something like 1% of error on cross-slide movements in theory but I'll think of something when it becomes a problem 😄

Getting MAX_FEED error means that system wants you to reduce your MAX_FEED constant value (line 23). I believe validation errors like this ensure that the system has time to issue the stepper pulses in all conditions.

@kachurovskiy
Copy link
Owner

Another option to make MAX_FEED validation happy is to reduce micro-stepping e.g. from 800 steps per revolution to 400 - or so I believe.

@pantonvich
Copy link
Contributor Author

I set it to 200 i.e 1 and and changed the driver to 200- I'm trying to verify what movement I get with 100 clicks from the handcoder ...

@pantonvich
Copy link
Contributor Author

so with
#define MOTOR_X_STEP_PER_REV 1185 // X motor steps (cross-slide) - almost always 200, microsteps configured below
#define SCREW_X 100
#define McSTEP_X 1

I get 1mm on the x axis for 100 clicks of the hand coder - is that what I should expect?

@kachurovskiy
Copy link
Owner

I get 1mm on the x axis for 100 clicks of the hand coder - is that what I should expect?

Yes. Or 10 clicks on 10x resolution.

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

No branches or pull requests

3 participants