General Mechanical

General Mechanical

Topics related to Mechanical Enterprise, Motion, Additive Print and more.

nCode Issue with corrupt results

    • karim.el-ghamrawy
      Subscriber

      Hello,

      I am new to nCode and I am trying to use it to calculate the fatigue from 3 different structural modules to accumulate damage from 3 events (1st image). This means there are 3 .rst files input into nCode. These structures are exactly the same and have the same mesh and material. When I map the loads, I see the three results from static structure without problems. When I run the analysis in nCode, there are no errors and the run is completed successfully, however, the result is distorted with the structure disappearing in the fatigue_results_display window (2nd image). Could someone help me understand why this might be happening. Is there a maximum of .rst that could be input into ncode? Any help would be very useful as the resources for nCode are scarce.

       

      Here are some snapshots to explain better the situation

       

    • danielshaw
      Ansys Employee

      Try plotting the results in Mechanical using "External DesignLife Fatigue Results.

       

    • karim.el-ghamrawy
      Subscriber

      Hi,

      Thanks for your response. I am using the standalone ncode module within ansys, and not the one in mechanical. At least I do not have ncode in my outline tree in mechanical. Any advice on how to do that? and another question is, do you know if it is possible to connect multiple static structural modules to the same ncode module, to accummulate the overall damage of let's say 10 static structural stress results?

      Many thanks!

    • danielshaw
      Ansys Employee

      I understand that you are using a WB integrated DesignLife system and not the Mechanical embedded Add-On.  The External DesignLife Fatigue Results option allows you to plot fatigue results calculated using onne of the WB integrated systems from within Mechanical.  You do not need to use the Add-On to plot DesignLife results within Mechanical.

      Yes, you can connect multiple Mechanical systems to one DesignLife system.  Open DesignLife and RMB > Simulation_Input > Properties.  You should see multiple results files.

       

    • karim.el-ghamrawy
      Subscriber

      Hello,

      Thank you for the information. I just need to clarify that I am able to add multiple .rst files in ncode. When the run completes, I cannot see the results, or at least the structure misses a lot of components and it looks corrupt. 

      You mentioned that I can check them using the External DesignLife Fatigue Results. I do not have this in Mechanical. To clarify, when my fatigue is completed in nCode, the module in workbench is not updated as in the following picture

      Can you walk me through the steps of finding the External DesignLife Fatigue Results? Any advice on why the module is not updated?

       

      Many thanks,

    • danielshaw
      Ansys Employee

      You can verify that the results files were read in the Simulation_Input glyph.  You can plot the stresses read from each results file to verify that the proper results files were read.  To access DesignLife results from within Mechanical, you need to RMB > Update the Solution and Results cells of the DesignLife system on Workbench.  As I showed earlier the External DesignLife Fatigue Results is just another Solution output item in Mechanical.

    • karim.el-ghamrawy
      Subscriber

      Ok, thank you, all clear except the External DesignLife Fatigue Results output, it is missing from my outline tree in mechanical. Is there something that I am missing here? 

      Here are some snapshots to show you what I mean:

       

       

      at the top it is shown that systems M and L are connected, but system M (nCode) is not shown in the outline tree. Any advice on why it is not showing in the tree?

       

      Many thanks,

    • danielshaw
      Ansys Employee

      The DesignLife system should not show in the Mechanical UI, but if you RMB > Solution inside Mechanical you should see the option to plot external fatigue results.

    • karim.el-ghamrawy
      Subscriber

       

      Hi again,

      I tried all what we discussed earlier in the thread. There is still the main issue of the results displayed are corrupt. When I tried to add the results in the external fatigue life results object, I got the following message:

      The file I add to the path for the external fatigue life results is the dl_results.csv

      I also get this in nCode:

       

      Initially, when I reset the solution and result component and ran the fatigue analysis for one case, I get the results with no problems. when I start adding more .rst files via connecting static structural modules to nCode, I still got the results. Once I saved and closed WB and reopened, the results are as shown in the previous figure, components disappearing. However, the dl_results, the DataValuesDisplay in nCode show the fatigue life and damage at all the nodes. 

       

      Any suggestion on why this is happening? Is this some kind a bug in the code or there is something I am missing here. Is this a visualisation issue with nCode and ANSYS?

       

      Thanks in advance,

       

    • danielshaw
      Ansys Employee

      Your project is not correctly defined to send multiple results files to one DesignLife system.  From the attached image, you have results cell (#5) from systems H, J, and M linked to the solution cell (#5) of the DL system, but the Mechanical model cells (#4) are not shared.  Therefore, it is possible for the meshes to be different in each Mechanical system.  When using multiple results files, DL requires the meshes to be identical.  Even if the meshes appear to be consistent, Mechanical might have created different contact or surface effect elements or the mesh could be the same, but the node/element numbering could be different. To ensure compatibility with DL, the Mechanical systems must share their model cells.

Viewing 9 reply threads
  • You must be logged in to reply to this topic.