1、Section 1General EnhancementsDevelopment FocusGeneral enhancements in MSC.Patran 2005General EnhancementsMPC NumberingExternally defined Excel spreadsheet (in CSV format) into Field spreadsheetLBC Display EnhancementGeometry IntegrationCAD Import: Create Groups from LayersPro/E Material Import Enhan

2、cementDirect Pro/E MeshCAD ExportDevelopment FocusGeneral enhancements in MSC.Patran 2005 (Cont.)Post-ProcessingResults Title EditorCombined Component PlotsScalar Marker ToolQuick Plot AnimationResults Type Naming ConsolidationPlot Set UtilityAdvanced Surface Mesher Phase IIMPC NumberingThe main pur

3、pose is to avoid any confusion when creating MPCs (RBE2) in MSC.Patran and then generates an input deckIn MSC.Patran the default numbering system labels the first MPC as “MPC 1” and then it might translate the input deck with the RBE being assigned an id 1025Make sure that MPCs created by the user h

4、ave the id which will appear in the input deck assigned to them from the beginning MPC NumberingWarn the user if an attempt is made to renumber the MPCs or Elements in such a way as to cause a renumbering when translated to the MSC.Nastran Input deck MPC NumberingPrior behavior25 elements in the mod

5、elStarting ID for MPC is still 1MPC NumberingPrior behaviorInconsistent MPC nuimbering between Patran & NastranMPC ID started at 1 in Patran databaseMPC ID was offset during the translation.$ Elements and Element Properties for region : propPSHELL 1 1 .08 1 1$ Pset: prop will be imported as: pshell.

6、1CQUAD4 1 1 1 2 8 7CQUAD4 2 1 2 3 9 8CQUAD4 3 1 3 4 10 9CQUAD4 4 1 4 5 11 10CQUAD4 5 1 5 6 12 11CQUAD4 6 1 7 8 14 13CQUAD4 7 1 8 9 15 14CQUAD4 8 1 9 10 16 15CQUAD4 9 1 10 11 17 16CQUAD4 10 1 11 12 18 17CQUAD4 11 1 13 14 20 19CQUAD4 12 1 14 15 21 20CQUAD4 13 1 15 16 22 21CQUAD4 14 1 16 17 23 22CQUAD4

7、 15 1 17 18 24 23CQUAD4 16 1 19 20 26 25CQUAD4 17 1 20 21 27 26CQUAD4 18 1 21 22 28 27CQUAD4 19 1 22 23 29 28CQUAD4 20 1 23 24 30 29CQUAD4 21 1 25 26 32 31CQUAD4 22 1 26 27 33 32CQUAD4 23 1 27 28 34 33CQUAD4 24 1 28 29 35 34CQUAD4 25 1 29 30 36 35$ Referenced Material Records$ Material Record : alum

8、$ Description of Material : Date: 28-Jan-04 Time: 13:51:45MAT1 1 1.+7 .3$ Multipoint Constraints of the Entire Model$ ID conflict : the PATRAN MPC ID was 1RBE2 26 27 123 20 21 22$ ID conflict : the PATRAN MPC ID was 2RBE2 27 15 123 8 9 10 1.-6$ ID conflict : the PATRAN MPC ID was 3RBE2 28 23 123 28

9、29 30 1.-6$ ID conflict : the PATRAN MPC ID was 4RBE2 29 11 123 16 17 18.MPC NumberingNew behaviorMSC.Patran forms simply request the next ID 25 elements in the modelStarting ID for MPC is now default to 26To make it happen please add the following lines to settings.pclpref_env_set_logical( elements

10、_mpcs_share_id_space, TRUE )pref_env_set_logical( elements_mpcs_warn_if_ids_conflict, TRUE )MPC NumberingNew behaviorMPC NumberingNew behaviorConsistent MPC numbering between Patran & NastranNo MPC ID offset during the translationNo more ID Conflict warning message$ Elements and Element Properties f

