Il giorno lun, 05/12/2011 alle 13.41 +, andy pugh ha scritto:
On 5 December 2011 13:13, Spiderdab 77...@tiscali.it wrote:
if (axisJogging != -1) {
// ignore request to jog, if an axis is already jogging
return 0;
...
do you think it can be implicated on the issue?
..in the meantime, i've also found another user having the same issue:
www.you*ube.com/watch?v=FgnxBaFFDi8
he confirmed me on e-mail.
in fact in the video, he's jogging only one axis at a time.
--
All the data
what about this part?
static int sendJogStop(int axis)
{
EMC_AXIS_ABORT emc_axis_abort_msg;
// in case of TELEOP mode we really need to send an TELEOP_VECTOR message
// not a simple AXIS_ABORT, as more than one axis would be moving
// (hint TELEOP mode is for
what about this part?
.
forgot to say it is in the halui.cc file, line 1352, emc 2.5.
I saw the same file into joint_axes3 branch, and there's not this part.
(there i can jog two or more axis at a time..)
--
All
..in the meantime, i've also found another user having the same issue:
http://www.youtube.com/watch?v=FgnxBaFFDi8
he confirmed me on e-mail.
in fact in the video, he's jogging only one axis at a time.
--
All the data
On 5 December 2011 14:51, Spiderdab 77...@tiscali.it wrote:
what about this part?
That's the ZERO_EMC_POSE which you already tried killing.
I guess you could try doing it in both places?
--
atp
The idea that there is no such thing as objective truth is, quite simply, wrong.
Il giorno lun, 05/12/2011 alle 15.28 +, andy pugh ha scritto:
On 5 December 2011 14:51, Spiderdab 77...@tiscali.it wrote:
what about this part?
That's the ZERO_EMC_POSE which you already tried killing.
I guess you could try doing it in both places?
ah, yes. but the lines were
On 5 December 2011 15:48, Spiderdab 77...@tiscali.it wrote:
but i cannot find in which file ZERO_EMC_POSE is created. can you help
me?
http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=src/emc/nml_intf/emcpos.h
--
atp
The idea that there is no such thing as objective truth is, quite simply,
If you want to make halui.jog-speed pin working in ja3 branch, comment
line 1223 (axis-teleop_tp.max_vel = axis-vel_limit;) in file
/src/emc/motion/control.c and recompile
regards,
Michael
W dniu 05.12.2011 17:32, andy pugh pisze:
On 5 December 2011 15:48, Spiderdab77...@tiscali.it wrote:
Il giorno lun, 05/12/2011 alle 19.01 +0100, Michał Geszkiewicz ha
scritto:
If you want to make halui.jog-speed pin working in ja3 branch, comment
line 1223 (axis-teleop_tp.max_vel = axis-vel_limit;) in file
/src/emc/motion/control.c and recompile
regards,
Michael
What i see, trying to change values, is that i can now change with the
Joystick-Slider the speed set in halui.jog-speed, but it doesn't go
further than [JOINT_n]MAX_VELOCITY.
I think this is an error, because the limit should be into
[AXIS-n]MAX_VELOCITY (which, unfortunately now seems to not have
2011/12/5 Spiderdab 77...@tiscali.it:
What i see, trying to change values, is that i can now change with the
Joystick-Slider the speed set in halui.jog-speed, but it doesn't go
further than [JOINT_n]MAX_VELOCITY.
It perfectly makes sense to me - You cannot jog than the slowest
joint, because
Il giorno lun, 05/12/2011 alle 21.38 +0200, Viesturs Lācis ha scritto:
2011/12/5 Spiderdab 77...@tiscali.it:
What i see, trying to change values, is that i can now change with the
Joystick-Slider the speed set in halui.jog-speed, but it doesn't go
further than [JOINT_n]MAX_VELOCITY.
It
Yes this issue is known and it is in TODO in ja3
regards
Michael
W dniu 05.12.2011 22:40, Spiderdab pisze:
Il giorno lun, 05/12/2011 alle 21.38 +0200, Viesturs Lācis ha scritto:
2011/12/5 Spiderdab77...@tiscali.it:
What i see, trying to change values, is that i can now change with the
Thank you, I like more the logic of ja3, and now that you solved my
'biggest' problem, i'll hardly go back to straight EMC.
So you know there's a good beta-tester here, when the ja3 developement
will go on!
regards, Davide.
Il giorno lun, 05/12/2011 alle 22.44 +0100, Michał Geszkiewicz ha
15 matches
Mail list logo
