I discovered the limitations of the hal inputs, what is needed is:
min
max
scale
increment value
increment value change from GUI
A choice to between actual or scaled value
None of the do it all.The hal dial may change the scale but what is really
needed is possibility to change increm
Hal dial has a pin called delta scale I think. Then changing the scale (by
clicking) only changes the scale of future dial moments, which is what I think
you want.
Chris M
- Reply message -
From: "Nicklas Karlsson"
To: "Enhanced Machine Controller (EMC)"
Subject: [Emc-users] EDM machi
Yes it does but it also have a bug.
It only works then moved by the mouse but value is not updated then using the
mouse wheel sd I did during the first try, it is good enough for now. I could
fine tune and will finish of others before starting something new.
On Tue, 10 Jan 2017 20:45:24 +
In sort of the delta scale is a little bit slippery. It slip while using the
mouse wheel and only graphics is moving but no update of value. Then left mouse
button is held down and dial is moved by moving mouse pointer both graphics and
value is updated.
On Tue, 10 Jan 2017 20:45:24 +
Chri
That sounds like a bug...wheel or mouse should move it the same.
- Reply message -
From: "Nicklas Karlsson"
To: "Enhanced Machine Controller (EMC)"
Subject: [Emc-users] EDM machining, user interface, increments
Date: Tue, Jan 10, 2017 1:35 PM
In sort of the delta scale is a little bi
a lot of the pyvcp widgets suffered from update problems
i dont know about gladevcp widgets, but it sounds similar.
how to fix in gladevcp, i dont know. i have not looked at the widget
code yet
i will set up some oscillating value for a glade meter to follow and
experiment
I understand the need f
Greetings all;
I am up2date on the pi a/o this morning. So my first question is:
Does the code I'm running have the latest commits from the work on the
encoder, or is that strictly benefitting the software stepping crowd?
In any event, it seriously needs help. I hooked up the analog scope so I
On Tue, 10 Jan 2017, Gene Heskett wrote:
> Date: Tue, 10 Jan 2017 21:39:09 -0500
> From: Gene Heskett
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: EMC
> Subject: [Emc-users] Two questions.
>
> Greetings all;
>
> I am up2date on the pi a/o this morning. So my first question is:
On 01/09/2017 07:42 PM, Gene Heskett wrote:
> Progress. Everything with power on it is now working,
> which means the vfd and the encoder, the noise is gone
> from the encoders velocity trace on the halscope.
GREAT!
> What sort of settings are those using a vfd using for
> minimum speed, and h
On 01/10/2017 08:39 PM, Gene Heskett wrote:
> But if I hook up the halscope, the apparent quadrature error is worthless
> due to the 1KHz servo-loop timing limiting the bandwidth.
Well, that's why we use hardware encoder counters, as
sampling the quadrature at 1 KHz just isn't fast enough.
Jon
-
I pushed a fix for hal_dial to 2.7 - not sure what you are using.
eventually it will cycle thru to master (and later releases)
The fix is simple (two lines) if you wish to just add it for now.
in gladevcp/hal_dial.py
# handle the scroll wheel of the mouse
def _scroll(self, widget,
On Tuesday 10 January 2017 23:02:28 Jon Elson wrote:
> On 01/10/2017 08:39 PM, Gene Heskett wrote:
> > But if I hook up the halscope, the apparent quadrature error is
> > worthless due to the 1KHz servo-loop timing limiting the bandwidth.
>
> Well, that's why we use hardware encoder counters, as
>
>>
>> AFAIK there are no significant issues with HM2 encoder velocity
>> estimation
>>
>> Heres a 100 Hz quadrature velocity trace:
>>
>> http://freeby.mesanet.com/100_Hz_quadrature_velocity.png
>>
>> Notice theres no discernible ripple in the velocity even though theres
>> considerable sample jitt
13 matches
Mail list logo
