#emc-devel | Logs for 2009-05-05

[02:20:50] <jepler> oh -- I see that alien hal style is seb's, not goslowjimbo's
[02:20:58] <jepler> I was about to criticise it
[02:28:39] <SWPadnos> net the_expected_position_to_which_the_motor.0.should-move axis.0.pos-cmd pid.0.command
[02:44:51] <steves_logging> steves_logging is now known as steve_stallings
[02:48:16] <cfrank> Ping
[02:50:49] <cfrank> cradek: I was able to run the 5axis simulator. How do gat it to control my machine?
[03:09:48] <cradek> what specifically do you mean? how far are you?
[03:10:51] <cfrank> cradek: I am adding two axes to my mill, and I am trying to create a config for it.
[03:11:21] <cfrank> Looking to use a parallel port interface.
[03:11:29] <cfrank> Steppers.
[03:11:38] <cfrank> XYZBC
[03:11:42] <cradek> ok I see. unless you have the same configuration of rotaries as an existing demo, you will need to write your kinematics code.
[03:12:35] <cfrank> I am good at code, but kinematics? no.
[03:12:55] <cradek> do you have a picture of the machine configuration? maybe we can brainstorm.
[03:13:06] <cfrank> I thought I just specify machine joint distances etc
[03:13:27] <cradek> don't be too scared - kinematics is usually just a little bit of simple trig once you get the idea
[03:13:51] <cradek> well, it depends whether the kins are already written.
[03:14:00] <cradek> there are many configurations of 5 axis machines.
[03:14:23] <cfrank> Doing something like your frist XYZBC machine. Using a Taig with B rotating around the Y axis miving up and down on the Z column
[03:14:46] <cfrank> C is just a rotary table sitting on the base.
[03:15:46] <cradek> gotcha
[03:15:58] <cradek> then you can use maxkins directly
[03:16:08] <cfrank> cool.
[03:16:42] <cradek> when you build it, you should arrange B so it rotates around where the tip of a typical-length tool is.
[03:17:00] <cradek> that way, you don't waste a huge amount of X motion to keep the tool tip in the same place when B rotates
[03:17:15] <cradek> I think that is the only tricky part of that machine configuration
[03:18:20] <cfrank> That's tough. I will need a very long arm of the rotating axis
[03:18:51] <cradek> do you understand the problem I described with wasted X motion?
[03:20:29] <cfrank> Yes, but I am not sure how much it wastes. If the tool tim is 3 inches past the center of rotation of B. how much x is wasted?
[03:21:26] <cradek> depends how far B turns
[03:21:49] <cradek> if it turns +- 90, clearly 6" of X is used
[03:23:36] <cfrank> I see. That slows it down also. I have 11.5 inch travel on the X so that should leave me a good 4+ inches for the size of the part rhght?
[03:24:07] <cfrank> Icould accept that if I could keep the arms short, ant the machine stiff.
[03:24:15] <cradek> yes I guess so
[03:24:45] <cradek> what is the diameter of the C rotary? remember your workspace is pretty much round in XY because of that
[03:25:06] <cfrank> I will move it up at some poing to speed things up and remove the extra x travel.
[03:25:17] <cfrank> 4 inch
[03:25:32] <cfrank> table
[03:26:24] <cfrank> yes. I plan to have my part round in the XY plane
[03:27:05] <cradek> it's surprising how small the working volume gets when you start thinking about this
[03:27:22] <cradek> then you stick a drill in a drill chuck, and you might not be able to reach anymore
[03:30:16] <cfrank> Yep. The Y and Z travel are small. Too small for the toolchanger. I try using collets directly on the spindle and short arbors.
[03:30:32] <cfrank> No drill chucks for me.
[03:32:51] <cfrank> under emc/configs I found max. Is that the one?
[03:33:03] <cradek> max5 I think
[03:33:14] <cfrank> not there.
[03:33:18] <cradek> oh, hmmmm
[03:33:27] <cfrank> m5i20?
[03:33:45] <cfrank> no
[03:33:57] <cradek> no, it's max5, must not be in cvs. one minute.
[03:35:58] <cradek> http://timeguy.com/cradek-files/emc/max5.tar.gz
[03:39:15] <cfrank> Got it. Thanks.
[03:39:36] <cradek> I see maxkins is in cvs, so it may just run as-is
[03:39:47] <cradek> but it might be stale - I haven't used it for a while.
[03:44:37] <cfrank> Loaded max5 into 2.4.0~pre. Any obvious veriables I need to change?
[03:45:12] <cradek> I have no idea :-)
[03:45:23] <cradek> you should look through it and then test.
[03:46:15] <cfrank> Cool. Thanks Chris!
[03:46:38] <cradek> welcome, hope you get it all going.
[03:47:25] <cfrank> With the amount of time I am willing to spend, It will work. Eventually :-)
[03:47:34] <cfrank> Thanks again.
[04:36:12] <steve_stallings> steve_stallings is now known as steves_logging
[12:19:34] <Roguish> alex_joni: are you on and alive this morning (5:20 here)
[12:20:54] <Roguish> I checked my 'atom' installation last night and it definitely does not run with the emc2 rtai kernal thing.
[12:22:51] <Roguish> please refer to ubuntu bug 239602 and ubuntu foum 869967. much better explanation than i can provide.
[12:24:00] <Roguish> after the ubuntu 8.04.2 install, i did the apt-get ....emc2-install.sh and everything went well as far as i could tell.
[12:24:07] <skunkworks> The atom board?
[12:24:18] <Roguish> rebooted, picked the proper build and error.
[12:24:24] <Roguish> skunkworks: yes.
[12:24:48] <skunkworks> I have installed the live cd mine here - seems to work great.
[12:25:08] <skunkworks> well - 17us latency - but never higher.
[12:25:24] <Roguish> mine will not go unless it's 8.04.1 or newer.
[12:26:01] <Roguish> put in 8.04.2 (what i could find to download) and it installs sweet.
[12:26:45] <skunkworks> http://imagebin.ca/img/z0vrLSPy.jpg
[12:28:09] <Roguish> was chatting with alex_joni yesterday morning.
[12:29:03] <Roguish> yeah, that's what i am doing also. wonderful. mesa board and all.
[12:29:12] <skunkworks> I guess all I have tested on it is the emc built livecd's - even dapper
[12:30:53] <Roguish> did you update the bios?
[12:31:39] <Roguish> ssd drive? or hdd?
[12:33:06] <skunkworks> hdd
[12:33:13] <skunkworks> I have not - right out of the box.
[12:33:53] <Roguish> i am going for low cost, low noise, low power, ......
[12:34:09] <Roguish> 80g hdd now, but want ssd
[12:36:02] <Roguish> intell D945GCLF board. 69.99 Fry's
[12:36:38] <skunkworks> is that the single core?
[12:38:21] <Roguish> don't knoe for sure.
[12:39:06] <skunkworks> I think that is the single core
[12:41:27] <skunkworks> This is what I bought http://www.newegg.com/Product/Product.aspx?Item=N82E16813121359
[12:43:32] <Roguish> cool. i see promise in these as they are really inexpensive.
[12:46:41] <skunkworks> yes - I am acutally using one as a media pc. working good.
[12:47:00] <skunkworks> (using the s-video out to a tv)
[12:55:21] <micges> is there possible to write keyboard driver for hal ?
[12:58:20] <SWPadnos> you mean like hal_input, which treats a keyboard like a bunch of switches?
[12:58:31] <micges> yep
[12:58:39] <SWPadnos> yes, it's possible to write that :)
[12:58:45] <micges> but more realtime than hal_input
[12:58:58] <SWPadnos> oh
[12:59:19] <SWPadnos> well, it may be possible to do that with a PS/2 port, but not USB
[12:59:43] <micges> situation: loaded axis with 700.000 lines of gcode, keyboard delays are in seconds :| (tested)
[12:59:44] <SWPadnos> I don't know how you could tell the OS/BIOS to ignore a PS/2 keyboard though
[13:00:04] <SWPadnos> I don't think that's the fault of the keyboard driver
[13:00:37] <micges> I know
[13:00:57] <micges> but delay can be removed when keyb stuff will be in rt
[13:01:03] <SWPadnos> you can plug in a second keyboard (make sure it's a different brand), then load the hal_input driver for that keyboard
[13:01:36] <micges> oh I didn't know that
[13:01:55] <micges> so hal_input is generic input driver ?
[13:02:09] <SWPadnos> put a + sign before the name, and hal_input will prevent the OS from seeing anything on the device
[13:02:11] <SWPadnos> yes
[13:02:31] <SWPadnos> it supports most any device that the Linux input layer supports
[13:02:45] <SWPadnos> (joysticks, keyboards, joypads, mice ...)
[13:03:05] <SWPadnos> there are some issues with some devices though, so test first
[13:03:17] <micges> ok
[13:03:25] <micges> SWPadnos: thanks
[13:03:27] <SWPadnos> sure
[13:03:38] <SWPadnos> plug in a SpaceNavigator for a really good time :)
[13:03:56] <SWPadnos> http://www.3dconnexion.com/3dmouse/spacenavigator.php
[13:04:36] <micges> heh, I have few of simmilar stuff :)
[13:04:52] <micges> if I have time I'll test it :)
[13:04:54] <micges> bbl
[13:06:31] <SWPadnos> see you
[13:31:10] <skunkworks> There isn't any access to the led's on the mesa 5120 board - is there? (I don't see any link)\
[13:31:14] <skunkworks> (in hal)
[13:43:26] <SWPadnos> hmmm. there used to be
[13:43:50] <SWPadnos> the m5i20 driver had a single byte that would set the LED pattern
[13:43:59] <SWPadnos> which may have been changed to a set of bits at some point
[13:45:49] <SWPadnos> hey skunkworks, you have a couple of the D945GCLF2 boards, right?
[13:47:27] <skunkworks> yes
[13:47:29] <skunkworks> 3
[13:47:45] <SWPadnos> ok. I may have some questions for you as the day goes on
[13:47:51] <SWPadnos> I think I'll be ordering 15 or so today :)
[13:48:12] <skunkworks> http://pastebin.ca/1413253
[13:48:16] <skunkworks> heh
[13:48:33] <SWPadnos> I should design a small case that lets you use a single PCI card and a mini ITX motherboard, but which isn't the size of a medium pizza box
[13:48:34] <skunkworks> wow - 15?
[13:49:04] <SWPadnos> yep
[13:49:29] <skunkworks> I have xp on one - emc/hardy on another - and one is in the box.
[13:49:31] <SWPadnos> do you have access to any of them over the course of the day?
[13:49:55] <skunkworks> I have access to the hardy one for sure. The one in the box could be hooked up also
[13:50:15] <SWPadnos> ok, cool. I may ask you to run some benchmarks or power checks or something, if that's OK
[13:50:25] <skunkworks> not a problem
[13:50:41] <SWPadnos> oh - actually there is one thing I'd like to see if you have a minute :)
[13:50:47] <skunkworks> you may have to talk very slow..
[13:50:47] <SWPadnos> (it starts already ;) )
[13:50:49] <skunkworks> heh
[13:50:50] <skunkworks> sure
[13:50:51] <SWPadnos> no problem
[13:51:07] <SWPadnos> there are 4 USB ports on the back and two additional headers, right?
[13:51:41] <skunkworks> yes
[13:52:14] <SWPadnos> if you have a USB2 device, like a camera or external hard drive, I'd love to know where those ports connect internally
[13:52:39] <SWPadnos> the cipset has only one USB2 controller and 4 USB 1.1 controllers, which are internally connected through a crossbar switch
[13:52:43] <SWPadnos> chipset
[13:53:05] <skunkworks> I have a both.
[13:53:30] <skunkworks> So you want me to connect the camera to each port and give you some sort of feedback?
[13:53:34] <SWPadnos> the way to test this is to run lspci -v once before plugging anything in, and then run lspci (no -v) when the device is plugged into each socket
[13:53:37] <SWPadnos> yep
[13:54:01] <SWPadnos> actually, the lspci -v may not be necessary
[13:54:41] <SWPadnos> err. of course I meant to say lsusb every time I said lspci :)
[13:56:31] <skunkhardy> http://pastebin.ca/1413258
[13:56:35] <skunkhardy> nothing plugged in
[13:56:42] <skunkhardy> did you need the -v?
[13:57:36] <SWPadnos> no, but I should have been saying lsusb instead of lspci :)
[13:58:04] <skunkhardy> heh - hold on
[13:58:40] <SWPadnos> I have a benchmark that several people ran before - I'll get some instructions together if you'd like to run it (image processing - easy stuff :) )
[13:58:55] <skunkhardy> http://pastebin.ca/1413261
[13:59:02] <SWPadnos> jmk did this on his board, but I can't seem to find the numbers
[13:59:19] <SWPadnos> hmmm
[13:59:31] <SWPadnos> oh right, this is the RTAI kernel, isn't it
[13:59:43] <SWPadnos> hmmm
[13:59:54] <skunkhardy> yes - I could download the livecd from ubuntu
[14:00:07] <SWPadnos> or install the generic kernel and reboot :)
[14:00:08] <skunkhardy> if you like. (I am here all day)
[14:00:10] <SWPadnos> heh
[14:00:40] <skunkhardy> also - I don't have any headers plugged into the motherboard at the moment.
[14:00:49] <skunkhardy> sure - is that easy?
[14:01:09] <cradek> jepler: how do you get networking to the beagle?
[14:01:14] <SWPadnos> http://pastebin.ca/1413264
[14:01:19] <jepler> cradek: USB
[14:01:28] <SWPadnos> lsusb output on jaunty, with all the information you could ever need :)
[14:01:43] <SWPadnos> I think there may be a PCI ID database that you're missing (or something like that)
[14:01:48] <SWPadnos> grr
[14:01:50] <SWPadnos> USB ID
[14:02:53] <SWPadnos> in any case, lsusb -v should tell us which of those root hubs (BUS numbers) is the 2.0 controller
[14:03:08] <SWPadnos> and once that's known, a simple lsusb will tell which hub the device is plugged into
[14:03:33] <SWPadnos> (the bus number of the device will be the hub it's connected to)
[14:03:53] <skunkhardy> http://pastebin.ca/1413268
[14:04:15] <SWPadnos> .ca is almost an rss feed now
[14:04:17] <cradek> jepler: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=WM19090-ND ?
[14:04:18] <skunkhardy> do I need to sudo?
[14:04:23] <SWPadnos> err. pastebin.ca
[14:04:28] <SWPadnos> no, shouldn't
[14:05:02] <SWPadnos> bus 5 is the USB2 one
[14:05:34] <SWPadnos> you can see that on line 5: bcdUSB 2.00
[14:05:43] <SWPadnos> the others are all 1.10
[14:06:15] <skunkhardy> upper left rear
[14:06:17] <skunkhardy> http://pastebin.ca/1413271
[14:06:20] <jepler> cradek: I bought a HDMI-HDMI cable, but that cable would work if you had a monitor with DVI input. I think dit has them for less (6' about $9)
[14:06:36] <cradek> thanks
[14:06:55] <jepler> http://ditcorp.com/itemdesc.asp?ic=CBLGENHDMDVI%2D06&eq=&Tp= http://ditcorp.com/itemdesc.asp?ic=CBLGENHDMI%2D06&eq=&Tp=
[14:06:58] <SWPadnos> hmmm. is that quickcam a USB2 device?
[14:07:17] <jepler> cradek: you're thinking about your media player project?
[14:07:25] <cradek> yeah
[14:07:27] <skunkhardy> my thumbdrive is usb 2 - I will use that.
[14:07:52] <cradek> I'm a little worried about getting the old software to build on it. The alternative is to start from scratch I guess.
[14:08:01] <SWPadnos> skunkworks, thanks
[14:08:15] <SWPadnos> maybe do lsusb -v, just for the heck of it
[14:08:57] <jepler> cradek: what software does it need?
[14:09:03] <jepler> cradek: festival, mpg123?
[14:09:08] <cradek> hacked festival, hacked mpg123
[14:09:36] <jepler> how much can they have changed in the meantime? both projects must be just about finish
[14:09:40] <jepler> ed
[14:09:50] <jepler> do you have source trees? I can try building them for you
[14:10:42] <cradek> I'll have to really dig around for them... or maybe firing up the old machine, if it'll boot, would be easier.
[14:11:00] <SWPadnos> or connect the hard drive to another machine
[14:13:51] <cradek> looks like my interface is currently 5 input bits
[14:14:06] <cradek> are there 5 bits somewhere that I can read directly with an inb?
[14:14:15] <SWPadnos> parport?
[14:14:41] <cradek> oh, I didn't think it had one
[14:14:48] <jepler> cradek: there are 18(?) GPIOs on the expansion header but they are 1.8V so you have to build level converting hardware
[14:15:07] <SWPadnos> oh - sorry. forgot you were talking about the beagleboard :)
[14:15:22] <SWPadnos> and here I was looking up cross-compilation information for it
[14:15:39] <jepler> I haven't tested the board I made for that purpose, but here's an 8-line equivalent to the part I used: http://focus.ti.com/docs/prod/folders/print/txb0108.html
[14:15:46] <skunkhardy> did you want this? http://pastebin.ca/1413274
[14:16:04] <jepler> you hook the low voltage signals and low vcc to one side, the high voltage signals and high vcc to the other, and you're done
[14:16:16] <cradek> seems like I could just use five zeners
[14:16:33] <SWPadnos> skunkworks, yeah - that's the kind of thins I'm looking for
[14:16:44] <jepler> you could find an LED with a ~1.6V forward voltage, then you get indicators for free
[14:16:59] <skunkhardy> SWPadnos: I didn't look - is the camera 2.0?
[14:17:17] <SWPadnos> it says 1.10, but I don't know if that's because of the camera or the bus
[14:17:23] <skunkhardy> heh
[14:17:27] <skunkhardy> hold on
[14:17:30] <SWPadnos> it's better to check with a known USB2 device
[14:17:55] <SWPadnos> it does look depressing though - if the back panel connectors are connected to USB1 hubs, that's a problem for me
[14:19:45] <jepler> according to the datasheet, acceptable high-level inputs are 1.17v-2.0v for vdds=1.8v (vdds*.65 to vdds+.3)
[14:19:46] <skunkhardy> heh - this is plugged intot he same port
[14:19:47] <skunkhardy> http://pastebin.ca/index.php
[14:19:55] <skunkhardy> (upper left)
[14:19:55] <SWPadnos> err
[14:20:18] <SWPadnos> ah, interesting
[14:20:39] <SWPadnos> I wonder if the crossbar is automatic
[14:20:49] <SWPadnos> I thought it was set up by hardware pins/BIOS
[14:21:04] <skunkhardy> do you want me to run my cruser around to each port and give you a lsusb -v?
[14:21:09] <SWPadnos> please
[14:21:14] <skunkhardy> ok
[14:21:14] <cradek> hmm, it has rs232...
[14:21:24] <SWPadnos> and the motherboard ones, if you have a suitable adapter for them
[14:21:28] <cradek> RI, DCD, CTS, DSR, RD = 5
[14:21:35] <cradek> not sure if RD can be read directly though
[14:21:37] <SWPadnos> RD can't be read directly
[14:21:42] <cradek> dang
[14:21:59] <SWPadnos> however, the serial port is probably also GPIO, if you set it up right
[14:22:10] <jepler> cradek: it only has RX and TX
[14:22:23] <cradek> oh, ok
[14:22:28] <cradek> not much of a cheese shop then, is it
[14:22:38] <jepler> here's an example use of GPIO pins: http://linuxjunk.blogspot.com/2009/01/beagleboard-gpio-input-driverless.html
[14:23:10] <SWPadnos> since the OMAP is a big microcontroller, you should be able to use most any pin for GPIO (assuming it's brought to a connector of some sort, with minimal hardware in between)
[14:23:22] <jepler> (maybe not the best example!)
[14:23:30] <skunkhardy> SWPadnos: lower left http://pastebin.ca/1413286
[14:23:56] <skunkhardy> is this going to help - or do I need to plug in 8 devices? ;)
[14:24:02] <SWPadnos> hmmm.
[14:24:12] <SWPadnos> if you have 8 device, that would also be interesting :)
[14:24:18] <skunkhardy> I might.
[14:24:25] <SWPadnos> cool
[14:24:51] <jepler> another example of gpio access, through /sys/class/gpio: http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html
[14:25:29] <skunkworks> Give me a few - I need to find motherboard usb plugs.
[14:25:31] <cradek> if I plugged in a usb parport cable and let the kernel do its normal thing, could I read the five inputs with inb?
[14:25:48] <SWPadnos> skunkworks, thanks a bunch
[14:26:24] <jepler> cradek: no, not with inb
[14:27:20] <jepler> this device would let you get some 3.3v or 5v I/Os on USB, but again you can't read them with inb(): http://www.sparkfun.com/commerce/product_info.php?products_id=718
[14:27:35] <jepler> some kind of ioctls, I think
[14:28:37] <jepler> for a parport cable, see the ioctls in /usr/include/linux/ppdev.h
[14:29:06] <jepler> unsigned char bits; ioctl(/dev/parport0, PPRDATA, &bits)
[14:29:14] <jepler> something like that, there's probably more setup to do
[14:29:29] <cradek> ah, that's simple
[14:29:42] <cradek> as long as I can do it from C without too much bizarreity
[14:29:59] <jepler> I have a USB parallel cable if you want one
[14:30:02] <jepler> never used
[14:30:09] <jepler> I'm 95% sure those ioctls will work on usb parports
[14:30:36] <cradek> that would let me just plug it in. (the less I have to mess with the avr interface board, the better)
[14:30:42] <SWPadnos> do you (any of you) want some parts from DigiKey that aren't worth spending the $5 handling fee on?
[14:30:54] <SWPadnos> (since you're talking about IO level shifting and stuff ...)
[14:30:59] <jepler> that you'd bring to workshop?
[14:31:03] <SWPadnos> yep
[14:31:26] <SWPadnos> I'm placing an order today or tomorrow, and will probably place another one early next week
[14:31:58] <jepler> let me see how much I'd be spending to get the parts to make proper ribbon cables for my project
[14:32:16] <SWPadnos> heh
[14:32:28] <SWPadnos> how many conductors?
[14:32:40] <jepler> I need a 28-28, a 26-26, and a 50-50, one each
[14:32:49] <SWPadnos> all relatively short, I imagine
[14:32:55] <jepler> yeah
[14:33:25] <SWPadnos> so you could take a couple of those old useless IDE or floppy cables and use them for the 26 and 28
[14:33:33] <SWPadnos> oh, 0.1 spacing or 2mm?
[14:33:44] <jepler> the one of the 26.01
[14:33:55] <jepler> argh, what was that
[14:33:57] <jepler> 0.1 spacing
[14:34:06] <jepler> one of the 26p connectors is shrouded, so that one has to be "right"
[14:34:21] <cradek> hacksaw
[14:35:44] <jepler> initially I'll just use http://www.sparkfun.com/commerce/product_info.php?products_id=8430 for the 26 and 28p connectors, and a 50p cable that's just too long
[14:36:08] <jepler> there are only 7 and 6 lines used on the 28 and 26 connectors
[14:36:22] <micges> anyone know if is it planned to add stepgen velocity mode for hostmot2 ?
[14:36:25] <cradek> I can shorten the 50 for you if you don't feel up to it.
[14:36:26] <SWPadnos> hmmm. cool. I may need some of those :)
[14:36:40] <jepler> oh I don't have a lot of spares
[14:36:50] <jepler> I'll try to remember to toss them in the stuff I bring though, if you think they'd be handy
[14:36:57] <SWPadnos> they're expensive at DigiKey (I think)
[14:37:08] <SWPadnos> oh, I was thinking of getting 20 or 30 to have around
[14:38:53] <jepler> SWPadnos: seb lives right by sparkfun, and I think he's even offered to bring stuff from there to fest
[14:38:58] <jepler> SWPadnos: if you want some, maybe you should contact him
[14:39:05] <SWPadnos> oh, excellent. thanks
[14:41:41] <jepler> and tell him I need a https://www.sparkfun.com/commerce/product_info.php?products_id=8548
[14:42:46] <SWPadnos> heh. new phone? :)
[14:43:18] <jepler> SWPadnos: newish phone, yes
[14:43:29] <jepler> not useful for communication, but it beats bringing a wall wart as a charger
[14:43:42] <SWPadnos> yep
[14:43:53] <jepler> (I have one at the office and last time I went on a trip I forgot to pack it.. packed a mini b by mistake)
[14:44:06] <SWPadnos> I replaced the battery in my phone, so I get to keep using a mini-USB cable for that
[14:50:52] <SWPadnos> actually that was an interesting experiment. both my phone and my wifes had maybe 10 minutes talk time, most of a day standby (unless you talk - you get more like 1-2 minutes at the end of the day), trouble making calls, dropped calls, etc
[14:51:02] <SWPadnos> all those problems were fixed with new batteries
[14:51:11] <jepler> interesting
[14:51:28] <SWPadnos> even a problem where you'd dial, and the phone would sit there for about 30 seconds, then say "call failed"
[14:51:30] <SWPadnos> yeah
[14:51:46] <SWPadnos> and the total cost was $30 or so, including shipping (not Motorola brand, of course)
[14:52:28] <SWPadnos> I left my phone on for most of a week, and talked for about 1.5-2 hours on it on a single charge
[14:52:34] <SWPadnos> (with the new battery, of course)
[14:52:57] <jepler> huh, a 28p idc connector is $10, while a 26p idc connector is <$2. I guess volume does make a difference.
[14:57:43] <SWPadnos> interesting - they don't even carry 28-conductor ribbon cable
[14:58:13] <SWPadnos> which may explain why the connectors are so expensive (they also appear to be individual crimp style - the photos are not like "normal" ribbon connectors)
[14:58:25] <jepler> oh I didn't look at that
[14:59:53] <SWPadnos> where does the 28-pin cable go?
[15:00:00] <jepler> SWPadnos: from beagleboard to level-converter board
[15:00:05] <SWPadnos> hmmm
[15:00:17] <jepler> no shrouds, so I'll probably use a floppy cable (34p) there
[15:00:40] <SWPadnos> yep
[15:00:53] <jepler> order me 4 of D89126-0131HK
[15:01:27] <jepler> that gets me one cable plus two mistakes, which is probably about par for the course
[15:02:28] <jepler> bbl
[15:14:13] <SWPadnos> damn. DigiKey is pretty expensive for cable assemblies: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=SAM8235-ND
[15:14:57] <SWPadnos> it's only $1.24 more for hte 6" model
[15:15:00] <SWPadnos> the
[15:16:38] <skunkhardy> SWPadnos: all 4 in back filled
[15:16:40] <skunkhardy> http://pastebin.ca/1413339
[15:16:51] <SWPadnos> great. thanks
[15:18:01] <SWPadnos> got a kill-a-watt meter handy? :)
[15:18:14] <SWPadnos> (or another way of measuring power draw)
[15:18:46] <skunkhardy> heh - no. I could measure current at the power supply though. I could borrow the fluke from the shop.
[15:19:13] <SWPadnos> are you using a normal AT supply, or some DC-DC thing?
[15:20:01] <skunkhardy> normal cheap at power supply
[15:20:51] <SWPadnos> hmmm. ok - nevermind the power calcs :)
[15:21:01] <SWPadnos> did you install a generic (SMP) kernel?
[15:22:06] <skunkhardy> whatever is on the live cd
[15:22:10] <SWPadnos> ok
[15:22:41] <SWPadnos> actually, I think Eric Johnson (?) made a SMP RTAI kernel for 8.04 - you could give that a try at some point
[15:23:00] <SWPadnos> hmmm. I think I need to put the latest one on linuxcnc.org, come to think of it
[15:24:03] <skunkhardy> ok. Hmm - either the plug that I have to hook into the motherboard isn't standard or I am having problems with it seeing devices plugged into the motherboard headers
[15:24:37] <SWPadnos> no biggie. the 4 external ports are all capable of USB2, which is the main info I was looking for
[15:25:04] <skunkhardy> ok - good :)
[15:25:36] <SWPadnos> so, install dcraw (you may have to enable "universe" to see it), download http://www.thothsystems.com/images/dsc_0291.nef and tell me the output of "time dcraw -q 3 dsc_0291.nef" :)
[15:25:44] <SWPadnos> before lunch! ;)
[15:26:04] <skunkhardy> heh
[15:26:05] <skunkhardy> ok
[15:26:16] <SWPadnos> thanks again. I owe you a Red Bull or something ;)
[15:27:08] <skunkhardy> not a problem. Least I can do.
[15:28:56] <jepler> SWPadnos: what's a good dcraw score?
[15:29:05] <SWPadnos> hmmm. good question
[15:29:38] <jepler> 5s here
[15:30:01] <skunkhardy> http://pastebin.ca/1413349
[15:30:45] <SWPadnos> ok, that's about the same as my A64 X2 4850e system
[15:30:53] <jepler> phenom 9600, so you should be able to do 4 in 5 seconds
[15:30:53] <skunkhardy> cool picture of the 7i31 ;)
[15:32:15] <SWPadnos> ok, those numbers are very close to jmk's numbers (I finally found them)
[15:32:17] <skunkworks> btw - dcraw was already installed.
[15:32:34] <SWPadnos> if you do it > /dev/null, it may be a little faster, but the user number will be about the same
[15:32:35] <skunkworks> heh - good. At least I am not screwing things up ;)
[15:32:40] <SWPadnos> nope, not yet ;)
[15:33:28] <SWPadnos> I did a multicore test by doing "time (dcraw ... & dcraw ... & wait)
[15:33:31] <SWPadnos> "
[15:33:36] <SWPadnos> add more dcraws for more cores
[15:33:54] <SWPadnos> ends up about the same wall time, which is nice (and expected)
[15:34:49] <skunkworks> is this for your camera project?
[15:35:03] <SWPadnos> yep
[15:35:27] <skunkworks> cool
[15:35:52] <SWPadnos> I sure hope so - I have to get it working for a demo in Dallas by the end of next week :)
[15:36:06] <skunkworks> he was also using the single core kernal - right? would smp help?
[15:36:07] <SWPadnos> so we can use it for an event at the end of the month
[15:36:19] <SWPadnos> SMP helps in that you can process two images at once
[15:36:25] <skunkworks> ah
[15:36:57] <SWPadnos> luckily these computers will only be connected to 4 cameras each, so the total time should be relatively quick
[15:37:21] <SWPadnos> which interface does your primary hard drive use? (IDE or SATA)
[15:37:31] <skunkworks> It is hooked into sata
[15:37:41] <skunkworks> 500gb seagate
[15:38:03] <SWPadnos> ok. could you time a large-ish file transfer from a USB-connected hard disk?
[15:38:13] <skunkworks> sure
[15:38:26] <SWPadnos> just cat $BIG_USB_FILE > /dev/null
[15:38:44] <SWPadnos> err - time cat ... :)
[15:43:01] <skunkhardy> SWPadnos: how do I do it if the file name is ESTIDATA.MDB?
[15:43:32] <skunkhardy> cat: .MDB: No such file or directory
[15:43:33] <SWPadnos> time cat /path/to/USB/drive/ESTIDATA.MDB > /dev/null
[15:43:37] <skunkhardy> ah
[15:43:49] <SWPadnos> use tab completion - it helps :)
[15:44:00] <SWPadnos> how big is that file?
[15:44:14] <skunkworks> close to 1gb
[15:44:20] <SWPadnos> perfect
[15:44:26] <skunkworks> I will get the info when it is done
[15:44:35] <SWPadnos> nice. thanks again
[15:44:42] <SWPadnos> should be a minute or two I guess
[15:45:28] <skunkhardy> http://pastebin.ca/1413353
[15:45:44] <SWPadnos> hmmm. no, theoretical 17 seconds, but could be limited by the actual read speed of the drive
[15:45:57] <SWPadnos> ok, not bad - 50% fill factor or thereabouts
[15:46:30] <SWPadnos> thanks. brb
[15:54:03] <jepler> recompiling dcraw with -mtune=native trims a little bit of time off (consistently just under 5s wall, instead of just over)
[15:56:26] <SWPadnos> huh - does native check the CPU and set things automatically?
[15:56:50] <SWPadnos> the actual application will be imagemacick actually, so I'll have to see what can be done there
[15:58:18] <jepler> 4 in parallel take about 5.5s wall
[15:58:43] <SWPadnos> cool. is that to /dev/null?
[15:58:54] <jepler> no, to the same default output file
[15:59:19] <SWPadnos> could you try it to /dev/null?
[15:59:22] <SWPadnos> just curious
[16:01:17] <jepler> it makes less of a difference than run-to-run differences
[16:01:34] <SWPadnos> oh. cache effects I guess
[16:04:17] <SWPadnos> interesting - mtune=native will optimize for the native CPU, but will not cause architecture-specific instructions to be used
[16:04:26] <SWPadnos> you need to add -march for that
[16:04:50] <SWPadnos> so -mtune=native -march=native could give a better result
[16:06:56] <jepler> using sched_setaffinity to make each instance run on a different core also doesn't make enough difference to measure
[16:07:09] <SWPadnos> oh. thanks for checking
[16:07:23] <jepler> -march=native also doesn't make a difference that can be measured
[16:07:40] <jepler> you could always try intel's icc too
[16:07:46] <jepler> I hear there's a version that's free to use
[16:08:37] <SWPadnos> hmmm - haven't seen that (the free-ish one)
[16:09:08] <SWPadnos> I'll leave those optmizations until after I have the computers, the networking, the control software, and the storage systems figured out :)
[16:17:16] <jepler> SWPadnos: thanks for looking for preassembled cables, but a 2" cable is too small anyway -- to avoid putting a twist in the cable, I end up having to pass it under the led board.
[16:17:42] <SWPadnos> yeah - you probably need 6-8" or so
[16:18:47] <SWPadnos> hmmm. are you referring to the cable that's installed in the photo?
[16:18:53] <jepler> yeah
[16:19:06] <SWPadnos> strange. it shouldn't need a twist
[16:19:18] <jepler> mounted that way, it doesn't
[16:19:22] <SWPadnos> ah
[16:19:34] <jepler> I originally had the 7i31 rotated 180 degrees
[16:19:37] <SWPadnos> yah, you';d still need a 6-8" cable if you wanted to put a twist in it :)
[16:20:18] <jepler> the other option is to swap the 7i43 and 7i31 so that the cable passes over the 7i43 which I don't need to see
[16:21:05] <SWPadnos> yeah, but you may need the second connector some day
[16:47:54] <BJT-Work> BJT-Work is now known as BJT-Gone-Fishing
[17:17:54] <alex_joni> this sounds like an AXIS bug: http://www.linuxcnc.org/component/option,com_kunena/Itemid,20/func,view/catid,10/id,208/lang,en/#212
[17:22:34] <cradek> or task
[17:22:40] <cradek> well, probably both
[17:22:47] <cradek> or motion
[17:22:49] <cradek> or all three
[17:22:50] <cradek> ha
[17:23:38] <alex_joni> I thought incremental/continous is a GUI thing, not task atm
[17:24:07] <cradek> well there's an incremental jog nml message. if getting it in teleop mode makes it go forever, that's not a gui issue (except the gui shouldn't have sent it either)
[17:24:36] <alex_joni> yeah, that
[17:24:42] <alex_joni> * alex_joni agrees on all three :D
[17:25:07] <alex_joni> otoh, I don't plan on working on this, except if we take on designing it from the beginning
[17:25:15] <cradek> I think at fest jmkasunich is going to work on the free planner vs teleop.
[17:25:34] <cradek> he has a new design, and part of it is even done (isolation of the free planner)
[17:26:20] <alex_joni> it would be great if you can come up with a design for jogging (both joint and world) at fest
[17:26:36] <cradek> afaik, the design is done
[17:26:45] <cradek> now, SMOP
[17:27:26] <alex_joni> I'm ok to do the SMOP, but haven't seen the design :)
[17:27:55] <alex_joni> and I started without on joints_axes, and got mudded in
[17:27:58] <cradek> I think: have a free mode planner including jog wheel for each joint and each axis
[17:28:46] <cradek> so you get continuous, incremental, and wheel jogs in both joint and world
[17:28:56] <cradek> jmkasunich would remember the details - he even has a drawing of it I think
[17:30:42] <alex_joni> jog wheel for axis will probably be a bit harder to do
[17:30:59] <alex_joni> but it's probably similar to incremental jogging
[17:32:01] <cradek> conceptually it doesn't seem hard: send the new axis position through kins, set the new joint commanded positions accordingly
[17:32:54] <alex_joni> hmm.. right
[17:32:56] <cradek> hm, I am now realizing that I don't know the design
[17:33:11] <cradek> I hope he can find our notes from a year (?) ago.
[17:33:29] <alex_joni> well, if you come up with anything, I'd be glad to help coding
[17:33:40] <cradek> thanks
[17:33:45] <cradek> will you be around during fest time?
[17:33:57] <alex_joni> when is it again?
[17:34:04] <alex_joni> but yeah, most likely I'm around
[17:34:50] <cradek> 21-28 I think
[17:34:53] <alex_joni> right
[17:50:01] <cradek> jepler: carrier no; hardflow no
[17:51:50] <jepler> cradek: in cu?
[17:52:09] <cradek> in 'port'
[17:53:01] <cradek> I think there's no way to tell cu except by using the uucp config files
[17:54:12] <jepler> this doesn't seem to be documented in the cu manpage..
[17:54:22] <jepler> anyway, qq was quick to write
[17:55:02] <cradek> I think maybe it's a mistake to think cu can be separated from the rest of the uucp package
[17:55:32] <cradek> although I understand why they did it.
[17:56:36] <jepler> for users like me who want a simple terminal program, I imagine
[17:57:24] <cradek> yeah
[17:57:42] <cradek> like you said, the choices are minicom (crappy qmodem clone) and cu
[18:00:50] <jepler> it sounds like the only thing missing from cu is a bit of documentation, and I'd have been happy
[18:01:11] <jepler> or maybe the proper signal loopbacks in my serial adapter
[18:01:21] <cradek> it's in the manpages, but they are in the uucp package
[18:01:41] <cradek> err, maybe in the info
[18:01:48] <cradek> grr gnu
[19:25:22] <BJT-Gone-Fishing> BJT-Gone-Fishing is now known as BJT-Work
[20:11:20] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/src/hal/components/joyhandle.comp: documentation markup fixes
[20:14:16] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/docs/src/lyxtree.py: when building lyx documentation into html, convert to the version that lyxtree knows how to handle
[20:18:04] <alex_joni> heh, that's fun to read when you're tired: '/usr/share/lyx/lyx2lyx/lyx2lyx'
[20:19:30] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/docs/src/lyxtree.py: apply the conversion to lyx files included from the main lyx file
[20:32:04] <jepler> huh, that's a good trick -- whenever I exit lyx it kills my window manager (icewm)
[20:32:34] <alex_joni> huh
[20:32:46] <alex_joni> does it restart at least?
[20:32:50] <jepler> yeah
[20:34:43] <alex_joni> wonder how it manages to do that.. (kill icewm)
[20:36:25] <alex_joni> huh, they changed the design for SF again
[20:50:20] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/src/ (configure configure.in): switch to lyx 1.5.x for documentation
[20:50:21] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/docs/src/lyxdep.py: switch to lyx 1.5.x for documentation
[20:50:59] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/docs/src/README: switch to lyx 1.5.x for documentation
[22:56:35] <skunkworks> This is cool http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&ssPageName=STRK:MEWAX:IT&item=110256821264
[22:56:57] <skunkworks> I have seen pictures of it in computer books explaining cnc
[22:57:09] <SWPadnos> heh. fennville - fenn ought to move there :)
[23:01:07] <jepler> let's move this over here
[23:01:07] <jepler> $ inivar -var Y -sec X -ini badly.ini | od -a
[23:01:07] <jepler> 0000000 Z cr Y = W nl
[23:01:14] <jepler> yeah, a similar problem exists for inifiles
[23:02:58] <jepler> (I'm not sure what dos2unix will do with X^MY though ...)
[23:03:06] <SWPadnos> good question
[23:03:33] <SWPadnos> you can do things like sed s/^M/\r/g can't you?
[23:04:48] <CIA-47> EMC: 03jepler 07TRUNK * 10emc2/src/hal/utils/halcmd.c:
[23:04:48] <CIA-47> EMC: detect errant carriage return codes and signal the user about it
[23:04:48] <CIA-47> EMC: "goslowjimbo" presented us with a hal file which had a sequence like
[23:04:48] <CIA-47> EMC: net ....^Mnet ...
[23:04:48] <CIA-47> EMC: which was intended to be two lines. This case is now an error. DOS-style line
[23:04:49] <CIA-47> EMC: endings (^M^J) are a warning, but won't stop executing the HAL file.
[23:04:53] <CIA-47> EMC: backport candidate
[23:05:13] <SWPadnos> durr. of course ^M is "an M at the beginning of the line" :)
[23:05:16] <jepler> I shudder to think about getting an inexperienced user to type the right thing at the commandline
[23:05:37] <jepler> dos2unix isn't on a base system?
[23:05:52] <SWPadnos> nope
[23:05:58] <SWPadnos> it's part of "tofrodos"
[23:16:31] <SWPadnos> skunkworks, is it just me, or does that machine look like it's got a giant handwheel on top of it
[23:42:13] <skunkworks405> SWPadnos: giant jog wheel
[23:42:17] <SWPadnos> yep
[23:42:23] <SWPadnos> that's what it looks like to me :)
[23:42:24] <skunkworks405> ;)
[23:44:21] <skunkworks405> http://www.nit.ac.jp/center/museum/tenji/width450/kosaku/14.jpg
[23:44:51] <cradek> looks like something from star wars
[23:45:26] <SWPadnos> yeah, the little lightsaber defense practice droid
[23:45:33] <SWPadnos> on a machining center
[23:57:34] <skunkworks405> that would fit in the corner of the garage... ;P