#emc-devel | Logs for 2008-12-07

[00:48:21] <CIA-42> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/classic_ladder.lyx: add modbus options
[01:31:08] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/ (5 files): add 10 internal error bit variables %E, %E0 is for MODBUS com errors
[02:51:19] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/projects_examples/modbus_rtu_serial.clp: change project example to work with new modbus routines
[03:15:15] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/classicladder.c: fix compile warning
[03:45:18] <CIA-42> EMC: 03cradek 07TRUNK * 10emc2/bin/.cvsignore: new file
[03:46:11] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/classicladder.h: cleanup old defines
[03:48:17] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/vars_access.c: oops forgot to offset for other bit variables
[04:00:58] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/ccomp/mill-zchanges/expected: rebase concave_comp branch
[04:00:58] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/ccomp/mill-g90g91g92/expected: rebase concave_comp branch
[04:01:05] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/src/emc/sai/saicanon.cc: rebase concave_comp branch
[04:01:05] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/interp/flowsnake/expected: rebase concave_comp branch
[04:01:06] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/interp/cam-nisley/expected: rebase concave_comp branch
[04:01:06] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/oword/sub.0/expected: rebase concave_comp branch
[04:01:13] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/src/emc/rs274ngc/ (interp_convert.cc rs274ngc.hh): rebase concave_comp branch
[04:01:13] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/ccomp/mill-line-arc-entry/expected: rebase concave_comp branch
[04:01:21] <CIA-42> EMC: 03cradek 07concave_comp2 * 10emc2/tests/ccomp/lathe-comp/expected: rebase concave_comp branch
[04:07:18] <cradek> poor CIA-42
[04:10:21] <SWPadnos> at least it wasn't kicked from an excess flood :)
[04:11:01] <cradek> yeah I bet it knows just how fast it can talk.
[04:11:56] <SWPadnos> oh funny. I didn't catch that it was you doing all those - I thought it was still cmorley
[04:12:03] <SWPadnos> starts with c, about the same length ...
[04:17:47] <SWPadnos> huh. interesting "issue" with hal_input
[04:18:04] <SWPadnos> I have a device which provides multiple usb endpoints, but they all have the same name
[04:19:06] <SWPadnos> http://pastebin.ca/1278504
[04:19:42] <SWPadnos> unfortunately, you can't use the same name twice with hal_input (in exclusive mode anyway)
[04:19:54] <SWPadnos> since it will always find the first device and try to re-use it
[04:20:23] <SWPadnos> I can do it by number, but that's dependent on whether I ever plug in a USB thumb drive or whatever
[04:20:41] <cradek> yuck.
[04:20:46] <SWPadnos> yeah
[04:21:00] <SWPadnos> I guess I can see a few options here
[04:21:28] <SWPadnos> 1) add an option so that the inputspec will only match certain types of device (I don't think this is what KRAL do now)
[04:21:51] <SWPadnos> 2) make it use all matching devices isntead of the first one found
[04:22:15] <SWPadnos> 3) add a number to the input spec (+Nostromo 2 = second one ...)
[04:22:31] <SWPadnos> 4) ignore devices hal_input is already using when scanning
[04:23:25] <SWPadnos> (or possibly any in-use devices - just look for a matching device that can be opened, and fail if there are none)
[04:25:50] <SWPadnos> ok, option 2 is bad. what if you add a second mouse (of the same type as the system mouse) for jogging?
[04:25:58] <SWPadnos> (dumb, but possible)
[05:05:09] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/classicladder.h: fix define for added error variables
[05:08:03] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/classicladder_gtk.c: Add a message window to display %E variable controlled errors with out grabing focus classicladder_gtk.h
[05:09:46] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/protocol_modbus_master.c: add a error call from a MODBUS communication failue
[05:10:23] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/classicladder_gtk.h: Add a message window to display %E variable controlled errors with out grabing focus
[06:55:45] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/zEMC_README.txt: update
[08:11:13] <CIA-42> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/config_gtk.c: noticed I had the MODBUS function names mixed up
[15:29:31] <jepler> SWPadnos: interesting issue
[15:39:53] <jepler> $ hal_input x
[15:39:53] <jepler> No input devices could be opened. This usually indicates a misconfigured
[15:39:53] <jepler> system. Please read the section 'PERMISSIONS AND UDEV' in the hal_input
[15:39:53] <jepler> manpage
[15:39:58] <jepler> ^^^ this would be an improvement
[16:12:14] <jepler> SWPadnos: let me know if this addresses your situation: http://emergent.unpy.net/index.cgi-files/sandbox/hal-input-multidevice-etc.patch
[16:12:22] <jepler> if so I'll check it in (or you can if you like)
[16:32:34] <jepler> bbl
[17:31:47] <cradek> I was stupid to add X tool offsets but not Y. I didn't have a plan for having them in the tool table, but I could have done everything but the tool table.
[18:01:33] <micges> what about tool table in 2.3 ? will be automatic like var file ?
[18:27:42] <Roguish_> Roguish_ is now known as Roguish
[18:31:28] <jepler> the tool table and the variable file should only be written by executing gcodes. that way, the interpreter is always aware of all changes to the parameters and tools without special tricks to make it re-read external files
[18:31:37] <jepler> G10 L2, G10 L1, G92, #xxx=
[19:52:10] <SWPadnos> jepler, I tried to apply that patch/diff, but I coundlt figure out the right incantation in 5 minutes of trying
[19:52:43] <SWPadnos> maybe less than 5 minutes
[19:57:04] <jepler> patch -p0 from the top directory, probably?
[19:57:20] <SWPadnos> hmmm. lemme try that. it looked like it needed p1 or p2
[19:57:51] <SWPadnos> err. thanks :)
[19:58:21] <SWPadnos> I've been working on command-lione completion for halcmd, and it's a PITA
[19:59:10] <SWPadnos> I have the -C option workling, but I don't see how to differentiate between "halcmd -C show p" and "halcmd -C show pin "
[19:59:40] <SWPadnos> since there's no way to tell whether argv[argc-1] is incomplete or not
[20:00:00] <jepler> give it an empty argument
[20:00:11] <jepler> argv = ['halcmd'
[20:00:14] <jepler> , 'show', 'p']
[20:00:20] <jepler> vs ['halcmd', 'show', 'pin', '']
[20:00:41] <jepler> you're working on allowing the completion to be done from bash? very cool, if you can get it to work
[20:00:57] <jepler> anyway, that's how I remember thinking I'd thought around that problem
[20:01:31] <SWPadnos> oh wait - those are fine
[20:01:39] <SWPadnos> it's the case of "halcmd -C show "
[20:01:56] <SWPadnos> there's no way to tell if there's supposed to be a space after "show"
[20:02:14] <SWPadnos> ie, am I trying to complete the word show, or get the possible options for the command "show"
[20:03:14] <SWPadnos> the way to do it is to make a completion script (_halcmd or something) that gets the completion array from bash
[20:04:09] <SWPadnos> since there's a separate variable that holds the item to be completed (which I believe is empty if it's looking for an additional word)
[20:09:26] <SWPadnos> jepler, yay, it worked! thanks
[20:09:33] <SWPadnos> (the hal_input thing)
[20:20:25] <CIA-42> EMC: 03swpadnos 07TRUNK * 10emc2/lib/python/linux_event.py: from jepler: allow use of multiple input devices with the same name spec
[20:20:28] <CIA-42> EMC: 03swpadnos 07TRUNK * 10emc2/src/hal/user_comps/hal_input.py: from jepler: allow use of multiple input devices with the same name spec
[20:20:28] <CIA-42> EMC: 03swpadnos 07TRUNK * 10emc2/docs/man/man1/hal_input.1: from jepler: allow use of multiple input devices with the same name spec
[22:49:31] <davidma> hello. i've been using emc for a couple years and i'm interested in joining the development team. what sort of stuff would you need help with?
[22:50:40] <BigJohnT> what are you good at?
[22:51:57] <davidma> C, C++, python. EE background, so I had a couple control systems classes.
[22:52:26] <BigJohnT> cool
[22:52:34] <SWPadnos> hi
[22:52:45] <davidma> oh, and some machining classes at the local trade school. converted a harbor freight 47158 to CNC, etc.
[22:52:56] <SWPadnos> there are a couple of pages on the wiki (which probably need editing) with "wish lists"
[22:53:08] <davidma> swpadnos: i'll check out the wish list.
[22:53:17] <BigJohnT> I was just looking for them :)
[22:53:25] <SWPadnos> if there's something you don't like, you could also fix/change it and submit a patch to one of the developers
[22:53:30] <SWPadnos> check under the fest pages
[22:53:33] <davidma> i probably should start by getting an up-to-date dev environment set up at home. up to now i have just been a user of live CDs, BDI installs, etc.
[22:53:40] <SWPadnos> I think we all listed what things we wanted to work on
[22:53:47] <SWPadnos> (not that it did any good ;) )
[22:54:07] <SWPadnos> apt-get build-dep emc2 should be about all you need
[22:54:11] <SWPadnos> oh, and apt-get install cvs
[22:54:16] <BigJohnT> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?EMC_Fest_2008
[22:54:28] <SWPadnos> yep, that's one of them :)
[22:54:38] <BigJohnT> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?CVS
[22:54:52] <fenn> i think there was need for a release manager for the next package release
[22:54:54] <SWPadnos> the ones from prior years may also have things, and there are other pages with requested features I think
[22:54:55] <davidma> swpadnos - what's the distro I should start with? ubuntu I assume from browsing various pages.
[22:55:08] <fenn> (but maybe that's biting off too much for start)
[22:55:08] <SWPadnos> I'd get the EMC2 Ubuntu LiveCD from linuxcnc.org
[22:55:14] <SWPadnos> fenn, yes, it is ;)
[22:55:22] <davidma> swpadnos: got it.
[22:55:57] <BigJohnT> the follow the instructions on the cvs page I linked
[22:56:12] <SWPadnos> from there, you can install the build-deps and miscellaneous other tools you may want for a dev system
[22:57:21] <davidma> thanks. one thing i have not done yet which would probably be interesting is to start from a basic distribution, and rebuild the kernel with RTLinux modules, etc. is that worthwhile or no?
[22:57:55] <SWPadnos> if you want to learn about it, then it's useful
[22:58:07] <SWPadnos> but it can be a lot of work for little gain
[22:58:11] <BigJohnT> ahh here is the page I was looking for http://www.linuxcnc.org/content/view/50/13/
[22:58:26] <davidma> bigjohn: thanks.
[22:58:40] <SWPadnos> you can always rebuild your own RT kernels on the Ubuntu distro as well, but you'll have the distributed one to fall back on
[22:58:43] <fenn> davidma: fyi RTLinux is not used anymore, only RTAI
[22:59:09] <SWPadnos> oh yeah - good point. RTLinux should still work, but it may have bit-rotted somewhat
[22:59:18] <fenn> it was abandoned due to commercial greediness issues
[22:59:29] <davidma> i'm dating myself somewhat - my first EMC was the old BDI install.
[22:59:34] <davidma> 2001-2002 era.
[22:59:42] <fenn> me too
[22:59:42] <SWPadnos> heh
[22:59:53] <davidma> i was first inspired by henry palonen's web pages.
[22:59:54] <SWPadnos> that's fairly early on :)
[22:59:56] <davidma> yty.net
[23:00:04] <SWPadnos> hmmm. haven't seen those
[23:01:04] <SWPadnos> ooooh - hey: http://www.yty.net/h/hpgl/
[23:01:18] <davidma> http://www.yty.net/cnc/
[23:01:37] <SWPadnos> the HPGL thing could be interesting for engraving/milling from drawings
[23:02:09] <fenn> hp2xx already outputs gcode
[23:02:15] <SWPadnos> oh, cool then
[23:05:10] <davidma> here's a video of my current set-up
[23:05:13] <davidma> http://video.google.com/videoplay?docid=-8492562273096564946&hl=en
[23:06:43] <SWPadnos> ooooh, somebody milling the AXIS splash screen :)
[23:06:48] <SWPadnos> cool that it works ;)
[23:09:30] <davidma> I originally started with a homemade board with some old allegro micro drivers. I could only get maybe 2 IPM with those before the steppers would start stuttering. I finally shelled out for a xylotex setup with some hefty motors and was excited at the speeds I could get, and so made a video.
[23:10:11] <davidma> I still want to wire up the 4th axis with a rotary table so I can make gears, etc.
[23:12:08] <SWPadnos> heh - all this talk makes me want to go out and hook stuff up to my Bridgeport
[23:12:16] <SWPadnos> but it's 20 degrees out and the garage isn't heated :)
[23:13:25] <davidma> kerosen!
[23:13:33] <SWPadnos> yeah, got one :)
[23:13:53] <SWPadnos> I just might do some more conversion this Christmas, if I can get some other stuff done first
[23:14:06] <davidma> i forget what kerosene was a few years back. definitely less than $4.50 the local filling station wants, or the $7 or so if you buy the 5 gallon can at lowe's or homer's
[23:14:06] <SWPadnos> I have about 100000 projects in process, and it shows
[23:14:15] <SWPadnos> (I can't see my office floor, for example)
[23:24:35] <BigJohnT> davidma: do you program gui's in c++?
[23:28:24] <fenn> BigJohnT: but why would anyone want to do that? :)
[23:28:32] <davidma> bigjohn: never have, but I could take a crack at it.
[23:28:40] <davidma> what widget set?
[23:29:13] <BigJohnT> ok, same question different way, what gui do you use with your c++ programs?
[23:29:27] <BigJohnT> glade, gtk+ qt ???
[23:29:33] <SWPadnos> heh
[23:29:42] <SWPadnos> that's a little like asking about which editor someone uses ;)
[23:29:54] <fenn> which way do you butter your bread?
[23:30:09] <fenn> either way it's going to fall butter side down and land on the cat
[23:30:10] <SWPadnos> fenn, top side only, why do you ask? :)
[23:30:16] <BigJohnT> left to right the back the other way
[23:35:53] <davidma> bigjohn: i played around a little bit with motif ages ago. that's about all the C++ gui coding I've done to date. but i'm willing to give it a shot if that part of the project needs people.
[23:36:20] <BigJohnT> no, I was just playing around with it
[23:36:21] <cradek> hm, either TLO_IS_ALONG_W or however it's spelled is not in the docs, or I missed it
[23:36:33] <cradek> looking here: http://www.linuxcnc.org/docs/devel/html/config_ini_config.html
[23:37:29] <BigJohnT> cradek: what is that?
[23:37:46] <SWPadnos> some config info for the last user list question, I think
[23:38:09] <cradek> [TRAJ]TLO_IS_ALONG_W moves tool length offset from Z to W
[23:38:25] <cradek> useful for a 5 axis machine or knee mill, for example
[23:39:02] <cradek> http://article.gmane.org/gmane.linux.distributions.emc.user/5863
[23:40:12] <SWPadnos> argh. this completion stuff is annoying
[23:42:45] <BigJohnT> is that in trunk only?
[23:42:58] <SWPadnos> which?
[23:43:06] <SWPadnos> TLO_ALONG_W?
[23:43:11] <BigJohnT> tlo is along w
[23:43:54] <SWPadnos> dunno
[23:45:37] <davidma> this is pretty cool (5 axis demo) http://www.youtube.com/watch?v=1EYaM4FkASA&NR=1
[23:47:59] <BigJohnT> is TLO_IS_ALONG_W = 1 the syntax?
[23:50:39] <jmkasunich> davidma: glad you like it
[23:50:48] <jmkasunich> that was cradek's mill, at the last CNC workshop
[23:57:53] <skunkworks> davidma: a bit bigger http://www.youtube.com/watch?v=35tHYaDUmZQ