11、or region : propPSHELL 1 1 .08 1 1$ Pset: prop will be imported as: pshell.1CQUAD4 1 1 1 2 8 7CQUAD4 2 1 2 3 9 8CQUAD4 3 1 3 4 10 9CQUAD4 4 1 4 5 11 10CQUAD4 5 1 5 6 12 11CQUAD4 6 1 7 8 14 13CQUAD4 7 1 8 9 15 14CQUAD4 8 1 9 10 16 15CQUAD4 9 1 10 11 17 16CQUAD4 10 1 11 12 18 17CQUAD4 11 1 13 14 20 19

12、CQUAD4 12 1 14 15 21 20CQUAD4 13 1 15 16 22 21CQUAD4 14 1 16 17 23 22CQUAD4 15 1 17 18 24 23CQUAD4 16 1 19 20 26 25CQUAD4 17 1 20 21 27 26CQUAD4 18 1 21 22 28 27CQUAD4 19 1 22 23 29 28CQUAD4 20 1 23 24 30 29CQUAD4 21 1 25 26 32 31CQUAD4 22 1 26 27 33 32CQUAD4 23 1 27 28 34 33CQUAD4 24 1 28 29 35 34C

13、QUAD4 25 1 29 30 36 35$ Referenced Material Records$ Material Record : alum$ Description of Material : Date: 29-Jan-04 Time: 15:49:04MAT1 1 1.+7 .3$ Multipoint Constraints of the Entire ModelRBE2 26 27 123 20 21 22RBE2 27 15 123 8 9 10 1.-6RBE2 28 23 123 28 29 30 2.-7RBE2 29 11 123 16 17 18MPC Numbe

14、ringIf an attempt is made to renumber MPC with a conflict ID25 elements in the model4 MPC with ID 26 - 29Starting ID for MPC is now 11The following warning message will be issued in the command window$# Warning :$# You have created MPC ID 11 which conflicts with an element of the same ID$# Warning :

15、$# You have created MPC ID 12 which conflicts with an element of the same ID$# Warning :$# You have created MPC ID 13 which conflicts with an element of the same ID$# Warning :$# You have created MPC ID 14 which conflicts with an element of the same ID$# 4 FEM entities renumbered. New IDs are: Mpc 1

16、1:14MPC NumberingMPC ID was again offset during the translation.$ Elements and Element Properties for region : propPSHELL 1 1 .08 1 1$ Pset: prop will be imported as: pshell.1CQUAD4 1 1 1 2 8 7CQUAD4 2 1 2 3 9 8CQUAD4 3 1 3 4 10 9CQUAD4 4 1 4 5 11 10CQUAD4 5 1 5 6 12 11CQUAD4 6 1 7 8 14 13CQUAD4 7 1

17、 8 9 15 14CQUAD4 8 1 9 10 16 15CQUAD4 9 1 10 11 17 16CQUAD4 10 1 11 12 18 17CQUAD4 11 1 13 14 20 19CQUAD4 12 1 14 15 21 20CQUAD4 13 1 15 16 22 21CQUAD4 14 1 16 17 23 22CQUAD4 15 1 17 18 24 23CQUAD4 16 1 19 20 26 25CQUAD4 17 1 20 21 27 26CQUAD4 18 1 21 22 28 27CQUAD4 19 1 22 23 29 28CQUAD4 20 1 23 24

18、 30 29CQUAD4 21 1 25 26 32 31CQUAD4 22 1 26 27 33 32CQUAD4 23 1 27 28 34 33CQUAD4 24 1 28 29 35 34CQUAD4 25 1 29 30 36 35$ Referenced Material Records$ Material Record : alum$ Description of Material : Date: 28-Jan-04 Time: 15:39:48MAT1 1 1.+7 .3$ Multipoint Constraints of the Entire Model$ ID confl

19、ict : the PATRAN MPC ID was 11RBE2 26 27 123 20 21 22$ ID conflict : the PATRAN MPC ID was 12RBE2 27 15 123 8 9 10 1.-6$ ID conflict : the PATRAN MPC ID was 13RBE2 28 23 123 28 29 30 1.-6$ ID conflict : the PATRAN MPC ID was 14RBE2 29 11 123 16 17 18.Field EnhancementImport an externally defined exc

