Back
[00:07:58] <benc-> anyone know how to set a default spindle speed? so when you run a gcode M3 turns on spindle even when no Sxxx was set.
[00:09:52] <jmkasunich> you could probably put an S word in the startup g-codes in the ini file
[00:10:09] <jmkasunich> not sure of the details or syntax, but I know you can specify codes to be executed on startup
[00:10:52] <SWPadnos> in the ini file, RS274NGC_STARTUP_CODES =
[00:11:49] <SWPadnos> oops - RS274NGC_STARTUP_CODE
[00:11:56] <SWPadnos> in the EMC section
[00:13:28] <benc-> thanks. that sounds promising.
[00:17:21] <toastydeath> one of the machines at work doesn't do T codes properly
[00:17:24] <toastydeath> and it's the one i am using
[00:17:37] <toastydeath> it has a tool magazine, not an umbrella
[00:17:44] <toastydeath> but it won't seek independantly
[00:18:05] <toastydeath> so it will sit on that line for like 30 seconds before it does anything else, no matter that the tool has changed and life can continue
[00:19:00] <toastydeath> also i wish i could rapid the A axis while other axes moved
[00:19:29] <toastydeath> that would also save time, but axis unclamp doesn't work that way =(
[00:26:49] <tomp> sounds like a plc timer, instead of using a sensor to end that step of the tool change.
[00:29:22] <Guest571> I am new to EMC2, I want to run a bridge port (with analog brushed DC Servo & drives), Is it possible?
[00:30:22] <tomp> yes
[00:30:57] <Guest571> what hardware is preffered, or parport can do it?
[00:31:25] <jmkasunich> to use analog servos you need something that has D/A converters, and you probably need hardware to count the encoder pulses
[00:31:34] <jmkasunich> there are several supported options
[00:31:48] <eric_U> what drives does it have now?
[00:31:48] <tomp> you need feedback (scales or rot encoders) and amplifiers what do you have?
[00:33:00] <Guest571> It has Heidenhein control 155, and its gone now, so motors are from SEM (Small Electric Motors Ltd.)
[00:33:10] <eric_U> so no drives?
[00:33:20] <toastydeath> tomp: it isn't, it starts immediately after the magazine finds the next tool
[00:33:40] <Guest571> Analog drives are there and mototrs run if applied analog voltages
[00:33:41] <tomp> toastydeath: whats the 30 secs always?
[00:33:51] <toastydeath> that's just what it feels like
[00:34:00] <toastydeath> because it's a big tool magazine and it takes forever to seek the right tool
[00:34:13] <toastydeath> so it'll swap out tool 2 for the next operation, then go seeking 3
[00:34:19] <tomp> ah, its "slow"
[00:34:19] <toastydeath> but instead of machining while it seeks, it waits
[00:34:33] <toastydeath> none of our other magazine machines do this
[00:34:39] <toastydeath> they all machine while the magazine is seeking
[00:35:36] <tomp> toastydeath: does it get separate M6 and then Tn commands?
[00:35:51] <tomp> err. maybe vs:vs
[00:36:08] <toastydeath> yes
[00:36:15] <tomp> dunno
[00:36:29] <toastydeath> what we've been doing is putting the Tx on the longest line nearby
[00:36:35] <toastydeath> so that it seeks while something else is going on
[00:36:37] <tomp> Guest571: you still need encoders, s\what plugs into the 155?
[00:37:20] <Guest571> The motors have rotory encoders and Tachogenerators, Tacho goes to Drive Card and encoders to Controls.
[00:37:20] <tomp> toastydeath: "pre-waiting" :)
[00:37:38] <toastydeath> =)
[00:37:59] <tomp> Guest571: and are the encoders heidenhain? thats >may< be special
[00:38:51] <tomp> whee, i got a 2nd monitor and can goto Hardy with spare partitions
[00:39:02] <Guest571> Tomp: Yes, they have plate Dr. Johannes Heidenhain.
[00:39:23] <tomp> hmm, does it say "11uA" or "1v" ?
[00:39:48] <Guest571> Tomp: seems to be differential A, B and Z pulses.
[00:40:47] <tomp> all have A B Z, but if '11ua" then it is sinusoidal ( not TTL at all ) if '1V p/p" then >might be ttl, handy with a scope?
[00:41:07] <tomp> any other markings ( i use heidenhains )
[00:41:35] <tomp> all will have a /a b /b z /z
[00:41:51] <Guest571> Tomp: wait I open the cover and see inside.
[00:42:40] <tomp> i'll look for a 155 manual ( awallin around? )
[00:44:01] <Guest571> Tomp: No other markings. The original control has a Card that is working so I can get TTL pulses.
[00:44:50] <tomp> is this a control or a Digital ReadOut ?
[00:45:01] <Guest571> It is a control
[00:46:14] <tomp> in any case, TTL is good, you can use Jon Elson's Paralele Port control for the analog command to the amplifiers and it can read the waveforms from the encoders. You can also use solutions from Mesa and others.
[00:47:02] <tomp> and if you ever need manuals...
http://www.heidenhain.com/index.php?WCMSGroup_2243_177=846&WCMSGroup_2238_177=2243&WCMSGroup_846_177=565
[00:47:05] <Guest571> It means pwmgen and RC circuit to convert it to analog?
[00:47:49] <tomp> I think Jon Elson's does that, yes some simple filtering to turn pwn into analog OR you can build fancier but you have less help
[00:48:24] <tomp> the Mesa has it done in hardware on an add-on board
[00:49:14] <tomp> There's more options for you to study, been to the wiki?
[00:50:00] <tomp> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?EMC2_Supported_Hardware
[00:50:05] <Guest571> I have set it up, to generate pwm pulses on parport and converting them to Analog value,
[00:50:57] <Guest571> and encoder feed back to parpot and counting in the software, this setup is working.
[00:51:11] <Guest571> but there is a problem
[00:51:26] <tomp> sounds like you're3 done :) what are you loking for?
[00:51:42] <tomp> problem?
[00:52:49] <Guest571> At slower feed rates (50 mm/min) the sizes are ok. but if we increase the feed rate to 200 mm/min, the sizes are less
[00:53:16] <tomp> could you mobe that fast with the 155 when it worked?
[00:53:20] <tomp> move
[00:53:57] <tomp> (2 ipm vs 8 ipm)
[00:54:05] <Guest571> yes, with 155 it can go upto 8,000 mm/min rapid and cutting what I used is 3000 mm/min
[00:54:41] <tomp> ok, now with a scope can you watch the inputs at those 2 speeds? ( maybe they breakup past your interface?)
[00:55:33] <Guest571> Inputs of what?
[00:55:50] <tomp> the parallel port
[00:56:01] <tomp> do you do any conditioning?
[00:56:09] <Guest571> for encoders or pwm?
[00:57:04] <tomp> ... " 200 mm/min, the sizes are less" i think we need to look at the encoder inputs to the parallel port
[00:57:34] <tomp> "conditioning" meaning, i thought these were differential...
[00:57:56] <Guest571> The conditioning may be in the card (that I used from older control)
[00:58:06] <tomp> pc card?
[00:58:58] <Guest571> No, it is 6x6 inch card to which encoders are attached and then TTL outputs come out.
[00:59:27] <K`zan> Sigh, looks like 8.04 is no better than 6.06, still doesn't recognize my wireless dongle :(. Looks like I am going to have to figure out how to get a RTK for 7.10 or get used to lugging it back and forth, sigh....
[00:59:37] <tomp> in any case you can separate the counting issue by moving the reader head without driving the motor, just debug the ability to read at 3m/min
[01:00:24] <Guest571> ?
[01:00:32] <Guest571> debug the ability?
[01:01:21] <tomp> Guest571: yes, make sure the output of the 6x6 card is good at 3m/min without moving the motor by pwm ( separate the issues)
[01:01:57] <Guest571> Ok I will check that when I will be at workshop.
[01:02:39] <tomp> this parallel port with encoder and pwm, was it controlled by EMC? (hal?)
[01:02:52] <tomp> or your own custom software?
[01:03:51] <tomp> you can make sure the pwm section works by itself by sending pwm to the filter to the amplifier and measuring the tacho output
[01:04:10] <tomp> (dont connect the motor to the axis for this test )
[01:06:07] <tomp> more info than Heidenhain has on the 155
http://faculty.etsu.edu/hemphill/entc3710/heid-op/h-chp1.htm
[01:59:11] <Guest571> Tomp: sorry elecricity failure.
[01:59:32] <Guest571> I am using EMC Hal.
[02:01:03] <tomp> excellent! with Hal you can easily separate the issues and test. especially since you are already using Hal.
[02:02:57] <Guest571> Can parport be used for 3m/min
[02:03:31] <tomp> good question, I dont know, it depends on your hardware AND i still wouldnt get you the best answer,
[02:04:13] <tomp> you'll need to get that answer from one of the guru's
[02:04:23] <Guest571> hardware latency test show 18000 ns so I have servo thread of 25000 ns
[02:05:00] <Guest571> sorry base thread 25000 ns
[02:09:25] <tomp> whats the smallest unit of measure with your scales ( .01mm .001mm .001" ?) because i think you get 40K counts/sec with that thread (1sec /.000025) and 40000 x unit change /60 is top distance/minute possible ( again, ask a guru ;)
[02:10:17] <Guest571> it is 0.001 mm
[02:11:12] <jmkasunich> software encoder counting with a 25000nS period in theory will fail at 40000 counts per second, in practice you should stay below 30000 or so
[02:11:25] <jmkasunich> with 1 micron resolution, that isn't very fast
[02:11:41] <jmkasunich> 30mm/sec, 1.8m/min
[02:12:00] <Guest571> I be happy if I can get 1500 mm/min
[02:12:05] <tomp> 40mm/sec * 60 secs is 2400mm/min???
[02:12:12] <Guest571> I am from Pakistan, so it is difficult to get one of the supported hardware.
[02:12:15] <tomp> 2.4m/min?
[02:12:51] <Guest571> yes 2.4 m.min theoratically and some margin so 1500/min is ok
[02:15:03] <tomp> "lower your expectations" :) and that still doesnt say how fast the parallel port can resolve that stream. your problem is even at 200mm/min = 3.333mm/sec = 3333 units/sec. so look at the hardware with a scope.
[02:15:58] <tomp> if you have a pulse generator, test your paralel port withpout the 6x6 board
[02:16:46] <Guest571> Ok, I will check that too.
[02:17:04] <tomp> where in Pakistan?
[02:17:37] <Guest571> Lahore
[02:17:49] <tomp> your english is perfect
[02:18:38] <Guest571> our medium of education is english
[02:20:11] <tomp> you can also verify the motor rpm by reading the tacho (it is some V/krpm)
[02:20:55] <Guest571> 9.5V/1krpm
[02:31:29] <Guest571> I have an idea, to make quad encoder counter card (24 bit) and then read it in EMC
[02:31:41] <Guest571> need to write some driver
[02:40:18] <tomp> hurray! the checksum is good, now to burn it
[02:53:45] <Guest571> Guest ---> shabbir
[02:54:14] <Guest571> Guest571 is now known as shabbir
[02:54:57] <shabbir> Tomp: I will be back after checking.... Thanks
[02:55:55] <shabbir> I have an idea, to make quad encoder counter card (24 bit) and then read it in EMC, needs a driver?
[03:02:00] <K`zan> I check the "over ride limits" box and it immediately unchecks. Got a home that is out in left field and can't seem to correct it short of rebooting?
[03:03:33] <K`zan> home homes to whever it is (in this case off the table) and then enforces limits, wth?
[03:03:42] <K`zan> NEver mind easier to reboot :).
[03:18:12] <jepler> K`zan: this may help clarify the intended function of "override limits":
http://thread.gmane.org/gmane.linux.distributions.emc.devel/848/focus=849
[03:18:58] <tomp> when booting the Hardy Heron EMC Live cd, i first get a pop-up "There was an error starting the GNOME settings Daemon..." I had this also on last box I installd to. ignore it?
[03:19:30] <jepler> you're right that it can be difficult to recover from emc having the wrong idea of where the soft limits are, without restarting. To cure that, emc 2.3 will allow an axis to be "unhomed"; on unhomed axes, soft limits are not applied.
[03:19:31] <eric_U> had problems with Gnomes because you have gremlins
[03:20:05] <eric_U> anything gnome related is graphical, shouldn't hurt much to ignore
[03:20:14] <jepler> tomp: pass that along to alex, I'm sure he'd at least like to look into it
[03:20:42] <tomp> it sounds like something that mightbe ok next time , will copy the text, ok
[03:21:05] <tomp> this is live,so not next time, but after install
[03:21:19] <eric_U> a "settings daemon" just sounds like a waste of memory and cpu cycles
[04:05:40] <K`zan_emc> Folks, how do I get an axis to home / zero ? Somehow I got my x out by -7.99 at the right place and nothing I am doing will let me get it to zero?!?
[04:06:10] <K`zan_emc> Override Limits immediately resets to unchecked...
[04:06:13] <cradek> K`zan_emc:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?CoordinateSystems
[04:06:19] <cradek> especially see section 3
[04:06:45] <K`zan_emc> cradek: Will check, thanks. I had not problems getting home/zero moved until today - most confusing.
[04:07:00] <cradek> override limits is for jogging off a limit switch. sounds like that is not your problem.
[04:08:17] <K`zan_emc> No home nor limit switches yet...
[04:08:31] <K`zan_emc> G53 G0 X0Y0Z0 - does nothing...
[04:08:34] <K`zan_emc> working
[04:08:39] <K`zan_emc> ...
[04:10:05] <K`zan_emc> No change.
[04:10:16] <K`zan_emc> x is still at -7.99
[04:10:43] <K`zan_emc> override limits, still won't hold.
[04:11:33] <K`zan_emc> guess I do a goo x8 and then power down and manually crank the table back.
[04:12:30] <cradek> ok tell me what you did after reading section 3
[04:13:13] <cradek> when you hit home you will get an absolute coordinate of whatever is in your ini HOME=. This is probably zero.
[04:13:21] <cradek> then if you clear your offsets you will see 0 on the screen too
[04:13:30] <cradek> this has nothing to do with override limits
[04:13:35] <K`zan_emc> errr
[04:14:06] <K`zan_emc> hit home axis and all it does is put a target up in front of x display.
[04:14:29] <K`zan_emc> Lemme get some gloves, brb. turning a 1/4-20 for 8 inches is hard on the fingers :)
[04:14:49] <cradek> why not just jog it?
[04:15:07] <cradek> stop doing stuff and tell me what's going on, and I can help
[04:15:23] <K`zan_emc> wont jog in that direction
[04:15:32] <cradek> or, read that page about offsets
[04:15:39] <cradek> ok tell me what you're doing
[04:15:56] <cradek> if you start emc, then press the jog arrow, it should jog
[04:16:18] <K`zan_emc> cranking on the lead screw, halfway there :)
[04:16:31] <K`zan_emc> Would NOT jog in the direction I need to go...
[04:16:46] <cradek> ok stop please
[04:16:54] <K`zan_emc> OK
[04:17:03] <cradek> when you start emc, it's not homed
[04:17:12] <cradek> if you press a jog key, it will jog
[04:17:22] <cradek> is this much not your experience? if so let's figure that out.
[04:17:23] <K`zan_emc> must be g00 x0 does nothing
[04:17:46] <K`zan_emc> ok got gloves off, can type again :)
[04:17:55] <K`zan_emc> Ok, lemme power up the drive again
[04:18:12] <K`zan_emc> In manual control...
[04:18:18] <K`zan_emc> x set to continious
[04:18:33] <cradek> is the home icon on?
[04:18:44] <K`zan_emc> Is that the target?
[04:18:46] <cradek> yes
[04:18:49] <K`zan_emc> Yes
[04:19:42] <cradek> ok this is the third time I've said it: when you start emc it's not homed. you can jog any way you want before you home.
[04:19:44] <K`zan_emc> OK jogged to physical zero / home
[04:20:11] <cradek> ok so home is like at the left of the table and you jogged over there?
[04:20:18] <K`zan_emc> Yes
[04:20:32] <cradek> ok now you can hit the home button
[04:20:43] <cradek> now you ARE at machine zero
[04:20:48] <cradek> g0 g53 x0 will NOT move
[04:21:00] <K`zan_emc> x now moves to -7.990 rather than zero...
[04:21:00] <cradek> if the X display does not show 0, you have some offsets in effect
[04:21:54] <cradek> are you with me?
[04:22:01] <K`zan_emc> If so, I have no idea where :-/. THe dotted box has moved WAY to the left.
[04:22:27] <cradek> ok let's go back to that wiki page about coordinate systems and follow the steps to clear the various offsets
[04:22:40] <K`zan_emc> Yes, but I see no place for offsets and unless I fumble fingeres something I didn't set any.
[04:22:48] <K`zan_emc> OK, checking again - thanks!!!!!!!!
[04:22:58] <cradek> "touch off" sets an offset, maybe you used that
[04:23:25] <cradek> ok at step 3 on the wiki page, go to mdi, g53 g0 x0
[04:23:37] <cradek> the machine will not move, since you are already at absolute zero
[04:23:38] <K`zan_emc> Ah, that may be it.
[04:23:43] <K`zan_emc> G53 G0 X0Y0Z0
[04:23:47] <K`zan_emc> oops
[04:23:51] <cradek> :-)
[04:24:01] <K`zan_emc> G92.1
[04:24:06] <K`zan_emc> arghhhhhhhhhh
[04:24:13] <cradek> haha :-)
[04:25:57] <K`zan_emc> OK, that gets everything back to 0,0,0
[04:26:12] <cradek> yay
[04:26:14] <K`zan_emc> the dotted box is still off, but that may be something in view!
[04:26:30] <cradek> maybe hit reload?
[04:26:33] <K`zan_emc> SO now I keep my hands off the "home axis button
[04:26:35] <K`zan_emc> "
[04:26:50] <K`zan_emc> reload did it!
[04:26:53] <cradek> yes you should jog to the "left" and home, then from then on, use touch-off
[04:27:16] <cradek> that way you can set soft limits to keep you from bonking into the end of travel, even though you don't have home or limit switches
[04:27:29] <K`zan_emc> not sure what touch off is yet, if it has to do with a probe, I aint got one :(.
[04:27:52] <cradek> nope, see #2.2 and #4 on that page
[04:28:05] <K`zan_emc> Thankee, will read that whole page.
[04:28:20] <cradek> touch off is the easy way to set an offset/work coordinate system
[04:28:26] <cradek> it's how you zero on a workpiece
[04:28:39] <K`zan_emc> Getting the machine dialed in slowly. Rebuilt the Z axis over the past couple days and it may be better.
[04:28:46] <K`zan_emc> Heh
[04:28:48] <cradek> ok, welcome, glad you got it figured out
[04:29:13] <K`zan_emc> Err, thanks but let credit go were due, you figured it out and lead the blind out of the darkness :)
[04:29:20] <cradek> mastering coordinate systems and tool offsets can take some time! but it's so important
[04:29:49] <K`zan_emc> Sigh, I never had to worry about that, I wrote the code, but they wouldn't let me near the machines. MUCH to learn.
[04:30:05] <K`zan_emc> Lot more to this than doing a pretty drawing and running off a tape :).
[04:30:43] <K`zan_emc> Lets see if it will draw the EMC2 AXIS thing. Got a pen refill in the chuck.
[04:30:59] <K`zan_emc> I suspect I am going to have to level up the table...
[04:31:09] <K`zan_emc> This whole thing is SO flakey.
[04:31:15] <K`zan_emc> But fun :)
[04:31:49] <cradek> heh
[04:31:51] <K`zan> http://wrlabs.shacknet.nu/~vw/MyMachineShop/PipeDreamMill/PDM-V2/
[04:32:02] <K`zan> On my desktop :)
[04:32:03] <cradek> haha pipedream
[04:32:20] <K`zan> Yeah, that is starting to look like a VERY apt description...
[04:32:40] <K`zan> A Bridgeport it ain't....
[04:32:55] <cradek> the flex shaft spindle looks clever
[04:33:23] <K`zan_emc> It came that way.
[04:33:38] <K`zan_emc> An affordable Foredom :)
[04:34:11] <cradek> have you measured the table flatness yet? that might be a challenging part
[04:34:20] <K`zan_emc> OK lets move the Z down to the table and see what happens.
[04:34:38] <K`zan_emc> The table is very flat, just in which dimensions are the questions(s).
[04:34:45] <cradek> heh
[04:34:56] <K`zan_emc> These larger steppers are a problem...
[04:35:26] <K`zan_emc> they unbalance the table. Had to Gorilla Glue some serious weights at the other ends.
[04:35:57] <K`zan_emc> I should, I guess, have gotten the floppy steppers and the single step drive I was looking at. Would have eliminated some of these problems.
[04:36:29] <cradek> floppy steppers seem good for nothing but floppy drives. I bet you did the right thing.
[04:37:10] <K`zan_emc> Well, yes, much more capable steppers (~= 60 in/oz) but also much bigger / heavier.
[04:38:05] <K`zan_emc> Here goes :).
[04:38:16] <cradek> hitting escape stops it :-)
[04:38:30] <K`zan_emc> so does the square button :)
[04:38:45] <K`zan_emc> Retracts from table contact and then never goes that far back...
[04:39:11] <cradek> ok you need to use touch off
[04:39:30] <K`zan_emc> Nothing in the EMC windows or dialogs is copyable :-(.
[04:39:45] <K`zan_emc> Lemme move it back.
[04:39:51] <cradek> you want to cut into the table?
[04:40:29] <K`zan_emc> No, got a piece of paper taped to it and a pen refill in the chuck (not turning).
[04:40:41] <cradek> ah ok. looks like the splash screen cuts 0.010 deep. this is a good number for your pen I bet.
[04:40:56] <cradek> so touch the pen to the paper and click touch-off, then accept the default of 0.0
[04:41:06] <K`zan_emc> OK, thanks
[04:41:15] <cradek> now 0.0 is the pen on the paper. -0.010 will be "into" the paper a bit.
[04:41:44] <K`zan_emc> Ok done, smoke test #2 :)
[04:41:46] <cradek> when you use touch off, you will see the program move in the preview, with respect to the cone. this gives a good feel for where it will cut.
[04:42:02] <K`zan_emc> Why do I want a big red ESTOP switch?!?
[04:42:04] <K`zan_emc> :-)
[04:42:12] <cradek> in fact, to see where a thing will be cut, jog the cone over to it, and then look at the machine to see where that is
[04:42:33] <cradek> (do you really have 7 inches of travel??)
[04:43:59] <K`zan_emc> End to end -10"
[04:44:02] <K`zan_emc> X
[04:44:09] <cradek> ah good, it will fit
[04:44:13] <K`zan_emc> Y maybe 5
[04:44:39] <K`zan_emc> Z 2.5 more or less depending on how the rebuild affects things.
[04:44:43] <K`zan_emc> DAMN!!!!!!!!!!!!!!!
[04:45:03] <cradek> uh-oh
[04:45:10] <K`zan_emc> A bit much pressure and tore the paper once, and out side of some paper wobble I done got it :).
[04:45:19] <K`zan_emc> Pix to follow in just a sec
[04:45:24] <cradek> oh, good damn, not bad damn
[04:45:29] <cradek> well yay!
[04:48:05] <K`zan_emc> There may be hope :)
[04:48:26] <K`zan_emc> Fray had to come over and check it out, I guess a nuzzle means I done good :)
[04:49:34] <cradek> or wanted to make sure you were ok after all that strange noise?
[04:53:19] <K`zan> http://wrlabs.shacknet.nu/~vw/MyMachineShop/PipeDreamMill/PDM-FirstSuccess/
[04:53:41] <K`zan> I'm about 9 feet above cloud nine :).
[04:54:01] <cradek> hey that looks great!
[04:54:15] <K`zan> Fray doesn't know what it is but he sure is happy for me :). Most companionable and sweet boy cat I ever met :)
[04:54:33] <K`zan> Paper slipped and caught once, but NOT shabby :).
[04:54:40] <cradek> yep they can be such good friends
[04:55:12] <K`zan> I never liked cats until one adopted me and proved all my previous exeperience was with utter asshole cats...
[04:55:19] <cradek> haha
[04:55:44] <K`zan> With a braincase that small, it is most interesting as to just how smart they can be.
[04:55:50] <cradek> I bet they grow up according to how they're treated
[04:56:28] <cradek> so I bet it's partly your fault he's so nice.
[04:56:31] <K`zan> Yes, I always treat my "pets" as family and the rules apply to everyone and they respond just like my dogs always did for the most part.
[04:56:48] <K`zan> True :-) True :), but I had good material to work with :-) :-) :-).
[04:57:25] <K`zan> I think the easy part is going to be getting the hardware together.
[04:57:45] <cradek> I better get to bed... goodnight and congrats on your running machine.
[04:57:56] <K`zan> Getting the CAD end together will be fun/
[04:58:13] <K`zan> Okdokee, rest well and thanks VERY much for the help and direction!
[04:58:20] <cradek> very welcome
[04:58:41] <K`zan> I think I'll float away and revel in the success :-)
[04:58:57] <K`zan> I guess I need to run through section 3 to reset that offset...
[04:59:15] <cradek> you can use machine / zero offset / G54
[04:59:35] <cradek> or, just leave it and set the next one you need later.
[04:59:46] <K`zan_emc> Thanks, just ran that.
[04:59:49] <cradek> just remember to jog "left" before you home
[05:00:04] <K`zan_emc> g0 xo y0 :)
[05:00:07] <cradek> just eyeball an origin point
[05:00:21] <cradek> yeah, g0 g53 x0 y0 z0 before you shutdown will save you some trouble.
[05:00:33] <cradek> then you can home right away next time.
[05:00:42] <K`zan_emc> copied that into my notes :). Thanks.
[05:00:52] <cradek> welcome, goodnight again :-)
[05:00:53] <K`zan_emc> cradek: Were you the one who sent me those caps?
[05:01:02] <K`zan_emc> Save it for later, go get some rest.
[05:01:05] <cradek> nope
[06:26:53] <K`zan_emc> Night folks
[06:30:10] <K`zan> Night all
[07:02:58] <alex_joni> cradek: or you can use the POSITION_FILE in the ini, that saves the position on shutdown
[11:04:00] <BigJohnT> when I run ./configure --enable-run-in-place --enable-build-documentation
[11:04:24] <BigJohnT> it gets to this line "checking for dvipng... none"
[11:04:36] <BigJohnT> and gives me this error
[11:04:49] <BigJohnT> configure: error: no dvipng, HTML documentation cannot be built
[11:05:22] <BigJohnT> do I need to change something on this line
[11:05:25] <BigJohnT> sudo apt-get install build-essential
[11:16:06] <jtr> did you run: "sudo apt-get build-dep emc2" ?
[11:18:56] <BigJohnT> yes
[11:19:46] <BigJohnT> it works fine without the --enable-build-documentation
[11:21:01] <jtr> Sounds like it's just missing from the depends list. I set up for building docs a good while ago, but don't have dvipng on my machine - guess it's a new requirement.
[11:22:19] <BigJohnT> what is the depends list?
[11:26:24] <renesis_> guys guys
[11:26:43] <renesis_> i maybe got a job running bigass wood router CNC
[11:27:18] <renesis_> hahah guy was like 'hey you dont have a problem like, putting the wood in, and like, starting the machine, and stuff, right?'
[11:27:45] <renesis_> like he had interviewed some pro draftsmen or engineers before me
[11:27:47] <jtr> BigJohnT: I'm assuming there's an input file for the "build-dep emc2" and called it the "depends list"
[11:28:12] <BigJohnT> thanks I'll look
[11:28:30] <renesis_> i got one more pcb job to do then im going to try ubuntu 8 emc
[11:29:00] <renesis_> hopefully new kernel and autodetect know wtf is going on with my hardwrae =\
[11:29:24] <renesis_> hardwrae (c) rencorp, all of the times
[11:29:50] <jtr> BigJohnT: I googled dvipng - there are hits at sourceforge if you want to install it manually for now.
[11:30:03] <renesis_> is loop code eccentric in anyway in emc?
[11:30:09] <renesis_> um, m98 and m99 i think
[11:30:23] <BigJohnT> jtr: thanks
[11:30:46] <jtr> BigJohnT: sure
[11:32:23] <BigJohnT> I did a search on my synaptic package manager and it show up there, thanks for the help
[11:37:36] <BigJohnT> well it made it past dvipng to the next line and can't find convert... at least I have a clue as to what to do now LOL
[12:22:09] <alex_joni> BigJohnT: try apt-cache search dvipng
[12:22:24] <alex_joni> that should tell you the package name where it's included
[12:22:33] <BigJohnT> ok
[12:22:51] <alex_joni> (but maybe you don't have universe turned on, so some stuff didn't install..)
[12:23:01] <alex_joni> is this for a 2.2.5 checkout? or for a recent CVS?
[12:23:15] <BigJohnT> yes universe is on
[12:23:19] <BigJohnT> tex4ht - LaTeX and TeX for Hypertext (HTML)
[12:23:20] <BigJohnT> dvipng - convert PNG graphics from DVI files
[12:23:32] <alex_joni> apt-get install dvipng ?
[12:23:33] <BigJohnT> pre 2.3
[12:23:47] <alex_joni> ok, that's why build-dep doesn't fully work
[12:23:50] <BigJohnT> I installed with with synaptic packager manager
[12:23:59] <alex_joni> (the build-dep is for an installed package: 2.2.5 in your case)
[12:24:06] <BigJohnT> ok
[12:24:08] <alex_joni> and the build dependencies have changed for pre-2.3
[12:24:15] <alex_joni> you can look in debian/control for a list
[12:24:23] <alex_joni> (if you care..)
[12:24:45] <BigJohnT> in my emc2-trunk folder?
[12:25:11] <BigJohnT> found control.in
[12:25:38] <alex_joni> yeah, that one
[12:26:07] <alex_joni> hmm.. I don't see it there
[12:26:12] <alex_joni> what platform are you on?
[12:26:12] <BigJohnT> what am I looking for in there?
[12:26:18] <alex_joni> 'dvipng'
[12:26:20] <BigJohnT> 6.06
[12:27:04] <BigJohnT> I was actually missing 3 things dvipnp, convert, and one I forgot
[12:28:16] <BigJohnT> I found convert was part of imagemagick AFAIK
[12:28:59] <alex_joni> right
[12:29:31] <alex_joni> ah, I remembered
[12:29:40] <alex_joni> build-dep only gets you stuff needed for building the package
[12:29:45] <alex_joni> (which only contains pdf docs)
[12:29:57] <alex_joni> the extra stuff you're installing now is for html docs
[12:30:19] <alex_joni> (you can also use ./configure --enable-run-in-place --enable-build-documentation=pdf)
[12:30:22] <alex_joni> or something like that
[12:32:01] <BigJohnT> ok, it seems like it worked, but just the pdf's would be ok....
[12:33:55] <BigJohnT> Oh Cool! I just noticed an index has been added to the pdf manuals
[12:34:44] <mshaver> BigJohnT: Will you be coming to the CNC Workshop?
[12:36:28] <BigJohnT> I'm not sure at this point. We finished one automatic yesterday and have 3 more (these are the same) automatics to have done by July 1
[12:37:05] <BigJohnT> We have most of the parts started and I have 99% of the engineering done so it's a toss up at this point
[12:38:52] <mshaver> It would be nice to meet you. I like what you did with the g-code generating python scripts, so I hope you get done in time!
[12:41:01] <BigJohnT> thanks
[12:41:21] <BigJohnT> alex_joni: I did get one error man9/pluto_servo.9:106: warning [p 144, 4.3i]: can't break line
[12:42:19] <BigJohnT> mshaver: it would be nice one day to roll that work into a real cam program that can import dxf files etc...
[12:43:23] <BigJohnT> actually 14 errrors on the same page...
[12:44:25] <mshaver> That's my hope as well. One of my biggest problems is having a CAM solution I can give to my clients. None of the commercial stuff, even disregarding price, really suits me. Too wierd of a GUI, too high a learning curve, bad g-code output, poor support, etc...
[12:45:18] <mshaver> and most people's requirements are simple 2.5D, rectilinear type parts!
[12:46:54] <BigJohnT> SheetCam is not bad and pretty cheap too. I agree with you on that most are not intutive to use
[12:47:43] <mshaver> yep, that's probably one of the best ones.
[12:48:09] <BigJohnT> gcnccam is at least on linux but it's very young in it's development
[12:48:30] <mshaver> Well, it's out to the shop with me! Lots of things to scrap & blow up today ;) !
[12:48:39] <BigJohnT> mine is version 0.4.4
[12:48:46] <BigJohnT> have fun
[12:50:08] <mshaver> true, there's a lot of promising projects. It's hard to decide which star to hitch your wagon to though... Back later, keep saying interesting things so I have something to read when I come in the office for coffee! :)
[12:50:54] <BigJohnT> I have to shut this computer down for a bit so I'll ttul
[13:00:10] <dimas_> * dimas_ just finished soldering an interface board
[13:44:37] <alex_joni> hey matt
[15:30:14] <JymmmEMC> So, has everyone updated their keys yet? LOL
[15:34:10] <JymmmEMC> alex_joni: Have them ISO's been updated?
[15:38:06] <assargadon> hi there
[15:39:52] <jepler> JymmmEMC: the correct way to address the ssh issue is to use the normal update procedure.
[15:40:23] <JymmmEMC> jepler: you still have to destroy ALL existing keys and regenrate them.
[15:41:00] <jepler> JymmmEMC: what's your point?
[15:41:09] <JymmmEMC> jepler: Has that been done?
[15:41:26] <jepler> JymmmEMC: when you install a fixed openssh-server package, the host key is regenerated if it was a vulnerable key.
[15:43:36] <jepler> if you used key-based authentication, you have to manually go remove that compromised key from any .ssh/authorized_keys files where you put it
[15:43:44] <JymmmEMC> jepler: That can't be, then anyone who uses keys only to get into a box, would never be able to get in. The keys have to be regenerated manually
[15:44:26] <JymmmEMC> I've already ran the updates, and don't use keys only, and theys are not changed automagically.
[15:45:55] <JymmmEMC> what do yo mean by "fixed" anyway?
[15:46:17] <jepler> JymmmEMC: if you put a compromised key in the ~/.ssh/authorized_keys file of any machine, you have to manually remove it yourself
[15:47:11] <jepler> JymmmEMC: by "fixed", I mean the openssh* packages that Ubuntu/Canonical released in order to fix the vulnerable key generation problem.
[15:47:37] <JymmmEMC> jepler: Right, put many ppl aren;t aware of that, and barely even read the "are you sure you want to add this key" dialog =)
[15:47:50] <JymmmEMC> ...when connecting to a new box
[15:47:58] <jepler> this is the fragment of the 'postinst' script which is intended to automatically cause the host key to be regenerated:
http://pastebin.ca/1021082
[15:49:47] <JymmmEMC> Just be glad that this didn't happen to GPG, we'd be fucked if that was the case.
[15:51:05] <JymmmEMC> In just 30 minutes, we found over 5000 duplicate keys
[15:58:38] <JymmmEMC> jepler: Maybe I missed it, but do the ISO have the vulnerability or have they been patched already?
[15:59:42] <jepler> JymmmEMC: as far as I know, the 8.04 live cd was made before the updated packages were released. we do not reissue the cd just because updates (even security updates) are released.
[15:59:54] <jepler> that is, the emc2 8.04 live cd
[16:00:42] <jepler> (as far as I know, canonical/ubuntu also don't reissue cd images just because security updates are released)
[16:06:16] <JymmmEMC> I just looked, they don't even have mention of it on the front page or release notes. I don't feel that's right. Especially due to the impact this vulnerability allows.
[16:09:24] <tomp> alex_joni: messages seen at boot time with 8.04/emc2 live cd
http://pastebin.ca/1021098
[16:10:50] <tomp> JymmmEMC: is this your page?
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TestedHardware. could you post your working emc system?
[16:11:35] <JymmmEMC> tomp: It was an attempt to, yes.
[16:12:01] <tomp> could you post your system to it? I'll prep mine, but they're bad news
[16:12:53] <JymmmEMC> What, you no like my Acme system?
[16:15:33] <tomp> JymmmEMC: the following is not pointed to you:
[16:15:35] <tomp> I've installed the live CD to 2 systems now, both get overruns,
[16:15:35] <tomp> and I've gone thru the troubleshooting page, turned off APM ACPI USB OnBoard video...
[16:15:35] <tomp> I installed 6.06 to 4 machines, and all had overruns.
[16:15:35] <tomp> I has not been running the latency tests previously, so some of the results are back-checking.
[16:15:35] <tomp> Therefore I think that mobos that run EMC2 w/o overruns are not common.
[16:15:36] <tomp> Please post any better results so users dont waste time and money on stuff that wont work.
[16:16:18] <tomp> the top live cd refers to 8.04 with emc
[16:17:00] <JymmmEMC> Ok, so why not add those systems to that page?
[16:17:07] <K`zan> Tried that yesterday with the hope it would deal with my wireless dongle. No luck. Interestingly the stock ubuntu 7.10 does. LOL, sigh.
[16:17:16] <tomp> fine, a page full of bad new coming right up
[16:17:39] <JymmmEMC> tomp: The top of the page DOES say "good, bad, and ugly"
[16:17:53] <K`zan> LOL, appropos :-)
[16:18:00] <SWPadnos> tomp, I've seen that problem "every once in a while", on 6.06 and 7.10 systems
[16:18:11] <SWPadnos> (the "error starting settings daemon" thing)
[16:18:32] <SWPadnos> on both EMC2 and non-EMC2 installs
[16:19:03] <JymmmEMC> * JymmmEMC dictionaries SWPadnos systems with the 32K dict file =)
[16:19:17] <SWPadnos> * SWPadnos gets out the 64k dict file
[16:19:29] <tomp> my main concern is a system that works, i want some confidence that it is possible
[16:19:32] <JymmmEMC> SWDamn dude, you need to get some QUALITY p0rn in there
[16:20:04] <SWPadnos> the quality pr0n is on a non-net-connected server
[16:20:13] <JymmmEMC> tomp: The reason for getting bad results too is 1) So ppl are aware of it, and 2) It could be a BIOS bug as well.
[16:20:31] <JymmmEMC> SWPadnos: lame
[16:21:13] <JymmmEMC> SWPadnos: Share the wealth, QUALITY p0rn is a rare thing.
[16:21:33] <SWPadnos> you'd have to sign an NDA
[16:21:39] <archivist> time to start hacking
[16:22:01] <tomp> anyone want to post one viable system on that page while i prep the text about the ones that do not work?
[16:22:46] <JymmmEMC> SWPadnos: been there, done that.
[16:26:56] <K`zan> Picked up a 1F/16V cap at the thrift store yesterday :). $5.00 :)
[16:27:14] <SWPadnos> SUPERCAP!
[16:27:42] <K`zan> A little research shows it is supposed to be for "stiffening" car audio power (lights dim on the bass passages).
[16:28:09] <K`zan> Personally I''d like to see RPGs for those folks, can hear them 3-4 blocks away...
[16:28:24] <rayh> Seems like the 16 volt might be an issue with an alternator.
[16:28:37] <SWPadnos> yep. check eBay for things like fuse holders and high current distribution blocks, and they're almost all for high power car stereos
[16:28:43] <K`zan> 2 more and it might do wonders for the drive power supply :0
[16:28:57] <SWPadnos> don't get too large a cap
[16:29:08] <SWPadnos> that will destroy the transformer
[16:29:10] <K`zan> Mostly I got it because I always just wanted a 1F cap :)
[16:29:15] <SWPadnos> heh
[16:29:21] <K`zan> Silly me :)
[16:29:45] <K`zan> Built one years ago that occupied several boxes using individual caps - not practical...
[16:29:56] <K`zan> This is about the size of a TALL beer can.
[16:30:03] <SWPadnos> wow - DigiKey sells 5000F caps
[16:30:08] <SWPadnos> (only 2.7V, but still)
[16:30:30] <K`zan> :-(, figures,finally reach a goal and it isn't even significant anymore :)
[16:30:45] <K`zan> RUn a LED for the rest of your life on 5KF :)
[16:30:58] <rayh> Night light
[16:31:08] <K`zan> LOL
[16:31:44] <K`zan> Might do that. Other than final gratification, I have no idea what to do with it. I will NOT have a car stereo that need it :)
[16:32:29] <rayh> okay. That's the last of the rm -rf .ssh
[16:32:47] <rayh> Now to see if I can get back into any of the other boxes.
[16:33:39] <SWPadnos> hmmm. Q=CV, i=dQ/dt=20mA=C dV/dt, so every second it loses 0.02/5000V = 4 microvolts
[16:34:27] <SWPadnos> assuming a 1.7V LED (for simplicity), that gives 1V loss before significant dimming, so 1.0.000004 = 250000 seconds
[16:34:33] <SWPadnos> which is only 3 days
[16:34:41] <SWPadnos> (or thereabouts)
[16:34:53] <K`zan> Sigh...
[16:34:55] <SWPadnos> I wonder if I did something wrong. that sounds awfully low :)
[16:35:27] <K`zan> I'll enjoy looking at it, I guess.
[16:35:34] <SWPadnos> err - that should have been 1/0.000004
[16:35:37] <SWPadnos> heh
[16:35:54] <SWPadnos> just don't charge it up then drop a wrench across it :)
[16:36:07] <K`zan> Could use it for a spot welder I suppose....
[16:37:07] <archivist> internal resistance may limit peak current to spoil the fun
[16:37:34] <K`zan> OK, I think we are down to having a 1F cap on the shelf :)
[16:38:07] <K`zan> Connectors it comes with are scary enough.
[16:43:41] <JanVanGilsen> hi, I'm experimenting with the gtksourceview-2.0 functions that come with ubuntu 8.04,
http://imagebin.org/18234
[16:45:01] <SWPadnos> cool. I think this was with rev 1.0, so maybe you could help update it :)
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Highlighting_In_Gedit
[16:45:33] <JanVanGilsen> my question, is the cfg-string obligated with the hal_parport component, or does it use a default base adress :)
[16:45:45] <JanVanGilsen> yes, i wrote that wiki page
[16:45:52] <SWPadnos> oh - ok :)
[16:46:10] <SWPadnos> I recall helping someone on IRC to get the regexes correct :)
[16:46:21] <SWPadnos> (but I could havebeen remembering something else)
[16:46:26] <JanVanGilsen> indeed that was me
[16:47:02] <SWPadnos> I think the parports are scanned in the order 0c3bc,0x378, 0x278 if no cfg parameter is specified
[16:47:38] <SWPadnos> I guess I could look at the source :)
[16:48:38] <SWPadnos> oh, nope. cfg is required now :)
[16:48:48] <JanVanGilsen> gtksourceview2 has an "extended" option, so the regexp ignores spaces :)
[16:48:58] <SWPadnos> cool
[16:49:06] <assargadon> Is it impossible to get some integer data from Virtual panels?
[16:49:13] <SWPadnos> no
[16:49:25] <assargadon> so pity
[16:49:38] <SWPadnos> maybe. I'm not sure if the slider/knob controls have s32 outputs or only float outputs
[16:49:54] <SWPadnos> heh - you asked if it's impossible. I said no, meaning that it is possible :)
[16:50:04] <assargadon> :)
[16:50:12] <assargadon> maybe I hate integers ;)
[16:50:16] <SWPadnos> but I'm not positive now :)
[16:51:09] <JymmmEMC> tomp: Happy now?
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TestedHardware
[16:51:31] <tomp> thanks for any effort, dodnt look yet, still wrtiing
[16:52:41] <JanVanGilsen> the hardest part will be adding al the emc components, functions and pins to the .lang file :)
[16:53:12] <tomp> JymmmEMC: thats nice, thanks, thats a micro board like rayh's, maybe i shouldnt try these normal desktop
[16:54:23] <SWPadnos> assargadon, the "Scale" control (a slider) has both a float and an integer output
[16:54:39] <assargadon> SWPandos, thanks
[16:55:47] <SWPadnos> JanVanGilsen, I think the loadrt word should still be hilighted on those "should not pass" lines
[16:55:58] <SWPadnos> but not the module name
[16:56:43] <rayh> I have found over time that different via MiniITX boards produce quite different latencies.
[16:56:56] <JanVanGilsen> I'll look intoo that =)
[16:57:01] <JymmmEMC> rayh: feel free to add your results to that page
[16:57:05] <rayh> I wonder if we should expand the board name to include models.
[16:57:09] <SWPadnos> also, if it's possible to have a couple of colors, it might be good to either hilight the instance number differently (parport.0 vs parport.1) or hilight the whole pin name differently for each instance
[16:57:37] <SWPadnos> hmmm. option 2 would get pretty confusing, so maybe just the numbers inside pin names :)
[16:58:14] <JanVanGilsen> okey that was easy, just adding a ?
[16:59:11] <tomp> rayh: thanks, i found those boards. your info is handy for users.
[17:01:10] <JanVanGilsen> SWPadnos, i dont know how I'd do that
[17:01:22] <SWPadnos> yeah, me either :)
[17:04:50] <awallin> the TestedHardware page should probably be merged with
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Latency-Test
[17:05:49] <JanVanGilsen> is there a man-page on the net command?
[17:06:01] <SWPadnos> halcmd help net
[17:06:09] <SWPadnos> or man halcmd
[17:06:20] <SWPadnos> (hopefully at least one of htose places has the info)
[17:06:23] <SWPadnos> those
[17:09:19] <rayh> Have you guys seen the hardware testing menu item in 8.04. I wonder if we could produce a similar thing for emc2
[17:11:55] <assargadon> how IO pins can be used at all? As far as I understand, every "net" should have exactly 1 input...
[17:12:27] <JanVanGilsen> loadrt at_pid num_chan=num [debug=dbg] , on the manpage it states "If numchan is not specified, the default value is three", shouldn't that be loadrt at_pid [num_chan=num] [debug=dbg]?
[17:21:40] <tomp> JymmmEMC: 1 entry added, will get the other systems next
[17:25:35] <JymmmEMC> tomp: If you're going to included video driver, you need to add the version of it too.
[17:26:53] <JymmmEMC> tomp: Also, try to keep the same syntax, as then it be easier to parse out into CSV if ever needed.
[17:27:38] <tomp> version wasnt reported in xorg dump, will look
[17:28:06] <tomp> i'll keep same syntax, please give example, didnt understand
[17:28:32] <JymmmEMC> tomp: Cpu info, it's one big entry, not comma seperated.
[17:28:42] <tomp> gotch, no commas
[17:29:20] <JymmmEMC> example: Pentium4, 800MHz, 533MHz,512K
[17:29:36] <tomp> you want commas, ok
[17:29:59] <JymmmEMC> While the board may be capacble of 400/533/800MHz, would rahter know what you are currently running it at.
[17:30:35] <tomp> 800
[17:30:54] <JymmmEMC> cpu freq != bus speed
[17:31:18] <tomp> right, i said cpu was 800, i said bus was 400/533/800
[17:31:36] <JymmmEMC> But what is it running at?
[17:31:48] <JymmmEMC> it's not running at ALL those speeds at the same time.
[17:31:53] <tomp> i dont know how to tell, could you tell me?
[17:32:13] <JymmmEMC> afraid not, maybe your manual could.
[17:32:17] <tomp> thx
[17:32:52] <tomp> will reboot and see if it says anything, then re-edit, thx
[17:32:54] <JymmmEMC> If you don't know just leave it blank, or better yet, just add an extra comma, like Pentium 4, 800Mhz,,512K
[17:33:17] <tomp> rebooting
[17:34:01] <tomp> memeory freq is at DDR333, does that mean 333mhz bus?
[17:34:06] <tomp> bios sez
[17:34:20] <JymmmEMC> no
[17:34:30] <SWPadnos> DDR333 actually means 166x2 (data is clocked on both edges of the clock)
[17:34:45] <tomp> i only get a few hundred ms at first text splash screen, re-trying now
[17:38:43] <tomp> dram clock is 166, yes, host/pci is 100/33Mhz , is 166 the 'bus freq' ?
[17:40:06] <SWPadnos> 100 I think
[17:40:31] <SWPadnos> the I/O bus is running at 100 I'd think
[17:40:33] <JymmmEMC> tomp: dont sweat it, I revised your entry alredy
[17:40:53] <tomp> so, the column header should be host frequency?
[17:40:54] <JymmmEMC> tomp: Just FYI, *ANY* overrun at all, is bad.
[17:41:08] <SWPadnos> well, time to look at the big outdoors (before it starts raining)
[17:41:11] <SWPadnos> bbl
[17:41:27] <JymmmEMC> tomp: Techincally FSB Freq
[17:41:50] <JymmmEMC> tomp: but abbr to Bus for brecity
[17:41:54] <JymmmEMC> brevity
[17:42:02] <JymmmEMC> (sp)
[17:42:16] <tomp> i got that all overruns mean no emc, yours doesnt work, mine doesnt work, i'm looking for one that does as soon as i get these reports out
[17:46:27] <assargadon> ah
[17:46:58] <assargadon> I tested my realtime port of my controller driver
[17:47:08] <assargadon> and I got a strange errors
[17:47:36] <assargadon> it looks like SOMETIMES other data became written to LPT port
[17:47:45] <assargadon> not one I put there
[17:48:23] <assargadon> I read man about rtapi_outb, and rtapi_request_region listed there
[17:48:58] <assargadon> 1) is error I talking about can be caused by non-using of rtapi_request_region ?
[17:49:31] <assargadon> 2) why my code still works without rtapi_request_region ? I thinking it's something similar to io_perm
[17:49:39] <assargadon> * assargadon reading rtapi_request_region's man
[17:51:52] <JymmmEMC> brb
[17:59:14] <tomp> SWPadnos: thx for the entry, will look for that board
[18:07:26] <assargadon> aggggr
[18:08:04] <assargadon> can't find error... I just replaced "normal" calls to "rtapi" ones....
[18:18:50] <jepler> if all drivers use rtapi_request_region (emc rtai) request_region (linux), then you can be confident that only one driver is writing to the I/O region at a time. If at least one does not, then you can't.
[18:19:47] <jepler> (a userspace program which uses iopl(2) or ioperm(2) could also interfere)
[18:21:45] <assargadon> jepler, yes, I just read man's about it...
[18:21:54] <assargadon> but I still do not understand
[18:22:07] <assargadon> I making experiments, thought :)
[18:25:26] <assargadon> Ah
[18:25:57] <assargadon> As always, you catch the error yourself as fast as you ask for help :)
[18:26:19] <assargadon> needed delay was 1 millisecond
[18:26:37] <assargadon> and thread period was 50 microseconds
[18:27:11] <assargadon> those numbers in different files, so it's hard to catch :)
[18:28:25] <JymmmEMC> tomp: Are you looking for a system that just works?
[18:29:20] <JymmmEMC> tomp: If so, this might do the trick...
http://www.weirdstuff.com/cgi-bin/item/62008 I might be able to confirm this next week.
[18:30:42] <assargadon> now I should invent good, structured and maintanable way to make "timer-like multiloops" delays instead of rtapi_delay calls :)
[18:40:27] <tomp> JymmmEMC: thanks, yes i am just looking for something that works
[18:41:50] <JymmmEMC> tomp: I have some RackMount (tm) boxes at work, but I haven't tested them.
[18:42:12] <JymmmEMC> LOUDER THAN A MOBO though.
[18:42:17] <JymmmEMC> MOFO
[18:49:36] <tomp> i have 12" fans 120V~ in some of mine, doesnt bother me after working around presses and big mills :)
[18:51:24] <tomp> i just asked a reseller in Dallas if he'd test a system with the live cd& the latency test, I would pay for testing in anycase.
[18:52:49] <JanVanGilsen> SWPapadnos, this is what I've go so far:
http://pastebin.com/m56d11496
[18:53:21] <JanVanGilsen> *SWPadnos ;)
[19:12:08] <gefink> Hallo
[19:12:43] <gefink> I have a question about steplen and stepspace
[19:12:52] <jmkasunich> just ask
[19:13:25] <gefink> Does one know why stepconf is using 0 and 1 for steplen and stepspace?
[19:14:40] <jmkasunich> stepconf uses the "doublestep" approach to step generation, to allow a higher step rate
[19:14:52] <jmkasunich> that means steplen is set to zero
[19:14:58] <gefink> I think i have short pulses while using high acceleraton and speed near maxfreq.
[19:15:19] <jmkasunich> your pulses should all be the same length
[19:15:21] <gefink> how wide is the pulse in this case?
[19:15:45] <SWPadnos> that's set by parport.0.reset-time (or similar)
[19:15:53] <gefink> the value used in stepconf is 5000 ns
[19:16:04] <SWPadnos> is that enough for your drives?
[19:16:42] <gefink> 2500 shold be enough
[19:17:03] <SWPadnos> then you can set it to 2500 in stepconf
[19:17:10] <gefink> moment, i check parport.0.reset-time
[19:17:12] <SWPadnos> the default is for Geckodrives, I think
[19:17:36] <gefink> I use smc-servo from elm
[19:17:44] <SWPadnos> hmmm. maybe not, but you can change the values :)
[19:18:43] <gefink> setp parport.0.reset-time 9000
[19:19:06] <SWPadnos> hmmm. interesting
[19:19:09] <gefink> that shold reach
[19:19:33] <gefink> now i know why this config works, but the last not
[19:19:34] <SWPadnos> you want the reset-time to be as short as possible, while still running the drives properly
[19:19:42] <gefink> thanks
[19:19:46] <SWPadnos> sure
[19:20:17] <gefink> sw: is parport.0.reset-time also used for stepspace?
[19:20:31] <SWPadnos> no
[19:21:32] <tomp> JymmmEMC: this is very close to same hdwr as that Tyan S2518 , its a Tyan S2510 but only 19$ less cpu less mem...
http://www.weirdstuff.com/cgi-bin/item/15184
[19:21:34] <gefink> mean this the signal is set while stepgen is called and reset after parport.0.reset-time
[19:22:19] <SWPadnos> yes. if stepgen says it needs a step, then its output will be set. the next interrupt, the parport pins are written at the start of the thread, then reset later by the parport.0.reset function
[19:22:58] <SWPadnos> with steplen 0, stepgen knows that it can request a step every interrupt, rather than every second interrupt
[19:24:03] <gefink> thanks. I will remove the sikefilter from my controller. then it shold work
[19:24:16] <gefink> spike-filter
[19:24:29] <SWPadnos> heh - good luck
[19:25:13] <gefink> I think its no problen, now i know for what i mast look
[19:25:20] <jepler> basically, in stepconf the step "0" timing is justified based on choosing BASE_PERIOD so that (BASE_PERIOD - latency - steplen - 5000) > stepspace
[19:26:44] <gefink> all worked well if acceleration is under 300 with speed 20mm/s
[19:31:26] <K`zan_emc> I found the latency test once, but for the life of me I can't find it now :-(, help please?!?
[19:31:42] <SWPadnos> open a terminal, type latency-test
[19:31:56] <K`zan_emc> SWPadnos: Thanks :-) <blush>
[19:32:00] <JymmmEMC> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TroubleShooting#RTAI_Latency_test
[19:32:01] <SWPadnos> heh
[19:32:06] <SWPadnos> see you all later
[19:32:13] <K`zan_emc> Thanks es later!
[19:37:04] <gefink> servo is modified. go testing
[19:46:01] <K`zan_emc> I'm really confused about the home/limit switches. Must have to do with the limited number of inputs on the parallel port.
[19:46:26] <K`zan_emc> I suppose one must create something external to monitor them and send that through the driver to EMC.
[19:46:40] <K`zan_emc> Seems that one would want them separate anyway...
[19:47:07] <rayh> Parport is why we piled them all in together.
[19:47:08] <K`zan_emc> Trying to figure out what to do for a test next :).
[19:47:32] <K`zan_emc> OK, that does make sense if seemingly "chancy".
[19:47:46] <K`zan_emc> * K`zan_emc is VERY ignorant of a LOT of this at this point.
[19:48:05] <rayh> You certainly loose the info about which axis and which end that way.
[19:48:15] <K`zan_emc> First ?successful? run of the Pipedream last night.
[19:48:49] <rayh> Fill me in on the Pipedream?
[19:48:55] <skunkworks> printer ports are cheap...
[19:48:57] <K`zan_emc> So it would seem, no way to tell which was which. Home seems to make sense and let EMC deal with the limits?!?
[19:49:01] <K`zan_emc> Hold...
[19:49:13] <K`zan_emc> Ah, multiple parallel port cards.
[19:49:35] <K`zan> http://wrlabs.shacknet.nu/~vw/MyMachineShop/PipeDreamMill/
[19:50:21] <assargadon> K`zan, yes, multiple LPTs
[19:50:24] <assargadon> or
[19:50:38] <assargadon> special interface cards with special drivers
[19:50:40] <assargadon> or
[19:50:42] <K`zan_emc> Had to go to the desktop to paste that.
[19:50:44] <gefink> Thanks, now without my spikefilter all works well
[19:51:03] <K`zan_emc> assargadon: I can see some exciting construction to fully implement that.
[19:51:18] <assargadon> "something external", as you told abvout
[19:51:19] <K`zan_emc> * K`zan_emc lusts for a big red estop button first though :)
[19:51:22] <assargadon> *above
[19:51:29] <K`zan_emc> rr
[19:52:07] <rayh> nice job. good to hear it's working.
[19:52:46] <K`zan_emc> Thanks, but it is certainly going to need adjusting, of that I am sure. Last pass took care of a lot of it.
[19:52:59] <K`zan_emc> Might work out now if I am not planning on doing work for NASA :)
[19:53:23] <rayh> Makes you feel great when it begins to work like it should.
[19:53:36] <K`zan_emc> Need to go get a piece of PCB and make a square on it to see how level everything actually is.
[19:54:04] <K`zan_emc> And for that I have to learn to write enough G-code or find a toolchain that will do it for me.
[19:54:22] <K`zan_emc> I knew I was right to presume that the hardware would be the easy part.
[19:54:25] <gefink> now i must use an hardwarespikefilter
[19:55:50] <rayh> gefink, Where you thinking of putting it in the circuit?
[19:56:51] <gefink> rayh: its a atmega- interruptpin, think about c+ schmitt-trigger
[19:57:40] <K`zan_emc> Which value do I want to plug into stepconf from the latency test? Higher of the two or servo or base thread?!?
[19:58:12] <gefink> or better replace hcpl 2631 with hcpl2231 which includes trigger.
[19:58:14] <K`zan_emc> None of anything to do with EMC - window/dialog is copyable, arghhhhhhhhh
[20:01:20] <rayh> Ah okay. I see what you are aiming at gefink.
[20:08:10] <assargadon> give me the link to good site about rtapi, please
[20:08:49] <SWPadnos> http://www.linuxcnc.org/
[20:08:51] <assargadon> I trying google, but somewhy first page fulfilled with not-very-usefull links
[20:08:54] <assargadon> :)
[20:09:15] <SWPadnos> RTAPI was written by one of the original EMC developers at NIST, and I think EMC is the only thing outside of NIST that uses it
[20:11:59] <K`zan_emc> servo thread shows 51061 so I'll use that one, been abusing the box for an hour now. LONG way from 15000 default :-/.
[20:12:42] <gefink> is there not difference between rtai ant rtapi
[20:14:08] <gefink> 51061 latency?
[20:14:15] <K`zan_emc> Seem that this HP 2K celeron should do better than it does. Compared to the 2.2G AMD it is a slug.
[20:14:27] <K`zan_emc> servo thread jitter, yes.
[20:14:40] <gefink> oh
[20:14:51] <K`zan_emc> I presume the bold values are what one wants and the highest of the two.
[20:15:08] <K`zan_emc> wiki isn't real informative....
[20:15:29] <K`zan_emc> program reports jitter, stepconf wants latency.
[20:15:39] <K`zan_emc> Perhaps trivial to folks with a clue :).
[20:15:47] <assargadon> SWPadnos, you are wrong about "only EMC uses RTAPI"
[20:16:18] <K`zan_emc> FOOD! bbiab
[20:17:26] <gefink> good night
[20:22:46] <assargadon> greate!
[20:23:13] <assargadon> It's much easier to implement realime delays then I thought :)
[20:24:47] <assargadon> I just should use rtapi_wait :)
[20:25:21] <assargadon> and some kind of time measuremeNT
[20:44:22] <assargadon> ha!
[20:44:25] <assargadon> It works!
[20:45:06] <assargadon> quite easy, quite simple ;)
[20:45:09] <Guest604> Guest604 is now known as skunkworks
[21:04:25] <K`zan_emc> ( AXIS "splash g-code" )
[21:04:40] <K`zan_emc> Is that just a comment of an AXIS directive?
[21:12:08] <K`zan_emc> joint 0 following error ?!?
[21:13:22] <jmkasunich> in g-code, things in () are comments
[21:14:44] <K`zan_emc> Perhaps running it with the drive powered down is the problem, although I can't imagine how it would detect a feedback problem.
[21:15:07] <K`zan_emc> THanks, wasn't sure if stuff could be embedded in comments (like #!/bin/sh) just wanted to be sure.
[21:15:34] <jmkasunich> this is steppers?
[21:15:59] <K`zan_emc> Yes
[21:16:04] <jmkasunich> if steppers, powering down the drives won't make a difference
[21:16:20] <jmkasunich> do you have backlash comp enabled (a non-zero value for backlash in your ini file)?
[21:16:25] <K`zan_emc> I can't imagine the gcode is a problem.
[21:16:43] <K`zan_emc> Not that I know of. Still setting things up here.
[21:16:46] <jmkasunich> did you create your config using stepconf, or manually
[21:16:52] <K`zan_emc> stepconf
[21:17:18] <jmkasunich> post your ini file on pastebin.ca so I can take a look
[21:17:27] <K`zan_emc> rr tnx
[21:19:38] <K`zan_emc> http://www.pastebin.ca/1021324
[21:21:00] <K`zan_emc> And the gcode - my first in the last 15 years :):
[21:21:03] <K`zan_emc> http://www.pastebin.ca/1021325
[21:21:36] <K`zan_emc> FWIW, last night I ran the EMC2 AXIS demo file with no problems...
[21:21:59] <jmkasunich> you don't have any margin on your max velocity
[21:22:15] <K`zan_emc> Err, huh?
[21:22:19] <jmkasunich> 65000nS period means a maximum of 15384 steps per second
[21:22:45] <K`zan_emc> lemme start stepconf
[21:22:59] <jmkasunich> your scale is 16000 steps per inch, so your max speed is 15384/16000 = 0.961
[21:23:01] <jmkasunich> no, don't
[21:23:10] <jmkasunich> stepconf will overwrite your ini file
[21:23:25] <K`zan_emc> yes, that is all that has ever accessed it, to date...
[21:23:44] <K`zan_emc> Done it all with stepconf (warnings made me paranoid about messing with it)
[21:23:49] <jmkasunich> I don't use stepconf, and I don't know how it works - but the numbers in this ini file are no good
[21:24:36] <K`zan_emc> max speed relates to IPM ?
[21:24:46] <K`zan_emc> * K`zan_emc is very ignorant at this point...
[21:24:58] <jepler> K`zan_emc: can you pastebin the stepconf file too?
[21:25:09] <jmkasunich> [AXIS_n]MAX_VELOCITY is the speed it will try to travel for rapids - in inches per second
[21:25:09] <K`zan_emc> should be using F1 rather than the F10?
[21:25:11] <K`zan_emc> Yes.
[21:25:16] <K`zan_emc> just a sec
[21:25:30] <jmkasunich> no, F10 is fine - that is inches per minute
[21:25:39] <jmkasunich> all speeds in g-code are in units per minute
[21:25:49] <jmkasunich> but ini file and hal numbers are inches per second
[21:25:53] <jmkasunich> (or mm per second)
[21:26:55] <jepler> in the present released version of stepconf, it will write bad .ini files if you enter a step rate higher than you can do based on your timings that you enter on the second (third?) page. Did you enter a really large value for jitter/latency, for step space, or for step length?
[21:27:19] <jepler> (the next version is supposed to automatically lower the speed you enter until it is possible to reach it)
[21:27:25] <K`zan_emc> http://www.pastebin.ca/1021331
[21:28:15] <K`zan_emc> I entered the high value for jitter out of the latency test which was 51061 (it rounds to 50000).
[21:28:16] <jepler> you entered 50000ns as the latency -- that has a very big impact on the maximum number of steps per second you can achieve <property name="latency" type="float" value="50000.0"/>
[21:28:45] <K`zan_emc> It seemed to work fine with the 15000 default, but I was trying to do this "right" :-)
[21:29:10] <K`zan_emc> I mucked about for about an hour to get that value in stepconf, seriously abusing the box.
[21:30:05] <K`zan_emc> How about I just go back to the default and let this go - not a clue as to what it really means other than to screw up the process :-/.
[21:30:35] <jepler> OK, you have several choices that should each get rid of the "following error": change jitter to a lower number than you actually saw, or change the max speed to be lower.
[21:30:58] <jmkasunich> given the small size of your machine, you could probably lower max speed and still be happy
[21:30:59] <jepler> if you put a lower number than your system's actual jitter, then there's a chance that the timings of the step waveform will not be in spec for your steppers
[21:31:00] <K`zan_emc> As noted, it seems to run OK with the default...
[21:31:13] <jmkasunich> my shoptask only does 48 IPM = 0.8 inches per second
[21:31:22] <jepler> the next version of stepconf/emc will detect this specific problem and automatically lower the speed (e.g., from 1.0 to 0.8)
[21:31:33] <jepler> (or whatever is within the limits according to the values you enter)
[21:31:33] <jepler> bbl
[21:32:08] <K`zan_emc> OK, so go back anu put in the 50K value and then muck with the individual axis values until it works?
[21:32:12] <K`zan_emc> ah, rr
[21:32:16] <jmkasunich> K`zan_emc: changing to the default is not a good idea - sure, it will let you get to 60 ipm, but when you inevitably get a 30000 or 40000 or 50000nS jitter event (rare) it might make you lose steps
[21:32:29] <jmkasunich> don't "muck with" them
[21:32:31] <jmkasunich> do the math
[21:32:48] <K`zan_emc> math?
[21:33:00] <jmkasunich> 65000nS = 15384 steps per second, and at 16000 steps per inch, your max speed is 0.9something inches per second
[21:33:03] <K`zan_emc> ekkk
[21:33:14] <jmkasunich> so tell stepconf you want 0.8 inches per second to give yourself some margin
[21:35:09] <K`zan_emc> Hummm, is that Max Velocity or Max Acceleration we are talking about here?
[21:35:52] <K`zan_emc> Velocity I think (in/s) acceleration is in/s2
[21:36:16] <jmkasunich> velocity
[21:36:30] <K`zan_emc> Done, thank you sir (from 1.0 to 0.8)
[21:36:47] <K`zan_emc> firing emc back up
[21:37:37] <K`zan_emc> Wonder what the green line with the X on it means?
[21:37:50] <K`zan_emc> about 1/3 the way down the first X move.
[21:38:28] <K`zan_emc> Works! Thanks folks!
[21:38:46] <K`zan_emc> Now do I get bold and track down a cutter and a piece of PCB or cower in the corner :)
[21:39:29] <rayh> I'd vote for both. Set it up, start it up, cower in the corner.
[21:40:27] <jmkasunich> with safety glasses on
[21:43:24] <K`zan> LOL, good plan.
[21:43:26] <K`zan> Looking to see what thickness the cladding on PCBs actually is - I question my z -0.01 value.
[21:43:32] <K`zan> Of course, google is toast here ATM :)
[21:43:39] <jmkasunich> you mean the copper?
[21:43:46] <jmkasunich> I think 1oz copper is 0.0014
[21:44:35] <K`zan> Corresponds to what I found, thanks:
[21:44:36] <K`zan> 1/2 oz. 0.7 mils
[21:44:36] <K`zan> 1 oz. 1.4 mils
[21:44:36] <K`zan> 2 oz. 2.8 mils
[21:44:51] <K`zan> S0 0.01 is probably overkill :)
[21:45:00] <jmkasunich> a bit
[21:45:14] <jmkasunich> this will be a demanding test of the flatness and squareness of your table
[21:45:24] <K`zan> Want to get an idea of how level the table is - affixing the PCB with double sticky tape...
[21:46:00] <K`zan> jmkasunich: Yes, I know <shudder> I expect to be disappointed but it will let me know what to do next.
[21:47:21] <tomp3> put a dish of water on it, the ring edge shows you level... the squareness of the quill motion to that surface is harder to inspect, but a bent piece of wire in the chuck swung over the surface in a large arc will say a lot
[21:47:58] <tomp3> or get an indicator and 123 blocks ;)
[21:53:32] <rayh> Level isn't as important as squareness of motion.
[21:54:57] <rayh> I'd put an indicator in the spindle, run it down so you've got room to move up or down, and then move in x and y and read the indicator.
[21:59:23] <jmkasunich> if you don't have an indicator, use a felt point marker - adjust it so it just touches, then run it around and see if the line gets fatter (table hi) or disappears (table low)
[22:07:45] <tomp3> moving the part under the felt tip shows parallelism of surface to x and or y way, it would show the same result if the quill was 45degrees to the surface.
[23:08:42] <jmkasunich> tomp3: if you are milling a PCB, parallelism is what you care about (consistent depth of cut)
[23:09:12] <jmkasunich> having the cutter at an angle to the surface has little effect when the DOC is measured in single digit thousandths
[23:32:26] <tomp3> we must be speaking of different things, when my spindle isnt square to the table, a normal square bottomed end mill will dig on one side. If K`zan wants a machine that works well, squaring the spindle to the table motion is a good thing.
[23:34:17] <tomp3> yes parallelism is neccesary before squareness, and linearity before parallelism, i see i was too far into the geometry
[23:48:27] <K`zan> Comcast has deemed to come back up!
[23:48:52] <K`zan> First cutting pass went reasonably well but there are still problems:
[23:48:55] <K`zan> http://wrlabs.shacknet.nu/~vw/MyMachineShop/PipeDreamMill/PDM-FirstCut/
[23:57:42] <dan> hi anyone home?