Il giorno mer, 30/11/2011 alle 16.44 +0000, andy pugh ha scritto:
> On 30 November 2011 16:33, Spiderdab <77...@tiscali.it> wrote:
>
> > any other idea?
>
> No, it's a mystery to me. The "ABORT" sets all velocities to zero
> prior to setting the selected axis to the requested speed, so it makes
> sense that that would be the reason you can only jog one axis at a
> time (And if you try to job more than one, the highest-numbered should
> always "win". Is that what you see?
>
Hi, again trying to solve the impossibility of jogging more than one
axis in teleop.mode.
i've foud this part into xemc.cc (emc 2.5):
....cut....
static int sendJogCont(int axis, double speed)
{
EMC_AXIS_JOG emc_axis_jog_msg;
if (axis < 0 || axis >= XEMC_NUM_AXES) {
return -1;
}
if (axisJogging != -1) {
// ignore request to jog, if an axis is already jogging
return 0;
}
if (0 == jogPol[axis]) {
speed = -speed;
}
emc_axis_jog_msg.serial_number = ++emcCommandSerialNumber;
emc_axis_jog_msg.axis = axis;
emc_axis_jog_msg.vel = speed / 60.0;
emcCommandBuffer->write(emc_axis_jog_msg);
axisJogging = axis;
return 0;
}
...cut...
do you think it can be implicated on the issue?
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
