Messages

11

Show"N"Tell ( Your Machines) / Re: The Laser Project.

« on: March 02, 2011, 10:10:48 AM »

Speaking of the router, i have decided to change the X&Y axis from belt to a ball screw setup. Both axis already have pretty hi precision rails they slide on, it is just that little bit of play in the belts that gets frustrating, especially when there are a lot of quick direction changes. they sort of vibrate, which sometimes causes a couple of thou error in the parts.

Would it be worth exploring some kind of belt vibration dampening before i embark on changing it to ball screw?

 
Jen

Jen,

Slightly off topic here but I'm just wondering what size your drive belting is.  The reason I ask is that I've just built a router that uses 3/8" belts for the xy drives and I'm trying to determine what kind of accuracy I can expect from it.  Right now I see no issues with it but I'm not working to .001 inches.  I have the belts quite firmly tensioned.  I'll try to see if I can measure the stretch later today.

Chris

12

G-Code, CAD, and CAM discussions / Re: Mach won't load this parametric code.

« on: February 19, 2011, 10:47:19 AM »

Ian,

When you refer to 'gcode interpreter' are you referring to the Mach specific interpreter or to an industry standard?  Either way is there a reference that details these operating subtleties?
Thanks.
Chris

13

G-Code, CAD, and CAM discussions / Re: Mach won't load this parametric code.

« on: February 18, 2011, 09:14:21 PM »

Thanks Ian.  This worked well.  What is the meaning of the percent symbol?

Chris

14

G-Code, CAD, and CAM discussions / Re: Mach won't load this parametric code.

« on: February 17, 2011, 06:25:06 PM »

Ok. Thanks Graham.

Chris

15

G-Code, CAD, and CAM discussions / Mach won't load this parametric code.

« on: February 16, 2011, 10:16:29 PM »

Mach3 won't load this parametric code.   Is it a syntax error or just not within Mach's capabilities?  It's hanging on line 4 not liking the word 'If'.

Thanks.

Chris

O001
N1#123=0
N2#100=[5/.125]
N3#101=[#123*.125]
N4IF[#123EQ#100]GOTO7
N5#123=[#123+1]
N6GOTO8
N7M30
N8G1 X[#101] Z0 Y0
N9Z0.037 Y0.0054
N10Z0.0643 Y0.0156
N11Z0.0924 Y0.0313
N13Z0.1144 Y0.0469
N14Z0.1332 Y0.0625
N16Z0.1646 Y0.0938
N17Z0.1904 Y0.125
N20Z0.2115 Y0.1563
N21Z0.2288 Y0.1875
N23Z0.2434 Y0.2188
....etc.
N121Z0.1227 Y11
N122Z0.1095 Y11.125
N123Z0.0961 Y11.25
N124Z0.0825 Y11.375
N125Z0.0687 Y11.5
N126Z0.0549 Y11.625
N127Z0.0409 Y11.75
N128Z0.0268 Y11.875
N129Z0.0127 Y12
N130G0Z.75
N131Y0
N132GOTO3
 

16

G-Code, CAD, and CAM discussions / Re: G41/42 question

« on: February 13, 2011, 10:04:22 AM »

Is there any particular preferred path for the leadin move?

Chris

17

G-Code, CAD, and CAM discussions / Re: G41/42 question

« on: February 12, 2011, 10:58:56 PM »

Thanks Ger,

I was hoping to keep the CAD side of it as simple as possible.  I drew the centerline paths in Rhino and used Rhinoscript to generate the g-code.  I failed to use the G40 word before changing the compensation so I'll have to try inserting that tomorrow to see what the effect is.  It was suggested to me on the cnczone g-code forum that I would have to use leadins with the cutter compensation change so if that is in fact a necessity it may make changing the CAD the easier solution.

Chris

18

G-Code, CAD, and CAM discussions / G41/42 question

« on: February 12, 2011, 06:26:47 PM »

I'm trying to generate a g-code program that zig-zags.  In order to keep the tool on the correct side of the cut I need to change the cutter offset at the end of each x axis motion.  The change from G41 to G42 and back again seems like it might be happening at maximum rapid speed.  What speed is used for the cutter compensation move and is there any strategy that applies to making a smooth transition between G41 and G42?
Thanks.

Chris

19

LazyCam (Beta) / Re: Tabs

« on: February 03, 2011, 06:33:00 PM »

Thanks Rich, that was very helpful.

Chris

20

LazyCam (Beta) / Tabs

« on: February 03, 2011, 01:23:42 PM »

Are Tabs part of LCam Pro?  I'm not seeing any tool paths for them in the demo version.
Thanks.

Chris