![]() Import to PDMS does not work and an error message like "Error reading package. Uninstallation and if not remove manually. \bin\applications\Tekla\Model\ExportToPDMS has been removed in Uninstall old installation before installing new. Usually closing Interoperability dialog in PDMS and reopening solves the problemĮxport to PDMS does not work and red color appear in row in Export to PDMS -dialog when new installation taken into use There might be some cases where mapping file is not correctly read, e.g. Mapping dialog in PDMS shows red color lines Problem can be that edited DesignAddins.xml file is not read at all. If so contact your PDMS support to get the modifications done correctly. can be read from a server based on company setup). The company setup might read files from different locations (e.g. Marine,Outfitting -> OutfittingAddins.xml Note: Do not change file name of TS export because it is used in revision handling when updates exported.Īlso important that the TEKLA UDA's (TEKLA_GUID, TEKLA_IFCGUID, TEKLA_VERSION) must be created for PDMS project (see instructions).Īlso important not to use spaces in file name when exported from TSĮdited file named in PDMS is related to module you are running. ![]() Revision handling does not work in PDMS side or error in importing file to PDMS ![]() ![]() Example of mapping row is W8X35 AISC-SPEC/W8x35 To be in PDMS project folder under TS-PDMS/Mapping. Mapping file ProfileMapping.txt is included in installation and it needs ![]() If mapping is found then a profile section is used (SCTN). => TS-PDMS link has a principle that if mapping for profile/part is not found panels/plates (PANE) used in PDMS Tekla sections shown as panels in PDMS but not as native PDMS sections. Having issues with the mapping to native sections ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |