#emc | Logs for 2008-08-02

[00:00:11] <jmkasunich> you are saying that the entities as output by the cad _don't_ match?
[00:00:29] <jmkasunich> I mean, the cad is outputing 6 place numbers that don't match in the 3rd digit?
[00:01:20] <SkinnYPup> Yes basically so, this is the free version in synaptic , dunno if the "pro" retail version would be better. May be crippled intentionally?
[00:01:31] <jmkasunich> I can't believe that
[00:01:40] <SkinnYPup> http://www.ribbonsoft.com/qcad.html
[00:02:40] <jmkasunich> if you do "trim to intersection" (or the equivalent) and the resulting endpoints "as output by the cad" aren't the same. the cad is _wrong_
[00:03:21] <jmkasunich> I've used qcad for a total of about 5 minutes, so unfortunately I can't help much beyond that
[00:04:00] <jmkasunich> I use easycad - costs modest money, but it is very nice
[00:04:07] <SkinnYPup> Yeah it makes small errors that really add up when you combine the rotate copy function
[00:04:23] <SkinnYPup> to its trimmed entities
[00:04:25] <jmkasunich> oh, you are trimming first, then rotating
[00:04:29] <jmkasunich> hmm
[00:05:00] <jmkasunich> how are you translating from DXF to g-code anyway?
[00:05:16] <SkinnYPup> Some is trim rotate
[00:05:54] <jmkasunich> how are you translating from DXF to g-code?
[00:05:58] <SkinnYPup> gcnccam conversion to gcode, however it contains the same small errors that can be traced back to the original .dxf
[00:06:15] <jmkasunich> is gnccam open source?
[00:06:28] <SkinnYPup> if you go back and analyze the entities center and endpoints its there in qcad
[00:06:48] <SkinnYPup> yeah opensource http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?GCncCam
[00:07:07] <jmkasunich> I wonder if it could be hacked to fix the problems
[00:09:06] <jmkasunich> gotta make more chips.... (gawd, cast iron is so nice - cuts like buttah!)
[00:09:19] <SkinnYPup> Now I can make rectangles with trims or radius to their corners that work fine, but throwing out a few construction lines to make a square tooth "gear" and radius the root and crest , then rotate , copy there will be problems
[00:09:55] <SkinnYPup> Enjoy the chips !
[00:16:29] <fenn> SkinnYPup: have you tried changing the precision values under edit->current drawing preferences
[00:20:10] <SkinnYPup> A few months ago when I was first having this prob with qcad , I cranked those precision values up to 6 decimal places. Then constructed a new"part" to have the same locating errors where it places arc centers, begining and end points , if you went back to the entity properties they would reflect this.
[00:22:00] <SkinnYPup> However it won't "zoom" deep enough to show on the screen that the parts were disconnected by .0006 for my particular problem. I used mastercam X demo to verify there was an error in what it was trimming
[00:24:29] <SkinnYPup> some small "teardrop" type features on a round disc would work out with numbers that emc wouldn't choke on , but after the third rotation the features entities began to shift in accumulating error.
[00:37:12] <Roguish> got my vertical into production: http://www.youtube.com/watch?v=KT_cAiyks5U
[00:38:18] <Roguish> more later next week.
[00:49:38] <SkinnYPup> This Qcad user sounds like he was having the same problem http://tech.groups.yahoo.com/group/qcad-user/message/1795
[01:29:37] <LawrenceG> Canada is famous again..... dont take the greyhound bus.....
[01:30:30] <LawrenceG> http://www.cbc.ca/canada/saskatchewan/story/2008/07/31/greyhound-transcanada.html?ref=rss
[01:36:43] <skunkworks> That vertical lathe is awsome
[01:39:27] <toastydeath> hahahaha that IS awesome
[01:39:37] <SkinnYPup> That this cool !
[01:39:50] <toastydeath> that's a very long endmill
[01:40:00] <SkinnYPup> that thing yes ... can't even type after that
[01:42:20] <SkullWorks_PGAB> OK Time for my stupid question of the day (part 1?)
[01:46:44] <SkullWorks_PGAB> 2 identical 12-0-12 CT transformers , 1st gets wired with a bridge rectifier, 2nd is wired with 2 diodes using the center tap. Can the outputs be connected in series before the the cap (liner power)?
[02:10:32] <rayh> SkullWorks_PGAB, Why would one want to do this. It does create different voltage between the two?
[02:12:08] <SkullWorks_PGAB> summing the voltage
[02:12:37] <rayh> Oh. You want to connect the negitive of one to the positive of the other?
[02:13:00] <SkullWorks_PGAB> yes
[02:13:51] <rayh> Why not connect primaries and secondaries so you get the voltage you want before the rectifiers?
[02:14:19] <SkullWorks_PGAB> 2x 24V in series gives about 68VDC after the cap - thats too much
[02:15:19] <SkullWorks_PGAB> true if there were suitable bucking trans that could let me hit the target Voltage without loosing Current capacity
[02:16:41] <SkullWorks_PGAB> other option is get a torrid and start unwinding... :(
[02:16:42] <rayh> So you want one of the transformers to produce 34 volts and the other 16?
[02:17:04] <SkullWorks_PGAB> about
[02:17:30] <rayh> What is the peak voltage of the device you're feeding?
[02:17:53] <SkullWorks_PGAB> target is 48VDC @ 10A - I was going to slip a diode inline for a slight drop.
[02:20:12] <rayh> Well one of the transformers will be working harder than the other. But...
[02:21:53] <SkullWorks_PGAB> greek to me - was told if I am hooking up in series the trannies had to be identical for load balance.
[02:22:12] <SkullWorks_PGAB> load balance may not be right term
[02:22:46] <rayh> Load balance only counts in parallel, I think.
[02:23:17] <SkullWorks_PGAB> anyway I thought that maybe setting one up old style using the center tap and 2 diodes would work
[02:23:33] <SkullWorks_PGAB> vrs a 4 diode bridge rectifier
[02:25:42] <SkullWorks_PGAB> skipping the center tap & using the bridge I get 34VDC at 10A - the other way I get 17VDC @ 10A
[02:26:44] <SkullWorks_PGAB> not sure how that works - kinda half wave rect?
[02:27:49] <rayh> You are rapidly reaching past the extent of my knowledge.
[02:28:06] <rayh> But the half wave on each half of the transformer seems right.
[02:28:15] <SkullWorks_PGAB> I'm out of my own depth at the moment
[02:30:36] <rayh> Just don't ground anything in the middle of it.
[02:32:50] <rayh> if anything including the driver is grounded at one end or the other.
[02:33:14] <jmkasunich> SkullWorks_PGAB: you can do what you are describing
[02:33:47] <jmkasunich> or you can save a couple of diodes, and just connect one half of the one transformer's winding in series with all of the other one, then rectify the result
[02:34:14] <jmkasunich> either way, one of the transformers will be at half its VA rating when the other one is fully loaded
[02:34:30] <SkullWorks_PGAB> ah - was not sure if I could do that
[02:35:05] <jmkasunich> paralleling is where you have to be carefull
[02:35:24] <jmkasunich> if the transformers aren't perfectly matched and you parallel them, you can get circulating currents
[02:35:42] <jmkasunich> if the mismatch is bad, you can overload the transformers before you even draw any load current
[02:35:50] <jmkasunich> but in series, the currents are forced to be the same
[02:36:26] <SkullWorks_PGAB> so that would cause lots of inductive heating without any applied load?
[02:36:49] <jmkasunich> what would?
[02:36:52] <jmkasunich> parallel, yes
[02:36:59] <SkullWorks_PGAB> got it
[02:37:49] <jmkasunich> in parallel, you can have one transformer (the one with higher voltage) delivering 10A, of which 9A is backfeeding the other transformer (since it has lower voltage) and only 1A is going to the load
[02:38:05] <jmkasunich> in series, if the load is drawing 1A, then both transformers must each also be carrying 1A, no more
[02:38:49] <SkullWorks_PGAB> but I should be safe getting 2 units same mfg and p/n.
[02:38:58] <jmkasunich> sure
[02:39:05] <jmkasunich> "getting" as in buying?
[02:39:10] <jmkasunich> or do you already have two?
[02:39:10] <SkullWorks_PGAB> yes
[02:39:18] <jmkasunich> if you are buying, you don't want to do that
[02:39:25] <jmkasunich> you will be wasting half of one transformer
[02:39:56] <jmkasunich> either get one transformer of the proper voltage, or get two with the same _current_ rating, and voltage ratings that add up to whatever you need
[02:40:00] <SkullWorks_PGAB> bought - 2 was to be for 2 diff projects but I decide one would require too much space
[02:40:36] <jmkasunich> heh, I can't tell what you are saying - do you have the transformers already or not?
[02:40:47] <SkullWorks_PGAB> have the allready
[02:41:07] <jmkasunich> lol - I thought that is what I asked you a few lines ago
[02:41:19] <jmkasunich> if you got 'em, use em
[02:41:27] <rayh> Do you really need the 48 volts or would a single transformer be sufficient?
[02:42:28] <SkullWorks_PGAB> even buying new - some units are less than half price because of the volume of sales over the less needed odd voltage units
[02:47:45] <jmkasunich> sure
[02:47:53] <jmkasunich> but suppose you need 24+12
[02:48:13] <SkullWorks_PGAB> yeah
[02:48:33] <jmkasunich> you can get 2 500VA 24s, use one center tapped to make 12, and put it in series with the other one for a total of 36
[02:48:51] <jmkasunich> you can draw a maximum of 750VA from that combo, but you bought and paid for 1000VA
[02:49:27] <jmkasunich> if you get a 500VA 24 and a 250VA 12 (or 250VA center tapped 24), you can still get 750VA total, and thats all you paid for
[02:49:55] <SkullWorks_PGAB> thats the plan - 2x $13 24v units vrs a single torrid @ $49
[02:51:00] <SkullWorks_PGAB> more cabinet space, less cash
[02:51:17] <jmkasunich> yeah - toroids usually aren't the cheapest, but they sure are small for the same power
[02:52:34] <SkullWorks_PGAB> and this project is for a guy who is unemployed - medical issues - will need more surgeries on his foot and will have to stay off it for about 9 months
[02:53:34] <SkullWorks_PGAB> I'm donating what spares I have that will work for his unit
[02:54:49] <jmkasunich> steppers?
[02:55:18] <jmkasunich> I mean, "is it a stepper machine", not "do you have the steppers already"
[02:55:50] <SkullWorks_PGAB> yeah - He has a CNC ready unit that needs Nema 34's
[02:55:56] <jmkasunich> you are aiming for 48V DC at what current?
[02:56:14] <SkullWorks_PGAB> 10A
[02:56:56] <SkullWorks_PGAB> maybe a bit less
[03:02:25] <jmkasunich> hmm, dog is whining, better take him for a walk
[03:05:40] <SkullWorks_PGAB> Thanks John and Ray - I'm off for an extended coffee break.
[07:11:12] <micges> hi all
[10:05:40] <alex_joni> hi all
[10:13:44] <Vq^> hello mr Joni
[14:07:18] <pmbdk> yet another hal question...
[14:09:11] <pmbdk> man motion is nice for documentation of pins the motion module presents to the hal-"user"
[14:10:58] <pmbdk> But some (ok at least one :-)) IN field is not described fully... The "axis.N.motor-pos-fb IN float" is described as "The actual position for this joint." but not how it is used in the code.
[14:11:51] <pmbdk> The same goes for axis.N.neg-lim-sw-in IN bit and axis.N.pos-lim-sw-in IN bit
[14:12:33] <pmbdk> Is this described somewhere, or should I simply look in the code?
[14:15:35] <jepler> pmbdk: motor-pos-fb is used for multiple purposes. here are some that come to mind: kinematics, determining following error, for the DRO when in "actual position" mode, for the result of G38.x probing moves, and to set the commanded position when going into machine on mode
[14:16:01] <jepler> pmbdk: lim-sw-in is used to trigger a fault condition when a limit switch is closed
[14:17:54] <jepler> (actually in machine off mode the commanded position tracks the feedback position at all times, and then that 'tracking' is turned off when you go into machine-on mode)
[14:18:24] <jepler> pmbdk: you might try to catch jmkasunich, he prepared a nice drawing showing the uses of commanded and feedback positions inside the motion controlller earlier this summer.
[14:19:51] <jepler> bbl
[14:20:49] <pmbdk> jepler: Thanks... I'm trying to find the use of the var in the code right now...
[15:14:39] <dave_1> awful quiet!
[15:14:54] <archivist_ub> shh
[15:15:03] <BigJohnT> busy hacking up the documents :)
[15:15:24] <archivist_ub> ah fix the arctan crap
[15:15:59] <dave_1> years ago .. when sim first came out I installed it on a FC5 system. Now I can't seem to remember how to start it ..
[15:16:27] <BigJohnT> where at archivist_ub ?
[15:17:00] <archivist_ub> gcode docs theres a table with three arctans
[15:17:41] <BigJohnT> * BigJohnT looking
[15:18:09] <archivist_ub> chapter13
[15:18:32] <archivist_ub> ATAN
[15:18:34] <BigJohnT> tool file and compensation?
[15:18:42] <archivist_ub> table 13.3
[15:19:08] <archivist_ub> language overview user doc
[15:20:07] <BigJohnT> what is the title of the table? The manuals have changed a lot since the last version
[15:20:28] <BigJohnT> functions?
[15:20:33] <archivist_ub> Table 13.3 Functions
[15:20:48] <BigJohnT> it's 6.3 now but I'm there
[15:21:16] <archivist_ub> it needs an explanation that you use the top one for all three
[15:22:42] <BigJohnT> can you elaborate a bit please?
[15:23:21] <archivist_ub> I tried using the other syntax but failed , it just gets error messages
[15:24:02] <jepler> yay -- now I have working X and Y home switches
[15:24:20] <jepler> archivist_ub: it's an error in the documentation -- there is not a one-arg ATAN function in gcode, only a two-arg one.
[15:24:54] <BigJohnT> ok thanks jepler
[15:26:52] <dave_1> hey jepler ... how do I start the sim version??
[15:26:58] <dave_1> of emc
[15:27:31] <BigJohnT> thanks archivist_ub
[15:28:14] <archivist_ub> BigJohnT, I found it writing my helix milling code
[15:28:28] <BigJohnT> I've fixed it
[15:29:04] <BigJohnT> archivist_ub: anytime you find stuff like that feel free to let me know
[15:30:13] <jepler> the home position repeats to much better than .001 inch
[15:30:46] <BigJohnT> I found mine to be more accurate than I gave the switch credit for
[15:30:53] <jepler> dave_1: the sim version of emc2 starts just the same as the rt version, but you have to choose a configuration that doesn't load any hardware drivers. the ones in the "sim" folder of sample configurations fall into this category, as do several others.
[15:31:12] <archivist_ub> jepler, you using cheapo micro switches as well
[15:31:15] <jepler> archivist_ub: yeah
[15:31:31] <archivist_ub> I have my supplies, I must fit
[15:32:10] <jepler> I need to figure out how to sanely route these wires and hook them to my I/O board
[15:32:32] <archivist_ub> dunno how to home the rotating axis's nicely yet
[15:33:08] <anonimasu> what about a inductive sensor
[15:33:17] <anonimasu> and a index pulse
[15:33:42] <anonimasu> or absolute encoders ;)
[15:34:14] <archivist_ub> nowhere to fit on a Vertex HV4
[15:34:50] <archivist_ub> hasnt even got sensible bolt holes to fit to table
[15:35:17] <anonimasu> ah.. yeah :/
[15:35:30] <anonimasu> I have one too
[15:35:44] <archivist_ub> I need another for the 5th axis
[15:35:50] <anonimasu> but it has sane bolt holes :)
[15:36:01] <archivist_ub> you drilled it?
[15:36:04] <anonimasu> I think a hv6
[15:36:11] <archivist_ub> ah
[15:36:19] <anonimasu> but it's got a bit of slop
[15:36:40] <archivist_ub> this is not perfect, but good enough
[15:39:38] <dave_1> jepler ... I've spaced ... typing emc only get me "emc: command not found"
[15:39:39] <archivist_ub> for the price I think reasonable
[15:40:12] <archivist_ub> dave_1, liveCD?
[15:40:42] <dave_1> no... older install ... right after sim was announced ...
[15:41:03] <dave_1> I don't get the usual popup to select config
[15:41:50] <dave_1> IIRC it took as multi word command line
[15:41:56] <dave_1> a multi
[15:43:23] <dave_1> maybe I should just reinstall with a more modern version
[15:48:49] <archivist_ub> anonimasu, I add a jog at the start of the gcode to remove backlash, so I always push against if I can
[15:50:42] <SWPadnos> dave_1, do you have any executables that begin with `emc` on your path?
[15:50:59] <SWPadnos> like the old emc.run (or generic.run, or whatever.run ...
[15:51:01] <SWPadnos> )
[15:54:12] <dave_1> ah .. finally stumbled across it. $scripts/emc does it :-)
[15:54:37] <dave_1> that gets me the popup
[15:54:46] <SWPadnos> oh, is this a compiled "run-in-place" install?
[15:54:54] <dave_1> yes
[15:55:02] <SWPadnos> if so, then you should source scripts/emc-environment
[15:55:11] <SWPadnos> `. scripts/emc-environment`
[15:55:24] <dave_1> ok
[15:55:45] <SWPadnos> that will set up the path and other stuff so things like man work (in that shell only)
[15:56:43] <dave_1> thanks!!
[15:57:01] <SWPadnos> qsure
[15:57:04] <SWPadnos> -q
[16:02:59] <DanielFalck> SWPadnos: if you have any plans to visit the Northwest, look me up. I'd like to show you our shop sometime.
[16:03:07] <SWPadnos> sounds good to me!
[16:03:12] <DanielFalck> your brother lives in Beaverton right?
[16:03:21] <SWPadnos> I'll let you know - I have a brother in law in Portland and friends in Seattle
[16:03:31] <SWPadnos> yeah - Beaverton (close enough :) )
[16:44:48] <jepler> hm, motor offset isn't available on a pin
[16:44:50] <jepler> or parameter
[16:45:36] <SWPadnos> joint.n.motor-cmd-pos vs. axis.n.motor-cmd-pos
[16:45:50] <SWPadnos> at least according to the manpage for motion
[19:01:33] <alex_joni> SWPadnos: don't think that's really motor offset
[19:01:49] <SWPadnos> it says it includes things like backlasn and screw comp
[19:04:05] <alex_joni> ok, might be
[19:19:23] <KimK> KimK is now known as KimK_
[19:19:56] <cradek> hi - are you the kim guy from cnc workshop?
[19:20:48] <KimK_> Hi Chris. Yeah, that's me.
[19:21:36] <cradek> welcome. how's it going?
[19:21:43] <alex_joni> hi Kim
[19:24:01] <KimK_> Still fooling around getting alternate nicks registered. Not bad, got a potential retrofit on a pair of chuckers. We'll see. Hi Alex, sorry I didn't get to meet you at the 2008 Workshop. Maybe next year.
[19:24:11] <alex_joni> KimK_: I wasn't there :)
[19:24:15] <alex_joni> maybe next year
[19:25:12] <KimK_> Anyone have any opinions on early 1980's Cincinnati Milacrons?
[19:25:29] <KimK_> either iron or electronics?
[19:26:04] <SWPadnos> I have zero experience with them, but I'd say scrap the electronics unless they work perfectly ;)
[19:26:12] <SWPadnos> hi Kim
[19:27:48] <KimK_> Hi SWP. Yes, I agree, especially since even the one that *works* takes five rolls of #$%^&* paper tape to bring it back from the "dead".
[19:28:09] <SWPadnos> heh
[19:28:16] <SWPadnos> tape == scrap IMO
[19:32:50] <KimK_> Yes, it's certainly an EMC2 candidate. At least that's what I have in mind. But the operators panel has some peculiarities. For example, it has 4 "select jog direction" buttons (membrane keyboard w/ adjacent state LED) and only one actual jog button (industrial pushbutton). Stuff I'll be glad to be rid of.
[19:34:16] <jmkasunich> you could probably even to that in EMC (not that you'd want to - but you can)
[19:35:34] <SWPadnos> actually, the 4 buttons and state indicator are more in keeping with the "NIST principle" than a multi-position knob
[19:35:39] <cradek> sounds like an awful user interface...
[19:36:20] <SWPadnos> if the GUI has an "active axis" output, then the LED show changes from the GUI as well as the buttons
[19:36:24] <cradek> mine has two buttons, X/Y/Z and JOG/WHEEL/INCREMENTAL so you have to stab at the two of them until the display shows what you want
[19:36:28] <jmkasunich> SWPadnos: only if you accept that a "direction + go" button is a good way to do jogs
[19:36:36] <cradek> it sucks. forget doing anything without looking at it.
[19:36:51] <SWPadnos> true, direction is pretty dumb, I was thinking it was the axis select
[19:37:08] <jmkasunich> axis select + jogwheel would be nice
[19:37:39] <cradek> jogwheel axis select should be a hard switch IMO. you should be able to switch it to the axis you want without looking.
[19:38:24] <SWPadnos> yeah - since each set of jogging controls is independent, you can have an axis selector+wheel at each one - keeps someone elsse from changing what the control in your hand will do
[19:40:51] <jmkasunich> cradek: exactly - the "push one button N times until the indicator says the right thing" is lame - it is used only when buttons (or I/O points) are way too expensive to afford more
[19:41:03] <jmkasunich> like alarm clocks
[19:42:24] <KimK_> Yeah, the electronics are junk, and that can be fixed with EMC2. But my "research project" is this: The owner is reluctant to spend any money on them at all. He seems to think that nobody would want a Cincinnati-Milacron, preferring instead (of same approx vintage, price, etc.) Okuma, Hass, (pretty much name your competing brand). So: does C-M have a bad rep in the used market? And is it because of the electronics (which I ca
[19:42:26] <KimK_> n agree with, and there's a remedy for) or is it because of the iron? (or something similar, maybe something not easily fixed?)
[19:42:49] <KimK_> Oops, talked too long, I'm a flooder, LOL
[19:43:06] <SWPadnos> heh
[19:45:32] <jmkasunich> unfortunately only a fairly small percentage of the people in here are familiar with production-class machinery
[19:46:23] <jmkasunich> for example, I have a 66 year old Van Norman knee mill, and a 10 year old chinese 3-in-1
[19:46:36] <jmkasunich> the 3-in-1 is CNC'ed with EMC, the mill is manual
[19:46:51] <cradek> I have a 25 year old bridgeport and 30 year old hardinge lathe
[19:47:33] <KimK_> Hi John. Thanks for joining in.
[19:47:53] <jmkasunich> oh, and I have a 18 year old "Targa" (taiwan) 6x12 manual surface grinder, that I am reconditioning
[19:48:32] <rayh> There is nothing wrong with Cinci. Good machines. I don't think I'd try to sell one that I'd fitted EMC2 to but that would be equally true of any retrofit not named Fanuc.
[19:48:42] <jmkasunich> you might want to post your question on the emc-users mailing list - there are about 600 people there (vs. 47 online here)
[19:48:59] <KimK_> Hi Ray, good to hear from you.
[19:49:08] <rayh> But for production it would work great. Hi Kim.
[19:49:30] <jmkasunich> you might also want to post on CNCzone - they seem to have a higher proportion of shop owners, etc (at least in some channels)
[19:54:05] <KimK_> rayh: Your point about the popularity of Fanuc is certainly valid, but the expected cost vs. resale price makes a Fanuc retrofit unlikely, and since these two have been sitting around for some time, I think it may be EMC2 or the scrapyard.
[19:54:41] <KimK_> Hate to see them made into patio furniture.
[19:55:02] <rayh> You bet it does.
[19:55:43] <rayh> Fanuc costs less now than a while back but still not worth it for my thinking.
[19:59:24] <KimK_> While I consider everyone's valuable advice... John, what reconditioning work does your grinder need?
[20:00:24] <fenn> rayh: curious, why would you not want to sell a retrofit machine?
[20:00:40] <alex_joni> fenn: the need to support it
[20:00:53] <alex_joni> (would be one of my reasons)
[20:01:20] <SWPadnos> many/most big shops will look at the brand of control, then move on if it isn't on their short list of favorites
[20:01:29] <rayh> The machine would be fine. Selling it with a "noname" control would be the difficult part.
[20:03:44] <KimK_> Yes, some (big) shops are that way, Fanuc only, Haas only, etc. But maybe small or medium shops would be OK with it. And occasional ongoing support is not necessarily a bad thing either.
[20:09:59] <KimK_> Are there INI files (or whatever?) to make EMC2's behavior more Fanuc-like, more Haas-like, more whatever-like?
[20:10:36] <fenn> it's already pretty close to fanuc
[20:10:42] <SWPadnos> no, if you're talking about the specific G-doce dialects
[20:10:47] <SWPadnos> g-code
[20:11:38] <SWPadnos> there has been some discussion about making custom G-codes using a macro language of some sort (Ken Lerman is thinking about it IIRC)
[20:12:52] <KimK_> I had in mind just so that someone who was very used to a brand X control would feel comfortable, or at least not be booby-trapped by some difference.
[20:13:52] <SWPadnos> yeah - it's not so configurable that you could make a Fanuc-like UI. at least not without writing some code
[20:13:56] <alex_joni> KimK_: we have a great manual :P
[20:14:20] <servant74> It would seem (I am no expert) that macro's or pre-processing the different dialect NC files could generate an independant version of NC files. ... that wouldn't get over user interface issues
[20:19:19] <KimK_> I don't think the UI would be a big problem. I was more worried about some obscure, seldom-used G command working "backwards" or something (yikes!). But servant74's idea of pre-processing, might be just the ticket.
[20:23:33] <SWPadnos> if a list of "trouble codes" can be made, it's pretty easy to look for them
[20:26:22] <KimK_> Yeah, that's good. And the fact that EMC2 is "already pretty close to fanuc" helps also. (Not sure if we are both following the standard or if the standard was set because of Fanuc, but, whatever, it works for me.
[20:28:43] <KimK_> KimK_ is now known as KimK
[20:45:09] <jmkasunich> KimK: regarding reconditioning (I was working when you asked) - it has a lot more wear on the cross-slide ways than I knew when I bought it
[20:45:19] <jmkasunich> it was only $210 tho, so I don't feel too bad
[20:45:53] <jmkasunich> I'm planning to rescrape the ways - I did one flat surface already: http://jmkasunich.com/cgi-bin/blosxom/index.html
[20:46:19] <jmkasunich> at the moment I'm working on an angle straight-edge to use for spotting the dovetails
[20:50:24] <dushantch_> dushantch_ is now known as dushantch
[20:57:01] <KimK> jmkasunich: Nice report, thanks. You've worked hard on that grinder, it should be nice when done. Keep us posted.
[21:38:25] <toastydeath> i need to come up with a banner for my webpage
[21:38:34] <toastydeath> to replace the default banner that comes with the framework =(
[21:47:37] <SkinnYPup> I was discussing Qcad yesterday, here's a little something I threw together real quick as an example of it goofin on the arc center placements .
[21:47:38] <SkinnYPup> http://imagebin.org/23498
[21:48:23] <mhel> hello
[21:49:27] <SkinnYPup> http://imagebin.org/23499 The toolpath shown in axis is a 30,60,90 triangle it had no problem radiusing.
[21:50:30] <SWPadnos> it looks like qcad is outputting 3 significant digits
[21:50:38] <SWPadnos> can you change it to 4?
[21:51:19] <SWPadnos> also, for the next screenshot, could you make the line with the error visible? :)
[21:52:36] <BigJohnT> SkinnYPup: what did you use to convert from dxf to g code?
[21:52:38] <SkinnYPup> I think it goes as high as .0000000x but it just doesn't calculate the radius trims to that accuracy.
[21:52:56] <SWPadnos> qcad lets you design and output GCode AFAIK
[21:53:33] <BigJohnT> * BigJohnT looks
[21:54:01] <SkinnYPup> I've used both gcnccam and dxf2gcode to generate that. But double verified that Qcad is to fault using mastercam to compare trim radiused start end and centerpoints
[21:54:17] <DanielFalck> SWPadnos: I think it's 'camexpert' from Ribbonsoft
[21:54:29] <SWPadnos> oh - does qcad not output GCode?
[21:54:33] <DanielFalck> no
[21:54:33] <BigJohnT> no
[21:54:37] <SkinnYPup> Not native
[21:54:42] <SWPadnos> bummer - nevermine me then :)
[21:54:46] <SWPadnos> nevermind
[21:54:53] <cradek> I see it says (Generated with dxf2code)
[21:55:07] <BigJohnT> I use sheetcam and qcad with no problems
[21:55:12] <cradek> it could be qcam or dxf2code that needs to be fixed
[21:55:15] <SWPadnos> well, I didn't observe that well :)
[21:55:28] <cradek> if they are open source this should be simple
[21:55:47] <BigJohnT> SkinnYPup: can you post the dxf file that qcad generates on pastebin?
[21:56:07] <SkinnYPup> Sure ! hangon
[21:56:23] <BigJohnT> also I get errors all the time from mastecam with arcs
[21:56:36] <BigJohnT> no matter the source of the dxf file
[21:57:40] <BigJohnT> DanielFalck: my wife says the bottom of the first one is too fat and don't look right for a butterfly
[21:58:34] <mhel> hobbyist & linux noobie here, need a little help compiling emc 2.2.5 on ARCHLinux kernel 2.6.25 patch with Xenomai 2.4.4
[21:58:36] <SkinnYPup> lol
[21:58:44] <SkinnYPup> Here's the pastebin
[21:58:46] <SkinnYPup> http://pastebin.com/m15b7d39c
[21:58:54] <DanielFalck> BigJohnT: I've never looked at them that close, so I wouldn't know
[21:59:38] <BigJohnT> SkinnYPup: one moment
[21:59:44] <cradek> the dxf looks fine. it has full precision
[21:59:54] <SkinnYPup> Oh no hurry been bangin at this for a while
[21:59:56] <cradek> so I assume 'dxf2code' is nuking it
[22:00:32] <BigJohnT> opens fine in sheetcam ...
[22:00:42] <cradek> #
[22:00:42] <cradek> 11
[22:00:44] <cradek> #
[22:00:44] <cradek> 2.4494897427831788
[22:00:44] <cradek> #
[22:00:46] <cradek> 21
[22:00:49] <cradek> #
[22:00:51] <cradek> 4.2426406871192857
[22:01:03] <cradek> compare these to the endpoints in the error message
[22:01:18] <cradek> you can see that dxf2code truncated them at 3 places after the decimal
[22:01:34] <cradek> you should be able to just change it to 4 or 5
[22:03:11] <BigJohnT> SkinnYPup: works ok with sheetcam
[22:03:17] <BigJohnT> on moment
[22:04:19] <BigJohnT> http://pastebin.ca/1091262
[22:04:40] <BigJohnT> you will have to comment out the o<touchoff> call line
[22:08:50] <DanielFalck> SkinnYPup: which program did you use again for converting to gcode? Where did you get it from?
[22:09:31] <Jamie> Jamie is now known as Guest26797
[22:10:35] <BigJohnT> * BigJohnT heads upstairs for butterfly inspection :)
[22:10:39] <SkinnYPup> Ok had to try out a few things there. BigJohn, yes that is a good toolpath. You generated that with sheetcam ?
[22:10:51] <BigJohnT> yes
[22:11:02] <SkinnYPup> I'll have to try it thankyou
[22:11:29] <BigJohnT> it's free at the moment and has a linux distro
[22:11:35] <SkinnYPup> DanielFalck: I used dxf2gcode
[22:11:53] <DanielFalck> SkinnYPup: was it from here:http://dxftogcode.googlepages.com/dxf2gcodedxftogcode
[22:11:55] <BigJohnT> If the post gets you confused I can send you one
[22:12:24] <DanielFalck> of was it a simpler c program from http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Cam
[22:14:53] <SkinnYPup> Its not c , .py
[22:15:46] <SkinnYPup> http://translate.google.com/translate?hl=en&langpair=de|en&u=http://www.christian-kohloeffel.homepage.t-online.de/dxf2gocde.html
[22:16:05] <DanielFalck> SkinnYPup: thanks
[22:16:20] <BigJohnT> * BigJohnT passed butterfly inspection
[22:16:46] <SkinnYPup> DanielFalck: Didn't know there was more than one dxf2gcode !
[22:17:06] <DanielFalck> there's a bunch with that name
[22:20:14] <cradek> SkinnYPup: in the dxf2gcode postproc file, set post_decimals to 4 instead of 3
[22:22:39] <SkinnYPup> cradek: I'll check that. Thanks
[22:23:31] <cradek> it's the first setting in the file :-)
[22:24:40] <colinb> ola
[22:24:43] <jmkasunich> mhel: your question got lost in the traffic I think
[22:24:58] <jmkasunich> if it has to do with compiling, etc, you might be better off asking on #emc-devel
[22:25:05] <mhel> thnks, I'm just waiting for possible reply :)
[22:25:27] <jmkasunich> actually, you didn't ask a question ;-)
[22:25:36] <cradek> I was noticing that too
[22:25:37] <jmkasunich> you just saId you were having a problem
[22:26:34] <mhel> I did hope that someone would ask me what tho.. he.he
[22:27:10] <mhel> i'm gonna ask at devel then.
[22:31:40] <SkinnYPup> cradek: The postproc file with post_decimals you refered to . Is it dxf2gcode A or B ? http://dxftogcode.googlepages.com/dxf2gcodedxftogcode
[22:31:42] <SkinnYPup> OR
[22:31:44] <SkinnYPup> http://translate.google.com/translate?hl=en&langpair=de|en&u=http://www.christian-kohloeffel.homepage.t-online.de/dxf2gocde.html
[22:33:29] <SkinnYPup> I don't have any M.S. windows running to try http://dxftogcode.googlepages.com/dxf2gcodedxftogcode at the moment.
[22:34:52] <DanielFalck> don't worry about it, I bet a lot of folks here don't either : )
[22:35:07] <DanielFalck> use the source Luke....
[22:39:14] <colinb> shame theres no real decent cad/cam under linux
[22:39:28] <colinb> pro/e is ok for cad but cam is a bit lacking
[22:39:31] <DanielFalck> there's is it's called Unigraphics NX
[22:39:49] <DanielFalck> it costs a lot
[22:40:15] <DanielFalck> there's also sheetcam and webersys now
[22:40:20] <colinb> true
[22:40:30] <colinb> dont think nx is all that good for cam eitehr
[22:41:01] <colinb> my place used nx5 for cam but binned it off for hypermill
[23:52:56] <dave_1> colinb ... I think synergy (webersys) will do just about anythink you want including 4th and 5 axis but the learning curve is really steep.
[23:53:23] <dave_1> at least is is steep for me but maybe that is an age thing. I don't do python either.
[23:53:25] <colinb> oh right
[23:53:33] <colinb> not heard of webersys tbh
[23:53:46] <dave_1> opps ... anythink == anything
[23:54:07] <colinb> learning delcam powermill at the moment for my new job
[23:54:18] <colinb> thats quite a complex program
[23:54:50] <dave_1> Weber Systems wrote and sells synergy
[23:55:25] <dave_1> 2.5 D thru 3D 5th axis
[23:56:39] <dave_1> $250 gets you 2.5D cam and then the price goes up from there. .... if you are interested email webersys.com ... check the website.
[23:57:26] <colinb> ah yeah just had a look
[23:57:29] <colinb> iv seen it before
[23:58:10] <dave_1> I use it for a lot of 2.5 D but have not been successful in the 3D mode