Back
[01:01:49] <jepler> rayh: the first one specified in the io= is parport.0, the next is parport.1, etc
[01:01:57] <jepler> or whatever the parameter name is for hal_parport
[01:25:06] <rayh> Hey thanks guys.
[01:29:09] <cradek> did you have success?
[01:40:15] <rayh> I found the addresses for both ports.
[01:40:51] <rayh> In the morning I'll try to figure out if the problem is outboard in the estop circuit or if it is a bad parport board.
[01:42:22] <rayh> I can disconnect the estop signal in HAL, connect it to a temp sig, and use sets to change it.
[01:42:49] <cradek> so there are still some IO problems? was it recently working or is this a new setup?
[01:43:49] <rayh> This is a broken 2.04 bdi that was upgraded to 6.06 by MattS.
[01:44:09] <rayh> Unfortunately he was not able to test.
[01:45:59] <cradek> sounds like a bit of a challenge to do remotely
[01:49:33] <rayh> If it's easy anyone would do it.
[01:50:54] <cradek> haha that's true.
[01:52:40] <rayh> We can't afford to make emc2 to easy, we'd be out of work!
[01:53:43] <cradek> besides, I'd rather have powerful than easy.
[01:57:55] <rayh> There you go.
[03:40:20] <skunkworks> jmkasunich: is the motenc_pidtest.hal file what you used to 'tune' the mazak
[03:40:47] <jmkasunich> I don't remember, I'd have to look at it
[03:41:38] <jmkasunich> no, I didn't use that on the Mazak
[03:41:51] <skunkworks> it uses siggen to make a circle
[03:42:07] <jmkasunich> yeah
[03:42:10] <skunkworks> ok
[03:42:15] <jmkasunich> it seems like a reasonable way to do tuning
[03:42:37] <jmkasunich> IIRC, peteV may have created that file, to help out a friend of his who was doing a retrofit
[03:42:51] <jmkasunich> I may have contributed to it a little as well
[03:43:16] <skunkworks> ok. It is a basic setup that looks like it could be used for my setup.
[03:43:36] <skunkworks> I still would not know what to change to tune ;)
[03:43:50] <jmkasunich> setp pid.0.Pgain 0.01
[03:43:50] <jmkasunich> setp pid.0.Igain 0
[03:43:50] <jmkasunich> setp pid.0.Dgain 0
[03:43:50] <jmkasunich> setp pid.0.bias 0
[03:43:50] <jmkasunich> setp pid.0.FF0 0
[03:43:51] <jmkasunich> setp pid.0.FF1 0
[03:44:08] <skunkworks> yes - I mean cause and effect
[03:44:13] <jmkasunich> oh
[03:44:18] <jmkasunich> yeah, thats the trick
[03:44:27] <jmkasunich> its very very hard to _explain_ tuning
[03:44:34] <skunkworks> Seems to be a closely guarded secret
[03:44:35] <skunkworks> :)
[03:45:00] <jmkasunich> no secret, just a skill that is best learned by doing
[03:45:10] <cradek> I think I got an ok feel for it by experimenting
[03:45:12] <skunkworks> I almost have the encoder mounted on the large servo.
[03:46:07] <skunkworks> right - I just need to jump in.
[03:46:47] <cradek> I still haven't tried out FF2
[03:47:33] <skunkworks> jmkasunich: a 1/4" set screw isn't enough to keep the sprocket on the servo shaft (it even had a flat spot)
[03:47:48] <jmkasunich> roll pin
[03:49:30] <skunkworks> we where disasembling a cincinati lathe and its hydrolic servos where only coupled with a keyway. No spit coupler or even setscrew. And that was profesionally designed
[03:49:56] <skunkworks> wow - sorry about the spelling.
[14:53:42] <jepler> AC_ERROR([modversions.h is missing. This is a known problem on
[14:53:45] <jepler> the BDI-TNG distro. Please re-run ./configure as root
[14:53:45] <jepler> -- configure.in
[14:53:49] <jepler> to replace it. You will only have to do this once.])
[15:14:21] <jepler> $ autoconf
[15:14:22] <jepler> NONE:0: /usr/bin/m4: ERROR: EOF in string
[15:14:22] <jepler> autom4te: /usr/bin/m4 failed with exit status: 1
[15:14:27] <jepler> well that is not a very useful error
[15:43:45] <jepler> MODEXT=`$RTS --module-ext 2>/dev/null` || MODEXT=".o"
[15:43:56] <jepler> does this do what the author intended -- set MODEXT to .o if $RTS exits with an error?
[15:44:16] <jepler> huh, I guess it does
[15:45:31] <cradek> I'm surprised by that too
[15:45:38] <cradek> (I wouldn't trust it)
[18:38:45] <steves_logging1> steves_logging1 is now known as steves_logging
[19:28:36] <jepler> jmkasunich: can you install the libgtk2.0-dev package on the bdi4 farm slot?