Community
Inventor Forum
Welcome to Autodesk’s Inventor Forums. Share your knowledge, ask questions, and explore popular Inventor topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Semi-Isolated Confustion?!?

4 REPLIES 4
Reply
Message 1 of 5
Anonymous
157 Views, 4 Replies

Semi-Isolated Confustion?!?

I've read the file on the IV6 CD on Project files & Concurrent Design. I
have set up a project file and am trying to use it in semi-isolated mode to
do ECN work. Some things I don't understand are:

1. When I open a file and check it out, in my Workspace, IV brings the
whole folder tree with the file which makes it inconvenient to have to dig
down 4 layers to selcet the file that I want. Why does it do this and can I
tell it to only bring the file and not the folders?

2. In order to fix the problems desribed in 1, I cut and paste the files
into the workspace file and delete extra folders. IV doesn't like that much
especially with .idw files.

3. If a file status is unresolved, I can put a place holder in one of the
Workspace files, but not in their sub-directories. What a pain. I could
list every directory and sub-directory as a workspace, but doesn't that
defeat the whole purpose of a filing systems?

4. I have a nut that is in a workgroup file, & that nut is used in a
chamber assembly that's in a library file. Whenever I open an assembly
containing the chamber, IV can't find the nut, so I locate it, and save the
assembly. Sure enough, the next time I open the assembly, IV still can't
find that same nut.

I'm glad to see AutoDesk attempting a vault-type drawing system, but I don't
think they understand how a user in an engineering/manufacturing enviroment
works.

Please help if you can.
4 REPLIES 4
Message 2 of 5
Anonymous
in reply to: Anonymous

Look within...
> 1. When I open a file and check it out, in my Workspace, IV brings the
> whole folder tree with the file which makes it inconvenient to have to dig
> down 4 layers to selcet the file that I want. Why does it do this and can
I
> tell it to only bring the file and not the folders?

I *think* that if you list all the subfolders in the Workgroup in your
project file, this won't happen. I'm not sure on this one though. If you
add all the subfolders to the project file, they'll appear red, but it's
just a warning that it's a nested folder. It is crucially important that
the subfolders appear BEFORE their parent.

> 2. In order to fix the problems desribed in 1, I cut and paste the files
> into the workspace file and delete extra folders. IV doesn't like that
much
> especially with .idw files.

Yes, because the referencing file is looking for the referenced file in the
subfolder that it was in, and you're moving it. Big no-no.

> 3. If a file status is unresolved, I can put a place holder in one of the
> Workspace files, but not in their sub-directories. What a pain. I could
> list every directory and sub-directory as a workspace, but doesn't that
> defeat the whole purpose of a filing systems?

Again, adding the subfolder paths to the project will resolve this. But
again, make sure the subfolders appear before their parent. Inventor will
place the placeholder file in the wrong location otherwise. I call it a
bug - Autodesk just says "don't do that then."

> 4. I have a nut that is in a workgroup file, & that nut is used in a
> chamber assembly that's in a library file. Whenever I open an assembly
> containing the chamber, IV can't find the nut, so I locate it, and save
the
> assembly. Sure enough, the next time I open the assembly, IV still can't
> find that same nut.

Inventor will not retain the change to the reference in the library
assembly, because libraries are read-only. If you create a temporary
project in which the library is listed in the Workgroup, then you can open
the assembly, locate the nut, and the change to the reference will hold.
But I don't think it's advisable for a library file to reference something
outside of the library. I'd suggest moving that nut into the library so you
don't have problems later on.
Message 3 of 5
Anonymous
in reply to: Anonymous

Thanks for confirming what I thought was happening.

This exemplifies what I was saying earlier about how AutoDesk doesn't
understand our needs. I can't just up & move that nut to the library file.
How would all the other assemblies that use it find it. Also, its part
number 550033 designates that it must be in the 550000-551000 folder.

Does anyone else design and draw a new product using generic file names in
an isolated folder and then, when the design is complete, assing part
numbers and move the files to the appropriate folders in an archive? Or it
is just me?

