On Monday 17 March 2014 03:11:25 EBo did opine:
On Mar 16 2014 10:23 AM, Gene Heskett wrote:
...
(debug,messsage text = ,#100)
However, in your gcode routine, as you probe the corners, store the
#5063
into a named variable, then
(one of msg|debug|print whichever corner = ,
On Monday 17 March 2014 03:31:58 Robert Ellenberg did opine:
It looks to be from the different maximum velocities of lines and arc
segments. The circular arc segments are limited to the minimum of the
two axes in the current plane. The short line segments in between arcs
are limited by the
please review:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/hal-revised-link-semantics
- Michael
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive
On Mar 17 2014 1:28 AM, Gene Heskett wrote:
On Monday 17 March 2014 03:11:25 EBo did opine:
On Mar 16 2014 10:23 AM, Gene Heskett wrote:
...
(debug,messsage text = ,#100)
However, in your gcode routine, as you probe the corners, store
the
#5063
into a named variable, then
(one
On Mon, Mar 17, 2014, at 03:48 AM, Gene Heskett wrote:
This seems like a potential problem for those of us with toy powered
spindles. I often set a straight line cut, not to the tool limit, but to
the spindle power limit, and that diagonal over speed move could lead to a
spindle stall.
On Mon, Mar 17, 2014, at 04:38 AM, Michael Haberler wrote:
please review:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/hal-revised-link-semantics
- Michael
Looks good to me.
The part I'm not able to verify is the pointer stuff. That SHMPTR mess
is
Hello again, it's been a long time since my last email, and I've tried to
make hal driver for my boards' gpios, but it seems I'm stuck.
First, I've used pcl720.comp as an example, and after a couple of
iterations I've got this code:
http://pastebin.com/4LT3WLRE
It compiles, and loadrt loads it,
On 3/17/14 09:08 , Paul S. wrote:
Hello again, it's been a long time since my last email, and I've tried to
make hal driver for my boards' gpios, but it seems I'm stuck.
First, I've used pcl720.comp as an example, and after a couple of
iterations I've got this code:
Hi Paul,
On 17/03/2014 15:08, Paul S. wrote:
Hello again, it's been a long time since my last email, and I've tried to
make hal driver for my boards' gpios, but it seems I'm stuck.
First, I've used pcl720.comp as an example, and after a couple of
iterations I've got this code:
This commit was applied to both 2.5 and master, was that intentional?
The usual way to do things like this would be to commit the patch to the
oldest applicable branch (2.5 in this case), then merge that branch into
master.
Just FYI for next time ;-)
On 3/16/14 16:58 , Dewey Garrett wrote:
I have a hefty servo machine with dual Y axis, I'd really like to use the
Mesa 7i80 for it. (+ 7i53, 7i83, 7i70, 7i71)
Testing has gone fairly well so far - running Ubuntu 12.04-32, 7i80-ubc3 and
3.10.4-rt1mah as described in Andy's post here:
On Monday 17 March 2014 12:22:45 EBo did opine:
On Mar 17 2014 1:28 AM, Gene Heskett wrote:
On Monday 17 March 2014 03:11:25 EBo did opine:
On Mar 16 2014 10:23 AM, Gene Heskett wrote:
...
(debug,messsage text = ,#100)
However, in your gcode routine, as you probe the
On Monday 17 March 2014 12:30:14 John Kasunich did opine:
On Mon, Mar 17, 2014, at 03:48 AM, Gene Heskett wrote:
This seems like a potential problem for those of us with toy powered
spindles. I often set a straight line cut, not to the tool limit, but
to the spindle power limit, and that
On 17 March 2014 16:28, Matt Westveld westv...@gmail.com wrote:
Is there a way to get joint-axis-4 stuff into the 7i80 branch?
In theory you would just need to merge JA4 into ubc3-7i80. In
practice I don't know how cleanly that goes, and I am in a hotel with
no access to git to try it
I think one can argue both ways John. Basically I just wanted to throw it
out there and see if it sticks. :)
You are of coarse correct because I can still set the F to what my machine
can do, and running smoother is always going to be faster. Those little
near stops of millisecond
On Monday 17 March 2014 14:34:34 Robert Ellenberg did opine:
I think one can argue both ways John. Basically I just wanted to
throw it
out there and see if it sticks. :)
You are of coarse correct because I can still set the F to what my
machine can do, and running smoother is
Hi,
Seb's email happened to draw my attention to this patch.
IMHO, the loadtool code already had a bug in it, and this patch will
make the bug happen 100% of the time that loadtool is used.
I understand that T#==H# is a common gcode convention. The key word here
is convention...
I am concerned
On Monday 17 March 2014 17:23:05 David Bagby did opine:
Hi,
Seb's email happened to draw my attention to this patch.
IMHO, the loadtool code already had a bug in it, and this patch will
make the bug happen 100% of the time that loadtool is used.
I understand that T#==H# is a common gcode
On 3/17/2014 1:00 PM, andy pugh wrote:
On 17 March 2014 19:09, David Bagbyd...@calypsoventures.com wrote:
The gocde state of a program should be controlled by the program
(according to the control language the program is written in: in this
case, gcode).
Yes, but, isn't it the case that
On 3/17/2014 2:46 PM, Gene Heskett wrote:
On Monday 17 March 2014 17:23:05 David Bagby did opine:
[snip]
This is not anything that I have ever played with. Why? Because I do the
majority of my TLO's via a probing touch, and set the corresponding G55-56-
etc co-ordinate system.
Not to
Sigh - bad typo in my sentence:
On 3/17/2014 4:15 PM, David Bagby wrote:
That's not the same as setting a TLO value and using G43 to get TLO
compensation done in the control logic as MC moves are converted to MC
moves.
make that ... as WC moves are converted to MC coves.
Dave
On Monday 17 March 2014 20:24:55 David Bagby did opine:
On 3/17/2014 2:46 PM, Gene Heskett wrote:
On Monday 17 March 2014 17:23:05 David Bagby did opine:
[snip]
This is not anything that I have ever played with. Why? Because I do
the majority of my TLO's via a probing touch, and
Ah, I see that Dewey just pushed a patch that adds some control options
for G43 usage to ngcgui.
(ref loadtool.ngc: provide options for g43 control on the commit list).
The loadtool now looks like:
oloadtool call [#toolno][#use_g43][#h_for_g43][#verbose]
I see that as much better. I also see
23 matches
Mail list logo
