Messages

1181

General Mach Discussion / Re: mach3 lathe homing and help

« on: September 06, 2015, 06:35:03 AM »

In fact, I also don't like the manual and auto screen

A lot of folks tend to echo that comment. Not  many lathe screen sets to be found so I also have done one which is basically done but  still testing/ tweaking /
checking it out running Version 3.042.062. Hope to post it in the near future.

It's uses a single page screen for set-up / running and a single page for tool set-up. But it is loaded with all kinds of features. So it's a hobby screen by other folks
definition of what a screen set should have.

I also use a quick change tool holder thus the tool setup page provides options for tool setup. It does however provide for lathe center finding and populating
the tool table via probing.

For your info, whenever the screen get's posted. 

RICH  

1182

General Mach Discussion / Re: Help please....mach3 jumping to reset when i cut any deeper than 0.5mm

« on: September 03, 2015, 10:25:05 PM »

Mike,
You may want to post some info on the drives, type motors ( steppers ) and size, Mach version used.
Also post your xml file that your using.

RICH

1183

Video P*r*o*b*i*n*g / Re: Best setup for probing a trumpet mouthpiece

« on: August 27, 2015, 07:39:34 PM »

I always say that accuracy will only be as good as the machine " system ".

By that I am meaning:
How repeatable is the machine ( it cannot be as good as the calculated resolution)?
How repeatable is the probe?
How repeatable is actual cutting?

SO
Any movement, sensitivity of a probe, and any actual machining, etc, etc will influence /  determine how accurate the information will be.
Thus it's all that makes up the routine / process.

RICH

1184

General Mach Discussion / Re: Input not recognized with USB controller

« on: August 27, 2015, 08:36:27 AM »

When using an external motion controller the movements are implemented  / controlled by the external device.
May need to go to the seller to resolve.

RICH

1185

LazyCam (Beta) / Re: lazycam wont save after editing

« on: August 27, 2015, 07:35:35 AM »

I assume you have the pro version as that is required offsetting.

Setup provides posting options so see where the file is being saved.

You open  dxf, clean it, create an offset based on a defined tool, go to project and un-enable that which you don't want code posted for,
in layer select the tool you want and fill in  cut inputs applying them to the layers. The graphics area should portray what you desired.
Now post code.

All in the Manual / Tutorials.......,

RICH

1186

LazyCam (Beta) / Re: lazycam wont save after editing

« on: August 26, 2015, 09:06:05 AM »

Suggest you have a read of the LazyCam manual.

RICH

1187

General Mach Discussion / Re: Backlash absolutely not working!

« on: August 26, 2015, 09:01:55 AM »

Did you input the settings, click OK, ........save settings, then go out  and restart Mach?

I never had any problems when I used BC And the 50-50-50 rule is about the best advice I could give to someone.

RICH

1188

Video P*r*o*b*i*n*g / Re: Best setup for probing a trumpet mouthpiece

« on: August 26, 2015, 08:55:17 AM »

From a Trumpet player ...........

In my lathe screen I created some buttons that will capture the manually probed X and Z points and then can create a version 12 DXF
file from the points or draw the lines. Using CAD you can create curves based on the points. Mouthpiece exterior profile is easy.
The rim and end edge contours require more attention to duplicate.

So it's  manual probing. I use axis MPG's to assist in touch off along with a light indicating probe. This allows control over
accuracy and location of the points ( +-0.0002" repeatability). Plus I can make custom probe tips and no compensation is
required. If auto probing is used, ie; G31 then a very slow probe rate is required ...like 1 or less ipm. Thus manual probing as it's quick and easy.

Just a thought... maybe make custom visualizers such that they match the mouthpiece being used!

I researched probing for the lathe and not much out there or you get high end and it's expensive.

Just some thought's,
RICH

 
 

1189

LazyCam (Beta) / Re: Choppy Letters from Illustrator

« on: August 25, 2015, 08:26:19 AM »

You may want to have a look at Cambam as it has basic CAD, produces good gcode , and is economically priced.

All the free stuff is usually lacking in some manner. You may also want to consider AutoCAD Light.
I agree with what Vogavt since you can spend a lot of time trying different CAD products, but,  like the CAM side,
what one likes another dislikes.

At one time there were probably 100 different CAD products being used by different industries. Over my many years I just stuck with
Microstation and AutoCAD. I find most other products cluncky and actually irritable to use, but, can also say the same about jumping from
one CAD program to a different one. So I personally don't even bother with  other ones. The higher end CAD programs
are not cheap......over time I probably spent $4000 on just AutoCAD upgrades. I must say that for 2D work  CAD versions from
1970 are just as good as compared to the latest ones .......must be able to draw lines, circles, arcs and all the other stuff just provides for efficiency.

So pick say 5 different ones, whatever one seems user friendly to you use it, but, make sure it can save as a version 12 dxf and is vector based.

You may also want to think about the future. IE; Will you want to do 3D work ( a different consideration)?

Have Fun,

RICH  

1190

LazyCam (Beta) / Re: Choppy Letters from Illustrator

« on: August 24, 2015, 09:33:52 AM »

LazyCam is a dxf importer and is not the best importer so it is what it is.
WYSIWYG......What You See Is What You Get.

I quickly drew the letter in CAD and saved as a version 12DXF and did not have the problem you are
showing.

You can copy, move and join entities such that one can do minor fix's. It's a PITA sometimes to do.
It's covered somewhat in the LazyCam Manual. LC should not be used as CAD.

BTW, you did not say if you are cutting on the line as drawn or doing an offset based
on a defined tool.

RICH