good lord it's bo&dick
he actually seems reasonably cluefull, just got stuck in a couple places
(that isn't the most intuitive datasheet I've ever seen)
ok, so I was wrong
[01:55:24] <cradek> http://timeguy.com/cradek-files/emc/PICT0082.JPG
[01:55:24] <cradek> http://timeguy.com/cradek-files/emc/PICT0083.JPG
^^ C axis
gonna use the time honored "piece of hose" coupling?
not sure. the other one has a solid coupling
alignment needs to be darn near perfect for that
well that was a design requirement :-)
if there is slop in your motor screws, you could loosen them, couple the shafts and let them align the motor, then tighten the motor screws
that only works if both shafts are also perfectly straight
right, I would tighten the coupling first, then everything else
the shaft is .2499. I have .2497 and .251 reamers
try the small one first
there are also tricks to make a reamer cut a bit big
like a wooden toothpick in the flutes
build to print, pound to fit, paint to match
I thought it was "measure with micrometer, mark with chalk, cut with chainsaw"
measure twice, cut once, measure a third time, cut it right the second time
assuming you didn't cut it too short the first time
just stretch it
cut a little back on
jmk-st: how's yours coming?
adding the SMI module solved the latency problem, so it back to metalwork
I thought you fixed that once before
mounting a molex connector to the plate that mounts the cabinet fan
then I'll mount the PC above that plate, and the PC supply can run the fan
the SMI? yeah, I did
but maybe the 151 updates, or the emc 2.2 update, broke it
steves_logging is now known as steve_stallings
steve_stallings is now known as steves_logging
Guest191 is now known as skunkworks_
cradek_ is now known as cradek
skunkworks_: did you see yesterday's photos of the C axis?
[15:09:55] <cradek> http://timeguy.com/cradek-files/emc/PICT0082.JPG
[15:09:57] <cradek> http://timeguy.com/cradek-files/emc/PICT0083.JPG
cradek: cool - yes I read back. Almost done :) how are you going to make the drive board?
I think I will make one just like the others
I haven't looked to see if I have all the parts yet. (I probably should have done that a few days ago)
it's sure nice now that I've fixed my vise. everything I do comes out square.
I want tool length sensing though! Drilling holes is a pain. spot drill, drill .010 under, drill actual size, counterbore. everything is a different length and I don't have enough holders/drill chucks to set lengths.
you need a lathe ...
err - well, conceptually, you need one. since you have one, that helps a lot
* cradek sends some coffee to SWPadnos
I have coffee, thank you :)
you can make tool holders with a lathe ...
uh-oh, you're still making no sense
I have two lathes named "too small" and "couldn't turn a correct taper to save its life"
too small is good - use the inaccurate one for roughing, and the small (and presumably reasonably accurate) one for finishing
I was very supprised you guys made the adaptor on your lathe at the cnc workshop
turned out great
skunkworks_: it's small but it's reasonably powerful and accurate
the small screws are a bonus for accuracy
or at least resolution :)
yeah it sure has resolution
I turned a reasonable taper with it to make my tool measuring fixture. I don't get blue throughout, but I do get it at both ends and in the middle
probably the best one can do without some kind of grinding
[17:12:02] <skunkworks_> http://www.cnczone.com/forums/showthread.php?t=48470
[17:12:16] <skunkworks_> http://www.cnczone.com/forums/showthread.php?t=48532
"When you change your steps per unit, you're also changing the rapid speed, even though it doesn't appear to change." -- wtf?
I read that.. scary. (assuming it is right)
hmmm. I know Mach has a few settings for "max step rate" (something like 25000, 35000, 45000 steps/sec), but I don't know if that directly sets the rapid rate
ie, max step rate / steps/unit = rapid speed
that's interesting. if the limiting factor is steps/second, as it often is on stepper machines, that keeps you from having to figure out units differences on your rotaries
you still need to set scaling
yes but how many degrees/second is the same step rate?
* SWPadnos goes for more coffee
it may make sense (but it's very stepper-centric)
mach is quite stepper-centric
it can do closed loop, if you have a galil card (which does closed-loop on its own)
so about gun control
it does this by outputting a series of velocities or positions, much like the EMC motion controller, and lets the Galil card do the work
re: gun control, see the Brady bill
I think gun control is either good or bad
I suppose it could be neutral
but it's much more likely to be good or bad
it's kind of funny actually. Vermont is one of just a couple of states (2 I think - VT and TX) that allows concealed weapons, and we have one of the lowest crime rates in the country
I'm not personally a hypocrite, but I think everyone *should* be one.
NE allows it I think
WI was trying to as is mn
I don't think you need a special license for concealed weapons vs. visible ones
I suspect that most states allow concealed weapons with a special license
my gun-rights-advocate coworker pointed out that the mall in omaha was a 'no concealed weapons' zone (as is much private property)
he wasn't quite bold enough to say that if it hadn't been, fewer people would have been killed because other shoppers would have shot the shooter
actually - I think you can in MN (the thing is every business/goverment building can opt out of it - posting a sign 'no consealed weapons') or something like that. So it makes it pretty worthless.
on a separate note, I finally found some conductive epoxy, so I can glue the rear defroster tab back on the glass instead of replacing the entire rear windshield
did anyone else notice that the words "shopper" and "shooter" look the same?
nice - way to change the subject ;)
which is good, because the glue/repair kit cost $20, and a used widnshield is $400, or a new one is $700
I'm immune to your subject-changing
SWPadnos: mine has a couple broken 'lines'... I wonder if I could use the same stuff
yes, the kit has conductive goo for the resistive strips as well
available at any auto parts store, in the section where they have the rear-view mirror glue
it's Permatex part number 09117
"Complete Rear Window Defogger Repair Kit"
thanks, maybe I'll try
unfortunately tinting is involved on my back window. It may not be accessible.
cut a little bit out (if it is film)
cradek: been updating this thread here http://www.cnczone.com/forums/showthread.php?t=47646
skunkworks_: yeah, if I can find the break
ah - i figured you kew
hmm maybe I should replace those 2MB photos then...
heh - I was going to scale it... but lost interest ;)
if you made it smaller - I would embbed it in the reply
o100 repeat 
does anyone but me think this would be nice?
yes, if there's no "for" loop already
why not a for loop?
this is almost always how I use while, but it's very tedious to do a counter and comparison
right, there is no for loop
yes, the "unnamed variable" would be nice
SWPadnos: I don't follow
ie, repeat creates an unnamed variable, which you don't explicitly need to decrement and compare
of course it's evaluated so you can do repeat[sqrt]
(rounds to int)
I already have it working, fwiw, I'm trying to decide whether to check it in
cradek: I am surprised you'd even write it
sure why not
I have a feeling that the "loop" construct that would be nice is one that mirrors the calculation of successive depths in a pecking configuration. It's not easy to get right.
e.g., cut down by 0.1" each time to 2.375"
good thing we have G83 (which is thankfully written in C)
is there a canned cycle that leaves the bit at the bottom of the hole?
yeah but you want the same kind of calculation in a pocketing routine that can't do the whole depth at once
a while loop seems fine for that kind of thing though
since you probably need to clip the last move a little
also, you need access to the loop variable within the loop, since it's the new depth
yes, you do
[17:49:12] <cradek> http://timeguy.com/cradek-files/emc/nested.png
ok now I've tested this 100%
does it properly catch errors like improper nesting?
ie, swap lines 6 and 7
same 10(?) levels as other calls/loops?
uh, it doesn't error, it does something strange instead
[17:51:21] <cradek> http://timeguy.com/cradek-files/emc/gigo.png
'cut down by 0.1" each time to 2.375"' will take 24 passes. I assume the current peck drilling cycle would do 23 with a depth increment of 0.1 and one with a depth increment of .075. Would it be acceptable if instead they were all an equal 0.9896?
no, because the user asked for 0.1
that's probably OK but it seems unnecessary to do that calculation
maybe it works for peck drilling, but say you are doing threadmilling or something..
the other question is whether it's better to do the oddball pass first, and then step down by the user-requested amount to the user-requested depth
if anything it's important that the first pass be the requested value
the first peck is the one where the drill centers itself etc. you don't want to screw it up
I guess pecking 0.001 might not be ideal, but then again it shouldn't hurt anything either
it could screw up your spot drill that you just did
that was another question I had -- if the total depth is 2.40001, should there be a .00001 pass after the last .1 pass?
not if it's < DEADBAND ;)
(which is actually very relevant because sum([0.1]*10) < 1.0))
you mean if it's less than one microstep
huh, if I write mismatched endwhiles, I also don't get an error
here come the geese!
(about two dozen just flew in, probably to hang out in the pond we have here next to the building)
isn't the pond frozen?
cradek: I would like to see repeat as an o word primitive... check it in unless you feel inspired enough to do a real "for loop"
skunkworks__ is now known as skunkworks_
EMC: 03cradek 07TRUNK * 10emc2/src/emc/rs274ngc/ (interp_read.cc interp_o_word.cc interp_internal.hh): repeat/endrepeat O words to make simple loops simpler than using while
seb_kuzminsky: please use lowercase directory and file names in cvs
okay - i'm used to bzr... sorry
you could make a new directory 'source' and I will remove 'SOURCE'
EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/ (7 files): initial commit of upstream files from Mesa Electronics
EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/SOURCE/ (6 files): initial checkin of upstream source for the eppio fpga firmware, from Mesa Electronics
seb_kuzminsky, I thought that was supposed to be in a lowercase directory name ;)
I can fix it
is that the stuff Luke uses?
EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/ (mesa7i43-gpio.h mesa7i43_gpio.comp Submakefile): new driver for the Mesa 7i43 FPGA board with EPP interface
swpadnos: i thought so too - i've got a "SOURCE" and a "source" dir locally, and i put the stuff in "source" and added it there
but I guess CVS think it knows better ;-)
anyone wanna have a revision control system flamewar? :-)
no thanks :)
let me fix it in the repository
thanks I'd appreciate that
then you will have to mess with your checkout until it's happy again
sorry for the hassle
when I did an update, I got a source directory
I'm not sure what you will have to do
i've used cvs extensively in the past, i think i can get it working here
if nothing else, deleting your entire mesa7i43-firmware directory and cvs up -dP will fix it
thanks for fixing the repo...
ok i'm all up to date over here. i'll try not to hose it again...
seb_kuzminsky: don't forget to add yourself to AUTHORS
seb_kuzminsky: and to add your changes to emc2/debian/changelog
seb_kuzminsky: hi btw ;) didn't get a chance to talk so far
hi alex, i'll do that
EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/rbf2h.py:
EMC: Make LGPL work, and a minor cosmetic fix for GPL.
EMC: (I discovered these when shamelessly stealing rbf2h.py for mesa7i43's
* fenn squints at the actual code-writing part of rbf2h.py
that's pretty neat
about the debian/changelog: looks like multimaintainer mode is off, is that intentional?
well.. I'm off to bed
good night all
see ya alex
EMC: 03seb 07TRUNK * 10emc2/debian/changelog: Added a note to the changelog about the new 7i43 driver, added myself to AUTHORS
EMC: 03seb 07TRUNK * 10emc2/docs/AUTHORS: Added a note to the changelog about the new 7i43 driver, added myself to AUTHORS
seb_kuzminsky: the mode where it puts [Your Name] above the change you are adding to debian/changelog? In my view, CVS preserves information about who made what change; the changelog is for public consumption and generally it is unimportant which developer made a particular bug fix or new feature -- all the user reading the changelog wants to know is what the differences *are*
jepler: that seems reasonable