EMC: 03jmelson 07TRUNK * 10emc2/configs/univstep/univstep_load.hal: add components estop_latch and and2 to thread
shouldn't he have actually connected those to something, or is that in the full file?
whatever it is, he needs to put it on the branch if he wants it released
hmm, I don't understand his change either
good thing it's jepler's problem :-)
it's pretty obvious what he did, but not what he was supposed to do
not obvious - that could be what he was supposed to do
ah - it looks like the connections were there already, but the loads were just missed
are they in a thread?
they are now
hmmm - no, maybe they aren't
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)
uh on the machine that won't go over 90ipm?
your point? ;)
I suspect glaciers move at 90ipm
or possibly IPM
actually it would probably be fine if the "table" didn't have to move a block and a half
you should have seen the quill when it was extended
man that thing is long
how big around is it?
8-10" I think
hmmm - maybe bigger. the taper had a couple of inches on either side
50 taper's pretty darn big to start with
yeah - about as big as max ;)
oh - I should upload those photos
finally uploading. it'll take a little while because I got lazy and copied everything
cradek: how was the birthday?
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/
"Max Tool envy.JPG" is a good one :)
hmm.. latest 2.2.x from CVS, I get a lot of messages:
nomodifier 16 <function <lambda> at 0xb7d58cdc>
I get them printed in the console (I ran scripts/emc and selected sim/axis) when jogging with keyboard
I get different messages while jogging with "-"/"+"
nomodifier 16 <function jog_minus at 0xb7cc733c>
nomodifier 16 <function jog_plus at 0xb7cc7304>
(running dapper with python 2.4.3-0ubuntu6 installed)
jepler: anything serious about those messages?
they seem to be coming from AXIS on key events
hm I must have left a print in
EMC: 03jepler 07v2_2_branch * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: remove debugging message
cool, that fixes it
Just this once .. here's the log: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-03-15.txt
EMC: 03jmelson 07TRUNK * 10emc2/configs/univstep/univstep_load.hal: add threads for estop_latch and and2
EMC: 03cradek 07TRUNK * 10emc2/src/emc/kinematics/5axiskins.c: this is out of date. update from wtool branch
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
oh - no, it's the right direction, but the mouse wheel is inverted (silly me)
fenn__ is now known as fenn
jepler: on a new install I noticed that python-tk isn't installed, yet configure doesn't catch that
whee.. it works :)
running emc2 on hardy .. sim only so far
Linux dana-laptop 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
hmmm. can anyone confirm that with EMC1, the io program had to be compiled for the particular hardware to be used?
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)
SWPadnos: I think that is the case
different io executables were put together based on the card used
I don't think all combos were in CVS though
right, and task didn't do any direct manipulation, so only motion and io had to be hardware-specific
io also having to be "machine" specific - ie, minimill vs. bridgeport functions, combined with the IO driver of choice
(which might be the parport in lots of situations)
and more advanced hardware usually having all the bridgeportio functions, since minimillio was there largely due to lack of pins :)
I vaugly remember the bridgeport setup used 2 printer ports
I was just seeing that the vti.ini also uses brisgeportio, whereas ppmc.ini uses ppmcio
err - vital.ini
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
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?
just no function?
I used it the other way around
ok, thanks (did you just check that? :) )
bridgeportio and the smaller task
was it minimilltask? can't remember
ok, minimilltask + bridgeportio I wouldn't expect to give errors, because the bridgeportio module understands a superset of the messages minimilltask would send
hardy is quite nice :)
cool. I plan to try it out once B1 is released
I have A6 running here
B1 is next week iirc
* alex_joni tries to remember rtai foo :)
I wonder where the developer summit will be this year