Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
I received this message today when I was trying to edit an exploded view:
What is "improper assembling"? The model had been regenerated without errors.
Thanks, Dale
Solved! Go to Solution.
Files were repaired and return. After one glitch (needing to delete a .xas file from before the repair) and re-verifying the instances in the family table, I no longer get the assembling error.
While .xas files played a small part in the fix, the main problem was corruption of the files.
Thanks, Dale
Currently, I am stepping through the assembly as mentioned by Doug Schaefer.
SUMMARY Improper Assembling Encountered error message
Thanks, Dale
Interesting, I have no recollection of that message. Obviously, I was replying to something in the old system.
Interestingly, you've had this problem before too:
Imporper Assembling encountered.
Clearly, we are both doing something wrong.
Did you see this post pointing to out of date instance accelerators?
I have that in my list of things to look through from searching on "improper assembling".
Unfortunately, stepping through the model didn't work. Everything was green and growing on the way down the tree from the very first item, but when I went back to the exploded view, I got the same error message.
I deleted all the .xas files and verified all the instances and when I went to exploded view, it was still there. Regen's were green to go!
How do I re-create the .xas files?
Dale,
do you really need to have assembly instance accelerator files (.xas) ?
1.] there is config.pro option SAVE_INSTANCE_ACCELERATOR
2.] in CR2 you can click File > Manage File > Instance Accelerator to open following dialog box.
MH
Hi Dale,
You can also try the following:
Set option regen_failure_handling to resolve_mode to expose regeneration failure at file opening.
Target flawed component constraints and define constraints again.
Thanks,
Amit
But there are no regeneration failures. The "stop light" is green.
That's true, interesting. What happens after you set the config and retrieve the model?
When the file was first opened, the "stop light" was yellow, but after one regen, the "stop light" is green.
When I go to open the exploded view, it is acting strange:
No view above the one listed, and activate the one listed, I get the "Improper assembling encountered" again.
Thanks, Dale
Hi Dale,
This is definitely some strange behavior. Especially with the default Explode state missing.
Would you be able to upload your model here, so I can take a look?
Amit
Case 12791042 - if you have access to this.
I have submitted the file to PTC for evaluation. During a WebEx, they were something was wrong with the file.
Case 12791042
Thanks, Dale
Files were repaired and return. After one glitch (needing to delete a .xas file from before the repair) and re-verifying the instances in the family table, I no longer get the assembling error.
While .xas files played a small part in the fix, the main problem was corruption of the files.
Thanks, Dale