On 20.06.17 10:25, Jon Elson wrote:
> On 06/20/2017 02:50 AM, Erik Christiansen wrote:
> > Incidentally, I've found that the Postscript printer language is sorta
> > almost like gcode on steroids. Fighting with a GUI drawing package gives
> > me chest pains, without producing useful output, so I've
Well, it has been homed and is searching for index when it faults with the
following errorbut it isn't homed as I have just killed and restarted
Linuxcnc. I then move the Z axis down a little bit and then Home All...
-Tom
> On Jun 20, 2017, at 7:54 PM, Peter C. Wallace wrote:
>
> This loo
On Tue, 20 Jun 2017, tom-...@bgp.nu wrote:
Date: Tue, 20 Jun 2017 19:52:13 -0400
From: tom-...@bgp.nu
Reply-To: "Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller (EMC)"
Subject: Re: [Emc-users] following error only while homing
Here is more zoom fwiw??. http://bgp.nu/~t
Here is more zoom fwiw…. http://bgp.nu/~tom/pub/enc-6.png
-Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Is this what you want…?
http://bgp.nu/~tom/pub/enc-5.png
And the log file is...
http://bgp.nu/~tom/pub/enc-5.log
-Tom
> On Jun 20, 2017, at 5:34 PM, Sebastian Kuzminsky wrote:
>
> On 06/20/2017 01:31 PM, tom-...@bgp.nu wrote:
>> The Halscope trace of: hm2_7i43.0.stepgen.02.position-cmd,
>> hm
On 20 June 2017 at 22:34, Sebastian Kuzminsky wrote:
> Also increase the gain so we can see the fine detail on all the
> position-releated pins (both cmd and fb).
I was going to suggest saving the data as a .log file from Halscope, so
that people can zoom and inspect for themselves, but I can't
On 06/20/2017 01:31 PM, tom-...@bgp.nu wrote:
The Halscope trace of: hm2_7i43.0.stepgen.02.position-cmd,
hm2_7i43.0.encoder.02.position, hm2_7i43.0.encoder.02.index-enable,
axis.2.home-sw-in with trigger of axis.2.f-errored can be seen here:
http://bgp.nu/~tom/pub/enc2.png
Wel that looks
Yes, when I re-enable the machine (with or without estop first) I get another
(immediate) following error. That is, I understand to make the notification
itself go away I click the X, but what I am seeing is a perpetual following
error when re-enabling with each new notification piling up on th
On Tue, 20 Jun 2017, Andrew wrote:
Date: Tue, 20 Jun 2017 22:33:43 +0300
From: Andrew
Reply-To: "Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller (EMC)"
Subject: Re: [Emc-users] Mesa 7i47S issue
2017-06-17 20:15 GMT+03:00 Andrew:
2017-06-17 18:34 GMT+03:00 Danny Mill
What is strange is that pressing Machine (F2) does not clear the alarm. (That
won't close the alarm notification window, you have to click the X on that
window to make it go away.)
- Original Message -
From: tom-...@bgp.nu
To: "Enhanced Machine Controller (EMC)"
Sent: Tuesday, June 20,
2017-06-17 20:15 GMT+03:00 Andrew:
> 2017-06-17 18:34 GMT+03:00 Danny Miller:
>
>> Similarly the inputs aren't true differential, they're an optoisolator's
>> input diode with a series resistor to produce the rated trigger current
>> when +5v is applied + to -. Due to some esoteric details in how
You guys are prolific, and I appreciate it! Thanks for all the input.
A few things in case it hasn’t been clear...
1) I don’t (currently) have a PID involved at all (position-mode steppers with
encoders only).
2) If I set FERROR=2 and MIN_FERROR=1, homing DOES complete successfully.
2) Pressi
On 20 June 2017 at 18:47, Sebastian Kuzminsky wrote:
> It looks like it'd be easy to add a ".raw-position" pin to the hostmot2
> encoder.
Does homing use the accumulated counts in the counter after index as part
of the homing offset? It feels like it should.
If it does, then this might not work
On 20 June 2017 at 18:47, Sebastian Kuzminsky wrote:
> It looks like it'd be easy to add a ".raw-position" pin to the hostmot2
> encoder. We already track .rawcount and compute .count from it, and
> compute .position from .count.
If that is the answer then rawcounts * scale => feedback might b
On 06/20/2017 11:47 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 11:39 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 11:34 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 10:51 AM, andy pugh wrote:
On 20 June 2017 at 17:37, Peter C. Wallace wrote:
I suspect this cannot work the way you have thi
On 06/20/2017 11:39 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 11:34 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 10:51 AM, andy pugh wrote:
On 20 June 2017 at 17:37, Peter C. Wallace wrote:
I suspect this cannot work the way you have this setup because of the
instantaneous jump in encoder
On 06/20/2017 11:34 AM, Sebastian Kuzminsky wrote:
On 06/20/2017 10:51 AM, andy pugh wrote:
On 20 June 2017 at 17:37, Peter C. Wallace wrote:
I suspect this cannot work the way you have this setup because of the
instantaneous jump in encoder (feedback) position at index
He has hooked up axi
On 06/20/2017 10:51 AM, andy pugh wrote:
On 20 June 2017 at 17:37, Peter C. Wallace wrote:
I suspect this cannot work the way you have this setup because of the
instantaneous jump in encoder (feedback) position at index
He has hooked up axis.*.motor-pos-cmd to the stepgens' .position-cmd,
a
On 20 June 2017 at 17:37, Peter C. Wallace wrote:
> I suspect this cannot work the way you have this setup because of the
> instantaneous jump in encoder (feedback) position at index
I wonder if the answer might be to only connect the encoder once homed?
ie, use a mux2 to to connect motor-pos-
On Mon, 19 Jun 2017, tom-...@bgp.nu wrote:
Date: Mon, 19 Jun 2017 22:51:59 -0400 From: tom-...@bgp.nu Reply-To:
"Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller
(EMC)" Subject: [Emc-users] following
error only while homing
Why would I get a following error only whil
On Tuesday 20 June 2017 10:03:42 Tom Easterday wrote:
> Is there a parameter I can tweak after it happens in order to clear
> the fault (e.g. can I clear the ferror value) ? I can then try to
> home again...
>
I've no clue if this would apply to your case or not, Tom. The mpja dial
encoders I u
Does anyone know why the "daily" digest feature never works correctly?
e.g. Its 9:30am CDT and I've gotten 4 emails from emc-users already (each with
about 4-6 messages in them).
-Original Message-
From: emc-users-requ...@lists.sourceforge.net
[mailto:emc-users-requ...@lists.sourcefo
On 06/20/2017 09:52 AM, Chris Radek wrote:
On Tue, Jun 20, 2017 at 09:27:46AM +0100, andy pugh wrote:
Now, this is perfectly normal, and with a servo / pid machine the system
knows to ignore the f-error immediately after an encoder reset. What is
puzzling me here is why it isn't working in this
On 06/19/2017 08:51 PM, tom-...@bgp.nu wrote:
Why would I get a following error only while homing (latest Linuxcnc
2.7.9)? I recently added home switches to my machine. My machine
has encoders on the steppers on each of the 3 axes so I want to use
the index pulse for home. I set up the homing
On 06/20/2017 09:03 AM, Tom Easterday wrote:
Is there a parameter I can tweak after it happens in order to clear the fault
(e.g. can I clear the ferror value) ? I can then try to home again...
PID error should be recomputed every servo cycle. If PID
error remains at a large value, then it me
On 06/20/2017 08:00 AM, Tom Easterday wrote:
Andy, you are correct it is related to using index. Homing works fine if I
don't use index. The encoder reset makes sense as to why it CAN happen (but
shouldn't be). Is this just a bug? I would try to home a second time but as
Todd says, I can't
On 06/20/2017 07:13 AM, Todd Zuercher wrote:
I wish that were true. For some reason my analog servo machine trips up and
sets a following error on an axis about 25% of the time when trying to home to
index for the first time after turning on LInuxcnc. (Almost every time since it
is a 4 axis
On 06/20/2017 03:27 AM, andy pugh wrote:
On 20 June 2017 at 03:51, wrote:
Why would I get a following error only while homing
I think it is probably because you are using HOME_USE_INDEX (which will
zero the encoder at the index pulse) and feeding the encoder feedback back
into LinuxCNC.
Now
On 06/20/2017 02:50 AM, Erik Christiansen wrote:
Incidentally, I've found that the Postscript printer
language is sorta almost like gcode on steroids. Fighting
with a GUI drawing package gives me chest pains, without
producing useful output, so I've just finished drawing
floorplans, elevations
On 06/20/2017 08:52 AM, Chris Radek wrote:
On Tue, Jun 20, 2017 at 09:27:46AM +0100, andy pugh wrote:
Now, this is perfectly normal, and with a servo / pid machine the system
knows to ignore the f-error immediately after an encoder reset. What is
puzzling me here is why it isn't working in this
On 20 June 2017 at 15:52, Chris Radek wrote:
> > Now, this is perfectly normal, and with a servo / pid machine the system
> > knows to ignore the f-error immediately after an encoder reset. What is
> > puzzling me here is why it isn't working in this case. I think it is
>
> pid's index-enables ne
On Tue, Jun 20, 2017 at 09:27:46AM +0100, andy pugh wrote:
>
> Now, this is perfectly normal, and with a servo / pid machine the system
> knows to ignore the f-error immediately after an encoder reset. What is
> puzzling me here is why it isn't working in this case. I think it is
pid's index-enab
I don't see why my step/dir servo setup would be any different from a step
motor + encoder config. (Obviously, PID settings would be different as they
would be machine specific.)
One thing to remember the PID loop will likely not be able to correct for a
stalled step motor. A few missed steps
Hmm, it seems like I failed miserably trying to do that when I first built the
machine (this was my first build and Linuxcnc endeavor) back in 2010. I have a
vague recollection someone suggested that as a method of using encoders with
steppers. Seems like I spent a bunch of time flailing with
Here is what my Hal file looks like for my step/dir machine with encoder
feedback. It has the stepgens configured for velocity mode and a PID loop
(using a Mesa 5i25/7i85s).
# Generated by PNCconf at Tue Jul 9 15:53:16 2013
# If you make changes to this file, they will be
# overwritten when
Is there a parameter I can tweak after it happens in order to clear the fault
(e.g. can I clear the ferror value) ? I can then try to home again...
> On Jun 20, 2017, at 9:49 AM, Tom Easterday wrote:
>
> Todd, the ini and hal config were in the first post
>
>> On Jun 20, 2017, at 9:21 AM,
What if you set up the stepgens in velocity mode with PID (I understand that it
is the better way to do hardware stepping with Mesa cards anyway.) This is how
I have my step/dir servos configured (using the encoder feedback for the PID
loop rather than the stepgens dummy position feedback.
---
Todd, the ini and hal config were in the first post
> On Jun 20, 2017, at 9:21 AM, Todd Zuercher wrote:
>
> I just checked my config on my step/dir servo machine, and it is homing to
> index on 2 of the axis. It is not having and problems. Maybe you have a
> configuration problem.
> Coul
I just checked my config on my step/dir servo machine, and it is homing to
index on 2 of the axis. It is not having and problems. Maybe you have a
configuration problem.
Could you post a copy of your ini and hal file somewhere where we could check
it over.
- Original Message -
From: "
Andy, you are correct it is related to using index. Homing works fine if I
don't use index. The encoder reset makes sense as to why it CAN happen (but
shouldn't be). Is this just a bug? I would try to home a second time but as
Todd says, I can't clear the error. Linuxcnc shuts off when it h
- Original Message -
> From: "andy pugh"
> To: "Enhanced Machine Controller (EMC)"
> Sent: Tuesday, June 20, 2017 4:27:46 AM
> Subject: Re: [Emc-users] following error only while homing
>
> On 20 June 2017 at 03:51, wrote:
>
> > Why would I get a following error only while homing
>
>
On 20 June 2017 at 03:51, wrote:
> Why would I get a following error only while homing
I think it is probably because you are using HOME_USE_INDEX (which will
zero the encoder at the index pulse) and feeding the encoder feedback back
into LinuxCNC.
Now, this is perfectly normal, and with a ser
On 20 June 2017 at 01:24, jim wrote:
> I need my machine to move On a 10 degree line using the x y axis .
Yet another way. You can use G10 L2 to rotate the coordinate system.
http://linuxcnc.org/docs/2.7/html/gcode/g-code.html#gcode:g10-l2
--
atp
"A motorcycle is a bicycle with a pandemoniu
On 19.06.17 16:42, hubert wrote:
> Just checking, It seems unusual not to have any posts in this long a period.
> My last received post was 6/17/17, 12:27 PM
IIRC, there is usually a bit of a lull in the northern hemisphere
summer. My guess is that there's been a bit of sunny weather, and
everyone
44 matches
Mail list logo
