HARNESS IN MODEL STATES ADAPTIVE.

[Marcin.Szklarek]

Hi!

I see a potential problem. When I am making harnes adaptive in one of the models states it creates new name. I cannot name it myself, it just creates next iteration of generic harness 2,3,4 etc.

Now, original name I had disappeaars from assemby and in other model states the harness comes under new name  and with implemented changes from that model state. this is completly wrong. How to keep the oldones and how to control naming which is a serious nuisance. Is the only option coping the harnes and reusing? if I make it adaptive it will change it again.

Regards

[Marcin.Szklarek]

Hi!

I managed to rename it ( I propably used the exsisting name, that is why it was rejecting).  The problem of using particular harness remains. Once I make it adaptive it changes name and is replicated in current form in ALL model states. Trying to replace it with the previous one ends with problem that the old one is already assigned and cannot be used to replace. Pacing it as a components does not help much as wires are not attached to pins( or connectors).

How to keep particular iteration of harness with a model state?

Regards

[johnsonshiue]

Hi Marcin,

Cable&Harness, Frame Generator, Tube&Pipe subassemblies do not fully support Model States. Only Master Model State is allowed. Non-master MS cannot be created. Within Master MS, components can be suppressed/unsuppressed.

Also, adaptive can only be active within one MS, not all. I believe you want to use Design View to manage the design variation just like in LOD.

Many thanks!

[ty_shippGBST3]

So for a harness that is model and adaptive, when the assembly changes MS's and the mechanical components move to their new states.. Then wire harness will need to be remodel for the new state. Then you would suppress your old harness? So if we have 10 states, I would need to model the harness 10 times to represent the state?  We cannot allow for adaptivity to stick throughout model states? and the wire be allowed to change in length based on state?

[johnsonshiue]

Hi! Model States does not fully support C&H and other specialized components. You cannot use multiple Model States to drive C&H components. The limitation here is that the C&H component can only be adaptive in one Model State, not multiple Model States. This is a general limitation in Model States regarding adaptive components.

I think you will need to use Design View to configure component visibility (just like LOD Suppress/Unsuppress in 2021 and earlier). When you are done with one variation, you may use iLogic Design Copy or Design Assistant to spawn the particular variation. Please feel free to share an example that you are working on. The forum experts can help explain the behavior more clearly.

Many thanks!