20、el spreadsheet (in CSV format) into a Patran Field spreadsheetExport the field spreadsheet out to an external excel spreadsheetField EnhancementThe spreadsheet input forms now have a new Import/Export. button in the upper rightFor more detailed information and workshop, see Section 4: Field Import a

21、nd ExportLBC Display BehaviorIn previous releases of Patran, LBC display performance could be slow depending on the model sizesFor large models, the time to create an LBC on a large number of entities is usually dominated by the creation and rendering of the display dataPatran automatically created

22、display data when an LBC is created or modifiedThis process could be very time consuming for large modelsLBC Display BehaviorThere were also difficulties with creating or displaying an LBC applied to most/all of a large modelMachine memory gets exhausted and the process abortedLBC Display BehaviorIn

23、 MSC.Patran 2005, LBC display behavior has been enhancedImprove the memory management of the functions in the processFor a model with loads applied to 300,000 elements, memory usage is now reduced by 500 MBLBC Display BehaviorSome LBC display behaviors have also been alteredOnly the requested LBCs w

24、ill be plottedExample: 4 LBCs are in the current LoadcaseOnly 1 LBC is plottedDelete the plotted LBCPrevious release of Patran will re-plot the 3 remaining LBCSIn Patran 2005, remaining LBCs will not reappearLBC Display BehaviorIn previous releases of PatranThe current loadcase has SPC, Pressure, Fo

25、rce and GravityOnly Pressure is plottedDelete PressureOther markers will appearLBC Display BehaviorIn MSC.Patran 2005The current loadcase has SPC, Pressure, Force and GravityOnly Pressure is plottedDelete PressureNothing re-plottedLBC Display BehaviorOther LBC display behaviors changesLBC marker dat

26、a not created if Display/Load/BC/Elem.Props Show LBC/El. Prop Vectors toggle is offPrevious releases of Patran always created marker data for an LBC when the LBC was created, even if the toggle was off and the markers did not display.In Patran 2005, if the toggle is off, no marker data is created or

27、 displayed. A warning message is given, and the user can use LoadsBCs/Plot Markers to display markers at his discretionFor large models, this can greatly speed up the LoadsBCs creation processLBC Display BehaviorIn Patran 2005Show LBC/EL. Prop. Vector OFFApply Pressure to modelLBC Display BehaviorOt

28、her LBC display behaviors changesLBC marker data not created if Display/Load/BC/Elem.Props Show LBC/El. Prop Vectors toggle is offSome Patran users create session files which create hundreds or thousands of LBCs. In previous releases of Patran the creation of marker data for each LBC caused this pro

29、cess to eventually e very slow.In Patran 2005, if the toggle is off, no marker data is created or displayed. So the process does not slow down. Afterwards, the user can use LoadsBCs/Plot Markers to display markers at his discretion.LBC Display BehaviorOther LBC display behaviors changesThe broom (di

30、splay_cleanup() command) really cleans up the LBC displayIn previous releases of Patran the broom removed LBC markers from display, but it left marker data on the database that was no longer being used. LBC Display BehaviorOther LBC display behaviors changesThe broom (display_cleanup() command) real

31、ly cleans up the LBC displayIn Patran 2005, the broom erases the memory of what LBCs were plotted. In the previous scenario, only the new LBC would be plotted when created. Any set of LBCs may still be plotted from LoadsBCs/Plot Markers.The use of the broom before closing a database will result in a

32、 smaller database depending on the number of LBCs displayed.You may notice a longer delay when using the broom if many LBC markers are displayed. However, this time is recovered in the next LBC creation or display.LBC Display BehaviorOther LBC display behaviors changesLBC application region highligh

33、ting controlIn previous releases of Patran when entities were added or removed from the LBC application region select databox to the textbox, the items in the textbox were always highlighted. For large models, this could take a significant amount of time.In Patran 2005, a settings.pcl preference can

