I have a Navisworks export routine setup on a project and everything is working fine except the PDMS attributes tab goes away in Navisworks at some point in the hierarchy. Starting at the top SITE everything works fine for the first six sites or so, and then after that the PDMS tab is gone in Navisworks. I have other projects setup the same way that do not have this issue. Has anyone seen this before? Any idea what could be causing this?
It could be due to the attribute not being available in the attribute dump file. Open attribute dump file and check if the elements which are not showing PDMS tab are listed there or not.
I spot checked the att file and it has the attributes for everything I checked, and also has attributes all the way to the end of the hierarchy, so that's not it.
I tried deleting and recreating the att file and that didn't help.
Really at a loss as to what is causing this issue.
Apart from this, are you dumping all attributes to a single text/att file? If yes, then attribute file size could be another one which may cause this. In few cases, I have seen truncated/partial reading of large text file which causes this (unfortunately I don't have an exact size limit where this may happen but it could be due to several factors such as machine RAM where this conversion is occurring).
I have another project with an att file three times the size of this one running on another machine, with no issues. I tried running this one on that same machine and no change.
I have a feeling it's something to do with an item in the E3D hierarchy but I can't figure out what it would be.
[QUOTE=ambnb;116445]I have another project with an att file three times the size of this one running on another machine, with no issues. I tried running this one on that same machine and no change.
I have a feeling it's something to do with an item in the E3D hierarchy but I can't figure out what it would be.
Thanks for your responses so far!
I have no idea of what that would be either!
My suggestion would be:
1. Create a directory with the same name as RVM file is and in the same export folder.
2. Create attribute dump in zone wise manner i.e. separate text output for each zone.
While this would not most certainly solve the error if your feeling is correct but it will make it easier to pinpoint the zone which causes it. This will give you a smaller subset to investigate. Good luck!
I found if you go back to your model and edit at least one attribute using the attributes window in every instance of PIPE or BRANCH (for example) that you are having an issue with - then re-export the attributes, works for me. This is a very stupid workaround but it does work - give that a try.
I have the same problem
I see this problem is likely because PDMS having trouble to export a large file of attributes when your model becomes larger and more complex.
@annabauman, if you have a large plant model, things can get bad to us, because now we have a major work to do for our model.
Many errors of export ATT files are in pml syntax writefile (unsuported symbols and attribute lenght etc.)
The way is to write new macro for exporting attributes file.
The ATT file structure is simple:
[COLOR=#008000]CADC_Attributes_File v1.0 , start NEW , end END , name_end = , sep &end&
NEW Header Information
END [/COLOR][COLOR=#00ff00]
[/COLOR]
[COLOR=#008000]NEW /BRAN1[/COLOR]
[COLOR=#008000]ATT1:=123[/COLOR]
[COLOR=#008000]ATT2:=123 [/COLOR]
[COLOR=#008000]END[/COLOR]
[COLOR=#008000]NEW BEND 1 of BRANCH /BRAN1 [/COLOR]
[COLOR=#008000]ATT1:=123[/COLOR]
[COLOR=#008000]ATT2:=123[/COLOR]
[COLOR=#008000]END[/COLOR]
+ YOU CAN ADD ANY TEXT TO ANY ELEMENT (IF EXIST IN navis SELECTION TREE - TUBI etc.)
+ YOU CAN ADD PSeudo Att ...
+ you have the attributes under control
To expand on this - and I found that I only have to do this every once in a while.
[HTML]
-- This macro pulls the Name on PIPE and Name on BRAN and populates the Description value for each.
-- This is a workaround to get the PDMS tab to come in when Navisworks file is generated.
-- Can be performed on the entire ZONE.
var !allPipeBran COLLECT ALL (PIPE BRAN) FOR CE
do !refe values !allPipeBran
-- Set CE to Element
$!refe
var !pipnm NAMN
-- check item if it has been named
var !isNamed ISNAMED
if (!isNamed eq 'false') then
Description '-'
else
Description '$!pipnm'
endif
enddo
