Software FAQs

Solid Edge

CAE

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Simcenter 3D

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

Simcenter Femap

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Load More

NX CAD

CAE

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Simcenter 3D

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

Simcenter Femap

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Load More

Simcenter 3D

CAE

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Simcenter 3D

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

Simcenter Femap

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Load More

Simcenter Femap

CAE

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Simcenter 3D

Simcenter 3D Motion software is an integrated, associative CAE tool that provides comprehensive mechanism modeling and analysis capabilities. You can use Motion to simulate and evaluate mechanical systems.

Categories: CAE, Simcenter 3D
  • A motion body represents a rigid body in the mechanism that moves. When you create a motion body, you specify the geometry that defines that motion body. A motion body can be:
    • An assembly component (recommended)
    • A set of solid bodies, curves, points, and so on.
Categories: CAE, Simcenter 3D
  • Joints represent connections between motion bodies.
  • Without any constraints, motion bodies in a mechanism “float” in space with six degrees of freedom (DOF):
    • Three degrees of translation (the X, Y, and Z directions) 
    • Three degrees of rotation (about the X, Y, and Z axes)
Categories: CAE, Simcenter 3D

Support Center->NX->Documentation-> NX series-> Simcenter 3D motion

Categories: CAE, Simcenter 3D
  • A joint driver assigns motion to a revolute, slider, or cylindrical joint or a point-on-curve constraint. It can only be a point on a rigid curve. 
  • Motion body drivers are available only with the Simcenter 3D Motion Solver.
  • These types of motion body drivers are available: 
    • None (lets you remove an existing driver from a motion body)
    • Polynomial 
    • Harmonic 
    • Function 
    • Control 
    • Profile
Categories: CAE, Simcenter 3D

Simcenter Femap

Femap has a built in associativity feature when creating entities. It can be difficult to recognize where the associativity is with a given entity. If the entity needs to absolutely be deleted such as a line, one method to remove the associativity is to use Modify > Associativity and remove the associativity of the nodes or elements from that particular entity. From there, the User can delete the entity using the Delete pulldown.

Categories: CAE, Simcenter Femap
  • Users can quickly create a custom toolbar by right clicking in any of the toolbar space and selecting the “Customize” option which will open a new dialog window. Press “New” and specify the toolbar name. Users can then drag commands to the new custom toolbar to populate it by clicking on the “Commands” tab. Users can also add Keyboard shortcuts in the “Keyboard” tab. Users can also add custom API functions in the “User Commands” tab. Once satisfied with the toolbar, click “Close”.
  • If users wish to turn off their new custom toolbar, they can right click the “Customize” option in the toolbar space and check the box to hide it under the “Toolbars” tab
Categories: CAE, Simcenter Femap
  • FEMAP 11.1 and later add a new graphics architecture to improve graphics performance of both the initial draw and dynamic rotation. This requires OpenGL 4.2. If your graphics card supports OpenGL 4.2, FEMAP will have a message in the message window such as:
  • Full OpenGL Hardware Acceleration (Double Buffered).
  • Your graphics card supports OpenGL 4.2.
  • If your graphics card doesn’t support OpenGL 4.2 or later, check with your graphics card vendor to see if there is an updated graphics driver with OpenGL 4.2 support. If your graphics card does support OpenGL 4.2 or later, you can turn on Performance Graphics.
    1. Choose File > Preferences.
    2. Select the Graphics tab.
    3. Check the box next to Performance Graphics.
    4. Click OK.
Categories: CAE, Simcenter Femap

In FEMAP 11.0, models with composite results may not import results when using the new Attach Results option. To work around this, use Import Results. This issue is corrected in FEMAP 11.1.

Categories: CAE, Simcenter Femap

FEMAP holds parts of your model and results in memory. To reduce the amount of memory FEMAP uses to do this, choose File > Preferences and click the Database tab. In the Database Performance group, reduce the Database Memory Limit by dragging the slider to the left. This decreases the amount of memory FEMAP uses for holding parts of your model and causes FEMAP to rely more on swapping to the scratch file. Note that this does not control the total amount of memory FEMAP uses, which includes commands, holding data in the data table, and drawing your model.

Categories: CAE, Simcenter Femap

In FEMAP, choose Tools > Data Table to show the Data Table if it is not showing already. Click the Unlock button to unlock the Data Table and select the entities you want to add. Click the Show/Hide Columns button to change which columns are included. For elements, C1-Cn represent the corner nodes and M1-Mn represent the midside nodes. Out-C1 etc represents the current output at the corresponding corner node. Once you have the data table set up how you want it, you can either click Copy to Clipboard and paste it to an Excel file, or click Save to File to save it to a .csv file.