"DJSpaceMouse" wrote in message
news:2250DA97537776CAAEB8C6059B7612B5@in.WebX.maYIadrTaRb...
> Look within...
> > 1. When I open a file and check it out, in my Workspace, IV brings the
> > whole folder tree with the file which makes it inconvenient to have to
dig
> > down 4 layers to selcet the file that I want. Why does it do this and
can
> I
> > tell it to only bring the file and not the folders?
>
> I *think* that if you list all the subfolders in the Workgroup in your
> project file, this won't happen. I'm not sure on this one though. If you
> add all the subfolders to the project file, they'll appear red, but it's
> just a warning that it's a nested folder. It is crucially important that
> the subfolders appear BEFORE their parent.
>
> > 2. In order to fix the problems desribed in 1, I cut and paste the
files
> > into the workspace file and delete extra folders. IV doesn't like that
> much
> > especially with .idw files.
>
> Yes, because the referencing file is looking for the referenced file in
the
> subfolder that it was in, and you're moving it. Big no-no.
>
> > 3. If a file status is unresolved, I can put a place holder in one of
the
> > Workspace files, but not in their sub-directories. What a pain. I
could
> > list every directory and sub-directory as a workspace, but doesn't that
> > defeat the whole purpose of a filing systems?
>
> Again, adding the subfolder paths to the project will resolve this. But
> again, make sure the subfolders appear before their parent. Inventor will
> place the placeholder file in the wrong location otherwise. I call it a
> bug - Autodesk just says "don't do that then."
>
> > 4. I have a nut that is in a workgroup file, & that nut is used in a
> > chamber assembly that's in a library file. Whenever I open an assembly
> > containing the chamber, IV can't find the nut, so I locate it, and save
> the
> > assembly. Sure enough, the next time I open the assembly, IV still
can't
> > find that same nut.
>
> Inventor will not retain the change to the reference in the library
> assembly, because libraries are read-only. If you create a temporary
> project in which the library is listed in the Workgroup, then you can open
> the assembly, locate the nut, and the change to the reference will hold.
> But I don't think it's advisable for a library file to reference something
> outside of the library. I'd suggest moving that nut into the library so
you
> don't have problems later on.
>
>
Message 4 of 5
Anonymous
in reply to: Anonymous

> I can't just up & move that nut to the library file.
> How would all the other assemblies that use it find it.

If you move the nut with the Design Assistant and search for all files that
reference it and update them as well, you won't have any problems with any
assemblies, drawings, etc. finding the reference.

> Does anyone else design and draw a new product using generic file names in
> an isolated folder and then, when the design is complete, assing part
> numbers and move the files to the appropriate folders in an archive? Or
it
> is just me?

I don't, personally. I try to give my parts and assemblies meaningful names
from the start so I know what part is what while I'm working on the design.
I know what "Pin 0.5x2.5.ipt" is - I have no clue what "Part14.ipt" is.
Message 5 of 5
Anonymous
in reply to: Anonymous

Yea, I don't use a generic name like "Part14.ipt", I use something like
"beam side plate.ipt". But when the design is complete, then I need to
change the name to something like 501452.ipt and store it in the file with
all the other parts that begin with 501... I don't like to assign numbers
like these in the beginning because I don't know if that part will make it
to the final assembly. Do you end up changing "Pin 1.5x2.5.ipt" to some
part number?

"DJSpaceMouse" wrote in message
news:AD62EE7A556DF9C562ADA1839A22A519@in.WebX.maYIadrTaRb...
> > I can't just up & move that nut to the library file.
> > How would all the other assemblies that use it find it.
>
> If you move the nut with the Design Assistant and search for all files
that
> reference it and update them as well, you won't have any problems with any
> assemblies, drawings, etc. finding the reference.
>
> > Does anyone else design and draw a new product using generic file names
in
> > an isolated folder and then, when the design is complete, assing part
> > numbers and move the files to the appropriate folders in an archive? Or
> it
> > is just me?
>
> I don't, personally. I try to give my parts and assemblies meaningful
names
> from the start so I know what part is what while I'm working on the
design.
> I know what "Pin 0.5x2.5.ipt" is - I have no clue what "Part14.ipt" is.
>
>

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report