Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Posted by
imserv1
on 2002-01-03 21:34:51 UTC
--- In CAD_CAM_EDM_DRO@y..., Chris L <datac@l...> wrote:
path that is created on the fly as John is so fond of accusing Vector
of creating G-code? Because Surfcam does it that way? No way, I
much prefer to have all the toolpaths as an editable, selectable,
configurable set of entities. Creating toolpaths on the fly is what
makes Bobcad so hard to understand. You never have a chance to
correct a toolpath until the G-code is generated. It's the same with
any CAM that tries to seperate the Drawing from the toolpaths. That's
the "way we've always done it", is exactly what you are suggesting
that we turn Vector into. (won't happen, we're too mean)
10 years ago Vector was one of the first Windows based Cad-Cam
systems. It was a very difficult struggle because our customers had
to be trained in both Cad-Cam and in Windows. The basic training
included how to use a mouse, what the left button was for, what the
right button was for. What and how to copy and paste. How to use
context sensitive help. Today some of our training materials look a
little too basic because everybody knows how to do that stuff.
It's supposed to. Clean circle is a Wire EDM function. You always
use cutter comp for wire, hence the cut goes to the line. Did you
notice there is no Z depth, for wire edm. Check out Spiral pattern
pocketing for milling or use cutter comp on you mill/router too,
works great.
placed on predesignated layers. It is quite clear inside Vector what
is drawing and what is toolpath. Lathe roughing and finishing are
also marked with unique layer names. So are hatches too for that
matter. In some cases I have pushed to have original entity
attributes retained where it made sense, rather than putting modified
geometry on a designated layer, we retain the original color, layer,
and other attributes.
contour you get what you deserve, nothing. ;-)
their support? Should I copy it and then also price Vector the
same? I prefer to identify a common problem and develop economical
solutions. Like for instance V-tip lettering toolpaths. Minimum cost
about $8000 before Vfontz was released at $300.
are actually holding back the entire Cad industry.
Signlab, however, you can probably buy a couple used CNC machines.
4axis wire edm should not have any Z connects as they add a lot of
breaks for layer name changes between up down, etc.
Use 3D mill, example or example 2 instead, makle sure the default
contour that is checked is G40 or somethng absolute & noncomped.
Vector simple. In Holland they call it the "machinists handy tool",
or something like that. Companies like Phillips have lots of seats
because their craftsmen can rely on the program to make parts the way
they want, not the way some programmer in a closet decided to program
a toolpath.
Right now we are in a major development of new capabilities. These
capabilities are about to be plugged in, after over 2 years of
intense development. Even with that effort, however, we still came
out with 2 (TWO!) major releases in 2001.
2002 is the tenth year anniversary for Vector and coincidentally it
is also the ten year anniversary for IMService. If you think we are
going to curl up and rest on our laurels, change your
prescriptions! ;-)
Happy New Year everybody!
Best Regards, Fred Smith- IMService
We are THE source for low cost Cad-Cam.
Listserve Special discounts and offers are at:
http://vectorcam.com/cced2.html
> Fred,to the
> I think I may understand Johns whole point here..... It comes down
> TOTAL separation of what exactly consists of the part drawing andthe
> generated toolpaths.Why? What's the difference? How can you control a theoretical tool
path that is created on the fly as John is so fond of accusing Vector
of creating G-code? Because Surfcam does it that way? No way, I
much prefer to have all the toolpaths as an editable, selectable,
configurable set of entities. Creating toolpaths on the fly is what
makes Bobcad so hard to understand. You never have a chance to
correct a toolpath until the G-code is generated. It's the same with
any CAM that tries to seperate the Drawing from the toolpaths. That's
the "way we've always done it", is exactly what you are suggesting
that we turn Vector into. (won't happen, we're too mean)
10 years ago Vector was one of the first Windows based Cad-Cam
systems. It was a very difficult struggle because our customers had
to be trained in both Cad-Cam and in Windows. The basic training
included how to use a mouse, what the left button was for, what the
right button was for. What and how to copy and paste. How to use
context sensitive help. Today some of our training materials look a
little too basic because everybody knows how to do that stuff.
>Case in point: Clean pocket. "clean pocket" sure looksin your
> like it works exactly like the old bobcad. If you select a circle
> drawing without offsetting a line to represent 1/2 the diameter ofthe
> tooling you want to use, It uses the parts circle line as atoolpath.
It's supposed to. Clean circle is a Wire EDM function. You always
use cutter comp for wire, hence the cut goes to the line. Did you
notice there is no Z depth, for wire edm. Check out Spiral pattern
pocketing for milling or use cutter comp on you mill/router too,
works great.
>that most
> Clean Pocket is probably not the best point because I well know
> other areas in regards Vectors pocketing DO create their own offsettoolpath
> line and leave the part drawing totally alone. It is one area touse caution
> though !All the pocketing toolpaths and their components are automaticlly
>
placed on predesignated layers. It is quite clear inside Vector what
is drawing and what is toolpath. Lathe roughing and finishing are
also marked with unique layer names. So are hatches too for that
matter. In some cases I have pushed to have original entity
attributes retained where it made sense, rather than putting modified
geometry on a designated layer, we retain the original color, layer,
and other attributes.
> I too feel that there are times where the direction arrows areannoying. It
> probably would not take much to add a mechanism to allow one todisplay them
> only when desired.Sorry not gonna happen. ;-) Talk about an old tired interface.
>Consider CorelDraw.
> Who cares! Create Code ! I have noticed that Vector DOES create thecode in a
> very trustworthy manner as long as the entity your creating it fromis
> "closed" and correct.Vector code is always on the money. If you try to pocket an open
contour you get what you deserve, nothing. ;-)
>What does it cost(upfront and per year for maintenance) & how is
> Get a copy of Signlab to Study.
their support? Should I copy it and then also price Vector the
same? I prefer to identify a common problem and develop economical
solutions. Like for instance V-tip lettering toolpaths. Minimum cost
about $8000 before Vfontz was released at $300.
> One may say that there is not one universal best way. Well, I thinkif they
> start with a CAD program that follows Ashlars methods of drawing,Who could
> argue with that ?Ashlar for one. They have some very nasty(nice for them) patents that
are actually holding back the entire Cad industry.
> I would like to see a much simpler toolpath generationand also
> technique and the ability to edit that path when and if necessary,
> dictate "order" and what I want to cut and when much like SignLab.Buy signlab. that's the only advice I can give. Between Vellum and
Signlab, however, you can probably buy a couple used CNC machines.
> I must have to hit the enter key for feedrate question a couple ofhundred
> times ! I will figure it out, I am sure it works the way i want !It's set to react to the layer names on the first entity of a chain.
4axis wire edm should not have any Z connects as they add a lot of
breaks for layer name changes between up down, etc.
Use 3D mill, example or example 2 instead, makle sure the default
contour that is checked is G40 or somethng absolute & noncomped.
>THE most
> I am pretty confident that Vector will continue to advance. That is
> important thing for any software developer. Listening and makingevery change
> possible that will suit the majority of its users will keep thesoftware on
> the desktop.Yes it will, but you missed the important thing, we want to keep
Vector simple. In Holland they call it the "machinists handy tool",
or something like that. Companies like Phillips have lots of seats
because their craftsmen can rely on the program to make parts the way
they want, not the way some programmer in a closet decided to program
a toolpath.
Right now we are in a major development of new capabilities. These
capabilities are about to be plugged in, after over 2 years of
intense development. Even with that effort, however, we still came
out with 2 (TWO!) major releases in 2001.
2002 is the tenth year anniversary for Vector and coincidentally it
is also the ten year anniversary for IMService. If you think we are
going to curl up and rest on our laurels, change your
prescriptions! ;-)
Happy New Year everybody!
Best Regards, Fred Smith- IMService
We are THE source for low cost Cad-Cam.
Listserve Special discounts and offers are at:
http://vectorcam.com/cced2.html
Discussion Thread
mszollar
2002-01-02 12:55:15 UTC
BobCAD/CAM v.s. Dolphin CAD/CAM
Tim
2002-01-02 13:16:17 UTC
RE: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
Darrell Daniels
2002-01-02 13:52:54 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
follicely_challenged
2002-01-02 14:13:53 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-02 14:41:45 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Andrew Werby
2002-01-02 15:06:44 UTC
BobCAD/CAM v.s. Dolphin CAD/CAM
Carol & Jerry Jankura
2002-01-02 15:46:00 UTC
RE: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
cnc002@a...
2002-01-02 15:51:44 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
Tim
2002-01-02 16:52:11 UTC
RE: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
fast1994gto
2002-01-02 18:54:43 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Steve Smith
2002-01-02 19:20:35 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
Darrell Daniels
2002-01-02 19:24:14 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
cnc002@a...
2002-01-02 19:50:51 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-02 20:48:15 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
mszollar
2002-01-02 23:00:07 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
John Stevenson
2002-01-03 01:24:05 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 07:57:37 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-03 09:02:13 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
j.guenther
2002-01-03 09:40:40 UTC
RE: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
follicely_challenged
2002-01-03 12:27:17 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-03 12:36:13 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 13:25:55 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 13:31:35 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
follicely_challenged
2002-01-03 14:34:03 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
hardingjjb@a...
2002-01-03 14:43:19 UTC
Re: [CAD_CAM_EDM_DRO] BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-03 14:55:29 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-03 15:05:13 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 15:12:57 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 15:24:01 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-03 15:29:28 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 15:49:15 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-03 19:11:35 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-03 20:15:53 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
imserv1
2002-01-03 21:34:51 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
follicely_challenged
2002-01-03 23:44:36 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-04 01:24:06 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-04 02:08:15 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
CL
2002-01-04 09:59:30 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
CL
2002-01-04 10:17:22 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
CL
2002-01-04 10:27:33 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Steve Smith
2002-01-04 18:35:04 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-04 19:37:25 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-04 20:46:31 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Michael Milligan
2002-01-04 22:54:55 UTC
RE: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-05 01:41:28 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2002-01-05 02:02:19 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
follicely_challenged
2002-01-05 02:47:52 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Steve Smith
2002-01-05 09:36:29 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
IMService
2002-01-05 11:44:51 UTC
Re: Re: Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Chris L
2002-01-05 22:41:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: Re: BobCAD/CAM v.s. Dolphin CAD/CAM
Ross
2003-05-01 11:36:12 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
stevenson_engineers
2003-05-02 22:25:24 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM
cnc002@a...
2003-05-03 08:32:18 UTC
Re: [CAD_CAM_EDM_DRO] Re: BobCAD/CAM v.s. Dolphin CAD/CAM
kdoney_63021
2003-05-03 09:41:06 UTC
Re: BobCAD/CAM v.s. Dolphin CAD/CAM