iso

iso

Anonymous
Not applicable
1,165 Views
7 Replies
Message 1 of 8

iso

Anonymous
Not applicable

My line number changes at a butterfly valve. The valve has the line number of (iso2).

But when I now produce my iso's, the valve stands on both iso's and it also comes on both bill of materials.

In my setting of this project the iso splits by linenumber (what he does with the other line numbers in this project)

 

But at the flange you can see on the iso1 that he place COI, but then he shows the valve and his opposite flange. but that only has to come on iso2.

Can I do something else to change this accept for changing the iso by hand? 

0 Likes
1,166 Views
7 Replies
Replies (7)
Message 2 of 8

Anonymous
Not applicable

I noticed a spec change in the valve configuration and line number. One thing to check it to make sure that your valve is tagged with the correct spec and all bolting and gasket material is the same that is connecting them.

0 Likes
Message 3 of 8

Anonymous
Not applicable

That was indeed so for that line number thank you.

But I still have the same problem with other line numbers. And there is everything tagged correctly?

0 Likes
Message 4 of 8

ryan.bales
Autodesk Support
Autodesk Support

What version of Plant 3D are you using?



Ryan Bales
Fusion 360 Product Support
0 Likes
Message 5 of 8

Anonymous
Not applicable

I'm using Plant 3D 2016

0 Likes
Message 6 of 8

ryan.bales
Autodesk Support
Autodesk Support

Okay, there was a defect with 2016 in which some components were randomly shown on both sides. This was resolved in Plant 3D 2017.1 or update 1. I'll DM you some more information on it.



Ryan Bales
Fusion 360 Product Support
0 Likes
Message 7 of 8

EricNyh
Collaborator
Collaborator

@ryan.bales wrote:

Okay, there was a defect with 2016 in which some components were randomly shown on both sides. This was resolved in Plant 3D 2017.1 or update 1. I'll DM you some more information on it.


Was there a fix for 2016???

0 Likes
Message 8 of 8

ryan.bales
Autodesk Support
Autodesk Support

No, it was verified through 2017 and resolved in update 1 for 2017 or 2017.1. 



Ryan Bales
Fusion 360 Product Support
0 Likes