jmkasunich_ is now known as jmkasunich
jepler: you around?
feed per rev
I believe that uses motion.spindle-speed-in
is that supposed to be in RPM?
it seems it should be the same units as the spindle speed output
that would be RPM
but it seems to be wrong on my machine
does the nist-lathe config tell you anything?
that should be the one that was used for all that lathe testing/demos
right now its doing 176 RPM (and that is what I'm sending to motion.spindle-speed-in), but when I command a G95 move with F0.001, it moves a lot more than 0.176" in a minute
does it seem to be 60x as far? ;)
I commanded a 1/2" move, and it was only a second or so
then I'd say the input is in revs/second ;)
nist-lathe isn't helpfull, that pin isn't hooked up
cradek's lathe is what FPR was tested on
oj, I thoought it was the loaner NIST lathe
sim/lathe: net spindle-rps-filtered lowpass.0.out scale.0.in motion.spindle-speed-in
so it is in RPS
that is gonna annoy people who want to loop back spindle-speed-out to spindle-speed-in
but there must have been a good reason for it
velocities in the motion controller are /second, not /minute
so that would be easier
I just realized that its almost midnight and I'm still setting up to make this part
I think I'll stick with conventional feeds and move on ;-)
jmkasunich: the output of "encoder" is going to be in rps with any natural setting of encoder.scale, but motion.spindle-speed-out was always in rpm
I probably should have changed spindle-speed-out to be rps but I didn't have the guts
fenn_ is now known as fenn
WOOWOOOOO! <- sound of oncoming trainwreck
cradek_ is now known as cradek
oooooh - a train!
* skunkworks likes trains
cradek: where's the train?
* fenn sets up a lawn chair next to the tracks
* skunkworks has cookies and coffee
yay, lerman bites the bullet for us
* skunkworks hugs lerman
* skunkworks thinks he would be ok with that.
hmmm - maybe I shouldn't have sent mine :)
bunch of emc fan-boys on the list now.. ;)
* fenn swoons
alex_joni: have you been building rt kernels on hardy alpha4 yet?
any idea when the post-alpha4 disc image is scheduled? I want to start playing with this, but won't realistically have time before the start of March
about the same here
jepler: I still ponder on a PC to use.. the one I have would be too slow
ah, I found dates for alphas 4 and 5 on the page HardyReleaseSchedule
er, 5 and 6 that is
Feb 27 and Mar 6, respectively
jepler: I was planning to have something set up by beta-1
alex_joni: I didn't see anything called "beta" on the schedule, just alphas 1 through 6..
the beta release is supposed to be March 22 - it's just not pointed out in the last column
on this page: https://wiki.ubuntu.com/HardyReleaseSchedule
err - March 20
I know I don't get to set deadlines, but it would be great to have the EMC2 Hardy Live CD working well enough to hand out at the upcoming CNC Workshop in June
it also seems like a pretty doable goal
I agree on all counts
I'd like to have discs for the ESC presentation, but that's in late April so it's unlikely
actually, it's impossible - nevermind
the release is a week after the presentation ;)
better to distribute something older and well tested
yeah. I'll probably mention that there'sa new release being worked on
and not bother handing stuff out - they can download it if they want
jepler: given the fact that there's a 2.6.24 patch in volcano, I suspect it should be doable
but the RT kernel is basicly a coinflipping technology :)
sometimes it works great, sometimes not at all
very good news that there's the right patch
maybe if all of us try, one of us will get a working kernel
oh, I am sure I'll get a working kernel
the thing I'm worried about is getting a working kernel which works on a lot of machines :)
of course, with time and hardware marching on, we can just turn stuff like APIC on and tell people who can't run it to use dapper instead
(to name the thing besides 1GB RAM that I remember being the most trouble)
that's an interesting idea
jepler: I don't see why APIC would be different in 2.6.24
was there something on this which I missed?
I think jepler is saying we could build for smp
APIC, not ACPI. APIC is newer alternative to the old PIT timer
* alex_joni is dislexic
I'm having trouble deciding where to put the packages
would linuxcnc.org/experimental/lenny/ work for you?
yes, it's okay
acemi: ok, great.. will let you know when it's done :)
acemi: when you built the packages.. there should have been a couple more files
.dsc and .tar.gz for the sources
you means for rtai-xxx or for the kernel
I saw the kernel source
I don't create source for rtai
how did you make the package then?
I'm not talking about a source deb
make-kpkg ... module_image
the source in a tar.gz is enough
alex_joni: I don't understand what you mean. do you want a package sometinh like rtai-source
I want the rtai-x.y.tar.gz you used to create the deb
I think you used rtai-3.6.tar.bz2
(judging by the wiki page..)
if you do make-kpkg ... modules, instead of modules_image, you should get source pacakges too
alex_joni: wget --no-check-certif https://www.rtai.org/RTAI/rtai-3.6.tar.bz2
oh wait I think I'm wrong
I use this tar.gz
cradek: I think it only creates a diff for stuff you changed from the original src
I created theese packages as described in http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Debian_Lenny_Compile_RTAI
module_image didn'T create a source package
doesn't python do garbage collection?
alex_joni: yes, python uses reference counting plus a cyclic garbage collector to reclaim memory used by unreachable objects.
why do you ask?
hmm.. seems odd python progs can have memory leaks..
do you have to specifically dealocate something so the garbage collector eats it?
When coding extensions for Python (e.g., in C or C++) you have to explicitly manage reference counts and for objects that can participate in cycles you must also write specific hooks for the cyclic garbage collector.
when writing Python code, you can't specifically free objects (you can only remove references to objects -- this is what the 'del' statement does; when an object becomes unreferenced, the implementation may free it)
so, why do you ask?
oh, was hanging around in #cia
and the guy working on cia is having some fun with python and memory leaks
hmmm. this page defines U V W axes as parallel to X Y Z (not in rotated tool-space): http://www.linuxcnc.org/handbook/gcode/g-code.html
don't believe everything you read :-P
heh - well ok then
someone smart recently said that when the docs and the code disagree, the code wins
I think it was jepler
fwiw, the tool-space uvw is how I decided to write my kinematics. you can do whatever you like when you write yours
I choose to complain about the current implementation instead ;)
complain complain complain
there, I'm done now
fwiw here's what the current docs say: http://linuxcnc.org/docs/2.2/html/gcode_main.html#axes,%20secondary%20linear
The U, V, and W axes produce linear motion in three mutually orthogonal directions. Typically, X and U are parallel, Y and V are parallel, and Z and W are parallel.
I wasn't being a smartass, actually - there are 6 linear axes and 3 rotary - you really can do whatever you want
notice the weasel-word stuck in there :-P
ooohhhh - clever wording there
cradek, I understand - I just noticed that there was a definition somewhere - something we missed when we (i) looked for it before
there's, uh, probably not much value to the stuff under /handbook anymore
in fact I'm surprised it even mentions UVW
"X, Y, and Z words will be accepted by the current (Jan, 2000) interpreter. NIST will soon release an expanded interpreter that will allow for three rotary axis A, B, C, as well."
yeah I can't wait for that to come out
well, it's not like it's Duke Nukem Forever or anything
acemi: done.. please check the filenames
I had to manually rename them all
ok, thanks alex_joni
* alex_joni leaves for a while..
haha this is fun
749G -8.0Z 1.1T 101% /home/.jared
total / used / free / percent used
heh, guess it doesn't support Yottabytes
8Zetta's is still a *huge* load of data .. missing
8 billion TB
-8.0 zettibytes seems is -2^63 1024-byte blocks i.e., the signed 64-bit number with all bits set