client was nice.
gave me like a $50 box of chocolates from her store.
wtf? history and tab completion in halcmd don't work
did a cvs up, reconfigured
configure says readline is ok
did a make clean and make
they were working a couple days ago
way too late up again I see
I'm at work for 1.5h already
jmkasunich_ is now known as jmkasunich
I knew there was a reason I liked xemet ;)
Hi skunkworks How you doing with the retrofit of that k&t
slow- have not had much time to work on it.
in a month or 2 - We are in the proccess of buying/selling our house
moving to trempealeau
I am following the directions on the wiki for a fresh install run in place. I am down to the ./configure --enable-run-in-place
and get this configure: error: Required header Python.h missing. Install it, or specify --di sable-python to skip the parts of emc2 that depend on Python
this is a fresh install of ubuntu
skunkwork1: did you follow the instruction that says to "apt-get build-dep emc2"?
skunkwork1: did it complete without error?
I think so - could I re-run it and see?
how did you install? official ubuntu cd? emc 2.0 live cd? emc 2.1 live cd?
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ok -- in that case, "apt-get build-dep emc2" installs the packages to rebuild emc 2.0 which did not include axis
change your repositories to the emc2.1 ones, then "apt-get update", then "apt-get build-dep emc2" again. it should install additional packages, including the one the error is about
ok -- I thought there used to be 2 apt-get commands to do that before.
is there still an apt-get axis.... command?
no, not anymore
oops hold on
missed your last previouse post
alethe linux kernel driver has some autodetection smarts which we don't have in emc
maybe we can use (not include) those in some testing/probing
that is suggested somewhere in the documentation, in fact
but why bother, his laptop will be unusable anyway
unloadrt hal_parport, loadrt pc_parport, grep /proc/ioports
loadrt pc_parport won't work
it's parport_pc anyway
[17:37:54] <jepler> http://linuxcnc.org/docs/2.1/html/hal/drivers/index.html
(sudo modprobe -a parport_pc)
jepler: I increased my period to 10ms just to see if that was it - same deal.
skunkworks: OK that's not very surprising
I should have this computer up pretty quick here - your help did the trick
jepler: seems to work just fine on this 450mhz computer.
skunkwork1: reading the encoders works, you mean?
well that's interesting
gives me one number counts as expected
velocity did the same on the portable aso
velocity is just calculated by (counts - old_counts) / time
if counts is bogus, velocity will be bogus
not entirely "duh" -- there are smarter ways which give better velocity estimates
I ment duh as I should have thought of that
This is cool. - what would velosity be with no scaling?
counts per second?
yes, I think that's right
I should go get a drill and see how fast I can spin it ;)
So I wonder what is wrong with my portable.
hard to say
could be a bug in pluto that most machines don't trigger
or it could be my portable ;)
I will update to the latest emc2 and try for shits and giggle
this is cool - I can flick it with my finger as fast as I can and it seems to go right back to 0 at the correct spot
its like it works or something ;)
jepler: seems to be rotation per second about?
btw - did you know you can have more than 1 halmeters running ;)
again - cool
skunkwork1: I usually run 4-5 of them
if I'm too lazy to start halscope
I thouhgt - boy it would be nice to have encoder velocity and posision at the same time ;)
scaling works - I can make it so 1 rotaion is a unit. (inch) but I am not understanding velocity now it reads .000something when I am turning it.
skunkworks: if you make 1 rotation be a unit, the velocity should be in rotations per second. .000something seems too low
that is what I thought - if I set the encoder scale to 4096 - position is 1 for one rotation but then velocity is .000something spinning it by hand.
with no scale it runs in the 1-10 or so
(spinning it by hand)
maybe I forgot to include the period in the velocity calculation
encoder_0_velocity = (count - data.last_count) / encoder_0_scale;
skunkworks: you could load a 'ddt' and calculate the velocity yourself by linking position to ddt.0.in
not an issue right now - just playing.
no period? (looking at your code)
do you want to try a patch?
* skunkworks like being a guinie pig
[19:21:36] <jepler> http://emergent.unpy.net/-files/sandbox/pluto-velocity.patch
[19:21:57] <jepler> http://emergent.unpy.net/files/sandbox/pluto-velocity.patch
cool - it will be a bit.
looks like the patch is wrong anyway
should be "fperiod" instead of "period_ns" whereever it appears
skunkworks: aww gee the motor's not very big is it
that is just the encoder...
it is not mounted to anything yet :)
skunkworks: oh -- in that case, I take it all back
good night all
I had updated to 2.1 on my portable and got a fresh checkout for rip.. Same thing. (just trying things)
skunkworks: it's not the best idea to say "same thing" when debugging something
skunkworks: did you try the velocity patch on the machine that was working OK for position?
How do you apply the patch automatically?
patch -p1 < file.patch
the number in '-p1' says how many levels of directory to strip off the patch
in this case, you want to be in src/hal/drivers and use -p0, I think
I will give it a try
I usually try with p0, and if that doesn't work p1 does the trick usually
alex_joni: wern't you going to bed a while ago?
I am in bed
:) I do the same thing - also in the bathroom ;)
jepler: what was that link?
[21:09:42] <alex_joni> http://emergent.unpy.net/files/sandbox/pluto-velocity.patch
patch -p1 < file.patch
patch -p0 < pluto-velocity.patch
jepler: now when I run it - the led doesn't flash anymore. just goes out.
(was sending a sin wave to pwm0
when I quit halcmp - the led is dim again
and I get nothing from the encoder.
skunkworks: well that means the patch was probably wrong
'patch' again and when it asks you if you want to reverse the patch say yes
I'll look at velocity when I hook up my pluto this weekend
off to sleep now, night all (again)
see you alex
jepler: reboot fixed it - the velocity seems right now - if I rotate it about 1 rps it reads about 1 - cool
if that happens again, check in dmesg for a message
if you want to know - I undid the patch and forgot to 'make' it. so when it did it didn't work again - I rebooted. then it worked. I then remembered I never compiled the undoing of the patch.
if that made sense
yes, it does