#linuxcnc | Logs for 2012-07-07

Back
[02:15:36] <DJ9DJ> moin
[02:47:45] <DJ9DJ> morning Loetmichel :D
[02:49:51] <Loetmichel> mornin'
[04:17:18] <r00t4rd3d> Nothing like dry heaves in the morning!
[07:33:54] <delkin> hi everyone. I built a cnc machine with a dremel mini driller machine, and I bought a drill bit (http://www.aki.pt/produto.aspx?categoryid=2613&productid=17727&sid=0) that became completely black and flat after 20min of usage (wood-MDF milling). Yesterday, I bought the best milling bit in the shop made of tungsten carbide (http://www.google.com/products/catalog?q=PFERD+drill+bit&oe=utf-8&client=ubuntu&channel=fs&um=1&ie=UTF-8&tbm=shop&cid=1401
[07:33:54] <delkin> 2914852356348886&sa=X&ei=Bin4T9OMAcqx0QXG78X5Bg&ved=0CG0Q8gIwCQ) and the result was the same :\ What am I doing wrong? What milling bits should I use for wood milling? What feed speeds to you recommend while milling wood?
[07:34:19] <delkin> (http://www.google.com/products/catalog?q=PFERD+drill+bit&oe=utf-8&client=ubuntu&channel=fs&um=1&ie=UTF-8&tbm=shop&cid=1401
[07:46:14] <jthornton> your links are borked
[07:47:26] <jthornton> archivist, I fingered out the missing link text :)
[07:48:47] <jthornton> delkin, what rpm, cutter diameter, depth of cut, and feed rate were you using?
[07:51:48] <gmagno> jthornton, 20000rpm, bit diameter: 2.1mm, depth: 3mm, feed rate: 1mm/sec
[07:52:13] <gmagno> btw, i'm working with delkin on this cnc project
[07:52:18] <delkin> jthornton: gmagno is gonna take care of the details
[07:52:51] <jthornton> let me see if I have my calculator on this computer
[07:53:05] <ctjctj> I'm attempting to write a "remote DRO display". I'm using linuxcncrsh for the source of information. Currently the DRO on axis is reporting: x=1.0, y=0, z=0: G54 x=0.5, y=0.5, z=-2.0 which is all correct. At the same time linuxcncrsh is reporting: ABS_ACT_POS 1.500000 0.500000 -2.000000 0.000000 0.000000 0.000000 (correct) REL_ACT_POS 0.500000 -0.500000 2.000000 0.000000 0.000000 0.000000 (does not match anything on the axis DRO)
[07:53:07] <ctjctj> and POS_OFFSET 1.000000 1.000000 -4.000000 0.000000 0.000000 0.000000 (Which apears to be abs-rel but does not match G54 numbers in DRO) Where do I get the actual G54 offsets via linuxcncrsh OR the current relative offsets?
[07:53:28] <archivist> jthornton, one day can someone get me a dump of the forum db so I can generate an update for all the dead links
[07:53:51] <jthornton> gmagno, yikes that is a small bit... reduce the DOC to 1/2 or less the bit diameter
[07:54:09] <jthornton> how many teeth on the cutter?
[07:54:46] <gmagno> jthornton, what is DOC?
[07:54:57] <Jymmm> Death of Cut
[07:55:01] <Jymmm> Depth
[07:55:11] <Jymmm> or death I guess works too =)
[07:55:12] <gmagno> hmm ok
[07:55:16] <gmagno> :D
[07:55:23] <ctjctj> If it is too deep it will be death of cut breaking material or cutter. *GRIN*
[07:55:54] <archivist> well it will be death of the cutter due to being burnt and clogged
[07:56:29] <jthornton> gmagno, how many teeth on the cutter
[07:57:08] <gmagno> jthornton, let me check
[07:57:21] <Jymmm> gmagno: If you ever get up to 1/4" shank, I'd recommend CMT (brand) Spiral Upcut router bit. I've have good results with them and crappy results/broken bits using Freud Brand.
[07:59:01] <andypugh> That carbide bit is a burr, intended for use in a die-grinder on metal. (and probably by hand)
[07:59:29] <andypugh> It is likely to just clog with MDF, which is largely made of glue.
[07:59:33] <gmagno> jthornton, I believe 12 teeth
[08:00:09] <jthornton> yep what andypugh said
[08:00:23] <archivist> not suitable for wood except light hand work
[08:00:55] <andypugh> You will see that wood is not listed amongst the applicable materials.
[08:01:35] <jthornton> gmagno, you might get by with a very shallow DOC like 1mm with a burr
[08:01:36] <gmagno> hmm
[08:02:54] <gmagno> and would you recommend this bit to pcb?
[08:02:57] <jthornton> something like this is wat you want http://www.aliexpress.com/store/product/solid-carbide-cnc-tool-router-bit-end-mill-suitable-for-MDF-PVC-ABS-Acrylic-Aluminum-copper/506241_434569247.html
[08:03:02] <jthornton> for mdf
[08:04:29] <gmagno> I see
[08:04:51] <jthornton> the only thing I've experienced with that kind of bit is violent shaking and the collet coming loose when trying to enlarge a hole
[08:05:17] <archivist> note the number of teeth is reduced to allow chip clearance
[08:05:18] <Jymmm> http://www.precisebits.com/applications/pcbtools.htm
[08:06:36] <andypugh> ctjctj: Ah, just remebered you :-)
[08:06:41] <Jymmm> http://www.thinktink.com/stack/volumes/voli/store/mechmill.htm
[08:06:55] <ctjctj> andypugh: Is that good or bad?
[08:07:39] <andypugh> ctjctj I just remembered skimming past your question, is what I meant. Billooms on the forum has noticed the same wierdness.
[08:07:57] <gmagno> jthornton, have you tried using this drill with pcb?
[08:08:06] <gmagno> would you recommend?
[08:08:18] <andypugh> I have a suspicion that there might be a bug.
[08:08:44] <archivist> gmagno, see bits Jymmm pasted for pcb, they will be different to mdf
[08:08:58] <ctjctj> andypugh: Hmmm, that's about where I was.
[08:09:06] <Jymmm> gmagno: Thy these: http://www.precisebits.com/applications/pcbtools.htm OR http://www.thinktink.com/stack/volumes/voli/store/mechmill.htm
[08:09:10] <Jymmm> Try
[08:10:00] <ctjctj> andypugh: Long time ago I learned that it is best to assume I'm making a mistake than to assume there is a bug.
[08:10:08] <andypugh> ctjctj: Have you had a look at the code to see if it makes any sense?
[08:10:12] <gmagno> ok, thanks a lot
[08:10:50] <ctjctj> Just about to dig into the code. There are other oddities in linuxcncrsh such as unit conversions. Today I'm getting inch conversion and yesterday it was all in mm.
[08:10:59] <Jymmm> gmagno: Those are for PCBs, not MDF =)
[08:12:20] <andypugh> ctjctj: You can use (DEBUG, #5420) and similar codes in the MDI window of AXIS to directly read out the G54 etc offsets. Give me a minute I will find the list.
[08:12:29] <ctjctj> andypugh: and if I'm in the code and it is usable I might just look into adding a "program_length" get so that I can get the number of lines in a program. Then the GUI will put up a progress bar based on current line number vs total lines in program. If current line number jumps twice then I'll assume a loop and go toa pulse progress bar.
[08:12:49] <gmagno> Jymmm, yup, in the end that's what I'll be machinning. Just tried some MDF works to see how the CNC worked
[08:12:54] <ctjctj> andypugh: that doesn't get it into linuxcncrsh.
[08:13:37] <r00t4rd3d> my first "part" :
[08:13:38] <r00t4rd3d> http://imgur.com/a/mvjQE
[08:13:40] <andypugh> No, not at all. The first step is to work out where the numbers used by linuxcncrsh are coming from...
[08:14:01] <ctjctj> gmagno: MDF makes a wonderful powder when milled that goes everywhere, clogs everything, kills just about everything. Different from pcb milling. (Or just about anything else)
[08:15:32] <Jymmm> r00t4rd3d: Cool! (PLEASE tell me you really aren't going to have that thin of tabs i the real thing? You need extra 'meat' in that area, no matter what material you'll be using)
[08:15:51] <andypugh> ctjctj: The G54 offsets are at 5221-5230 : http://www.linuxcnc.org/docs/html/gcode/overview.html#_numbered_parameters_a_id_sub_numbered_parameters_a
[08:16:32] <ctjctj> yes: And they are reported correctly in the axis DRO. Checked those. But they don't match anything in the emcrsh outputs.
[08:18:19] <Loetmichel> hmm, the android devices are getting stacked over here... i think i should restrain my ebay habits ;-) -> http://www.cyrom.org/palbum/main.php?g2_itemId=13406 ;-)
[08:18:20] <gmagno> ctjctj, yeah, my garage becomes a mess :)
[08:18:40] <r00t4rd3d> Jymmm, I only know how to use pycam to do engraving atm with gravure settings, so it cut out the line instead of just following the outline :(
[08:18:56] <ctjctj> andypugh: what's the git repository URL?
[08:19:13] <Jymmm> r00t4rd3d: Ok, that you can resolve though =)
[08:19:17] <andypugh> ctjctj: You have spotted that linuxcncrsh is src/emc/user_intf/emcrsh.cc ?
[08:19:32] <andypugh> git.linuxcnc.org
[08:19:44] <r00t4rd3d> i need to ask in the forums how
[08:20:09] <andypugh> ctjctj: Spcifically http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=src/emc/usr_intf/emcrsh.cc;h=f1bda64627c381ab6acb9d6fc2eb343b8014a8a9;hb=HEAD
[08:20:42] <ctjctj> andypugh: I'm having a hard time cloning it (newish to git)
[08:22:36] <andypugh> ctjctj: git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev
[08:22:59] <andypugh> Or use the gitweb link to view the single file.
[08:23:21] <ctjctj> Thank you.
[08:23:27] <andypugh> Git instructions for linuscnc here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Git
[08:23:45] <ctjctj> Yeah, found those just before you answered. :-(
[08:24:03] <Jymmm> andypugh: ctjctj lies.
[08:24:12] <ctjctj> I'm going to go eat breakfast with the kids then come back and look at source till I figure out where those numbers come from.
[08:24:28] <ctjctj> Jymmm: Yes he does. He's going to eat with kids and wives.
[08:25:07] <Jymmm> ctjctj: If you have wives, I hope you have a damn fine set of earplugs too!
[08:26:12] <Jymmm> Anyone have a 100 Ton press you could fax me?
[08:26:58] <archivist> use an inertial press.....hammer
[08:27:31] <Jymmm> archivist: I aint 100 tons
[08:27:42] <Jymmm> 99.9999 maybe ;)
[08:27:43] <archivist> poor mans press a jack, paupers press, a screw
[08:28:15] <archivist> the lazy use a lever
[08:29:07] <Jymmm> Heh, no. I would like to press out some containers from a coin sized disc
[08:29:25] <andypugh> Naval press a jack tar.
[08:29:47] <archivist> a fly press
[08:29:48] <Jymmm> andypugh: Say that in an earth language please
[08:30:17] <Jymmm> like have they make soda cans and such
[08:30:50] <Jymmm> or wine bottle toppers
[08:31:01] <andypugh> I was speaking english. It's just that you speak american. http://en.wikipedia.org/wiki/Impressment and http://en.wikipedia.org/wiki/Jack_tar
[08:31:29] <Jymmm> andypugh: I never said english, I said an EARTH language =)
[08:32:50] <archivist> Jymmm, be sensible, get a subcontractor to make parts like that
[08:33:42] <Jymmm> archivist: It's just a pipe dream, will never happen. The tooling alone would be way over the top.
[08:34:27] <archivist> toggle press, I have one
[08:34:44] <Jymmm> Even if the initial order was 1000 units, the tooling would be 10x as much.
[08:35:41] <archivist> I have made press tooling for my model watering cans
[08:37:02] <archivist> a tube, a male sphere die, and a ball bearing and a clamping ball bearing
[08:38:42] <Jymmm> Well, I found aluminum container (from china of course) around $2/unit in small qty, and I got a quote for 50,000 units in plastic WITHOUT any tooling charges that's fairly reasonable.
[08:38:55] <Jymmm> US made
[08:41:01] <Jymmm> pcw_home: Got any spare room for a shipping container by chance? lol
[08:42:59] <Jymmm> Gawd... How many 6"x1" could you fit in a shipping container I wonder?
[08:43:11] <Jymmm> 6"x1"x1"
[08:47:46] <ctjctj> Jymmm: 1,172CuFt 337536 max not allowing for pallets or packing.
[08:47:51] <andypugh> I had a press made for a metal dish once. And I onluy needed one.
[08:48:22] <andypugh> A press is cheap, and will be useful in the future.
[08:49:08] <andypugh> http://www.harborfreight.com/20-ton-shop-press-32879.html
[08:51:17] <ctjctj> andypugh: Oh I love this, setOpen() has a char fileStr[80] which is filled from user input. ...
[08:52:38] <archivist> andypugh, I needed that two weeks ago
[08:53:44] <archivist> used screw type pullers to put basic stress on and a little hammer work to get above the friction
[08:54:22] <andypugh> ctjctj: I think that GET_REL_POS is broken. Have a look at lines 1678 onwards. The g5x offset is subtracted twice. over and over again. Also in REL_ACT_POS. POS_OFFSET might also be half-wrong, as that uses g92 offset, which I think was the intention in the other functions. It looks an awful lot like a long-standing copy and paste error
[08:55:09] <ctjctj> andypugh: I'm getting there. Thanks. G92 is suppose to be added to the G54... offsets (I think)
[08:58:51] <ctjctj> Ok. Looks like the positions are going to come from emcStatus->motion.traj.position....
[09:00:46] <ctjctj> andypugh: and you are absolutely correct. They are subtracting task.g5x_offset twice and I think the second should be a g92 instead of g5x but I have to look at the structure of a task.
[09:02:20] <andypugh> billooms on the forum has been puzzling over the exact same issue. I am almost tempted just to make the change and push it as a bugfix. But it is just possible that it is correct.
[09:02:37] <Jymmm> Those poor bastards... http://www.youtube.com/watch?v=3v8g0SE6jX4
[09:02:50] <ctjctj> Nope. Matches what I've been seeing as a result. Just didn't understand it.
[09:03:10] <ctjctj> andypugh: it is wrong and a bug. Where is the task structure defined?
[09:03:17] <andypugh> (You _might_ subtract the same number twice to save multiplying by 2 in time-critical code. But I am pretty sure that it makes no sense)
[09:03:56] <ctjctj> The second should be g92_offset instead of g5x_offset
[09:04:11] <ctjctj> Per taskmodule.cc
[09:11:41] <ctjctj> andypugh: look at line 1780 and you'll see that somebody had already done a partial fix for the A,B,C and D axis.
[09:11:49] <andypugh> The bug seems to have persisted for many years.
[09:12:21] <andypugh> ctjctj: I don't think that was a partial fix, I think those just dodn't get copy-pasted the same way.
[09:12:35] <ctjctj> and if you asked for pos_offset on a per axis basis it gave the "right" result. I think it was a cut and paste that went wrong.
[09:12:48] <andypugh> I am sure it was.
[09:13:57] <andypugh> I don't need any more convincing about what the bug is. I am just waiting on confirmation from a developer to push the fix.
[09:14:02] <ctjctj> Ok: Now for the 64,000,000 dollar question (inflation don't you know): You've made the fix. It is in the source, it will show up in my next pull from buildbot for my workstation. How the heck do I get this linuxcncrsh over to my 10.04 REAL system?
[09:15:10] <ctjctj> andypugh: can you explain the procedure that you allude to via "waiting on confirmation from a developer to push the fix?"
[09:15:31] <andypugh> If you point your real system at the buildbot, then it will get the daily builds as a normal update, I think.
[09:15:56] <Tom_itx> Jymmm are they stackable?
[09:16:46] <Tom_itx> who was asking about step and repeat code the other day?
[09:17:09] <ctjctj> andypugh: Hmmm... So I'd pull the daily build for the 2.5 and it would get the bug fix?
[09:17:11] <andypugh> ctjctj: I have push-access to the main Linuxcnc code repository, so I can make bugfixes. I just want a second opinion from someone familiar with the code that there are no unanticipated consequences of making the change.
[09:17:48] <Tom_itx> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Oword#Sample_5_Subroutine_for_generating_multiple_parts_using_Local_and_Global_coordinates
[09:17:49] <ctjctj> *nods* Thank you for explaining.
[09:18:00] <andypugh> ctjctj: Well, it would if the builbot wasn't on vacation.
[09:18:10] <andypugh> Ah, wait, he's back
[09:19:20] <ctjctj> andypugh: so you'd push your fix to the main repository. Then (my learning git) that commit would be merged with the older 2.5, 2.4 branches in order for the fix to propagate correctly?
[09:20:52] <andypugh> I would make the change in the 2.5 branch. It would then be included in the next 2.5 buildbot build, and eventually the release build too. The changes would be merged into the upstream (master / 2.6 ) build at some point too. They would _never_ be included in 2.4.
[09:21:39] <ctjctj> Just curious, why "never" in 2.4? because that is closed?
[09:21:49] <andypugh> There will never be any more 2.4 releases (as far as I know) so no point making changes there.
[09:22:19] <Tom_itx> yeah, .5 was the big name change ver
[09:23:28] <ctjctj> andypugh: there is still more wrong. I need to double check before you push that fix. You can test via linuxcncrsh and asking "get pos_offset" and "get pos_offset x" They return different wrong answers.
[09:24:48] <andypugh> There are problems in at least three functions.
[09:25:48] <ctjctj> Yes. But I'm testing the code that is currently in place. If you look at the original pos_offset you'll see that they had g5x_offset twice when you use the default.
[09:25:52] <Poincare> any advice/hints for someone who just put his index finger between the workpiece and a spinning circular saw?
[09:26:06] <Tom_itx> don't do it again?
[09:26:32] <ctjctj> If instead you ask "get pos_offset x" the code that you and I were assuming would work is used, g5x_offset+g92_offset,
[09:26:36] <Poincare> :-)
[09:26:57] <Tom_itx> must not be that bad. you're still here and typing
[09:26:59] <ctjctj> The results for get pos_offset x returns "POS_OFFSET X 0.0" and that is incorrect as well.
[09:27:31] <ctjctj> Poincare: invest in GOOD medical insurance?
[09:27:56] <Poincare> ctjctj: Belgium... I even can smoke or drink myself to almost dead and still insured
[09:29:01] <Poincare> This was with a blade to cut Aluminium, I think I wouldn't be typing now if it was another blade.
[09:30:06] <ctjctj> If the spinning blade touched you and you are here typing then I am very glad for you. You were very very lucky.
[09:30:20] <ctjctj> I know more than a few woodworkers with parts of fingers missing from that same mistake.
[09:30:22] <andypugh> Poincare: You are the target market for: http://youtu.be/E3mzhvMgrLE
[09:30:41] <ctjctj> andypugh: that's the "instant stop" table saws?
[09:30:48] <andypugh> Yes
[09:30:59] <r00t4rd3d> who can make the tabs bigger?
[09:31:00] <r00t4rd3d> http://www.cnczone.com/forums/attachment.php?attachmentid=152865&d=1329346053
[09:31:07] <r00t4rd3d> its a dxf file
[09:31:36] <ctjctj> I've seen an in person demo of those. Very impressive. And if I remember correctly, you can actually retro fit it to any table saw.
[09:31:45] <Poincare> ctjctj: well, I'm was working with aluminium...
[09:32:05] <ctjctj> r00t4rd3d: have you looked at librecad? or heekscad?
[09:35:10] <JT-Shop> andypugh, that drawing you sent me of the circular part with two connecting arms to the center, do the strain gauges go on top of the arm or on the sides?
[09:35:50] <andypugh> JT-Shop: Top and bottom, in the cutouts.
[09:36:14] <andypugh> When I made one I used lumps of foam stuffed in the hole to hold them.
[09:36:33] <andypugh> The sticky-tape trick in the link is definitely the way to install them.
[09:37:44] <Tom_itx> JT-Shop, cannon firing today?
[09:38:07] <Poincare> hmmm, that sawstop wouldn't help when working with conductive materials
[09:38:15] <JT-Shop> ok, I think that is a viable idea to try and develop, I still need to contact vishay for some advice
[09:38:33] <JT-Shop> Tom_itx, yes, 4 cannons and 2 mortars are going to be firing
[09:38:52] <ctjctj> Poincare: contact them. It might still work when working with conductive materials. I don't remember exactly what the method is.
[09:39:06] <Tom_itx> JT-Shop, get your full video production crew out
[09:40:15] <ctjctj> does the configure flag --enable-simulator disable all real time operations and interfaces?
[09:40:22] <JT-Shop> yea, I hope one of my riding associates will have their movie camera
[09:42:45] <ctjctj> JT-Shop: are you a yankee or a reb?
[09:43:16] <ctjctj> It sounds like you are a re-enactor of the war of northern agression.
[09:44:30] <andypugh> ctjctj: I think enable-simulator allows the code to run on a normal linux kernel without rtai. So, there is no realtime, but the other code doesn't realise that.
[09:45:19] <ctjctj> Well my poor over used desktop is making things now. I want to test our bug fix.
[09:45:58] <JT-Shop> I guess I'm a yankee from King Salmon Island but they were Russian back then so I'm confused
[09:46:27] <ctjctj> *laughs* Ok, you are neither. Those are americanisms.
[09:46:39] <JT-Shop> ctjctj, we just like things that make a satisfying report when lit
[09:46:54] <JT-Shop> or explode your choice
[09:47:28] <ctjctj> I like bomb things. I use to make my own fireworks when I had a space large enough to shoot them.
[09:47:38] <ctjctj> I to like big booms. (not bombs)
[09:48:42] <JT-Shop> glad you reminded me to get the tannerite rocket ready for launch
[09:48:59] <ctjctj> JT-Shop: do you make your own black powder?
[09:49:17] <ctjctj> I think I asked you that last time...
[09:49:20] <JT-Shop> no, it's cheaper to get by the keg
[09:49:51] <ctjctj> JT-Shop: then you are luck. It is way to expensive to buy it by the keg here in the US. (And you need extra permits and crap)
[09:51:15] <JT-Shop> I'm in the USA but not in a communist state
[09:51:16] <andypugh> When did JT-Shop exit the US?
[09:51:33] <ctjctj> I'm overly confused and made an arse of my self by assuming.
[09:51:40] <JT-Shop> it's been a while andypugh
[09:52:04] <JT-Shop> ctjctj, I reside in Swamp East Missouri
[09:52:38] <ctjctj> JT-Shop: Coolness. My parents live out there.
[09:53:07] <JT-Shop> if it wasn't for ticks and chiggers it would be paradise
[09:53:49] <ctjctj> *nods* I'm out in NH. ticks, and 3 oz miscettos(sp).
[09:53:58] <JT-Shop> I get my powder from Union City TN at Dixie Gun Works
[09:54:41] <JT-Shop> only the flat grounders have mosquitoes around here
[09:55:38] <ctjctj> Interesting. I couldn't find a place selling BP for less than $15/pound before hasmat shipping. I was making my own for around $5/pound or a bit less.
[09:56:02] <ctjctj> and my dyslexia is kicking in badly. s/hasmat/hazmat/
[09:57:05] <JT-Shop> yea, they won't even ship it you have to go and pick it up
[09:57:47] <JT-Shop> can you make F or is it a random size?
[09:58:09] <ctjctj> Yeah, F is no problem. You make pucks, crack them and then sift.
[09:59:01] <JT-Shop> you got a recipe you care to share?
[09:59:02] <ctjctj> You can then take those that are two small and reprocess them into pucks.
[09:59:13] <JT-Shop> ah ok
[09:59:42] <ctjctj> JT-I have lots of BP info. private message me with an e-mail.
[10:00:17] <Tom_itx> aww
[10:04:38] <Tom_itx> if you put subroutines in your main code file do they need to be listed above your main code?
[10:04:45] <JT-Shop> yes
[10:04:56] <Tom_itx> is it better to put them in separate files?
[10:05:15] <Tom_itx> how do you call them passing parameters to them?
[10:05:26] <Tom_itx> i'm reading the html currently
[10:06:03] <JT-Shop> o<mysub> [1] [2] [3] etc
[10:06:36] <JT-Shop> it doesn't matter where you put them but separate files does make housekeeping easier
[10:06:51] <Tom_itx> then in the sub [1][2][3] get replaced with #1 #2 #3?
[10:07:07] <Tom_itx> or are the numbers passed in order
[10:07:26] <Tom_itx> so if you want 2 you use #2 even if it's a 3 for example
[10:07:32] <Tom_itx> order of parameters passed
[10:08:58] <JT-Shop> the first parameter passed will be #1, the second one is #2 etc
[10:09:10] <Tom_itx> yeah
[10:09:22] <Tom_itx> so you can skip one if it's not used
[10:09:35] <Tom_itx> was thinking about making a general purpose template
[10:09:59] <JT-Shop> [123] [345] [456] make #1 = 123 and #2 = 345 and #3 = 456
[10:10:24] <Tom_itx> how would you write the #1 back to a memory location like G54 offset
[10:10:35] <Tom_itx> yes
[10:11:27] <Tom_itx> ie g54 x = 5221
[10:11:34] <Tom_itx> y = 5222
[10:11:48] <Tom_itx> in the table
[10:12:06] <JT-Shop> #5221 = #1
[10:12:14] <Tom_itx> that easy?
[10:12:16] <Tom_itx> :)
[10:12:18] <JT-Shop> yea
[10:12:27] <Tom_itx> so you could mod them on the fly
[10:12:40] <JT-Shop> yea
[10:12:42] <Tom_itx> do some math on #1 then store it again
[10:13:04] <Tom_itx> #1 = (#1+1)
[10:13:06] <Tom_itx> like that?
[10:13:45] <JT-Shop> no, #1 = [#1=1]
[10:13:48] <JT-Shop> +
[10:13:57] <Tom_itx> or another var if you wanted to pass the offset like: #1 = (#1 + #2)
[10:14:03] <JT-Shop> #1 = [#1+1]
[10:14:05] <Tom_itx> ok
[10:14:10] <Tom_itx> brackets instead
[10:14:14] <JT-Shop> yea
[10:14:20] <Tom_itx> but you can add vars
[10:14:37] <Tom_itx> rather do math on vars
[10:14:50] <JT-Shop> aye
[10:15:15] <Tom_itx> so in effect i could do #5221 = [#5221 + #1]
[10:15:23] <JT-Shop> http://linuxcnc.org/docs/html/gcode/overview.html#sec:Expressions
[10:15:35] <Tom_itx> that may be what i was looking for :)
[10:15:38] <JT-Shop> read those 3 paragraphs
[10:15:57] <Tom_itx> yeah, thanks
[10:16:01] <JT-Shop> np
[10:16:51] <Tom_itx> so the sub parameters need to be within the range of 1 to 30
[10:18:32] <JT-Shop> yes
[10:18:48] <JT-Shop> for the ones you pass to a sub
[10:19:08] <Tom_itx> if you use named parameters to they automatically take the next available number?
[10:19:21] <Tom_itx> it seems easier to use named oens
[10:19:24] <Tom_itx> ones*
[10:20:39] <Tom_itx> if you use a named parameter do you need to use the name inside the sub or it's placeholder nubmer i guess would be the question
[10:25:06] <gene_> jepler: ??
[10:25:54] <JT-Shop> Tom_itx, can you rephrase that question?
[10:26:05] <Tom_itx> i'll give you an example
[10:26:09] <JT-Shop> ok
[10:27:33] <Tom_itx> o100 call [#<x_offset>] [#<y_offset>]
[10:27:41] <Tom_itx> then inside the sub:
[10:28:02] <gene_> JT-Shop: Whats the temps there? I'm approaching well done here..
[10:28:07] <Tom_itx> would i use #1 #2 or: #<x_offset> #<y_offset>
[10:28:25] <Tom_itx> i think the former
[10:29:20] <JT-Shop> Tom_itx, [#<x_offset>] will be passed to #1 in your sub
[10:29:29] <Tom_itx> ok that's what i thought
[10:29:33] <JT-Shop> gene_, it is only 88F here atm
[10:29:57] <JT-Shop> with a predicted high of 102F
[10:30:20] <archivist> Tom_itx, see http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Named_Parameters note the leading _
[10:30:22] <gene_> Tom-itx: you can use either, or you could use them direct with the global format, #<_x_offset> etc, but if modified they won't revert at the end of the sub
[10:31:00] <Tom_itx> the double underscore needed?
[10:31:04] <Tom_itx> in the sub
[10:31:28] <gene_> Yes, AFAIK
[10:31:45] <Tom_itx> k, i know some languages are that way
[10:32:07] <gene_> 95 here John, projected to hit 105-109 before the day is out.
[10:32:21] <Tom_itx> so it actually becomes a local var to the sub by reference?
[10:32:21] <archivist> the leading _ means global I think others I only see one _ that matters
[10:32:32] <Tom_itx> (pointer)
[10:33:01] <Tom_itx> i can test the behavior
[10:33:40] * archivist stabs dead links
[10:33:48] <Tom_itx> i'm just trying to figgr out the rules right now
[10:34:15] <Tom_itx> then i'll try to bend em :)
[10:35:34] <gene_> Same here, and while I can't recall the details, I do recall finding a situation a month back where I had to go back to the old way to make it work as expected.
[10:36:09] <gene_> Bend 'em? Nah, just plain break em to see what happens. :)
[10:36:18] <Tom_itx> heh
[10:36:48] <gene_> as long as you don't break the machinery...
[10:36:58] <Tom_itx> i cut air when testing
[10:37:30] <gene_> Yup, many inches above the table, or even with motor power off.
[10:38:28] <gene_> Has anyone come up with a better way to calibrate a lathe except make a cut, measure and touch off?
[10:39:07] <Tom_itx> i was trying to remember how we did it on the little okuma kadet we had
[10:39:45] <Tom_itx> it had soft limits which was nice until you needed to cut .001 past them
[10:39:59] <Tom_itx> to avoid hitting the spindle etc
[10:41:21] <Tom_itx> i still have the pocket reference for it here somewhere
[10:41:40] <gene_> I keep dreaming of a flip-up on the back of the cross-slide carrying a contact for a G38.2 move as one way since the 53xx vars are available after that.
[10:42:34] <Tom_itx> on the old manual multi spindles we had a height gage we used to set the tooling for spindle center
[10:42:54] <gene_> Problem is in getting the contact surface, a piece of pcb, z axis aligned.
[10:43:06] <Tom_itx> yeah
[10:43:34] <Tom_itx> i got a .1" gage block to use for one but haven't had the heart to use it for that yet
[10:43:58] <gene_> Pursuant to that, another piece of pcb to set tool height with, but thats manual, darnit.
[10:45:01] <Tom_itx> i can't remember but the okuma may have had a height block for that as well
[10:45:03] <Tom_itx> for tool center
[10:46:27] <Tom_itx> done once on job setup then from then on it was just a matter of chaning inserts
[10:46:40] <Tom_itx> changing*
[10:46:48] <gene_> I hadn't thought of that idea, gettin slow in my dotage I guess. Its a good idea I do believe.
[10:47:32] <Tom_itx> set off the cross slide or tool post
[10:48:45] <gene_> Yep. For me its a right PIMA to spend longer than the job takes to get all that set so if I want a section .371" in diameter and cut .504" long, its more often a set a hair big, run, trim & rerun.
[10:49:19] <gene_> Nice cuts,way better than by hand but time consuming to tune.
[10:50:14] <gene_> Toy lathe, a 10+ year old speedway 7x12. :(
[10:50:36] <Tom_itx> the center to slide height should never change and if it does you got bigger problems
[10:50:43] <archivist> I use a trial cut that is over size to set, so can use the same metal
[10:50:56] <gene_> Yep
[10:51:22] <gene_> Is Jeff Epler about?
[10:54:14] <gene_> Well, I have a QC post & changing tool holders changes the tool height. I have 2 cutoff blade holders, one set to cutoff with just the blades normal rake, and one set about 3/32 higher because it has the single tooth thread profile on the end.
[10:54:59] <Tom_itx> a universal height gage would be ideal for that
[10:56:12] <Tom_itx> something like a 'Z' with a ground off bolt in the upper part of the Z for initial height adjustment
[10:56:24] <gene_> Once the holder is in the ballpark it seems to stay well though. I have one of those but it is actually too big to set on the back of the cross-slide well. 6" tall, usual dial caliper with carbide jaws
[10:56:28] <archivist> I thought the whole point of a qc changer was maintaining the correct height
[10:56:37] <Tom_itx> heh
[10:56:58] <gene_> It is, but I'm still 'tweaking', new kit.
[10:57:21] <archivist> mine seems to be ok even if chinese
[10:57:22] <ctjctj> andypugh: Ok. I located another but in emcrsh.cc in getPosOffset there is a switch (s[0]). This leads to a problem where "get pos_offset X" returns the correct answer. "get pos_offset x" returns 0.0; In addition all other commands use "0..9" to identify joints but get pos_offset uses letters. Two fixes required. the switch needs a "default" that returns an error and the case 'X': needs a following case 'x':
[10:57:29] <Tom_itx> ie, you take the cutoff blade out of it's holder to sharpen it you need to reset it
[11:00:28] <gene_> That too. For the threading tooth, I fix it in a rotary table sitting abouit 7 degrees nose up on the mill, & polish to shape with a dremel diamond disk in the spindle, moving the table left or right to get the 60 degree side angle.
[11:00:57] <gene_> If I can see the front flat, is almost too wide!
[11:02:09] <gene_> table=rotary table of course...
[11:03:03] <r00t4rd3d> i hate all cad programs
[11:03:42] <gene_> So far it has cut the 1/4x28 threads for several 209 nipples for one of my BP front loaders.
[11:03:45] <ctjctj> r00t4rd3d: *grins* me too.
[11:06:19] <gene_> I think freecad might be ok, but for an old fart 'Merican' I can't seem to adapt to its metric only working format. My fault, or should blame that on the gas stations who screwed the moose back in the '70's?
[11:07:36] <r00t4rd3d> librecad is okay , i got it to do what i wanted.
[11:07:55] <r00t4rd3d> and a lot of fighting
[11:08:02] <r00t4rd3d> and/after
[11:08:04] <gene_> URL handy?
[11:08:14] <ctjctj> librecad is based on qcad. Read the qcad documents and tutorials for help.
[11:08:59] <r00t4rd3d> I might just dive into Blender
[11:09:07] <gene_> Ahh, and no output format that can be xlated to gcode, so I gave up on qcad.
[11:09:48] <gene_> Heekscad/Heekscnc had promise but Dan is sending folks to freecad now.
[11:10:05] <ctjctj> Which means we still need a CAM solution.
[11:10:30] <gene_> Right, and no volunteers in sight...
[11:11:05] <archivist> some idiots are playing with APT
[11:11:08] <ctjctj> gene_: I'm writing it in java. Just got back burnered because of learning git and the fact that there are no "current" dxf java libraries.
[11:11:50] <ctjctj> I had profiles working for dxf files and when I did the change to git and upgraded to kajeba version everything broke due to dependencies.
[11:12:09] <gene_> I was rather pleased that pcb2gcode worked with eagle, quite well after I'd written some more helpers to calibrate the mill.
[11:13:15] <ctjctj> andypugh: You still here? Is there going to be problems with using standard c-library file system calls (fopen, fread, fclose) in emcrsh?
[11:13:26] <gene_> Thats great ctjctl. By current, I always thought .jars were forward compatible though?
[11:14:08] <ctjctj> The problem is that dependency A requires dependency B which requires C D E and F and D E and F are all dead projects without good jars.
[11:14:31] <gene_> Uurrgh
[11:14:58] <gene_> Been there, done that.
[11:15:15] <ctjctj> It is actually worse than that as D, E and F are inter related and also have references to dead projects.
[11:15:31] <ctjctj> So "current" to me means "requires no dead projects"
[11:16:48] <gene_> That is why I downloaded the latest rtai kit this morning, but it doesn't mention in the docs I've read so far, if there is a cutoff point when updating the kernel under it.
[11:17:13] <ctjctj> Yeah, is RTAI a dead project?
[11:17:39] <JT-Shop> a simple 2-d cam for linux would be the berries... I keep thinking about writing one
[11:18:11] <gene_> That def of current is _very_ restrictive. Dunno, what I pulled this morning is Feb 2012 release.
[11:19:23] <gene_> Or the cats meow. 2d is all we need for a lathe.
[11:19:25] <ctjctj> My code handles nesting of rectangles, setting processes for profiles (in, out, on), climbing, conventional, pass depth, tool tables. And it generates ok paths. I've not done any optimizing of rapids.
[11:20:11] <Tom_itx> ncgui won't handle most lathe needs?
[11:20:17] <Tom_itx> ngcgui
[11:20:56] <gene_> Tool tables in linuxcnc is a sore point, there seems to be 2 formats, both poorly documented...
[11:21:08] <ctjctj> I'm having problems with gui design issues. Like "How do I draw a conventional cut?" and stupid things like that.
[11:21:54] <gene_> I haven't looked at it. Is it part of the distro now ? (I'm on 2.5)
[11:22:38] <JT-Shop> gene_, hurts my feelings now
[11:22:40] <ctjctj> gene_: what are you refering to as "it"?
[11:22:55] <gene_> ngcgui
[11:23:02] <JT-Shop> Tom_itx, ngcgui handles 95% of my lathe needs
[11:23:47] <JT-Shop> "it" will even do profiles...
[11:23:51] <gene_> Didn't mean to John, but if its better than axis I'll switch that machine to it
[11:24:17] <JT-Shop> Tool tables in linuxcnc is a sore point, there seems to be 2 formats, both poorly documented...
[11:24:28] <JT-Shop> http://linuxcnc.org/docs/html/gcode/tool_compensation.html#_tool_table_a_id_sec_tool_table_a
[11:24:37] <gene_> there is an echo in here :)
[11:24:43] <JT-Shop> gene_, ngcgui is an add on to Axis
[11:24:49] <archivist> tool table limits is silly just send changes, removes limit
[11:25:35] <gene_> Ok, how do I add it?
[11:26:54] <gene_> I just logged into that box, ready
[11:27:17] <Tom_itx> it must be really easy if i can do it
[11:32:17] <gene_> Found the setup on the wiki...
[11:35:08] <ctjctj> Ok, who/what/how do I send in a patch? I've made some mods to linuxcncrsh and its man page that I would like evaluated (and accepted. *GRIN*)
[11:35:15] <ctjctj> Oh, and tested it.
[11:43:14] <gene_> Problem John, my 2.5 install doesn't have the nc_files/ngcgui_lib tree. Now what?
[11:43:54] <ctjctj> gene_: It is buried in the /usr/share/ area. It has to be put in the right places. Which is not documented (well)
[11:44:08] <jdh> woohoo... I have 24,000 BTUs of cooling to stick in my garage.
[11:44:25] <ctjctj> And do you have power to run it?
[11:44:33] <ctjctj> locate ngcgui_lib
[11:44:41] <jdh> yeah, I'm going to plug it in to my compressor outlet
[11:45:25] <ctjctj> /usr/share/linuxcnc/ncfiles/ngcgui_lib needs to be linked in $HOME/linuxcnc/nc_files (I think I go that right)
[11:45:29] <JT-Shop> gene_, just create a sample ngcgui config and like magic they are there but locked for some strange reason
[11:45:32] <jdh> after I make my extension cord
[11:46:31] <JT-Shop> gene_, have you seen all the lathe subs for ngcgui on my web site?
[11:46:45] <ctjctj> jdh: My shop has great power. 15 amps from the house and 10,000 watts from the generator.... :-( Sometime soon I'll spend money to run a real cable from the power panel in the basement to to the power panel in the shop.
[11:47:50] <Tom_itx> i ran a line off a 50A breaker out to the garage
[11:48:02] <Tom_itx> has been adequate for years now
[11:48:38] <jdh> I'd like to be able to run the compressor and the A/C, but I'd have to run a new line from the main panel
[11:49:21] <ctjctj> Tom_itx: I have to do that, but it is a 50+ foot run and that part of the house is a UGLY crawlspace (left over bolders, left over fiberglass insulation and who knows what else.) So I've not put it high enough on the priority list. Plus my lady always has something else for me to fix/do with my money.
[11:49:40] <JT-Shop> gene_, also beware that the subs in the ngcgui are complicated and depend on helper subs
[11:50:30] * JT-Shop things gene_ wandered away
[11:50:45] <gene_> Yep, moving stuffs
[11:51:09] <ctjctj> Again: How do I contribute patches/mods?
[11:51:57] <archivist> ctjctj, a message on the dev mailing list
[11:54:10] <gene_> Humm, got stuffs missing yet, startup advisories.
[11:54:24] <gene_> simp.ngc for instance
[11:55:41] <gene_> Looks like I need to convert the paths in RS274 to ~/ based. BRB.
[11:56:14] <JT-Shop> ctjctj, you can make a git patch and submit it to the developers mailing list
[11:56:17] <ctjctj> archivist: I'm not on that list, will you please let me know if you see that patch/mod go through.
[11:56:51] <Tom_itx> or ask in -dev
[11:56:54] <ctjctj> grr, bounced as I'm not on the list.
[11:57:35] <Tom_itx>  /j #linuxcnc-devel and ask
[11:58:38] <ctjctj> Tom_itx: thank you.
[12:01:52] <gene_> Ahh, had to make ALL the paths in the ini file absolute, but I believe its working, as in running without any startup errors now.
[12:02:10] <JT-Shop> YEA
[12:07:13] <gene_> That huge DRO is neat, as are the G54 offsets. I'll have to explore the rest of it in person. I ran it without any motor power enabled from here. Thank you John.
[12:08:48] <JT-Shop> np gene_
[12:09:18] <gene_> I think the path problems are because I was doing a 'linuxcnc -l' from the login screen and wasn't sitting in my ~/gene directory. No biggie since I am the only user anyway.
[12:12:33] * JT-Shop wanders in for a nap
[12:18:56] <gene_> Mmm, nap, sounds good. 99F here at 13:05 local
[12:56:14] <Jymmm> Tom_itx: no
[12:56:43] <_abc_> 99F where?
[12:56:47] <_abc_> I have 87 or si
[12:56:50] <_abc_> *so
[12:57:31] <_abc_> Can someone point me to a web paper wrt G54 and so on offsets?
[12:57:48] <_abc_> I have been using cnc machines for a while, but I never had to go deep into such details
[12:58:03] <ctjctj> _abc_: it is in the linuxcnc users manual.
[12:58:20] <_abc_> I have read that, I would like to see a more extensive discussion heh
[12:58:52] <Jymmm> _abc_: Here ya go then, https://www.google.com/search?q=g54+site%3Alinuxcnc.org
[12:59:02] <_abc_> :)
[12:59:45] <Jymmm> _abc_: 12,400 results for G54, now you are on your own!
[13:00:40] <ctjctj> _abc_: do you understand abs or machine coordinate system?
[13:00:50] <_abc_> abs?
[13:00:56] <ctjctj> absolute
[13:00:57] <_abc_> Sure I understand, I write gcode by hand and so on
[13:01:06] <_abc_> It's about when to choose which one and all that
[13:01:13] <_abc_> That's what I would like to see discussed
[13:01:20] <ctjctj> Ok. G5x is an offset to the machine/absolute coordinate system.
[13:01:37] <_abc_> Jymmm: on my g'search there are only 12k results :)
[13:01:53] <ctjctj> abs coordinate = relative coordinate - g5x offset.
[13:01:55] <Jymmm> About 12,400 results (0.36 seconds)
[13:02:15] <ctjctj> and we complicate that with G92. But it really is pretty simple. *GRIN*
[13:02:15] <Jymmm> _abc_: Now, go read them all!
[13:02:37] <_abc_> http://www.linuxcnc.org/docs/devel/html/gcode/coordinates.html this is a better start (but I already read it)
[13:03:07] <ctjctj> _abc_: I'm having a hard time understanding what you don't understand so I can't give references.
[13:03:14] <_abc_> meh
[13:03:15] <Jymmm> _abc_: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?action=browse&id=CoordinateSystems&revision=10
[13:03:19] <_abc_> Give me a second
[13:03:39] <ctjctj> My simple answer is "It's an affine transformation." *GRIN*
[13:04:11] <Jymmm> _abc_: that last link has explainations and illustrations,
[13:05:52] <_abc_> Let's assume an example: One has a large work table, 3 fixed station positions on it, for example for tool change or realignment (manual!), and 3 pieces of work. I need to address the 3 fixed places in G53 absolute, and then go to the previously touched off 3 work pieces and run their relevant files (for the same tool). I will probably glue the gcode for the 2 pieces of work into one file, add the between-parts realignment/tool cleaning station ...
[13:05:58] <_abc_> ... trips, start the job and wander off with a cup of coffee. This is just suppose.
[13:06:09] <_abc_> And yes affine transforms are fine
[13:06:13] <_abc_> forward and reverse
[13:06:27] <_abc_> So the absolute stations fixed on the table are all in G53
[13:06:57] <_abc_> The 3 work pieces are in, I assume, G54-G59.3
[13:07:11] <_abc_> So can I just put all this in the gcode file and expect axis to like it?
[13:07:29] <ctjctj> The three work pieces are likely in a G54 location. And then for each piece you set a G92 offset from the G54 offset and re run the code.
[13:07:33] <_abc_> Navigate to the touchoff points in G53? Or how?
[13:07:49] <_abc_> ctjctj: by hand or can I can it? That is the question?
[13:08:01] <_abc_> As in, can I switch between coordinate modes at any time and back?
[13:08:22] <ctjctj> You can switch between all coordinate modes EXCEPT for absolute/machine.
[13:08:29] <_abc_> (add to this that the work for each piece is coded in absolute mode usually - I can recode it in relative but usually I would like not to do that)
[13:08:50] <ctjctj> So the method is to reserve one of the G5x codes to have offsets of zero. Which means it now matches absolute.
[13:09:04] <_abc_> And Inever use G53?
[13:09:30] <ctjctj> I don't use G53 in programs but do use it by hand.
[13:10:13] <ctjctj> So in your canned program you would set up G59 (example) to have an offset of 0,0,0. Then you go to your fixed location while in G59 mode. Do what you need to do at those stations.
[13:10:38] <ctjctj> Then switch to G54 (example) which has been touched of to a known location of the work pieces one.
[13:10:41] <_abc_> Let's get this straight, if I use G54 to set a touched off position, then the code after it written in absolute mode will stay in that place, right?
[13:11:02] <_abc_> I mean use the G54 set zeros as its 'absolute' zeros?
[13:11:03] <ctjctj> _abc_: rephrase the question please.
[13:11:45] <ctjctj> Except that the default is that G54 is our normal mode for cutting. So we'd use a different G5X coordinate system to reduce the confusion.
[13:12:35] <ctjctj> process: record abs location for fixed-1, fixed-2, fixed-3. Jog/run code to locate the Zero location for your Work piece-1.
[13:12:52] <_abc_> referring to: http://www.linuxcnc.org/docs/devel/html/gcode/coordinates.html if I store the G54's values in the relevant variables and then invoke G54 and after that G0 Z-0.5 // G1 X10.0 then I get a line at the G54 coded 'zero', of length 10 in X, right?
[13:13:07] <ctjctj> touch off and set G54 to that zero location for work piece-1
[13:13:12] <_abc_> I see
[13:13:28] <_abc_> Yes I usually do it by hand for each touchoff which implies G54 I think.
[13:14:01] <ctjctj> Ok. Record the offsets from work piece 1 to work piece 2 and work piece-1 to work piece-3 (called fixtures)
[13:14:19] <_abc_> yes, ok. That is more or less what I do.
[13:14:37] <_abc_> Except for now I do it by hand (Shift-Home I think)
[13:14:41] <_abc_> for each axis
[13:15:34] <ctjctj> so your code no looks something like: G59 to all zeros and switch to it.. use rapid to fixed-1 and do stuff. rapid to fixed-2 and do stuff, rapid to fixed-3 and do stuff. Now switch to g54 and set g92 to zero. Rapid to work piece-1 (g0x0y0) run code to cut work piece-1
[13:16:07] <ctjctj> set g92 to the offset from work piece-1 to work-piece-2. Rerun your program to cut work piece-2.
[13:16:28] <ctjctj> set g92 to offset from work piece-1 to work piece-3 and re run to cut work piece-3.
[13:16:32] <ctjctj> Done.
[13:17:14] <ctjctj> Now there are lots of things you can do with a G53 but the issue comes with such stupid things as g38 probes don't allow a G53 prefix.
[13:18:07] <ctjctj> stupid is defined as "it doesn't work the way I want it too." *GRIN*
[13:18:10] <ctjctj> Does that help _abc_
[13:18:16] <_abc_> yes, thanks
[13:20:56] <ctjctj> Does anybody know how to force ssh to never prompt for a keyboard password? I just want it to fail if a password is required.
[13:22:14] <jdh> you can remove password imteractive in the config
[13:23:39] <_abc_> ctjctj: see ssh -n and BatchMode option in config
[13:23:53] <Jymmm> ctjctj: -o NumberOfPasswordPrompts
[13:24:06] <Loetmichel> hmmm... how much hdd space is needed fpr a linuxcnc install minimum?
[13:24:09] <ctjctj> -n doesn't do what's required by Jymmm seems to have nailed it.
[13:24:36] <Jymmm> ctjctj: RTFM =)
[13:24:36] <_abc_> BatchMode If set to ``yes'', passphrase/password querying will be disabled. In addition, the ServerAliveInterval and SetupTimeOut options will both be set to 300 seconds by default. This option is use- ful in scripts and other batch jobs where no user is present to supply the password, and where it is desirable to detect a broken network swiftly. The argument must be ``yes'' or ``no''. The
[13:24:43] <_abc_> deault is ``no''.
[13:24:45] <_abc_> ^^
[13:24:48] <ctjctj> Jymmm: I was reading that very find manual.
[13:25:03] <Jymmm> It's FUCKING, not FINE
[13:25:24] <_abc_> this is a ssh option not sshd option. ssh -o BatchMode=yes should work
[13:25:26] <ctjctj> Jymmm: -o NumberOfPasswordPrompts=0 is the actual form but it did what I needed.
[13:25:50] <_abc_> Well that should also force what you need
[13:26:01] <ctjctj> _abc_: and you get a win as well.
[13:26:08] <andypugh> ctjctj: Back now. I guess that you already answered your own questions?
[13:26:50] <ctjctj> andypugh: except that I don't know if it was actually seen in the bedroom (everybody sleeping) known as linuxcnc-devel. I didn't do our g92 fixes because you implied you had a patch for that.
[13:27:56] <_abc_> I find that running linuxcnc via ssh remote X11 session is satisfactory even with a lower end linuxcnc machine
[13:28:05] <andypugh> Not yet, but in 30 mins or so.
[13:28:59] <ctjctj> andypugh: And I'm unsure if we want to fix get pos_offset switch regarding 'X' vs 'x' and or getting it to use integers to identify axis. Or doing all three X,x,0
[13:30:25] <ctjctj> _abc_: That's an option but I need the display in the workshop and I want to monitor progress here in the office. Lazy answer is an IP camera watching the machine and the monitor code running here. I can actually hit the estop from here if I notice something.
[13:30:50] <ctjctj> But more importantly for me is that I don't get paid to watch my machine make chips but I do get paid to program here in the office.
[13:32:00] <ctjctj> being able to know when it is time to load the next program or do the manual tool change is a *good* thing.
[13:34:27] <andypugh> I thought it would be a simple mod to the function atio() but that actualy seems to do something rather different.
[13:34:49] <ctjctj> andypugh: ???
[13:35:14] <andypugh> I was talking about making x X and 0 equivalent
[13:35:36] <ctjctj> ah. No. atoi() is standard libc for ascii to integer.
[13:35:46] <ctjctj> He's translating from a string to an integer.
[13:36:37] <andypugh> So, X isn't accepted? Or is it just that any non-numeric evaluates to zero?
[13:37:36] <ctjctj> In "abs_act_pos" you can request all axis via "abs_act_pos" or you can request just one axis with "abs_act_pos INT" where INT is 0-9.
[13:38:04] <ctjctj> But in "pos_offset" he switched from that format to using X, Y, Z, A, and some others which I don't remember.
[13:38:58] <ctjctj> At the very least I believe that the code should be changed to accept x,y,z,a and the others (lower case version) and I'm asking if we should make it consistent with the other axis selection code to allow it to use integers
[13:42:23] * JT-Shop rubs eyes and looks at the unfinished cannon left to do
[13:42:28] <andypugh> It is all rather ancient and strange anyway, no UVW axes.
[13:42:51] <andypugh> And for some reason accepts R P and W for A B and C
[13:43:00] <ctjctj> Yeah, they used a different set of names.
[13:43:51] <_abc_> In the example at the bottom of http://www.linuxcnc.org/docs/devel/html/gcode/coordinates.html they use G55, G56 etc. But one could simply reuse G55, no?
[13:45:06] <_abc_> I mean use a G10 L2 P2 X... after each section?
[13:45:07] <ctjctj> _abc_: the wonderful thing about unix (gcode) is that there are so many ways to make the same mistakes... Opps to do things.
[13:45:31] <_abc_> agree
[13:45:33] <ctjctj> _abc_: Yes, you can do that. And it is an easy way to do things.
[13:45:50] <_abc_> yes, I will try to teach my gcode writing program some new tricks
[13:46:00] <_abc_> after testing
[13:46:37] <_abc_> My problem is that I am used to an ultra low end router which has no circle interpolation even, and moving to axis is a step up. So many toys...
[13:46:50] <ctjctj> *grins* The thing that I find absolutely amazing is that I use to get pissed when it took more than 5 seconds to test a program I was writing. Now I'll stare at a spindle for hours waiting to see if the program I just wrote is "right"
[13:56:32] <Jymmm> andypugh: http://www.dealextreme.com/p/square-4-pin-speaker-socket-connectors-5-piece-pack-138397
[14:01:15] <andypugh> O can't find any plugs though...
[14:01:37] <Jymmm> Well, half way there at least, maybe, sorta kinda
[14:01:56] <Jymmm> andypugh: Just thought you might be interest is all =)
[14:02:32] <andypugh> I have all that I need at the moment.
[14:03:30] <Tom_itx> you don't like DIN connectors?
[14:05:43] <_abc_> G64 is used when exactly? Also tool compensation is best used when?
[14:10:35] <JT-Shop> _abc_, have you read this? http://linuxcnc.org/docs/html/common/User_Concepts.html
[14:18:18] <_abc_> So G28 and G30 are basically the same?
[14:28:03] <JT-Shop> same but different yes
[14:28:36] <JT-Shop> YEA the last cannon comes together
[14:30:22] <Jymmm> JT-Shop: Who's the beta cannon bitch?
[14:32:44] <Jymmm> JT-Shop: Are these cannons pre-tested before you get them?
[14:33:41] <Tom_itx> they are soon after
[14:34:47] <Jymmm> I'd expect them to be xrayed, then test fired in a secure environment
[14:35:14] <Tom_itx> they probably have a steel sleeve cast in them
[14:35:33] <ctjctj> I forgot to ask JT-Shop do you shot anything but blanks from these cannon?
[14:35:59] <Jymmm> ctjctj: Kinda a personal question don't ya think?
[14:36:51] <ctjctj> You're right Jymmm
[14:36:59] <Jymmm> =)
[14:37:46] <Jymmm> But, since you mentioned it... Will a rim fire fire if the firing pin is center fire?
[14:38:00] <Jymmm> and vise versa?
[14:38:18] <Jymmm> .22lr specifically
[14:38:38] <ctjctj> Jymmm: nope.
[14:38:53] <ctjctj> Or not reliability.
[14:39:18] <Jymmm> so the charge doens't cover the enter bottom, just the edges?
[14:39:27] <Jymmm> or rim if you will
[14:39:33] <ctjctj> Jymmm: there is more to it than just that.
[14:39:56] <Jymmm> ctjctj: I'm listening
[14:40:18] <ctjctj> when the firing pin hits the primer (or rim of a rim fire shell) the primer material is "pinched" between an anvil and the dent made by the firing pin.
[14:40:18] <Jymmm> I read the wikipedia pages already too
[14:40:31] <JT-Shop> ctjctj, my cannon and Ray's are 1 3/4" bore so in addition to tin foil balls and lead balls we can also shoot golf balls
[14:40:50] <ctjctj> If the distance between the anvil and the "dent" are not small enough the primer might not go off.
[14:41:04] <Jymmm> ctjctj: and the anvil being what?
[14:41:09] <ctjctj> When a 22lr is created the base is covered by the primer material but there is only anvil at the edges.
[14:42:08] * _abc_ knows nothing about guns
[14:42:13] <_abc_> what is the lr in 22?
[14:42:16] <ctjctj> http://www.hallowellco.com/primer.htm for pictures of primers
[14:42:20] <ctjctj> long rifle.
[14:43:18] <ctjctj> In a .22lr the anvil is the case itself. So when the firing pin hits it crushes the material between the bottom of the shell casing and the other side of the rim. This makes it go bang.
[14:43:34] <Jymmm> ctjctj: Oh, so the "lip" is the rim fire anvil?
[14:44:04] <ctjctj> On a center fire the primer has the anvil (cup) and the firing pin crushes the primer material between the anvil and the base of the firing cap.
[14:44:11] <ctjctj> Jymmm: yep, the lip is the rim fire anvil.
[14:44:46] <ctjctj> So if you hit a rim fire in the center the shook*MIGHT* cause the primer material to ignite and give you a bang or it might not.
[14:44:57] <Jymmm> ctjctj: Is it possible to have a "firing pin" as a "bar with a dimple" that with reliably fire both types?
[14:45:16] <ctjctj> I.e. it aint safe to hit the center like that.
[14:45:17] <Jymmm> or even a "U" groove?
[14:45:30] <ctjctj> Jymmm: absolutely it is possible. It just isn't reliable.
[14:46:18] <ctjctj> image a two pin system like you are talking about. What happens if it does not apply equal pressure? Or the materials are differnent under the pins. One will get more energy than the other.
[14:46:45] <ctjctj> The only way I've seen that done is to have TWO separate firing pins that act independently.
[14:47:01] <Jymmm> but concurrently
[14:47:27] <ctjctj> A rifle firing pin is "free floating" which means that when the hammer hits the pin it transfers energy to the pin and the momentum of the pin carries that to the primer.
[14:47:52] <ctjctj> Well, for relatively small large values of "concurrently"
[14:47:57] <Jymmm> =)
[14:48:16] <ctjctj> So if you had two firing pins and you hit them both with a hammer it would likely work "correctly" most of the time.
[14:48:24] <Jymmm> ok, nm the dual ting. not that big a deal. Was just thinking of making a zipgun is all
[14:48:24] <ctjctj> Why do you want to do something so silly though?
[14:48:44] <Jymmm> out of SS tubing
[14:48:46] <ctjctj> dual pin is silly. making your own fire arm is not.
[14:49:25] <ctjctj> Jymmm: there are very few rim fire cartridges out there. The .22lr is the only one that is in common use.
[14:49:47] <Jymmm> I also have a 25 that will not fire even though it puts a hell of a dent in the shell. tried different brand ammo too. but that's for another day
[14:50:13] <Jymmm> ctjctj: Yeah, but I was trying to figure out how to make a rim firing pin
[14:50:38] <Jymmm> the whole "offset from center" thing
[14:51:04] <ctjctj> And at this point it is wise for me to say: Making any sort of fire arm is a dangerous thing. It can also open you up to multiple issues with the ATF. In particular most "zip" guns fall into the machine gun category and as such are and invitation for a visit from your local ATF
[14:51:37] <Jymmm> ctjctj: I'm fully aware of that =)
[14:52:06] <Jymmm> ctjctj: http://www.youtube.com/watch?v=yPrnyc03C2Q
[14:52:32] <Jymmm> ctjctj: That's more what I'm intended which *IS* permitted by ATF
[14:53:19] <Jymmm> ctjctj: the problem is that specific flare gun is hard to come by
[14:54:08] <_abc_> what is a zip gun?
[14:54:29] * _abc_ is in Europe and hot shot at with AK47s and tank mounted machine guns during a revolution here a few years ago
[14:54:55] <_abc_> https://en.wikipedia.org/wiki/Hand-Held_Maneuvering_Unit hehe zip gun
[14:56:45] <ctjctj> _abc_: you can make a gun by taking a piece of pipe the right size, putting a cartridge in it. you then screw on a pipe cap. A hole is drilled in the cap to centered over a hole. A pin is placed in that hole. A handle is attached to the pipe. A punch of rubber bands are used to supply spring power to a hammer. You pull back the hammer with your thumb, let go with your thumb, "zip" the hammer flys forward, hits the pin, fires the
[14:56:47] <ctjctj> cartridge and the bullet goes down range at speed.
[14:56:57] <ctjctj> Total cost is around $10-$20.
[14:57:03] <ctjctj> Illegal as hell in the US.
[14:57:17] <_abc_> oh?
[14:57:21] <_abc_> Illegal why?
[14:57:34] <_abc_> The power enfarcement likes to keep track of barrels?
[14:57:39] <_abc_> Or is it dangerous as is?
[14:57:42] <Jymmm> guberment cant track em
[14:57:43] <_abc_> I mean to the shooter
[14:57:44] <ctjctj> Because it is cheap and easy to make so everybody could have one. Therefore our government doesn't want us to have them.
[14:57:55] <_abc_> Ah, makes perfect sense
[14:58:28] <ctjctj> Jymmm: the reason the flare gun adaptor is ATF approved is because of the trigger method of the flair gun.
[14:58:33] * _abc_ wonders if his and other's fooling around with 100bar nitrogen and hose pipes fitted to copper tubing and ball bearings qualifies as zip gunning
[14:58:44] <_abc_> That must have been like 30 years ago
[14:59:03] <ctjctj> Depends on the country you are in.
[14:59:22] <_abc_> I was in a country with a communist dictator who had even typewriters registered and fingerprinted
[14:59:22] <Jymmm> ctjctj: Nah, but the letter gives a detailed description of their decision.
[14:59:37] <_abc_> What do you mean "because of the trigger method?"
[15:00:22] <Jymmm> ctjctj: they went so far as to mill their own adapter and everything as olin (flare gun mfg) bitched about ppl using their cheap plastic flare pistol with the insets =)
[15:00:53] <ctjctj> _abc_: in the US the department of Alcohol, tobacco, firearms, explosives (BATFE) is known as the ATF. They are one of the meanest government agencies.
[15:01:03] <_abc_> I heard about them
[15:01:12] <_abc_> But what about the trigger mechanism you alluded to?
[15:01:13] <Jymmm> ctjctj: Nah, that would be the IRS
[15:01:16] <_abc_> Just curious?
[15:01:23] <_abc_> I thought it was the DHiS
[15:01:45] <ctjctj> So the ATF has ruled that certain types of trigger/firing mechanisms are "bad"
[15:01:52] <_abc_> https://en.wikipedia.org/wiki/Improvised_firearm interesting article
[15:02:12] <_abc_> ctjctj: bad as in, too easy to make and work well, or, bad, as in, they are dangerous to one's fingers
[15:02:19] <ctjctj> For example they ruled that having a shoelace attached to another trigger on a gun made that gun a "machine gun" and
[15:02:28] <_abc_> ?!
[15:03:05] <ctjctj> _abc_: ATF doesn't like cheap guns. Regardless of anything else.... So they claim" dangerous" but it is more political than that.
[15:03:16] <_abc_> I see
[15:03:27] <Jymmm> Heh, I like the maglite zipgun
[15:03:45] <ctjctj> and as a machine gun, not having paid his "stamp tax" the guy with the shoelace went to prison.
[15:03:47] <_abc_> Is this a good time to mention the booby traps used in Vietnam? Such as the wooden plank with hole and cartridge kind? Is that also a 'machine gun' by ATF?
[15:03:52] <Jymmm> I can see using 14400 battery instead of 2xAA's
[15:04:14] <_abc_> Jymmm: If you use Chinese CR123s they will also double as cartridges
[15:04:22] <ctjctj> _abc_: That falls under a different category of forbidden. But it is forbidden.
[15:04:35] <_abc_> They tend to blow up in flashlights and make holes in cupboard doors and the like
[15:04:50] <_abc_> The CR123s
[15:04:59] <Jymmm> ctjctj: The ATF also says that I can't NOT laser engrave firearms without having a gunsmith permit, even if it's just the slide.
[15:05:22] <ctjctj> Jymmm: I hadn't heard that.
[15:05:56] <Jymmm> ctjctj: The only exception being is if the owner never leaves sight of the firearm while it's being engraved.
[15:06:32] <ctjctj> what reason did they give for that one?
[15:06:35] <Jymmm> ctjctj: And yes, they DO check at random.
[15:06:44] <Jymmm> ctjctj: it's the ATF, who knows.
[15:07:02] <andypugh> You know that guy with the old fire-engines I linked to? It turns out he has a CNC lathe too, which he has been thinking of updating to a more modern control than 1985 Anilam.
[15:07:12] <_abc_> So you can surprise the owner with a new serial number or something?
[15:09:45] <archivist> andypugh, the mad doctor?
[15:10:43] <andypugh> He is mad, and has a PhD, but that applies to at least half the people I know :-)
[15:31:03] <_abc_> https://en.wikipedia.org/wiki/Sputter_Gun hah ctjctj
[15:31:15] <_abc_> your ATF is really creative (so are your inventors)
[15:33:46] <archivist> andypugh, striving to be normal I call real madness :)
[15:33:53] <_abc_> http://web.archive.org/web/20040716040536/stenguns.tripod.com/id12.html ...
[15:34:26] <_abc_> "I conceived and built the "sputter gun". My attorney friend named it. ATF
[15:34:27] <_abc_> never gave a written classification on it. It was only stated to me personally by [the late] Chuck Lanam from the Tech Branch when he was at my shop in 1982 looking at all the Sten Guns we were building that he thought my finger would be classified the trigger. He said this I'm sure in order to scare us off in producing the sputter gun.
[15:34:32] <_abc_> very promising
[15:34:38] <_abc_> Anyway let's forget about guns
[15:34:52] <_abc_> What does tool radius compensation ACTUALLY do in axis/linuxcnc?
[15:35:38] <_abc_> Does it have to do with sharp external corners and such?
[15:35:55] <_abc_> I use very small mills for engraving and such, so it has almost never played a role yet
[15:42:10] <andypugh> It moves the axis of the tool left or right of the programmed path, so that the line of cut is the programmed path.
[15:42:52] <_abc_> Ah, so nothing to do with corners.
[15:43:01] <_abc_> That will be the precision setting there only.
[15:43:03] <_abc_> Okay.
[15:44:02] <ctjctj> andypugh: thanks for pushing that patch out there for the cut-paste issue.
[15:51:14] <_abc_> I need to get some books and study cnc machining more
[15:51:24] <_abc_> I am doing other more important things now heh.
[15:55:17] <andypugh> The CNC part is relatively easy. It is important to know about Machining in general though.
[15:57:20] <syyl_ws> i thought cnc is doing all the work? ;)
[16:09:16] <archivist> syyl__, what sudo machine make it for me? :)
[16:13:20] <archivist> some silly addresses were in the wiki /me trawling with a spider eg http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl/emcinfo.pl?BDI-4_38_Compile_EMC2
[16:19:27] <DJ9DJ> gn8
[16:19:55] <pcw_home> Not silly just hystorical
[16:21:12] <archivist> pcw_home, note the double emcinfo.pl
[16:21:59] <archivist> I only found those on one page
[17:02:59] <taiden> hey all
[17:03:10] <taiden> any way to reset active gcodes without restarting linuxcnc?
[17:06:42] <archivist> reset? set a modal state as needed, ones gcode normally has a preamble to set your norms
[17:06:59] <archivist> wait for teh answer!
[17:19:10] <tom3p> did IchGuchLive do his own blender2gcode or did he use yoyo's scripts?
[17:19:55] <tom3p> this refers to recent http://mechmo.de/bild-simba.jpg
[17:21:29] <archivist> looks like heekscnc there
[17:22:17] <gmagno> er... hello, I'm in trouble, my computer just crashed running pycam... I had to hardware reboot the pc but it wouldn't jump to the OS, it keeps restarting over and over again... :-( Just tried to run from an ubuntu live cd but without success. It shows the options, to run from cd, install ubuntu, test memory, etc, but when I choose one of these options I get this command prompt "boot:" Any idea what might be the problem? I'm asking here b
[17:22:18] <gmagno> ecause the operating system the pc runs is a linuxcnc ubuntu
[17:23:43] <gmagno> another thing, after runnung the live cd I first get a message error "Boot loader: /casper/~mlinuz: file not found"
[17:25:19] <tom3p> maybe a problem with cd. Ive recently had probs with several livecds, and had to change the drive. no probes now. not necc your prob but may be your prob :/
[17:27:27] <andypugh> gmagno: Did that particular LiveCD boot the machine previously?
[17:27:52] <gmagno> andypugh, you mean before the crash?
[17:28:12] <andypugh> I mean, has that particular LiveCD booted that machine
[17:28:55] <andypugh> If the LiveCD won't boot it, and the HDD won't boot it, then I would be thinking in terms of hardware faults.
[17:29:04] <gmagno> i see
[17:30:02] <andypugh> Try just one memory stick. Then try a different one. Try re-seating any PCI devices.
[17:30:04] <gmagno> could a hardware reset with the paralel port connected to the driver board (being powered) damage the pc?
[17:30:28] <alex4nder> a hardware reset?
[17:30:37] <gmagno> I mean, pushing the pc reset button
[17:30:37] <andypugh> gmagno: It shouldn't. I am not going to say that it couldn't, but it really shouldn't
[17:31:17] <gmagno> fuc***
[17:31:51] <tom3p> andypugh, i think he used blender to model, and heeks to post using emc2b but i;m wildassguesing some intermediate STL file, well getting booted outta library, by4now
[17:31:55] <gmagno> im worried about the config files... I had a hard time annoying ppl from the channel to help me with that... And have no backup... all I had is in the PC...
[17:32:45] <andypugh> Well, the data on the HDD should still be there.
[17:33:15] <gmagno> unless it is an hdd problem :-/
[17:33:16] <andypugh> Have you tried booting from one of the alternative kernels?
[17:33:38] <andypugh> It can't be _just_ a HDD problem if it won't boot from CD either.
[17:33:44] <gmagno> right
[17:34:17] <andypugh> You might need to hold down the shift key when booting to see the Grub menu and pick an alternative kernel.
[17:34:22] <gmagno> what alternative kernels? I just installed linuxcnc ubuntu. Everytime I powered on pc there was no grub, it just jumped to the OS
[17:34:28] <gmagno> ah
[17:34:29] <gmagno> ok
[17:34:41] <Tuipveus> try system rescue cd
[17:35:07] <andypugh> Try making a bootable USB stick from the LiveCD image.
[17:35:15] <Tuipveus> and take backup of your data as soon you get computer with that harddrive up
[17:35:49] <andypugh> I am assuming that you have an alternative PC, and aren't managing to chat on IRC using a bare ethernet cable and a 9v battery.
[17:35:53] <Tuipveus> gmagno: with ubuntu you can check that cd is ok from the menus... I think it has some checksum in one of those option which you mentioned
[17:37:13] <Tuipveus> http://www.sysresccd.org/Sysresccd-manual-en_How_to_install_SystemRescueCd_on_an_USB-stick
[17:37:43] <Tuipveus> you can also install that one on usb-stick... or even run from over the network, if your lan-card supports booting using pxe
[17:38:12] <gmagno> ok, holding shift does nothing pc keeps restarting all the time.
[17:39:04] <gmagno> bios menu is weird, it has some weird artifacts on gui
[17:39:36] <gmagno> i think i didn't say this but ubuntu livecd menu also has this artifacts
[17:39:50] <gmagno> this is all fuc*** up
[17:40:01] <gmagno> gonna try the flashdisk
[17:40:52] <andypugh> Try swapping out memory first
[17:41:57] <Tuipveus> since you don't know which component is defective, you should take the harddisk to another computer and take backup with that
[17:42:41] <Tuipveus> that would at least ensure that you are not taking broken backups because a) ram is broken, b) disk-controller is broken
[17:43:14] <Tuipveus> I was lucky couple of months ago to restore one computer with ddrescue
[17:43:58] <Tuipveus> that poor laptop had broken harddisk and I asked owner to buy new one, but I was able to recover the data from old one to new, even old didn't boot
[17:44:41] <Tuipveus> according to ddrescue there was 4 kilobytes corrupted data... and after a while I was able to copy 512 bytes of it...
[17:45:10] <Tuipveus> and that 3,5 kilobytes didn't contain any data, so system booted with new harddisk
[17:45:54] <andypugh> Yes, good point, rescuing the data is probably the first priority.
[17:46:02] <Tuipveus> some of the files which were used during the boot tried to use that file with 512 broken bytes... (one sector)
[17:47:01] <Tuipveus> ddrescue is great tool... and if it does not help, you can try to put your harddisk to deep freeze and try ddrescue after that! :)
[17:50:29] <gmagno> :D
[17:51:20] <Tuipveus> I have never needed to go that far though
[17:51:46] <Tuipveus> I am running Debian Linux, with software raid-5
[18:22:21] <Tom_itx> ok something is off on arcs
[18:23:13] <Tom_itx> supposed to cut a .5625 circle and it cut .660
[18:23:37] <andypugh> Tom_itx: G41?
[18:23:49] <Tom_itx> no i think i see why now
[18:24:00] <Tom_itx> i'm not used to diameter in the tool table
[18:24:09] <Tom_itx> i set the z height for the tool but not the diameter
[18:24:36] <Tom_itx> it says it has an .093 endmill and it really had a .187
[18:24:37] <andypugh> I think if it was a general problem we would have more complaints. (though that bug in linuxcncrsh was a couple of years old)
[18:24:48] <Tom_itx> no it was me
[18:24:53] <Tom_itx> it will still work though
[18:25:08] <Tom_itx> should i enter zero for diameter or the actual tool diameter?
[18:25:38] <Tom_itx> it did cut a fairly round circle though after entering the backlash comp
[18:25:53] <andypugh> Actual tool diameter. But it is ignored ig you don't use diameter compensation. You get a better preview with the right diameter though.
[18:26:06] <Tom_itx> i don't think i had comp on but i'm not sure
[18:26:13] <Tom_itx> i'll fix the tool table
[18:26:43] <Tom_itx> i'll match it with my cad cam tool setup so i don't need to enter T1 for each tool rather the actual tool spit out by the cam
[18:26:53] <Tom_itx> just details i haven't done yet
[18:29:44] <Tom_itx> G40 is active
[18:29:47] <Tom_itx> comp off
[18:29:52] <Tom_itx> so i dunno what's up
[18:29:57] <djdelorie> anyone feel like helping me tune a current loop?
[18:30:02] <Tom_itx> i know to enter the diameters now though
[18:31:12] <pcw_home> What tune do you want it to play?
[18:32:10] <djdelorie> "beep" would be nice
[18:32:14] <djdelorie> see http://www.delorie.com/electronics/bldc/iloop-1.png
[18:33:16] <djdelorie> the step response is based on v = L dI/dt and gets it to the target current pretty easily, but it doesn't seem to be able to track it after that
[18:33:36] <Tom_itx> andypugh shouldn't it ignore the table if G40 is in effect?
[18:33:38] <pcw_home> Do you have an I term
[18:33:44] <djdelorie> I'm trying to figure out which of the many constants I have needs to be used to compensate
[18:34:21] <djdelorie> I don't have "pid" at all yet, I'm using a motor model. At the moment, I'm wondering - when compensating for back-EMF, do I use the actual current, or the actual RPM?
[18:34:36] <andypugh> Tom_itx: Yes, it should.
[18:34:40] <djdelorie> or should I dump the motor model and use a plain PID ?
[18:34:53] <djdelorie> I have all these lovely constants to use, shame to not use them ;-)
[18:35:03] <Tom_itx> it didn't cut the exact toolpath then
[18:35:10] <andypugh> PID is rather limited.
[18:35:11] <Tom_itx> it read from the table
[18:35:22] <pcw_home> I would start with PI and then add FF1 (your BEMF comp)
[18:35:23] <andypugh> Wierd
[18:35:30] <Tom_itx> because that's about how much it was off
[18:35:42] <djdelorie> I mean, I know the K for the motor (volts/rpm) and winding inductance and resistance
[18:35:43] <Tom_itx> G40 doesn't appear to work
[18:36:09] <pcw_home> Yes but you still need feeedback
[18:36:21] <djdelorie> but the "coil" is a rotating field too (you can see it in the waviness in the chart; it goes one revolution before switching
[18:37:24] <pcw_home> The motor inductance may change by a factor of 2 depending on rotor stator alignment, you _need_ feedback
[18:37:33] <djdelorie> so... figure P based on motor constants, and pull in I/D from elsewhere?
[18:37:41] <pcw_home> no D
[18:37:50] <djdelorie> ok, D is zero :-)
[18:38:48] <djdelorie> actually, I have an I term... let me disable it and see what happens
[18:38:59] <pcw_home> typica;l FOC uses just PI (as the motor inductance is a almost perfect first order system)
[18:39:18] <djdelorie> I think it's disabled anyway, it's a position I not a current I
[18:40:05] <pcw_home> Are you doing the normal Park/Clarke stuff?
[18:40:20] <djdelorie> no
[18:40:35] <djdelorie> like I said, I was going with a "motor model"
[18:40:45] <pcw_home> ahh Thats what I am familiar with
[18:41:00] <djdelorie> I know the desired and actual current, and based on that, I apply a voltage to the coils to change the current
[18:41:41] <djdelorie> except by "voltage" I mean PWM
[18:41:56] <pcw_home> Right (thats P)
[18:41:57] <djdelorie> and it's three-phase, with the sin/cos stuff buried beneath this layer. That might be a mistake, thugh
[18:42:07] <djdelorie> I might need to PID each coil separately
[18:42:45] <andypugh> Sounds like you might need a motor-speed dependent P.
[18:43:17] <djdelorie> right, which would be the Ka for the motor, or the winding resistance, or one of the other of several constants I have
[18:43:45] <pcw_home> Thats what the transforms are all about (transforming the measured currents into a non-rotating frame of reference and back) so you only need 2 PID loops to keep both the current and drive angle correct
[18:44:10] <djdelorie> I *do* have an FF1 for RPM to close the following lag, though, but it's at a higher level
[18:44:30] <djdelorie> I should have the drive angle right, I'm using the encoder to measure that precisely
[18:44:51] <djdelorie> I assume you're talking about the drive torque, to hold/follow position?
[18:44:54] <pcw_home> The drive angle lags because of inductance
[18:45:54] <djdelorie> I haven't noticed any lag in the current, is that an indicator?
[18:46:02] <pcw_home> thats what FOC (field oriented control) is all about keeping the drive angle +-90 from the rotor position
[18:47:16] <pcw_home> Its only a problem at higher speeds (since VBUS -VBEMF/L gets small)
[18:47:38] <pcw_home> so di/dt gets small
[18:47:41] <djdelorie> hmm... maybe I should apply the sin/cos stuff to the three current measurements, instead of just +1/-1 signs?
[18:48:21] <djdelorie> I think at one time I had an rpm-dependent term to compensate for that at one time. I'm currently (sic) working on the slow speed and holding conditions
[18:48:29] <djdelorie> the motors vibrate when they should be "still"
[18:48:49] <andypugh> Are they connected to the machine?
[18:49:06] <andypugh> It is known to be difficult to tune a bare motor.
[18:49:08] <djdelorie> a local CNC guy told me I had to tune from the inner loop out, so I'm just looking at current, turns out the current loop just wasn't working
[18:49:22] <djdelorie> it's a test rig on my desk. It's conncted to *something* but it's not the CNC machine
[18:49:47] <djdelorie> basically, I'm trying to figure out *how* to tune the motor, get the software written correctly, then go tune the CNC machine
[18:50:04] <djdelorie> (remember, I'm building my own controllers :)
[18:51:13] <djdelorie> the "test rig" is a 3/8-16 screw rod driving a 2.5 lb weight back and forth
[18:51:32] <pcw_home> Well I would first try a PI loop on the current (then take a look at standard FOC)
[18:51:34] <pcw_home> If I look at your plots they say too low P term in your current feedback to me
[18:52:31] <djdelorie> yeah, I agree with that part, I'm just trying to figure out *why*
[18:52:36] <andypugh> The PID controller I am working with at the moment has precontrol, P I and D. all the terms are the product of two 8x8 maps (except for I which is the product of 3 8x8 maps) with inputs for temperature, demand pressure, pressure error, pump speed and rate of change of setpoint. Simple PID is sometimes not nearly enough.
[18:53:07] <djdelorie> I haven't even begun to worry about the position loop :-)
[18:53:20] <pcw_home> Yeah bit current in an inductor is a simpler "plant"
[18:53:30] <pcw_home> s/bit/but/
[18:53:41] <djdelorie> if it's ONE inductor, sure. three rotating ones is not as simple
[18:54:00] <andypugh> And when I get it wrong, the engine siezes. Software controlled oil-pump. Oh dear.
[18:54:16] <pcw_home> (ignoring for the moment the fact the inductance varies with position)
[18:54:33] <djdelorie> reminds me of a story my dad tells. "What does that switch do?" "It tells the computer to shut off the engine." "Ah. Take it out."
[18:55:06] <andypugh> djdelorie: PCWs motor controllers work.
[18:55:21] <djdelorie> mine works too. It just works badly
[18:55:34] <djdelorie> (relative to what it *should* be doing)
[18:55:52] <andypugh> Even I can make one that works badly :-)
[18:55:52] <pcw_home> We just went the standard way (Park/Clark FOC)
[18:56:14] <andypugh> (Although mine worked badly and briefly)
[18:57:17] <andypugh> I always felt that the Park/Clark transform would be important to the bldc component, but in the end it appeared to be irrelevant.
[18:58:49] <pcw_home> Its important for FOC but voltage plain old voltage mode works pretty darned well
[18:59:50] <pcw_home> we will eventually add voltage mode (with current limit) to the 8I20 for induction motors
[19:00:15] <djdelorie> I assume that when you're trying to hold a BLDC motor to 0.09 degree, getting the angles right is important? ;-)
[19:00:55] <pcw_home> No actually but when you are spinning a spindle at 6000 RPM and want full power it is
[19:01:18] <djdelorie> that too :-)
[19:02:17] <pcw_home> when moving slow your drive current and voltage will be nearly in phase (sin you only have a few Hz three phase freq
[19:02:19] <pcw_home> and no BEMF
[19:02:29] <pcw_home> s/sin/since/
[19:02:46] <djdelorie> true, but you still need to apply holding torque at the right angle
[19:04:24] <pcw_home> a few degrees is not very important (heck Hall commutated motors get away with +-30 degrees)
[19:04:42] <djdelorie> true
[19:05:01] <pcw_home> that only represents about 13 % torque ripple
[19:05:05] <djdelorie> hall motors suffer from cogging, though
[19:05:28] <pcw_home> yes its a 13% step (not nice for servos)
[19:05:55] <pcw_home> Hall commutation is "Ticky"
[19:06:03] <djdelorie> however, I do use the hall sensors to "pretend" to be encoder inputs, until I see the encoder's Z pulse
[19:06:14] <pcw_home> right
[19:06:43] <djdelorie> hmmm... I forgot to wait for the pulse for those charts, I wonder if that affects the wobble in the current...
[19:07:10] <pcw_home> I think that one of the most common alignment schemes (well waiting for Hall edge anyway)
[19:08:01] <djdelorie> I figured I could "hold step" even if I hadn't seen a hall edge. That way the motor never had to move at startup to just figure out where it was
[19:08:11] <pcw_home> but you definitely will get current wobble unless you have feedback because of the inductance variation
[19:08:53] <djdelorie> no, it's a full rotation for the test, it would have seen Z by that point
[19:11:43] <pcw_home> Whats the time scale of your plot?
[19:12:36] <djdelorie> 20,000 tics / sec
[19:13:22] <pcw_home> and the desired/actual is current?
[19:13:31] <djdelorie> amps
[19:13:38] <djdelorie> "drive" is my PWM settings
[19:14:17] <pcw_home> is this at a fixed drive angle?
[19:14:46] <djdelorie> the field is always 90 degrees to the rotor. The test is one rotation in each direction, back and forth
[19:15:16] <djdelorie> so the rotor is moving
[19:15:25] <pcw_home> OK for tuning the current loop, I would use a drive angle of 0
[19:15:37] <djdelorie> non-moving rotor then?
[19:15:50] <pcw_home> Yes (so you are looking at just one thing)
[19:16:37] <djdelorie> in that test, it's only going 100 RPM. That's close enough to "stopped" for my machine
[19:18:59] <djdelorie> even if I have the clark-park math wrong, the loop should still be able to make the "actual" match "desired" even if the "actual" isn't the right actual current?
[19:19:17] <pcw_home> so something looks odd to me, the current response looks instant (with overshoot) and the PWM lags
[19:19:19] <pcw_home> these look backwards to me
[19:19:58] <djdelorie> there's a PWM spike when the current steps that gets it close to desired. It's the hold-on-value that isn't working
[19:20:53] <pcw_home> Well thats why you need feedback...
[19:20:54] <djdelorie> the current loop runs once per tick, and the inverter is good for up to 20 KHz drive
[19:22:54] <pcw_home> so the step response of the current control is good (from feed-forward/modeling)
[19:22:55] <pcw_home> but the gain of the control loop is insufficient
[19:25:20] <djdelorie> http://www.delorie.com/electronics/bldc/iloop-2.png close up of the step response itself
[19:27:20] <djdelorie> the initial current change is over in under a millisecond
[19:28:03] <pcw_home> Right but still need feedback
[19:28:53] <djdelorie> yeah
[19:29:00] <djdelorie> well, *more* feedback
[19:29:40] <pcw_home> IF you have P gain its not enough
[19:51:37] <r00t4rd3d> anyone use ArtCAM?
[19:54:18] <Tom_itx> r00t4rd3d was it you asking about step and repeat?
[19:54:31] <Tom_itx> couple days ago
[19:54:40] <r00t4rd3d> nope
[19:55:08] <andypugh> Are you sure?
[19:55:18] <Tom_itx> someone making dog tags iirc
[19:58:01] <r00t4rd3d> andypugh, i was asking how to join gcodes
[19:58:37] <andypugh> Yeah, the logs indicate that it was Tom_itx asking about it, so now I am properly confused.
[19:59:07] <Tom_itx> look back further
[20:06:20] <WiillenCMdesign> question for you folks, what salary increase would you leave your job for?
[20:06:59] <cradek> the only possible answer to that is "depends"
[20:07:48] <WiillenCMdesign> i have an offer for a 26,000 a year increase
[20:07:55] <WiillenCMdesign> but here is the catch
[20:07:58] <andypugh> I seriously considered leaving my job for a salary decrease.
[20:08:07] <WiillenCMdesign> my dad owns the company i work for
[20:08:31] <syyl__> i would leave.
[20:08:40] <WiillenCMdesign> even if you worked for you dad
[20:08:44] <andypugh> Even in your feeble currency, 26k is a lot
[20:09:14] <WiillenCMdesign> i know, and its my dream position. Its actually the first customer i designed a machine for
[20:09:48] <WiillenCMdesign> the other kicker is the shop is just down the street from my dads lol
[20:09:57] <andypugh> Ask your dad what you should do.
[20:10:22] <andypugh> Is it a direct competitor?
[20:10:32] <WiillenCMdesign> no
[20:10:49] <WiillenCMdesign> no a distributor he sometimes uses or sawblades
[20:11:23] <cradek> if it's your dream job, then take it if you can survive comfortably enough on the salary, whether it's up or down from what you currently make
[20:11:40] <cradek> you're worrying about the wrong question IMO
[20:11:41] <WiillenCMdesign> i like what i do now
[20:11:52] <WiillenCMdesign> im worried about my relationship with my dad
[20:12:52] <WiillenCMdesign> and even though he says i could leave, i know it would upset him. Im in charge of everything. All of the programs i have wrote for the machines are above anyones ahead using all macro based programming. I have saved his company a fortune
[20:13:02] <andypugh> The job I was looking at was a postdoc in machine tool design at the University local to my parents. It would have been tempting even with the £12k pay cut, except that the timing just didn't work out with the sailing thing.
[20:13:26] <WiillenCMdesign> they use gcode, not cam for the cnc lathes, im the only one who does the cad/cam for the mill
[20:13:49] <cradek> so you're asking a relationship question, not a salary question
[20:13:55] <WiillenCMdesign> basically
[20:13:58] <andypugh> But it isn't like you are leaving town, he will still have access to you. Probably without having to pay you.
[20:14:01] <cradek> have you talked to him?
[20:14:27] <WiillenCMdesign> yes, i had to type it up because its hard to talk to him... i have already quit once to get a pay raise
[20:14:36] <WiillenCMdesign> a few years back
[20:14:55] <WiillenCMdesign> he was so pissed he sent me home the day i came in to talk to him
[20:15:08] <WiillenCMdesign> told me he didn't want me there, he's a hot head
[20:15:22] <WiillenCMdesign> called me 4 days later matching the offer
[20:16:06] <andypugh> Your career prospects are likely to be a lot better outside your dad's company.
[20:16:25] <cradek> how old are you?
[20:16:38] <andypugh> (The absolute best you can hope for there is to take over from him)
[20:16:49] <WiillenCMdesign> 27
[20:16:52] <cradek> dealing with a hothead boss who's not your dad is hard enough
[20:17:35] <WiillenCMdesign> i know... i work for free every day overtime, converted 2 machines to cnc for free(they payed for the parts when i was done) but not my time
[20:17:51] <cradek> I'd think unless I wanted to inherit the company business, I'd get the hell away from that and make my own way as a self-sufficient adult with full autonomy
[20:18:13] <WiillenCMdesign> its easier said though than done, ya know
[20:18:19] <cradek> um do you realize that's all bullshit and he's taking advantage of you?
[20:18:33] <WiillenCMdesign> nots, im his son the way i see it its a learning experience
[20:18:42] <WiillenCMdesign> if it wasn't for that i wouldn't have a company doing it now
[20:18:57] <cradek> ok well I don't know your situation of course
[20:19:00] <WiillenCMdesign> not to mention unlimited use of the machines
[20:19:51] <cradek> but I'm old compared to you and know that sometimes you have to get away from your parents a while in order to (possibly if you both choose to) have a new relationship as adult peers
[20:21:18] <WiillenCMdesign> i don't know if i want the company, to be honost he is 50 percent owner with his partner, and they are bothin in there upper 50's and kinda just run it status quo
[20:21:52] <WiillenCMdesign> basically they are on the back nine and don't want more work because they don't want to do more work
[20:21:55] <cradek> you've got some thinking and deciding to do :-)
[20:22:26] <cradek> can you talk to a trusted and smart older friend? counselor or clergy if that's your way?
[20:22:53] <cradek> gotta run, wishing you the best
[20:22:53] <WiillenCMdesign> yeah i have, just thought would hear from those who might be in the field or maybe have been in the same position
[20:22:53] <andypugh> I think that might be what he is doing here…..
[20:23:28] <WiillenCMdesign> its just stressful thats all, ill let it go though i appreciate your insight
[20:23:49] <cradek> welcome, and I bet andypugh is right
[20:24:02] <cradek> also I think he's older and possibly smarter than me :-)
[20:24:12] <cradek> bbl
[20:24:27] <andypugh> Time for me to sleep too.
[20:24:46] <andypugh> Night all
[20:25:10] <andypugh> ig1
[20:28:03] <r00t4rd3d> daytona is on
[21:12:17] <jdh> quit.raise or not.
[21:12:37] <WiillenCMdesign> huh?
[21:14:37] <jdh> imo. move on.
[21:16:36] <WiillenCMdesign> i want to, im going to put my resume out again i think
[21:16:54] <WiillenCMdesign> make sure this job offer is the best available
[21:20:19] <jdh> working for parents makes you beholden to them. You can't compete on your own merits.
[21:21:03] <WiillenCMdesign> yeah, and i have to hear about every purchase, and every problem, plus i have to help with everything instead of them asking other siblings
[21:21:11] <WiillenCMdesign> if i don't shave for 2 days i hear about it
[21:21:21] <WiillenCMdesign> heaven forbid i want to grow a beared
[21:21:34] <WiillenCMdesign> is it supposed to magically appear
[21:25:11] <ReadError> http://p.twimg.com/AxPywjuCEAIOcYU.jpg:large latest project ;)
[21:25:42] <WiillenCMdesign> :) nice
[21:25:50] <WiillenCMdesign> im waiting for my bt30 spindle to come in
[21:25:58] <ReadError> g10 cuts awesome
[21:26:03] <ReadError> i need to get some black though
[21:26:05] <WiillenCMdesign> then i'll be making an industrial robotic arm
[21:26:08] <ReadError> yellow is fugly
[21:32:56] <r00t4rd3d> hey
[21:33:36] <WiillenCMdesign> hey!
[21:34:30] <r00t4rd3d> ReadError, http://imgur.com/a/LlOpX
[21:34:43] <r00t4rd3d> close
[21:35:21] <ReadError> router mount?
[21:35:35] <r00t4rd3d> ya
[21:42:44] <r00t4rd3d> i made the end tabs bigger in LibreCAD
[21:42:46] <ReadError> shouldnt you beef up the scre area ?
[21:42:52] <ReadError> screw*
[21:42:54] <ReadError> ya
[21:43:18] <r00t4rd3d> Im going out in a minute to try again
[21:46:32] <ReadError> get us a vid of it purring along
[21:48:47] <r00t4rd3d> you ever try librecad?
[21:48:51] <r00t4rd3d> its pretty easy
[21:50:35] <ReadError> nah i went with solidworks, i like it
[21:50:45] <ReadError> i think i tried it
[21:50:58] <ReadError> but didnt spend much time with it
[22:21:29] <linux-cnc-bob> does cutter diameter compensation work with G3?
[22:21:55] <Tom_itx> i can tell you for sure that it does
[22:22:20] <Tom_itx> i screwed up a hole tonight with it but it was supposedly turned off with G40
[22:22:39] <Tom_itx> enter the cutter diameter in the tool table
[22:30:38] <linux-cnc-bob> im trying to hard code it but get an error with this: G41.1 0.118
[22:32:00] <linux-cnc-bob> what does T3 M6 do?
[22:32:07] <linux-cnc-bob> loads tool T3?
[22:32:08] <Tom_itx> tool change
[22:32:10] <Tom_itx> yes
[22:32:14] <linux-cnc-bob> whats the M6?
[22:32:38] <linux-cnc-bob> 6mm?
[22:32:41] <Tom_itx> T is the tool M6 is the change
[22:32:54] <Tom_itx> http://www.linuxcnc.org/docs/html/gcode/m-code.html#_m6_tool_change_a_id_sec_m6_tool_change_a
[22:33:21] <linux-cnc-bob> i dont actually have a tool changer
[22:33:27] <linux-cnc-bob> but just wanted to use cutter compensation
[22:33:37] <linux-cnc-bob> do i still need to edit the tool table?
[22:33:39] <Tom_itx> i don't either
[22:33:43] <linux-cnc-bob> or can i hard code it in the gcode
[22:33:46] <Tom_itx> yes i certainly would
[22:33:59] <Tom_itx> tool length and diameter minimal
[22:34:13] <linux-cnc-bob> ok
[22:34:21] <linux-cnc-bob> so just add a new entry in there i gues
[22:34:29] <Tom_itx> yes
[22:36:41] <linux-cnc-bob> T3 M6 ;select tool from the tool table to use for cutter compensation
[22:36:43] <linux-cnc-bob> G41 T3 ;start cutter radius compensation left
[22:36:46] <linux-cnc-bob> is that good?
[22:37:11] <Tom_itx> i wouldn't specify it on a tool change
[22:37:18] <Tom_itx> maybe put it the line afterward
[22:37:51] <Tom_itx> although they show it on the same line
[22:37:59] <Tom_itx> http://www.linuxcnc.org/docs/html/gcode/gcode.html#_g41_g42_cutter_compensation_a_id_sec_g41_g42_a
[22:39:27] <linux-cnc-bob> i get an error "length of cutter compensation entry move is not greater than the tool radius"
[22:40:17] <jdh> you need to do a lead in move
[22:41:08] <Tom_itx> did you look at the link?
[22:41:17] <Tom_itx> they give you an example
[22:41:21] <linux-cnc-bob> ok
[22:41:34] <Tom_itx> they also specify the axis
[22:41:46] <linux-cnc-bob> i think i start milling right where the machine is zseroed
[22:41:49] <linux-cnc-bob> zeroed
[22:42:09] <Tom_itx> G41.1 Z0.118 for example
[22:43:03] <Tom_itx> i personally would use the tool table
[22:44:17] <linux-cnc-bob> ok i fixed that error
[22:46:40] <linux-cnc-bob> dam the error is back
[22:49:53] <gene_> I haven't used it, but the man pages say that it must have room to apply the compensation without gougeing.
[22:50:49] <gene_> So try moving several tool diameters away, apply the G41.1 option, and move back to the starting position.
[22:53:00] <linux-cnc-bob> G41.1 Z0.118 gives the error "no D word"
[22:53:45] <linux-cnc-bob> but got rid of the cutter compensation error again :D
[22:54:30] <gene_> You do have a valid diameter for the tool whose # was used in the 'T#m6" command in the tool table I hope?
[22:56:23] <gene_> I'm going to go get some zz's, its witching hour in WV, USA.
[22:56:36] <Tom_itx> yup
[22:56:44] <Tom_itx> nearly is here too
[23:04:13] <linux-cnc-bob> doh got a new error: "arc to straight motion makes a corner the compensated tool cant fit without gouging"
[23:05:29] <Tom_itx> why do you need cutter comp?
[23:05:45] <linux-cnc-bob> cutting out some circles
[23:05:52] <Tom_itx> so?
[23:06:00] <Tom_itx> enter the tool diameter in the tool table
[23:06:04] <linux-cnc-bob> basically put in the part into gcode without hardcoding what cutter im using
[23:06:31] <linux-cnc-bob> so i dont need to use G41 then?
[23:06:37] <Tom_itx> i don't use it
[23:07:03] <linux-cnc-bob> so T10 M6 will automaticaly compensate based on the tool diameter?
[23:07:08] <linux-cnc-bob> hmm
[23:07:13] <linux-cnc-bob> it cant know left or right then
[23:07:25] <Tom_itx> T10 M6 will change to Tool 10
[23:07:40] <linux-cnc-bob> ya
[23:07:55] <linux-cnc-bob> but then there is no cutter compensation
[23:08:23] <Tom_itx> so enter the actual tool diameter in the tool table
[23:08:29] <linux-cnc-bob> ya i did
[23:08:32] <linux-cnc-bob> for T10
[23:09:31] <linux-cnc-bob> i put a 1" circle in the gcode
[23:09:52] <linux-cnc-bob> so it will be less than 1" if I dont use G41 i guess?
[23:10:56] <Tom_itx> i'm still trying to figure how linuxcnc handles it. just cut a part this evening and i made a mistake on my tool entry
[23:11:19] <linux-cnc-bob> sounds like same issue
[23:11:21] <Tom_itx> i think it programs the tool center though
[23:11:25] <linux-cnc-bob> ya
[23:11:26] <Tom_itx> test it and see
[23:14:32] <linux-cnc-bob> k
[23:14:39] <linux-cnc-bob> did a test with two different tool diameters
[23:14:48] <linux-cnc-bob> it will cut on same line
[23:14:57] <linux-cnc-bob> for the centers of the tool
[23:15:12] <Tom_itx> did you specify a g41?
[23:15:15] <linux-cnc-bob> no
[23:15:29] <linux-cnc-bob> cant since I still have an error for it
[23:15:53] <jdh> the lead in error?
[23:15:59] <linux-cnc-bob> no fixed that one
[23:16:01] <Tom_itx> was there an entry in the table?
[23:16:07] <linux-cnc-bob> i added T10
[23:16:14] <linux-cnc-bob> 0.118" diameter
[23:16:36] <Tom_itx> 3mmA?
[23:16:40] <Tom_itx> 3mm?
[23:16:43] <linux-cnc-bob> ya
[23:16:48] <linux-cnc-bob> ok here is new errror:
[23:17:22] <linux-cnc-bob> "arc to straight motion makes a corner the compensated tool cant fit without gouging"
[23:17:46] <linux-cnc-bob> i think that is when i cut a circle and then change Z
[23:17:50] <linux-cnc-bob> not sure
[23:18:02] <jdh> do you have a corner?
[23:18:04] <linux-cnc-bob> thats with G41 T10
[23:18:06] <linux-cnc-bob> ya i do
[23:18:10] <linux-cnc-bob> hmm
[23:18:11] <linux-cnc-bob> oh ya
[23:18:13] <jdh> does it have a radius?
[23:18:14] <Tom_itx> just a sec, i'll post the one i just ran
[23:18:15] <linux-cnc-bob> good point
[23:18:27] <linux-cnc-bob> no it has no radius oops
[23:18:30] <r00t4rd3d> http://imgur.com/a/50VAz
[23:18:33] <r00t4rd3d> there we go
[23:19:03] <linux-cnc-bob> whats that for?
[23:19:26] <linux-cnc-bob> i guess i will turn off cutter compensation on the corners
[23:20:53] <Tom_itx> http://tom-itx.dyndns.org:81/~webpage/cnc/cnc_files/enc_hub.txt
[23:20:58] <Tom_itx> that's one i just ran
[23:21:05] <Tom_itx> to give you an idea
[23:21:17] <jdh> why do you do N's?
[23:21:20] <Tom_itx> just a sec..
[23:21:56] <Tom_itx> because i do
[23:22:07] <Tom_itx> most controls don't care
[23:22:37] <linux-cnc-bob> is there a way to ignore that error about arc to straight motion makes a corner..
[23:22:47] <Tom_itx> my post generates it but i could get rid of it
[23:23:24] <Tom_itx> if there's an error i wouldn't ignore it
[23:23:29] <linux-cnc-bob> hmm
[23:23:35] <linux-cnc-bob> i dont really know why there is an error
[23:23:52] <jdh> because you are telling it to cut a compensated path that is not possible
[23:25:06] <jdh> is it a square inside corner?
[23:25:13] <linux-cnc-bob> ya
[23:25:25] <linux-cnc-bob> but i turned off the compensation (G40)
[23:25:31] <linux-cnc-bob> for that part, and still get the error
[23:25:41] <jdh> same place?
[23:25:59] <jdh> did you turn it off immediately before the corner?
[23:26:31] <linux-cnc-bob> immediately after the last circle
[23:26:37] <linux-cnc-bob> then theres an XY move to the start of the corner
[23:26:43] <linux-cnc-bob> ya error is same place
[23:27:57] <linux-cnc-bob> hmm
[23:28:01] <linux-cnc-bob> error is on a G0 line
[23:28:10] <linux-cnc-bob> when i move from the first circle to the next
[23:29:10] <linux-cnc-bob> G0 XY translate gives the error
[23:29:43] <jdh> after the G40?
[23:29:52] <linux-cnc-bob> before
[23:30:16] <linux-cnc-bob> the error is in the circle drawing part
[23:30:33] <linux-cnc-bob> i draw a couple circles and XY translate between them with G0
[23:30:54] <linux-cnc-bob> i put the G40 in a rectangle drawing section, but get the error before that anyway
[23:31:14] <linux-cnc-bob> code was in a sub so didnt know what line the error was on
[23:32:27] <jdh> the resultant move must make a corner that is tighter than the tool radius
[23:35:16] <linux-cnc-bob> maybe i should move with arcs instead of straight lines to get to the next circle
[23:36:19] <linux-cnc-bob> compensation error shouldnt apply to G0 anyway
[23:36:21] <linux-cnc-bob> that sucks
[23:37:41] <toastyde1th> cutter comp must apply to g0 otherwise it loses track of the profile
[23:45:22] <linux-cnc-bob> i got it working but had to put a G40, then a XY move and then G41 between each circle
[23:51:49] <Tom_itx> i noticed my axis button that moves to x y z zero doesn't work if i use mdi and enter a g91
[23:52:13] <Tom_itx> i gotta change it back to g90 then it works fine
[23:58:59] <linux-cnc-bob> i type this in gcode: G10 L1 P20 R0.118
[23:59:11] <linux-cnc-bob> and then T20 M6 gives error
[23:59:26] <WiillenCMdesign> whats the error?
[23:59:28] <linux-cnc-bob> requested tool not found in the tool table
[23:59:43] <Tom_itx> did you add T20 to it?