Sheetbody analyze failure

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Hello! 

I want to optimize the beam, but system showes me 'Unable to run'

<?xml version="1.0" encoding="UTF-8"?>image.thumb.png.d707840c910ab15a35a321ce727c9925.png

 

Progress.log file consist of:

# -------------------- Progress Tracker --------------------
hwfdmfeprocessor process id = 6900
# Opening Model
# Model opened successfully
Client  = Inspire    18.0 9508 
Name  = model1 (2) 
ModelName  = Model 
stmodOffsetId  = 2 
# RunType: OPTIRUN_ANALYSIS = 1, OPTIRUN_TOPOLOGY = 2, OPTIRUN_TOPOGRAPHY = 4,  OPTIRUN_SHAPE = 8, OPTIRUN_GAUGE = 16, OSSMOOTH_REANALYSIS = 128 
RunType  = 1 
# Using CAE_HOME='C:/Program Files/Altair/2018/sTInspire2018/unity/bin/win64/'
RUN_STATE = 1 ## Run started
RUN_STATE = 3 ## Generating fresh mesh/Using old mesh
#--------Generating fresh Mesh 
#--------No solid parts found
RUN_STATE = 7 ## Meshing completed successfully
RUN_STATE = 15 ## Realizing model
#--------Unable to populate mesh data for sheet bodies
#--------Unable to realize 
# Error - Unable to ralize synthesis data
RUN_STATE = 1039 ## Done
# --------------------- END -----------------------

 

 

Please, help me to solve thiis problem!


 

Unable to find an attachment - read this blog

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited March 2018

    Dear Ilin Engineering


    I would suggest to convert your sheet surface to a sheet body with the push/pull commando. Instead of specifying a plate with a thickness of 0.01m, you increase the thickness of the plate with 0.01m in order to obtain a body. When I do this, I am able to analyze the model. In the attachment you can find the adapted model. I hope this will help you.


    Regards,


    Michael

    Unable to find an attachment - read this blog

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

     

    please download and install the latest v2018.1 !

    I could reproduce your issue with v2018, with v2018.1 everything is doing fine.

     

    Kind Regards,

    Felix