34、 be used to control highlighting. If the number of entities in the textbox exceeds “limit” only the select databox items are highlighted.pref_env_set_integer( lbc_app_reg_hilight_limit, limit )Setting the “limit” to 0 (zero) will highlight any number of entitiesIn Patran 2005, the PCL command may al

35、so be used to set “limit”. This command overrides the settings.pcl preference.loadsbcs_selapplreg.set_lbc_app_reg_hilight_lim( limit )LBC Display BehaviorIn previous releases of PatranThe items in the textbox were always highlightedIn Patran 2005pref_env_set_integer( lbc_app_reg_hilight_limit, 2 )Hi

36、ghlighted items are controlledMSC.Patran Geometry IntegrationCAD ImportCreate Groups from LayersThe purpose of this enhancement is to automatically create Patran Groups from Layers when importing geometryThe following CAD sources are supportedCATIA V4CATIA V5UnigraphicsParasolid xmtI-DEASACISIGESExp

37、ress NeutralCAD ImportA new button on the Import Options forms“Create Groups from Layers”CAD ImportCAD ImportClicking on “Create Groups from Layers” button will display a sub-form to allow the user to turn ON or OFF the automatic create of MSC.Patran groups from layersA databox is provided to allow

38、the user to define the Group Name PrefixIf left blank, the group name will be the same as the prefix of the file being importedCAD ImportIf ON (Default), creates a Patran Group for each Layer and adds all geometry on a layer to the Patran Group The group name(s) will be the group name prefix with _L

39、_n appended CAD ImportThe IGES file has 6 layers 1, 2, 3, 4, 5, 6Group name prefix: DEMO_IGESPro/E Material EnhancementThis enhancement will provide additional capability to transfer material data from a Pro/Engineer part (which may include multiple parts and materials from an assembly) to a Patran

40、databaseMaterial data associativity to each part/solid will be maintained Pro/E Material EnhancementThe Pro/Engineer import mechanism will now transfer the following material data from a part:Material name (a standard PTC part parameter)Material properties(standard PTC part parameters)Material Refer

41、ence (a customized extension, using a user defined parameter)Each solid will be associated with the proper material property via an element property record Access of assemblies with multiple parts and instances will be supportedCreating all necessary material and element property information Example

42、 Import 1Standard Pro/E partNo customized extension “PART_SPECIFICATION_NO” The Pro/E part crankshaft.prt contains material, FE_MALL_MMNS, with the following material property values:Elastic Modulus = 1.793000000e+05Poisson Ratio = 0.25Density = 7.358000000e-09Thermal Expansion Coeff = 1.350000000e-

43、05Reference Temperature = 0.Example Import 1Standard Pro/E partNo customized extension “PART_SPECIFICATION_NO” One material extracted from Pro/EOne material & one element property were created in PatranExample Import 1Standard Pro/E partNo customized extension “PART_SPECIFICATION_NO” Example Import

44、1Standard Pro/E partNo customized extension “PART_SPECIFICATION_NO”One element property was created with appropriate solid association Example Import 2Standard Pro/E partWith customized extension “PART_SPECIFICATION_NO” An Externally Defined material will be created, with the following attributes:Na

45、me=material name associated with the Pro/E part Description=Material info extracted from Pro/Engineer on date-time-stamp - MATERIAL=material-name-here and PART_SPECIFICATION_NO=part-spec-here. The Pro/E part tm_mirror_ftg2.prt contains material, ST4340, with the following standard part parameter def

46、ined in Pro/EPART_SPECIFICATION_NOAnd no no other material properties specifiedExample Import 2Standard Pro/E partWith customized extension “PART_SPECIFICATION_NO” One material extracted from Pro/EOne material & one element property were created in PatranExample Import 2Standard Pro/E partWith custo

47、mized extension “PART_SPECIFICATION_NO” Example Import 2Standard Pro/E partWith customized extension “PART_SPECIFICATION_NO”One element property was created with appropriate solid association Direct Pro/E Access & MeshDirect Pro/E access/mesh technology originally developed in MSC.GS-Mesher has been

