Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: Benjammann on January 12, 2019, 07:35:21 PM
-
I'm running a SmoothStepper ESS with a Gecko breakout board. I'm having to set my nema 23 motor steps per unit to 40000 to get correct travel. Is this common? Seems high.
-
Hi,
tell us about your machine...what ballscrews for instance?
What gear/belt reduction between the stepper and the ballscrew?
What are your native units?
Craig
-
Hi,
tell us about your machine..
Craig
Hi Craig, It's a Taig mini mill with a acme 1/4-20 TPI lead screw that is directly driven by the nema 23 stepper. Working in inches. Using the Ethernet version of the SmoothStepper board.
-
In that case your 40000 steps per inch would be correct.
20 TPI x 200 full-steps/rev x 10 micro-steps/full-step = 40000
Steve Stallings
PMDX
-
In that case your 40000 steps per inch would be correct.
20 TPI x 200 full-steps/rev x 10 micro-steps/full-step = 40000
Thanks! Just curious where you got the 10 micro-steps info from?
-
Hi,
10 microsites per fullstep is built into the G540.
Craig
-
10 microsites per fullstep is built into the G540.
Thanks! So I got this all setup and calibrated. I'm having a few issues:
1: When I put jog speed way down low and attempt to bring the end mill close to the part to touch off by continually tapping the arrow key I have mapped to jog, I see the head doing a small bounce back. Am I just not sending enough of a signal or something by having the jog speed so low and then doing a tiny tap on the jog key?
2: When trying to set backlash compensation on the Y axis no matter what value I put it doesn't seem to be compensating. I've checked that it's the correct motor. I did see that I was setting it in Mach vs the SmoothStepper plugin, and that I did not have the backlash compensation enabled in the SmoothStepper plugin, but I was able to get the compensation to work on the other two axis, so im thinking that's not the issue. I haven't had time to check what happens if I try to set it via the SmoothStepper plugin.
3: I'm running a demo of Mach 4. Is this why the return to work zero button doesn't work? I am guessing that's what I press when I want to return to X0 Y0 Z0 that I've set? It's not working.
Thanks!
3:
-
Hi,
can't answer 1). It sounds to me like the jerk caused by taking a small step is flexing the machine. The spring back
you are observing is just that...the spring of the machine.
2) To my knowledge Mach does not have backlash compensation, it MUST be enacted it real-time and therefore is
SOLEY the responsibility of the ESS.
Please double check which of the two plugins (Control vs ESS) the settings appear.
Craig
-
Hi,
had a thought about question 3). I don't think its got anything to do with Demo mode.
Hit the <GoTo Work Zero> button and have a look at the status message in the lower left of the screen.
What does it say?
Craig
-
status message in the lower left of the screen.
What does it say?
Status message says: Axis 3 commanded while disabled..
Also, I did some more testing and I don't think the machine is flexing. It's very rigid. I noticed that when I very quickly tap the jog key the motor rolls forward and then right back into the samp position. It looks like it's the motor itself doing the bouncing motion. Is this just because I'm tapping the key so fast something isn't registering?
-
The status message, "Axis 3 commanded while disabled" is because in the "Go To Work Zero" button, A axis is commanded to go to 0.00 as well as X, Y, and Z.
There are a couple of ways you can fix this.
1. Go into the screen editor and edit the goto work zero function in the screen load script to not include the A axis move.
2. Simply enable motor 3 in mach config. If you don't have using motor 3 this won't have any adverse effects, it will just be enabled.
I am using the ESS on a mill with Mach4 and I do get a little bit of funny noise while jogging, it messes with my spindle slightly and extremely briefly. I haven't messed with the ESS Config in a while, but is there a way to reduce noise on it? Maybe it is getting a false keyboard press?