• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Autodesk Simulation Mechanical and Multiphysics

    Reply
    Member
    Posts: 5
    Registered: ‎09-28-2007

    Terminal Error: FEM2ESH#82

    203 Views, 3 Replies
    02-08-2013 12:31 PM

    I just migrated to 2013 and installed SP2.  I am trying to run a transient heat transfer analysis on a scenario that ran under 2012 earlier this week.  I do not know what to do to fix it.  Below is the log data:

     

    fem2esh - Make esh file from fem file for a specified design scenario
    Version 2013.02.00.0010-W64/X64 02-Oct-2012
    Copyright (c) 2012, Autodesk, Inc. All rights reserved.

      Version of fem2esh.exe          : 2013.02000010
      Version of dcx1-win-x64.dll     : 2013.02000010
      Version of femapi-win-x64.dll   : 2013.02000010
      Version of agsdb_ar-win-x64.dll : 2013.02000010
      Version of tsx2tsy.exe          : 2013.02000010

      Input Model     : C:\Simulation files\V2-2 SIC JOINT TEMP STUDY LAP JOINT GAP.ds_data\46\ds
      Input File      : C:\Simulation files\V2-2 SIC JOINT TEMP STUDY LAP JOINT GAP.fem
      Output File     : C:\Simulation files\V2-2 SIC JOINT TEMP STUDY LAP JOINT GAP.ds_data\46\ds.mod\group.esh
      Log File        : C:\Simulation files\V2-2 SIC JOINT TEMP STUDY LAP JOINT GAP.ds_data\46\ds.mod\group.ldx
      Design scenario : 46
      Analysis type   : Heat Transfer
      Start time      : 2013/02/08-15:02:47 

      --- Get 12 active element parts in range [1, 13] from fem file
      --- 2 enabled L&C groups are defined
      --- No Mean_delta_t defined in part 1
      --- No Mean_delta_t defined in part 2
      --- No Mean_delta_t defined in part 3
      --- No Mean_delta_t defined in part 4
      --- No Mean_delta_t defined in part 5
      --- No Mean_delta_t defined in part 7
      --- No Mean_delta_t defined in part 8
      --- No Mean_delta_t defined in part 9
      --- No Mean_delta_t defined in part 10
      --- No Mean_delta_t defined in part 11
      --- No Mean_delta_t defined in part 12
      --- No Mean_delta_t defined in part 13
      --- Get 84912 points defined in range [1, 562896] from fem file
      Mesh 3 line based element parts...
      --- Part3: make local points and lines for meshing...
      --- Meshing based on 4106 lines for gType=1 elements...
      --- made 1960 elements with element_type=40
      --- Part5: make local points and lines for meshing...
      --- Meshing based on 6411 lines for gType=1 elements...
      --- made 3021 elements with element_type=40
      --- Part12: make local points and lines for meshing...
      --- Meshing based on 194 lines for gType=1 elements...
      --- made 78 elements with element_type=40
      Calling the Surface Topology Generator (tsx2tsy)...
      tsx2tsy: Update part surface contact/bonding data (duration=1 sec.)
      --- No mid-side node required
      Set up FEM points and B.C. by connected elements...
      --- Load up 482 non-trivial coincident nodal pairs of 482 in FEM
      Consolidate points between parts using contact definitions...
      --- 184 out of 184 contact definitions have been used in bonding nodes
      Compress FEM points to ESH nodes...
      --- Found 28294 independent nodes
      --- 28294 mesh nodes formed from 84912 FEM points
      Output the mapping arrays of FEM points to FEA nodes...
      Loop 1 contact pairs to build enabled contacts...
      Writing to ESH file in phase I (nodes & elements)...
      --- Part1: type=40, flags=131, meshType=2, elements=5484, maximumID=5484
      --- Part2: type=40, flags=3, meshType=2, elements=920, maximumID=920
      --- Part3: type=40, flags=167, meshType=1, elements=1960, maximumID=1960
      --- Part4: type=40, flags=135, meshType=2, elements=3328, maximumID=3328
      --- Part5: type=40, flags=163, meshType=1, elements=3021, maximumID=3021
      --- Part7: type=40, flags=7, meshType=2, elements=756, maximumID=756
      --- Part8: type=40, flags=3, meshType=2, elements=3600, maximumID=3600
      --- Part9: type=40, flags=7, meshType=2, elements=2146, maximumID=2146
      --- Part10: type=40, flags=3, meshType=2, elements=2862, maximumID=2862
      --- Part11: type=40, flags=3, meshType=2, elements=576, maximumID=576
      --- Part12: type=40, flags=163, meshType=1, elements=78, maximumID=78
      --- Part13: type=40, flags=7, meshType=2, elements=656, maximumID=656
      Working on MPCs...
      --- Made total 3641 enabled MPCs.
      Writing to ESH file in phase II (FEA objects)...

      In working on FEM file for a FEA model
      Terminal Error: FEM2ESH#82
        FEM_ERROR_OBTAIN_OBJECT
    2013/02/08-15:02:49

     

    Thanks,

    Please use plain text.
    Member
    Posts: 5
    Registered: ‎09-28-2007

    Re: Terminal Error: FEM2ESH#82

    02-08-2013 01:15 PM in reply to: cummingsga

    It appears the problem is a part that I suppressed.  If I un-supress it, the model runs.  If it is suppressed I get the error.  The suppressed part is one of two heating elements.  I suppressed one to see the impact on the temperature profile if one element was "broken".  That worked on 2012 but not in 2013.  I will have to try something else.

    Please use plain text.
    Distinguished Contributor
    Posts: 220
    Registered: ‎08-30-2012

    Re: Terminal Error: FEM2ESH#82

    02-08-2013 01:44 PM in reply to: cummingsga

    Hi G.A.,

     

    It can be hard to understand the log file, but if my "translation" is correct, the last two things that the software did are as follows:

    1. "Made total 3641 enabled MPCs" from the log file indicates that you are using "smart bonding" because the mesh does not match between some of the parts. If this is the source of the error, it could be that this routine does not recognize that the part is suppressed. If you or the software defined contact with the suppressed part, try to suppress or delete that contact. The contact pairs are listed in the  "Contact (Default: ssss)" of the browser.
    2. "Writing to ESH file in phase II (FEA objects)" in the log file. I think this means that it is taking the loads (convections, constrained temperature, etc) and applying it to the model. For some reason, it may not be recognizing that the load is applied to a suppressed part. If this is the case, you can suppress the loads that are applied to the suppressed part.

     

    John Holtz, PE
    Mechanical Engineer
    Pittsburgh, PA

    15 years experience with Simulation Mechanical
    Please use plain text.
    Member
    Posts: 5
    Registered: ‎09-28-2007

    Re: Terminal Error: FEM2ESH#82

    02-08-2013 01:49 PM in reply to: AstroJohnPE

    That is what I did, I un-suppressed the part and removed the part applied temperature.  It is running now. 

     

    Thanks,

     

    Gary

    Please use plain text.