how have you guys been?
[14:06:20] <skunkworks_> http://www.linuxcnc.org/index.php
that is funny
[14:06:35] <skunkworks_> http://www.cnczone.com/forums/showthread.php?t=87047&page=2
skunkworks_: the guy doesn't find a trajectory period in his inifile because all the samples had it removed; they all use the same value for servo and traj. This doesn't seem to have made it into the release notes, but it was in 2.3.0.
I think he figured that out.
'I searched through the code and it looks like it defaults to the servo period if left unspecified'
how is the zenbot coming? I have 2 sides of the garage sided. :) (putting in access doors and windows slow me down) (and angle cuts on the gable ends)
untouched. but I helped Chris with JR last night. While I was there we got the spindle running.
nice! what ended up being the problem?
with the spindle? no problem, just working out the wiring.
oh - I thought there was some error on it - like over-speed or something
I dunno what cradek might have worked out about the spindle before I got there
there are a bunch of indicators on the spindle drive that we eventually figured out the meaning of
wasn't it a servo drive (Y axis) that had the various error codes?
that also :)
when ever I see JR - I think of sean conery saying jr in indiana jones..
SWPadnos: yeah, I think chris is planning to re-mount that amp horizontally and use a bobbing bird to reset it when it errors.. at least, that was my suggestion.
tuning the bob frequency could be a fun task
we had a solinoid setup on the 'input' button on the laser controller... The computer was far enough away that it was an annoyance to get up and set the controller to receive. So there was a little button ot the desk so the solinoid would push the button on the controller.
skunkworks_: how's your puma?
sitting in the corner.
I was planning on making a 2 axis board (smaller version of the big amp) 10a maybe 80v for the puma.
but other things have gotten in the way - garage
how is your model?
well.. the model is fine
the kins are a bit problematic :D
slowly starting to get a grasp on things
like what a Jacobian is ;)
jacobian matrix :)
made some solver programs that run on the ps3 under linux last semester, but they were gauss-jacobi
just a different type, we mixed the two
maybe im too tired, it may have been jacobi, and then a gauss-seidel, ide have to look
alex_joni : what are you working on?
gezar: some robot simulation
alex_joni: do you teach a class of have pull with an instructor?
skunkworks_: come again?
do you teach a class that you have access to students for help?
nope.. had an intern
oh - nice
he struggled.. but didn't quite make it
he did write a lot of code though ;)
and ok'ed to GPL it
I'll have to see if I can get it to usefull status, and commit it
basicly it's a library like posemath, but for DH stuff
oh. of course
it's basicly quite simple
but obviously there are a ton of pages describing the same thing with slight differences out there
so getting the "right" one is hard ;)
oh right - that was the general pivoting arm robot solution
so you could enter all the dimensions of the arm?
it's basicly only a way of defining the coordinate systems for each joint/link
wow - very cool
forward kins is trivial
you set up one coordinate system for each joint
DH says that Z points up at each joint, and the joint rotates around that Z
you define X (in a way hard to describe on IRC)
then you also get Y
the distance in X from the previous coordinate system (i-1) to this one (i) is called Di
and the distance in Z from the ... is called Ai
you also have a rotation between the previous and the current, called Alphai
[18:32:27] <SWPadnos> http://prt.fernuni-hagen.de/lehre/KURSE/PRT001/course_main/node15.html
picture 3.2 is what I'm talking about
so you have 4 "variables" for each joint
Ai, Di, Alphai and Thetai
A and D are constants though, aren't they?
(the pivot length and Z offset)
and alpha is constant
oh right - if it would change, it would be on the previous link
theta is the rotation of the joint (e.g. joint rotation)
alpha only changes if the robot has a serious problem :D
then you construct 4 matrices for each link
2 rotation (alpha and theta)
and 2 translations (ai, di)
the 4 multiplied generate the transformation matrix for this joint
that way you can generate all 6 transf. matrixes
and multiplied together you get the forwards kins ;)
it's basicly about 6 + 5 lines of C code
(using the lib obviously ;)
should be one line :)
(in C++ anyway)
well.. you need to pass 6 x 4 params
hard to do in one line ;)
is it C or C++?
kinematics run in kernel space ;)
ok. that would make a lot of this kind of thing more complex
but not the part about putting it in the kernel
oh great. now I have to reboot again.
well, maybe it'll let the mouse work for more than 30 seconds at a time
I would really like to make a hexapod also. Buy 6 small ballscrews - spin the nut and one of the yokes. Too many projects.
good night all
good night alex