On Friday 11 April 2014 00:59:31 Sebastian Kuzminsky did opine:

> On 04/10/2014 11:38 AM, Gene Heskett wrote:
> > I believe a similar gotcha exists in the MIN_LIMIT/MAX_LIMIT of the
> > .ini files. They are not, when given in inches, scaled to match
> > actual distances without a trip into gedit for a metric translation. 
> > I got used to the old way, and its going to bite me trying to run old
> > code in its inch mode.
> 
> I just tried this too, again with 2.5.3-131-ged3ed34 and
> 2.6.0-pre0-5418-gf74c5d3.
> 
> 
> As the docs say, [TRAJ]LINEAR_UNITS specifies the user units of the
> machine, inch or mm.
> 
> http://www.linuxcnc.org/docs/2.5/html/config/ini_config.html#sub:TRAJ-se
> ction
> 
> 
> Then, [AXIS_*]MIN_LIMIT and MAX_LIMIT specify the soft limits, in those
> machine units.
> 
> http://www.linuxcnc.org/docs/2.5/html/config/ini_config.html#sub:AXIS-se
> ction
> 
> 
> The soft limits work in both 2.5 and 2.6-pre, in both G20 and G21 mode,
> independent of the machine's native units from [TRAJ]LINEAR_UNITS.
> 
> All of this works just like it should, in both 2.5 and 2.6-pre, as far
> as i can tell.

The main reason I was concentrating on the limits, using the same code, was 
that I had written a peck cycle wrapped around a G33.1, which advanced half 
a turn per run in.  I had moved the code back away from the workpiece, 
basically cutting air, and had noted that on some occasions, the spindle 
became unlocked from Z with Z stopping while the spindle ran on for 3 or 4 
turns, stopping and reversing as normal but picking up the z again when it 
was at about at the same position while backing out.  This was using one of 
last summers 2.5.3's.  My back has precluded me from finishing the lathe 
re-assembly so I have not been able to check it against a current 2.5.3.

And running the sim, patched for bidi spindle, I have not, in 20+ runs, 
been able to duplicate that uncoupling.

I think, but can't say for sure since it all happened last summer, that I 
had done the backout so it was cutting air, with a touchoff. And I haven't 
checked (I have to think about this stuff & then go back & check) as to 
whether the soft limits move with the touchoff or not.  So I have obviously 
not been able to prove that it was the soft limit being hit, but it did not 
throw up any error messages, and the loop ran to its normal conclusion.

All I can say is that in the 2.6.0-pre visible 2 days ago, it does catch 
it, and kills the G33.1 instantly when it hits the softlimit.  This is not 
great since depending on the tap and how tightly chucked, that may damage 
the threads, or break the tap as the Z stops a lot faster than a 12 lb 
chuck and motor doing about 10x the chucks rpms.

In that event, the safest thing to do would be to set a whoops flag, 
continue that stroke with Z following even it the chuck takes 3 turns to 
reverse, then back out still synchronized & do the e-stop at the disconnect 
point of the backout move when everything is clear.  Unless the tap bottoms 
in the hole on the over travel, no damage to tool or workpiece.  If the tap 
bottoms out, thats my fault. I didn't drill the hole deep enough. :)

As for my back, once I get the taxes done, hopefully tomorrow, I have a 
bunch of stuff to check with my insurance, I'm supposed to do a spinal 
stenosis and some P.T., they don't want to operate just yet since I can 
still walk a short distance, maybe 40 yards when I feel good.

I hope I've made it clear, in any event it might serve as a heads up for 
anyone else using less than optimum tools and wraps a loop around the G33.1 
to make a peck cycle.

So unless someone else gets bit, or recalls seeing that happen, lets let it 
ride until such time as I in my reverie, manage to make it do it again.


Thanks Seb.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to