sf has sure hidden the way you subscribe to the mailing lists
I think that's why we're getting so many mails to *-owner
yeah, it's hard to get to the mailing list for subscribing
you can find their too-stupid-to-show-threads archive pretty easily, but the subscribe is sure obscure
you have to guess to click on the thing that also causes a menu to appear when you waggle the mouse over it
that's a very sad user interface
its web 2.0
that's not how menus work
user convenience doesn't matter, only ad revenue
you don't pull down File and then click on File and expect something to happen
I know I tried the other day to get to subscribing, and I didn't find it
now you know the secret
we do link the proper page from our website don't we?
go to sf.net/projects/emc
click "More" (ugh)
waggle the mouse over "Mailing Lists" until the menu appears
now ignore the menu and click on "Mailing Lists" anyway
yeah, I found it eventually.. but it sucks big time
rob is now known as Guest19691
SWPadnos: still around?
jmkasunich@robot:~$ time dcraw -q 3 dsc_0291.nef
thats a lot of pixels
(I was able to easily read IC markings ;-)
how about time dcraw -q 3 -c dsc_0291.nef > /dev/null
12 MP :)
Nikon D300. nice cameras
the user number seems to represent the conversion time pretty consistently
oh, true enough
you're not at work are you?
(if so, go home! :) )
I went to the grocery, and work is nearby, so I stopped in and grabbed the bot
ah, cool. thanks
that's an Atom 1.6 GHz?
I wanted to investigate the strange usb thing
dual core - I wonder if there is a multi-threaded dcraw
there is, but this isn't it
hmmm. you're on 32-bit also
this machine is almost 3x faster (on one core also)
just for grins, I started two dcraws in two shells
steve@jauntyA3:/Project/Digicam09/images$ time dcraw -q 3 dsc_0291.nef
steve@jauntyA3:/Project/Digicam09/images$ time dcraw -q 3 -c dsc_0291.nef > /dev/null
yeah, about the same total time
I did it the "easy" way: time (dcraw ... & dcraw ... & wait)
I bet the atom wins in speed per $ and speed per watt
speed per watt, probably, though this is a 45W CPU
and speed per cubic inch
definitely, if you include the heatsink ;)
how did your robot do, jmk?
I'm not comparing CPUs at all
total system size, total system power
(and total system price)
this isn't a super-machine though, it's low power and cast-offs :)
Athlon X2 4850e
not even quad core!
oh, you use those?
I cast the stuff off ;)
seb_kuzminsky: epic failure
this is a system I put together with the Gigabyte motherboard that exploded a FET on me
after working all night on it, I wasn't ready in time for the 9am deadline, so I couldn't compete in the actual contest
that's exactly what I said
and alex (though he forgot the sad face)
and when I tried to do a demo run (immediately after the contest runs), to show what I _had_ managed to get working, a FET failed on my motor driver board, and blew a fuse
[03:10:29] <seb_kuzminsky> http://xkcd.com/376/
the fet failure was particularly annoying - it was driving all over the place before that, with no signs of issues
it got nervous
at work we blame the demo gremlins
the robot equivalent of throwing up from stage fright ;)
on hardy/xubuntu, you can't resize a window from the top
and the bottom is off-screen
[03:16:06] <jmk-robot> http://www.pastebin.ca/1344110
try this: alt-space r down-arrow multiple up-arrows
^^^ is what I get when I plug the camera into the mobo usb header
alt-space for the window menu, R is resize, down-arrow selects the bottom, up-arrows move the bottom up
alt-space gets the window menu, R does nothing, arrows just change the selected item in the menu
might be xubuntu vs gnome
not important really
is there a resize option on the window menu?
hm, i can't commit a small bugfix to infrastructure/farm-scripts/emc2_mail.py
what does it look like when you plug it into a rear header
Checking in emc2_mail.py;
new revision: 1.2; previous revision: 1.1
cvs [commit aborted]: could not open lock file `/cvs/infrastructure/farm-scripts/,emc2_mail.py,': Permission denied
* seb_kuzminsky blushes
dont mind me...
heh - either intel's docs are wrong, or the camera cable uses the wrong color coding
I swapped data+ and data- and it worked
color code of a USB cable?
its sad how easy things become when you aren't under time pressure
like, one with a sliced off connector?
black, green, white, red
black is ground and red is power, thankfully they didn't screw that up
EMC: 03seb 07TRUNK * 10infrastructure/farm-scripts/emc2_mail.py: initialize 'author' so it doesnt croak if it's missing
is there a color code for the wires in the cable? (and do you think every cheapo manufacturer follows it?)
or is this an Intel cable?
actually, I neglected the third possibility - that either I (or my co-worker who actually made the annotations on the paper) can't read
we referred to this page to get the "standard" color code http://www.usbman.com/Guides/BelkinMotherboard_cable_assembly.htm
I printed the intel manual page showing the header pinout
he wrote the colors on the printout, but got green and white backwards
(I have the printout with his writing on it in front of me)
he did make the cable per his notations (and very neatly too, including terminating the ground with a ring lug on a mobo mounting screw, and heatshrink over the exposed shield
I thought of swapped pins when I first had the problem
but it was late o-clock and I was in a hurry, so I jury rigged a swap back to the old cable
I think this board would be neat with a right-angle PCI extender and a mesa card
complete CNC control in 7 x 7 x 4"
yeah. I'm interested in something like that
even better - get a toroid and some geckos
the ones I have for the power supply project are about the same, except they're in a case
complete control with drives, in a 7" cube
argh. I'm just looking at all those gas receipts from the trip to pick up the lathe
it's quite a stack
at least it wasn't $4 gas
I lucked out on that front
heh. about 111 gallons, 1298 miles
11.7 MPG average. that's probably not too bad actually
yay, we have all sorts of choices for venue
I think we have two or three distinct goals, which may or may not play well with each other
maybe four even :)
(in no particular order):
evangelism / promotion / education
bugfixing / feature additions / software design
messing with big machines :)
anything I missed? :)
oh, well then we should include food to
but seriously - I think that's it
ok, excellent! :)
sadly, lines 1 and 2 are often conflicting goals
hm, interesting point
hmmm. got to practice getting up early. good night
can you set the front and back angle with G10L1 when your running in lathe mode?
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add info on touch off
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/images/Lathe-X-TouchOff.png: add image
BigJohnT: I think I remember cradek saying you couldn't.
ok thanks jepler
hmm .. xsltproc should only be needed with --enable-build-documentation (build both pdf and html). if configure requires it for --enable-build-documentation=pdf (which debian build configures with) then it should be fixed
jepler: should we add a note on the second page of the stepconf wizard to sherline users to use the configuration selector instead of the wizard?
just reading the sf bug on it
BigJohnT: if in radius mode, you need to enter a radius for touch off; if in diameter mode, you enter diameter
heh cradek thanks for that
maybe it's obvious, I don't know
and good morning
maybe to some :) and maybe not to others
just to verify on G10 L1 there is no way to set the frontangle or backangle right
or comment, like you said
* BigJohnT smells something good cooking
that's what I need too
BigJohnT: in 2.3, stepconf should work for sherline users
huh that's weird
I didn't see anything on my screen after "<BigJohnT> just reading the sf bug on it" until after I typed that
I was reading your comment in bug report 2187024 where it might not be fixed in 2.3
I must be feeling more upbeat today than that day
bbl, time for the last full day of vacation
jepler: you may be right that configure only checks for xsltproc if --enable-build-documentation is given
but that's how the .deb configures itself, so that's why i added xsltproc to the build-depends
oh wait, nevermind, go enjoy your vacation! :-)
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gcode/ (main.lyx tool_compensation.lyx): more info on touch off
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: remove ref to pyvcp on parallel port page
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add info on using g10 l1
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/stepconf-entry.png: add image
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add note about radius mode
in the stepconf wizard chapter on axis configuration page in Leadscrew Pitch it has "If the machine travels in the wrong direction, enter a negative number here instead of a positive number."
would it not be better to invert the direction pin for that axis?
BigJohnT: not always
inverted direction pin might cause problems with step timings
but I don't understand as off is one direction and on is the other???
how could that cause problems?
hmm.. for dir it might not, for step it surely does
yes for step I understand that step space and step time can honk things up if backwards
if the timing is different
so it would be safe to say "or invert the direction pin"
btw good morning alex_joni
heh, good evening to you too
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/ (stepconf-advanced.png stepconf-entry.png): add image
steves_logging is now known as steve_stallings
inverting the direction pin to correct travel direction would be safe as it does not change the timing between the active edge of the step pulse and the direction signal
inverting the step signal may well alter the timing and result in problems
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: update info
Hi John. Where do you get the drive to do so much documentation work? It is always the hardest part of any job I tackle.
gee, and I was hoping for a simple solution like Red Bull soda 8-)
no, I guess it just bugs me if it is wrong
but a little homemade wine or beer helps
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/ (copy_and_run.lyx stepconf.lyx launcher.png): image not used in docs
halui.jog only allows 0-7 and not 8 for the 9th axis?
scstemp is now known as steve_stallings
BigJohnT: you're right, I'll fix it in a sec
initially the motion controller only supported 8 joints
ok I'll fix the docs in a sec
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/halui.lyx: changed jog and joint to 9 axis
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: minor edits
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/classic_ladder.lyx: minor edits
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/images/SaveAs.png: minor edits
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: minor edits
* BigJohnT thinks it is naptime :)
EMC: 03alex_joni 07TRUNK * 10emc2/src/emc/usr_intf/halui.cc: fix comment, joints go from 0 to max 8 now
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/common/Integrator_Concepts.lyx: minor edits
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: minor edits
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: minor edits
BigJohnT_ is now known as BigJohnT
I have a question about plasma
how thick can your machine cut?
it can cut 3/4 or so but it gets ugly after 5/8
I think they say it will cut 1"
(just collecting ideas for a project)
anyone know what homing.dot and hss.dot are for in docs/src/code ?
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/ (latency.png stepconf-latency.png): update image
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/ (latency.png stepconf.lyx): update image
SWPadnos: left yet?
nope. tomorrow at 0:dark thirty :)
we are driving to the st paul airport at 5:00 today
actually 7:45 AM, so it might be light out already, if the snowstorm has finished by the
it's been rainy in Vegas for the last week - you may want to bring raincoats
build #715 of hardy-x86-trunk-realtime-deb is complete: Failure [failed compile] Build details are at http://emc2-buildbot.colorado.edu/buildbot/builders/hardy-x86-trunk-realtime-deb/builds/715
SWPadnos: yes. My wife though thinks it is turning
could be. a friend just got back
either way - it will be fun ;)
build #678 of dapper-x86-trunk-realtime-deb is complete: Failure [failed compile] Build details are at http://emc2-buildbot.colorado.edu/buildbot/builders/dapper-x86-trunk-realtime-deb/builds/678
build #14 of lenny-x86-trunk-realtime-deb is complete: Failure [failed compile] Build details are at http://emc2-buildbot.colorado.edu/buildbot/builders/lenny-x86-trunk-realtime-deb/builds/14
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf_fr.lyx: missed that one
* BigJohnT hums the final jepordy tune while waiting for the buildbot to say I can go out and play...
[Global Notice] Hi all, I'm about to take services down for an upgrade, this means that for the duration of the downtime the network will be without our friends NickServ, ChanServ and so forth -- the upgrade shouldn't take long, but feel free to cross fingers and toes for luck regardless! I'm sorry for the inconvenience and hope you have a nice Sunday!
Houston buildbot is go for launch :)
[Global Notice] Hi again everyone, that went a lot smoother than the LHC, and as with the hadron collider no black holes have appeared! Normal Services may now commence (ok, that was a poor joke, even for me)! Apologies for the inconvenience, thank you for using freenode and have a good evening.
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: fix broken link rob found
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: second time is a charm
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: add link thanks rob
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/motion/tweaking_steppers.lyx: add link thanks rob