#emc-devel | Logs for 2009-02-22

Back
[00:16:46] <cradek> sf has sure hidden the way you subscribe to the mailing lists
[00:17:08] <cradek> I think that's why we're getting so many mails to *-owner
[00:18:25] <alex_joni> yeah, it's hard to get to the mailing list for subscribing
[00:18:58] <cradek> you can find their too-stupid-to-show-threads archive pretty easily, but the subscribe is sure obscure
[00:19:14] <cradek> you have to guess to click on the thing that also causes a menu to appear when you waggle the mouse over it
[00:19:29] <cradek> that's a very sad user interface
[00:19:43] <jmkasunich> its web 2.0
[00:19:47] <cradek> that's not how menus work
[00:19:59] <jmkasunich> user convenience doesn't matter, only ad revenue
[00:20:00] <cradek> you don't pull down File and then click on File and expect something to happen
[00:20:07] <alex_joni> I know I tried the other day to get to subscribing, and I didn't find it
[00:20:15] <cradek> now you know the secret
[00:20:24] <jmkasunich> we do link the proper page from our website don't we?
[00:20:25] <cradek> go to sf.net/projects/emc
[00:20:32] <cradek> click "More" (ugh)
[00:20:44] <cradek> waggle the mouse over "Mailing Lists" until the menu appears
[00:20:51] <cradek> now ignore the menu and click on "Mailing Lists" anyway
[00:20:56] <cradek> (ugh ugh)
[00:21:07] <alex_joni> yeah, I found it eventually.. but it sucks big time
[01:12:20] <rob> rob is now known as Guest19691
[03:00:53] <jmk-robot> SWPadnos: still around?
[03:00:57] <SWPadnos> yep
[03:01:05] <jmk-robot> jmkasunich@robot:~$ time dcraw -q 3 dsc_0291.nef
[03:01:05] <jmk-robot> real0m23.033s
[03:01:05] <jmk-robot> user0m15.709s
[03:01:05] <jmk-robot> sys0m0.500s
[03:01:14] <SWPadnos> hmmm
[03:01:32] <jmk-robot> thats a lot of pixels
[03:01:43] <jmk-robot> (I was able to easily read IC markings ;-)
[03:01:45] <SWPadnos> how about time dcraw -q 3 -c dsc_0291.nef > /dev/null
[03:01:48] <SWPadnos> heh
[03:01:51] <SWPadnos> 12 MP :)
[03:02:07] <SWPadnos> Nikon D300. nice cameras
[03:02:36] <jmk-robot> real0m16.675s
[03:02:36] <jmk-robot> user0m15.853s
[03:02:36] <jmk-robot> sys0m0.164s
[03:02:55] <jmk-robot> the user number seems to represent the conversion time pretty consistently
[03:03:04] <SWPadnos> oh, true enough
[03:03:25] <SWPadnos> you're not at work are you?
[03:03:29] <jmk-robot> no
[03:03:30] <SWPadnos> (if so, go home! :) )
[03:03:32] <SWPadnos> good
[03:03:46] <jmk-robot> I went to the grocery, and work is nearby, so I stopped in and grabbed the bot
[03:03:57] <SWPadnos> ah, cool. thanks
[03:04:06] <SWPadnos> that's an Atom 1.6 GHz?
[03:04:16] <jmk-robot> I wanted to investigate the strange usb thing
[03:04:16] <jmk-robot> yes
[03:04:20] <jmk-robot> atom 330
[03:04:36] <jmk-robot> dual core - I wonder if there is a multi-threaded dcraw
[03:04:46] <SWPLinux> there is, but this isn't it
[03:05:16] <SWPLinux> hmmm. you're on 32-bit also
[03:05:32] <SWPLinux> this machine is almost 3x faster (on one core also)
[03:05:48] <jmk-robot> just for grins, I started two dcraws in two shells
[03:05:48] <SWPLinux> steve@jauntyA3:/Project/Digicam09/images$ time dcraw -q 3 dsc_0291.nef
[03:05:50] <SWPLinux> real0m6.503s
[03:05:51] <SWPLinux> user0m5.552s
[03:05:53] <SWPLinux> sys0m0.376s
[03:05:54] <SWPLinux> steve@jauntyA3:/Project/Digicam09/images$ time dcraw -q 3 -c dsc_0291.nef > /dev/null
[03:05:56] <SWPLinux> real0m5.669s
[03:05:57] <SWPLinux> user0m5.500s
[03:05:59] <SWPLinux> sys0m0.172s
[03:06:00] <SWPLinux> steve@jauntyA3:/Project/Digicam09/images$
[03:06:03] <SWPLinux> yeah, about the same total time
[03:06:11] <jmk-robot> real0m18.527s
[03:06:11] <jmk-robot> user0m15.733s
[03:06:11] <jmk-robot> sys0m0.220s
[03:06:16] <jmk-robot> real0m18.685s
[03:06:16] <jmk-robot> user0m16.093s
[03:06:16] <jmk-robot> sys0m0.248s
[03:06:37] <SWPLinux> I did it the "easy" way: time (dcraw ... & dcraw ... & wait)
[03:06:51] <jmk-robot> I bet the atom wins in speed per $ and speed per watt
[03:07:08] <SWPLinux> speed per watt, probably, though this is a 45W CPU
[03:07:10] <jmk-robot> and speed per cubic inch
[03:07:22] <SWPLinux> definitely, if you include the heatsink ;)
[03:07:30] <seb_kuzminsky> how did your robot do, jmk?
[03:07:37] <jmk-robot> I'm not comparing CPUs at all
[03:07:43] <jmk-robot> total system size, total system power
[03:07:53] <jmk-robot> (and total system price)
[03:07:59] <SWPLinux> possibly
[03:08:15] <SWPLinux> this isn't a super-machine though, it's low power and cast-offs :)
[03:08:22] <SWPLinux> Athlon X2 4850e
[03:08:27] <SWPLinux> not even quad core!
[03:08:28] <jmk-robot> oh, you use those?
[03:08:29] <SWPLinux> :)
[03:08:36] <SWPLinux> I cast the stuff off ;)
[03:08:43] <jmk-robot> heh
[03:08:49] <jmk-robot> seb_kuzminsky: epic failure
[03:09:00] <SWPLinux> this is a system I put together with the Gigabyte motherboard that exploded a FET on me
[03:09:18] <SWPLinux> (after RMA)
[03:09:21] <jmk-robot> 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
[03:09:41] <seb_kuzminsky> bummer :-(
[03:09:49] <SWPadnos> heh
[03:09:56] <SWPadnos> that's exactly what I said
[03:10:07] <SWPadnos> and alex (though he forgot the sad face)
[03:10:07] <jmk-robot> 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/
[03:11:00] <jmk-robot> the fet failure was particularly annoying - it was driving all over the place before that, with no signs of issues
[03:11:11] <SWPadnos> demo syndrome
[03:11:14] <SWPadnos> it got nervous
[03:11:23] <jmk-robot> cursed
[03:11:23] <seb_kuzminsky> at work we blame the demo gremlins
[03:11:28] <SWPadnos> the robot equivalent of throwing up from stage fright ;)
[03:14:39] <jmk-robot> that's annoying
[03:15:01] <jmk-robot> on hardy/xubuntu, you can't resize a window from the top
[03:15:18] <jmk-robot> and the bottom is off-screen
[03:16:06] <jmk-robot> http://www.pastebin.ca/1344110
[03:16:09] <SWPadnos> try this: alt-space r down-arrow multiple up-arrows
[03:16:24] <jmk-robot> ^^^ is what I get when I plug the camera into the mobo usb header
[03:16:40] <SWPadnos> alt-space for the window menu, R is resize, down-arrow selects the bottom, up-arrows move the bottom up
[03:17:21] <jmk-robot> not here
[03:17:43] <jmk-robot> alt-space gets the window menu, R does nothing, arrows just change the selected item in the menu
[03:17:50] <jmk-robot> might be xubuntu vs gnome
[03:17:55] <SWPadnos> could be
[03:17:56] <jmk-robot> not important really
[03:18:02] <SWPadnos> is there a resize option on the window menu?
[03:18:26] <seb_kuzminsky> hm, i can't commit a small bugfix to infrastructure/farm-scripts/emc2_mail.py
[03:18:29] <SWPadnos> what does it look like when you plug it into a rear header
[03:18:29] <seb_kuzminsky> Checking in emc2_mail.py;
[03:18:30] <seb_kuzminsky> new revision: 1.2; previous revision: 1.1
[03:18:30] <seb_kuzminsky> cvs [commit aborted]: could not open lock file `/cvs/infrastructure/farm-scripts/,emc2_mail.py,': Permission denied
[03:18:45] <SWPadnos> anon checkout?
[03:19:20] <seb_kuzminsky> heh
[03:19:26] <seb_kuzminsky> * seb_kuzminsky blushes
[03:19:31] <seb_kuzminsky> dont mind me...
[03:20:20] <jmk-robot> heh - either intel's docs are wrong, or the camera cable uses the wrong color coding
[03:20:29] <jmk-robot> I swapped data+ and data- and it worked
[03:21:23] <SWPadnos> color code of a USB cable?
[03:21:29] <jmk-robot> its sad how easy things become when you aren't under time pressure
[03:21:32] <SWPadnos> like, one with a sliced off connector?
[03:21:34] <jmk-robot> yes
[03:21:47] <jmk-robot> black, green, white, red
[03:21:59] <jmk-robot> black is ground and red is power, thankfully they didn't screw that up
[03:22:10] <CIA-2> EMC: 03seb 07TRUNK * 10infrastructure/farm-scripts/emc2_mail.py: initialize 'author' so it doesnt croak if it's missing
[03:22:41] <SWPadnos> is there a color code for the wires in the cable? (and do you think every cheapo manufacturer follows it?)
[03:22:48] <SWPadnos> or is this an Intel cable?
[03:23:36] <jmk-robot> actually, I neglected the third possibility - that either I (or my co-worker who actually made the annotations on the paper) can't read
[03:24:01] <jmk-robot> we referred to this page to get the "standard" color code http://www.usbman.com/Guides/BelkinMotherboard_cable_assembly.htm
[03:24:10] <jmk-robot> I printed the intel manual page showing the header pinout
[03:24:32] <jmk-robot> he wrote the colors on the printout, but got green and white backwards
[03:24:41] <jmk-robot> (I have the printout with his writing on it in front of me)
[03:25:20] <SWPadnos> heh
[03:25:24] <SWPadnos> a-ha!
[03:25:27] <jmk-robot> 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
[03:25:35] <SWPadnos> nice
[03:25:37] <SWPadnos> ish
[03:25:59] <jmk-robot> I thought of swapped pins when I first had the problem
[03:26:26] <jmk-robot> but it was late o-clock and I was in a hurry, so I jury rigged a swap back to the old cable
[03:27:55] <jmk-robot> I think this board would be neat with a right-angle PCI extender and a mesa card
[03:28:08] <jmk-robot> complete CNC control in 7 x 7 x 4"
[03:28:23] <SWPadnos> yeah. I'm interested in something like that
[03:28:40] <jmk-robot> even better - get a toroid and some geckos
[03:28:43] <SWPadnos> the ones I have for the power supply project are about the same, except they're in a case
[03:28:47] <jmk-robot> complete control with drives, in a 7" cube
[03:29:05] <SWPadnos> argh. I'm just looking at all those gas receipts from the trip to pick up the lathe
[03:29:11] <SWPadnos> it's quite a stack
[03:29:17] <jmk-robot> ouch
[03:29:22] <jmk-robot> at least it wasn't $4 gas
[03:29:28] <SWPadnos> yeah
[03:29:35] <SWPadnos> I lucked out on that front
[03:42:45] <SWPadnos> heh. about 111 gallons, 1298 miles
[03:43:04] <SWPadnos> 11.7 MPG average. that's probably not too bad actually
[04:12:33] <cradek> yay, we have all sorts of choices for venue
[04:16:18] <SWPadnos> yep
[04:16:53] <SWPadnos> I think we have two or three distinct goals, which may or may not play well with each other
[04:17:00] <SWPadnos> maybe four even :)
[04:17:19] <SWPadnos> (in no particular order):
[04:17:30] <SWPadnos> evangelism / promotion / education
[04:17:49] <SWPadnos> bugfixing / feature additions / software design
[04:18:02] <SWPadnos> messing with big machines :)
[04:18:17] <SWPadnos> anything I missed? :)
[04:20:44] <cradek> beer
[04:20:56] <SWPadnos> oh, well then we should include food to
[04:20:58] <SWPadnos> o
[04:21:03] <cradek> but seriously - I think that's it
[04:21:15] <SWPadnos> ok, excellent! :)
[04:21:39] <SWPadnos> sadly, lines 1 and 2 are often conflicting goals
[04:22:00] <cradek> hm, interesting point
[04:32:19] <SWPadnos> hmmm. got to practice getting up early. good night
[04:42:02] <jmk-robot> good plan
[12:29:16] <BigJohnT> can you set the front and back angle with G10L1 when your running in lathe mode?
[12:42:48] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add info on touch off
[12:42:54] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/images/Lathe-X-TouchOff.png: add image
[13:28:04] <jepler> BigJohnT: I think I remember cradek saying you couldn't.
[13:28:32] <BigJohnT> ok thanks jepler
[14:04:50] <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
[14:14:50] <BigJohnT> 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?
[14:15:06] <BigJohnT> just reading the sf bug on it
[14:26:29] <cradek> BigJohnT: if in radius mode, you need to enter a radius for touch off; if in diameter mode, you enter diameter
[14:26:53] <BigJohnT> heh cradek thanks for that
[14:27:12] <cradek> maybe it's obvious, I don't know
[14:27:20] <BigJohnT> and good morning
[14:27:33] <BigJohnT> maybe to some :) and maybe not to others
[14:28:01] <cradek> good morning!
[14:29:00] <BigJohnT> just to verify on G10 L1 there is no way to set the frontangle or backangle right
[14:29:12] <cradek> right
[14:29:22] <BigJohnT> ok dokie
[14:29:30] <cradek> or comment, like you said
[14:29:41] <BigJohnT> * BigJohnT smells something good cooking
[14:29:57] <cradek> that's what I need too
[14:30:11] <cradek> bbl...
[14:31:00] <jepler> BigJohnT: in 2.3, stepconf should work for sherline users
[14:31:34] <jepler> huh that's weird
[14:32:00] <BigJohnT> what's that?
[14:32:01] <jepler> I didn't see anything on my screen after "<BigJohnT> just reading the sf bug on it" until after I typed that
[14:32:52] <BigJohnT> I was reading your comment in bug report 2187024 where it might not be fixed in 2.3
[14:33:00] <BigJohnT> breakfast calls
[14:33:04] <jepler> I must be feeling more upbeat today than that day
[14:35:39] <jepler> bbl, time for the last full day of vacation
[14:42:13] <seb_kuzminsky> jepler: you may be right that configure only checks for xsltproc if --enable-build-documentation is given
[14:42:36] <seb_kuzminsky> but that's how the .deb configures itself, so that's why i added xsltproc to the build-depends
[14:42:51] <seb_kuzminsky> oh wait, nevermind, go enjoy your vacation! :-)
[14:45:02] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gcode/ (main.lyx tool_compensation.lyx): more info on touch off
[14:45:44] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: remove ref to pyvcp on parallel port page
[14:48:22] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add info on using g10 l1
[14:49:00] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/stepconf-entry.png: add image
[14:57:14] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/lathe/lathe-user.lyx: add note about radius mode
[15:33:55] <BigJohnT> 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."
[15:34:14] <BigJohnT> would it not be better to invert the direction pin for that axis?
[15:34:23] <alex_joni> BigJohnT: not always
[15:34:33] <alex_joni> inverted direction pin might cause problems with step timings
[15:34:59] <BigJohnT> ok
[15:36:03] <BigJohnT> but I don't understand as off is one direction and on is the other???
[15:36:15] <BigJohnT> how could that cause problems?
[15:36:29] <alex_joni> hmm.. for dir it might not, for step it surely does
[15:37:15] <BigJohnT> yes for step I understand that step space and step time can honk things up if backwards
[15:37:24] <BigJohnT> if the timing is different
[15:37:58] <BigJohnT> so it would be safe to say "or invert the direction pin"
[15:38:12] <BigJohnT> btw good morning alex_joni
[15:38:18] <alex_joni> heh, good evening to you too
[16:16:37] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/ (stepconf-advanced.png stepconf-entry.png): add image
[16:19:13] <steves_logging> steves_logging is now known as steve_stallings
[16:20:06] <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
[16:20:42] <steve_stallings> inverting the step signal may well alter the timing and result in problems
[16:28:58] <BigJohnT> hi steve_stallings
[16:32:05] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: update info
[16:37:17] <steve_stallings> 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.
[16:37:46] <BigJohnT> dangifIknow :)
[16:39:23] <steve_stallings> gee, and I was hoping for a simple solution like Red Bull soda 8-)
[16:39:58] <BigJohnT> LOL
[16:40:34] <BigJohnT> no, I guess it just bugs me if it is wrong
[16:40:46] <BigJohnT> but a little homemade wine or beer helps
[17:45:18] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/ (copy_and_run.lyx stepconf.lyx launcher.png): image not used in docs
[17:52:52] <BigJohnT> halui.jog only allows 0-7 and not 8 for the 9th axis?
[17:53:58] <scstemp> scstemp is now known as steve_stallings
[17:54:03] <BigJohnT> and halui.joint?
[18:00:32] <alex_joni> BigJohnT: you're right, I'll fix it in a sec
[18:00:43] <alex_joni> initially the motion controller only supported 8 joints
[18:00:51] <BigJohnT> ok I'll fix the docs in a sec
[18:09:01] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/halui.lyx: changed jog and joint to 9 axis
[18:13:34] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: minor edits
[18:13:39] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/classic_ladder.lyx: minor edits
[18:13:46] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/images/SaveAs.png: minor edits
[18:13:47] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: minor edits
[18:14:43] <BigJohnT> * BigJohnT thinks it is naptime :)
[18:29:15] <CIA-2> EMC: 03alex_joni 07TRUNK * 10emc2/src/emc/usr_intf/halui.cc: fix comment, joints go from 0 to max 8 now
[20:04:07] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/common/Integrator_Concepts.lyx: minor edits
[20:04:07] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: minor edits
[20:04:07] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: minor edits
[20:17:51] <jmkasunich> hello BigJohnT_
[20:39:34] <BigJohnT_> hi jmkasunich
[20:40:34] <BigJohnT_> BigJohnT_ is now known as BigJohnT
[20:40:45] <jmkasunich> I have a question about plasma
[20:40:51] <jmkasunich> how thick can your machine cut?
[20:40:54] <jmkasunich> (in steel)
[20:41:29] <BigJohnT> it can cut 3/4 or so but it gets ugly after 5/8
[20:41:37] <jmkasunich> thanks
[20:41:42] <BigJohnT> I think they say it will cut 1"
[20:41:46] <jmkasunich> (just collecting ideas for a project)
[20:42:10] <BigJohnT> ok dokie
[20:43:47] <BigJohnT> anyone know what homing.dot and hss.dot are for in docs/src/code ?
[20:46:11] <SWPadnos> document templates?
[20:54:36] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/images/ (latency.png stepconf-latency.png): update image
[20:56:30] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/ (latency.png stepconf.lyx): update image
[21:00:13] <skunkworks> SWPadnos: left yet?
[21:00:27] <SWPadnos> nope. tomorrow at 0:dark thirty :)
[21:01:43] <skunkworks> we are driving to the st paul airport at 5:00 today
[21:01:47] <SWPadnos> actually 7:45 AM, so it might be light out already, if the snowstorm has finished by the
[21:01:50] <SWPadnos> cool
[21:02:10] <SWPadnos> it's been rainy in Vegas for the last week - you may want to bring raincoats
[21:02:16] <buildmaster> 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
[21:02:43] <BigJohnT> crumb
[21:03:16] <skunkworks> SWPadnos: yes. My wife though thinks it is turning
[21:03:29] <SWPadnos> could be. a friend just got back
[21:03:52] <skunkworks> either way - it will be fun ;)
[21:05:25] <buildmaster> 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
[21:06:07] <buildmaster> 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
[21:08:21] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf_fr.lyx: missed that one
[21:08:58] <BigJohnT> * BigJohnT hums the final jepordy tune while waiting for the buildbot to say I can go out and play...
[21:18:00] <christel> [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!
[21:26:15] <BigJohnT> Houston buildbot is go for launch :)
[21:32:15] <christel> [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.
[23:13:30] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: fix broken link rob found
[23:18:37] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: second time is a charm
[23:27:24] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/install/Latency_Test.lyx: add link thanks rob
[23:27:34] <CIA-2> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/motion/tweaking_steppers.lyx: add link thanks rob