I appreciate all the help. This is a low-priority project and I don’t have much
time to work on it and I‘m learning as I go here.
I’ve tested all main powered devices for ground loops by individually
disconnecting each ground and testing with an ohm meter. It appears that I took
Gene’s
On Wed, 19 Aug 2020, Thaddeus Waldner wrote:
Date: Wed, 19 Aug 2020 13:04:54 -0500
From: Thaddeus Waldner
Reply-To: "Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller (EMC)"
Subject: Re: [Emc-users] 7i73 Lagging jog key
Can someone define a good wa
On Wednesday 19 August 2020 14:04:54 Thaddeus Waldner wrote:
> Can someone define a good way to test the keypad scan signals? I put a
> scope on a circuit and it appears that the signals stands out clearly
> from the noise. I don’t know what the switch thresholds are so the
> noise could still be
I wonder if there is some aggressive switch de-bounce happening. Without
looking at your hal file, I'd bet there is a software debounce. If so it
has to wait until it sees a steady-state on the pin for some period of
time. Any random noise above some threshold would re-set the waiting time.
On Wed, 19 Aug 2020 at 19:07, Thaddeus Waldner wrote:
> Could unused pins be an issue?
I have seen unused pins charge up and carry a signal into the next pin
in the multiplexer, in multiplexed ADC.
But whether that might be a problem here would need PCWs expertise.
--
atp
"A motorcycle is a
Can someone define a good way to test the keypad scan signals? I put a scope on
a circuit and it appears that the signals stands out clearly from the noise. I
don’t know what the switch thresholds are so the noise could still be enough to
cause issues. Setting the scope trigger voltage to about
;
>> To: "Enhanced Machine Controller (EMC)"
>> Subject: Re: [Emc-users] 7i73 Lagging jog key
>> I finally got to do a little troubleshooting and hereџџs what I found:
>
> Key response on the keypad is never as fast as the on-screen UI but it is
> consistent.
On Friday 07 August 2020 14:07:04 Thaddeus Waldner wrote:
> I finally got to do a little troubleshooting and here’s what I found:
>
> Key response on the keypad is never as fast as the on-screen UI but it
> is consistent. I’m guessing there’s about a 100-300 ms delay but
> that’s just a guess.
On Fri, 7 Aug 2020, Thaddeus Waldner wrote:
Date: Fri, 7 Aug 2020 13:07:04 -0500
From: Thaddeus Waldner
Reply-To: "Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller (EMC)"
Subject: Re: [Emc-users] 7i73 Lagging jog key
I finally got to do a li
I finally got to do a little troubleshooting and here’s what I found:
Key response on the keypad is never as fast as the on-screen UI but it is
consistent. I’m guessing there’s about a 100-300 ms delay but that’s just a
guess. Could this delay be due to the fact that this is a scanning keypad?
On Fri, 31 Jul 2020 at 15:15, Peter C. Wallace wrote:
> Also even with default sserial error management you could only have
> 10 servo thread cycles (10 ms with a 1 ms servo thread) of delay
> due to failed transactions before a sserial error popup would occur.
Maybe noise on the keyboard
There does not seem to be any delay in the matrix_kb component:
http://freeby.mesanet.com/matrix_kb.png
Also even with default sserial error management you could only have
10 servo thread cycles (10 ms with a 1 ms servo thread) of delay
due to failed transactions before a sserial error popup
Jogging from the gmoccapy ui works as fast as I can click the on-screen button
with the mouse.
So it’s not a userspace issue.
> On Jul 30, 2020, at 5:43 PM, Chris Albertson
> wrote:
>
> I'm using an x-box gamepad to jog three-axis and it is 100% in user space.
> There is zero noticeable
On Thu, 30 Jul 2020, Thaddeus Waldner wrote:
Date: Thu, 30 Jul 2020 17:41:50 -0500
From: Thaddeus Waldner
Reply-To: "Enhanced Machine Controller (EMC)"
To: "Enhanced Machine Controller (EMC)"
Subject: Re: [Emc-users] 7i73 Lagging jog key
*EMI, I meant to say
On J
*EMI, I meant to say
> On Jul 30, 2020, at 5:38 PM, Thaddeus Waldner wrote:
>
> The halui jog pin and the matrix_kb pin do move in unison on the halscope,
> both with random lag of up to nearly a second.
>
> Also:
>
> This problem is made much worse when the vfd is running. So I suspect
I'm using an x-box gamepad to jog three-axis and it is 100% in user space.
There is zero noticeable "lag" or delay.
If there is a lag then it's a bug and not just the way it is. Even on a
non-real-time system if something like a web server or a spreadsheet took 2
seconds I'd say it was broken.
The halui jog pin and the matrix_kb pin do move in unison on the halscope, both
with random lag of up to nearly a second.
Also:
This problem is made much worse when the vfd is running. So I suspect have an
Emf or grounding issue.
Is there a way to test the sserial connection? Should this
On Thursday 30 July 2020 16:12:09 andy pugh wrote:
> On Thu, 30 Jul 2020 at 19:49, Thaddeus Waldner
wrote:
> > I’m having an issue with jog lag when using a matrix keypad.
> > Keys are connected via a 7i73 board. I have each Jog key mapped to
> > halui.axis pins. Eg. X- is mapped to
On Thu, 30 Jul 2020 at 19:49, Thaddeus Waldner wrote:
>
> I’m having an issue with jog lag when using a matrix keypad.
> Keys are connected via a 7i73 board. I have each Jog key mapped to halui.axis
> pins. Eg. X- is mapped to halui.axis.x.minus
> Is this the correct way to connect jog keys?
I’m having an issue with jog lag when using a matrix keypad.
Keys are connected via a 7i73 board. I have each Jog key mapped to halui.axis
pins. Eg. X- is mapped to halui.axis.x.minus
Is this the correct way to connect jog keys?
___
Emc-users
20 matches
Mail list logo
