Only model in the scope models list can be selected

I'm trying to assemble a subassy which is made almost entirely of
imported parts/features except for a datum plane I added.

Of course in WF2 you have to use this stupid cryptic "find box"
making much more difficult to choose what you want

Rant Mode Off...

I open the find box
click on the arrow to choose a model and I get this error message
when I select the subassy I'm trying to assemble

"Only model in the scope models list can be selected"

this sounds like the reference control box
I've looked at the on the Assy I'm assembling to
plus I've looked at the one in the component window
and neither have anything checked that would restrict this model from
being selected.

Is my problem with reference control or is it something else?

Thanks

Mike

 

You're losing me from the start.

Are you trying to place a subassy or assembling a sub while working in a higher
level assy?

"find box"?

Grasping for a straw Tools > Options, Find, keyword SCOPE, Search Descriptions.

 

--
David Janes

If try seaching for "components" instead of "parts", I doubt that they'll be "out
of scope".

And, I'll agree with nunzer: it's a little vague WHAT you are looking for and why.
So, naturally, I'm just guessing about the "solution" when I haven't even been
told the problem.

 

"find box"?

Come one guys, you know, the dialogue box that replaced query select...
The dialogue box is called the Search Tool

I don't know what that means.
Is there an Options pulldown?

 

Are you trying to place a subassy or assembling a sub while working in a higher

Sorry I forgot to reply to this part...

This sounds like the same thing to me.

I'm trying to place a component, assemble a component that is a subassy
while working in a higher lever assy.

I hope this clarifies it.

Thanks, Mike

 

"Only model in the scope models list can be selected"

Hey David,

I'm not sure what you mean here.
In order to find the axis I want to constrain to in the component I'm
trying to assemble...
I thought I would use the search tool.
I open the search tool
it defaults to the assy I'm assembling to
I need to change it so it will see the features of the component in the
component window
I choose the arrow under the "look in" box
I use pick from list since my component is an assy
when I choose the top assy of the component, I get that error message I
mentioned initially.

I don't understand the "searching for components instead of parts"
statement.
I don't know where or when I'm supposed to do that.

Sorry being so vague I was trying not to type details ad-nauseum as
above

Thanks for your help.

Mike

 

The details of what you are doing and how you be trying to do it are important;
everything, in fact. Bet if you were paying by the minute for support you'd be
articulate and concise.

Assembling the bits and pieces (oops, I made a pun),
it looks like...

- - - - - - - - -
I'm trying to place a component, assemble a component that is a subassy while
working in a higher lever assy.

In order to find the axis I want to constrain to in the component I'm trying to
assemble...

I thought I would use the search tool.

I open the search tool. It defaults to the assy I'm assembling to.

I need to change it so it will see the features of the component in the
component window.

I choose the arrow under the "look in" box.

I use pick from list since my component is an assy when I choose the top assy of
the component, I get that error message I mentioned initially.
- - - - - - - - - - - -

I don't know for sure but think that objects in the component window are
'outside the scope' of the main window Find fuction. Edit > Find cannot be
launched from a menu in the component window. You should be able to go on about
it if you pick the component in the main window.

===========================================
===========================================

 

Well, I was close, Mike. You ever try to do some modelling in assembly!?! Use
other components as references for features you wanted to create in a mating part?
Remember that you can't create the features in the part until you "activate" it,
meaning Pro/e has a subtle, invisible way of turning an assembly component back
into a modifiable part, while it is still in an assembly! I know everyone goes
"Hey, neat!" but I doubt that one in ten realizes what a miracle this is. More to
the point, you're trying to modify subordinate assembly C while you are in
assembly A. Here's the issue: you can't modify assembly C while you're in assembly
A: the out of scope message is telling you that you "can't get there from here".
So, go there, ACTIVATE the component you want to work on and it works, whether the
component is a part or an assembly with lots of other components. If the component
is a part, you can create features; if an assembly, you can assembly stuff or
create assembly features. But it must be ACTIVATED first.

