Well, no solution yet, and only narrowed things a little bit:
Continuing Charles's work, I merged the bitmuster-patched v2.4.4
forward. Whatever changes are causing the problem Charles describes
were introduced between v2.4.7 and v2.5.0, and also between v2.5.0-pre0
and v2.5.0-pre1.
That
Here's Ken Lerman's idea worked in: jog in coordinated mode during pause
http://www.youtube.com/watch?v=2wabcOH9YAA
I'm entertaining feedback on the principle; this is not a patch yet; it's still
shaky on abort and limit checking.
The nice thing is that it's fairly unintrusive - all through
hi,
sounds good. The work will deminish with more insight.
I thought I was going to set up a system this weekend, but at the moment I
lean to rather digging the code and the diffs.
Since I do not think that me repeating your and Charles' findings will
help, unless you think different.
As a
I wonder if this might be related to our problem.
Deadlocking mutexes .. perhaps we should ask on the rt-linux mailing list ?
Right now I am a bit undsure about userspace mutexes but I'll
look at the code when I get home, it just sounds familiar, but might
be out of context.
Sorry people,
I sent the last message twice, but sourceforge told me my ip was blocked
and the message was refused: because of abuse
yet the messages go through . . . .
must be that I put my rabbit foot in the wrong pocket this morning.
j.
Looking good. Is this capable of using the existing jog mechanism? For
instance I have MPGs on my machines so ideally they need to still
function correctly.
Les
On 26/04/2012 09:10, Michael Haberler wrote:
Here's Ken Lerman's idea worked in: jog in coordinated mode during pause
2012/4/26 Michael Haberler mai...@mah.priv.at:
The only gotcha I see is - this is coord mode, so its axes not joints input,
this might be a bit confusing for an MPG and a non-trivkin machine
Well, I think that it is great that it is axes, not joints... How will
You jog a puma robot straight
so what's the idea?
Do you want to have the option to jog in coordinated mode in manual?
- Michael
Am 26.04.2012 um 12:53 schrieb Viesturs Lācis:
2012/4/26 Michael Haberler mai...@mah.priv.at:
The only gotcha I see is - this is coord mode, so its axes not joints input,
this might be a
2012/4/26 Michael Haberler mai...@mah.priv.at:
so what's the idea?
Do you want to have the option to jog in coordinated mode in manual?
Ideally - INI file option for automatic switching to teleop mode as
soon as all joints are homed. So that user does not interact with
joint mode - they tend
If you were running a gantry, I would think that it would still be
pretty obvious which way you would need to move even in
coordinated mode with non trivial kinematics.
Dave
On 4/26/2012 9:08 AM, Jan de Kruyf wrote:
Makes sense to me. Except inthe case of an emergency, how do you want to
jog
yes, but hexapods and robots are a problem
j.
On Thu, Apr 26, 2012 at 3:42 PM, Dave e...@dc9.tzo.com wrote:
If you were running a gantry, I would think that it would still be
pretty obvious which way you would need to move even in
coordinated mode with non trivial kinematics.
Dave
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/26/2012 2:49 AM, John Morris wrote:
Well, no solution yet, and only narrowed things a little bit:
Continuing Charles's work, I merged the bitmuster-patched v2.4.4
forward. Whatever changes are causing the problem Charles
describes were
On 26 April 2012 08:49, John Morris j...@zultron.com wrote:
That sounds encouraging until you look at git and see that span between
v2.5.0-pre0 and -pre1 is over a year, 833 files and 120k+ insertions,
and that v2.5.0-pre0 is more closely related to v2.4.0 than v2.4.4.
git bisect will
Il giorno gio, 26/04/2012 alle 13.53 +0300, Viesturs Lācis ha scritto:
2012/4/26 Michael Haberler mai...@mah.priv.at:
The only gotcha I see is - this is coord mode, so its axes not joints
input, this might be a bit confusing for an MPG and a non-trivkin machine
Well, I think that it is
I dont seem to get 'rtapi_shmem_new()' and friends in ./rtapi/linux_rtapi.c
which presumably is the rtapi interface in the case of rt_preempt.
j.
On Thu, Apr 26, 2012 at 6:47 PM, Charles Steinkuehler
char...@steinkuehler.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
2012/4/26 Jan de Kruyf jan.de.kr...@gmail.com:
yes, but hexapods and robots are a problem
There is no way to jog single joint on hexapod without causing damage
to the construction of machine!
Jogging in joint mode is dangerous with machines with parallel
kinematics, including gantries. It is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still working on figuring those out as well. :)
Near as I can tell, since there's no kernel space vs. user space with
the preempt-rt patch (everything runs in user-space), the realtime and
user-mode functions can be the same so the functions
I was going to bring that issue up as well, that is indeed my understanding
of preempt_rt, from reading the docs.
I am not sure though that this has caused the mutex drama. That can only be
if there is an unbalanced mutex or if the inheritance mechanism has not
worked properly, or perhaps if some
By the way: there is somewhere a note in the software about some pagefaults
at startup that probably dont need fixing!
I forget at the moment where I saw it. Keep your eyes popped for that. It
also explains Lars' experience.
j.
On Thu, Apr 26, 2012 at 9:32 PM, Jan de Kruyf
Hi Andy,
git bisect will probably allow you to narrow things down a lot more
quickly than you imagine.
I was so anxious to get a head start on your suggestion that I began
yesterday!
The commit where the problem begins is
8868436313c34eaf60a14f5c930f0f2035b9ee48.
After saying this was
Mmm, yes you might be very right.
I postulated a theoretical case there, since I have no real experience to
speak of on those machines.
OK, so what about the old trusted way of supplying a springloaded
key-switch in the electrical cabinet that allows joint mode.
But at the same time travel in the
Hey just go and sell it to that investor, and just make double sure to
please your family. So you will be all fresh when you come back.
I will put in some more code reading and see what gives. (and please my
wife off course!)
j.
On Thu, Apr 26, 2012 at 9:38 PM, John Morris j...@zultron.com
check out the RT wiki ... there are some examples, usually you
prefault the stacks, for threads and then do a mlock on all of the
memory for the process.
2012/4/26 Jan de Kruyf jan.de.kr...@gmail.com:
By the way: there is somewhere a note in the software about some pagefaults
at startup that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/26/2012 2:32 PM, Jan de Kruyf wrote:
I was going to bring that issue up as well, that is indeed my
understanding of preempt_rt, from reading the docs. I am not sure
though that this has caused the mutex drama. That can only be if
there is an
24 matches
Mail list logo
