argh! this gets aggravating!
ubuntu-lucid/drivers/usb/core/hcd.c:144: error: expected expression before '>>' token
patch gone wrong
I compiled this fine the other day and now it does this!
did you patch in between?
no, changed one measly little config option!
that's the kind of error you get when a patch doesn't quite work
what kernel version is that? 2.6.32.soemthing>?
I had this problem on Karmic as well, just when I created a branch. I redid everything on master and it worked fine.
then I tried making a branch again and it worked fine that time!
oh. the KERNEL_VER or KERNEL_REL may have spaces in them
somewhere in the make/config files
thanks. I'll take a look. right now I've got to go to the shop for a while. take some frustration out on some wood! :)
ever get that IO board working?
no, got side-tracked.
ah. happens to the best of us
or at least the rest of us :)
hopefully I'll work on it tonight (late)
SWPadnos: thanks for the tip about KERNEL_VER or KERNEL_REL.
that was what was on the line you mentioned :)
I had added -rtai to the version in the changelog, so I changed it to .rtai and it seems to be working
yeah, I had seen that before but I couldn't figure out anything. The mention of spaces made me think it could be my extension on the changlog version
does emc need rtai_shm?
it "might" work with rtai_shm compiled in, but during testing I found having it separate is a bit easier to test with
mozmck_work: hi, you looked for me last night?
err.. right, mozmck was it ;)
sorry.. was tired ..
EMC: 03micges 07joints_axes3 * r8bd148a74f5f 10/src/emc/motion/ (motion.c motion_debug.h usrmotintf.cc): Remove motion debug structure fields used to debug TP before HAL was introduced
alex_joni: re joints_axes3: I think that it should be possible to teleoperating jogging UVW axes
I want to merge master into ja3 and I wonder if it caouse flood of commit messages?
I don't think it will cause more than a few - do it and see :-)
cradek, did you see my e-mail about velocity calcs?
yes but I don't know the answer, sorry. looks like you are on the right track.
bbl, getting ready for work
EMC: 03micges 07joints_axes3 * r42e9d0b09c04 10/src/emc/motion/ (command.c control.c motion.c motion_debug.h): Rename coord mode trajectory planner structure according to new naming convention
I meant micges_work who timed out
EMC: 03micges 07joints_axes3 * r8b543dc77baf 10/ (334 files in 69 dirs): Merge branch 'master' into joints_axes3
hey alex_joni. That was in the morning here! I thought it would be daytime there.
emc compiled and ran without the rtai_shm module.
Ouch! a replacement tank for my way lube on the Hardinge cost $506
16:45 < mozmck> emc compiled and ran without the rtai_shm module.
for time reference
yay, the merge must have worked out
alex_joni: 8:44 here
I had to recompile the kernel with MODVERSIONS disabled to get it to run. It may be a regression in rtai magma
I thought that was in the RTAI building instructions - you had to disable MODVERSIONS before too
(our wiki page, not their instructions)
used to be, but not supposed to have to do that as of 3.7 I believe
I have done several kernels with MODVERSIONS using rtai 3.7.1 and 3.8 without any problem
cradek: merge was little complicated but I managed to solve all conflicts
I'm glad that it is one commit not ~300 :D
yep that's nice
wish you could come to cnc workshop in june
it would be cool
micges: have you been this side of the pond?
we could make huge progress in many areas
skunkworks_: I never travelled by plane yet
I like car driving better (but longer)
I do too
oh - well my first time was only a few years ago.. And it was a 7hour flight to ireland :)
skunkworks_: and how old are you?
oh so I have time :) I have 26
wait - 36
heh, I have that problem too
we could bring the puma - but I doubt if it will be anyway close to being something moveable.
The k&t is getting the focus.
we have all the drives we need - but we still have not looked to see if the encoders are quadature
how hard is it to increase the number of tools?
I remember it being defined somewhere - but I also remember there being an issue with a size limit between emc layers.
there is no longer a limit on tool numbers
do you mean pockets or tools?
well - We can have tool numbers up to 32767 (only 60 pockets)
oh - so if it is in the tool table - emc can pick it?
yes, no problem with any of those tool numbers
ok - for now - I am going with the tool chain finding the tool - vs emc knowing what pocket it is in.
if you want emc to keep track of what tool is in what pocket, though, you need 60 pockets
currently it looks like emc can deal with 56 pockets. you can increase it if you want.
(you would have to recompile)
ok, with your scheme, it doesn't matter and you can use any tool numbers you want.
this is going to be cool :)
and it looks like the idea of latching the fingers - then readin them on the rising edge of the prox/reseting on the falling edge is going to work also.
cool, that sounds like a very robust way of doing it.
so - it reads each tool - compares it to the tool prep number - then when if finds it - move ahead 2 pockets - clamp. (seems easy enough ;)
yep sounds simple. but I notice you can't just put the tools in order in adjacent pockets and have it work well - you'd need to interleave them 3 or 4 apart
which is kinda freaky
what do you mean?
oh - you mean evenly space all the tools around the chain?
yes if it uses up 3 pockets to find the tool and load it, you'd want to space them 3 apart or so
otherwise it would always have to make a complete circle
[16:10:07] <cradek> http://en.wikipedia.org/wiki/Interleave
gotta love "Writting Worst Case Pattrn."
the maching operations just need to be long enough that there is time for the chain to make a complete cycle ;)
true but my way is better!
of course! :)
you could always have it back up three before it searches again...
oh - interesting...
that would be a simple hack that would help a lot
that would require some plumbing.. (the hydraulics is only setup to run one dirction)
do you mean that would require tearing out some hydraulic crap and putting a motor there? :-)
well - that is one solution... We are always going to need hydraulics though...
pallet clamping, table rotation lift, gear shifting, counterbalance, tool change arm, pallet stations.
how long do you think until it moves and homes?
month (I hope)
depends on how much dad works on it. Hi dad! ;)
retirement has made him soft ;)
Hi cradek , Hi skunkworks
SWPadnos_ is now known as SWPadnos
Not adding an encoder to the tool chain drive sprocket?
KimK: not yet... I think it will work 'well' as it. (reading the rings)
KimK: did you see this?
[18:05:18] <skunkworks_> http://electronicsam.com/images/KandT/conversion/Toolreader.JPG
skunkworks: Yes, very impressive. But a good "comb" for chips and swarf, maybe? Are you sure you can't "observe" the tool chain instead in a more conventional manner? Just thinking out loud here.
hi skunkworks_'s dad
"The truth may be out there, but lies are inside your head."
no, some lies are pretty out-there
AIRPORTS: A place where people hurry up and wait.
-- From A Scientific Encyclopedia for the Enquiring Young Nome
by Angalo de Haberdasheri
KimK: I think air was blown thru the switch to clean the swarf off.
(atleast there was a connection.)
they are pretty hard to press.. I bet they would move the swarf out of the way
EMC: 03micges 07v2.4_branch * r4ca13e5d0674 10/src/emc/rs274ngc/rs274ngc_return.hh: Remove unused string after merge of tlo_all_axes
OK. Well, I was just thinking that if it knew that the next tool was in such-and-such pocket, it wouldn't have to search, just go there immediately. Do your pockets have a good place to put a pocket number?
KimK: we keep telling him and telling him that, but does he listen? no!
heh - I really am taking the easy way out at the moment.
although I think the way he wants to do it is cool too. you can just put the tools wherever. you can write their number on them with a sharpie and it'll stay the same forever. extremely simple.
why write a number?
I'm sure most in here read binary just fine
those look a little hard to read...
I need a biggish end mill - what's in the machine - ok there's one - it says 12345 on it
hmm.. get stricky without a reference
I do that all the time
Sure, hi-lo-lo-hi-hi... oops, I mean one-zero-zero-one-one...
but I have to count pockets - then look in the tool table and find the tool number for that pocket - then load the tool
anything over 4 bits and i get confused.
There is actually a little card from K&T that you would hold up to the rings to calculate the tool number. We need to find that agian.
skunkworks_: but at least you're used to it
you could keep your tool numbers in octal - might be a bit easier to read them.
you could also build a small hand reader
can't do hex unfortunately, since they have to be integers.
couple switches + led's, and a micro which displays the number
cradek: I 'think' that is how it was setup on the k&t - 5 sets of 3 rignts
yeah I can see how that'd be easy to read
Hey, maybe you could use one of those point-of-sale laser scanners?
alex_joni: we have another readhead..
skunkworks_: one that you can easily carry?
KimK: heh, that's a neat idea
so you'd have tools 00000 to 77777
right (I would have to look at the manual)
but going from that, you can just mill barcode on the holder
or numbers ;)
well one of those would be invalid, else you couldn't tell if a pocket is empty
heh - right
I vote for making tool 00000 empty, LOL. If tool 77777 (-37777 ?) was empty, well, that's just wrong.
interesting that if you ask for T00000 you could have the ladder say it's already there. you know the pocket right above the spindle is going to be empty
er, duh, no you don't
Sam, how many of those straight-shank toolholders do you have over there? Anything especially impressive? (6 inch indexable insert facemill maybe?)
And are most of the usual sizes some type of collet holders or more like weldon shanks?
we have probably 200 holders
mmm, mountain dew
heh - I don't drink it..
plus they would be easy to make...
strait shank tooling
EMC: 03micges 07v2.4_branch * r15b145450f4d 10/src/po/pl.po: Updated Polish translations
err should be small letter :P
yay for up-to-date translations
many peoples here asked for up-to-date translation, not shitty one like polish m.ch version
skunkworks: have you got a big tombstone fixture for it? If not, that should be your first project. Horizontal milling has some advantages.
KimK: this is the one we use a lot - we have some actual box ones also..
[19:53:24] <skunkworks_> http://www.electronicsam.com/images/KandT/DSCCurrent.JPG
horizontals are great for chip removal
that looks wobbly - not enough depth
well - we don't do heavy stuff on it. :)
but it is pretty solid
that was tapped with a floating tap holder. worked ok :) rigid tapping is cooler.
cradek: re emc bug report: that is strange: http://imagebin.ca/view/Ogncx2eT.html
running his program
micges: using 2.3.5?
err.. right, can't read :/
micges: inconsistent accel being applied?
inconsistent blending more likely
I think blending conditions
from the picture those look like line-arcs to me
is it arc or lots of lines?
* alex_joni kinda remembers micges touch line-arc blending lately
I'd try before that fix
here it was 2.4 branch, but even after make clean Axis displays wrong emc version
so long before blending patch
micges: is g64 Pxx set?
building 2.3 for tests
it was run emc -> homing -> load program -> run
no G64 in ngc
ah - ./configure after make clean fixes Axis dispalyed version
one thing: in 2.4 branch tool was not visible on Axis preview, in 2.3 it is
no G64 means max blending
so it depends on the segment size
I bet some of those lines are shorter, some longer
on the shorter lines blending will be more exact
that makes sense
it has to touch each segment - but if the segment is long - the blend will be bigger - if accel is low reletively
alex_joni: you're right
sometimes I still am
so for now no clue what it was
I've got few such incorrect path errors like (it was like some vecotrs was skipped) but I was unable to reproduce them :|
here problem was solved by adding G4 P0.001 after few G1 lines, but no idea why :|
maybe those two problems are related