Back
[06:48:14] <jthornton> I've installed backuppc and in the process generated new key files... I assume I need to send cradek one of the ssh keys to replace the old one for git
[07:36:30] <jepler> Subject: [ANNOUNCE] 3.18.13-rt9
[08:02:36] <mozmck> jepler: and then over on #linux-rt: ***rostedt curses bigeasy for releasing a new -rt in the middle of a stable rc release!
[08:05:30] <mozmck> but I guess that's not relevant. looks like rostedt is talking about the 3.14 kernel patch?
[08:23:56] <jepler> oh do they have a channel? I guess I should try hanging out there.
[10:01:34] <JT-Shop> cradek, I need to send you a new key for pushing, but which one?
[10:02:15] <cradek> JT-Shop: send only the pub half
[10:02:36] <JT-Shop> ok thanks
[10:03:45] <JT-Shop> I'm working on the manuals for 2.7 and created a branch off of 2.7 for testing and review
[10:05:41] <cradek> sweet
[10:06:23] <jepler> JT-Shop: ouch, you installed some backup software and the first thing it did was overwrite some files with critical contents?
[10:06:26] <jepler> wowowow
[10:07:32] <cradek> ooh I didn't see that
[10:07:37] <cradek> what the heck
[10:08:04] <cradek> first, assume the user doesn't use ssh for anything important?
[10:11:54] <JT-Shop> jepler, no, it was a new install of Debian Wheezy so they didn't exist
[10:12:18] <jepler> JT-Shop: ah
[10:12:27] <jepler> so the old file was lost already
[10:12:36] <JT-Shop> and I didn't think about it at the time
[10:12:51] <JT-Shop> no I still have a complete copy of the old computer
[10:13:22] <jepler> you could copy the old .ssh directory wholesale to the new computer if you want to use the same key
[10:13:35] <JT-Shop> I guess I can just resend the keys to the computers on my LAN for the backup
[10:13:55] <JT-Shop> ok I'll do that
[14:20:20] <cradek> heh some stuff in this directory is like baby pictures of AXIS:
http://timeguy.com/cradek-files/emc/origin-preview.png
[14:23:14] <archivist> all that unused space
[14:23:33] <cradek> haha
http://timeguy.com/cradek-files/emc/homehomehomehome.png
[14:29:02] <tinkerer> cradek: 2nd try. (00:38:07) tinkerer: cradek: any news on the pluto front?
[14:29:43] <cradek> sort of. by adding pullups I got it to program reliably, but it does not communicate in epp mode after programming.
[14:30:11] <cradek> I found that a 7i43 does work on this port, but epp_wide=0 is needed
[14:30:23] <cradek> ... so I have been testing pluto with epp_wide=0
[14:30:29] <tinkerer> yep, the cable is too long
[14:30:53] <cradek> I tried several cables and am now using the one that makes the 7i43 work correctly
[14:31:24] <cradek> the signals I checked all (now) look square and not too noisy
[14:31:34] <tinkerer> there have to be some work in the verilog code
[14:32:10] <cradek> I tried your pluto-step with verilog changes that you sent to jepler a while back. it also had the same problem for me.
[14:33:18] <cradek> (I have now added pullups to pins 1, 14, 16, 17)
[14:33:22] <tinkerer> you just check the signals on the pluto side. thr wait signal is too short for a cable
[14:34:19] <cradek> is this something you fixed in the pluto-step firmware you sent to jepler?
[14:34:36] <tinkerer> i've some more strange effects with the sun1989.
[14:34:49] <tinkerer> not all.
[14:35:03] <cradek> note this is sun1888
[14:35:05] <mozmck> cradek: I think the package tom needs is glade-gtk2
[14:35:27] <cradek> sun1989 was not recognized
[14:35:29] <tinkerer> in the code which i sent jepler i fixed the handshaking generaly
[14:35:46] <cradek> tinkerer: unfortunately when I tried it, it did not help me
[14:36:01] <tinkerer> ??
[14:36:11] <cradek> I tried your pluto-step with verilog changes that you sent to jepler a while back. it also had the same problem for me.
[14:36:33] <tinkerer> the step is the unloved part ;)
[14:36:36] <cradek> I copied only the pluto-step.rbf and rebuilt
[14:36:50] <tinkerer> i work mainly with the servo
[14:37:04] <cradek> I don't care about the step, I use pluto-servo, but jepler said only step was modified in the files you sent him
[14:37:21] <tinkerer> no, definitivly not
[14:37:36] <cradek> hmm
[14:37:42] <tinkerer> i've sent you e fixed version
[14:37:54] <cradek> he had a tar file with many unrelated changes in it, so it's possible we were both confused by it
[14:38:06] <tinkerer> but with opendrain support for optocouplers
[14:38:54] <cradek> you sent me pluto_servo_opendrain.rbf but I don't understand what it is
[14:40:50] <tinkerer> the outputs of the pluto board works like open collector.
[14:41:37] <tinkerer> it have nothing to do with the printerport and epp.
[14:42:17] <tinkerer> with obendrain you can drive higher current
[14:44:05] <tinkerer> the pluto have limited power supply
[14:44:12] <cradek> would that fix the epp problem?
[14:44:33] <tinkerer> no, the epp fix is different
[14:46:18] <tinkerer> the synchronization of the epp handshaking in the original fpga code was incomplete.
[14:48:42] <tinkerer> if you are interessted I can make a wait delay for longer cable. maybe in the next week.
[14:49:03] <cradek> I'd be happy to test whatever you want
[14:49:08] <tinkerer> ok
[14:50:40] <tinkerer> how do you drive your lathe? do you have opto couplers?
[14:50:49] <cradek> I do not have any drive problems at all
[14:50:55] <tinkerer> :D
[14:51:11] <cradek> I don't remember exactly what the hardware is, but the pluto's pwm directly drives dumb H bridges
[14:51:17] <cradek> the lathe is very small
[14:51:33] <cradek> I have differential receivers for the encoders
[14:51:53] <tinkerer> L298?
[14:51:56] <cradek> yes
[14:52:07] <cradek> one L298 for two servos
[14:52:10] <tinkerer> ok direct w/o oc?
[14:52:19] <cradek> it works perfectly
[14:52:33] <cradek> I have been using it for years
[14:52:33] <tinkerer> jes the etch version. it was my 1st setup too
[14:52:50] <cradek> it's only replacing the PC that causes a problem
[14:53:41] <cradek> http://timeguy.com/cradek-files/cnc/lathe/DSCN6296.JPG
[14:54:29] <cradek> http://timeguy.com/cradek-files/cnc/lathe/DSCN6295.JPG
[14:54:39] <archivist> is that a real 36 way printer socket I see
[14:54:44] <cradek> the pluto is inside that box
[14:55:09] <cradek> archivist: all the wiring to the lathe is through that scsi cable
[14:55:22] <cradek> it's an old external scsi box of course
[14:55:32] <tinkerer> i see
[14:55:33] <archivist> heh
[14:56:09] <tinkerer> i've have such one from a atari :)
[14:56:19] <cradek> well there is more now - I added a hand wheel and switches to run touchy, and they go to another plug on the box
[14:57:37] <tinkerer> how long is the printer cable?
[14:58:16] <cradek> probably about 30"
[14:58:46] <cradek> same cable that worked with 7i43
[14:59:35] <tinkerer> yes but the mesa boards are electricaly much more stable
[15:01:48] <cradek> yeah :-/
[15:02:38] <tinkerer> and the old comps too :)
[15:02:52] <cradek> is the pluto important to you, or is it just an interesting challenge?
[15:02:55] <cradek> comps?
[15:03:09] <tinkerer> computers
[15:03:22] <cradek> oh right, also true
[15:04:22] <tinkerer> both, it drives my router and i learn much with it :)
[15:04:44] <cradek> ok good, then I am not the only remaining user!
[15:05:08] <cradek> because if I am the only one, I should rebuild with mesa
[15:09:55] <tinkerer> I'm planning to port the pluto code to other altera chips. some tries are promising. but im very busy in my job.
[15:13:55] <tinkerer> about the sun1989. it works very well when it is connected directly. but when I try to use a cable, the computer restarts when i load the pluto module.
[15:14:03] <tinkerer> very strange.
[15:14:13] <cradek> wow
[15:14:14] <cradek> yuck
[15:14:33] <tinkerer> but only the sun chip
[15:14:49] <cradek> maybe the sun cards are crap too, like the pluto
[15:15:35] <tinkerer> you mean they should work well together...? ;)
[15:18:28] <cradek> well that's one possibility I guess!
[15:18:57] <cradek> I think when you interface crap to crap, you get crap^2 instead of 2*crap
[16:43:48] <JT-Shop> lol
[17:11:34] <mozmck> If crap is negative, then crap^2 would be positive...
[17:14:45] <mozmck> Is there a way to set the default jog speed in terms of percentage of the max velocity?
[18:08:44] <tinkerer> cradek: I've sent you a test firmware. pleas try it out.
[18:14:25] <Tom_itx> mozmck, what does MAX_FEED_OVERRIDE, MAX_LINEAR_VELOCITY, and DEFAULT_LINEAR_VELOCITY do in the [DISPLAY] section?
[18:14:51] <Tom_itx> maybe the DEFAULT one would do that
[18:15:15] <Tom_itx> my default is set to 1.2
[22:19:44] <mozmck> DEFAULT_LINEAR_VELOCITY sets the default jog speed, but it is in units per second. My problem is that my X and Y are set at 1000 IPM max, and I want about 200 IPM default, but my Z only does about 150 IPM max, so it goes full speed when jogging.
[22:20:41] <mozmck> If I could set the default jog speed in a percentage of max, then the Z could jog slowly by default and full speed with the shift key.
[22:26:59] <Tom_itx> what does setting MAX_VELOCITY in the axis section do?
[22:27:24] <mozmck> Sets the max velocity of that axis.
[22:28:12] <mozmck> MAX_LINEAR_VELOCITY set the maximum linear jog velocity, which can be less than the axis max vel.
[22:29:40] <Tom_itx> would be nice if those could be set on a per axis basis
[22:30:12] <mozmck> The jog speed?
[22:30:28] <Tom_itx> the first 3 i mentioned
[22:30:39] <Tom_itx> default linear velocity etc
[22:31:00] <mozmck> Yes, or a percentage would work fine too.
[22:31:31] <Tom_itx> just for jogging?
[22:31:37] <mozmck> yes
[22:31:46] <Tom_itx> otherwise you could put it thru a scale comp
[22:31:59] <mozmck> Those settings are for Axis, and I'm working on a custom GUI, so I may implement something like that.
[22:32:15] <mozmck> put the jog speed through a scale comp?
[22:32:30] <Tom_itx> but it would also limit it overall so that may not work
[22:32:48] <mozmck> oh, yes, probably not.
[22:32:51] <cradek> do you mean keyboard jogging?
[22:32:55] <mozmck> yes.
[22:33:12] <Tom_itx> so one axis would move slower than the others
[22:33:13] <cradek> the gui sets the speed each time you press a keyboard jog key. you could have Z separate if you want, no problem
[22:33:28] <cradek> separate slider or whatever
[22:33:41] <mozmck> If there is not a built in way to do it, I bet I can write some code for my gui to do it.
[22:33:55] <cradek> turn on TASK ISSUE debug and jog around and you can see what messages are issued
[22:34:11] <mozmck> thanks, I'll look into that.
[22:34:12] <cradek> yeah, jog speed is totally a gui problem
[22:34:24] <mozmck> ok, that makes sense.
[22:34:37] <Tom_itx> set up a slider for each axis maybe
[22:36:12] <mozmck> naw, a single percentage slider will work fine.
[22:36:51] <mozmck> 20% of 1000 is 200 IPM, and 20% of 150 is 15 IPM which are probably both about right for a slowish jog.
[22:37:32] <mozmck> I guess if I really needed to I could make the Z separate, but mach does it that way so I know it works ok ;)
[22:40:26] <cradek> tinkerer: ooh! tomorrow!
