Am 29.01.2012 um 06:37 schrieb Erik Christiansen:
- wouldnt it be more readable to write:
--
$var1 = $foo + 1
$var2 = 10
if $var1 $var 2
...
else
...
endif
--
Indeedy, but even the '$' is unnecessary.
I'm not sure whether
On Sat, 28 Jan 2012 22:40:29 +, you wrote:
Haven't seen the belated 2.5 yet...
It has, indeed, been imminent for a long time. I suspect that a lot
of the delay has been due to the EMC lawyers.
Last time I asked here the reason given for the delay was bugs - not so
long ago either.
I have
Viesturs,
regardless of possible tuning questions, if I recall right, you are
using a 24 volts supply for the stepper amplifiers. This seems a little
low to me as I was using 90 volts on my dual Parker Hannifing
amplifier/driver. I had stepper motors attached to the two slides of my
lathe and
Peter, just as the name of threads says, I am trying to tune servo
motors, not steppers :)
I just checked - the supply voltage is 27,9 VDC, because 7i39 drives
have 28 VDC limit.
Ohh, and there is update:
The motor that yesterday worked fine at 4000 mm/min, today is not
working fine at that speed
On 29.01.12 09:31, Michael Haberler wrote:
Am 29.01.2012 um 06:37 schrieb Erik Christiansen:
--
$var1 = $foo + 1
$var2 = 10
if $var1 $var 2
...
else
...
endif
--
Indeedy, but even the '$' is unnecessary.
I'm not sure
On 29 January 2012 12:29, Erik Christiansen dva...@internode.on.net wrote:
While that could be 'de-hashed' without an alternative numbered
parameter identifier, I don't see how you'd propose to handle:
#43 = foo / #44
I am puzzled how you would handle
foo = 10
oo = 1
g1fooZ100
Is it not
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 = Acceleration Feed Forward Gain or Friction Feed Forward Gain.
I would like to update the docs with some descriptive text in addition
to 0th order feed forward gain
On 1/29/2012 12:37 AM, Erik Christiansen wrote:
On 25.01.12 21:22, Michael Haberler wrote:
[this should move to emc-developers, which is why I'm cc'ing there]
It would be a pity if the rest of us were to be excluded. It is a very
interesting discussion, and the EMC issue was secretive enough.
On 29.01.12 12:59, andy pugh wrote:
On 29 January 2012 12:29, Erik Christiansen dva...@internode.on.net wrote:
While that could be 'de-hashed' without an alternative numbered
parameter identifier, I don't see how you'd propose to handle:
#43 = foo / #44
I am puzzled how you would
On 29 January 2012 13:23, John Thornton bjt...@gmail.com wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 = Acceleration Feed Forward Gain or Friction Feed Forward Gain.
I would like to update the docs
On 29 January 2012 14:02, Erik Christiansen dva...@internode.on.net wrote:
oo = 1
OK, O Codes. They'll all go in a declutter, replaced by their naked
keywords,
No, that is creating a second named parameter in order to be more
ambiguous later:
g1fooZ100
Is there an axis identifier
On 29.01.12 08:57, Kent A. Reed wrote:
Erik:
There's nothing secretive about emc-developers. Anyone can subscribe
to the list and anyone can peruse its archive of messages. (see the Wiki)
My point was not self-referential, it related to keeping the discussion
in front of all users. I feel
On dom, 2012-01-29 at 14:04 +0200, Viesturs Lācis wrote:
Peter, just as the name of threads says, I am trying to tune servo
motors, not steppers :)
I just checked - the supply voltage is 27,9 VDC, because 7i39 drives
have 28 VDC limit.
Ohh, and there is update:
The motor that yesterday
2012/1/29 Spiderdab 77...@tiscali.it:
Hallo Viesturs, i don't remember who suggested, but i've read, with
those encoders, it's better to glue them to the rotating axle, because
they can slip at high speeds and during fast accelerations.
Thanks! I already did that this morning. Did not help...
On 1/29/2012 9:52 AM, Erik Christiansen wrote:
And if we make the effort to update the subject line, as I have done,
then the post is still presented in the thread by my mailreader, but
the subject immediately identifies it as a digression. There being no
cloaking, recipients are then
On 29 January 2012 15:10, Viesturs Lācis viesturs.la...@gmail.com wrote:
I am now reading a thread, started by Jon Elson in June 2011 on
developers' list about these encoders. It turns out that they have
acceleration lag, so overall conclusion - do not use them in CNC
machine!
I have yet to
Sorry, Viesturs, that was a language glitch of mine. Servo is used in
German as a general classification for anything moving with power
assistance, above all in the motor vehicle sector, e. g. Servolenkung
(power steering) or Servobremse (power brake) as well as in Ruderservo
(RC model
2012/1/29 andy pugh bodge...@gmail.com:
On 29 January 2012 15:10, Viesturs Lācis viesturs.la...@gmail.com wrote:
I am now reading a thread, started by Jon Elson in June 2011 on
developers' list about these encoders. It turns out that they have
acceleration lag, so overall conclusion - do not
On Sun, 29 Jan 2012, Viesturs L?cis wrote:
Date: Sun, 29 Jan 2012 14:04:43 +0200
From: [UTF-8] Viesturs L?cis viesturs.la...@gmail.com
Reply-To: Enhanced Machine Controller (EMC)
emc-users@lists.sourceforge.net
To: Enhanced Machine Controller (EMC) emc-users@lists.sourceforge.net
On 29.01.12 14:20, andy pugh wrote:
On 29 January 2012 14:02, Erik Christiansen dva...@internode.on.net wrote:
oo = 1
OK, O Codes. They'll all go in a declutter, replaced by their naked
keywords,
No, that is creating a second named parameter in order to be more
ambiguous later:
Viesturs,
if your laser seems too bulky - have you tried transporting the beam to
the work head via optic fibres? In the laser division of my former
company, we had several powerful (many, say, 50 watts output) gold vapor
ans other lasers that weighed about a ton each and filled a whole
On 29.01.12 10:23, Kent A. Reed wrote:
On 1/29/2012 9:52 AM, Erik Christiansen wrote:
And if we make the effort to update the subject line, as I have done,
then the post is still presented in the thread by my mailreader, but
the subject immediately identifies it as a digression. There being
On 1/29/2012 10:55 AM, Erik Christiansen wrote:
...
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
of the grammar tree for G1 then gets the handling of the common clauses
for free, and we only
2012/1/29 Peter Blodow p.blo...@dreki.de:
Viesturs,
if your laser seems too bulky - have you tried transporting the beam to
the work head via optic fibres?
The laser itself is less than 100g, so that is not the problem.
The machine itself has heavy construction as its primary task is wood
On 29 January 2012 15:47, Viesturs Lācis viesturs.la...@gmail.com wrote:
I took one of them off, I see 4 DIP switches, but do not see a jumper.
Their manual also does not show, where on that pcb jumper would be located.
http://www.amtencoder.com/Resources/Frequently-Asked-Questions#3
--
atp
On Sun, 2012-01-29 at 16:16 +, andy pugh wrote:
On 29 January 2012 15:47, Viesturs Lācis viesturs.la...@gmail.com wrote:
I took one of them off, I see 4 DIP switches, but do not see a jumper.
Their manual also does not show, where on that pcb jumper would be located.
On Sunday, January 29, 2012 12:00:01 PM andy pugh did opine:
On 29 January 2012 13:23, John Thornton bjt...@gmail.com wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 = Acceleration Feed Forward Gain
On 1/29/2012 12:03 PM, Kirk Wallace wrote:
On Sun, 2012-01-29 at 16:16 +, andy pugh wrote:
On 29 January 2012 15:47, Viesturs Lācisviesturs.la...@gmail.com wrote:
I took one of them off, I see 4 DIP switches, but do not see a jumper.
Their manual also does not show, where on
Hi Chris;
I think I may have it grokked as to why it wasn't working yesterday.
I wasn't giving the G38.2 a z value that would have gone more than a thou
past the expected contact detection based on my fear of damaging the gage I
had just made, and my thoughts on this overnight came to the
Am 29.01.2012 um 13:59 schrieb andy pugh:
On 29 January 2012 12:29, Erik Christiansen dva...@internode.on.net wrote:
While that could be 'de-hashed' without an alternative numbered
parameter identifier, I don't see how you'd propose to handle:
#43 = foo / #44
I am puzzled how you
On 1/29/2012 9:02 AM, Erik Christiansen wrote:
On 29.01.12 12:59, andy pugh wrote:
On 29 January 2012 12:29, Erik Christiansendva...@internode.on.net wrote:
While that could be 'de-hashed' without an alternative numbered
parameter identifier, I don't see how you'd propose to handle:
#43 =
Am 29.01.2012 um 15:20 schrieb andy pugh:
g1YfooZ100
And here is the question? What did I mean?
I was actually meaning feed at the rate defined by the parameter oo,
but how is the parser to know that is what I wanted rather than there
being a missing S (for example) in G1 Sfoo Z100
On 1/29/2012 9:20 AM, andy pugh wrote:
On 29 January 2012 14:02, Erik Christiansendva...@internode.on.net wrote:
oo = 1
OK, O Codes. They'll all go in a declutter, replaced by their naked
keywords,
No, that is creating a second named parameter in order to be more
ambiguous later:
On 1/29/2012 10:55 AM, Erik Christiansen wrote:
On 29.01.12 14:20, andy pugh wrote:
On 29 January 2012 14:02, Erik Christiansendva...@internode.on.net wrote:
oo = 1
OK, O Codes. They'll all go in a declutter, replaced by their naked
keywords,
No, that is creating a second named
Am 29.01.2012 um 16:55 schrieb Erik Christiansen:
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
By 'grouping common clauses' do you mean testing for required or permitted
'words' pertaining to
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with CAM,
including canned cycles and such. Less is more.
If one insists on improving g-code, I would
On 29 January 2012 18:43, Kirk Wallace kwall...@wallacecompany.com wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with CAM,
including
On Jan 29, 2012 12:44 PM, Kirk Wallace kwall...@wallacecompany.com
wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with CAM,
including
On Sun, Jan 29, 2012 at 6:43 PM, Kirk Wallace
kwall...@wallacecompany.com wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with CAM,
On 1/29/2012 8:10 AM, andy pugh wrote:
On 29 January 2012 13:23, John Thorntonbjt...@gmail.com wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 = Acceleration Feed Forward Gain or Friction Feed Forward
On 29 January 2012 17:31, gene heskett ghesk...@wdtv.com wrote:
What if the spring is either too much or too little, this seems to invite
the need for a non-symmetrical FF0 function.
You could account for the constant offset with the PID bias term.
--
atp
The idea that there is no such thing
On Sun, 2012-01-29 at 19:08 +, andy pugh wrote:
On 29 January 2012 18:43, Kirk Wallace kwall...@wallacecompany.com wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more.
John Thornton wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
You have these reversed.
Jon
--
Try before you buy = See our
gene heskett wrote:
On Sunday, January 29, 2012 12:00:01 PM andy pugh did opine:
On 29 January 2012 13:23, John Thornton bjt...@gmail.com wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 =
On Sunday, January 29, 2012 06:37:43 PM andy pugh did opine:
On 29 January 2012 17:31, gene heskett ghesk...@wdtv.com wrote:
What if the spring is either too much or too little, this seems to
invite the need for a non-symmetrical FF0 function.
You could account for the constant offset
Greets all;
I've written a testz.ngc that is about 6 or 7 lines of code, whose main
reason for existance is to test my autoz function when called as a file.
I get as far when I try to load it, because it cannot open the 'lathe-
encoder/autoz.ngc' file. Then I try to load it directly, and
So you agree with Andys description? I have a hard time keeping them
straight...
John
On 1/29/2012 3:46 PM, Jon Elson wrote:
John Thornton wrote:
So, looking at one of the links for servo tuning is our
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
You have these
On 29.01.12 13:12, Kenneth Lerman wrote:
On 1/29/2012 9:02 AM, Erik Christiansen wrote:
But I haven't seen a troublesome gcode example yet. :-)
Remember that just because a computer can understand a grammar does not
mean that a person can. (Consider the C++ grammar.)
Point taken. (And perl
On Sun, 29 Jan 2012 10:43:18 -0800, you wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with CAM,
including canned cycles and such. Less is
On 29.01.12 11:14, Kent A. Reed wrote:
On 1/29/2012 10:55 AM, Erik Christiansen wrote:
...
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
of the grammar tree for G1 then gets the handling
On Sun, 29 Jan 2012 19:08:23 -0600
John Thornton bjt...@gmail.com wrote:
So you agree with Andys description? I have a hard time keeping them
straight...
John
On 1/29/2012 3:46 PM, Jon Elson wrote:
John Thornton wrote:
So, looking at one of the links for servo tuning is our
FF0 =
On Sun, 29 Jan 2012 19:08:23 -0600
John Thornton bjt...@gmail.com wrote:
So you agree with Andys description? I have a hard time keeping them
straight...
John
On 1/29/2012 3:46 PM, Jon Elson wrote:
John Thornton wrote:
So, looking at one of the links for servo tuning is our
FF0 =
On 29.01.12 13:30, Kenneth Lerman wrote:
On 1/29/2012 10:55 AM, Erik Christiansen wrote:
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
of the grammar tree for G1 then gets the handling of the
On 01/29/2012 10:40 PM, Erik Christiansen wrote:
On 29.01.12 13:30, Kenneth Lerman wrote:
On 1/29/2012 10:55 AM, Erik Christiansen wrote:
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
of the
FF0 = Velocity Feed Forward Gain.
FF1 = Position Feed Forward Gain.
FF2 = Acceleration Feed Forward Gain or Friction Feed Forward Gain.
As Jon and others wrote, FF0,1,2 are related to consecutive time
derivatives of the controlled parameter: if the controlled parameter is the
position
On 29.01.12 19:31, Michael Haberler wrote:
Am 29.01.2012 um 16:55 schrieb Erik Christiansen:
What further simplifies the task is that we can, for example, group the
clauses which are common to G0, G1, etc., and give them a name. The part
By 'grouping common clauses' do you mean
On 29.01.12 23:05, Kenneth Lerman wrote:
Are you suggesting that a three axis machine where there is
no A axis should have a different grammar than a four axis machine that
does have an A axis.
No, there is no such constraint in the current parser, and there is no
reason to imagine that
On 30.01.12 02:33, Steve Blackmore wrote:
On Sun, 29 Jan 2012 10:43:18 -0800, [Kirk] wrote:
Regarding messing with the g-code interpreter, my vote is that g-code
should describe axis position, feedrate; and spindle speed and
direction, and little more. Everything else should be handled with
58 matches
Mail list logo
