Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Andy last won the day on September 8 2018

Andy had the most liked content!

About Andy

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Country
    United States
  • Are you University user?

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Andy

    [Help] Radioss with Nvidia CUDA 10

    Hi, Unfortunately, GPU calculation is not supported for Radioss explicit. In older versions of Radioss implicit, the GPU could be used but it is no longer supported. It is best to use multiple CPU cores to reduce the run time of your simulation. The Intel MPI is included in Radioss 2017 installation so you should be able to use the <install directory>/altair/scripts/radioss -np # input_0000.rad where # is the number of cores you want to use to run your model. Thanks, Andy
  2. Andy

    Shear failure in bolt

    Hi, I have attached an example model of using two spring in series to model the failure and pretension. For pretension one type 32 spring with a second duplicated element with type13 spring for DOF 2-6. A second TYPE13 spring includes the failure properties. As far as modeling the washer as rigid or not it depends on how detailed of a model you want to create. Thanks, Andy model_001a_0000.rad model_001a_0001.rad
  3. Andy

    Shear failure in bolt

    Hi, Note that /PROP/SPR_PRE (TYPE32) only includes stiffness in the axial direction. If you use TYPE32 you will need to include a second TYPE13 with stiffness in DOF 2-6 to model the other bolt stiffness. Note that RD-T: 3510 tutorial doesn't include the TYPE13 spring. To model the shear failure, you can define failure values in the TYPE13 spring. Please read the comments in the TYPE32 spring about the pretension force curve needed to go to zero to lock the pretension force. If you don't lock the spring then the pretension force is always applied in the model. Thanks, Andy
  4. Hi @fcolomb Sorry for the late reply. Concerning run time,, you can try applying the load faster then the actual forming. This is often still valid if the kinetic energy doesn't get too high. Next, to increase the time step you could use /DT/NODA/CST and define a higher timestep which will add mass in the model. Alternatively, you can artificially increase the density of the whole part to increase the time step. Last instead of using /DT/NODA/CST or increasing the density, you could try using advanced mass scaling. /DT/AMS in the engine and /AMS in the starter. Using AMS you can normally increase the timestep by a factor of 10 - 20 time your original timestep. The AMS method requires more computations so your simulation will run approximately 4-10 time faster. With all these methods, I would recommend running the model a short amount of time with and without these options and compare the results to make sure these options give good results. The amount of mass add using /DT/NODA/CST or using the AMS is model dependent so you have to validate using these options. Last concerning the energy error. I suspect that is coming from the friction which is included in the contact energy. If you have high contact energy relative to your total energy you can get a larger error. Plot the contact energy and compare to the TTE: Translational total energy. If this is true then it is OK to ignore the energy error. Thanks, Andy
  5. Hi, Sorry for the late reply. I agree it seems the material could have too high of a yield stress. Ideally you would have a stress strain test done on the actual material used to make the part and then use that data in your simulation. If you are unable to do that, then you could try using LAW2 and reducing the yield stress to see if that helps. I also wonder if a finer mesh would change the deformation and buckling behavior of the model. Thanks, Andy
  6. Andy

    Density in material PLAS_JOHNS

    Hi, I doubt this is an issue with the time step. Radioss calculates the highest timestep based on the desnity, modulus and mesh size as mentioned by Nachiket Kadu. The change in density/mass could cause the part to fail sooner. It depends how much mass you were adding before and how close the part was to failing. As already suggest check the kinetic energy in both models. If it is a quasi static test then the kinetic energy should remain low in both models. The importance of mass in the simulation is the same as the importance of mass in the test. In both the test and the simulation if the mass is different the physic and energy will be different which can cause a difference in the results. Thanks, Andy
  7. Andy

    Friction in RADIOSS

    Hi, In the 2018.0.1 which is scheduled to be released soon, we will have a new /FRICTION option which can to the same thing as *DEFINE_FRICTION. At this time we do not have any way to define friction in two principal directions. What is the use case for this? Thanks, Andy
  8. Hi, I reviewed your files and ran them a little while. I think the motion is caused by the lack of contact and deformation of the plane. The tool doesn't seem to be hitting the plate very much. The contact gap between your tool and sheet is defined as a constant value of Gapmin=0.01 because Igap=1000. Is the location of tool correct for that small of a contact gap? I would suggest changing to Igap=1 and then the half the thickness of the tool and sheet (more like the actual physical part) will be used to calculate the contact gap between the parts. The initial motion of the tool doesn't cause any plastic strain which seems strange to me. Is this correct? For more accurate stress results set /PROP/SHELL, N=5, I_thick=1 and I_plas=1. You can also make a 2nd contact where the tool is the master and the sheet is the slave. We call this a symmetric contact and with these two contact you basically have a suface to surface contact. Last, I would recommend making your sheet mesh more coarse which will increase the time step of the model and reduce the run time. This will allow you to confirm motion of the tool and contact and get approximate results in a shorter amount of time. Then once those are correct you can go back to your original mesh. Thanks, Andy
  9. Hi, I am glad it is working. There are a few different ways to do the spring back calculation in Radioss. I would suggest running HyperForm and looking at the options in the engine files it creates and using those same commands. There is a tutorial HF-3070: Springback Analysis. It looks like they are saving a state file (*.sta) at the end of the first simulation and then creating a second analysis and include the *.sta file from the first analysis. To create a state file see the /STATE/DT help and comments. You can either rerun your simulation with the state file outputs included or if you still have your *.rst files created at the end of the simulation you could create a second engine file with the state outputs in it and then run the simulation for a short amount of time. This is how to continue a simulation with a second engine file. How to create a second engine file. If the first engine file is named runname_0001.rad. When creating a second engine file the number is increased by 1 for the next engine file to a maximum of 9999 engine files. So, the second engine file would be named runname_0002.rad. To avoid a warning message, the engine file number should also match the Run Number listed in the keyword, /RUN. Example: First Engine file, TensileTest_0001.rad /RUN/TensileTest/1 5.0 /TFILE 0.005 /ANIM/DT 0. 0.5 /ANIM/TENS/STRESS/MEMB /PRINT/-1000 /DT/NODA/CST 0.9 1e-6 Example: Second Engine file TensileTest_0002.rad with changed options. /RUN/TensileTest/2 10.0 /TFILE 0.0005 /ANIM/DT 0. 0.05 /ANIM/TENS/STRESS/MEMB /PRINT/-10 /DYREL 1.00 0.002 /DT/NODA/CST 0.9 1e-7
  10. I was referring to /IMPDISP. /IMPDISP/FGEO moves a set of nodes from a start location to an end location linearly. Your motion doesn't sound linear so I am guessing /IMPDISP/FGEO would not work. My assumption is that the ball for SPF would be rigid so you could create a /RBODY of the ball mesh. Then on the master node of the /RBODY define 3 /IMPDISP and 3 /FUNCT one for each direction (x, y, z). Each /FUNCT would be a be displacement versus time. Like this, /IMPDISP/1 x displacement # Ifunct DIR Iskew Isensor Gnod_id Frame Icoor 224 X 0 0 2858 0 0 # Scale_x Scale_y Tstart Tstop 1 1 0 0 /IMPDISP/2 Y displacement # Ifunct DIR Iskew Isensor Gnod_id Frame Icoor 225 Y 0 0 2858 0 0 # Scale_x Scale_y Tstart Tstop 1 1 0 0 /IMPDISP/1 Z displacement # Ifunct DIR Iskew Isensor Gnod_id Frame Icoor 226 Z 0 0 2858 0 0 # Scale_x Scale_y Tstart Tstop 1 1 0 0 /GRNOD/NODE/2858 IMPDISP_group_2860_of_NODE 3235 /FUNCT/224 X displacment # Time displacement 0 0 1 0.5 2 1.5 3 3.5 ..... /FUNCT/225 Y displacment # Time displacement 0 0 1 0.5 2 1.5 5 5.5 .... /FUNCT/226 Z displacment # Time displacement 0 0 1 0.5 2 1.5 2.6 4.5 ....
  11. Hi, If you can export your x, y, z data as a function of time. Then you could define 3 /IMPDISP, one for each direction with a time versus displacement function for each direction. Does the ball also need to rotate while translating in the x, y, z? Is this for Incremental sheet forming (or ISF, also known as Single Point Forming) ? Thanks, Andy
  12. Hi, /TRANSFORM/ROT will rotate the initial model but that will not make the ball have an imposed movement during the simulation. I believe in /IMPDISP you need to set Icoor=1 and define a local /SKEW Now the x, y, z DIR are. x= radial direction (r), y= azimuthal angular direction ( θ ) z= longitudinal direction (Z) So you need reorient your local system so that the local z direction is the axis you rotate about. Then set DIR=Y to get rotation. I have attached a sample model. Thanks, Andy rotate_0000.rad rotate_0001.rad
  13. Using LAW42, The Mooney Rivlin parameters C10 and C01 can be used to calculate mu and alpha, mu1=2*C10 mu2=-2*C01 alpha1=2 alpha2=-2 For Neo-Hooken use. mu1=2*C10 mu2=0.0 alpha1=2 alpha2=0.0 Last as suggested by Prakash for Yeoh use LAW94 which was added in RADIOSS 2017.2. Thanks, Andy
  14. Andy

    Reaction Force at Time Zero

    I believe this is caused by using the imposed displacement. If you differentiate your imposed displacement curve you will get a non-zero velocity curve at T=0. Thus RADIOSS has to apply a force to get that initial velocity. You could try an imposed velocity and see if that gives you the zero force at t=0. If not and you have contact then maybe the issue is initial penetrations. Usually the initial force caused by imposed displacements does not change the results later in the simulation as compared to using an imposed velocity.
  15. Andy

    Issue with Mat Law 42

    Hi Jonas, For solid parts using LAW42 it is recommended to use Ismtr=10 in /PROP/SOLID. Is is written in the comments in /PROP/SOLID. This probably won't fix the tied contact problem though. The 1157 warning means that there are slave nodes of your tied contact that are not able to be projected to a master surface so they are removed from the tied contact. Please check and see which nodes this happens with to see if these are the nodes that are not being tied correctly. Thanks, Andy