On 12 October 2015 at 06:44, EBo wrote:
> I agree with option #3. The question is what g-code whould be
> defined/chosen? How about G78.9 (a generalization of G17, G18, and
> G19)?
I note that G16 is spare and that whereas some G-code systems use G15
/ G16 to switch between
>
> --
>
> Message: 5
> Date: Mon, 12 Oct 2015 08:54:45 -0500
> From: Chris Lesiak
> Subject: Re: [Emc-developers] normal.z=0.039370
> To:
> Message-ID: <561bbba5.6020...@licor.com>
> Content-Type:
On 10/12/2015 08:08 AM, andy pugh wrote:
> I think we need to consider whether we want arbitrary arcs or
> arbitrary working planes. They are not really the same thing. Out of
> interest, with the Heidenhain code, what happens to the apparent XYZ
> when you change plane? Are XYZ still in
On 10/12/2015 08:08 AM, andy pugh wrote:
> On 12 October 2015 at 13:59, TJoseph Powderly wrote:
>> Hint: you only need 2 angles, 3 is really overconstrained.
>> It ___really___ makes programming easy.
>> All programming is just like you had a trunnion table.
>
> You can do this
On 10/12/2015 08:50 AM, Stuart Stevenson wrote:
> Gentlemen,
> On my Fanuc 15mb control I would use G68 and G69 to rotate the coordinate
> system.
> I was allowed to rotate any axis by an amount
>
> ex.
> G68 X0 Y0 Z1 R20 was a rotation of the XY plane by 20 degrees. I am not
> sure R was the
On 10/12/2015 08:54 AM, Chris Lesiak wrote:
> On 10/12/2015 08:08 AM, andy pugh wrote:
>> I think we need to consider whether we want arbitrary arcs or
>> arbitrary working planes. They are not really the same thing. Out of
>> interest, with the Heidenhain code, what happens to the apparent XYZ
>>
On 12 October 2015 at 13:59, TJoseph Powderly wrote:
> Hint: you only need 2 angles, 3 is really overconstrained.
> It ___really___ makes programming easy.
> All programming is just like you had a trunnion table.
You can do this already in LinuxCNC with kinematics, I think (not
Gentlemen,
On my Fanuc 15mb control I would use G68 and G69 to rotate the coordinate
system.
I was allowed to rotate any axis by an amount
ex.
G68 X0 Y0 Z1 R20 was a rotation of the XY plane by 20 degrees. I am not
sure R was the correct symbol but the example still stands. I was only
allowed to
On Oct 12 2015 10:01 AM, Stuart Stevenson wrote:
>
> I think we should be able to probe coordinate rotations
>
> Two points for a plane rotation and three for a complete coordinate
> system
> orientation
If you only probe 2, there are special collinear cases which could
still be two of the
On Oct 12 2015 9:42 AM, TJoseph Powderly wrote:
>
> BTW when a simple ROTATE (not the 3D titl plane )
> is used on Heidenhain, theres a
> machine parm that allows the DRO to show the new X' and Y'
> so radial moves make more sense.
I can see that being useful, but if that functionality was added
On 10/12/2015 12:20 PM, EBo wrote:
> On Oct 12 2015 9:42 AM, TJoseph Powderly wrote:
>>
>> BTW when a simple ROTATE (not the 3D titl plane )
>> is used on Heidenhain, theres a
>> machine parm that allows the DRO to show the new X' and Y'
>> so radial moves make more sense.
>
> I can see that being
On 10/12/2015 12:11 PM, EBo wrote:
> On Oct 12 2015 10:01 AM, Stuart Stevenson wrote:
>>
>> I think we should be able to probe coordinate rotations
>>
>> Two points for a plane rotation and three for a complete coordinate
>> system
>> orientation
>
> If you only probe 2, there are special
Hello!
I'm building an ethernet based IO board to be used with LinuxCNC. I
wrote a short webpage about my project on www.pekka.eu/cnc
Everything is working quite well, except for the write and read
operations being too slow. I have two functions exported to HAL, read
and write. The .time pin
On Oct 12 2015 12:38 PM, TJoseph Powderly wrote:
> On 10/12/2015 12:11 PM, EBo wrote:
>> On Oct 12 2015 10:01 AM, Stuart Stevenson wrote:
>>>
>>> I think we should be able to probe coordinate rotations
>>>
>>> Two points for a plane rotation and three for a complete coordinate
>>> system
>>>
On 10/12/2015 11:27 PM, emc-developers-requ...@lists.sourceforge.net wrote:
> Date: Mon, 12 Oct 2015 13:27:36 -0700 (PDT)
> From: "Peter C. Wallace"
> Subject: Re: [Emc-developers] Timing of realtime functions in uspace
> To: EMC developers
>
Thanks, i will do some research on the TP codes.
2015年10月12日星期一,Robert Ellenberg 写道:
> Hi Julian,
>
> As you've discovered, the trajectory planner itself can already create
arcs
> in an arbitrary plane. However, the interpreter and canon only support the
> subset that Jeff
> > Date: Mon, 12 Oct 2015 22:55:03 +0300
> > From: Pekka Roivainen
> > Reply-To: EMC developers
> > To: emc-developers@lists.sourceforge.net
> > Subject: [Emc-developers] Timing of realtime functions in uspace
> >
> > Hello!
> >
> > I'm
17 matches
Mail list logo