Machsupport Forum

G-Code, CAD, and CAM => LazyCam (Beta) => Topic started by: tamathumper on October 02, 2008, 08:38:16 AM

Title: LazyCam only ouputs 49 lines of g-code? SOLVED
Post by: tamathumper on October 02, 2008, 08:38:16 AM
Can anyone help me figure out why LazyCam will only output 49 lines of G-Code for this DXF file of a gear?  GCode-2000 handles the DXF-to-G-Code conversion just fine, but LazyCam seems to be choking on something...

I have attached the original DXF file, my LCam file, and the resultant TAP file.

Any help would be greatly, greatly appreciated.
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: ger21 on October 02, 2008, 11:07:59 AM
The free version only outputs 50 lines of code. You have to pay for the license to get more.
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: tamathumper on October 02, 2008, 11:29:02 AM
I looked all over the site and couldn't find that anywhere.  Bummer!  Thank you for the response!

So this begs the question - is it worth the $75 to purchase the Pro, or should I look to another product?  It's hard to evaluate the thing if it only outputs 50 lines of code!  I do have a current license for Mach3 already.
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: budman68 on October 02, 2008, 11:58:13 AM
Quote
I do have a current license for Mach3 already.


If that's the case, then I believe there should be no lines of code limitations but the free version does not have pocketing or offsets. I remember before I bought the pro version, I was definitely using more than 50 lines of code as I had a Valid Mach license.

Bottom line, not sure why you're having those issues, possibly uninstall lazycam and reinstall again.

If you want my advice, I'd look at Cut2D first as that program is way more user friendly. I'm still playing around with the trial version and haven't made the purchase as of yet-

Dave
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: RICH on October 02, 2008, 12:43:13 PM
tamathumper,
I just imported you dxf and posted code to Mach Mill. I have a licensed version.
As can be seen, it generated some 2100 lines of code. I can't speak for the mill end of
Lazycam and just how good the Beta is for milling. What else can I say.
RICH
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: tamathumper on October 02, 2008, 12:46:22 PM
I'm baffled but heartened.  I tried Cut2D just now and it crashes when I try to load the DXF file, so I guess I'll uninstall and re-install LazyCam!?
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: tamathumper on October 02, 2008, 01:03:01 PM
Nope, that didn't help either!  >:( ??? :P :-[ :-\ :'(
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: ger21 on October 02, 2008, 01:28:20 PM
If Cut2D crashes, send the .dxf to Vectric and they'll fix you up pretty quickly. Their support is second to none.
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: budman68 on October 02, 2008, 03:37:45 PM
Just as a side note, I had no problems outputting the dxf to LCam and then over to Mach3 as Rich had confirmed above-

Dave
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: RICH on October 02, 2008, 04:05:18 PM
tamathumper,
Just thought that I would  mention that your DXF is a "3D" file and not 2D.
RICH
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: tamathumper on October 02, 2008, 08:33:33 PM
Got it - had to do a reboot!  Not sure why, but something must just have been cobbed up.  It cranked out a LOT of g-code after that!  Over 50,000 lines!

Does the fact that it's a 3D file matter?  I don't see any indication that it's 3D in the original DXF, in fact there's no ISO view capability or Z value assigned to any of the objects...  Most of them I deleted just to get an outline of the gearset...

I found out the "no offset" limitation in LazyCam, apparently I can't tell the package to offset each tool or operation :(  That's a big problem!
Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: RICH on October 03, 2008, 07:00:49 AM
tamathumper,
When the file is  imported into into Autocad or Microstation it tells you that it is 3d and you can't manipulate
the file until converted  to a 2d if working in 2d. Each line or circle would represent a cut, boundry , etc which you need to define, delete depending on what you want to do. IE; A circle between two others could represent the toolpath  of
a ball endmill. Once coverted the circle's then become individual lines making up the circles, thus many inidividual cuts for
a simple toolpath.
Even though Lazcam imports the DXF it dosn't know what you want to do with each line until you define them for cutting. I have not fooled with Lazcam Mill ( just " exploring " it's use for turning ) and don't want to make assumptions about the milling and miss guide you. That said, try siimple profiles for manipulation, until you get a feel for what lazcam will do in regards to importing a file, how to define the toolpaths for cutting, etc. ( watch the videos).
Maybe duplicate what the wizards generate for milling and compare the generated gcodes. You can do a lot with the wizards. Soon as you get into
unique profiles you now need something more. Lazcam should satisfy that need.
Lazycam or any other program is not smart enough to automaticaly generate gcode for machining with out addtioinal instructions or definition.
Lazcam is Beta and undocumented, but, at least you have videos for milling giving instructioins on use. I would beliieve that although not a CAM replacement it is still a very powerfull tool for milliing.
  
RICH

Title: Re: LazyCam only ouputs 49 lines of g-code?
Post by: tamathumper on October 03, 2008, 08:40:27 AM
Thanks for the response Rich.

What would be awesome is if LazyCam or some other system would be able to duplicate the sloping profiles of each spoke from shallow on the outside of the wheel to slightly deeper near the hub.

I do have the simpler profiles loaded in LazyCam now, and it puts out g-code that Mach3 will use, although I have to edit it by hand because it doesn't do Tool Changes correctly, leaving off the "0" if I call for Tool 0.  I suppose I should stop being a computer nerd and start numbering my tools at "1".

I'm also trying out Cut2D and that looks pretty good.  I especially like how easy it is to modify the elements in the program and preview the toolpaths.  Now I just need to find $150 somewhere...