Large assembly problem with the drawings and the level of detail

[Alejandro_Manuel]

Hello to everybody,

first, I want to apologise for my errors in the written english. I trust you can follow my explanation and I hope you can give me a hand to solve this problem.

I prefer to put the problem in a word, with images and a step to step visualitation describing of the problem.

I try to solve the problem for weeks and I can't found the error...

Thanks you very much! 

[HermJan.Otterman]

Hello,

start with making a unique copy of your master assembly, and then do the configurating.

All sheets in one drawing, will cause a slow drawing (and later on problems with PDM if you use that)

saving should not be a problem after making the copy

if you get ....newver, normaly Inventor deletes that after the coppy is ready. in the past I saw this when the data was stored on a verry slow network drive. try this on you C:\, and see what happens.

saving a file is always in the master LOD.

best is not to work with LOD's because they give all kind of problems.....

with code you can set the right LOD again.

What you see in the assembly depends on the design view that is set at the assembly level. so maybe the subassembly is changed but in the designview "default" and in the assembly you see the master desginview of that subassembly. you can see this better by opening the subassembly. if it is changed, you code worked. then you need to change the designview setting in the main assy.

[Alejandro_Manuel]

Thanks for your replay Hans, 

You told me that is better saving without LOD, in a Master mode, and then put a rule that control the differents LOD that are needed in my configuration?

But if I just need that all the time the level of detail were the same custom LOD, have I to do it too?

I have controlled the design views in the differents sub-assemblies and they are all in the correct form.

The problem is just when I save the drawing .idw, that change the LOD of the subassemblies of my model to a master LOD insted of the customisazed LOD.

I don´t know why this is happening. I have done a similar project before this one, and it runs perfectly...

The procedure I follow is this one:

1. I enter in the model and with a form and different ilogic rules, I change differents aspects of my assembly like the lengths or the activation of some parts/assemblies.

2. I save the model when it finished. Until here, there is no problems.

3. I open my drawing, where I have different sheets (between 25-28) with the differents drawings of the model, and I update it.

4. I export the different sheets of my .idw. Until here there isn't any problem.

5. Finally, I save this .idw

6. I reopen my model, and I can see how the LOD have been changed I don't know why, after saving the drawings. I have to enter in all the differents sub-assemblies and putting manually again the correct LOD. This take me several minutes (not so much, maybe 15-20), but its waste time for a thing that its supposed to run automatically. AND I can forget some of the subassemblies without change it, with a mistake that maybe I don't notice...

So, I don't know If I have done it one time correctly with other model, why with this one I have this error and how to fix it! 

Thanks you again Hans! 

[HermJan.Otterman]

If you can manage without LOD's it would be more easy for your self. but if you would stay working with LOD's than you can change them with code..

when you save a part, than that will be in the master LOD.

maybe you can use the option "Link Level Of Detail", with this you can make all LOD's with the same name linked. that way if you choose one in the top assy, the rest will also be set to that one.

one thing to understand is that LOD's may not be used for making configurations!!

the strange thing is that iLogic is miss using LOD's... when you use component.isactive....

LOD's where introduced to make an assembly lighter, not make configurations!, so maybe this is what is causing you problems..

if your drawing views have a different LOD than you model, and you have them both open, you can't save...!

this is one of many things with LOD's, so that's why I don't use them any more..

why it does work in your other project I don't know. maybe less complex?

[Alejandro_Manuel]

That "link Level of Details" sounds nice! Thank you Hans, I will try.

At the moment, I just use LOD because I need them to use the command "component.IsActive". You told me to not use them but, how can I work without LOD and that the command "compnent.IsActive" runs properly? Do you have any sample to share with me in which I can see the way you work?

[HermJan.Otterman]

I use the visible property and then to get the right BOM, I also change the Bom property.

a little the same as iLogic does this but then with out the LOD.