Hi Andy,
On the real machine it does.
The spindle comes up to the change position and waits for tool change as
expected.
After confirming with the "tool changed" button, it moves directly to the
probe and is probing.
I'll try to increase the debugging level in my .ini and will put the M0 in th
> Date: Tue, 14 May 2013 23:08:34 -0500
> From: j...@zultron.com
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] LinuxCNC week at MPM/SFI
>
> Michael and I have a room reserved at the Motel 6. It's <2 miles from
> the shop and about $50/night for a room with two singl
Michael and I have a room reserved at the Motel 6. It's <2 miles from
the shop and about $50/night for a room with two singles.
I failed to check if they have wifi, which the website says they do but
for which there may be a fee.
John
On 05/10/2013 09:07 AM, John Kasunich wrote:
> I wi
On 05/14/2013 08:51 AM, Sebastian Kuzminsky wrote:
>
>
> Curtis Dutton wrote:
>
>> Ok I have integrated the wj200_vfd driver into linuxcnc
>> src/hal/user_comps/wj200_vfd
>>
>> The repository is available at https://github.com/OKComputers/linuxcnc
>
> Great, i'll review it later today.
Looks like
> There are other ways to do that, though not Fanuc-ways. One option
> would be to have two different tools in the same "Pocket" with the
> same Geometry and different wear. This isn't actually possible in
> LinuxCNC at the moment, as it enforces one tool per pocket, and
> doesn't understand wear
Am 15.05.2013 um 00:46 schrieb andy pugh :
> On 14 May 2013 05:56, ENGELMANN Luc wrote:
>
>> Yes you are probably right, those were my thoughts too, as I can't find any
>> error, nor in my test code (tcdemo.ngc) neither in the manual_change.ngc.
>> I guess that the problem could come from the
On 14 May 2013 05:56, ENGELMANN Luc wrote:
> Yes you are probably right, those were my thoughts too, as I can't find any
> error, nor in my test code (tcdemo.ngc) neither in the manual_change.ngc.
> I guess that the problem could come from the GCode Interpret, because after
> probing the correc
On 14 May 2013 22:41, Michael Haberler wrote:
> the platform and reserve flags on the gpiomap module are just there to block
> a standard sets of pins from use per-platform, and have an escape mechanism
> with reserve= if that doesnt completely fit the bill
Sorry, I see that now. Reading it wi
On 14 May 2013 22:21, Michael Haberler wrote:
> halcmd loadrt gpiomap platform= [reserve= pins beyond platform reserved pins>]
Would it be neater to have the drivers reserve their pins internally
(in much the same way as hal_malloc is called by each driver)?
The first module to be loaded "wins
we have now several HAL drivers which access GPIO pins (for now in ARM builds,
but I am sure the problem is more general)
due to the way hardware resources are accessed in RT threads, one cannot rely
on kernel coordination between different HAL drivers accessing pins; in fact
drivers might have
On 14 May 2013 15:38, Daniel Rogge wrote:
> Say I've got a drawing of as shaft with two diameters. Diameter 1 is 20mm
> +0.0/-.03mm. Diameter 2 is 30mm +.03mm/-0.0mm. If I want to hold the
> tolerances using only one tool, I need the ability to apply two different
> offsets to the same tool
Curtis Dutton wrote:
>Ok I have integrated the wj200_vfd driver into linuxcnc
>src/hal/user_comps/wj200_vfd
>
>The repository is available at https://github.com/OKComputers/linuxcnc
Great, i'll review it later today.
>During my work, I discovered a bug in the comp.py program. The problem
>is
Andy,
T44 applies the geometry offsets for tool 44 only.
T applies geometry and wear offsets for tool 44.
T4402 applies geometry offsets for tool 44 and wear offsets for tool 2.
Say I've got a drawing of as shaft with two diameters. Diameter 1 is 20mm
+0.0/-.03mm. Diameter 2 is 30mm +.03mm
Ok I have integrated the wj200_vfd driver into linuxcnc
src/hal/user_comps/wj200_vfd
The repository is available at https://github.com/OKComputers/linuxcnc
I have not yet completed the driver, I need to add command line option
parsing to set the modbus communication parameters. However I have run
On 14 May 2013 15:04, Daniel Rogge wrote:
> The only thing that I would advise is - don't couple the wear offset to the
> geometry offset. The entire scheme hinges on the ability to apply the wear
> offset from tool X to a different tool Y.
This is the part that I don't really understand.
We
Andy,
I think there are two questions here:
1. Should the operator interact with the control in a way that mirrors the
Fanuc implementation? This includes both Txxyy tool call and G10 P100xx offset
setting, even if we suspect that it wouldn't break compatibility. It also
includes a way of e
Michael,
It works now.
Thank you so much.
Christophe
On 13/05/2013 19:35, Michael Haberler wrote:
> I think it is fixed now, please pull and rebuild
>
> - Michael
>
> Am 13.05.2013 um 18:14 schrieb Christophe Grellier :
>
>> Hello,
>>
>> I got my new 5i25 / 7i76 cards connected today to G203V dr
17 matches
Mail list logo
