#emc | Logs for 2007-04-06

[00:00:26] <eric_u> I don't really understand why host and client couldn't be more compatible with each other
[00:00:31] <SWPLinux> oops - gotta run. Hous of Prime Rib time!!
[00:00:34] <SWPLinux> Hous, even
[00:00:39] <SWPLinux> no, House!!!
[00:00:40] <SWPLinux> yay
[00:01:51] <toastydeath> HAUS
[00:01:59] <eric_u> unterhaus
[00:02:17] <toastydeath> tru
[00:19:11] <renesis> wooo found scanline combination that worked with crappy monitors
[00:43:32] <renesis> is ubuntu blackbox broken or something?
[00:59:35] <renesis> okay i figured it out it wants the menuFile line at the beginning of .blackboxrc
[00:59:42] <renesis> new blackbox is kinda lame...
[01:36:03] <CIA-19> 03cradek 07TRUNK * 10emc2/src/emc/task/emccanon.cc:
[01:36:03] <CIA-19> document petev's question about arc parameters, fix a wrong comment,
[01:36:03] <CIA-19> and undo some `indent' screwage
[01:44:36] <lerman_> lerman_ is now known as lerman
[01:47:07] <tomp> SWPlinux: re petev's suggestion... right on, i had thought about using .v (verilog) files in the same way. the advantage to either is: you put stuff where you want stuff and the 'wiring' follows, yet can be modified. either format can be parsed. good thinking petev!
[01:50:53] <jmkasunich> what suggestion is that?
[01:51:12] <jmkasunich> somebody suggested using geda for HAL stuff earlier today, was that pete?
[01:52:56] <tomp> jmkasunich: thats what i read, installing gschema and PCB now to look at the idea
[01:53:15] <jmkasunich> Its something thought about probably a year and a half ago
[01:53:26] <jmkasunich> just didn't have the time to run with it
[02:09:35] <tomp> oops, dont use synaptic to install gschem, you get only gschem :( with no manual :( instead use 'sudo apt-get install geda'
[02:10:08] <tomp> found symbol creation guide online http://www.vision.caltech.edu/bouguetj/ICCV98/index.html
[02:34:53] <eric_u> eric is not in the sudoers file. This incident will be reported.
[02:35:06] <eric_u> will I have to go to the principal's office
[02:35:25] <cradek> it really does mail root...
[02:35:38] <cradek> kind of silly when it's so easy to do that on the wrong machine
[02:36:15] <eric_u> what happens if root never reads his mail?
[02:36:34] <cradek> it builds up forever?
[02:36:43] <cradek> it will eventually fill the universe
[02:36:45] <eric_u> can you delete it without reading it?
[02:37:31] <eric_u> I've got some robots that have been getting mail from the cron jobs that run automatically for years now
[02:38:21] <eric_u> no yum package for geda apparently
[02:39:48] <crepincdotcom`> test
[02:42:12] <eric_u> how did crepinc do a test in between the time that he left and entered the room? spooky
[02:43:03] <jmkasunich> there is more than one of him
[02:43:12] <jmkasunich> see the ` at the end of his name
[02:43:27] <eric_u> tricksy
[02:53:56] <ejholmgren> * ejholmgren smacks root with a rolled up newspaper
[02:53:58] <ejholmgren> bad root
[04:03:00] <ds3> Stop smacking Mr Robert Oot!
[04:24:39] <tomp> built 1st component in gschema and saved to a library.
[04:24:49] <tomp> some local dot files (~/gEDA/gafrc) have to be manually created.
[04:24:56] <tomp> Symbol files have to be sudo cp'd into /usr/share/gEDA/sym/local.
[04:25:06] <tomp> There will be some discussion about appearances ( IEEE symbols dont seem applicable )
[04:25:12] <tomp> and elements like gain become pins connected to constants.
[04:25:15] <tomp> still lookin at all this, it's just like new components in CircuitMaker et al.
[04:25:44] <tomp> oops (~/.gEDA/gafrc)
[04:30:12] <tomp> http://imagebin.org/8012
[05:04:10] <petev> tomp, that doesn't look half bad
[05:04:34] <tomp> which half :)
[05:04:41] <petev> if you need some help with a netlist parser, let me know, I can probably make something up pretty quickly with ANTLR
[05:04:41] <SWPLinux> the other half ;)
[05:05:03] <ds3> hmmm
[05:05:07] <petev> SWPLinux, how does it feel to be on PST ?
[05:05:24] <SWPLinux> I looked at the text representation of a component (in the help files), and it doesn't look too nice
[05:05:33] <ds3> SWPLinux: when are you learning?
[05:05:37] <SWPLinux> petev: not bad, I usually keep west coast hours even when I'm on the east coast :)
[05:05:44] <SWPLinux> I'm learning all the time
[05:05:48] <ds3> leaving
[05:05:48] <ds3> bah
[05:05:51] <SWPLinux> heh
[05:05:56] <SWPLinux> I leave tomorrow morning
[05:06:05] <SWPLinux> packing as we speak
[05:06:08] <ds3> SJC?
[05:06:12] <ds3> or SFO?
[05:06:16] <SWPLinux> sjc
[05:06:30] <ds3> oh nice short shuttle ride
[05:06:52] <SWPLinux> no shutt;e from the Hilton, strangely - taxi for me
[05:06:59] <ds3> WHAT!?
[05:07:04] <SWPLinux> heh
[05:07:05] <ds3> you can take the light rail if you want it cheap
[05:07:21] <SWPLinux> nah - I'd rather get the extra sleep
[05:07:35] <SWPLinux> taxis are fast and on demand
[05:07:41] <ds3> heh
[05:08:48] <SWPLinux> and pretty cheap, unless your cell phone falls off in the back
[05:09:03] <ds3> cheap?! is probally a $30-$40 ride
[05:10:04] <SWPLinux> $13
[05:10:08] <SWPLinux> $15 with tip
[05:10:19] <SWPLinux> at least, that's what it was on the way here
[05:10:22] <SWPLinux> (SJC, remember?)
[05:10:26] <ds3> didn't think it is that close...
[05:10:32] <SWPLinux> 3 or 4 miles, I think
[05:10:34] <ds3> it is a 15min light rail ride....
[05:10:44] <SWPLinux> 6 or 8 in a cab
[05:11:46] <ds3> so you won any raffles this year?
[05:12:11] <SWPLinux> http://www.google.com/maps?q=300+S+Almaden+Blvd,+San+Jose,+California+95110,+USA&sa=X&oi=map&ct=title
[05:12:21] <SWPLinux> nope - didn't really enter any (or stick around for them)
[05:12:38] <SWPLinux> I did well enough last year, so I still average out OK
[05:12:46] <ds3> haha
[05:12:58] <ds3> so the paid talks don't have give away raffles?
[05:12:58] <SWPLinux> (512M ipod shuffle, 1G secure jumpdrive, 128M i-stick ...)
[05:13:00] <SWPLinux> heh
[05:13:18] <SWPLinux> no, but I did get permission to do limited distribution of a few of the papers
[05:13:28] <SWPLinux> not that that's really a prize or anything
[05:13:33] <ds3> haha
[05:13:44] <ds3> did you goto any of the prius stuff?
[05:14:07] <SWPLinux> no, I missed all that
[05:14:19] <SWPLinux> actually, the 3 talks I went to today were excellent
[05:14:53] <ds3> which ones?
[05:14:56] <SWPLinux> all by the same guy - one on memory-mapped I/O (and other things) in C++, one on C++ templates, and another on the behind-the-scenes stuff C++ does for things like virtual functions and stuff
[05:15:40] <ds3> got your money's worth?
[05:16:00] <SWPLinux> it's surprising, but in many cases, using templates (which people including me) think are the worst thing for bloat, are actually better sizewise than C
[05:16:03] <SWPLinux> yes, I think so
[05:16:34] <ds3> sure sounds like the paid track is very different from the free stuff
[05:16:46] <SWPLinux> there aren't enough advanced or "good intermediate" courses for my tastes, but there are always subjects where an introductory course is enough (VHDL, Verilog, control theory ...)
[05:16:51] <SWPLinux> absolutely
[05:17:00] <SWPLinux> you can get credit through UCSD for the paid stuff
[05:17:10] <ds3> but what's the credit good for?
[05:17:09] <SWPLinux> maybe I'll get a degree one day
[05:17:17] <SWPLinux> well, degrees ...
[05:17:23] <ds3> really? as in a MS?
[05:17:38] <SWPLinux> at least BS, and maybe MS - I didn't attend that session, unfortunately ;)
[05:17:50] <ds3> interesting.
[05:17:59] <SWPLinux> I can check it online, but I suspect that enough of the advanced courses might be good for an MS
[05:17:59] <SWPLinux> yes
[05:18:06] <SWPLinux> they just started that program this year
[05:18:16] <ds3> might do a paid track next year then
[05:18:36] <ds3> You do VHDL/Verilog?
[05:18:58] <SWPLinux> I usually scan the brochure and make sure that there are interesting things for around 1/2 the time slots or more
[05:19:05] <SWPLinux> yes, intro to each of them
[05:19:24] <ds3> what tools do you use?
[05:19:32] <SWPLinux> the verilog guy has a $12 intro book you can get on his website - he was pretty good
[05:19:37] <SWPLinux> I have Altium Designer
[05:19:50] <SWPLinux> so I use that plus the vendor tools for place+route
[05:19:56] <ds3> ouch... that's a powerful vacuum on the wallet!
[05:20:02] <SWPLinux> indeed
[05:20:21] <ds3> want to find someone that has used Icarus to see how good is it
[05:20:56] <SWPLinux> they seem to have a good philosophy though - I've gotten 7 updates (another is on the way in the next couple of months), and they don't charge until they do a new release (usually every 3 years or so)
[05:21:20] <SWPLinux> they've added features, improved compatibility with old file formats (!), fixed bugs ...
[05:21:34] <SWPLinux> the next release will also have their C-to-FPGA compiler
[05:21:43] <ds3> but is it reliable? their old Protel stuff was very crash prone
[05:21:50] <SWPLinux> (at no extr charge ...)
[05:22:14] <SWPLinux> I had Protel PCB 2.78 and Schematic 3.0x (yes, pre-99se)
[05:22:35] <SWPLinux> which I can now load files from, I'm very happy to say
[05:22:37] <ds3> one version of schematic was very crash prone
[05:22:48] <SWPLinux> it seems stable, but like all modern programs takes a long time to start up
[05:23:01] <ds3> oh hehe and not very Linux friendly either
[05:23:17] <SWPLinux> no, but it does work fine on VMWare
[05:23:32] <eric_u> checking your license
[05:23:37] <ds3> including the speed/performance aspects?
[05:23:38] <SWPLinux> and every chance I get, I ask for a Linux version :)
[05:23:57] <ds3> they pretty much chewed me out at the booth when I asked about a Linux version
[05:24:18] <SWPLinux> speed is of course slower than native, but I don't know by how much because my main Windows machine is an Athlon 1800 and my Linux machine with VMWare is a dual Opteron 275 :)
[05:24:35] <SWPLinux> I don't really see a slowdown ...
[05:39:34] <tomp> ok, the component pins in gEDA must be drawn in a certain direction ( else all the wires fall off when the component is moved ) http://imagebin.org/8013
[05:40:51] <petev> that seems a bit funny, you mean it can't figure out to put the red connection point away from the component?
[05:41:09] <SWPLinux> they are very explicit in the manual that the pin ends (the live ends) MUST!!! be on a 0.1 inch grid
[05:41:52] <tomp> yep all snapped to grid, but its the direction of the drag that make the little red end in or out
[05:42:00] <tomp> grid = 100
[05:42:07] <petev> look at the pics
[05:42:11] <SWPLinux> oh right - I was looking at the tet representation, to see if there might be some way of autogenerating components at build time
[05:42:19] <petev> it puts the connection end on the component if you draw it the wrong way
[05:42:29] <petev> that's just lame
[05:43:01] <SWPLinux> it seems to put the hotspot at the start of the line (at least I think that's what it was doing when I tried it out)
[05:43:12] <tomp> i wont do that wrong again , fortunately i could rotate and edit them then sudo cp them again...
[05:43:33] <tomp> now i gotta hand sketch all the comps we have
[05:43:35] <SWPLinux> mi = move flip (mirror)
[05:43:52] <tomp> yep, using the key cmds is the way to use it
[05:44:00] <SWPLinux> that's why I was thinking of autogenerating them ;)
[05:45:58] <tomp> autogen from what input? the .comp files?
[05:46:10] <petev> not all have .comp files
[05:46:15] <petev> some are C
[05:47:02] <SWPLinux> from pin parsing in the C files (possibly), and automatically from comp
[05:47:04] <petev> you might be able to load them and use halcmd api orsomething
[05:47:18] <SWPLinux> hmm. halcmd save symbol ...
[05:48:01] <SWPLinux> I didn't spend enough time trying to figure out the format, and I'm not sure quite where it's documented though (if it is)
[05:49:14] <ds3> is gEDA really useable yet?
[05:49:35] <petev> all we need it to do is draw a schematic and generate a netlist
[05:49:46] <SWPLinux> it doesn't look it to me, but then again ...
[05:50:01] <SWPLinux> we need the components to put on the schematic first
[05:50:08] <petev> true
[05:50:25] <ds3> think gEDA integrates with SPICE, right?
[05:50:28] <SWPLinux> I think the netlist format is OK (if it's anything like the old text ones for Tango or Protel)
[05:50:52] <SWPLinux> the component format is also text, so we should be able to generate components if we want
[05:50:54] <petev> does it only have one netlist format?
[05:51:00] <SWPLinux> dunno
[05:51:11] <SWPLinux> I played with it for about 20 minutes earlier today ;)
[05:51:35] <ds3> seems like eagle + LTspice is the best option AtM
[05:51:46] <SWPLinux> I was going to try to make a symbol for a HAL driver, and realized that the number of pins/params was larger than I wanted to deal with manually :)
[05:51:48] <petev> why do we need spice?
[05:51:58] <SWPLinux> Altium does OK for that
[05:51:58] <petev> we want to use it for graphical hal config
[05:52:09] <SWPLinux> simulate the machine ;)
[05:52:15] <petev> NOT
[05:52:18] <SWPLinux> heh
[05:52:39] <SWPLinux> just geta netlist from Mariss or Copley or whoever, and go
[05:53:19] <ds3> spice is nice for analog stuff
[05:53:30] <petev> it's a simulator
[05:53:40] <petev> it does mixed signal with digital as well
[05:54:12] <ds3> simulation is a good thing
[05:54:47] <petev> is the free eagle un-restricted enough to make a HAL config?
[05:54:55] <ds3> now if there is a usable clone of ProE; we should be able to simulate every aspect of a machine cheaply
[05:55:00] <tomp> i dont see any difference in pins and params when in gEDA, they both are pins, is that a problem? is pintype too limited? ( no numeric floats in electronics )
[05:55:30] <SWPLinux> petev: probably not, the sie limitation of 4x6 inches would probably kill you (though I'm not sure what the component limitations are in schematic, that's PCB ...)
[05:55:52] <ds3> if you can fit it in one page
[05:55:55] <SWPLinux> tomp: I thought about that, and don't have a solution
[05:56:21] <petev> I guess we can't get full type checking, but maybe we can do some
[05:56:30] <petev> what pin types does gEDA have?
[05:58:35] <tomp> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info (looking )
[05:59:11] <petev> so maybe we can use some of those to get some type checking in the schematic
[05:59:29] <petev> HAL will catch the rest when you load the config, same as now
[06:00:44] <SWPLinux> yeah - only drive types, not data types
[06:00:53] <tomp> what was the compliment program to PCB ( the tcl/tk app ) ?
[06:01:10] <tomp> it's schematic capture counterpart?
[06:01:37] <SWPLinux> gschem?
[06:01:47] <tomp> no, it was also tickle
[06:01:58] <SWPLinux> hmmm
[06:03:12] <tomp> never mind. it uses same symbol files... so same restrictions
[06:04:24] <tomp> xcircuit!
[06:05:31] <tomp> with embeded python interpreter , hmmm
[06:10:05] <SWPLinux> well guys, time for me to run. see you on the weekend (unless I have to do honey-do stuff the whole time :) )
[06:10:23] <tomp> have fun, thanks!
[06:10:33] <SWPLinux> thanks, I will :)
[06:10:33] <petev> this weekend is mountain bike and mill time
[06:10:35] <SWPLinux> heh
[06:10:37] <petev> have a good flight
[06:10:51] <SWPLinux> thanks - hav efun on the mountain (bike) :)
[06:20:59] <tomp> xcircuits 'subcircuit' feature is like meta-widgets ( make a collection of many hal components into a reusable component, yet keep the original primitives in tact )
[06:21:54] <petev> you mean like a heirarchical schematic library component?
[06:24:10] <tomp> yeh
[06:24:14] <tomp> macro
[06:25:41] <tomp> xcircuit has a user interface that must be blender's great grandfather ;) (2weird4words)
[07:02:24] <tomp> xcircuit is touchy about numlock. the menus work work at all if it's on!
[07:04:36] <tomp> nite all
[07:04:45] <petev> gn
[11:55:40] <lerneaen_hydra_> anyone here?
[11:58:48] <alex_joni> not me
[11:58:55] <lerneaen_hydra_> * lerneaen_hydra_ gasp
[12:00:19] <lerneaen_hydra_> http://lerneaenhydra.shacknet.nu/images/files_temp/img_6706.jpg <-- any idea why when I cut small threads the profile is all fscked up
[12:00:30] <lerneaen_hydra_> it's not 30 degrees from the normal
[12:00:45] <lerneaen_hydra_> more like 40/20
[12:00:49] <alex_joni> maybe the CAM output is all fscke up?
[12:01:00] <lerneaen_hydra_> no, the code is correct, at least I think so
[12:01:09] <alex_joni> try G76
[12:01:09] <lerneaen_hydra_> same Z values for the thread
[12:02:53] <lerneaen_hydra_> have you ever got threads like that?
[12:05:07] <alex_joni> nope.. I never threaded though
[12:05:11] <alex_joni> can you pastebin the code?
[12:05:50] <lerneaen_hydra_> http://pastebin.ca/426784
[12:05:54] <lerneaen_hydra_> oh, wait
[12:06:01] <lerneaen_hydra_> the Z coord is different
[12:06:16] <lerneaen_hydra_> the reason for that though is that the lead in is angled
[12:06:48] <alex_joni> so you have a screenshot from AXIS?
[12:07:00] <alex_joni> * alex_joni is at work..
[12:07:47] <lerneaen_hydra_> ah
[12:09:35] <lerneaen_hydra_> http://lerneaenhydra.shacknet.nu/images/files_temp/temp1.png
[12:18:38] <alex_joni> I somehow suspect the output from CAM is not right..
[12:18:51] <alex_joni> but you'd have to ask cradek later
[12:22:30] <cradek> what do you mean the profile?
[12:24:34] <cradek> you mean it doesn't look like a V?
[12:24:52] <alex_joni> cradek: the sides don't have the same angle
[12:25:07] <cradek> some of that is normal - you'll only see the V if you are seeing along a diameter
[12:25:22] <cradek> but maybe it's worse if the tool isn't on center (height)
[12:29:04] <alex_joni> cradek: seen the pic LH posted?
[12:29:09] <cradek> yes
[12:29:16] <alex_joni> ok..
[12:29:54] <cradek> I can't really etell if it's bogus or not
[12:30:49] <alex_joni> * alex_joni cusses at SF
[12:31:00] <alex_joni> my mail takes ages to get through
[12:31:19] <lerneaen_hydra_> cradek: they're not V even when looking straight on
[12:32:25] <cradek> lerneaen_hydra_: ok but there must be a V somewhere where your tool can sit? above or below centerline maybe?
[12:32:36] <lerneaen_hydra_> I'm not following you
[12:32:48] <lerneaen_hydra_> the tool is centered correctly
[12:32:57] <cradek> poke at it with the tip of the tool until you find the V?
[12:33:09] <lerneaen_hydra_> huh?
[12:33:10] <cradek> I mean the tool can only cut a V, so the V must be in the wrong place
[12:33:14] <cradek> haha
[12:33:17] <cradek> hard to explain
[12:33:24] <lerneaen_hydra_> most definetly
[12:33:30] <cradek> how carefully did you set the height of the tool?
[12:33:53] <lerneaen_hydra_> to within +-0.05mm
[12:34:02] <cradek> I might be wrong but I don't think this is a gcode problem
[12:34:04] <cradek> hmm
[12:34:07] <lerneaen_hydra_> the nub in the middle after planing is very, very minimal
[12:34:19] <cradek> did you get a lot of lifting of the work while threading?
[12:34:30] <lerneaen_hydra_> no, none that I could see
[12:34:54] <cradek> how many passes was this?
[12:34:57] <lerneaen_hydra_> I've actually had this problem often, it's most visible when cutting smaller threads
[12:35:00] <lerneaen_hydra_> 5-6 or so
[12:35:02] <lerneaen_hydra_> a 4-40 thread
[12:35:23] <lerneaen_hydra_> in brass, with a very sharp HSS tool
[12:35:25] <cradek> I don't see the passes - can you?
[12:35:47] <lerneaen_hydra_> err, how would you be able to see the passes?
[12:35:54] <cradek> I mean in the work
[12:36:05] <lerneaen_hydra_> oh, wait, what's a pass, the number of cuts needed to make the thread?
[12:36:19] <cradek> yes
[12:36:28] <lerneaen_hydra_> 5-6 or so
[12:36:34] <cradek> if the cam is wrong, you might see 5-6 steps on one side
[12:36:34] <lerneaen_hydra_> I think I had 5 cuts and a spring cut
[12:36:45] <cradek> if you can't see the steps, the final cut touched on both sides and HAS to be a V
[12:37:01] <lerneaen_hydra_> oh, the tool doesn't have flank-feed
[12:37:07] <lerneaen_hydra_> it feeds straight down
[12:37:10] <lerneaen_hydra_> constant volume
[12:37:28] <lerneaen_hydra_> yeah, that's exactly why I'm so confused
[12:37:38] <alex_joni> then it's a problem with your tool
[12:37:46] <alex_joni> imvho
[12:38:03] <cradek> have to get ready for work - bbl
[12:38:04] <lerneaen_hydra_> hmm, I've had this issue with both this tool and standard threading carbide cutters
[12:38:18] <lerneaen_hydra_> as well as triangular cutters
[13:10:19] <cradek> lerneaen_hydra_: wish I could see/touch it
[13:10:59] <cradek> lerneaen_hydra_: just for fun can you give us the program or an AXIS plot of it?
[13:14:48] <alex_joni> cradek: they are above
[13:14:55] <alex_joni> http://pastebin.ca/426784
[13:21:02] <alex_joni> * alex_joni heads home
[13:39:39] <lerneaen_hydra_> cradek: it may be a non-issue, depending on how you tilt the screw the artifacts go from non-existant to awful
[13:43:31] <cradek> lerneaen_hydra_: wait that's where I started! (it's normal)
[13:43:41] <cradek> does a nut screw on?
[13:44:19] <lerneaen_hydra_> yeah
[13:58:30] <cradek> lerneaen_hydra_: is your cam supposed to cut subsequent passes straight in, or offset along the thread in Z?
[13:59:39] <lerneaen_hydra_> uh, it cuts equally much on both sides of the cutter
[14:00:02] <lerneaen_hydra_> ie. the G33 move starts at the same Z coord
[14:00:15] <lerneaen_hydra_> different X values though of course
[14:11:18] <tomp> there is a python tool that converts structured text into gEDA symbols... http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html
[14:15:38] <cradek> lerneaen_hydra_: I think the gcode is wrong for that - the leadins would all have to be the same length for that to work, since spindle synchronization is at the start of the leadin
[14:17:29] <cradek> lerneaen_hydra_: but since the syncs all happen at the same place, later passes will be at different Z since they have to travel further to get to cutting depth
[14:18:39] <cradek> lerneaen_hydra_: oh maybe not! the Ks change
[14:19:58] <lerneaen_hydra_> cradek: I think that the gcode is correct, if not somewhat ugly
[14:21:26] <cradek> ok
[14:21:41] <cradek> I'd have to figure out the length of those leadin segments and compare it to K
[14:21:52] <cradek> too much trouble :-)
[14:23:27] <lerneaen_hydra_> yeah
[14:23:34] <lerneaen_hydra_> I did test a different version however
[14:23:46] <lerneaen_hydra_> with straight lead-ins
[14:24:15] <lerneaen_hydra_> same result, which leads me to believe that the thread is actually correct
[14:24:20] <cradek> for G76 I made sure the lengths of leadins were the same - changing K is an interesting strategy I didn't think of
[14:25:43] <lerneaen_hydra_> IMO a lead-in of constant length is better
[14:26:05] <lerneaen_hydra_> as if the total depth is very large then the change in K could take a while if accel is low
[14:26:30] <lerneaen_hydra_> then again, there's a change-of-dir accel too, but that won't affect the resulting pitch at least
[14:27:05] <cradek> threading without infinite acceleration is a juggling of compromises (like everything I guess)
[14:27:28] <lerneaen_hydra_> yeah
[14:29:10] <lerneaen_hydra_> lerneaen_hydra_ is now known as lerneaen_hydra
[14:37:08] <mschuhmacher_> mschuhmacher_ is now known as mschuhmacher
[15:25:48] <anonimasu> adcc
[16:54:53] <tomp> autogenerated hal component using gEDA and this howto http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html
[16:54:59] <tomp> src textfile is http://pastebin.ca/427115
[16:55:00] <tomp> result looks like http://pastebin.ca/427115
[16:57:35] <tomp> isnt really automatic, i still had to hand edit somethings. after a few of these, I'll decide if its just easier to hand edit a text file than to use the intermediate spreadsheet.
[17:20:21] <tomp> http://imagebin.org/8026
[18:30:44] <Martin_Lundstrom> Hello everyone
[18:31:08] <Martin_Lundstrom> Dallur: Are you around?
[19:21:51] <Jymmm> http://www.infoworld.com/article/07/04/06/HNjudgebarsvonage_1.html
[19:53:39] <robin_sz> meep?
[19:56:24] <alex_joni> beew
[19:56:33] <Rugludallur> bahh
[20:02:52] <alex_joni> ??
[20:04:15] <Rugludallur> !!
[20:04:42] <alex_joni> \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-
[20:23:49] <lerneaen_hydra> that's how much weed alex is going to use this easter
[20:24:02] <alex_joni> yay me
[20:24:11] <lerneaen_hydra> fun time
[20:33:20] <Jymmm> alex_joni he said weed, not canabis
[20:33:28] <Jymmm> boo you!
[20:38:45] <alex_joni> is there a difference/
[20:38:47] <alex_joni> ?
[20:39:03] <Jymmm> Yes, one you put weed killer on, the other you smoke =)
[20:39:18] <alex_joni> never tried any :P
[20:46:58] <Jymmm> Weed Killer is good stuff, you should try it sometime.
[20:47:52] <alex_joni> heh
[21:07:37] <lerman_> lerman_ is now known as lerman
[21:34:59] <lerman_> lerman_ is now known as lerman
[21:44:29] <alex_joni> g'night all
[21:44:36] <Jymmm> nite
[22:43:41] <robin_sz> bwahaha
[23:19:53] <Jymmm> fucking bullshit... I'm testing a new AV Sw, made a EICAR file, but xp is refusing access to it with the onyl dialog msg being "Access to C:\eicar.com was denied"