Model States and View Reps

[steveh5]

2023.3 Inventor....

Looked at a few discussions from ThomasW and JohnsonS, but not sure those were exactly what I was looking for....

Shouldn't have to use iLogic in my mind for something that should be common, IMHO :-).

So, attempting to put model states into production.

I have an assembly that gets assembled Red and Green. I have two model state and two View Reps. When I activate 45860G, I want the Green View Rep to activate, and when I activate the 45860R, I would like the Red View Rep to activate automatically.

I thought you could control this via the spreadsheet, but not having any luck.

Thought tested this in Beta few years back.

Thoughts?

Thanks in advance...

Steve H.

[Frederick_Law]

MS and View Rep are two different "setting".

MS does not control View Rep.

So 2 MS and 2 View Rep = 4 configs.

Same with Pos Rep.

[Frederick_Law]

MS does control Material.

You can set same Material with different Appearance.

ie Steel Red, Steel Green

[Gabriel_Watson]

You should use only model states to control the changes, either via appearance or the new finish tool (2024):
https://forums.autodesk.com/t5/inventor-forum/model-state-view-in-part/m-p/10319648/highlight/true#M...
Related thread:
https://forums.autodesk.com/t5/inventor-forum/changing-model-states-modifies-view-representations/td...
There is some allusion to iLogic to swap View Reps as you swap Model States too, but that's something to research:
https://forums.autodesk.com/t5/inventor-forum/inventor-2022-model-states-colors/td-p/10401456

[steveh5]

I guess...I'm kind of looking to the future. Our production floor is accessing 3D models directly along with the idw from Vault and the Item. I know the capability is not there today to view different model states, but when it does, I need the user to pick the Red model state and they see the Red View Rep. I don't want them picking the Red model state and seeing the Green View Rep. They have to be tied together. You can't expect a non CAD user to understand how model states and view reps work. They just need to be able to pick a model state and poof they have the correct view rep.

Thinking out loud :-).

Thanks for the responses!

[Gabriel_Watson]

In that sense, remove view reps and simply use model states. If it's a one-to-one relationship, you are not losing any variants.

[mluterman]

OK, this is how I see it (for an assembly):

-Model States control the existence of the physical item (Suppressed or Unsuppressed).

-View Reps control the visiblity of the item (Visible or not) even though it's "still there", appearances, view settings, etc.

-You can't Suppress an item within a subassembly (trick: that's a case where I would turn that one item's visibility off or I would go into that subassy and make a Model State there that I would activate in the upper-level assembly (without resorting to a combination of Model States and View Reps to depict that state of the part).

Long story, short: In my View Reps, I almost right-click/unlock them/make them "All Visible" and re-lock them...then I only use Model States to Suppress or Unsuppress what I want to see (or not)....most of the time.

[johnsonshiue]

Hi Steve,

Such automation can be done using an iLogic rule. Basically on activating a Model State, the rule makes sure the same named Design View Rep is activated. It should be doable now.

Many thanks!

[swalton]

Our production floor likes having the 3d from Vault available too.

We need the ability to show model states, design view reps and position reps from the Vault viewer.  

Currently we are using Design View Reps to show assembly steps and order, color-code hydraulic hoses and electrical cables, highlight welds in hard-to-see areas of the model, etc.  It is easy to show all of those details in our full-color paper prints, but we can't show them in the viewable.

I also want to tie the Model State (which we might use to control BOM) with the View Rep, which we use to control assembly instructions.  

[swalton]

---

@johnsonshiue wrote:

Hi Steve,

Such automation can be done using an iLogic rule. Basically on activating a Model State, the rule makes sure the same named Design View Rep is activated. It should be doable now.

Many thanks!

---

Does iLogic control what is shown using Vault Thin Client? Our need is to control and manage what folks outside of our engineering department can see.

[CGBenner]

@steveh5 Hey Steve, did any of these responses solve this for you?

[steveh5]

Not sure I like the solution, but it should work. Have not yet had a chance to prove out.