Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Posted by
Marcus & Eva
on 2000-11-29 08:20:38 UTC
Hi Bill:
How did the program get to having the arcs broken up into line segments
in the first place?
Was the toolpath generated from a spline or a surface in the CAM software?
Splines and arcs will output as line segments in most CAM software, since
there are very few machine controls out there that can handle NURBS input.
(Splines and surfaces are often described mathematically as NURBS entities).
Sometimes, it's difficult to determine if the entity you see on the screen
is an arc or a spline.
Most programs have some king of "analyze" function that will tell you.
Anyway, back to your original question.
A lot of the guys I worked with, preferred to take a simple 2D profile and
program only the first pass.
They would then "loop" the program to create all the subsequent passes.
That gave them only one short chunk of code to edit.
If you have multiple copies of your profile to cut, it makes for a very
economical program, but you have to know how to set up the loop commands in
your particular controller.
Hope this helps
Marcus
-----Original Message-----
From: BillDarby <ddarby@...>
To: CAD_CAM_EDM_DRO@egroups.com <CAD_CAM_EDM_DRO@egroups.com>
Date: Wednesday, November 29, 2000 7:38 AM
Subject: Re: [CAD_CAM_EDM_DRO]A question of size managenent.
How did the program get to having the arcs broken up into line segments
in the first place?
Was the toolpath generated from a spline or a surface in the CAM software?
Splines and arcs will output as line segments in most CAM software, since
there are very few machine controls out there that can handle NURBS input.
(Splines and surfaces are often described mathematically as NURBS entities).
Sometimes, it's difficult to determine if the entity you see on the screen
is an arc or a spline.
Most programs have some king of "analyze" function that will tell you.
Anyway, back to your original question.
A lot of the guys I worked with, preferred to take a simple 2D profile and
program only the first pass.
They would then "loop" the program to create all the subsequent passes.
That gave them only one short chunk of code to edit.
If you have multiple copies of your profile to cut, it makes for a very
economical program, but you have to know how to set up the loop commands in
your particular controller.
Hope this helps
Marcus
-----Original Message-----
From: BillDarby <ddarby@...>
To: CAD_CAM_EDM_DRO@egroups.com <CAD_CAM_EDM_DRO@egroups.com>
Date: Wednesday, November 29, 2000 7:38 AM
Subject: Re: [CAD_CAM_EDM_DRO]A question of size managenent.
>Hi Allin the real world) Now my question is this: This
>
> I recently ran a tool path with 36,000 lines of code. (no big deal
>path was really only 200 sets of (a line an arc and a second line) or[line, arc, line, 200 times]. "If" I could have entered the
>summation of the 160 lines of code representing each arc into one common"arc command" I would have had a total of just 600 lines
>of code.could run the program, but if I wanted to change anything I
>
> As it was, there was not enough memory to edit on the CNC. It
>had to do the change on my off line program on my PC, then reload by floppyto the CNC.
>into arc commands?
> Is there any software that could convert all these line commands
>became smaller my CNC began what appeared like a series of
>Just compelled to ask!!!
>
>Bill Darby
>
>Also (have never seen my CNC do this before) As these [160 line] arcs
>jerky motions as it rounded these corners and sped up when it hit thestraight-away. The cut looked and felt perfect but there
>definitely some jerking going on as the entire mill set up a rocking motionon the wooden floor. I almost thought the CPU was
>bogged down. The feed was set at 32 IPM and dropped to less then 1/3 rd onthe corners.
>
>What do you think is going on??
>
>
>
Discussion Thread
BillDarby
2000-11-29 07:37:31 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Marcus & Eva
2000-11-29 08:20:38 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Joe Vicars
2000-11-29 08:26:06 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Jon Elson
2000-11-29 12:05:43 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-29 13:00:15 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-29 15:36:31 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Fred Smith
2000-11-29 16:06:35 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-29 17:43:57 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
ballendo@y...
2000-11-29 17:58:16 UTC
Re: A question of size managenent.
Marcus & Eva
2000-11-29 20:27:28 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Fred Smith
2000-11-29 20:29:12 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-29 20:54:50 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Jon Elson
2000-11-29 21:08:23 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Jon Elson
2000-11-29 21:40:13 UTC
Re: [CAD_CAM_EDM_DRO] Re: A question of size managenent.
BillDarby
2000-11-29 21:57:01 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Jon Elson
2000-11-29 22:27:15 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Fred Smith
2000-11-29 22:39:28 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-30 06:28:17 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Marcus & Eva
2000-11-30 08:04:52 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Joe Fahy
2000-11-30 08:12:33 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-30 08:26:15 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Fred Smith
2000-11-30 12:02:40 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
Fred Smith
2000-11-30 12:17:10 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
BillDarby
2000-11-30 12:38:23 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.
ballendo@y...
2000-11-30 20:36:20 UTC
Re: A question of size managenent.
Marcus & Eva
2000-11-30 20:59:15 UTC
Re: [CAD_CAM_EDM_DRO]A question of size managenent.