Re: [Emc-users] Machine zero, fixture offsets.
John Alexander Stewart wrote: > Viesturs; > > > >> Jon, docs do not say anything about L word in G92 command. Is that just a >> small typo? >> Yup, I got G92 and G10 mixed up. Jon -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
There I'd a oword subroutine in the wiki that jepler wrote for me several years back. Basically a rectangular array that you spec rows, columns, offset distance s and finally the code. I tweaked a copy to read a gcode part file. Used numerous times to cut out Xmas ornaments several years in a row for swmbo. Brian On Aug 14, 2013 4:02 PM, "John Thornton" wrote: > I do the same thing on my plasma cutter, jog to the start point and use > the G92 magic. > > JT > On 8/14/2013 1:45 PM, andy pugh wrote: > > On 14 August 2013 19:16, Kenneth Lerman > wrote: > > > >> Of course, if you think like a programmer and don't want to know > >> anything about G92 or stuff like that, you just write a gcode subroutine > >> to make the part. The subroutine takes two arguments, the X and Y > >> coordinates of the (center, edge, whatever) the part. > > I have subroutines like this for connector cutouts, but they don't > > even take a position parameter. > > > > You position the tool where you want the feature (typically with > > G-code) and then call the sub. > > The first thing that the sub does is G92 the as-called position to > > zero, then it cuts the shape, then it clears the G92 offset. > > > > > > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
I do the same thing on my plasma cutter, jog to the start point and use the G92 magic. JT On 8/14/2013 1:45 PM, andy pugh wrote: > On 14 August 2013 19:16, Kenneth Lerman wrote: > >> Of course, if you think like a programmer and don't want to know >> anything about G92 or stuff like that, you just write a gcode subroutine >> to make the part. The subroutine takes two arguments, the X and Y >> coordinates of the (center, edge, whatever) the part. > I have subroutines like this for connector cutouts, but they don't > even take a position parameter. > > You position the tool where you want the feature (typically with > G-code) and then call the sub. > The first thing that the sub does is G92 the as-called position to > zero, then it cuts the shape, then it clears the G92 offset. > -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
2013/8/14 andy pugh > > The first thing that the sub does is G92 the as-called position to > zero, then it cuts the shape, then it clears the G92 offset. Thank you! I do not know, why I did not think about clearing that offset right in subroutine, so that all the coordinates remain untouched in main program. -- Viesturs -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
On 14 August 2013 19:16, Kenneth Lerman wrote: > Of course, if you think like a programmer and don't want to know > anything about G92 or stuff like that, you just write a gcode subroutine > to make the part. The subroutine takes two arguments, the X and Y > coordinates of the (center, edge, whatever) the part. I have subroutines like this for connector cutouts, but they don't even take a position parameter. You position the tool where you want the feature (typically with G-code) and then call the sub. The first thing that the sub does is G92 the as-called position to zero, then it cuts the shape, then it clears the G92 offset. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
Of course, if you think like a programmer and don't want to know anything about G92 or stuff like that, you just write a gcode subroutine to make the part. The subroutine takes two arguments, the X and Y coordinates of the (center, edge, whatever) the part. Then call the subroutine once for each place that you want to make the part. Ken On 8/14/2013 1:48 PM, John Alexander Stewart wrote: > Viesturs; > > >> Jon, docs do not say anything about L word in G92 command. Is that just a >> small typo? >> > pre-coffee typo. > > Essentially what I want to do is to make 9 copies of a shape, and, thought > > "if I make 9 imaginary fixtures, I can simply change to the next fixture > and machine the part again" > > but it might just be easier to move the coordinate system than worry about > imaginary fixtures. > > Right? > > Yesterday I did learn that I needed to do a lot more reading and > experimenting on coordinate systems in Gcode, and actually went through the > emc.var file to see what was happening, so lots of stuff learnt. > > Maybe tonight I'll get more time to play (learn), before I start actually > machining. > > Thanks! - John A. Stewart. > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
Viesturs; > Jon, docs do not say anything about L word in G92 command. Is that just a > small typo? > pre-coffee typo. Essentially what I want to do is to make 9 copies of a shape, and, thought "if I make 9 imaginary fixtures, I can simply change to the next fixture and machine the part again" but it might just be easier to move the coordinate system than worry about imaginary fixtures. Right? Yesterday I did learn that I needed to do a lot more reading and experimenting on coordinate systems in Gcode, and actually went through the emc.var file to see what was happening, so lots of stuff learnt. Maybe tonight I'll get more time to play (learn), before I start actually machining. Thanks! - John A. Stewart. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
2013/8/14 Jon Elson > John Alexander Stewart wrote: > > Marcus; > > > > Thinking about it, and reading about the G92 command, I think that the > G92 > > might be a better solution for what I want to do, (which is just machine > a > > bunch of identical parts on a sheet of brass). > > > > I had thought that setting up an array of "fixtures" would be the > solution, > > but I think the G92 is the way forward. > > > > > Yes, that's how I do it. Go to G54, move to the zero feature of the next > position, do G92 L2 X0 Y0, > then G55, and run the subroutine, then go to G54, move to next > position and repeat. Jon, docs do not say anything about L word in G92 command. Is that just a small typo? And could you, please, explain, why do you switch back and forth to G55? G92 moves the origin of all coordinate systems, so it does not make much sense to me. Or did you mean G10 L2 X0 Y0 previously, which would move origin of G55 and leave G54 untouched? But then you need a P word to specify, which coordinate system should be changed. -- Viesturs -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
John Alexander Stewart wrote: > Marcus; > > Thinking about it, and reading about the G92 command, I think that the G92 > might be a better solution for what I want to do, (which is just machine a > bunch of identical parts on a sheet of brass). > > I had thought that setting up an array of "fixtures" would be the solution, > but I think the G92 is the way forward. > > Yes, that's how I do it. Go to G54, move to the zero feature of the next position, do G92 L2 X0 Y0, then G55, and run the subroutine, then go to G54, move to next position and repeat. Note that at least with the version I'm running, this will NOT work right if you try to restart from line if you interrupt the program. Jon -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
Marcus; Thinking about it, and reading about the G92 command, I think that the G92 might be a better solution for what I want to do, (which is just machine a bunch of identical parts on a sheet of brass). I had thought that setting up an array of "fixtures" would be the solution, but I think the G92 is the way forward. Thanks for your questions and suggestions - they certainly helped light the way forward. John A. Stewart. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
Marcus; Thank you for the tips. You could always do a manual test (and apologies if you have already done > this) by manually setting the G54-59.3 origins by moving and touching off > each in turn. You should then be able to go to each origin in turn using > G55 G0 X0 Y0 Z0 and so on. > What happens then? > if I set different z depths via touching off, then (eg) G54 g0 z0 and G55 g0 z0 I go to the z depths as defined as 0.0 for that G-origin. Now for the solution: > > I can't see it affecting your method, but I find G10 L20 much more > convenient than the L2 version of that command. It saves calculation > because the L2 offsets should be calculated form absolute machine > co-ordinates, whereas L20 works all that out for you . > Yes! When setting the G55 Z depth for tool touching material, the 9 fixture points follow down the Z axis if the G10 L20 is set, rather than the "L2". I'll have to figure out why touching off G54 does not change the position of the cut in Axis, but G55 does. > Is there a G92 in effect anywhere? > What happens if you put G92.1 at the start of the program? No, there was not, and I don't see any change if a G92.1 is there or not. Obviously, I've lots of reading and button clicking to do, but thank you for the help, especially the L20 rather than the L2 - I think that would have taken me a bit of time to find. John A. Stewart. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Machine zero, fixture offsets.
John, Looks ok, but it may be something "simple". You could always do a manual test (and apologies if you have already done this) by manually setting the G54-59.3 origins by moving and touching off each in turn. You should then be able to go to each origin in turn using G55 G0 X0 Y0 Z0 and so on. What happens then? I can't see it affecting your method, but I find G10 L20 much more convenient than the L2 version of that command. It saves calculation because the L2 offsets should be calculated form absolute machine co-ordinates, whereas L20 works all that out for you . Drive the controlled point to each fixture reference point in turn and touch off at each, before you begin the program. Is there a G92 in effect anywhere? What happens if you put G92.1 at the start of the program? Regards, Marcus On 13 Aug 2013, at 22:39, John Alexander Stewart wrote: > I'm having a bit of difficulty getting my first attempt at changing machine > offsets for fixtures. > > I have 9 locations that I want to machine the same things to. > > 1) Synopsys - start LinuxCNC. Home machine. touchoff G54 x/y/z. > > 2) Load in program. > > 3) Load first tool (collet chuck, manually done) > > 4) bring tool down to just above surface. > > 5) touch off Z for G54. > > Nothing on the screen moves. The AXIS display leaves everything "up above". > > I'm used to having AXIS move things down when touching off. > > No touch offs move any of the "fixture locations". > > > > Here's some of the code - > > > ( StarTest-16mm 8/11/2013 7:15:38 PM ) > ( T1 : 1.0 ) > G21 G90 G64 G40 > G0 Z1.0 > (T1 M6) > (G17) > (M3 S7000) > (pause for 2 seconds) > (G4 P2 ) > > (set up 9 positions) > (respectively G54 G55 G56 G57 G58 G59 G59.1 G59.2 G59.3) > > G10 L2 P1 X00.0 Y0.0 > G10 L2 P2 X19.0 Y0.0 > G10 L2 P3 X38.0 Y0.0 > G10 L2 P4 X00.0 Y17.0 > G10 L2 P5 X19.0 Y17.0 > G10 L2 P6 X38.0 Y17.0 > G10 L2 P7 X00.0 Y34.0 > G10 L2 P8 X19.0 Y34.0 > G10 L2 P9 X38.0 Y34.0 > > (drilling centre hole subroutine) > O888 SUB > ... > O888 ENDSUB > > (milling 1mm end mill, outline of valve handle) > O999 SUB > ... > O999 ENDSUB > > > > (drill 9 centre holes, tool 10) > T10 M6 > G17 > M3 S1000 > (pause for 2 seconds) > G4 P2 > > G54 > O888 CALL > G55 > O888 CALL > G56 > O888 CALL > G57 > O888 CALL > G58 > O888 CALL > G59 > O888 CALL > G59.1 > O888 CALL > G59.2 > O888 CALL > G59.3 > O888 CALL > > (Mill the handwheels, tool 1mm endmill) > T1 M6 > G17 > M3 S7000 > (pause for 2 seconds) > G4 P2 > > G54 > O999 CALL > G55 > O999 CALL > G56 > O999 CALL > . > G54 x0 y0 z0 > M5 > M30 > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
