What do we want?
Posted by
Bertho Boman
on 1999-10-18 11:25:14 UTC
I see many comments and requests for CAD being integrated with the "CNC" or "CAM". Maybe my definitions are not well defined
and I guess it depends on goals and how we work.
I know there are very high end systems where everything is integrated and machining centers are tied together with the design
systems (car manufacturing for example) but I do not think that is our goal, at least it is not mine.
I see several levels of system requirements but would like comments and suggested typical programs for each.
PHASE 1: When I design a new product, I spend days and often weeks to put the system together so that all the individual
hardware and subsections fit and work together. After that, I create drawings and specifications of the different components
and normally send the drawings and DXF file out to get prototypes made. If the parts can reasonably by made manually, I make
my own prototypes. I am in the process of converting my mill to CNC.
This point seems to me to be a crucial dividing line. My work as an engineer is over and I put on my machining hat and go and
get dirty.
PHASE 2: Actually, once I am in the shop, I would work in the shop office first and create "the machine control file". I like
to be able to load the "data" from the previous design program or from a customers data file. Hopefully, the customer will have
it as some data file, DXF, or what not. Presumably, at this point I will need a program to generate G-codes from the data file
together with my manual interaction for tool selection and desired tool path. I envision this program as an intermediate step,
a converter, from the engineering world to the machining world and the output would be G-codes although I have seen references
on the list to other unfamiliar systems. The G-codes can be saved and just reused for future production. It would be important
that the converter program can show tool path and machine operation to catch blunders. Even better, hopefully, it can also show
clamps and fixtures.
This is to me the second major dividing line. Now the data is ready for production manufacturing (hopefully) and it gets to the
flying chips part.
PHASE 3: From the shop office the G-codes would be sent to the machine on the floor. There the G-codes and tools and DRO
functions would be displayed and the part would be machined under "CNC".
There are other desired software features that would be nice, for example, reverse G-code to DXF and some type of quicky
"manual" CNC for very simple operations on the floor.
Phase 1, design stage. I have seen Rhino mentioned and there are many other CAD programs available at a tremendous price range
from free to $$$$$$$. I am using AutoCad for my part and I am not doing any fancy curved surfaces, at least not yet but it is
tempting with CNC available.
Phase 2, conversion. I have zero experience with programs to convert. Suggestions??
Phase 3, machining. I have used several different programs but they have always been supplied by the machine manufacturer. I
guess the prime candidate here is EMC and there are expensive commercial software, often tied with hardware manufactured by the
same company.
After all that writing (I'm competing with Arne) comes a few questions:
Many of the "free" or low-cost programs that are discussed here seem to blur the definitions between the phases that I have
tried to create. Maybe the phases are wrong.
Why would anyone use a program that can not accept G-codes? Time to put on flame proof jacket again! Why a CAD program that
runs a milling machine? Of course, it would be great if one program could do all but then it is usually mediocre instead.
So, what are the recommended software for the different phases or how should I re-split the definitions?
Bertho Boman
and I guess it depends on goals and how we work.
I know there are very high end systems where everything is integrated and machining centers are tied together with the design
systems (car manufacturing for example) but I do not think that is our goal, at least it is not mine.
I see several levels of system requirements but would like comments and suggested typical programs for each.
PHASE 1: When I design a new product, I spend days and often weeks to put the system together so that all the individual
hardware and subsections fit and work together. After that, I create drawings and specifications of the different components
and normally send the drawings and DXF file out to get prototypes made. If the parts can reasonably by made manually, I make
my own prototypes. I am in the process of converting my mill to CNC.
This point seems to me to be a crucial dividing line. My work as an engineer is over and I put on my machining hat and go and
get dirty.
PHASE 2: Actually, once I am in the shop, I would work in the shop office first and create "the machine control file". I like
to be able to load the "data" from the previous design program or from a customers data file. Hopefully, the customer will have
it as some data file, DXF, or what not. Presumably, at this point I will need a program to generate G-codes from the data file
together with my manual interaction for tool selection and desired tool path. I envision this program as an intermediate step,
a converter, from the engineering world to the machining world and the output would be G-codes although I have seen references
on the list to other unfamiliar systems. The G-codes can be saved and just reused for future production. It would be important
that the converter program can show tool path and machine operation to catch blunders. Even better, hopefully, it can also show
clamps and fixtures.
This is to me the second major dividing line. Now the data is ready for production manufacturing (hopefully) and it gets to the
flying chips part.
PHASE 3: From the shop office the G-codes would be sent to the machine on the floor. There the G-codes and tools and DRO
functions would be displayed and the part would be machined under "CNC".
There are other desired software features that would be nice, for example, reverse G-code to DXF and some type of quicky
"manual" CNC for very simple operations on the floor.
Phase 1, design stage. I have seen Rhino mentioned and there are many other CAD programs available at a tremendous price range
from free to $$$$$$$. I am using AutoCad for my part and I am not doing any fancy curved surfaces, at least not yet but it is
tempting with CNC available.
Phase 2, conversion. I have zero experience with programs to convert. Suggestions??
Phase 3, machining. I have used several different programs but they have always been supplied by the machine manufacturer. I
guess the prime candidate here is EMC and there are expensive commercial software, often tied with hardware manufactured by the
same company.
After all that writing (I'm competing with Arne) comes a few questions:
Many of the "free" or low-cost programs that are discussed here seem to blur the definitions between the phases that I have
tried to create. Maybe the phases are wrong.
Why would anyone use a program that can not accept G-codes? Time to put on flame proof jacket again! Why a CAD program that
runs a milling machine? Of course, it would be great if one program could do all but then it is usually mediocre instead.
So, what are the recommended software for the different phases or how should I re-split the definitions?
Bertho Boman
Discussion Thread
Bertho Boman
1999-10-18 11:25:14 UTC
What do we want?
Clint Bach
1999-10-18 15:30:14 UTC
RE: What do we want?
garfield@x...
1999-10-18 15:04:18 UTC
Re: What do we want?
Clint Bach
1999-10-18 17:28:40 UTC
RE: What do we want?
George Potter
1999-10-18 16:51:04 UTC
Re: What do we want?
Bertho Boman
1999-10-18 16:36:22 UTC
Re: What do we want?
Jon Anderson
1999-10-18 17:01:44 UTC
Re: What do we want?
Bertho Boman
1999-10-18 18:33:59 UTC
Re: What do we want?
Jon Anderson
1999-10-18 19:11:17 UTC
Re: What do we want?
garfield@x...
1999-10-18 19:55:13 UTC
Re: What do we want?
Ray Henry
1999-10-19 09:05:32 UTC
Re: What do we want?
Ian Wright
1999-10-19 10:45:34 UTC
Re: What do we want?
Jon Elson
1999-10-19 12:16:13 UTC
Re: Re: What do we want?
Jon Elson
1999-10-19 12:48:09 UTC
Re: What do we want?
Andrew Werby
1999-10-19 04:50:19 UTC
Re: What do we want?
Andrew Werby
1999-10-19 05:00:08 UTC
Re: What do we want?
Clint Bach
1999-10-19 10:50:07 UTC
Re: Re: What do we want?
stratton@x...
1999-10-19 14:04:04 UTC
Re: Re: What do we want?
Bertho Boman
1999-10-19 13:48:37 UTC
Re: What do we want?
batwings@x...
1999-10-19 05:34:10 UTC
Re: Re: What do we want?
Ron Ginger
1999-10-19 15:06:42 UTC
Re: What do we want?
Ian Wright
1999-10-19 15:50:01 UTC
Re: Re: What do we want?
Bertho Boman
1999-10-19 17:35:31 UTC
Re: Re: What do we want?
PTENGIN@a...
1999-10-19 18:56:00 UTC
Re: Re: What do we want?
Robert N Ash
1999-10-19 19:24:22 UTC
Re: What do we want?
Bertho Boman
1999-10-19 19:45:42 UTC
Re: What do we want?
Jon Elson
1999-10-19 21:09:00 UTC
Re: Re: What do we want?
Clint Bach
1999-10-19 20:19:13 UTC
Re: Re: What do we want?
Marshall Pharoah
1999-10-20 05:46:55 UTC
Re: Re: What do we want?
Ian Wright
1999-10-20 03:43:42 UTC
Re: What do we want?
Ian Wright
1999-10-20 03:48:45 UTC
Re: Re: What do we want?
Ian Wright
1999-10-20 03:34:08 UTC
Re: Re: What do we want?
Andrew Werby
1999-10-20 03:22:37 UTC
Re: What do we want?
stratton@x...
1999-10-20 11:38:32 UTC
Re: Re: What do we want?
Andrew Werby
1999-10-20 03:59:03 UTC
What do we want?
PTENGIN@x...
1999-10-20 12:18:14 UTC
Re: Re: What do we want?
PTENGIN@x...
1999-10-20 12:26:16 UTC
Re: Re: What do we want?
Clint Bach
1999-10-20 10:00:59 UTC
Re: Re: What do we want?
Jon Elson
1999-10-20 15:20:53 UTC
Re: Re: What do we want?
Marshall Pharoah
1999-10-21 05:20:23 UTC
Re: Re: What do we want?
Bertho Boman
1999-10-24 05:20:50 UTC
What do we want?
Ray Henry
1999-10-25 12:11:19 UTC
Re: What do we want?
Jon Elson
1999-11-04 23:11:34 UTC
Re: Re: What do we want?