I'm in an assembly. It has 3000 little tits, acting as via fills. I wish to find
and eliminate them, but they are patterned components, part of an assembly that's
been patterned. How to find them: well, right away, I know that, as assembly
members, they're components. So, I DON'T look for parts but components, beccause,
at the assembly level, all I'm concerned with is components (i.e., things that are
part of the assembly ~ they might be parts, they might be features, they might be
other assemblies, but when assembled, they become components. They may have the
same name as the part, but searching for a list of parts and components, gives
different lists. Also, I don't look for parts because a part could be used in
several different subassemblies and assemblies. You might wish to find and deal
with the part at onlly one level and in only one assembly: then you absolutely
need to particularize it as a component. "Part" recognizes XR.PRT in a global,
unassociated context; "Component" recognizes XR.PRT as a member of LXR.ASM and
only as a member 35 of LXR.ASM. "Part" has very broad, general, unlimited scope;
"component" has very limited, restricted scope. Component is so limited, so
restricted that you can eliminate a part, used a thousand times, in a dozen
different places, in only one instance, in only one assembly. The broader the
scope (part), the more "scope" comes into play. Activate a subassembly, find on
"component" and you've automatically narrowed your scope to a range underneath
"scope" error messages. Finding on "components" in activated assemblies brings you
to periscope depth: you're a submarine.

The "details ad-nauseum" are your pain; ours are mind reading and the frustration
of doing a bad job of it, in fact, guessing embarrassingly off the mark. Guys,
don't make us do it; it just wastes time and patience. The other thing I never
wanted to be was a dentist, but sometimes, getting even a glimmer of a hint of an
idea what people are talking about (because they seem like the crazy people,
mumbling, raving incomprehensibly, lunatics) is like pulling teeth. Guys, don't
make us pull teeth. We just want to help with your technical problems in
modelling, assembling and detailing (we might even venture in to mechanisms and
analysis or animation or photo rendering), but we'd like to keep the psychotherapy
to a minimum. A co-worker at Caterpillar Hydraulics convinced me that a most of
the troubleshooting was just calming some intensely frustrated people. When we'd
get a call, he'd just appear: "Ready to go do some pyschotherapy, David?" "Ever
ready, Dr Sanjiv", I'd answer and off we'd go to interview and calm and reassure
the troops (and gather enough data to be able to sort out and remove the
impediment to their productivity.) That's all we're doing here: calming/reassuring
frustrated people (which we know about, first hand) and gathering enough data for
some down home, authentic, lip smackin', finger lickin' good troubleshootin'. (Can
you get too much shrimp and sausage gumbo!?! Only if you're watching your
colesterol.) BTW, Mike, nice job in explaining, second time around. I think I got
it, anyway. But why make us ask twice? We're not PTC tech support who'll sit
there, like phone sex operators, paid by the minute, and ask you questions for an
hour, put you through the mill and nothing comes out the other end. Nobody here
wants to be like that. We want good grist for the mill and out comes a loaf of
fresh, sweet bread. The best we can do.

 

OK let's try this again.
I wasn't trying mod the part.

I had created the axis in the part before I opened the assy.
Once I was in the assy all I wanted to do was contrain the part.

Mike

 

It wouldnt be that your assembly scope isnt set to what you need?
in WF2.
/Tools/Assembly Settings/Reference Control/
then in the objects tab your limiting references to none?

 

It wouldnt be that your assembly scope isnt set to what you need?

Hey Stu,

Thanks for trying to help but I think I laready covered that in my
iniital post.
I'm kinda familiar with that reference control box and it didn't help

Mike

 

Sorry for being so obtuse, Mike, and I sure hope you figured it out on your
own by now. I know we weren't a lot of help. Anyway, apparently, none of us
have run into this kind of message before and suspect that it's a process
problem: something to do with the way you're assembling the component or
selecting the axis. So far as I recall, if you can see it onscreen, you can
pick it and use it in an assembly constraint. Makes me wonder, though, why
you're using the Search function: can you see the axis? if you can't see it,
you can't pick it for an assembly reference (layer problem?). If you can see
it, why're you using the shotgun approach of the Search utility, which will
find WAY too much? So, we're going to play "the tech support challenge"
where I ask you a bunch of questions and you mumble some phrases in response
untill we have enough information to solve the problem. Hey, I'm game, how
about you!

I was offline for a few days, laptop died in the midst of a partitioning
operation, got a used Dell Optiflex GX 260 and spent the last couple days
getting it up and running, including getting email and news functioning. I'm
not back 100% but I'm back Anyone know a good GPU for this machine? Please,
someone suggest a GeForce4 card that I can try to softquadro. I'll be the
guinea pig, the fall guy, the straight man ~ I've been told I'm good at it.
And I'll report the results here.