Starting in December, we will archive content from the community that is 10 years and older. This FAQ provides more information.
Currently we do have the following issue.
Within the same project some pipe line isometrics are being developed in a smaller scale than the normal.
Attached are two screenshots of the isometrics, 1_ISO the problematic one and 2_ISO the correct one, as well as the corresponding pcf files (renamed as .txt files). Both isometrics have been developed with the same project and iso development settings, the version of Plant 3D that we are using is 2014 with Extension 2.
Any comment or recommendation would be appreciated.
As far as i can see on your snap, the Iso components are in scale, but not the line for piping right? please confirm, and in any case, have your tried checking the line using quick iso (eg. from nozzle to first elbow) to see where the said error occurs? thanks... ill see more to your problem , thanks.
Best Regards,
Pat Andres
Autodesk Expert Elite
Plant 3D Administrator
GHD Manila
Hi,
Thank you for your response.
I did quick iso as well as iso with break points.
In the attached word file you may see the different ISOs that were developed.
What I noticed is that each time an elbow ISO is produced I get a warning as seen in teh attached txt file, not sure what this is for.
I see, just a suggestion, can you use nodes( weld points) as break points? or use quickiso and select from weldpoint to next weldpoin (eg. spool of first pipe to first elbow) so you can segregate and check much accurately. as per your iso, i think the one with problem is the ISO V, not much sure because of the breaks you have done is in the middle of the pipes, which you must break exactly at the joints which in your case are the welds. We need that to see if the connections between your pipes and fittings are of good integrity, which if yes, you will see the continuation component's ISO symbol correctly( Eg. the whole elbow, or the whole valve and not just a hidden line). Another thing is, if your piping is too far form the Origin 0,0,0 copy that sample piping to a coordinate near 0,0,0 then try to extract an Iso if it still produce same output. Thanks
Best Regards,
Pat Andres
Autodesk Expert Elite
Plant 3D Administrator
GHD Manila
Hi,
Attached are the ISOs produced with the break points placed at nodes level.
During the process of the process of the ISOs production a warning message similar to the one mentioned in my previpous post came up.
I’m not sure in this discussion what is meant by “scale” exactly. In Plant 3D, Isometrics are not drawn to any scale such as 1/8” = 1’-0”. I assume you’re talking about the amount of information per Isometric sheet / Blank space on the sheet (?). I may be missing something...
What is the exact output or end result you’re after? Looking at the ISO Test.pdf you posted, what specifically are you wanting to change there?
In any event, in addition to Pat’s helpful posts…a few more things to try if you haven’t yet:
If my reply post was helpful, please give a "Kudos" or mark the "Accept as Solution" button below (or both).
Hi,
The issue is how the info are being deployed in the sheet.
The ISO Test.pdf is the output having use the ISO break points, if we produce this ISO without the break points the output we get is as seen in the attached ISO Test 1.pdf file.
The actual problem is that the info is not spread equally in all the sheet area.
Regarding your recommendations we have done all of them, we used more styles (OOTB), checked the piping model, purged local cach, etc.
At this point need to mention that other lines within the same project and using the same ISO style, are being produced OK.
Also the proplematic pipe in other machine, using Plant 3D Ultimate, is being produced OK.
Thank you,
You say running Isometrics on all other lines works fine. And even this line runs correctly from another machine (I assume using the same exact Iso style). That’s strange; there should be no difference. Is the other computer using the exact same version of Plant 3D? Same extension and/or service pack?
Did you purge the local data cache on each machine working in the project?
It may be that there is just something wrong with that pipe as a 3D component, maybe some data corruption. Was that pipe native Plant 3D pipe or imported from a different source? Can you re-model that one problem pipe?
Can't find what you're looking for? Ask the community or share your knowledge.