14:07:02 <paul_c>  Any thoughts on how we can get the "registered" developers more involved ?
14:09:11 <SteveStallings>  How well is it known that EMC2 is now "runnable". More folks might get going, at least on I/O stuff, if they realized that a working platform exists.
14:09:24 <rayh>  Several are there for emc2.  I believe that they are following the development by testing.
14:12:38 <rayh>  There is a lot to learn before a body begins to write serious code.
14:12:56 <danfalck>  where is the emc2 download located?
14:13:47 <paul_c>  cvs @ Sourceforge
14:13:52 <paul_c>  checkout the emc2 module
14:17:11 <les>  was just looking at emcsegmot.c cvs
14:17:33 <les>  I don't think the minFerror bug was fixed there
14:17:53 <paul_c>  That is quite possible...
14:17:55 <les>  making it fabs()
14:18:16 <les>  but it was fixed in emcmot.c?
14:18:53 <paul_c>  To be quite honest, having three (or more) variations of emcmot.c makes it hard to keep them all in sync
14:19:02 <les>  for sure
14:19:26 <paul_c>  It would help if common code was split out...
14:19:45 <paul_c>  so that fixes in one would be seen in all the others.
14:20:15 <les>  for the time being I am just going to try to untar what I have...do the fix, and tar it back
14:21:46 <les>  always get garbage when I try to just ./compile
14:22:03 <les>  but thr BDI make thing always works
14:23:46 <paul_c>  see 26th July 2004 mail to the emc-commit list for the fix
14:26:25 <les>  ok
14:48:05 <les>  I see your fix for following error on line 3430 in emcmot.c
14:50:03 <les>  Actually I did fabs(emcmotDebug->jointVel[axis])...you fabs() the whole expression. Either should work though.
14:50:40 <les>  I will test this on the machine and report back,
14:38:15 <rayh>  I'm surprised at the additions and changes to emc.  Just updated my copy of the repository.
14:39:20 <paul_c>  when was the last time you did an update ?
14:39:40 <rayh>  'bout a week ago.
14:40:13 <paul_c>  emc hasn't changed... emc2 has had a few commits.
14:41:02 <rayh>  Oh.  /emc.run/1.10/Mon Aug  9 14:43:19 2004//
14:41:21 <rayh>  Several others in there as well.
14:42:20 <rayh>  I count nine changes in emc/src/emcmot as well.
14:42:44 <rayh>  Unless I'm reading things wrong.
14:44:40 <rayh>  I see an issue with the additions of univpwm.ini and univstep.ini.  They were made from version 1.1 of emc,ini and are missing all of the stuff that has been added more recently.
14:45:39 <rayh>  Individual axis vel and accel and step and hold times. The units stuff is all missing.
14:45:45 <paul_c>  there were a number of changes at the end of August with Jon's ppmc driver code
14:46:24 <rayh>  Sept 12 I see.
14:47:00 <rayh>  Must not be seeing right.
14:47:45 <paul_c>  The web cvs interface at SF shows when and what changed...
14:49:12 <rayh>  It looks to me like univstep.ini and univpwm.ini are nothing more than emc.ini tuned for a specific PC and machine.
14:49:55 <paul_c>  probably...
14:50:22 <paul_c>  Does Jon's board do setup and hold timings ?
14:50:43 <rayh>  Even the ; IO_BASE_ADDRESS   =    0xe000
14:50:44 <rayh>  is pci specific.
14:51:09 <rayh>  Doesn't matter if it does or not.
14:51:45 <rayh>  Seems like this stuff needs to be kept up to date with changes in the base code rather than forking.
14:52:16 <rayh>  A current version of jon's stuff would use individual axis vel and accel.
14:52:44 <rayh>  Servo stuff doesn't use setup or hold either.
14:54:02 <paul_c>  Just a couple of ini & run scripts along with comments about the options...
14:56:29 <rayh>  Just clutter and confusion.
14:56:58 <rayh>  Remember a few months back when generic wouldn't run the first time cause the generic.var file didn't match the new interpreter.
14:57:29 <paul_c>  must have been while I was up a mountain...
14:58:30 <rayh>  I believe that I set up generic for stepper and emc for servo and got both current.
15:00:48 <paul_c>  perhaps a post to the dev list asking if someone would like to take on the task of a cleanup ?
15:02:00 <rayh>  I see that Matt tried to bring lucas up to date last year.
15:02:19 <rayh>  There is a lot of clutter in there.
15:03:53 <paul_c>  Much of the run script could be pruned out
15:04:08 <rayh>  I suspect that several of the *.nml files will not run on a current system.
15:05:19 <paul_c>  Two samples of *.nml would suffice - one for local, and another for remote GUI's
15:05:56 <paul_c>  likewise, single samples of tool tables & *.var
15:07:22 <rayh>  lucas.var is identical to generic.var
15:07:54 <rayh>  But it we took it out, lucas.ini would fault.
15:08:17 <paul_c>  would imagine all the *.vars are the same...
15:09:31 <rayh>  minitetra has the offsets for the cable hex.
15:10:18 <paul_c>  offsets are in real world coordinates rather that strut lengths ?
15:11:57 <rayh>  I remember something about that.  We set joint homes at 20 something then offset for a world zero.
15:14:12 <rayh>  So how would we preserve individual or specific machine stuff without cluttering the emc directory?
15:15:16 <paul_c>  Add comments around machine specific variations
15:16:25 <rayh>  And put them in a separate directory?
15:17:46 <rayh>  I can see that even remove_realtime_base is getting dated.
15:19:44 <paul_c>  doesn't include adeos or rtai_hal in the module list
15:19:27 <rayh>  I can see why there is a desire to abandon emc in favor of emc2.
15:20:22 <rayh>  I noticed that a while back on Live and Knoppix both.
15:22:22 <paul_c>  the run scripts in emc2 are a little cleaner
15:24:55 <rayh>  Inflamitory statement follows -- I just hope that we are not using the same if/then/else/endif mindset in the design of 2
15:25:19 <paul_c>  for the run script ?
15:26:07 <rayh>  For handling multiple os versions.
15:26:24 <paul_c>  much of that has been removed.
15:26:56 <paul_c>  however, the remains are still pretty much the same.
15:27:25 <paul_c>  That needs to be looked at and overhauled at some point.
15:29:18 <paul_c>  Back to var files - We can add comments to one and they get ignored at run time.
15:30:01 <rayh>  We don't use any tickle stuff in 2 at the moment but when we do, we will need to add back in the cleanup stuff.
15:30:24 <paul_c>  emc2 uses tkemc
15:30:40 <rayh>  Any comments will kill the run in which that var is called and remove them during exit.
15:30:58 <rayh>  That happened with the new interpreter.
15:33:40 <rayh>  I see also in 2 a hard coded tkemc as the graphical interface.
15:33:53 <rayh>  This is a problem left over from emc as well.
15:33:55 <paul_c>  Added some random comments to generic.var and it is running fine
15:34:38 <rayh>  See if they persist.
15:34:53 <paul_c>  No they don't
15:35:50 <paul_c>  but is that really a problem ?
15:36:23 <rayh>  Only if a run version gets returned to a repository.
15:37:05 <paul_c>  but then that would also be a problem with ini files
15:37:13 <rayh>  Back in the old days, I'd add variables to the var with comments about what they did.
15:37:39 <rayh>  As soon as the new interp came along all of that went away.
15:38:06 <rayh>  No you can do anything you want with ini file comments.
15:38:22 <paul_c>  OK, so we need to look at the var_dump routines to see what changed.
15:39:14 <rayh>  Or just ignore it.  Would be nice to be able to add machine specific variables in there.
15:39:55 <rayh>  And be able to comment about what they are.
15:43:18 <rayh>  Nice if we could do something like 1000  2.1235 (x tool change position)
15:43:33 <rayh>  Or however they used to comment.
15:43:26 <paul_c>  Pity there isn't an easy way to make some of the files read only in CVS
15:44:11 <rayh>  Very true but the process to limit access is awkward, isn't it.
15:44:34 <paul_c>  on specific files, very.
15:45:21 <rayh>  My guess is that we need a general cleanup of the emc directory and a broadcast statement of the nature of files that should be placed in there.
15:45:44 <paul_c>  yup
15:46:03 <rayh>  At the same time we should allow for machine or project specific inis and runs and such someplace else.
15:46:42 <paul_c>  May even be possible to set a filter up so that any ini/var/run changes trigger a warning message to who ever did the commit
15:47:12 <rayh>  Can we do that?
15:47:36 <rayh>  and add in tbl and nml as well.
15:47:58 <paul_c>  would need to look into it and try it out here..
15:48:21 <rayh>  What might we name a directory below emc that would house this kind of stuff.
15:48:50 <rayh>  We have scripts.  Could we change the nature of it a bit.
15:48:50 <paul_c>  emc/sample_configs ?
15:49:08 <rayh>  Okay.  I'm easy.
15:50:02 <rayh>  How would just emc/configs be?
15:51:07 <rayh>  That's what we've got in emc2
15:51:36 <SteveStallings>  Paul, for your information.... as of the commits you did today, I can now get a clean compile of EMC2 again. Thanks. I am slowly moving toward using EMC2 to demo my products at shows.
15:53:33 <rayh>  paul_c:  Gotta get with the fam.  If I can get a few minutes I'll write a suggested cleanup for emc and post it to developers and see if I get someone who will help.
15:54:17 <paul_c>  OK and I'll look into cvs foo to see what can be done to limit future changes to the files
15:54:23 <paul_c>  in question.
15:54:50 <rayh>  Sounds like a bit of progress.
16:00:25 <SteveStallings>  Paul, would you like for the LinuxCNC web site to start promoting EMC2 as ready for alpha testing? Is it too soon to provide binaries for download?
16:02:06 <paul_c>  I'd be inclined to wait for a few days and ask John
16:02:12 <SteveStallings>  OK
16:02:27 <paul_c>  I'm probably not the best person to ask at the mo...
16:03:10 <paul_c>  One thing that was suggested yesterday though...
16:03:33 <paul_c>  A page of stuff made with EMC powered machines
16:03:34 <SteveStallings>  I am just hoping to shift some of the cleanup and other effort towards EMC2.
16:05:03 <SteveStallings>  I would be happy to provide a gallery of EMC implementations if people would provide photos, descriptions, and links.
16:05:18 <danfalck>  Steve, I added some more links last night.
16:05:35 <danfalck>  I just found Dean Hedin's page a moment ago.
16:05:48 <danfalck>  Added Les' page last night
16:06:16 <paul_c>  As the Documentation team start adding tags to the source code, I'd like to try setting up a web server here to host the doxygen stuff on
16:06:38 <paul_c>  and maybe crosslink from linuxcnc.org
16:12:28 <SteveStallings>  Let me know about the doxygen site when it is running. Recently at work I told my lead engineer to check out doxygen as a way to make sense of some code we turned over to a customer who hacked on it for five years and then wanted us to cleanup and enhance it. It took some formatting work, but doxygen helped him a lot.
16:12:38 <Imperator_>  is somebody testing EMC2 with servos ????
16:13:16 <paul_c>  Not yet - No drivers
16:13:26 <Imperator_>  Hello all, first
16:13:58 <SteveStallings>  Les - I see your links, but think we need a little work on organizing. High time we made a place for hardware that supports EMC.
16:16:55 <danfalck>  I've looked at some of the German EMC sites to gather more links
16:17:08 <les>  I kinda have the machining links buried a bit
16:18:08 <les>  let me see which link dan put on the site
16:19:33 <les>  oh ok that's the direct link
16:22:38 <les>  I could also supply pictures of emc made parts...signs, the encoder product line prototypes, test stations, and others
16:23:15 <danfalck>  That would be great.
16:23:49 <les>  Have some work this week using (gulp) .02" d endmill
16:23:56 <les>  looks kinda silly
16:25:20 <SteveStallings>  Just added "hardware" links category and moved a few others around a bit.
16:26:07 <danfalck>  It seems like about a year ago I asked for things that people were doing with EMC and got one response from David Munro
16:26:09 <SteveStallings>  Didn't Paul create another drivers besides Vital?
16:26:28 <paul_c>  Vigilant
16:26:39 <danfalck>  ok I'll check it out
16:26:43 <les>  Going to retro a Bridgeport with emc as soon as I find one close by
16:27:03 <les>  I will try to document that
16:27:49 <les>  Question: Does the Vital card work reliably for servo emc?
16:28:43 <les>  In other words has it been tested in a real cnc machine
16:28:49 <paul_c>  Dave Engvall would be the one to ask
16:29:10 <les>  ok will get in touch with him
16:29:13 <paul_c>  He has it running on a Mazak
16:29:22 <les>  oh good
16:30:09 *       paul_c needs to pull a finger or two out and get the lathe running
16:30:58 <SteveStallings>  Viligent Products added to hardware list. Thanks Paul.
16:31:31 <SteveStallings>  Vigilant
16:32:45 <danfalck>  Ok, I see it.
16:33:43 <danfalck>  I checked out "Tim's first part made with EMC" and all the photos are gone.  I will remove it.
16:35:53 <SteveStallings>  OK, but we do need to be careful with two of us editing as there is nothing to prevent us both from haveing a page "checked out" at the same time.
16:36:17 <SteveStallings>  having --- gee my spelling gets worse and worse
16:37:20 <danfalck>  Steve, go ahead and remove Tim's link. I'll hold off
16:38:52 <SteveStallings>  Done
16:40:17 <danfalck>  Steve, check this out:
16:40:23 <danfalck>  http://www.hedingrips.com/
16:40:47 <danfalck>  and:
16:40:50 <danfalck> http://users.pandora.be/engineering/index_files/page0001.html
16:48:02 <les>  I have had some email conversations with the latter
16:48:47 <les>  as for the first link...#$%# wish I had thought of that!
16:49:40 <les>  I end up with a lot of short cut-offs of exotic wood
16:50:35 <SteveStallings>  Added these two sites, but we should check back as they are both "buried" links.
16:55:04 <SteveStallings>  Weather is pretty here.... time for some yard work.
16:55:23 <les>  well i'm off...need to hit some little white dimpled balls in to the woods
16:55:31 <danfalck>  Same here... house painting. I will leave irc on to log.
18:43:13 <rayh>  Hi Paul.  Did we pretty well wrap up the emc directory stuff?
18:43:35 <paul_c>  I think we covered most of it.
18:43:57 <rayh>  Thanks for clearing up my thinking there.
18:44:23 <paul_c>  Have read up on the CVS stuff and I think we could trap commits of specific files and trigger an error message
18:44:54 <paul_c>  Would need to do some testing first though.
18:45:57 <rayh>  Ought we to leave emc.(run,ini,var,tbl,nml)  and generic.(run,ini) in the base emc directory?
18:47:16 <paul_c>  Yes - Just two basic sets along with the run script(s)
18:47:48 <paul_c>  emc.run (or generic.run) can be reduced to a few lines.
18:48:04 <rayh>  Along with the tickle config, axis comp, and rt install and remove.
18:48:21 <paul_c>  yes.
18:48:43 <rayh>  That cleans it up a lot.
18:53:12 <CIA-9> paul_c * emc2/configs/emc.ini: Comment about comments added
18:53:23 <paul_c>  And we have a new friend on this channel
18:53:43 <rayh>  Introduction?
18:53:54 <paul_c>  It will be a nice suprise for John when he gets back...
18:54:32 <paul_c>  CIA-9 is a bot with a feed from the SF commit messages
18:54:37 <rayh>  I'm all ears.
18:54:46 <paul_c>  and sends a notification to us on irc
18:55:09 <rayh>  Really.
18:55:11 <paul_c>  So each time a commit is made, we get a realtime notification here.
18:55:23 <rayh>  I gotta try this.
18:55:38 <paul_c>  Thought you might want to play ;-)
18:55:53 <paul_c>  pick a file, any file....
18:59:54 <rayh>  Gotta update documents and then change scratch.
19:04:10 <CIA-9> paul_c * emc2/src/emc/rs274ngc/rs274ngc_pre.cc: Small comment about splitting the files up
19:04:10 <paul_c>  incomming
19:04:27 <paul_c>  buggerme - That thing is fast...
19:04:46 <CIA-9> rayhenry * documents/scratch.txt: bot test
19:05:27 <paul_c>  That should add some incentive perhaps...
19:05:49 <rayh>  Yes it is.  That confirms my need for a full time connection.
19:06:11 <rayh>  Anyone got 156 miles of two conductor?
19:06:31 <paul_c>  Is cable (or isdn) viable in your neck of the woods ?
19:07:12 <rayh>  Nah.  Dish at $80 or so.
19:08:01 <paul_c>  Something for the squirrels to play on
19:08:20 <rayh>  Right.
19:08:43 <rayh>  Was naming it CIA your choice.
19:08:53 <paul_c>  nope
19:09:52 <paul_c>  http://cia.navi.cx
19:12:00 *       paul_c notes rayhenry@sf isn't on the commit list....
19:13:23 <paul_c>  Want me to add you while I'm bouncing messages ?
19:13:46 <rayh>  Certainly.  But I've been getting commit messages.
19:14:01 <rayh>  CIA is a nice project.
19:14:25 <paul_c>  You still need to register with your SF usr addy - A note was sent out last week...
19:14:49 <paul_c>  Added it anyway.
19:15:20 <rayh>  Note??  I seem to be missing things now and then.
19:15:27 <paul_c>  and checked the nomail box so that you don't commit notices twice.
19:16:01 <rayh>  I think that you are loosing me.
19:18:04 <paul_c>  Just forwarded a copy of the original notice to you
19:18:51 <paul_c>  The emc-commit list has you listed twice now. Once with your SF account, and again with the regular addy.
19:19:33 <paul_c>  On the SF entry, it is set so that you dont get any notices sent to that account.
19:21:38 <rayh>  I got it figured out now -- I think.
19:23:00 <paul_c>  Hopefully it will encourage the likes of JE to subscribe
19:23:21 <rayh>  I understand.
19:23:33 <rayh>  Hi Robin.
19:23:38 <robin_sz>  Hi Ray
19:25:11 <robin_sz>  so .. did I miss much?
19:26:42 <rayh>  Got here not long ago myself.
19:27:05 <rayh>  You building flame tables?
19:30:57 <robin_sz>  well ....
19:31:02 <robin_sz>  sort of ...
19:31:31 <robin_sz>  I'm wondering whether just laser cutting parts for people might be more profitable and a whole lot easier
19:34:53 <robin_sz>  I might go out to the factory in a bit and continue prepping the laser ... spent 3 days cleaning it up so far, it was filthy!!
19:35:33 <robin_sz>  note to previous owner: if yuo do insist on running it in a factory full of powder coating paint, ffs keep the lid closed.
19:37:34 <rayh>  Ah.  Laser table.
19:37:58 <robin_sz>  yep ... I sort of acquired another one.
19:38:08 <robin_sz>  the first is an EMC candidate I think
19:38:32 <robin_sz>  the second is fully fettled and ready to rock ... well, when I put it in position anyway
19:42:40 <robin_sz>  http://www.rapidcut.co.uk/images/LY2500.jpg
19:43:39 <robin_sz>  the controller on that one is a Bosch, quite nice, lots and lots of IO, but only about 100K of program memory
19:45:02 <robin_sz>  the other one I have is an EMC candidate I think ... awful controller using a 6502 and lots of TTL ... I thnk it works, but its poor, and destined to blow up at an inconvenient moment
19:46:02 <robin_sz>  also, I need to do "interesting" things with the laser I want to put on it .. so EMC is the baby for that I think
19:51:36 <rayh>  That should work.  It would be trivial with EMC.
19:52:41 <robin_sz>  and anyway ... EMC doesn't have aproblem with program memory ... we can have huge ones for minimal cost .. :)
19:52:55 *       robin_sz lurves PC based controls
19:53:04 <rayh>  What kinds of interesting things are you wanting to do with EMC control of a laser.
19:53:23 <robin_sz>  well, the laser I have has several control inputs ...
19:53:27 <robin_sz>  nothing weird there
19:53:32 <robin_sz>  standby,
19:53:38 <robin_sz>  pre-heat
19:53:44 <robin_sz>  shutter
19:53:46 <robin_sz>  and beam on
19:53:51 <robin_sz>  .. that bits easy
19:54:04 <robin_sz>  it also has an 8 bit digital command interface
19:54:26 <robin_sz>  set a new cmnd word and it spots that stuff has changed and does it ...
19:54:45 <robin_sz>  thats the bit that would be neat with EMC
19:55:33 <robin_sz>  the digital cmnd word sets things like pulse rate, duty cycle, power level and such
19:55:52 <rayh>  You could automate all of the controls and mix them right into g-code using M101+.
19:56:40 <robin_sz>  yep ... and write a nice custom driver to map the cmnd words to messages in emc
20:11:08 <danfalck>  Robin,  did you already have a lot of custom laser/plasma stuff worked out in EMC?
20:11:19 <robin_sz>  yes
20:11:49 <robin_sz>  2 basic areas.
20:11:59 <robin_sz>  no .. 3 basic ares
20:12:07 <robin_sz>  1) torch ignition
20:12:30 <robin_sz>  basically fire torch, wait x seconds
20:12:43 <robin_sz>  if you get an arc good signal then continue
20:13:34 <robin_sz>  if no signal in x seconds, then do something like stop program, note current line and X Y position, lift torch, come to table front position etc
20:14:01 <robin_sz>  2) tec table. basically like the tool table
20:14:52 <robin_sz>  but with things like pierce delay time, cutting speed, corner correction coeff., amperage etc for a whole list of materials
20:14:57 <robin_sz>  and finally ...
20:15:15 <robin_sz>  3) corner correction
20:15:27 <robin_sz>  plasma is a 'floppy tool' right?
20:15:32 <danfalck>  ok
20:15:43 <robin_sz>  you have to slow down on corners or they flare
20:16:00 <robin_sz>  as the bendy flame drags around the curve, lagging behind
20:16:47 <robin_sz>  so ... corner speed = programmed speed x ( coefficient x fn(radius) )
20:17:14 <robin_sz>  most or even close to all of that was all done ...
20:17:16 <robin_sz>  somewhere
20:17:41 <robin_sz>  but the structure of EMC1 drove me insane
20:18:00 <danfalck>  would emc2 be better?
20:18:04 <robin_sz>  I might port it to EMC2, as there are glints of sanity in it :)
20:18:43 <robin_sz>  I re-wrote the GUI as well, again , its not finished, but its about 80% done ..
20:19:42 <robin_sz>  ummm ... now where is that
20:19:54 <robin_sz>  ah ha! ... http://www.redpoint.org.uk/cgi-bin/cvsweb.cgi/tkemc/
20:20:05 <danfalck>  ok I'll check it out
20:20:24 <robin_sz>  its still in tcl
20:20:30 <robin_sz>  but more ... structured.
20:20:35 <robin_sz>  needs finishing
20:21:05 <robin_sz>  if you look in 'components' directory you'll get the idea
20:22:05 <danfalck>  I'll see if I can bring it up on a machine with working tk/tcl a bit later....
20:22:20 <danfalck>  I'm on a mac w/ os x right now.
20:22:25 <robin_sz>  I think it was left in a sort of working state
20:22:38 <robin_sz>  basically I was working to remove all the globals
20:22:41 <danfalck>  it surfs the net and plays music well....
20:22:47 <robin_sz>  of which there were 'undreds
20:23:25 <robin_sz>  and encapsulate each set of things as a component ... eg Axes displays
20:23:30 <robin_sz>  command buttons
20:23:31 <robin_sz>  etc
20:23:58 <robin_sz>  you then can build flexible generic GUI's from these components ratehr than a big, hardwired script
20:24:23 <robin_sz>  my key principle was that the GUI should still work with any component removed
20:25:18 <robin_sz>  so you could build a remote display by taking the standard GUI and removing the buttons component, and it should work just fine, without any mods to the code
20:25:33 <danfalck>  that would be good
20:25:45 <robin_sz>  thats about how far I got
20:26:05 <danfalck>  I played with Tkemc a bit a couple years ago
20:26:20 <danfalck>  but I am a bit slow
20:26:36 <danfalck>  and I broke a lot of things on my system
20:26:38 <robin_sz>  its the worlds worst language
20:26:41 <danfalck>  playing around
20:27:02 <robin_sz>  truly awful programming language ... I hate it muchly
20:27:11 <robin_sz>  but, it does its job .. just.
20:27:33 <robin_sz>  I'd prefer to get to grips with QT ... but thats a big learning curve
20:27:44 <danfalck>  kind of like a 2n op lathe next to the main machine...
20:28:08 <robin_sz>  yeah .. or in the office so you can monitor severla machines ...
20:28:23 *       paul_c decides to pull out a BDI-2.xx box...
20:29:09 <robin_sz>  it would be great for the OEMs
20:29:19 <robin_sz>  say you want a toolchanger
20:29:23 <robin_sz>  no problem
20:29:34 <robin_sz>  add a 'toolchanger' component to the GUI
20:29:44 <robin_sz>  slide it into the framework ...
20:29:58 <robin_sz>  it knows what messages to listen for coming up from emc
20:30:10 <robin_sz>  it knows what messages to send down to emc when you click button
20:30:51 <robin_sz>  it needs someone to finish it ...
20:30:56 <robin_sz>  Im crap at finishing
20:31:08 <robin_sz>  (so my wife tells me anyway ;)
20:31:17 <danfalck>  can I play with it?
20:31:21 <robin_sz>  sure ...
20:31:29 <danfalck>  thanks.
20:31:45 <robin_sz>  click the tarball or zip links ...
20:31:53 <robin_sz>  bottom of page
20:32:25 <danfalck>  ok
20:32:32 <danfalck>  got the tar file
20:37:15 <Imperator_>  hm, did anybody know if John joins also today ???
20:37:37 <Imperator_>  have some problems wirering my servo with EMC2
20:39:11 <Imperator_>  my driver for my motion control card works now, and i can see the encoder counting on the gui
20:39:13 <paul_c>  John is on his way back from Georgia
20:39:22 <robin_sz>  uh huh ...