#emc-devel | Logs for 2006-01-26

[01:24:08] <rayh> back
[01:24:24] <SWPadnos> phone
[01:37:48] <SWPadnos> ok - I'm mostly back as well
[01:38:47] <rayh> incoming 900 number?
[01:38:52] <SWPadnos> I wish
[01:38:59] <rayh> me to
[01:39:17] <SWPadnos> a friend trying to get Windows XP to run for more than 14 seconds without getting a virus ;)
[01:39:32] <rayh> Were you thinking of writing the ini conversion program using c++
[01:39:43] <SWPadnos> C or C++ probably
[01:39:44] <rayh> keep xp off line
[01:40:01] <SWPadnos> actually, the problem started before he plugged in the network cable
[01:40:04] <rayh> So a line by line conversion
[01:40:09] <SWPadnos> maybe it was a floppy or CD
[01:40:17] <SWPadnos> sort of
[01:40:25] <rayh> ah. itunes, sony, or ms
[01:40:31] <SWPadnos> I was thinking more that there should be a configuration file for the translator
[01:40:49] <rayh> a rule set.
[01:40:55] <SWPadnos> yep
[01:41:16] <SWPadnos> with snippets of hal and/or ini code that get pasted into the output file(s) wen certain things are found in the input ini file
[01:41:18] <rayh> something like the file you built for kbuild demo
[01:41:37] <SWPadnos> hmmm - I'm not sure about that
[01:42:12] <rayh> Paul is working toward xml for config stuff.
[01:42:17] <SWPadnos> really?
[01:42:24] <SWPadnos> I thought he was opposed to that???
[01:42:31] <rayh> yup on the BDI fork
[01:42:40] <SWPadnos> cool. we should sync up
[01:42:48] <rayh> Was till he built a demo for a LUG meet.
[01:43:00] <SWPadnos> heh - probably was 100x easier to configure
[01:43:07] <rayh> * rayh looks for the parser he used.
[01:43:18] <SWPadnos> I think it was libxml or something
[01:45:23] <SWPadnos> I really like the KDE-style config management scheme
[01:45:36] <SWPadnos> too bad the standalone library is unmaintained
[01:48:36] <rayh> xpat
[01:48:49] <rayh> expat?
[01:49:08] <rayh> short memory, switches with my kvm
[01:49:09] <SWPadnos> good question
[01:49:13] <SWPadnos> hweh
[01:49:15] <SWPadnos> heh
[01:49:42] <rayh> yep expat is it.
[01:50:05] <SWPadnos> yep
[01:50:46] <rayh> He also favors using autotools nowadays.
[01:51:03] <SWPadnos> that's the step above ./configure?
[01:51:23] <rayh> He calls it's advantage building "selective systems."
[01:51:49] <SWPadnos> yep - better tuned configs for the specific build environment
[01:52:10] <rayh> I tried to talk us into selective builds for EMC
[01:52:31] <SWPadnos> yep - that's one of hte things the KBuild stuff was aimed at
[01:52:53] <SWPadnos> "don't build ppmc, because it doesn't compile, and I don't need it anyway"
[01:53:09] <rayh> buthey...
[01:53:13] <SWPadnos> heh
[01:53:24] <SWPadnos> nothingevergoesasplanned
[01:53:34] <rayh> the configure stuff is a big step forward.
[01:53:42] <SWPadnos> yep
[01:54:13] <rayh> it's amazing how you have to think "don't tick the spacebar, thumb."
[01:54:23] <SWPadnos> heh
[01:54:59] <SWPadnos> eventually (maybe in the 2.4 or 2.6 timeframe), we may be able to make a new emcHALsh, plus an extended VCP-like thing, and get the last "feature" of mach off our bnacks - configurable screens
[01:55:08] <SWPadnos> backsd
[01:55:10] <SWPadnos> backs
[01:55:56] <rayh> then there is vtcl with an EMC enabled lib
[01:56:08] <SWPadnos> emc or emc2?
[01:56:20] <SWPadnos> I think that's what I meant with emcHALsh
[01:56:31] <rayh> I made it originally for emc but it would work equally well with 2
[01:56:49] <SWPadnos> ie, emcsh + HAL in tcl-usable form, with UI controls that are placed from a config file
[01:58:20] <rayh> One has to be careful about direct applications to hal.
[01:58:33] <SWPadnos> how so?
[01:58:35] <rayh> witness the recent "weaving" discussion.
[01:59:03] <SWPadnos> sure, but I see that not as a HAL problem, but that emc isn't meant for what he wants
[01:59:08] <rayh> many times better control through gcode
[01:59:38] <SWPadnos> true, and the subroutine support makes the problem mostly moot
[02:00:25] <rayh> Yep. But because HAL is so damned accessable many view it as the first line of customization.
[02:00:35] <SWPadnos> true
[02:01:12] <SWPadnos> there is a slight breakdown between the "device driver" aspects and actual control software
[02:01:16] <rayh> btw if you put the weave generator between pid and motmod it works
[02:01:40] <SWPadnos> only if you allow the max weave offset as ferror
[02:02:00] <rayh> no because ferror is computed from pid input
[02:02:02] <SWPadnos> doesn't motion calculate its own ferror?
[02:02:12] <rayh> not that I see.
[02:02:19] <SWPadnos> odd. I thought it did
[02:03:25] <rayh> You are without a doubt much closer to truth there than I am.
[02:03:40] <SWPadnos> of course - I'm just telling you what I think ;)
[02:03:56] <SWPadnos> I may be totally wrong about pid/motion though
[10:50:59] <alex_joni> morning all
[11:19:14] <alex_joni> hey anders
[11:21:29] <anonimasu> hey
[11:21:31] <anonimasu> it's been a while
[11:23:56] <alex_joni> yeah.. didn't see you much lately
[11:25:19] <anonimasu> busy with life & work
[11:25:25] <anonimasu> mostly with life
[11:28:30] <alex_joni> nice
[11:31:45] <anonimasu> yeah
[11:31:51] <anonimasu> how are you doing?
[11:35:43] <anonimasu> I am rewriting this software again
[11:44:40] <alex_joni> hmm.. pretty ok
[11:44:43] <alex_joni> kinda busy
[11:45:15] <anonimasu> nice :)
[13:02:56] <cradek> good morning
[13:03:02] <cradek> alex_joni: on my new machine I get bug 1205237
[13:03:08] <cradek> (mode not switching)
[13:04:09] <cradek> from the bug report it looks like you know the most about it; do you have any idea what we should do next to figure it out?
[13:04:27] <cradek> btw make install/make deb work now
[13:07:36] <cradek> also jepler got the same behavior on his laptop
[13:19:45] <alex_joni> seen the make install stuff, nice
[13:20:08] <alex_joni> ok, now regarding to that bug, I didn't touch it in a while, and I don't have a machine now that does it
[13:23:21] <rayh> that bug?
[13:23:55] <rayh> Hi Alex.
[13:25:35] <alex_joni> 15:05 < cradek> alex_joni: on my new machine I get bug 1205237
[13:25:35] <alex_joni> 15:05 < cradek> (mode not switching)
[13:25:35] <alex_joni> 15:06 < cradek> from the bug report it looks like you know the most about it;
[13:25:35] <alex_joni> do you have any idea what we should do next to figure it out?
[13:25:35] <alex_joni> 15:06 < cradek> btw make install/make deb work now
[13:25:38] <alex_joni> 15:09 < cradek> also jepler got the same behavior on his laptop
[13:25:40] <alex_joni> 15:13 -!- rayh [n=swanlake@dial-pn1-17.wic.up.net] has joined #emc-devel
[13:26:24] <alex_joni> cradek: how fast is your debugging process on that machine? Is that your home machine?
[13:26:38] <rayh> thanks
[13:26:50] <alex_joni> cradek: how often does the bug appear? (only after a lot of mode-switches, or just after a few?)
[13:27:17] <alex_joni> cradek: last time I've seen that ( a few months ago iirc), I had to change modes like crazy (about 50-60 times till it locked)
[13:29:37] <alex_joni> * alex_joni is reading the bug notes to refresh his memory
[13:49:13] <cradek> alex_joni: yes it's my home machine, and it shows up immediately/always
[13:49:24] <cradek> I can switch modes 1-2 times and then it always hangs
[13:50:22] <alex_joni> ok, that's GOOD
[13:50:42] <alex_joni> I think it's some racing condition, that ends up in having those bits set wrong
[13:52:08] <cradek> that sounds like it won't be very fun to hunt down
[14:13:02] <rayh> What gui is the bug 1205237 reported on?
[14:13:30] <cradek> all
[14:13:35] <cradek> it's not a gui bug
[14:13:57] <rayh> EMC2?
[14:13:59] <cradek> yes
[14:14:19] <cradek> the problem is I've changed two things at once: I got a much faster computer and I switched to rtai
[14:14:21] <rayh> I've switched a couple thousand times here in the last 10 minutes and don't see anything with tkemc
[14:14:28] <cradek> so either of those might have been the cause
[14:14:59] <cradek> it happens for me with either gui after just a couple switches
[14:15:14] <cradek> it's a totally fatal bug
[14:15:27] <cradek> jepler gets the same thing on his (fast) laptop
[14:15:54] <rayh> Okay. This is bdi-4.30 with the 2.95.4 compiler
[14:16:10] <cradek> do you know which rtai version that is?
[14:16:17] <rayh> magma
[14:18:25] <cradek> my current guess is it's related somehow to machine speed
[14:18:36] <cradek> it might be hard to find.
[15:03:28] <alex_joni> oops.. sorry
[15:03:37] <alex_joni> was away for a while welding some pipes, back now
[15:04:21] <alex_joni> cradek: it is related to machine speed, but so far I've only seen it on very slow machines
[15:04:25] <alex_joni> on a PII-233
[15:06:27] <cradek> I think our machines are around 2GHz... also maybe it's worse with rtai3.3
[15:07:05] <alex_joni> don't think so
[15:07:12] <alex_joni> you at the machine now?
[15:07:15] <alex_joni> or only at home?
[15:07:51] <alex_joni> the machines I tried are 1.4GHz (one Athlon, one Centrino), but also a 2.66GHz P4
[15:23:27] <alex_joni> and never seen it there
[15:23:28] <alex_joni> :D
[15:33:37] <alex_joni> * alex_joni heads home..
[15:34:39] <cradek> the machine is at home but I have ssh to it
[15:35:00] <cradek> maybe we should compare latencies instead of processor speed
[15:35:37] <cradek> like I said, maybe rtai3.3 is faster/slower and therefore makes the problem worse
[16:09:52] <alex_joni> I think we can nail the problem
[16:10:08] <alex_joni> for any speeds/latencies
[16:12:10] <alex_joni> it's a flag set when it shouldn't
[16:12:14] <alex_joni> or a check too early
[16:12:33] <alex_joni> maybe the mode switch shouldn't get done while not INPOS set
[16:13:50] <alex_joni> I see some strange things at first glance...
[16:15:21] <alex_joni> but I need to study the stuff in control.c a bit more thoroughly
[16:15:26] <alex_joni> but, dinner first ;)
[16:15:56] <alex_joni> actually late lunch :D
[16:48:45] <SWPadnos> Hi guys
[16:48:50] <SWPadnos> hey cradek - what's the best place to put in AXIS feature requests?
[16:57:04] <cradek> email, or here
[16:57:16] <SWPadnos> ok.
[16:57:16] <cradek> we don't have a feature request tracker except the wishlist (TODO) in cvs
[16:57:34] <SWPadnos> ok - I considered a SF tracker item in the axis category
[16:58:13] <cradek> I considered that, but it's overkill
[16:58:20] <SWPadnos> ok
[16:58:23] <cradek> have a look at the TODO in cvs
[16:58:32] <SWPadnos> axis CVS?
[16:58:36] <cradek> yeah
[16:58:53] <SWPadnos> I looked at the list of possible additions for 1.2 (I think)
[16:59:32] <cradek> so all this aside, what's the request?
[16:59:36] <SWPadnos> heh
[16:59:41] <SWPadnos> several, actually
[17:00:02] <SWPadnos> I finally fired it up on the 800x600 touchscreen (though I wasn't using the touch driver)
[17:00:11] <SWPadnos> first, a full-screen mode would be great
[17:00:32] <cradek> that's a function of your window manager.
[17:00:42] <SWPadnos> second, the tooltip text is unreadable because it's so small (about 5 pixels high)
[17:00:53] <cradek> that's an X misconfiguration.
[17:00:57] <SWPadnos> true - or you could make it draw on the root window
[17:00:59] <cradek> hey these are easy
[17:01:01] <SWPadnos> heh
[17:01:05] <SWPadnos> pass the buck
[17:01:07] <cradek> no, that would be an abomination.
[17:01:32] <cradek> the problem is that X can't read your monitor's DDC information, so it calculates a wrong DPI.
[17:01:40] <cradek> set your monitor's size in xorg.conf
[17:01:47] <SWPadnos> also, add several controls that allow you to change the left-drag function on the preview - zoom, pan, and rotate
[17:01:52] <SWPadnos> I think it's set, but I can check
[17:02:27] <SWPadnos> basically that last one makes it so you can still use all the preview features with only one button and dragging
[17:02:36] <cradek> Section "Monitor"
[17:02:37] <cradek> ...
[17:02:45] <cradek> DisplaySize 123 456
[17:02:47] <cradek> EndSection
[17:02:59] <cradek> replace with your display's size in mm
[17:03:01] <SWPadnos> what font size is that supposed to be?
[17:03:19] <cradek> umm... small
[17:03:28] <cradek> let me see if I can find it
[17:03:39] <SWPadnos> heh - it is certainly small
[17:09:55] <cradek> SWPadnos: run xdpyinfo and check for these two lines
[17:09:56] <cradek> dimensions: 1600x1200 pixels (411x311 millimeters)
[17:09:56] <cradek> resolution: 99x98 dots per inch
[17:11:42] <SWPadnos> actually, the size was set wrong
[17:11:50] <cradek> does that fix it?
[17:12:09] <SWPadnos> not sure yet - I'm creating a desktop shortcut :)
[17:12:17] <SWPadnos> to save time, dontcha know
[17:12:19] <cradek> btw, in icewm (and also gnome I think) you can make a window fullscreen with Alt-F11
[17:12:33] <SWPadnos> I see that KDE has a fullscreen option as well
[17:12:49] <SWPadnos> we should make a good icon for emc
[17:13:20] <alex_joni> * alex_joni plans to do that
[17:13:28] <alex_joni> what size is an icon usually?
[17:13:35] <alex_joni> 32x32 or bigger?
[17:13:39] <cradek> I remember someone drew chips2 and he was pretty good
[17:13:43] <cradek> do you remember who that was?
[17:13:47] <alex_joni> I expect 256 colors, or 24bit
[17:13:56] <alex_joni> chips2?
[17:14:36] <cradek> yeah he was like chips but drawn better
[17:14:49] <cradek> he was holding an end mill in one ... flipper
[17:15:00] <alex_joni> huh, that might have been me
[17:15:08] <alex_joni> hang on, I'll give you an URL soon
[17:15:12] <SWPadnos> fenn did one
[17:15:35] <cradek> he was wearing safety goggles
[17:16:04] <alex_joni> oh, then probably it was fenn's
[17:16:28] <alex_joni> cradek: what size icon?
[17:16:41] <cradek> I don't remember what it was
[17:16:45] <SWPadnos> how about svg, targeting 48x48
[17:16:51] <cradek> I think it was a medium-sized image, not an icon
[17:17:00] <alex_joni> no, I mean what size should the icon have?
[17:17:04] <SWPadnos> fenn had made a desktop / bootup background, I think
[17:17:14] <SWPadnos> 48x48 is the standard, I think
[17:17:26] <alex_joni> I only made an chips2 ages ago, but I don't like how it looks..
[17:17:26] <SWPadnos> at least it was for NextStep ;)
[17:17:29] <alex_joni> http://www.robcon.ro/emc/chips2.jpg
[17:18:01] <SWPadnos> maybe a chisel with a motor on it
[17:18:45] <SWPadnos> http://fenn.dyndns.org/pub/emc/chips2.png
[17:19:21] <cradek> I think that's the one I remember
[17:20:12] <cradek> I'm not sure I love either of the chips2, but this is the kind of thing I stay out of because I have no artistic skills.
[17:20:25] <SWPadnos> my problem as well
[17:20:38] <cradek> is your font problem fixed?
[17:20:38] <SWPadnos> my wife is a graphic designer though, so we may be able to get something done
[17:20:45] <SWPadnos> they're readable now - thanks
[17:20:50] <SWPadnos> still a bit small
[17:21:16] <cradek> they're supposed to be small but legible
[17:21:38] <cradek> I can't even find where the font is set
[17:21:53] <SWPadnos> in KDE, there's a fullscreen mode, but if the application doesn't provide a way of getting out of it, then you have to use the keyboard to get through the application menus to restore to non-FS mode
[17:22:07] <SWPadnos> it's legible if I'm within 2" of the screen
[17:22:20] <cradek> SWPadnos: what DPI does X think it is now?
[17:22:26] <SWPadnos> one sec
[17:22:54] <SWPadnos> 81x81 dpi
[17:23:09] <SWPadnos> alightly over 1 pixel/point
[17:23:12] <SWPadnos> slightly
[17:25:11] <alex_joni> how's this? http://www.robcon.ro/emc/chips2icon.png
[17:25:28] <SWPadnos> not bad, actually :)
[17:25:40] <cradek> I agree
[17:25:48] <alex_joni> ok, that was a quickie ;)
[17:25:58] <alex_joni> it can get better if I do it slower :)
[17:26:04] <alex_joni> but I need to rush out now
[17:26:07] <alex_joni> * alex_joni will be back later
[17:26:11] <cradek> bye
[17:26:13] <SWPadnos> see ya
[17:26:20] <alex_joni> cradek: if you can use it, be my guest
[17:26:37] <alex_joni> we need to package it along with emc2
[17:26:54] <alex_joni> so users will get the icon on the desktop after apt-get'ing
[17:26:57] <cradek> toss it in cvs and we'll figure out what make install should do with it
[17:27:13] <alex_joni> ok, along with the splash?
[17:27:13] <SWPadnos> make a desktop link ro emc, probably ;)
[17:27:17] <SWPadnos> s/ro/to/
[17:27:25] <cradek> sure
[17:27:45] <cradek> we'll have to figure out how ubuntu handles putting things on the menu etc.
[17:28:17] <alex_joni> ok, will do that later ;)
[17:28:51] <cradek> yeah.
[17:29:20] <SWPadnos> is the "live" distro going to be ubuntu now?
[17:29:58] <cradek> none of us can predict the future, but I'm working on some ubuntu stuff.
[17:30:27] <SWPadnos> "this document contains forward-looking statements, which cannot be guaranteed ... "
[17:30:55] <SWPadnos> this brain intentionally left blank
[17:31:48] <alex_joni> laters everyone.. I'm off
[17:37:31] <SWPadnos> OK - so I guess the feature requests boil down to (1) possibly adding a button to toggle fullscreen mode (WM dependent, I suspect), and (2) adding drag mode selection for the preview window
[17:38:26] <SWPadnos> oh - and if there's a context menu added to the G-code display, then have a button to toggle that as well (maybe click a line, then click a" menu" button)
[18:13:22] <cradek> can you explain what you mean by drag mode selection?
[18:15:25] <SWPadnos> yes
[18:15:46] <SWPadnos> right now, dragging with the middle button rotates
[18:15:53] <SWPadnos> left button pans
[18:16:03] <SWPadnos> no option for zoom (right?)
[18:16:31] <SWPadnos> put buttons on the toolbar or somewhere so that a left drag can perform any of those functions
[18:16:50] <cradek> I think the right button or wheel zooms
[18:16:59] <cradek> shift does something too
[18:17:27] <cradek> how about keyboard modifiers? shift+drag, control+drag?
[18:17:38] <cradek> those would let you use just the left button, but still not muddy up the user interface
[18:18:00] <SWPadnos> that would work
[18:18:12] <SWPadnos> I see that shift+left = middle (rotate)
[18:18:25] <SWPadnos> so add ctrl+left=zoom, and you're all set
[18:20:28] <cradek> * control + left drag = zoom, which is the final thing needed for left-button-only navigation (SWP's touchscreen).
[18:20:48] <SWPadnos> (assuming I can even drag with it :) )
[18:20:58] <SWPadnos> but a touchpad would be the same
[18:21:03] <cradek> yeah, that part's up to you!
[18:21:19] <SWPadnos> maybe I'll install the driver again
[18:21:25] <cradek> my touchpads all have three (two plus three-button emulation) buttons
[18:21:48] <SWPadnos> true
[18:22:18] <cradek> for a very long time, X applications have always been able to assume three mouse buttons
[18:22:42] <SWPadnos> yep - that's what we had on the Irises, way back when
[18:22:58] <SWPadnos> with amazingly speedy 25 and 33MHz processors O_O
[18:23:00] <cradek> today we're near everyone assuming three buttons + wheel, but that's not the rule yet
[18:23:22] <SWPadnos> what about those poor souls who are stuck with only a light pen?
[18:23:40] <cradek> I ran autocad on a sun 386i
[18:23:48] <cradek> not sure what the clock speed was, probably 25
[18:24:02] <SWPadnos> oooh - the only 386 based computer that actually booted in 32-bit mode
[18:24:25] <cradek> nah
[18:24:31] <cradek> I ran OS/2 on a 386 too
[18:24:57] <SWPadnos> I've still got a copy of Warp somewhere
[18:25:04] <cradek> but anyway, the point is we had three buttons
[18:25:08] <anonimasu> os2 rocked :)
[18:25:11] <SWPadnos> I had v3 as well, on floppies
[18:25:11] <cradek> actually I had 16
[18:25:13] <SWPadnos> yep
[18:25:33] <SWPadnos> ok - a tablet with a 16-button puck
[18:25:36] <cradek> os2 only rocked when compared to windows 3.1
[18:26:01] <cradek> <os2> oh something's wrong? go wade through the 300 line config.sys </os2>
[18:26:06] <SWPadnos> actually, it's still good compared to Windows 2000 or XP, but not necessarily in the eye candy department
[18:26:14] <anonimasu> yep
[18:26:35] <SWPadnos> lots of banks still use it, because it doesn't crash
[18:43:00] <alex_joni> hello
[18:45:46] <cradek> welcome back
[18:49:37] <SWPadnos> hi
[18:57:36] <rayh> whazzup?
[19:13:58] <alex_joni> not much
[19:14:06] <alex_joni> I'm at some friends ;)
[19:31:29] <alex_joni> hrmm.. do you guys have any idea why hdparm is failing?
[19:31:52] <alex_joni> hdparm -c3 -d1 /dev/hda
[19:31:52] <alex_joni> /dev/hda:
[19:31:52] <alex_joni> setting 32-bit IO_support flag to 3
[19:31:52] <alex_joni> setting using_dma to 1 (on)
[19:31:54] <alex_joni> HDIO_SET_DMA failed: Operation not permitted
[19:31:57] <alex_joni> IO_support = 3 (32-bit w/sync)
[19:31:59] <alex_joni> using_dma = 0 (off)
[19:32:07] <SWPadnos> root?
[19:32:42] <alex_joni> yup
[19:32:45] <alex_joni> the 32bit works
[19:32:54] <alex_joni> only DMA can't get set
[19:32:56] <SWPadnos> is this a BDI?
[19:33:24] <alex_joni> no, stock debian
[19:33:28] <SWPadnos> hmmm
[19:33:40] <alex_joni> does hdparm work on scsi too?
[19:33:51] <SWPadnos> not that I know of
[19:33:54] <cradek> no
[19:34:03] <alex_joni> ok.. but on IDE it should
[19:34:59] <SWPadnos> maybe the specific chipset support wasn't compiled into the kernel?
[19:35:34] <cradek> -d Disable/enable the "using_dma" flag for this drive. This option
[19:35:37] <cradek> now works with most combinations of drives and PCI interfaces
[19:35:40] <cradek> which support DMA and which are known to the IDE driver.
[19:35:50] <cradek> that doesn't sound like a sure thing
[19:35:52] <SWPadnos> http://seclists.org/lists/linux-kernel/2002/Oct/0162.html
[19:39:13] <alex_joni> SWPadnos: it's a stock debian SMP kernel
[19:39:20] <alex_joni> I'll check the config :(
[19:39:46] <SWPadnos> yeah - it should have support for most of the common chipsets, but who knows
[19:40:01] <SWPadnos> it's not SATA is it?
[19:40:04] <alex_joni> no,
[19:40:08] <alex_joni> udma4
[19:40:15] <alex_joni> hrmmm.. # CONFIG_IDEDISK_MULTI_MODE is not set
[19:40:33] <SWPadnos> that's multiblock transfer, not DMA (I think)
[19:40:55] <alex_joni> CONFIG_IDEDMA_AUTO=y
[19:41:51] <SWPadnos> I think that just sets DMA mode automatically, if the kernel knows it's usable
[19:43:21] <alex_joni> ok.. looking further
[19:43:26] <SWPadnos> what's the chipset?
[19:44:33] <alex_joni> # cat /proc/ide/ide0/model
[19:44:33] <alex_joni> generic
[19:44:48] <alex_joni> I think it's not discovered properly
[19:44:56] <alex_joni> but I have no idea what chipset there is :D
[19:45:18] <SWPadnos> dmesg | grep -i chipset ?
[19:45:25] <SWPadnos> I'm not sure how they're reported, actually
[19:45:54] <alex_joni> Jan 20 17:12:58 localhost kernel: ICH: IDE controller at PCI slot 00:1f.1
[19:45:54] <alex_joni> Jan 20 17:12:58 localhost kernel: ICH: chipset revision 2
[19:45:54] <alex_joni> Jan 20 17:12:58 localhost kernel: ICH: not 100%% native mode: will probe irqs later
[19:45:57] <alex_joni> Jan 20 17:12:58 localhost kernel: ide0: BM-DMA at 0xfff0-0xfff7, BIOS settings: hda:DMA, hdb:pio
[19:46:00] <alex_joni> Jan 20 17:12:58 localhost kernel: ide1: BM-DMA at 0xfff8-0xffff, BIOS settings: hdc:DMA, hdd:pio
[19:46:22] <SWPadnos> eeeww - an Intel 865 or similar
[19:46:28] <SWPadnos> recent P4, right?
[19:46:50] <alex_joni> no, dual P3 XEON
[19:46:58] <alex_joni> older
[19:47:04] <SWPadnos> ok - the ICH threw me
[19:47:36] <alex_joni> # dmesg | grep -i chipset
[19:47:36] <alex_joni> ICH: chipset revision 2
[19:47:36] <alex_joni> agpgart: Detected an Intel i840 Chipset.
[19:47:45] <SWPadnos> ah - OK
[19:47:54] <alex_joni> any ideas?
[19:48:34] <SWPadnos> http://www.ussg.iu.edu/hypermail/linux/kernel/0305.3/0055.html
[19:49:02] <SWPadnos> I googled for i840 IDE DMA
[19:52:58] <alex_joni> ??
[19:53:15] <SWPadnos> that may not help though ;)
[19:58:29] <anonimasu> alex_joni: usually you just need the generic stuff there and it'll work..
[19:58:35] <anonimasu> alex_joni: that was the case on my laptop..
[20:03:42] <alex_joni> well.. it didn't
[20:03:58] <alex_joni> anyways, don't care right now, too tired :D
[21:17:48] <rayh> four hal variables in watch takes 956 microseconds per iteration
[21:23:56] <alex_joni> * alex_joni is back
[21:24:25] <rayh> Hi alex
[21:24:26] <SWPadnos> rayh, is that with separate execs?
[21:25:02] <rayh> no that's with the open followed by separation of the reply and changing of the displays in a canvas.
[21:25:24] <SWPadnos> ok
[21:25:46] <rayh> If a person is conservative about how many variables they watch at a time it should be okay.
[21:26:11] <SWPadnos> so that's a single HAL command, and then TCL parsing the result?
[21:26:24] <SWPadnos> or separate commands?
[21:26:35] <rayh> No there is a halcmd for each through the open channel
[21:26:40] <SWPadnos> ok
[21:27:04] <SWPadnos> that may be worse than using the TCL string functions
[21:27:21] <rayh> We talked once about sending a matrix of pins and getting back the values but that's for later I suspect
[21:27:29] <SWPadnos> remember - halcmd internally does a string compare for every pin (or whatever) each command
[21:27:52] <rayh> yep.
[21:28:06] <SWPadnos> and it's not likely to be better than TCL at string manipulation ;)
[21:28:16] <rayh> and then I've got a pile of parsing, ifing and setting displays.
[21:28:22] <SWPadnos> yep
[21:28:38] <rayh> I've a notion to commit this and let you guys have a go at it.
[21:28:53] <SWPadnos> heh - that's not fair
[21:30:49] <rayh> all's fair in emc
[21:38:24] <rayh> syntax error in expression "": premature end of expression
[21:38:30] <rayh> never seen that before.
[21:38:52] <SWPadnos> well - that is premature
[21:39:01] <rayh> I suspect that I'm reading a global while another is changing it.
[21:39:17] <SWPadnos> where did it occur?
[21:40:05] <rayh> In the watch loop.
[21:40:25] <SWPadnos> is there a way to remove watches?
[21:40:39] <rayh> while I was adding another pin.
[21:40:51] <SWPadnos> ok
[21:41:14] <SWPadnos> I've seen some odd stuff with watch mode, (didn't mention it because I know it's a WIP)
[21:41:36] <rayh> I suppose that I should have the user select the pins to watch.
[21:41:46] <rayh> then kick off the loop to watch.
[21:41:51] <SWPadnos> right
[21:41:56] <rayh> I'm not using the unix watch command.
[21:41:58] <SWPadnos> and allow deletions
[21:42:10] <rayh> Have not gotten that far yet.
[21:42:21] <SWPadnos> I ended up with 3 copies of the same pin (due to my own stupidity(
[21:42:33] <SWPadnos> no problem - like I said, WIP
[21:42:48] <SWPadnos> one other useful thing would be to disallow duplicates
[21:43:12] <rayh> Hey that is quite possible with the pattern.
[21:44:11] <rayh> I could build some watch control buttons and place them in the control frame.
[21:45:38] <SWPadnos> sounds good to me
[21:50:49] <rayh> got the disallow duplicates.
[21:50:56] <SWPadnos> cool - that was fast
[21:51:13] <SWPadnos> I had noticed that sometimes the vars disappear fora couple of seconds
[21:51:33] <SWPadnos> the blank line will still be there, just no text on it
[21:53:47] <rayh> the value variables or the varname?
[21:53:53] <SWPadnos> both, I think
[21:54:36] <rayh> this is in watch mode
[21:55:04] <SWPadnos> I think so (not running it right now)
[21:55:20] <rayh> okay. I'll watch for it.
[21:55:56] <SWPadnos> I'll try it again
[21:59:58] <rayh> I've got a more complete error message.
[22:00:02] <rayh> syntax error in expression "": premature end of expression
[22:00:03] <rayh> while executing
[22:00:03] <rayh> "expr $ret"
[22:00:03] <rayh> (procedure "watchLoop" line 15)
[22:00:04] <rayh> invoked from within
[22:00:04] <rayh> "watchLoop"
[22:00:05] <rayh> ("after" script)
[22:00:22] <SWPadnos> ok - so $ret is empty
[22:00:34] <rayh> sounds like it.
[22:00:39] <SWPadnos> you can check for that before the expr
[22:00:48] <rayh> 'suppose i could just catch it.
[22:01:43] <rayh> That is where the value of a non bit var is converted from scientific notation to decimal
[22:03:03] <SWPadnos> hmm
[22:04:37] <rayh> I'm getting a few oddities in the selection between bit and other also.
[22:05:10] <SWPadnos> ok. I just cvs upped, and I'm taking a quick gander at it
[22:05:17] <rayh> Must try buttons to stop the loop while adding.
[22:06:26] <SWPadnos> heh
[22:06:41] <SWPadnos> I've got the blinky lines again, btw
[22:07:13] <rayh> what all is blinky
[22:07:20] <SWPadnos> ok - maybe it's just some extra blank lines getting added or something
[22:07:33] <rayh> in watch mode
[22:07:37] <SWPadnos> let me start over, and tell you exactly what I do to cause it
[22:07:40] <SWPadnos> yes, in watch mode
[22:07:44] <rayh> k
[22:08:32] <SWPadnos> ok, ran halconfig, waited for tree to refresh
[22:08:43] <SWPadnos> this is with the univstep config
[22:08:56] <SWPadnos> so lots of hal stuff around
[22:09:17] <SWPadnos> select Settings->Watch
[22:09:53] <SWPadnos> expand the tree as follows: first pins, then ppmc, then 0, then encoder
[22:10:44] <SWPadnos> click 00 (which should give me a list, I think, but it adds encoder.00.count)
[22:11:15] <SWPadnos> watch screen says "ppmc.0.encoder.00.counthal_ppmc -1"
[22:11:56] <SWPadnos> click index, delta, and position - no change
[22:12:05] <SWPadnos> (clicking in the tree)
[22:12:38] <SWPadnos> click count, and a blank line is inserted above the existing line in the watch pane
[22:12:59] <SWPadnos> this toggles back and forth a couple of times (top line, then second line ...)
[22:13:50] <SWPadnos> ok - simpler method. click 00 a couple of times - you'll see the watch pane change in odd and interesting ways (unless the dupe elimination fixed this)
[22:14:55] <rayh> I don't seem to be able to duplicate your display here.
[22:16:50] <SWPadnos> I wonder if my wife's finished snowblowing the driveway
[22:17:18] <alex_joni> lol
[22:17:29] <alex_joni> and you're sitting inside where it's warm
[22:17:33] <SWPadnos> at least I started it for her
[22:17:38] <SWPadnos> I'm sick, you see ;)
[22:17:43] <SWPadnos> (cough cough)
[22:17:44] <alex_joni> lame excuse
[22:17:46] <alex_joni> :D
[22:18:15] <SWPadnos> server her right - she gave me the cold in the first place
[22:18:18] <SWPadnos> serves
[22:23:04] <rayh> ah there appears to be a problem with the tree encoder.00 is a node rather than a leaf.
[22:23:08] <SWPadnos> ok - no blinky here, plus I have nice little fake LEDs
[22:23:10] <SWPadnos> right
[22:23:19] <SWPadnos> that happens in a couple of places, I think
[22:23:23] <rayh> so it returns at least three or four lines.
[22:23:34] <SWPadnos> ok - that could be
[22:23:44] <SWPadnos> hmmm - I should change the index output to a bit
[22:24:14] <SWPadnos> ok - it is a bit - you need to fix halconfig ;)
[22:26:13] <rayh> I'll try using the channel flag to prevent these partial reads.
[22:27:20] <SWPadnos> is it a partial read during the tree refresh?
[22:34:46] <rayh> No it looks like some sort of tree building error. I see the raw reply split out okay.
[22:35:03] <rayh> It just does not build the tree right.
[22:35:10] <SWPadnos> mmm
[22:37:00] <rayh> ah I do have five levels of nodes but a wrong index to the last.
[22:39:49] <SWPadnos> is that a fixed 5 levels, or can it be more?
[22:41:12] <rayh> aha 'dat's better 'eh.
[22:41:23] <rayh> that's a fixed five levels.
[22:41:32] <SWPadnos> * SWPadnos waits for cvs message ;)
[22:41:43] <rayh> brute force
[22:41:47] <SWPadnos> heh
[22:41:57] <SWPadnos> would CL want more?
[22:42:15] <SWPadnos> hmmm. probably not, since there's only one instance of CL
[22:42:29] <SWPadnos> at most
[22:43:47] <rayh> we could look at the stuff in demo_step_cl
[22:44:34] <SWPadnos> is there an initial delay before the first tree refresh?
[22:45:39] <rayh> ah there is an issue with demo_step_cl. No stepgen max vel.
[22:47:17] <rayh> The tree should be there when the display comes up.
[22:47:38] <rayh> I did eliminate the open all nodes thing.
[22:47:47] <SWPadnos> ok - it takes around 5 seconds before the pluses appear
[22:47:54] <SWPadnos> on my celeron 500
[22:47:56] <rayh> Really.
[22:48:14] <SWPadnos> it looked like it might be a 5-second delay plus a little, but it could just be that slow
[22:48:18] <rayh> * rayh makes a note to try on his slowest box.
[22:48:41] <SWPadnos> heh - fast computers are the bane of developers
[22:48:45] <SWPadnos> "it seems fine here"
[22:48:50] <rayh> Try adding a sig and see how long it takes to display the new.
[22:49:01] <SWPadnos> adding a sig to the watch?
[22:49:11] <rayh> No to the show.
[22:49:33] <rayh> newsig MySig1 bit in the lower entry widget
[22:49:37] <SWPadnos> as fast as I can click
[22:49:41] <SWPadnos> oh - hold on
[22:50:17] <SWPadnos> about 5 seconds
[22:51:04] <rayh> Okay. I'll have to change the way refresh works. Just add or subtract rather than a total rebuild.
[22:51:16] <rayh> But that will be later.
[22:51:25] <SWPadnos> but the signal doesn't show up in the tree
[22:51:35] <SWPadnos> hey - when did we get 8 axes?
[22:52:46] <SWPadnos> bummer - the Tapmatic 70TC/DC I'm watching on eBay is up to $145
[22:52:53] <SWPadnos> still a good deal though
[22:53:48] <rayh> we always get 8.
[22:54:04] <SWPadnos> odd - I thought it was 6
[22:54:12] <rayh> It would be nice to limit to the ini variable's number
[22:54:18] <rayh> that would clean up stuff a lot.
[22:54:37] <SWPadnos> like - read the ini to figure out how many axes to export?
[23:04:30] <SWPadnos> out of curiosity, do you have any idea where to get nichrome wire?
[23:05:14] <rayh> No I don't.
[23:05:21] <SWPadnos> ok
[23:05:37] <SWPadnos> I'd think that would pop balloons pretty well - don't you?
[23:06:31] <rayh> should. I know they use it round here for cutting foam and bending plastic countertop.
[23:07:05] <SWPadnos> yep - I found some places that sell foamcutters, but they have no specs on the wire (like ohms / ft, or current capacity)
[23:08:27] <rayh> I built a veeneer trimmer with some.
[23:08:41] <SWPadnos> cool.
[23:08:48] <SWPadnos> how much current id it take? ;)
[23:08:55] <SWPadnos> s/oid/did/
[23:08:57] <SWPadnos> s/id/did/
[23:09:37] <rayh> Seems like about 3 amps
[23:09:47] <rayh> Nice red glow.
[23:09:52] <SWPadnos> what gauge, if you recall?
[23:10:47] <rayh> I don't remember. I do remember doing some testing.
[23:10:56] <rayh> But the guy I was working for got the wire.
[23:11:05] <SWPadnos> heh, OK. maybe I'll order a small spool
[23:11:06] <rayh> Don't see it in McMaster.
[23:11:36] <SWPadnos> nope
[23:11:51] <SWPadnos> there are places that sell Inconel wire as well
[23:12:22] <SWPadnos> well whadda ya know: http://www.wiretron.com/nicrdat.html
[23:12:28] <SWPadnos> lots of data on nichrome
[23:13:32] <rayh> You guys and those damn fast connections.
[23:13:43] <SWPadnos> heh
[23:14:00] <SWPadnos> maybe we can all chip in for a satellite dish and a 600' mast for you
[23:14:41] <rayh> That should do it.
[23:15:01] <SWPadnos> will that get you above the horizon for the geoxync satellites?
[23:15:06] <SWPadnos> geosync
[23:16:18] <rayh> Sure. I'm a bit above 46, i think.
[23:17:09] <SWPadnos> ok - about a degree north of me (44 75-ish)
[23:18:41] <SWPadnos> that made no sense
[23:18:58] <rayh> all the variables are coming back 1.
[23:19:09] <rayh> now.
[23:19:21] <rayh> need to do a bit of checking
[23:19:48] <SWPadnos> oops - got to get to a meeting. see you later
[23:19:55] <SWPadnos> SWPadnos is now known as SWP_Away
[23:30:51] <rayh> rayh is now known as rayh_away