61
General Mach Discussion / Re: Strange backlash compensation
« on: June 24, 2007, 08:02:15 AM »
Graham,
In the case of continuous jog mode you are correct that Mach3 does not know but the first
move will be at least more than the backlash comp so in my case it would automatically add 0.1mm
to that first move in the new direction without including that extra distance in the DRO calculations.
Another way would be to mathematically subtract the backlash distance from the DRO and then
just jog as normal. The first 30 steps or so in my case would not move the table but they would
be counted by the DRO so 30 steps later, the DRO would be back to the starting value and the
backlash would be taken up.
Please remember that I am new to Mach3 and the Micromill so I am probably doing something
wrong in the configuration or otherwise but the backlash is clearly not working correctly on my
system and on tmsmith’s . Also the backlash distance is very small so it ought to be completely
transparent; tmsmith was using 5/1000 and I am using 8/1000 (0.1mm).
The part that I do not understand is why there is a separate backlash speed. If a G code directs
a movement in the opposite direction so backlash is required, I believe that the backlash move
should (or could) just be part of a normal move that is mathematically handled in the background
and then the normal acceleration and speed setting would handle that combined move.
By the way, I am extremely happy to have found Mach3 and the related products and the support
through from Art and Brian and the user community is fantastic. I specially like the feature that I
can customize Mach3 to fit my needs and taste. I have spent yesterday playing with LazyCAM
Pro but I save that for another post.
Have a nice Sunday!
Bertho
In the case of continuous jog mode you are correct that Mach3 does not know but the first
move will be at least more than the backlash comp so in my case it would automatically add 0.1mm
to that first move in the new direction without including that extra distance in the DRO calculations.
Another way would be to mathematically subtract the backlash distance from the DRO and then
just jog as normal. The first 30 steps or so in my case would not move the table but they would
be counted by the DRO so 30 steps later, the DRO would be back to the starting value and the
backlash would be taken up.
Please remember that I am new to Mach3 and the Micromill so I am probably doing something
wrong in the configuration or otherwise but the backlash is clearly not working correctly on my
system and on tmsmith’s . Also the backlash distance is very small so it ought to be completely
transparent; tmsmith was using 5/1000 and I am using 8/1000 (0.1mm).
The part that I do not understand is why there is a separate backlash speed. If a G code directs
a movement in the opposite direction so backlash is required, I believe that the backlash move
should (or could) just be part of a normal move that is mathematically handled in the background
and then the normal acceleration and speed setting would handle that combined move.
By the way, I am extremely happy to have found Mach3 and the related products and the support
through from Art and Brian and the user community is fantastic. I specially like the feature that I
can customize Mach3 to fit my needs and taste. I have spent yesterday playing with LazyCAM
Pro but I save that for another post.
Have a nice Sunday!
Bertho