Gentlemen,
I think I have it figured out.
I can now see both the forward and inverse variables after moving
the machine to a position with mdi.
I will be playing with this much more and report what I find. I
will document how I did this when I get it figured out and repeatable.
:)
thanks
S
Gentlemen,
1. open two shells
2. type em2-trunk-sim/scripts/emc-environment in each shell
3. in the first shell start gdb
gdb rtapi_app
4. at the gdb prompt
b kinematicsForward
5. answer 'y' to the question
6. at the gdb prompt
yes, I read http://dirac.org/linux/gdb/ - it was helpful
if that is supposed to work then I probably did something prior to
continue that 'helped' it to not work.
I will try it again
thanks
Stuart
On Sat, Jan 31, 2009 at 10:37 AM, Jeff Epler wrote:
> did you "continue" after you "disable"d?
>
> J
did you "continue" after you "disable"d?
Jeff
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_
Gentlemen,
I tried that but couldn't make it work. I couldn't get EMC to move
after I disabled the break point.
I will try it again in the morning.
thanks
Stuart
On Fri, Jan 30, 2009 at 9:49 PM, Jeff Epler wrote:
> On Fri, Jan 30, 2009 at 11:39:27AM -0600, Stuart Stevenson wrote:
>> Gentle
On Fri, Jan 30, 2009 at 11:39:27AM -0600, Stuart Stevenson wrote:
> Gentlemen,
>I read the link. It helped a lot. I am able to use gdb to do
> limited debug of the kinematics file. I need to be able to stop the
> debug (I think it is disable 'n') and run the control and then restart
> the debug
Gentlemen,
I read the link. It helped a lot. I am able to use gdb to do
limited debug of the kinematics file. I need to be able to stop the
debug (I think it is disable 'n') and run the control and then restart
the debug to catch the break point (I think it is enable 'n'). I
haven't been able fi
Actually, I discovered that someone I had apparently already documented
a lot of this stuff on the wiki:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?DebuggingRtapi
Including this item which is an important one:
To make gdb find the source files, it seems necessary to use the
'directory
thank you very much
On Tue, Jan 20, 2009 at 11:24 AM, Jeff Epler wrote:
> If you configure emc with --enable-simulator and run with a
> configuration that doesn't load any hardware drivers, then you can use
> "gdb" (commandline debugger) to single-step through your kinematics.
>
> Step 0: Assumin
You might want to put that on the wiki, Jeff.
Mark
On Tue, Jan 20, 2009 at 12:24 PM, Jeff Epler wrote:
> If you configure emc with --enable-simulator and run with a
> configuration that doesn't load any hardware drivers, then you can use
> "gdb" (commandline debugger) to single-step through your
If you configure emc with --enable-simulator and run with a
configuration that doesn't load any hardware drivers, then you can use
"gdb" (commandline debugger) to single-step through your kinematics.
Step 0: Assuming you also configured with "--enable-run-in-place",
always remember to ". scripts/e
11 matches
Mail list logo
