Hello,
Yes, Gmoccapy has all of the required pins for using with a jog wheel, that
is what I am doing now, and it really works well.
The issue is that compared to the worst commercial grade controller I have
worked with, is it is a poor hack.
There needs to be some way to show the user what axis is
On 23 June 2016 at 21:27, Neil Whelchel wrote:
> On the subject of Gmoccapy, I think that a REALLY important modification
> would be to add a jog wheel mode. This would be a configuration setting
> that would replace the jog increment buttons with axis selection and
> scaling buttons for the jog w
Hello,
On the subject of Gmoccapy, I think that a REALLY important modification
would be to add a jog wheel mode. This would be a configuration setting
that would replace the jog increment buttons with axis selection and
scaling buttons for the jog wheel.
In my setup, I added five physical lighted
On 21 June 2016 at 23:47, Dewey Garrett wrote:
> I imagine Andy will want to update the update_ini script.
commit 5fd614e1b42c3455514079eac9aa41ed5c3f572a
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
Hallo Dewey,
thanks for your very detailed explanation, most of that is known, but I
still do not understand why that have been changed, as it does not
change any behavior, it just makes thinks more difficult for users, used
to have the same INI settings for several updates.
I have the impress
The specification of velocities (and accelerations) is
confusing because of the multitude of ini settings available
in the [TRAJ], [AXIS_ll], [JOINTS_nn], and [DISPLAY] sections
of an ini file. Extra complications may occur because the
interpretation of items in the [DISPLAY] section may be
GUI-d
On 22 June 2016 at 07:18, Niemand Sonst wrote:
> IMHO the solution is not ideal!
> You changed all INI Files to use [TRAJ] MAX_LINEAR_VELOCITY, but why?
> This will invoke, that every user with intention to update to JA will
> have to modify that value, as this behavior is completely different to
Hallo Dewey,
I just took a look on your last JA15 push, solving this issue.
IMHO the solution is not ideal!
You changed all INI Files to use [TRAJ] MAX_LINEAR_VELOCITY, but why?
This will invoke, that every user with intention to update to JA will
have to modify that value, as this behavior is c
I think the change was made in joints_axes over 8 years ago and
maintained through various rebases.
The commit which indicates that it squashes even earlier commits
is (in the rebased 17jun2016 joints_axes15 branch):
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=commitdiff;h=cdc073dc6068ec0e003
On 21 June 2016 at 20:28, Niemand Sonst wrote:
> self.stat.max_velocity should return the value of [TRAJ]MAX_VELOCITY,
> but it does not!
> it returns the value of MAX_LINEAR_VELOCITY, what is wrong! That is a
> difference from master to JA15, Why ?
The change is here:
https://github.com/LinuxCN
10 matches
Mail list logo
