Yes, that's exactly what I'm looking for. Minor dips and humps in the
table that I'd like to have some software correction for. I only have
the two axes, X and Z on the machine. It's a saw beveler that cuts a
tapered triangular bamboo strip.
Wait a day or so. I am in the middle of writing
Hi John,
The problem is that bed wear or spindle misalignment causes
cross-coupling between the X and Z axes, which is why it needs to be
done in kinematics.
Les
On 02/07/17 01:47, John Kasunich wrote:
How many points do you need? If 16 or less, check out the lincurve
component
Try ebay seller cwjkman , he sells surplus screws reasonably
On Jul 2, 2017 12:12 AM, "Gene Heskett" wrote:
> On Saturday 01 July 2017 21:34:27 Gene Heskett wrote:
>
> > Greetings guys;
> >
> > That <$200 2505 by 1475 screw I used for z drive is haunting me,
> > again.
> >
By ugly I was talking about setting up shared memory communications
simply to pass config values once at startup. It is also untidy from
the user's viewpoint. They need to load two modules even though one is
going to simply read from a file, squirt those values to the HAL
module then exit.
On 30 June 2017 at 22:01, Condit Alan via Emc-users
wrote:
> Where is the firmware (bit file) that is to be loaded found? I have a 7i43p
> 200K board.
The bitfile will be in /lib/firmware/hm2
But it sounds to me more like an EPP problem. I am confused by your
On 07/02/2017 09:11 AM, Les Newell wrote:
Yes, that's exactly what I'm looking for. Minor dips and humps in the
table that I'd like to have some software correction for. I only
have the two axes, X and Z on the machine. It's a saw beveler that
cuts a tapered triangular bamboo strip.
Wait
On Sunday 02 July 2017 09:15:05 jeremy youngs wrote:
> Try ebay seller cwjkman , he sells surplus screws reasonably
>
I found him, but how do I do a search within what he has?
I was not able to find loose balls that are oversize. I /think/ they
are .125 and 3.25mm are hens teeth.
Also. I found
On 07/01/2017 08:39 PM, John Kasunich wrote:
Screw error comp isn't really applicable, but you can do something similar in
HAL.
You want (if I understand correctly) a compensation value that applies a minor
tweak
to Z as X moves, right?
Yes, that's exactly what I'm looking for. Minor dips
On 30 June 2017 at 23:20, wrote:
> I have built a bootable USB stick using two different methods, one from my
> Mac using terminal commands and one from another Debian machine using the
> instructions on the Linuxcnc web site.
I went round this loop several time last time I
On 2 July 2017 at 16:50, Gene Heskett wrote:
> I was not able to find loose balls that are oversize. I /think/ they
> are .125 and 3.25mm are hens teeth.
Are ny of these an improvement?
Brain farts and other errors! I was trying to send the firmware via a parallel
cable that wasn’t plugged into the cpu box. Fixed that! Then I realized that I
originally bought 2 of the D525MW boards. I upgraded the bios on one of them,
then my house was burglarized and guess which one got
On Sunday 02 July 2017 15:58:53 andy pugh wrote:
> On 2 July 2017 at 16:50, Gene Heskett wrote:
> > I was not able to find loose balls that are oversize. I /think/ they
> > are .125 and 3.25mm are hens teeth.
>
> Are ny of these an improvement?
>
On 2 July 2017 at 09:07, Les Newell wrote:
> The problem is that bed wear or spindle misalignment causes cross-coupling
> between the X and Z axes, which is why it needs to be done in kinematics.
Putting the Z axis position into the input of "lincurve" could give
you
Are you sure it is cancelling cutter comp or is it changing cutter comp to
the other side of the programmed path?
On Jul 2, 2017 4:50 PM, wrote:
Yes, I do see different results, the line becomes horizontal rather than
angled. But my question is, why when cutter compensation IS
The motion I see in the link looks like I would expect it to look. Are you
expecting cutter comp on just the X axis or just the Z axis or both X and Z?
On Jul 2, 2017 5:12 PM, wrote:
> I admit that compensation confuses me on a lathe. I have no idea if it is
> cancelling or
I don’t disagree but am failing to see the connection to my question…?
-Tom
> On Jul 2, 2017, at 4:16 PM, Stuart Stevenson wrote:
>
> It has always been my experience G40 cancels cutter compensation.
>
> On Jul 2, 2017 2:44 PM, wrote:
>
> Why would G0 to a
I admit that compensation confuses me on a lathe. I have no idea if it is
cancelling or changing - but why would it change? There is a single G42 at the
beginning of the routine. The routine is simply cutting a taper (as can be
seen by the steeper lines in the back plot) starting at
I would expect compensation to be on or off period (that is, not PER axis).
I am curious why you expect it to look that way. Why would you expect the
first move to position itself one cutter diameter lower than where the cut
should be?
We are using a NGCGUI routine that was written by
Why would G0 to a given location in one axis (X) differ such that a G1 movement
in another axis (Z) causes the first axis to move? Let me explain...
Attached is a screenshot of the back plot from Axis:
http://bgp.nu/~tom/pub/G0G1.png
The highlighted line is "G0 X#"
However, if you look at
It has always been my experience G40 cancels cutter compensation.
On Jul 2, 2017 2:44 PM, wrote:
Why would G0 to a given location in one axis (X) differ such that a G1
movement in another axis (Z) causes the first axis to move? Let me
explain...
Attached is a screenshot of the
Yes, I do see different results, the line becomes horizontal rather than
angled. But my question is, why when cutter compensation IS on, are the moves
treated differently. By the way, even if we change the first G0 to a G1, we
still get the angled line. So, it isn’t G0 vs G1, it is simply
You SHOULD see different results.
On Jul 2, 2017 3:46 PM, wrote:
> I don’t disagree but am failing to see the connection to my question…?
> -Tom
>
> > On Jul 2, 2017, at 4:16 PM, Stuart Stevenson wrote:
> >
> > It has always been my experience G40 cancels
22 matches
Mail list logo