Back
[01:47:33] <CIA-22> EMC: 03jmelson 07TRUNK * 10emc2/configs/univstep/univstep_load.hal: add components estop_latch and and2 to thread
[01:53:39] <SWPadnos> shouldn't he have actually connected those to something, or is that in the full file?
[01:54:10] <cradek> whatever it is, he needs to put it on the branch if he wants it released
[01:54:18] <SWPadnos> heh
[01:59:49] <cradek> hmm, I don't understand his change either
[01:59:56] <cradek> good thing it's jepler's problem :-)
[02:00:37] <SWPadnos> it's pretty obvious what he did, but not what he was supposed to do
[02:00:50] <cradek> right.
[02:00:50] <SWPadnos> not obvious - that could be what he was supposed to do
[02:02:50] <SWPadnos> ah - it looks like the connections were there already, but the loads were just missed
[02:06:36] <cradek> strange
[02:06:42] <cradek> are they in a thread?
[02:06:54] <SWPadnos> they are now
[02:07:22] <SWPadnos> hmmm - no, maybe they aren't
[02:25:32] <SWPadnos> I wonder if Stuart's servo thread time would be significantly reduced by (a) removing the extra DAC card (I think he doesn't need it), and (b) rearranging the order of daughtercards so the overall register map is optimized (if it isn't already)
[02:30:39] <cradek> uh on the machine that won't go over 90ipm?
[02:30:46] <SWPadnos> heh
[02:30:50] <SWPadnos> yes
[02:30:54] <SWPadnos> your point? ;)
[02:31:05] <cradek> ha
[02:31:18] <cradek> I suspect glaciers move at 90ipm
[02:31:36] <SWPadnos> 90IPY
[02:31:43] <SWPadnos> or possibly IPM
[02:32:02] <cradek> actually it would probably be fine if the "table" didn't have to move a block and a half
[02:32:12] <SWPadnos> yeah
[02:32:21] <SWPadnos> you should have seen the quill when it was extended
[02:32:27] <SWPadnos> man that thing is long
[02:32:48] <cradek> how long?
[02:32:55] <SWPadnos> 36"
[02:32:59] <cradek> wow
[02:33:03] <cradek> how big around is it?
[02:33:04] <SWPadnos> yeah
[02:33:12] <SWPadnos> 8-10" I think
[02:33:18] <cradek> jeez
[02:33:35] <SWPadnos> hmmm - maybe bigger. the taper had a couple of inches on either side
[02:33:55] <cradek> 50 taper's pretty darn big to start with
[02:34:05] <SWPadnos> yeah - about as big as max ;)
[02:34:10] <SWPadnos> oh - I should upload those photos
[02:34:10] <cradek> ha
[02:34:13] <cradek> oh yeah!
[03:23:57] <SWPadnos> finally uploading. it'll take a little while because I got lazy and copied everything
[03:43:37] <skunkworks> cradek: how was the birthday?
[04:14:17] <SWPadnos> well, I haven't made any nice index or anything, but the photos from Wichita (plus some of the big power supply I worked on, and the analog card) are online now
[04:14:29] <SWPadnos> http://www.willepadnos.net/photos/
[04:15:01] <SWPadnos> "Max Tool envy.JPG" is a good one :)
[11:18:56] <alex_joni> hmm.. latest 2.2.x from CVS, I get a lot of messages:
[11:19:07] <alex_joni> nomodifier 16 <function <lambda> at 0xb7d58cdc>
[11:20:02] <alex_joni> I get them printed in the console (I ran scripts/emc and selected sim/axis) when jogging with keyboard
[11:20:40] <alex_joni> I get different messages while jogging with "-"/"+"
[11:20:50] <alex_joni> nomodifier 16 <function jog_minus at 0xb7cc733c>
[11:20:50] <alex_joni> nomodifier 16 <function jog_plus at 0xb7cc7304>
[11:21:38] <alex_joni> (running dapper with python 2.4.3-0ubuntu6 installed)
[11:41:52] <alex_joni> jepler: anything serious about those messages?
[11:42:09] <alex_joni> they seem to be coming from AXIS on key events
[11:48:11] <jepler> hm I must have left a print in
[11:49:23] <CIA-22> EMC: 03jepler 07v2_2_branch * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: remove debugging message
[11:58:45] <alex_joni> cool, that fixes it
[17:46:53] <skunkworks> logger_dev: bookmark
[17:46:53] <skunkworks> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-03-15.txt
[18:26:12] <CIA-22> EMC: 03jmelson 07TRUNK * 10emc2/configs/univstep/univstep_load.hal: add threads for estop_latch and and2
[19:26:09] <CIA-22> EMC: 03cradek 07TRUNK * 10emc2/src/emc/kinematics/5axiskins.c: this is out of date. update from wtool branch
[20:28:21] <SWPadnos> too funny - when I load this file, zooming works backwards on text, and has no effect on the graphics:
http://wiki.linuxcnc.org/uploads/emcmot03.svg
[20:28:58] <SWPadnos> oh - no, it's the right direction, but the mouse wheel is inverted (silly me)
[20:51:23] <fenn__> fenn__ is now known as fenn
[21:21:40] <alex_joni> jepler: on a new install I noticed that python-tk isn't installed, yet configure doesn't catch that
[21:25:33] <alex_joni> whee.. it works :)
[21:25:45] <alex_joni> running emc2 on hardy .. sim only so far
[21:32:43] <alex_joni> uname -a
[21:32:46] <alex_joni> Linux dana-laptop 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
[23:33:42] <SWPadnos> hmmm. can anyone confirm that with EMC1, the io program had to be compiled for the particular hardware to be used?
[23:34:32] <SWPadnos> I see ppmcio as one option, but I don't see for example a vtiio - would the bridgeportio module just use a parallel port instead of any IO on the servo card (assuming there was any IO)
[23:34:34] <SWPadnos> ?
[23:37:24] <alex_joni> SWPadnos: I think that is the case
[23:37:34] <SWPadnos> ok, thanks
[23:37:37] <alex_joni> different io executables were put together based on the card used
[23:37:44] <alex_joni> I don't think all combos were in CVS though
[23:38:06] <SWPadnos> right, and task didn't do any direct manipulation, so only motion and io had to be hardware-specific
[23:38:42] <SWPadnos> io also having to be "machine" specific - ie, minimill vs. bridgeport functions, combined with the IO driver of choice
[23:38:58] <SWPadnos> (which might be the parport in lots of situations)
[23:39:42] <SWPadnos> and more advanced hardware usually having all the bridgeportio functions, since minimillio was there largely due to lack of pins :)
[23:40:39] <skunkworks> I vaugly remember the bridgeport setup used 2 printer ports
[23:40:45] <SWPadnos> yes
[23:41:10] <SWPadnos> I was just seeing that the vti.ini also uses brisgeportio, whereas ppmc.ini uses ppmcio
[23:41:58] <SWPadnos> err - vital.ini
[23:43:34] <SWPadnos> I guess I was wondering if there were a bunch of different bridgeportio executables, with different "drivers" built in, or if they were named differently for the different hardware - I think it's method 2 there
[23:46:57] <SWPadnos> one other question: anyone know what would happen if e.g. bridgeporttask and minimillio were used? just errors, or lube/spindle just wouldn't work?
[23:56:43] <alex_joni> no errors
[23:56:52] <SWPadnos> just no function?
[23:56:55] <alex_joni> yup
[23:57:00] <alex_joni> I used it the other way around
[23:57:04] <SWPadnos> ok, thanks (did you just check that? :) )
[23:57:20] <alex_joni> bridgeportio and the smaller task
[23:57:28] <alex_joni> was it minimilltask? can't remember
[23:57:37] <SWPadnos> ok, minimilltask + bridgeportio I wouldn't expect to give errors, because the bridgeportio module understands a superset of the messages minimilltask would send
[23:58:15] <alex_joni> hardy is quite nice :)
[23:58:33] <SWPadnos> cool. I plan to try it out once B1 is released
[23:58:42] <alex_joni> I have A6 running here
[23:58:50] <alex_joni> B1 is next week iirc
[23:59:04] <SWPadnos> March 20
[23:59:23] <alex_joni> thursday
[23:59:30] <SWPadnos> yep
[23:59:45] <alex_joni> * alex_joni tries to remember rtai foo :)
[23:59:54] <SWPadnos> I wonder where the developer summit will be this year
[23:59:55] <SWPadnos> heh
