Sirius2
Mechanical
- Dec 15, 2002
- 67
Heres a question for you, lol.
We currently use an antiquated 2d system and I want the office to get something better for 2d mechanical design. AutoCad LT is perfect for our requirements (Mechanical is the best, but the budget is stupendously tight).
The dilemma is this:
We currently cant use/create views or manipulate 3d geometery for our 2d designs and have to time consumingly try and (very basicly) get the main bits drawn from scratch ourselves. This is often fraught with errors and is basicly a poor looking job.
I know autocad LT is not for 3d, but we generally only need to construct our fixtures or whatever around customer supplied information. LT has wireframe, a 3d UCS and the oh so important 'align' command.
This information sent is not solid data, but a badly drawn mismash of wireframe and some surface data. We dont always get paper prints, so we have to rely on the CAD data.
*right, on to the question* lol.
I was wondering about the possibility of opening the iges files of wireframe and surface data in Mechanical Desktop and saving them as an AutoCad file. This would open in LT as 'proxy objects'. So far so good.
The problem is now drawing the fixture around the data.
I was hoping to be able to draw the job in Paperspace, using views/viewports etc aligned up etc. The centers/endpoints of model geometry are still able to be picked up in paperspace even when viewports are not activated. The viewports (ie front top left view) would all be corectly aligned and scale to each other and locked.
Can you realisticly do this?. The only trouble I forsee is that when the job is bigger than the largest paper size. If we had to scale the component views in the viewports to half, our fixture would have to be drawn half size too....which isnt good.
Its just a crazy idea, yet it could save us so much time and work from what we have now. I know the proxy thing works etc, but the limitations of the drawing area in paperspace is throwing a spanner in the works.
Is there any further pitfalls or advice on this?
Thanks a lot for any response on this
Sirius.
We currently use an antiquated 2d system and I want the office to get something better for 2d mechanical design. AutoCad LT is perfect for our requirements (Mechanical is the best, but the budget is stupendously tight).
The dilemma is this:
We currently cant use/create views or manipulate 3d geometery for our 2d designs and have to time consumingly try and (very basicly) get the main bits drawn from scratch ourselves. This is often fraught with errors and is basicly a poor looking job.
I know autocad LT is not for 3d, but we generally only need to construct our fixtures or whatever around customer supplied information. LT has wireframe, a 3d UCS and the oh so important 'align' command.
This information sent is not solid data, but a badly drawn mismash of wireframe and some surface data. We dont always get paper prints, so we have to rely on the CAD data.
*right, on to the question* lol.
I was wondering about the possibility of opening the iges files of wireframe and surface data in Mechanical Desktop and saving them as an AutoCad file. This would open in LT as 'proxy objects'. So far so good.
The problem is now drawing the fixture around the data.
I was hoping to be able to draw the job in Paperspace, using views/viewports etc aligned up etc. The centers/endpoints of model geometry are still able to be picked up in paperspace even when viewports are not activated. The viewports (ie front top left view) would all be corectly aligned and scale to each other and locked.
Can you realisticly do this?. The only trouble I forsee is that when the job is bigger than the largest paper size. If we had to scale the component views in the viewports to half, our fixture would have to be drawn half size too....which isnt good.
Its just a crazy idea, yet it could save us so much time and work from what we have now. I know the proxy thing works etc, but the limitations of the drawing area in paperspace is throwing a spanner in the works.
Is there any further pitfalls or advice on this?
Thanks a lot for any response on this
Sirius.