What do we want?
Posted by
Bertho Boman
on 1999-10-24 05:20:50 UTC
Hello again,
I spent Wednesday at a machine tool show here in Fort Lauderdale. I talked to a lot of vendors and got demos and useful
information. I also saw some very heavy duty machines doing cuts that I thought would be impossible. After that, I like to update
my previous comments and questions about "What do we want".
In my previous initial thread I had three phases of development and software but now I think we really need just two: Machine
Control and CAD-CAM.
MACHINE CONTROL: Virtually every machine at the show uses G-codes as input to control the machine itself. There are many types of
machine controllers both custom and general purpose that are used for retrofits. In some cases they can be used by manually
cranking the hand wheels and using the display as an expensive DRO or they can be used with jog buttons or dials for manual feed.
A feature that is added to many of the machine controllers are called "Conversational programming". These are basically a prompting
mode for producing very simple tasks as a hole circle, pockets and so on. Usually, what is created in this mode can be saved and
reused. Right now, I am ignoring the motion controller hardware and issues of servos vs steppers. I am only referring to the user
interface and how it is used. An other observation was that the machine controller portion of the software is designed for limited
keyboard/mouse use and often set up for function buttons to push and then to supply the desired numerical value. No CAD & mouse
functions at all!
There is one exceptions to that all machine controllers accepts G-codes; Accurite only does "conversational programming". I see
that as a very large limitation.
Based on the above, what options for machine control do we have that will accept G-codes?
Free-Shareware: EMC and ???? (please fill in)
Commercial Low cost: .................
Commercial Expensive .................
(as you see, this is a work in progress)
CAD-CAM:
I saw several demonstrations of CAD-CAM software: Feature-CAM, Esprit, Master-CAM, Gibs-CAM. The typical cost for a 2.5 axis
system is $5,000 and for the full 3-axis surface version it is about $12,000.
All were basically set up for an office environment with a full keyboard and a mouse. They all emphasized how easy it is to create
a part and it was. There are lots of smarts in the program to help in the process. In all cases, after the part /process was done,
a simulation can be run to show the machining of the part. The programs generate G-codes which is then sent to the machine
controller on the floor.
A little more details about them. The programs internally generate a generic tool path output. That generic internal listing is
then converted to a specific flavor of G-codes that applies to the hardware motion controller by what they call a post processor.
Typically, they have hundreds of versions to choose from. (There is even an Accurite output version) Extra post processors can be
added and there is an editor included to create custom versions from scratch or to modify one that is close to the desired result.
The simulation is done on the generic internal file. That is significant to understand since if the created post processor is
defective, the end result will not match the simulation. Apparently all simulators are independent plugins mainly written by three
companies: VeriCut, NSee and Solaris. These companies also sell very extensive freestanding simulators that can include the whole
setup including tooling and clamps and so on.
One gray area that I was referring to in my previous post and that is still not clear to me. When I design a product, I do not
design a part, I design many parts working together. Very high level programs will allow all kinds of simulation (I wish I had one
and the time to learn how to use it....) but the above mentioned programs might not be able to do that. They might be more intended
to use to import a "one part" file from the "big" program and then create a tooling (G-code) output for just that part. Or if a
drawing is received, use the program to create the part in software and then machine it.
What free/shareware programs will do this?
What low-cost programs?
I have listed several of the expensive ones.
To me, it really looks like a very good splitting point:
CAD-CAM with G-code output that can be customized.
Machine Controllers that understands regular G-codes.
What are your thought and suggestions?
Bertho Boman
Vinland Corporation
I spent Wednesday at a machine tool show here in Fort Lauderdale. I talked to a lot of vendors and got demos and useful
information. I also saw some very heavy duty machines doing cuts that I thought would be impossible. After that, I like to update
my previous comments and questions about "What do we want".
In my previous initial thread I had three phases of development and software but now I think we really need just two: Machine
Control and CAD-CAM.
MACHINE CONTROL: Virtually every machine at the show uses G-codes as input to control the machine itself. There are many types of
machine controllers both custom and general purpose that are used for retrofits. In some cases they can be used by manually
cranking the hand wheels and using the display as an expensive DRO or they can be used with jog buttons or dials for manual feed.
A feature that is added to many of the machine controllers are called "Conversational programming". These are basically a prompting
mode for producing very simple tasks as a hole circle, pockets and so on. Usually, what is created in this mode can be saved and
reused. Right now, I am ignoring the motion controller hardware and issues of servos vs steppers. I am only referring to the user
interface and how it is used. An other observation was that the machine controller portion of the software is designed for limited
keyboard/mouse use and often set up for function buttons to push and then to supply the desired numerical value. No CAD & mouse
functions at all!
There is one exceptions to that all machine controllers accepts G-codes; Accurite only does "conversational programming". I see
that as a very large limitation.
Based on the above, what options for machine control do we have that will accept G-codes?
Free-Shareware: EMC and ???? (please fill in)
Commercial Low cost: .................
Commercial Expensive .................
(as you see, this is a work in progress)
CAD-CAM:
I saw several demonstrations of CAD-CAM software: Feature-CAM, Esprit, Master-CAM, Gibs-CAM. The typical cost for a 2.5 axis
system is $5,000 and for the full 3-axis surface version it is about $12,000.
All were basically set up for an office environment with a full keyboard and a mouse. They all emphasized how easy it is to create
a part and it was. There are lots of smarts in the program to help in the process. In all cases, after the part /process was done,
a simulation can be run to show the machining of the part. The programs generate G-codes which is then sent to the machine
controller on the floor.
A little more details about them. The programs internally generate a generic tool path output. That generic internal listing is
then converted to a specific flavor of G-codes that applies to the hardware motion controller by what they call a post processor.
Typically, they have hundreds of versions to choose from. (There is even an Accurite output version) Extra post processors can be
added and there is an editor included to create custom versions from scratch or to modify one that is close to the desired result.
The simulation is done on the generic internal file. That is significant to understand since if the created post processor is
defective, the end result will not match the simulation. Apparently all simulators are independent plugins mainly written by three
companies: VeriCut, NSee and Solaris. These companies also sell very extensive freestanding simulators that can include the whole
setup including tooling and clamps and so on.
One gray area that I was referring to in my previous post and that is still not clear to me. When I design a product, I do not
design a part, I design many parts working together. Very high level programs will allow all kinds of simulation (I wish I had one
and the time to learn how to use it....) but the above mentioned programs might not be able to do that. They might be more intended
to use to import a "one part" file from the "big" program and then create a tooling (G-code) output for just that part. Or if a
drawing is received, use the program to create the part in software and then machine it.
What free/shareware programs will do this?
What low-cost programs?
I have listed several of the expensive ones.
To me, it really looks like a very good splitting point:
CAD-CAM with G-code output that can be customized.
Machine Controllers that understands regular G-codes.
What are your thought and suggestions?
Bertho Boman
Vinland Corporation
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?