#emc | Logs for 2010-04-21

Back
[00:00:44] <andypugh> I found my keys this evening, in the glass recycling crate in the back yard. I have no idea....
[00:01:01] <JT-Hardinge> was my fluke meter in there too?
[00:01:33] <archivist> and the log book for my bike?
[00:11:09] <JT-Hardinge> I think the log book for your bike is in my van...
[00:11:23] <morfic> andypugh: best place ever to find keys was inside the bass reflex tube of my old speakers, we would have never looked if our daughter would not have reached in there again while we looked for the keys
[00:12:11] <JT-Hardinge> * JT-Hardinge wanders inside to make green eggs and ham
[00:54:16] <Tonok2_> Tonok2_ is now known as Tonok2
[02:44:41] <morfic> "EMS moves the smoothest of all three, the cuts are consistent and the
[02:44:41] <morfic> code seems very robust. The backplot screen is great on Axis. The
[02:44:41] <morfic> other screens are pretty good, but I'm loving the simplicity of axis."
[02:45:02] <cradek> cool
[02:45:15] <morfic> interesting comment i think, found it while googling EMC2 backlash
[02:45:35] <morfic> realized i never asked a single question about backlash when we took it out of X on the Fanuc controller this morning
[02:46:03] <morfic> cradek: so your email said you are the ladder logic wizzard to call upon in times of need? :P
[02:46:12] <cradek> if you have a laser, you can do better and actually map the screw errors for emc to compensate
[02:46:38] <cradek> backlash comp is simple to configure but sure assumes a lot
[02:47:06] <morfic> cradek: converting a knee mill in a few days is promising, the tech who services our Johnford mills thinks 4 weeks down time with rewiring stuff
[02:47:37] <cradek> somewhere in between is where you'll always end up I bet
[02:47:45] <morfic> which we thought sounded high
[02:48:16] <morfic> we guessed 2 to tops 3 weeks on first retrofit, less on second
[02:48:49] <cradek> whether that's reasonable depends hugely on the machine, what schematics you have available, and how well you plan.
[02:51:44] <morfic> cradek: any docs on this laser mapping of screw errors? googling bring up a cnczone emc thread , but no info on how, just that it's simple
[02:52:04] <morfic> all i ever seen involved dial test indicators
[02:52:05] <cradek> you put the errors in a text file and emc reads it in
[02:52:24] <cradek> yeah you can measure however you think you can get good results :-)
[02:52:46] <morfic> cradek: i am wondering about the laser part of it, just intrigued by another method
[02:53:28] <cradek> oh there are systems where you set a target on the axis and move it, and the laser head tracks it and gives you the precise position of the target.
[02:54:16] <morfic> cradek: unfortunately taking out backlash this morning made the second part worse, and it being the last part, no time to find out if part moved, or whatever the root cause was for the cut in X+ being the one cutting too much, not the X-Y+ or X-Y- cuts
[02:55:47] <cradek> if you were discussing this earlier, I didn't see it
[02:56:45] <morfic> nah, just sharing a bit of my work day, aside, Fanuc backlash comp is not realy #emc stuff
[02:57:09] <cradek> ah I see
[02:57:29] <morfic> just glad EMC has it, since i had not asked about it before, google made me happy though ;)
[02:57:53] <cradek> yeah screw comp is a nice emc feature
[02:58:27] <cradek> what we don't have is periodic corrections (measure, curve fit, give to emc, it corrects that)
[02:58:33] <cradek> someday that might be nice.
[02:59:07] <cradek> relatively simple, but nobody has cared to do it
[03:04:01] <calcite> How does EMC handle backlash comp? Just add (+/-) distance to the axis move?
[03:04:25] <calcite> as opposed to a unidirectional approach
[03:04:26] <morfic> it would have to consider direction change of the ballscrew only
[03:04:45] <cradek> sort of. you have to add it in gracefully - not quite abruptly
[03:04:51] <cradek> but yeah that's the general idea
[03:05:20] <cradek> you're always (ALWAYS) better off fixing the machine though
[03:05:28] <calcite> still, milling is not an easy thing to do with backlass present, lathe work....fine
[03:05:52] <morfic> cradek: realistically expect a ballscrew to go a year longer than it should
[03:05:58] <cradek> software backlash comp, no matter how well it's implemented, doesn't work very well to remove the effects of a sloppy machine
[03:06:14] <morfic> * morfic is all psyched none of the lathes turn flat spots on the apex of balls right now
[03:07:05] <calcite> My manual mill has a little lever on the long feed table with a climb mill pictogram. Tighten up on that nut!
[03:07:08] <morfic> ^^ backlash comp works well to keep flats off balls
[03:07:34] <calcite> Who's?
[03:07:46] <calcite> ;-)
[03:08:03] <morfic> whose comp or whose balls, i now wonder
[03:09:15] <morfic> * morfic sees .cc files in /emc2-dev that's good, i unfortunately took a turn towards motion.c first, .cc is better for my brain, much better
[03:09:37] <cradek> all realtime parts of emc are pure c
[03:11:49] <morfic> i don't see myself touching realtime stuff
[03:15:00] <morfic> clock is cruel, screaming at me saying it's late, so thanks all, 'night
[03:44:10] <jimbo> I am trying to compile the latest download of 2.4-dev. when I run sudo apt-get build-dep emc2 I receive not found errors:
[03:44:12] <jimbo> checking for rtl... not found
[03:44:14] <jimbo> checking for mbuff... not found
[03:44:15] <jimbo> checking for rtl_time... not found
[03:44:17] <jimbo> checking for rtl_sched... not found
[03:44:18] <jimbo> checking for rtl_posixio... not found
[03:44:20] <jimbo> checking for rtl_fifo... not found
[03:44:21] <jimbo> What have i missed?
[04:11:25] <jimbo> night....
[04:34:35] <elmo40> 0.12.0 HeeksCAD is nice.
[04:34:42] <elmo40> a few new features
[04:49:03] <MrSunshine_> like what? :)
[04:49:24] <elmo40> umm...
[04:49:26] <elmo40> lol
[04:49:36] <elmo40> zig-zag roughing and finishing?
[04:50:20] <elmo40> https://sites.google.com/site/heekscad/news
[06:55:11] <fenn> thought this was cool, if anybody is trying to make a delta robot: http://www.societyofrobots.com/robotforum/index.php?topic=10906.0
[07:01:44] <SWPadnos_> SWPadnos_ is now known as SWPadnos
[07:04:00] <micges_work> fenn: cool
[09:14:34] <piasdom> g'mornin all
[09:55:48] <findux> hello all
[09:58:12] <findux> open source dwg viewer ?
[09:59:31] <awallin> you need it, you write it.
[10:05:42] <findux> I need reading dwg file . for my own software.
[10:06:28] <findux> so I need open source code dwg viewer lib.
[10:08:24] <findux> I use python but I can use .dll. Are there any dwg viewer lib.?for python or any language
[10:28:29] <MarkusBec_away> MarkusBec_away is now known as MarkusBec
[11:25:27] <fenn> findux: http://www.gnu.org/software/libredwg/
[11:26:05] <fenn> i don't know anything about it
[11:26:39] <fenn> i can't believe youtube doesn't support ogg theora
[11:34:34] <The_Ball> I received some cards from Mesa Electronics today and they included some star shaped orange plastic bits. Each "arm" on the stars looks like it is supposed to break away, but I don't know what these little arms are for. Anybody have a clue?
[11:44:36] <alex_joni> http://www.youtube.com/watch?v=AENJxqR0g48 <- wow
[11:55:29] <The_Ball> alex_joni, I was sure this would be some mad 9-axis machining or something... but still cool
[11:55:34] <elmo40> findux: can't you use qCAD for a dwg viewer? Or is it only dxf?
[11:59:21] <The_Ball> alex_joni, ok after watching the whole thing, WOW
[12:04:08] <alex_joni> the first part is ok-ish.. but the augmented stuff is really nice
[12:04:16] <alex_joni> not hard to do either
[12:05:06] <findux> elmo40 actually I need dwg library for use my own software. I developing a soft ware.but software not cad software. I need to read dwg file but I have some problem dwg file library source.
[12:05:26] <The_Ball> it's like having the laser on the circular saw just much better
[12:06:44] <frallzor> anyone around? :)
[12:12:46] <sealive> yes
[12:13:45] <frallzor> http://pagesperso-orange.fr/fabrun/project%201/indexproject1.html what is this type of model called in english?
[12:13:50] <frallzor> cant figure it out
[12:14:13] <frallzor> sheets of wood you assemble
[12:24:59] <ries> frallzor: Hey Mr #57!!
[12:25:14] <frallzor> yo :P
[12:25:19] <frallzor> finally :P
[12:25:59] <ries> good work.... so now you are going to make little cars in 3D?
[12:26:15] <frallzor> would be cool to make one and have on a shelf
[12:27:00] <frallzor> will be fun to see how my dust shoe performs today
[12:27:07] <frallzor> will be assembling it later =)
[12:28:00] <frallzor> simple design made for the Mechmate =)
[12:28:02] <ries> frallzor: I designed the shoe so it moves with the router... what was the reason you make it staic?
[12:28:41] <frallzor> simple, allows more movement atm, but i will mak a moving one later
[12:28:54] <frallzor> but for sheet work this is good
[12:29:03] <frallzor> since the fan blows air down
[12:29:18] <frallzor> if it lifts then some dust might escape around
[12:31:55] <ries> frallzor: ic.... I have a router, and I need to make sure that I move my air back up, else the router blows more air then the fac..
[12:34:38] <frallzor> i see it as a good thing
[12:34:51] <frallzor> if you have brushes or similar and then suction
[12:35:09] <frallzor> flow makes the dust never settler
[12:35:12] <frallzor> *settle
[12:35:18] <frallzor> and is easy to suck
[12:41:27] <elmo401> findux: I timed out, did you receive my message?
[12:42:55] <findux> qcad yes receive
[12:44:28] <ries> frallzor: I thought so to, for my fac it was just to much :) The dust blew all over the plce
[12:44:34] <elmo401> no, freecad :P
[12:47:13] <frallzor> when i did have some suction using old vac, it was allmost ok, the new one will make it work nicely i assume
[12:55:27] <ries> frallzor: good.. I must admit, my vac wasn't to powerfull... I like the idea of your design though, I am going to consider that aswell..
[12:57:31] <frallzor> but im just using what I got, the spindle is aircooled, so its blows alot of air =)
[13:11:05] <elmo401> frallzor: how did the item come out?
[13:12:49] <frallzor> http://pici.se/p/ppOKrFhVV/
[13:12:52] <frallzor> pretty ok
[13:16:17] <elmo401> a couple lines at the right.
[13:16:27] <elmo401> tool length move or something?
[13:19:03] <frallzor> the fact that I dont have proper fastening yet =)
[13:19:13] <frallzor> after some material was gone it started lifting
[13:19:31] <elmo401> vacuum problem?
[13:19:35] <frallzor> need to figure out a nice way to fix that
[13:19:49] <frallzor> no vacuum at all =)
[13:20:01] <elmo401> there is your solution ;)
[13:20:24] <frallzor> will be making some kind of T-slot solution
[13:21:36] <frallzor> not bad, made the machine in 5 months according to the log
[13:23:01] <elmo401> t-slots will work. vacuum is easier
[13:23:35] <frallzor> I disagree =P
[13:25:00] <elmo401> but your machine is for large flat parts
[13:25:06] <elmo401> vacuum is simple to setup.
[13:25:13] <elmo401> t-slots need bolts and such
[13:25:21] <elmo401> and you have to avoid clamps when machining
[13:27:17] <frallzor> well how to fix easy vacuum then?
[13:31:12] <elmo401> you have a vacuum cleaner? it will work, a little... but a compressor will be better.
[13:31:44] <elmo401> then the hose to the back. and a table with holes in it.
[13:31:48] <JT-Work> a vacuum pump is the way to go
[13:31:52] <JT-Work> we use piab
[13:32:02] <elmo401> split the hose to each hole. close off the ones that don't fit the material (no leaks)
[13:32:49] <frallzor> that seems like a messy work if you need to split for every single mount
[13:33:26] <JT-Work> just make channels and block off unused ones
[13:34:01] <frallzor> channels on the top that is? and block with rubber?
[13:34:20] <JT-Work> http://www.piab.com/en-gb/Products/Vacuum-pumpsgenerators/
[13:34:56] <JT-Work> yea or a bunch of holes and the bottom as a small box
[13:35:10] <frallzor> pics? :)
[13:37:29] <JT-Work> the smaller the size of the box the faster the vacuum will work
[13:38:25] <elmo401> http://www.klitgaard-design.dk/?p=314
[13:38:31] <elmo401> very simple design ;)
[13:38:43] <elmo401> but for plastic forming... same concept, though
[13:38:54] <elmo401> a 'pro' version: http://www.techno-isel.com/cnc_routers/technical_section/Vacuum_Hold_Down.htm
[13:39:33] <frallzor> one could mill those tables pretty faste
[13:39:35] <frallzor> *fast
[13:57:07] <frallzor> ah got a nice idea now
[13:57:22] <frallzor> some piping required :P
[13:57:34] <frallzor> how is mdf for vacuum?
[14:00:13] <sealive> first styrocut test with emc ->http://www.pictureupload.de/originals/pictures/210410155936_werbung_sim.png
[14:00:33] <sealive> generated by heekscad
[14:00:56] <sealive> i will try it on a VF2
[14:01:32] <JT-Work> frallzor: mdf should be good for that
[14:05:09] <frallzor> a few holes, milled zones in the mdf and some gaskets should do the trick
[14:06:05] <frallzor> the table is 2750x1630 aroundish, divide into maybe 8 zones of 2750x200mm
[14:06:23] <frallzor> and just limit to the holes for smaller areas
[14:07:46] <frallzor> would a back valve be of some use?
[14:07:54] <frallzor> or what ever its called in english?
[14:08:24] <frallzor> so suction kan be kept if the vacuum is lost in the motor
[14:09:13] <JT-Work> it's called a check valve and it would not work unless you had a perfect seal
[14:09:33] <frallzor> well I assume a gasket will make sure that happens
[14:10:56] <Dave911> The_Ball: >> I received some cards from Mesa Electronics today and they included some star shaped orange plastic bits.
[14:10:57] <Dave911> I believe those are "keys" used to key the plug on connectors to a certain socket. I haven't installed them yet and may not use them..
[14:11:38] <cradek> I don't recall seeing anything like that
[14:11:59] <JT-Work> Dave911: yes they are keys
[14:12:01] <frallzor> JT-Work what do you use as gaskets?
[14:12:36] <JT-Work> our vacuum applications are not for wood cutting
[14:12:38] <frallzor> I assume it must be quite flexible to allow it to sink so the material lies flat on the table? yet not too soft so it can be vacuumed
[14:13:13] <Dave911> JT .... so do you insert those in the socket slot and then remove the little tab on the plug to create a key situation?
[14:16:03] <JT-Work> yes
[14:16:19] <JT-Work> I had a couple fall out after...
[14:25:27] <The_Ball> Dave911, aha! now it all makes sense
[14:26:30] <The_Ball> cradek, I didn't receive these "keys" for my older Mesa card, but the older Mesa card has a black style connector, these new ones are green
[14:26:54] <The_Ball> cradek, screws are on the top instead of on the sides
[14:27:45] <Dave911> Thanks JT.... I think I will skip the keys and take my chances .. yep I know... I'm living on the edge ;-)
[14:28:10] <cradek> oh ok, replacing those black connectors with something else is good :-)
[14:28:18] <Dave911> The ones I received about 6 weeks ago also have green connectors..
[14:29:11] <Dave911> The green connectors work fine..
[14:30:01] <The_Ball> I put in a couple of these "keys" and they fit perfectly, but they don't stop you from inserting the terminal block at all
[14:34:29] <atmega> I have some of those, also green.
[14:34:30] <SWPadnos> they only work if you have the "blocks" in the terminal strip
[14:34:40] <atmega> (not mesa though)
[14:38:34] <JT-Work> Dave I used a fine tip marker to mark mine as well
[14:45:17] <The_Ball> SWPadnos, I have the "fins" that will block against the "keys", and it does make a difference, with no key the terminal block will drop in by its own weight, with one key I need to apply 50-100 grams (guestimate) of force to enter the terminal. So I guess it works
[14:48:05] <terrylm> Hi all
[14:49:00] <terrylm> Yesterdays advice to set P,I, and D to zero and FF1 to 1 worked great!
[14:50:29] <terrylm> There was still an accumulating error over long rapids, but that was corrected by slightly reducing the max velocity.
[14:52:23] <pcw_home> A little P and I should fix that error
[14:53:16] <pcw_home> (you need a little because the stepgens xtal derived rate is not an exact match to the PCs clock)
[15:01:18] <terrylm> Now the error is a small amount, about 0.0009, right from the start of a move.
[15:01:51] <terrylm> Falls to zero or so after the move stops.
[15:02:34] <pcw_home> Without at least some P and I you are running open loop so you will get accumulated errors in velocity mode
[15:02:36] <pcw_home> FF1 alone works well because the stepgens generated velocity is so close to commanded but you still need feedback
[15:19:32] <terrylm> Got distracted, had a visitor. back now.
[15:20:26] <terrylm> Tried some P & I, it just seemed to make it jittery.
[15:21:33] <terrylm> About P = 0.75 it starts to jitter, adding I did not seem to help.
[15:21:53] <SWPadnos> what is your encoder resolution?
[15:22:07] <terrylm> 4000 count per turn
[15:22:22] <SWPadnos> ok, so it matches the step resolution (?)
[15:22:29] <terrylm> 8 turns per inch = 32000 counts per inch.
[15:22:36] <SWPadnos> oh, right
[15:22:52] <SWPadnos> turn ~= inch :)
[15:22:55] <SWPadnos> err, !=
[15:23:16] <terrylm> turn = .125 inch.
[15:23:23] <SWPadnos> yep
[15:23:43] <pcw_home> You only need a little but if you have none, (only FF1) the position will creep away...
[15:23:46] <SWPadnos> you need deadband of around one step, or 0.00025
[15:25:48] <terrylm> One step would be 0.00003125 in theory.
[15:25:55] <SWPadnos> no, that's one encoder count
[15:26:00] <terrylm> oh
[15:26:03] <terrylm> right
[15:26:58] <terrylm> OK, I was using 0.0005, so that should have been OK?
[15:27:06] <SWPadnos> yep, should be
[15:28:07] <terrylm> Now that I have the 5i23 card I can actually step the signal generator faster then the motors can take. So...
[15:29:19] <terrylm> I plan to redo the signal generator firmware to only make half as many tiny steps per commanded step.
[15:29:41] <terrylm> Thus changing it to 1000 steps per turn.
[15:30:35] <pcw_home> If it jitters at P-=.75 , use 1/2 or 1/4 that you still need feedback...
[15:30:39] <terrylm> This should maybe reduce the deadband to half?
[15:30:41] <SWPadnos> make the signal generator do 1:1, there's no need to have any multiplier in there
[15:31:28] <terrylm> I'm not sure if the 5i23 card can step that fast?
[15:31:34] <SWPadnos> megahertz
[15:31:36] <pcw_home> (in other words you are not actually using your encoder unless you have some P or I)
[15:31:57] <terrylm> explain?
[15:32:20] <SWPadnos> the 5i23 can do millions of steps per second
[15:32:27] <cradek> the encoder will still cause a following error if it stalls - I think that's still the only possible advantage of this setup (and you don't need velocity mode for that)
[15:32:31] <terrylm> OK
[15:32:35] <SWPadnos> as for peter's statement, FF doesn't use feedback, it's command only
[15:32:56] <SWPadnos> P,I, and D are the terms that incorporate feedback into the equation
[15:33:10] <SWPadnos> so you're effectively open loop when you only have FF0, FF1, and FF2
[15:33:23] <terrylm> OK
[15:33:40] <terrylm> So open loop with crash detection?
[15:33:52] <SWPadnos> more or less
[15:33:58] <SWPadnos> and stall detection added for free!
[15:34:47] <pcw_home> closing the loop will also work better if you decrease your ustep size
[15:35:53] <terrylm> OK, I'll redo the signal generators firmware for 1:1 micro steps, that will make it 25000 steps per turn.
[15:36:09] <pcw_home> I suspect your encoder resolution is better than your step size this will lead to jitter
[15:36:15] <SWPadnos> huh. I thought it was doing 8 microsteps per step ...
[15:36:37] <terrylm> Oh, no, 50.
[15:36:53] <SWPadnos> oh. that's a lot :)
[15:37:02] <terrylm> Ya
[15:37:20] <SWPadnos> so that'll be 200ksteps/inch. how fast does this thing move?
[15:37:36] <terrylm> I was thinking of going to 25, for 1000 steps per turn.
[15:37:45] <SWPadnos> you may have to look at the inputs (if they're optoisolated) - optos may not keep up
[15:37:49] <terrylm> not fast
[15:37:59] <terrylm> 0.55 in. / sec.
[15:38:04] <SWPadnos> the Mesa card can step pretty fast, it's a question of the optos
[15:38:22] <SWPadnos> ok, 110 kHz probably shouldn't be an issue
[15:38:25] <terrylm> No optos, direct.
[15:38:33] <SWPadnos> oh
[15:38:43] <SWPadnos> then 110 lHz is really fine :)
[15:38:47] <SWPadnos> kHz
[15:38:53] <terrylm> optos on most other stuff though.
[15:39:28] <terrylm> OK
[15:40:11] <terrylm> But I'm not sure if the dsPIC30 can read that fast, 16MHz internal clock.
[15:40:48] <SWPadnos> is the step input on an interrupt line?
[15:40:54] <terrylm> no
[15:41:10] <terrylm> it is polled and debounced.
[15:41:11] <SWPadnos> remember, you can get rid of all the timing stuff in there - there's no need to count the time between pulses or anything
[15:41:34] <SWPadnos> just increment/decrement the sine wave index whenever a step is detected
[15:41:50] <terrylm> no, it is slow enough that none is needed.
[15:42:06] <terrylm> yes
[15:42:28] <Jymmm> maybe
[15:42:31] <SWPadnos> even 16 cycles is pretty close to enough to poll and update the DAC outputs
[15:42:49] <SWPadnos> (which would give you 1 MHz step inputs)
[15:42:55] <SWPadnos> 160 cycles is plenty
[15:43:34] <terrylm> I don't know, I was kind of disappointed in the dsPIC30 as far as it seems very slow.
[15:44:10] <SWPadnos> hmmm. do the dsPIC's have the clock divided by 4 like the regular PIC?
[15:44:27] <frallzor> * frallzor gotz screws
[15:45:08] <terrylm> I has a choice of 3 clock dividers, I have it on the fasted, had to add a heat sink.
[15:45:32] <SWPadnos> I'm talking about the machine cycle being different from the clock cycle
[15:45:32] <terrylm> multipliers actually.
[15:45:38] <pcw_home> DSPics have a PLL the ones I'm used to have 30 or 40 MHz CPU clock capability (1 clock.inst)
[15:45:45] <SWPadnos> ok
[15:46:19] <SWPadnos> * SWPadnos hasn't used a PIC since the 16F84
[15:46:39] <terrylm> Maybe it could have a faster XTAL, but I ordered it as a demo board, so ...
[15:47:16] <Jymmm> frallzor: You finally called 1-900-Happy-Hookers ?
[15:47:22] <terrylm> All I had to build was the DAC board that plugs right onto it.
[15:47:46] <frallzor> Jymmm 1-900-Nasty-Cows
[15:47:52] <frallzor> of course
[15:47:52] <Jymmm> ROTF
[15:48:15] <Jymmm> frallzor: oh man, you made my day =)
[15:48:19] <Jymmm> lol
[15:48:32] <frallzor> you're welcome
[15:52:41] <terrylm> Well Thanks all. I'm going to call it a day and get ready for work. (night shit^Hft)
[16:06:53] <cradek> jon e's spindle encoder is clever
[16:08:40] <JT-Work> it is neat
[16:10:02] <cradek> having index for tapping is neat because all your threads end up oriented the same way - but it's not necessary if you don't care about that - I just wired one of the AB phases to Z
[16:10:27] <JT-Work> we just got a RFQ from one of our customers and their spec called out our jet orientation device so we are going to get part of it for sure
[16:10:46] <cradek> I guess I can't "peck tap" either, but who cares, I use proper taps instead
[16:12:02] <JT-Work> have you used a thread mill yet?
[16:12:16] <cradek> no, they're too expensive for me
[16:15:26] <JT-Work> I have one but have not used yet LOL
[16:29:09] <Jymmm> "Borowed" ? http://sfbay.craigslist.org/sby/wan/1702922099.html
[16:29:29] <Jymmm> err "Borrowed" ?
[16:30:04] <JT-Work> wonder if he can spell lock now
[16:30:19] <cradek> hay you if your reading this add
[16:30:26] <cradek> grngnthrrrf!
[16:30:29] <Jymmm> He can spell Lock Out
[16:30:53] <JT-Work> that's how we spell it down here LOL
[16:31:36] <Jymmm> Either he didn't lock it up, or it got towed.
[16:32:26] <JT-Work> been waiting for my replacement tank for the way lube for 2 weeks :/
[16:33:00] <JT-Work> cradek: what was that coolant you used for the hardinge?
[16:33:43] <cradek> "soyeasy nucut something"
[16:34:01] <Jymmm> soy?! yuck!
[16:34:03] <cradek> the "something" is different weights or something - if you call they'll help you match it to your work
[16:34:14] <cradek> Jymmm: smells like french fries
[16:34:21] <JT-Work> ok, I got it now
[16:34:56] <Jymmm> cradek: LOL, oh that would kill me. You're trying to finish a job, hungry, and the place smells of french fries!!!
[16:35:51] <cradek> JT-Work: the manufacturer: http://www.elmusa.com/
[16:36:00] <cradek> I ordered mine from them directly - not sure if they still do that.
[16:36:32] <JT-Work> thanks, I'm an oem equipment manufacturer so maybe they will sell to me
[16:39:23] <archivist> a bit crazy http://www.crabfu.com/steamtoys/rc_steam_turbine_tank/
[16:48:07] <Jymmm> http://v5.tinypic.com/player.swf?file=apa9ti
[16:51:38] <SWPadnos> now that is funny
[16:53:58] <Jymmm> lol, how so? The hunter/hunted part?
[16:55:46] <SWPadnos> no, more that there are far fewer ducks as pets than almost any other animal ;)
[16:55:46] <tom3p> in 'apt-get install build-dep emc2' is not 2 files? 'build-dep' is a switch ?
[16:56:00] <SWPadnos> build-dep and install are two commands
[16:56:08] <SWPadnos> I think you can only use one or the other at a time
[16:56:19] <tom3p> as a kid my duck was 'herkimer'
[16:56:21] <Jymmm> SWPadnos: Ah. I guess ppl dont realize how smart birds can be.
[16:56:34] <tom3p> the command was from the wiki page
[16:56:36] <SWPadnos> the command line you typed should have tried to install a package called "build-dep" and one called "emc2"
[16:56:38] <bill2or3> do "apt-get build-dep emc2" and "apt-get install emc2" separately
[16:56:38] <SWPadnos> huh
[16:57:52] <tom3p> works 'apt-get install build-dep emc2' does not work 'apt-get install build-dep'
[16:58:21] <SWPadnos> could you rearrange that in the form of a sentence? :)
[16:59:18] <tom3p> This phrase works 'apt-get install build-dep emc2' . This phrase does not work 'apt-get install build-dep'. ( no idea of colon placement for correct grammar :)
[16:59:27] <SWPadnos> heh
[16:59:33] <SWPadnos> that is a strange result though
[16:59:45] <SWPadnos> "apt-get build-dep emc2" should work
[16:59:52] <SWPadnos> as should "apt-get install emc2"
[17:00:04] <SWPadnos> oh, well duh
[17:00:24] <SWPadnos> "apt-get install build-dep" tries to install a package called "build-dep"
[17:00:32] <SWPadnos> which probably doesn't exist
[17:01:08] <SWPadnos> tom3p, were you looking at the "Installing EMC2" wiki page?
[17:03:40] <tom3p> stupid computer, do what i mean (R J DALEY )
[17:03:45] <SWPadnos> heh
[17:04:05] <SWPadnos> somebody commingled "build-dep" and "build-essential", I think :)
[17:04:25] <tom3p> yep http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Installing_EMC2 ( client keeps dropping out, sorry wlan0down... wlan0up... rinse lather repeat )
[17:04:52] <SWPadnos> I'd suggest lathering before the rinse, but that's just me :)
[17:04:52] <tom3p> oh well, it got something
[17:06:26] <Jymmm> then repeat.
[17:09:34] <tom3p> yesterday i was looking for how to find dependencies, found that you can get a dot (vizgraph) style plot of relations from dpkg using the 'dotty' option
[17:10:19] <Jymmm> tom3p: OR, you could just connect the machine to the net and be done with it.
[17:12:16] <tom3p> yah, can you help me carry the eight towers into the library ;)
[17:12:56] <Jymmm> tom3p: No, but I can give you the color code so you can run a cat5 cable to them =)
[17:15:09] <tom3p> isnt there some offcolor mnemonic device to remember that color order?
[17:15:35] <Jymmm> nfc
[17:17:57] <grommit> I am trying to configure EMC2 do control my spindle motor and am having problems understanding what I need in the HAL file. I am using a Mesa 7i43 card driving a 7i47 daughter card. This in turn is plugged into a Homann DC-06 board that turns a step/dir command into a variying DC voltage (0-10v) that is connected to a motor control board.
[17:18:50] <grommit> I started with a base config that was generated by pncconf (an alpha utility in dev EMC).
[17:19:49] <grommit> I pasted the spindle portion of the .hal file to http://pastebin.com/JxXE7anq
[17:19:50] <cradek> possibly you want to use mesa's stepgen in velocity mode to generate your pwm signal
[17:20:06] <grommit> Yes, I do want stepgen in velocity mode.
[17:20:21] <cradek> ok, cool. what is your specific question then?
[17:20:47] <grommit> well, I have a scope on the output of my mesa card and am not getting any pulses
[17:21:39] <SWPadnos> you may need to set the stepgen pins to output mode (?)
[17:21:39] <cradek> ok, that narrows it down. while you are expecting but not getting output, could you do a show pin hm2_7i43.0.stepgen.03 and pastebin the result?
[17:22:04] <SWPadnos> grommit, could you post the whole hal file on pastebin>
[17:22:06] <SWPadnos> ?
[17:22:20] <grommit> yes, on both counts. Hold on a min....
[17:25:51] <Jymmm> LOL "...and the police reloaded it for her" love it!!! http://www.cnn.com/video/#/video/crime/2010/04/21/dnt.elderly.woman.vs.intruder.kcci?hpt=T2
[17:28:17] <SWPadnos> that's about as funny as the duck :)
[17:28:21] <grommit> Ok, entire config is here: http://pastebin.com/ByvhgUc4
[17:28:37] <grommit> will try show pin now....
[17:29:58] <SWPadnos> ok, I don't see anything that sets the stepgen pins to output mode, but I confess that I don't know if it's necessary (I'd expect the driver to default to output mode for pins that are assigned to output functions like a stepgen)
[17:31:54] <grommit> how do I do a show pin with AXIS running?
[17:34:13] <sealive> grommit: my enlish not good enoph to anser this quest
[17:34:38] <micges> grommit: open console and type 'halcmd show pin show pin hm2_7i43.0.stepgen.03
[17:35:03] <micges> err sorry, open console and type 'halcmd show pin hm2_7i43.0.stepgen.03'
[17:36:42] <grommit> ok, show pin is at: http://pastebin.com/aVTJhswe
[17:37:50] <SWPadnos> how about the results of halcmd show pin | grep "*is_output*"
[17:37:51] <cradek> what hardware pins are you scoping?
[17:37:54] <JT-Work> grommit: if your running Axis you can select Show Hal Configuration from the machine window to view pins
[17:38:02] <cradek> what emc2 version and firmware package version are you running?
[17:38:23] <SWPadnos> and also important, what does dmesg say about which pins are assigned to what functions?
[17:39:00] <cradek> I see that for at least some firmwares, stepgen 3's pinout in this firmware was bogus
[17:39:04] <grommit> halcmd show pin | grep "*is_output*" does nothing, just returns the unix prompt
[17:39:14] <SWPadnos> err
[17:39:21] <SWPadnos> right, no stars needed
[17:39:32] <SWPadnos> haldmd show all | grep is_output
[17:40:00] <SWPadnos> (they're params, not pins also - oops :) )
[17:40:37] <cradek> non-gpio pins do not have an is_output parameter
[17:40:52] <SWPadnos> ok
[17:40:57] <SWPadnos> that solves that problem :)
[17:42:12] <grommit> ouput is here: http://pastebin.com/dmKCb1RW
[17:43:02] <cradek> grommit: lots more questions have been asked - we'll quit bombarding you with more while you answer them :-)
[17:43:45] <grommit> Lets see... I am running the latest EMC2 (2.3.5).
[17:44:13] <grommit> Firmware for 7i43 is the lateset from Peter Wallace for my 7i47 card
[17:44:30] <grommit> The steppers on my x,y,and z seem to be working
[17:45:01] <grommit> I have commented out the encoder stuff for the time being (but will work on that next).
[17:45:49] <grommit> cradek: what firmware was stepgen 3 bogus and where did you see that?
[17:46:20] <grommit> Have I caught up on questions?
[17:46:40] <cradek> except for what physical pins are you scoping
[17:46:56] <grommit> How do I determine that?
[17:47:08] <SWPadnos> you tell us where you hooked up the oscilloscope
[17:48:00] <grommit> oh, duh. I am currently on the output of the 7i47 card for stepgen 03. hang on and i will tell you which physical pin
[17:48:12] <cradek> I can't find the PIN file that matches your firmware - it is probably on your system somewhere. would you pastebin it too?
[17:49:03] <grommit> yep, hang on....
[17:49:46] <cradek> well I bet SWPadnos is right and we should check the output in dmesg too
[17:52:12] <grommit> PIN file is: http://pastebin.com/Pw3kVUmH
[17:55:52] <grommit> My step signal is on 7i47 card header P2 Pin 19, which is logical I/O 18
[17:56:14] <SWPadnos> ok, I think that's an error :)
[17:56:38] <SWPadnos> I/O 18 is pin 39
[17:56:42] <cradek> yeah seems like you should be on 39
[17:56:51] <SWPadnos> err, 37
[17:56:58] <SWPadnos> 37 for step, 39 for dir
[17:57:04] <cradek> yeah that
[17:57:54] <grommit> no, that is 37,39 of physical pins on 7i43 card (header P4).
[17:58:11] <grommit> onto that header, I have my 7i47 plugged in
[17:58:19] <SWPadnos> yes
[17:58:37] <SWPadnos> you're using a physical oscilloscope, aren't you?
[17:58:48] <grommit> hee hee
[17:58:50] <grommit> yes
[17:58:53] <SWPadnos> ok :)
[17:58:57] <cradek> I'm so confused
[17:59:09] <SWPadnos> look at pins 37 and 39 on the P4 header on the 7i43 first
[17:59:19] <grommit> I was confused as hell. PWC gave me the mapping and it took me hours to get it straight
[17:59:37] <SWPadnos> if you see step pulses there, *then* look at the pins where you expect the outputs from the 7i47
[18:00:02] <grommit> It is very difficult to get a scope on there because it is a ribbon cable that ties the two together.
[18:00:44] <SWPadnos> unplug the ribbon cable
[18:01:30] <SWPadnos> just to be sure, you're using the 7i47 "12 channel motion oriented RS-422 interface" card, not the 7i37 "Isolated I/O card"?
[18:12:41] <ChanServ> [#emc] "This is the #emc channel - talk related to the Enhanced Machine Controller and general machining. Website: http://www.linuxcnc.org/, wiki at http://wiki.linuxcnc.org/"