Categories: CAE, Simcenter Femap
  • Geometry: *.asm* , *.catp*, *.dlv, *.dxf, *.exp, *.igs, *.jt, *.mdl, *.model, *.par, *.prt*, *.psm, *.pwd, *.sat, *.sldasm, *.sldprt, *.step, *.stl, *.stp, *.x_b, *.x_t, *.xmt_txt
  • Databases: *.ans, *.bdf, *.blk, *.cae, *.cdb, *.d, *.dat, *.fno, *.inp, *.nas, *.neu, *.neu, *.nid, *.out, *.pat, *.sdb, *.t16, *.unv, d3*
  • Results: *.cae, *.csv, *.dis, *.els, *.f06, *.f11, *.fil, *.fin, *.fno, *.lis, *.neu, *.nod, *.onf, *.op2, *.out2, *.prt, *.rst, *.rth, *.sdb, *.sof, *.t16, *.xdb, d3*

Categories: CAE, Simcenter Femap

The best element type depends on the geometric shape of the part, but, typically a part modeled with lower-dimensional elements (1D or 2D) will yield more accurate results and faster processing speeds. With that said, 3D elements are necessary when modeling parts with complex features. In the end, each element type has its advantages and there is not a best type for all situations.

Categories: CAE, Simcenter Femap

FEMAP has a tool that will measure your mesh based on certain criteria or ratios such as aspect or skew. The tool can be found under the drop down menu Tools > Check > Element Quality.

Categories: CAE, Simcenter Femap

Groups and layers are very similar functions that are fundamental for having an organized model.  The feature that separates the two methods is that an entity (ie. nodes, elements) can only be in one layer at a time while groups can have overlapping entities. Both tools can be used over the other, and in the end it comes down to personal preference.

Categories: CAE, Simcenter Femap

The Data Table in FEMAP is used to look at model data in a tabulated format. For nodes and elements, it can show geometric locations, resultant displacements, resultant stresses, and more. It is an easy way to collectively look at the model’s computed data. The Data Table can also be exported to the following file formats: *.txt, *.csv, *.rtf.

Categories: CAE, Simcenter Femap
  • Some customers have noted that CBUSH spring forces or Grid Point Force Balance data (used for Freebody) was not appearing in FEMAP when the model was run from FEMAP, but the did show up when manually importing the results.
  • The workaround is to manually import the .op2 file (File > Import > Analysis Results). There is no more work being done to add new features to the .f06 file reader, only to the .op2 file reader. Starting with 11.1, the plan is to only use the .f06 file reader when the results destination is set to “1..Print Only”. The .op2 file reader will be used wen Results Destination is set to “3..Print and PostProcess” and you will still get all of the info, warning and error messages along with other stuff from the .f06 file (for instance, modal participation factors) which can’t be found in the .op2 or .xdb file.
  • Up through FEMAP 11.0, if you have the Results Destination set to “0..Default”, “2..PostProcess”, “5..Punch and Postprocess”, or “6..XDB”, FEMAP will read the results data out of the .op2 file (or the .xdb file when “6..XDB” is used). In this situation, all the results will be read. However, if you set the Results Destination to “3..Print and PostProcess”, FEMAP will put the results into both the .f06 files and the .op2 file. When FEMAP does the auto import of results, if it sees results in the .f06 file, it uses that for all results, and never imports results from the .op2 file. The problem happens because the FEMAP .f06 file reader, being older legacy code, does not support some items, including CBUSH forces or Grid Point Force data.
Categories: CAE, Simcenter Femap

On the FEMAP Documentation page, click What’s New in FEMAP vX.

Categories: CAE, Simcenter Femap

MSC input is a bit different, but it’s not to hard to convert the input file with a text editor:

NXMSCFunctionNotesConversion
BCBODY1Defines deformable bodyReferences BSURFCreate a separate BCBODY1 for each BSURF. To keep it simple, use the same id as the BSURFBCBODY1,id,,2D or 3D,,bsurf-id
BCTSET or BGSETBCTABLE1/ BCONECTDefines connection between bodiesBCONECT references BCONPRG/BCONPRP, BCTABL1 references individual BCONECT contact pairsBreak BCTSET/BGSET up into individual pairs to convert to BCONECTs. This uses the ids of BCBODY1, not BSURF. If you used the same ids for BCBODY1 as BSURF, then you shouldn’t need to worry about ids. Give each BCONECT pair an ID. Create a BCTABL1 that lists the ids of the BCONECT pairs. If you have friction, that needs to go on the BCONPRP, which is otherwise optional.BCONECT,pair-id,bconprg-id,bconprp-id,slave-id,master-idBCTABL1,table-id,pair-id1,pair-id2,pair-id3,etc.
BCRPARABCONPRG/ BCONPRPDefines top/bottom and offset for NXBCONPRG,id,,IGLUE,3 turns on glued contact for the BCONECT.BCONPRP,id,,FRIC,value turns on friction for the BCONECT.BCONPRG also has options for top vs. bottom face, and shell thickness
BSURFBSURFDefines elements that make up contact surfaceNo change neededNo change needed
Categories: CAE, Simcenter Femap

Load More