48、 implemented in MSC.Patran 2005For all Windows and Unix platforms Existing Run GS-Mesher option has been removedCore Patran implementationNo local installation of MSC.GS-Mesher is neededNo MSC.GS-Mesher license is neededYour existing ProENGINEER access license will activate this added featureDirect

49、Pro/E Access & MeshThe Pro/ENGINEER import form now has two selectmenu iconsPro/ENGINEER geometry importDirect Access/MeshNo geometry importDirect Pro/E Access & MeshPro/ENGINEER Geometry ImportExisting capabilitySGM routeParasolid route Direct Pro/E Access & MeshPro/ENGINEER Direct Access/MeshDirec

50、t Access to Pro/E Geometry, without the need of translatorUnnecessary to import the geometry modelModel translation from CAD to CAE has a tendency to cause model errorRevision work (healing etc.) takes so much effortUnnecessary to clean-up the model dataNo-healing & No-stitchingMake a high quality e

51、lementMore effective for large-scale modelTraining freeAssumptions and dependenciesPro/ENGINEER must be able to be executed from the machine where Patran will be run from in order to access the Pro/ENGINEER .prt filesDirect Pro/E Access & MeshPro/ToolkitDirect Access/MeshGeometryPro/ENGINEERMSC.Patr

52、anDirect Pro/E Access & MeshPro/ENGINEER Direct Access/MeshOption to import:Tri surface meshes onlyTet solid meshes onlyBoth tri & tet meshesMesh size controlAvailability element topologyDirect Pro/E Access & MeshPro/ENGINEER Direct Access/Mesh116765 elements were created/importedCAD ExportIn additi

53、on to the Parasolid xmt, STEP, IGES and Patran Neutral, the following common geometry formats can now be exported from MSC.Patran 2005CATIA V4.1.9I-DEAS 10 ACIS 13.0VDA STEP 214CAD ExportCAD ExportThe translators all start with a parasolid transmit file as the input, which is created from within Pat

54、ran. Then the parasolid transmit file is the input to the translators executable which first converts from parasolid to ACIS, then from ACIS to the above mentioned formats The geometric entities supported for export areCurvesSurfacesSolidsCAD ExportIf the parasolid transmit file contains attributes,

55、 the attributes will also be translated.The supported attributes are:For CATIA V4Parasolid Attribute CATIA AttributeRemarksSDL/TYSA_COLOUR Colour value from Element Directory SectionColor attribute SDL/TYSA_NAME String from Data sectionName attributeATTRIB_XPARASOLID_LAYERLayer value from Element Di

56、rectory sectionLayer attributeCAD ExportThe supported attributes are:For I-DEASFor ACISParasolid Attribute I-DEAS AttributeRemarksSDL/TYSA_COLOUR OI_IdeasColorColor attribute SDL/TYSA_NAME OI_Root:UserAttributeDataName attributeATTRIB_XPARASOLID_LAYEROI_Root:UserAttributeDataLayer attributeParasolid

57、 Attribute ACIS AttributeRemarksSDL/TYSA_COLOUR ATTRIB_RGB Color attribute SDL/TYSA_NAME ATTRIB_XACIS_NAMEName attributeATTRIB_XPARASOLID_LAYERATTRIB_XACIS_LAYER Layer attributeCAD ExportThe supported attributes are:For STEP 214Parasolid Attribute STEP AP214 AttributeRemarksSDL/TYSA_COLOUR As colour

58、_rgb entities stored in styled_itemsColor attribute SDL/TYSA_NAMEIn label field of representation_itemsName attributeMSC.Patran Post ProcessingResults Title EditorIn MSC.Patran 2004, a number of keywords have been created which can be used for results title creation Results Title EditorIn MSC.Patran

59、 2005, a comprehensive user interface is implemented to access the definition of title variablesProvides access to all of the results variables and control variables User has the ability to interactively choose the content of the titleAccess to the Results Title Editor form is provided on each Resul

60、ts Display Attributes formFor more detailed information and workshop, see Section 5: Results Title EditorCombined Component PlotsGenerate vector marker plots of combined components (forces/stresses)Previous releases of Patran can only create plots of individual components (XX, YY, ZZ) or the resulta