#emc-devel | Logs for 2007-12-28

[00:50:52] <fenn> who compiles kernels and doesn't know 'lsmod'?
[00:54:40] <cradek> well that's an interesting question
[01:35:18] <jmkasunich> curses on all things cheap and chinese!
[01:36:49] <jmkasunich> smoke came out of a motor run cap
[01:37:23] <jmkasunich> curses on single phase motors and their horrid caps while I'm at it
[01:37:42] <cradek> again??
[01:40:17] <jmkasunich> last time it was startup current blowing a fuse (mill motor)
[01:40:38] <jmkasunich> this time it was running current letting the foul smelling smoke out of the cheap ass run cap
[01:43:22] <jmkasunich> (running the lathe at the moment(
[01:47:22] <cradek> can you just put a better motor on it? I'm sure you have one in your piles of dumpster stuff...?
[01:51:19] <jmkasunich> actually I don't have any single phase motors laying around
[01:51:34] <jmkasunich> besides, just about all single phase motors use caps of some sort
[01:51:58] <jmkasunich> there's not really another good way to get a rotating magnetic field (need some phase shift from somewhere)
[01:52:33] <fenn> induction motors ? not a good way?
[01:52:44] <jmkasunich> I'm talking about induction motors
[01:53:08] <jmkasunich> a single phase stator without caps or other tricks will give a field that flops back and forth rather than rotating
[01:53:26] <fenn> oh, i forgot they have a little cap with a centrifugal switch
[01:53:31] <fenn> to get started
[01:53:40] <jmkasunich> in this case, two caps, one large one for starting, and another for running
[03:34:56] <Unit41> hmm
[16:18:25] <alex_joni> * alex_joni wonders if run-from-line should work with G91 (relative coords)
[16:34:30] <jepler> * jepler wonders if run-from-line works for any interesting cases
[17:03:02] <cradek> what do you mean work with?
[17:04:17] <alex_joni> cradek: a user reported that he has a file with relative coordinate moves (I think that's G91)
[17:04:54] <alex_joni> it works fine running it from the beginning, but run-from-line only gives him a ferror
[17:06:45] <jepler> ferror? no matter what junk the interpreter spews out its canon interface, it shouldn't lead to a following error
[17:07:12] <alex_joni> jepler: I thought so too.. and I can't rule out a user-error
[17:08:10] <jepler> or there could be two problems
[17:08:12] <cradek> I get the impression that, again, you don't have a real bug report here
[17:10:06] <cradek> last night someone reported a jfe when running the axis splash screen in stepper_mm
[17:54:05] <cradek> I found an interesting behavior of cutter comp. I don't know if it's a bug
[17:54:05] <cradek> g0x0y0
[17:54:05] <cradek> g42d1x1y1
[17:54:05] <cradek> y3
[17:54:06] <cradek> m2
[17:58:17] <jepler> hm, surprisingly to me I was able to start the home sequence (homing "Z") while on the X limit switch
[17:58:28] <jepler> I think I hit L F2 Ctrl-Home
[17:59:03] <cradek> hmm, I wonder if that's a feature
[17:59:07] <cradek> (probably not.)
[17:59:23] <jmkasunich> speaking of homing
[17:59:40] <jmkasunich> what determines if there is a "Home Axis" or "Home All" button on Axis's manual tab?
[17:59:41] <cradek> anyway the surprise about that comp code is that it changes if you use g0 vs g1 for the entry
[17:59:52] <cradek> presence of a homing sequence in the ini
[18:00:02] <jmkasunich> thats what I thought too
[18:00:19] <jmkasunich> lathe: I have home sequence 0 on one axis, nothing on the other, I get home all
[18:00:43] <cradek> then home all will only home that one?
[18:00:45] <jmkasunich> mill: I have home sequence 0 on Z, seq 1 on Y, and nothing on X, and I don't get home all
[18:00:49] <cradek> (why do you have that?)
[18:01:04] <cradek> oh, hmm
[18:01:11] <cradek> you might have to rtfs
[18:01:21] <jmkasunich> the saddle axis (Z on lathe, X on mill) doesn't have a switch
[18:01:21] <cradek> maybe it only checks one of them or something
[18:01:29] <jepler> if homing_order_defined:
[18:01:29] <jepler> widgets.homebutton.configure(text=_("Home All"), command="home_all_axes")
[18:01:31] <jepler> homing_order_defined = inifile.find("AXIS_0", "HOME_SEQUENCE") is not None
[18:01:47] <jmkasunich> lol
[18:02:03] <cradek> jepler is faster at both rtfs and rtfm
[18:02:21] <jmkasunich> well, he knows where to look in Axis
[18:02:34] <jmkasunich> btw, whoever wrote file reload - that is a great feature
[18:03:00] <jmkasunich> for this keyway, I wrote a prog that had #vars for several params like the depth to start and stop
[18:03:22] <jmkasunich> I could set them, load the program, run it, measure the result, and set them again for another pass
[18:03:29] <jmkasunich> alt F R and start the next pass
[18:03:40] <cradek> even ctrl-R I think
[18:04:21] <jmkasunich> I used to avoid keyways like the plague
[18:04:29] <jmkasunich> even this one probably took a half an hour
[18:04:32] <jmkasunich> but its done and nice
[18:04:55] <cradek> it's no secret that I think AXIS is pretty decent :-)
[18:04:55] <cradek> lunch! bbl
[18:05:03] <jmkasunich> same here
[19:14:31] <cradek_> cradek_ is now known as cradek
[19:23:11] <cradek> the error is still there, around line 1196
[19:27:05] <alex_joni> stepgen?
[19:28:15] <cradek> yes
[19:29:26] <alex_joni> * alex_joni agrees
[19:29:52] <alex_joni> it's less emc specific though
[19:30:26] <cradek> maybe it doesn't work?
[19:30:42] <cradek> although I'm sure I got it recently
[19:40:19] <jmkasunich> stepgen?
[19:40:37] <jmkasunich> version 1.58 (latest I think), line 1196 is the last line of the file
[19:40:48] <cradek> 883, sorry
[19:40:53] <cradek> I'm still not used to vim
[19:41:14] <jmkasunich> np
[19:43:00] <jmkasunich> oh, I bet I know why he didn't see the message
[19:43:11] <jmkasunich> (maybe, lemme check something)
[19:44:02] <jmkasunich> jepler broke it
[19:44:08] <jmkasunich> http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/configs/common/core_stepper.hal.diff?r1=1.10;r2=1.11;f=h
[19:44:26] <jmkasunich> the sample configs no longer set the maxvel parameter at all
[19:44:30] <jepler> aha
[19:44:36] <jepler> I guess I'm the evildoer here
[19:44:45] <cradek> ouch
[19:44:49] <cradek> ok, my config was old and still did that
[19:44:53] <jmkasunich> it was probably an attempt to reduce the cruft in the ini file
[19:45:21] <jmkasunich> and I probably told you that maxvel isn't used, only maxaccel is used (for the "pretuned position loop" stuff)
[21:11:28] <jmkasunich> jepler I hate you
[21:12:23] <jepler> :(
[21:12:41] <jepler> what did I do? can I still fix it?
[21:13:01] <jmkasunich> you posted your experience with pwmgen and servomotors (etch-servo)
[21:13:07] <jepler> oh
[21:13:12] <jmkasunich> xemet saw it and tried to copy it, but he is lacking in clue
[21:13:26] <jmkasunich> I've been trying to help him for the last hour or so, and its painfull
[21:14:13] <jepler> you understand that I only mean to do good by sharing things like this on the web, right?
[21:14:21] <jmkasunich> I know, I was joking
[21:14:24] <jepler> that said, I feel your pain and I'm sorry I caused it
[21:14:28] <jepler> "caused"
[21:14:37] <jmkasunich> things on the web should be labeled with a "tinkerer level"
[21:15:12] <jmkasunich> if your tinkerer level is much less than the project level, you should skip it
[21:15:39] <jmkasunich> if only slightly lower, then try it but be very meticulous - and if you succeed, yay, you've raised your level
[21:16:48] <jmkasunich> xemet needs to start with soldering, using a meter, basic troubleshooting (its going in this end of the wire but not coming out the other)
[21:18:10] <jepler> as opposed to going in one ear and out another?
[21:18:17] <jmkasunich> yeah
[21:18:27] <jmkasunich> his enable signal is flakey
[21:19:02] <jmkasunich> I was gonna try to walk him thru tuning (after spending half an hour chasing a ghost problem), but as soon as he powered up the motor started going at full speed
[21:19:12] <jepler> yech
[21:19:28] <jmkasunich> halcmd showed everything inside OK, so I told him to meter the parport and then the L298 pin
[21:19:47] <jmkasunich> they didn't match, one was 0V, the other 0.8 (both low, so it should work)
[21:20:17] <jmkasunich> then he said "I used a little brush on the driver and now it is 0.2V and works ok"
[21:20:29] <jepler> gee
[21:20:30] <jmkasunich> dirty or bad solder joint maybe
[21:21:58] <jmkasunich> but I'd think enable open would still be off
[21:22:49] <jepler> the datsheet trumpets the part's LOGICAL "0" INPUT VOLTAGE UP TO 1.5V (HIGH NOISE IMMUNITY)
[21:24:23] <cradek> WHY IS IT YELLING?
[21:27:54] <jepler> beats me
[21:28:04] <jepler> because it thinks the reader might have SIGNAL IMMUNITY?
[21:29:32] <jepler> anyway .. not that it has much bearing on the more general problem
[21:29:54] <jmkasunich> xemet just found an "interrupted cable"
[21:35:30] <jepler> I need to hook up pluto-step to my stepper board -- I finally got some of these, which will let me adapt the pluto pinout to the xylotex without making a board or hand-rewiring an idc cable .. http://www.sparkfun.com/commerce/product_info.php?products_id=8430
[21:36:19] <cradek> I like your idea of a 'tinkerer level'
[21:37:23] <jepler> geek social fallacy says that everyone's level is about like mine (actually I figure that since I only started on electronics a few years ago everyone else knows a lot more than me)
[21:55:51] <alex_joni> cradek: now we need some authority to impose it :)
[21:57:14] <jmkasunich> jepler: for any technical topic about which a person knows anything, they know vastly more than 95% of humanity
[21:57:51] <cradek> that's funny
[22:01:12] <alex_joni> I think it's sad :)
[22:02:08] <jmkasunich> it is
[22:02:21] <jmkasunich> axis question - can you set the incremental jog increments in the ini file?
[22:02:29] <jmkasunich> xemet is using mm, and 0.1 is pretty small
[22:02:30] <cradek> yes
[22:02:39] <cradek> simple matter of rtfm
[22:02:39] <jmkasunich> how would he set a 1mm increment?
[22:02:52] <cradek> (I'd have to look too)
[22:03:10] <jmkasunich> I've spent 2 hours with him so far, and my patience is wearing thin - you are supposed to know everything about axis
[22:03:14] <cradek> % grep -r INCREMENT .
[22:03:14] <cradek> ./dallur-thc/dallur-advanced.ini:INCREMENTS = 1000 10 1 0.1 0.01
[22:03:14] <cradek> ./sim/axis_mm.ini:INCREMENTS = 1 mm, .01 in, .1mm, 1 mil, .1 mil, 1/8000 in
[22:03:24] <jmkasunich> thanksd
[22:03:27] <jmkasunich> -d
[22:03:46] <cradek> that's [DISPLAY]INCREMENTS
[22:04:20] <cradek> dallur has 1000mm which seems like one hell of an incremental jog
[22:05:10] <alex_joni> maybe it's inches?
[22:05:17] <alex_joni> :P
[22:05:39] <cradek> I've noticed you can't have a separate increment setting for rotaries - that would be nice
[22:05:47] <cradek> 0.1 inches is pretty big, but 0.1 degrees is small