barwin
Mechanical
- Apr 3, 2007
- 1
Hello there,
Yesterday I discovered very very strange behaviour of Pro/E Wildfire 2.0. Let me explain.
I wanted to create very simple assembly model (let's say box with the hole in the centre and pin) driven by skeleton.
I started with skeleton model in assembly, a few simple curves representing box shape and box height. Then I created family table in that assembly skeleton model - 3 instances - each of them drove different box width, depth and height. Everything worked very well so far. Below you can find the "family table" - it's just an example:
d0 d1 d2
asm_skeleton1 10 10 10
asm_skeleton2 20 20 20
asm_skeleton3 30 30 30
Next step - I created two parts in my assembly - box and pin. Then, in box part, I made by "copy geom" first feature "extern copy geom" with all curves I needed from Skeleton model. After that I created family table in the same part (box if you don't remember
) using 3 different instances f.e.
box1 asm_skeleton1
box2 asm_skeleton2
box3 asm_skeleton3
After verifying and regenerating everything worked well. I closed all models, cleaned the memory and started again.
I opened box part, went to family table window, and tried to open one of the instances. It did opened but the curves from assembly skeleton looked like they were from "Generic asembly skeleton" (Pro/E showed model fully regenerated - green light in the right-bottom corner). I tired to redefine first feature in box part (remember? extern copy geom from assembly skeleton part). After opening "redefine" window I discovered that my curves looked correct, so I closed it and saw that there was yellow light in the corner.
The question is why Pro/E did not remember the skeleton features in my box part? Why I have to open "redefine window" of extern copy geom in the box part? Is it a problem with "config.pro" settings?
Please response as soon as possible.
Many thanks and regards,
Marcin
Yesterday I discovered very very strange behaviour of Pro/E Wildfire 2.0. Let me explain.
I wanted to create very simple assembly model (let's say box with the hole in the centre and pin) driven by skeleton.
I started with skeleton model in assembly, a few simple curves representing box shape and box height. Then I created family table in that assembly skeleton model - 3 instances - each of them drove different box width, depth and height. Everything worked very well so far. Below you can find the "family table" - it's just an example:
d0 d1 d2
asm_skeleton1 10 10 10
asm_skeleton2 20 20 20
asm_skeleton3 30 30 30
Next step - I created two parts in my assembly - box and pin. Then, in box part, I made by "copy geom" first feature "extern copy geom" with all curves I needed from Skeleton model. After that I created family table in the same part (box if you don't remember
) using 3 different instances f.e.box1 asm_skeleton1
box2 asm_skeleton2
box3 asm_skeleton3
After verifying and regenerating everything worked well. I closed all models, cleaned the memory and started again.
I opened box part, went to family table window, and tried to open one of the instances. It did opened but the curves from assembly skeleton looked like they were from "Generic asembly skeleton" (Pro/E showed model fully regenerated - green light in the right-bottom corner). I tired to redefine first feature in box part (remember? extern copy geom from assembly skeleton part). After opening "redefine" window I discovered that my curves looked correct, so I closed it and saw that there was yellow light in the corner.
The question is why Pro/E did not remember the skeleton features in my box part? Why I have to open "redefine window" of extern copy geom in the box part? Is it a problem with "config.pro" settings?
Please response as soon as possible.
Many thanks and regards,
Marcin