>
> I think the masking should continue to be honored. I think masking
> the overrides is VERY rarely used (I know I've never programmed it
> by hand), but where it is used it is critical.
>
> The G76 threading cycle uses this functionality for instance - when
> it gets to the end of the thre
I can say for sure that there would never be any more than one offset in use
at any given time. They may use different offsets on the same tool in the
same program, example, you have a shaft you are turning that has 4 different
diameters on it, you can use the same tool to run the whole shaft, and
On 6/10/14 11:03 , Rick Lair wrote:
> As longs as the way the tool/offset call is made and a table to store the
> fixed "tool" offsets and a possible second table to store the Assignable
> "wear" offsets, is the same as the way we do it with the Fanuc Style Patch,
> is really the important part to
The wear offset values are stored on the same tool table as the actual
tools, they just use the numbering of 10001, 10002, 10003, etc
Which sometimes can get confusing, if the operator is in a hurry, and fat
fingers the wrong row on the table?
Thanks
Rick Lair
Superior Roll & Tur
Don't get me wrong though we have made it this long with what we have and as
long as the patch still works, I can still make it work on my end.
If we wouldn't have at least found the patch though, LinuxCNC would have
been very short lived on the turning side of our shop.
Thanks
On 10 June 2014 18:03, Rick Lair wrote:
> I guess a question I have would be, how/where do you store the values of the
> "H" which would be the assignable offsets?
Where do you store them now? I can't recall how it works (and I am at work)
--
atp
If you can't fix it, you don't own it.
http://ww
My two cents,
As longs as the way the tool/offset call is made and a table to store the
fixed "tool" offsets and a possible second table to store the Assignable
"wear" offsets, is the same as the way we do it with the Fanuc Style Patch,
is really the important part to us.
It is here nor there ho
On 10 June 2014 17:15, Daniel Rogge wrote:
> It wasn't hard coded - it was something only enabled in an ini file, and was
> off by default.
That wasn't what I meant. I meant that it was just one fixed variant
toolhandler, rather than a generic way to allow other approaches.
> I know that you
On Jun 10 2014 10:15 AM, Daniel Rogge wrote:
>>I don't think that is quite fair.
>>There is some resistance to the iocontrol hack that hard-codes the
>> behaviour. (And there are reasons not to like the Fanuc way, too,
>> it is incompatible with the tooldatabase schema that we hacked
>> out last ye
On Mon, Jun 09, 2014 at 06:12:55AM +, Chris Morley wrote:
>
> I built your branch seemed to work for me. I didn't test much.
> My 2 cents worth:
Thanks for testing!
> If we add the direct-value switch then one could connect
> halui.feed-override.value to halui.rapid-override.counts...
> oh
>I don't think that is quite fair.
>There is some resistance to the iocontrol hack that hard-codes the
> behaviour. (And there are reasons not to like the Fanuc way, too,
> it is incompatible with the tooldatabase schema that we hacked
> out last year)
> Chris recently proposed a new variant o
On Tue, Jun 10, 2014 at 10:01:26AM +0200, Micha?? Geszkiewicz wrote:
> You have copy/paste error in halui support
> Also I think ini setting for max rapid override is not needed, there is
> no move at RO > 100.0 %.
You are right about both; I pushed the fixes. Thank you for the
review.
--
On 10 June 2014 15:19, Daniel Rogge wrote:
> Someone would have to add this functionality to that program, which is
> unlikely because most of the linuxcnc developers aren't in favor of the Fanuc
> patch in the first place
I don't think that is quite fair.
There is some resistance to the iocon
Rick,
The display of the wear offsets is entirely in the GUI code, not in the
linuxcnc code. I imagine you are using a program called tooledit (that's what
gets called in Axis when you edit the tool table file). Someone would have to
add this functionality to that program, which is unlikely b
I don't recall the actual problem using the MDI_COMMAND but one button
is G10 L11 P#5400 Z0.0 then the second is G43. Just testing in 2.5.4 and
G10 L11 P#5400 Z0.0 G43 seems to work in the MDI tab...
The touch off to material is G10 L20 P1 Z0.375 because I use a 3/8"
dowel to touch off with.
J
On 10/06/2014, EBo wrote:
> The first two I can see, but not the third. Why should you have an
> additional one just to update Axis (or are you reffering to the internal
> button handler, and not an actual button)?
>
> On Jun 10 2014 4:35 AM, John Thornton wrote:
>> Actually it takes me 3 pyvcp b
Hello Daniel,
Have you guys made any improvements on the Fanuc tool change patch?
I have that setup on three turning centers in our shop, and it is used all
day everyday for the last year and a half. I saw in your manual for your
lathe, that the wear offsets are put in the columns next to the ac
The first two I can see, but not the third. Why should you have an
additional one just to update Axis (or are you reffering to the internal
button handler, and not an actual button)?
On Jun 10 2014 4:35 AM, John Thornton wrote:
> Actually it takes me 3 pyvcp buttons to touch off, one for materi
Actually it takes me 3 pyvcp buttons to touch off, one for material and
one for tool and one to update Axis after a tool touch off.
JT
On 6/9/2014 7:29 PM, andy pugh wrote:
> I can't even guess how many times I have touched off a tool when I
> meant to touch off the coordinates, or more often, t
W dniu 07.06.2014 03:54, Chris Radek pisze:
> On Fri, Jun 06, 2014 at 06:52:03AM +, Chris Morley wrote:
>> This patch adds a pin to motion that allows rapids to be overridden
>> from 0 to 100 percent.
>> connecting this pin to halui.feed-override.value makes GUI's feed override
>> also control
20 matches
Mail list logo
